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:10.990 align:start position:0% [Music] 00:00:10.990 --> 00:00:11.000 align:start position:0% 00:00:11.000 --> 00:00:13.509 align:start position:0% swanik<00:00:12.000> we're<00:00:12.120> going<00:00:12.240> to<00:00:12.360> be<00:00:12.519> jumping<00:00:12.880> into 00:00:13.509 --> 00:00:13.519 align:start position:0% swanik we're going to be jumping into 00:00:13.519 --> 00:00:15.789 align:start position:0% swanik we're going to be jumping into bootstrapping<00:00:14.240> your<00:00:14.440> dapex<00:00:15.240> but<00:00:15.440> first<00:00:15.679> I 00:00:15.789 --> 00:00:15.799 align:start position:0% bootstrapping your dapex but first I 00:00:15.799 --> 00:00:17.630 align:start position:0% bootstrapping your dapex but first I want<00:00:15.920> to<00:00:16.119> ask<00:00:16.400> two 00:00:17.630 --> 00:00:17.640 align:start position:0% want to ask two 00:00:17.640 --> 00:00:20.470 align:start position:0% want to ask two questions<00:00:18.640> who<00:00:18.880> here<00:00:19.199> has<00:00:19.359> struggled<00:00:19.800> to<00:00:20.000> make 00:00:20.470 --> 00:00:20.480 align:start position:0% questions who here has struggled to make 00:00:20.480 --> 00:00:25.950 align:start position:0% questions who here has struggled to make a<00:00:20.720> complex<00:00:21.199> crypto<00:00:21.640> app<00:00:21.960> feel<00:00:22.279> simple<00:00:23.039> to<00:00:23.240> new 00:00:25.950 --> 00:00:25.960 align:start position:0% 00:00:25.960 --> 00:00:28.429 align:start position:0% users<00:00:26.960> and<00:00:27.119> who<00:00:27.320> feels<00:00:27.679> that<00:00:27.920> resource 00:00:28.429 --> 00:00:28.439 align:start position:0% users and who feels that resource 00:00:28.439 --> 00:00:30.790 align:start position:0% users and who feels that resource constraints<00:00:28.960> on<00:00:29.199> their<00:00:29.400> team<00:00:30.039> have<00:00:30.199> made<00:00:30.359> it 00:00:30.790 --> 00:00:30.800 align:start position:0% constraints on their team have made it 00:00:30.800 --> 00:00:35.150 align:start position:0% constraints on their team have made it difficult<00:00:31.119> to<00:00:31.359> create<00:00:31.640> an<00:00:31.880> ideal<00:00:32.279> user 00:00:35.150 --> 00:00:35.160 align:start position:0% 00:00:35.160 --> 00:00:37.670 align:start position:0% experience<00:00:36.160> if<00:00:36.280> you<00:00:36.480> face<00:00:36.840> these<00:00:37.079> challenges 00:00:37.670 --> 00:00:37.680 align:start position:0% experience if you face these challenges 00:00:37.680 --> 00:00:40.830 align:start position:0% experience if you face these challenges you're<00:00:38.040> not<00:00:38.320> alone<00:00:39.320> together<00:00:39.760> we'll<00:00:40.000> be 00:00:40.830 --> 00:00:40.840 align:start position:0% you're not alone together we'll be 00:00:40.840 --> 00:00:43.110 align:start position:0% you're not alone together we'll be discussing<00:00:41.680> how<00:00:41.840> we<00:00:41.960> can<00:00:42.160> Implement<00:00:42.800> best 00:00:43.110 --> 00:00:43.120 align:start position:0% discussing how we can Implement best 00:00:43.120 --> 00:00:45.350 align:start position:0% discussing how we can Implement best practices<00:00:43.760> to<00:00:43.920> help<00:00:44.120> you<00:00:44.320> overcome<00:00:45.039> these 00:00:45.350 --> 00:00:45.360 align:start position:0% practices to help you overcome these 00:00:45.360 --> 00:00:50.549 align:start position:0% practices to help you overcome these challenges<00:00:46.360> and<00:00:46.520> bring<00:00:47.440> the<00:00:47.600> next<00:00:47.920> billion<00:00:48.800> on 00:00:50.549 --> 00:00:50.559 align:start position:0% challenges and bring the next billion on 00:00:50.559 --> 00:00:53.470 align:start position:0% challenges and bring the next billion on chain<00:00:51.559> now<00:00:51.879> before<00:00:52.120> we<00:00:52.280> dive<00:00:52.520> into<00:00:52.800> Solutions 00:00:53.470 --> 00:00:53.480 align:start position:0% chain now before we dive into Solutions 00:00:53.480 --> 00:00:55.990 align:start position:0% chain now before we dive into Solutions allow<00:00:53.719> me<00:00:53.840> to<00:00:54.039> introduce<00:00:54.640> myself<00:00:55.640> you<00:00:55.800> might 00:00:55.990 --> 00:00:56.000 align:start position:0% allow me to introduce myself you might 00:00:56.000 --> 00:00:59.110 align:start position:0% allow me to introduce myself you might know<00:00:56.239> me<00:00:56.520> as<00:00:56.680> the<00:00:56.840> crypto<00:00:57.480> bride<00:00:58.480> about<00:00:58.960> three 00:00:59.110 --> 00:00:59.120 align:start position:0% know me as the crypto bride about three 00:00:59.120 --> 00:01:01.430 align:start position:0% know me as the crypto bride about three and<00:00:59.239> a<00:00:59.359> half<00:00:59.519> years<00:00:59.680> ago<00:01:00.320> I<00:01:00.480> exchanged<00:01:00.960> nft 00:01:01.430 --> 00:01:01.440 align:start position:0% and a half years ago I exchanged nft 00:01:01.440 --> 00:01:03.709 align:start position:0% and a half years ago I exchanged nft wedding<00:01:01.719> rings<00:01:02.079> with<00:01:02.280> my<00:01:02.440> now<00:01:02.719> husband<00:01:03.480> on 00:01:03.709 --> 00:01:03.719 align:start position:0% wedding rings with my now husband on 00:01:03.719 --> 00:01:07.710 align:start position:0% wedding rings with my now husband on ethereum<00:01:04.519> mainnet<00:01:05.519> uh<00:01:05.680> we<00:01:06.200> used<00:01:07.200> of<00:01:07.320> course<00:01:07.560> we 00:01:07.710 --> 00:01:07.720 align:start position:0% ethereum mainnet uh we used of course we 00:01:07.720 --> 00:01:10.109 align:start position:0% ethereum mainnet uh we used of course we overpaid<00:01:08.280> in<00:01:08.520> gas<00:01:09.280> this<00:01:09.400> was<00:01:09.600> before<00:01:09.880> any 00:01:10.109 --> 00:01:10.119 align:start position:0% overpaid in gas this was before any 00:01:10.119 --> 00:01:12.270 align:start position:0% overpaid in gas this was before any layer<00:01:10.400> twos<00:01:10.799> existed<00:01:11.560> but<00:01:11.840> you<00:01:11.960> know<00:01:12.119> what 00:01:12.270 --> 00:01:12.280 align:start position:0% layer twos existed but you know what 00:01:12.280 --> 00:01:14.789 align:start position:0% layer twos existed but you know what they<00:01:12.439> say<00:01:12.880> love<00:01:13.159> is 00:01:14.789 --> 00:01:14.799 align:start position:0% they say love is 00:01:14.799 --> 00:01:17.270 align:start position:0% they say love is priceless<00:01:15.799> and<00:01:16.040> about<00:01:16.240> me<00:01:16.520> professionally 00:01:17.270 --> 00:01:17.280 align:start position:0% priceless and about me professionally 00:01:17.280 --> 00:01:18.830 align:start position:0% priceless and about me professionally I've<00:01:17.400> been<00:01:17.600> designing<00:01:18.000> and<00:01:18.119> leading<00:01:18.439> teams 00:01:18.830 --> 00:01:18.840 align:start position:0% I've been designing and leading teams 00:01:18.840 --> 00:01:20.870 align:start position:0% I've been designing and leading teams for<00:01:19.040> the<00:01:19.200> past<00:01:19.479> 15 00:01:20.870 --> 00:01:20.880 align:start position:0% for the past 15 00:01:20.880 --> 00:01:23.950 align:start position:0% for the past 15 years<00:01:21.880> most<00:01:22.200> recently<00:01:22.880> I<00:01:23.000> led<00:01:23.280> the<00:01:23.400> design<00:01:23.680> of 00:01:23.950 --> 00:01:23.960 align:start position:0% years most recently I led the design of 00:01:23.960 --> 00:01:25.950 align:start position:0% years most recently I led the design of coinbase<00:01:24.439> Commerce<00:01:25.240> where<00:01:25.439> I<00:01:25.560> help 00:01:25.950 --> 00:01:25.960 align:start position:0% coinbase Commerce where I help 00:01:25.960 --> 00:01:30.270 align:start position:0% coinbase Commerce where I help businesses<00:01:26.960> use<00:01:27.360> crypto<00:01:27.799> payments 00:01:30.270 --> 00:01:30.280 align:start position:0% businesses use crypto payments 00:01:30.280 --> 00:01:32.830 align:start position:0% businesses use crypto payments now<00:01:30.560> as<00:01:30.680> a<00:01:30.799> defi<00:01:31.200> design<00:01:31.600> consultant<00:01:32.360> I<00:01:32.520> help 00:01:32.830 --> 00:01:32.840 align:start position:0% now as a defi design consultant I help 00:01:32.840 --> 00:01:35.069 align:start position:0% now as a defi design consultant I help businesses<00:01:33.840> that<00:01:33.960> are<00:01:34.200> tackling<00:01:34.680> the<00:01:34.799> same 00:01:35.069 --> 00:01:35.079 align:start position:0% businesses that are tackling the same 00:01:35.079 --> 00:01:37.510 align:start position:0% businesses that are tackling the same challenges<00:01:35.600> that<00:01:35.759> you're<00:01:36.119> facing<00:01:37.119> so<00:01:37.320> with 00:01:37.510 --> 00:01:37.520 align:start position:0% challenges that you're facing so with 00:01:37.520 --> 00:01:40.069 align:start position:0% challenges that you're facing so with that<00:01:37.880> let's<00:01:38.159> dive<00:01:38.439> in<00:01:38.960> to<00:01:39.240> how<00:01:39.399> we<00:01:39.560> can<00:01:39.759> bring 00:01:40.069 --> 00:01:40.079 align:start position:0% that let's dive in to how we can bring 00:01:40.079 --> 00:01:42.510 align:start position:0% that let's dive in to how we can bring those<00:01:40.399> next<00:01:40.720> billion<00:01:41.280> on 00:01:42.510 --> 00:01:42.520 align:start position:0% those next billion on 00:01:42.520 --> 00:01:45.270 align:start position:0% those next billion on chain<00:01:43.520> to<00:01:43.759> guide<00:01:44.000> us<00:01:44.360> I<00:01:44.439> want<00:01:44.560> to<00:01:44.799> introduce 00:01:45.270 --> 00:01:45.280 align:start position:0% chain to guide us I want to introduce 00:01:45.280 --> 00:01:47.069 align:start position:0% chain to guide us I want to introduce you<00:01:45.479> to<00:01:45.640> a<00:01:45.880> framework<00:01:46.280> that<00:01:46.399> I 00:01:47.069 --> 00:01:47.079 align:start position:0% you to a framework that I 00:01:47.079 --> 00:01:50.109 align:start position:0% you to a framework that I developed<00:01:48.079> through<00:01:48.520> analyzing<00:01:49.399> dozens<00:01:49.799> of 00:01:50.109 --> 00:01:50.119 align:start position:0% developed through analyzing dozens of 00:01:50.119 --> 00:01:53.749 align:start position:0% developed through analyzing dozens of popular<00:01:50.600> defi<00:01:51.240> apps<00:01:52.040> I<00:01:52.200> call<00:01:52.399> it<00:01:52.640> the<00:01:52.799> DAP 00:01:53.749 --> 00:01:53.759 align:start position:0% popular defi apps I call it the DAP 00:01:53.759 --> 00:01:56.670 align:start position:0% popular defi apps I call it the DAP funnel<00:01:54.759> it<00:01:54.880> outlines<00:01:55.360> the<00:01:55.520> key<00:01:55.799> stages<00:01:56.399> people 00:01:56.670 --> 00:01:56.680 align:start position:0% funnel it outlines the key stages people 00:01:56.680 --> 00:01:58.149 align:start position:0% funnel it outlines the key stages people go<00:01:56.920> through<00:01:57.159> when<00:01:57.360> interacting<00:01:57.960> with 00:01:58.149 --> 00:01:58.159 align:start position:0% go through when interacting with 00:01:58.159 --> 00:02:00.429 align:start position:0% go through when interacting with decentralized<00:01:58.960> applications 00:02:00.429 --> 00:02:00.439 align:start position:0% decentralized applications 00:02:00.439 --> 00:02:02.350 align:start position:0% decentralized applications from<00:02:00.680> their<00:02:00.920> first<00:02:01.320> interaction<00:02:02.039> to 00:02:02.350 --> 00:02:02.360 align:start position:0% from their first interaction to 00:02:02.360 --> 00:02:04.109 align:start position:0% from their first interaction to transacting<00:02:03.320> and 00:02:04.109 --> 00:02:04.119 align:start position:0% transacting and 00:02:04.119 --> 00:02:08.790 align:start position:0% transacting and Beyond<00:02:05.119> the<00:02:05.320> stages<00:02:05.719> are<00:02:06.439> connect<00:02:07.679> configure 00:02:08.790 --> 00:02:08.800 align:start position:0% Beyond the stages are connect configure 00:02:08.800 --> 00:02:11.630 align:start position:0% Beyond the stages are connect configure transact<00:02:09.800> and 00:02:11.630 --> 00:02:11.640 align:start position:0% transact and 00:02:11.640 --> 00:02:14.430 align:start position:0% transact and track<00:02:12.640> each<00:02:12.920> stage<00:02:13.680> represents<00:02:14.239> an 00:02:14.430 --> 00:02:14.440 align:start position:0% track each stage represents an 00:02:14.440 --> 00:02:17.350 align:start position:0% track each stage represents an opportunity<00:02:15.120> to<00:02:15.360> either<00:02:15.599> engage<00:02:16.160> people<00:02:17.040> or 00:02:17.350 --> 00:02:17.360 align:start position:0% opportunity to either engage people or 00:02:17.360 --> 00:02:20.390 align:start position:0% opportunity to either engage people or lose<00:02:17.800> them<00:02:18.800> let's<00:02:19.120> begin<00:02:19.800> with<00:02:19.959> the<00:02:20.120> first 00:02:20.390 --> 00:02:20.400 align:start position:0% lose them let's begin with the first 00:02:20.400 --> 00:02:22.470 align:start position:0% lose them let's begin with the first stage 00:02:22.470 --> 00:02:22.480 align:start position:0% stage 00:02:22.480 --> 00:02:25.350 align:start position:0% stage connect<00:02:23.480> this<00:02:23.599> is<00:02:23.879> all<00:02:24.080> about<00:02:24.920> connecting 00:02:25.350 --> 00:02:25.360 align:start position:0% connect this is all about connecting 00:02:25.360 --> 00:02:26.509 align:start position:0% connect this is all about connecting with<00:02:25.480> a 00:02:26.509 --> 00:02:26.519 align:start position:0% with a 00:02:26.519 --> 00:02:29.509 align:start position:0% with a wallet<00:02:27.519> as<00:02:27.640> I<00:02:27.760> was<00:02:27.920> doing<00:02:28.200> my<00:02:28.440> research<00:02:29.200> I 00:02:29.509 --> 00:02:29.519 align:start position:0% wallet as I was doing my research I 00:02:29.519 --> 00:02:32.630 align:start position:0% wallet as I was doing my research I discovered<00:02:30.000> that<00:02:30.120> where<00:02:30.239> to<00:02:30.440> start<00:02:30.879> is<00:02:31.120> often 00:02:32.630 --> 00:02:32.640 align:start position:0% discovered that where to start is often 00:02:32.640 --> 00:02:35.350 align:start position:0% discovered that where to start is often unclear<00:02:33.640> best<00:02:33.920> practice<00:02:34.319> number<00:02:34.560> one<00:02:35.080> make 00:02:35.350 --> 00:02:35.360 align:start position:0% unclear best practice number one make 00:02:35.360 --> 00:02:38.869 align:start position:0% unclear best practice number one make connect 00:02:38.869 --> 00:02:38.879 align:start position:0% 00:02:38.879 --> 00:02:43.509 align:start position:0% obvious<00:02:39.879> let<00:02:40.000> me<00:02:40.200> start<00:02:40.519> with<00:02:40.720> what<00:02:40.959> not<00:02:41.200> to<00:02:41.480> do 00:02:43.509 --> 00:02:43.519 align:start position:0% obvious let me start with what not to do 00:02:43.519 --> 00:02:46.350 align:start position:0% obvious let me start with what not to do don't<00:02:44.519> don't<00:02:44.920> mislead<00:02:45.440> with<00:02:45.599> interactive 00:02:46.350 --> 00:02:46.360 align:start position:0% don't don't mislead with interactive 00:02:46.360 --> 00:02:50.830 align:start position:0% don't don't mislead with interactive zero<00:02:46.959> state<00:02:47.959> so<00:02:48.200> here's<00:02:48.400> an<00:02:48.640> example<00:02:49.239> on<00:02:49.720> B<00:02:50.720> you 00:02:50.830 --> 00:02:50.840 align:start position:0% zero state so here's an example on B you 00:02:50.840 --> 00:02:53.229 align:start position:0% zero state so here's an example on B you can<00:02:51.040> see<00:02:51.400> that<00:02:51.599> I<00:02:51.720> can<00:02:51.959> enter<00:02:52.519> an<00:02:52.720> amount<00:02:53.000> to 00:02:53.229 --> 00:02:53.239 align:start position:0% can see that I can enter an amount to 00:02:53.239 --> 00:02:56.030 align:start position:0% can see that I can enter an amount to deposit<00:02:54.239> but<00:02:54.400> the<00:02:54.560> button<00:02:54.920> is<00:02:55.120> disabled<00:02:55.800> and<00:02:55.920> I 00:02:56.030 --> 00:02:56.040 align:start position:0% deposit but the button is disabled and I 00:02:56.040 --> 00:02:57.630 align:start position:0% deposit but the button is disabled and I don't<00:02:56.239> know<00:02:56.440> what<00:02:56.560> to 00:02:57.630 --> 00:02:57.640 align:start position:0% don't know what to 00:02:57.640 --> 00:03:00.190 align:start position:0% don't know what to do<00:02:58.640> another<00:02:59.040> common<00:02:59.360> mistake<00:02:59.640> is<00:02:59.840> is<00:02:59.959> what<00:03:00.080> we 00:03:00.190 --> 00:03:00.200 align:start position:0% do another common mistake is is what we 00:03:00.200 --> 00:03:04.509 align:start position:0% do another common mistake is is what we see<00:03:00.560> here<00:03:01.280> on<00:03:01.599> pancake<00:03:02.280> swap<00:03:03.280> where<00:03:04.120> somebody 00:03:04.509 --> 00:03:04.519 align:start position:0% see here on pancake swap where somebody 00:03:04.519 --> 00:03:06.910 align:start position:0% see here on pancake swap where somebody comes<00:03:04.799> in<00:03:05.159> wanting<00:03:05.519> to<00:03:05.680> do<00:03:05.879> an<00:03:06.080> action<00:03:06.440> such<00:03:06.640> as 00:03:06.910 --> 00:03:06.920 align:start position:0% comes in wanting to do an action such as 00:03:06.920 --> 00:03:09.949 align:start position:0% comes in wanting to do an action such as swap<00:03:07.599> but<00:03:07.920> the<00:03:08.120> call<00:03:08.360> to<00:03:08.599> action<00:03:09.120> button<00:03:09.519> says 00:03:09.949 --> 00:03:09.959 align:start position:0% swap but the call to action button says 00:03:09.959 --> 00:03:13.710 align:start position:0% swap but the call to action button says connect<00:03:10.760> wallet<00:03:11.760> so<00:03:12.040> any<00:03:12.319> kind<00:03:12.480> of<00:03:12.920> benefit<00:03:13.480> to 00:03:13.710 --> 00:03:13.720 align:start position:0% connect wallet so any kind of benefit to 00:03:13.720 --> 00:03:16.110 align:start position:0% connect wallet so any kind of benefit to surfacing<00:03:14.280> this<00:03:14.480> interactivity<00:03:15.200> is<00:03:15.360> negated 00:03:16.110 --> 00:03:16.120 align:start position:0% surfacing this interactivity is negated 00:03:16.120 --> 00:03:18.030 align:start position:0% surfacing this interactivity is negated by<00:03:16.400> this 00:03:18.030 --> 00:03:18.040 align:start position:0% by this 00:03:18.040 --> 00:03:20.750 align:start position:0% by this disconnect<00:03:19.040> what's<00:03:19.319> better<00:03:19.760> is<00:03:19.920> how<00:03:20.159> Zora<00:03:20.599> and 00:03:20.750 --> 00:03:20.760 align:start position:0% disconnect what's better is how Zora and 00:03:20.760 --> 00:03:23.270 align:start position:0% disconnect what's better is how Zora and Lio<00:03:21.159> and<00:03:21.280> a<00:03:21.360> few<00:03:21.599> others<00:03:22.200> are<00:03:22.519> proactively 00:03:23.270 --> 00:03:23.280 align:start position:0% Lio and a few others are proactively 00:03:23.280 --> 00:03:26.789 align:start position:0% Lio and a few others are proactively surfacing<00:03:23.920> the<00:03:24.080> login 00:03:26.789 --> 00:03:26.799 align:start position:0% 00:03:26.799 --> 00:03:29.149 align:start position:0% screen<00:03:27.799> best<00:03:28.040> practice<00:03:28.400> number<00:03:28.680> two 00:03:29.149 --> 00:03:29.159 align:start position:0% screen best practice number two 00:03:29.159 --> 00:03:31.789 align:start position:0% screen best practice number two streamline 00:03:31.789 --> 00:03:31.799 align:start position:0% 00:03:31.799 --> 00:03:34.470 align:start position:0% options<00:03:32.799> is<00:03:32.959> anyone<00:03:33.319> here<00:03:33.599> designing<00:03:34.120> cross 00:03:34.470 --> 00:03:34.480 align:start position:0% options is anyone here designing cross 00:03:34.480 --> 00:03:35.789 align:start position:0% options is anyone here designing cross chain 00:03:35.789 --> 00:03:35.799 align:start position:0% chain 00:03:35.799 --> 00:03:38.830 align:start position:0% chain DBS<00:03:36.799> awesome<00:03:37.599> here's<00:03:37.920> another<00:03:38.360> example<00:03:38.680> of 00:03:38.830 --> 00:03:38.840 align:start position:0% DBS awesome here's another example of 00:03:38.840 --> 00:03:41.190 align:start position:0% DBS awesome here's another example of what<00:03:39.040> not<00:03:39.200> to<00:03:39.400> do<00:03:39.959> don't<00:03:40.360> combine<00:03:40.760> Network 00:03:41.190 --> 00:03:41.200 align:start position:0% what not to do don't combine Network 00:03:41.200 --> 00:03:43.110 align:start position:0% what not to do don't combine Network selection<00:03:41.799> with<00:03:42.040> wallet<00:03:42.400> selection<00:03:42.920> it's 00:03:43.110 --> 00:03:43.120 align:start position:0% selection with wallet selection it's 00:03:43.120 --> 00:03:45.270 align:start position:0% selection with wallet selection it's just<00:03:43.280> too<00:03:43.480> much<00:03:43.720> information<00:03:44.400> it<00:03:44.560> could<00:03:44.720> be 00:03:45.270 --> 00:03:45.280 align:start position:0% just too much information it could be 00:03:45.280 --> 00:03:47.350 align:start position:0% just too much information it could be handled<00:03:45.760> in<00:03:45.920> multiple 00:03:47.350 --> 00:03:47.360 align:start position:0% handled in multiple 00:03:47.360 --> 00:03:50.910 align:start position:0% handled in multiple steps<00:03:48.360> save<00:03:48.840> time<00:03:49.360> by<00:03:49.760> implementing<00:03:50.760> a 00:03:50.910 --> 00:03:50.920 align:start position:0% steps save time by implementing a 00:03:50.920 --> 00:03:52.750 align:start position:0% steps save time by implementing a ready-made<00:03:51.439> wallet<00:03:51.760> plugin<00:03:52.159> there's<00:03:52.319> so<00:03:52.480> many 00:03:52.750 --> 00:03:52.760 align:start position:0% ready-made wallet plugin there's so many 00:03:52.760 --> 00:03:55.750 align:start position:0% ready-made wallet plugin there's so many options<00:03:53.120> out<00:03:53.400> there<00:03:54.239> that<00:03:54.760> will<00:03:55.040> simplify 00:03:55.750 --> 00:03:55.760 align:start position:0% options out there that will simplify 00:03:55.760 --> 00:03:58.270 align:start position:0% options out there that will simplify your 00:03:58.270 --> 00:03:58.280 align:start position:0% your 00:03:58.280 --> 00:04:01.630 align:start position:0% your onboarding<00:03:59.280> another<00:03:59.959> great<00:04:00.239> option<00:04:00.760> is<00:04:00.959> to 00:04:01.630 --> 00:04:01.640 align:start position:0% onboarding another great option is to 00:04:01.640 --> 00:04:05.149 align:start position:0% onboarding another great option is to combine<00:04:02.640> the<00:04:03.000> disclosures<00:04:04.000> with<00:04:04.319> your<00:04:04.799> wallet 00:04:05.149 --> 00:04:05.159 align:start position:0% combine the disclosures with your wallet 00:04:05.159 --> 00:04:06.630 align:start position:0% combine the disclosures with your wallet connect 00:04:06.630 --> 00:04:06.640 align:start position:0% connect 00:04:06.640 --> 00:04:09.270 align:start position:0% connect screen<00:04:07.640> um<00:04:08.040> people<00:04:08.360> who<00:04:08.480> are<00:04:08.680> familiar<00:04:09.120> with 00:04:09.270 --> 00:04:09.280 align:start position:0% screen um people who are familiar with 00:04:09.280 --> 00:04:11.309 align:start position:0% screen um people who are familiar with web<00:04:09.519> 2<00:04:09.840> will<00:04:10.000> likely<00:04:10.360> click<00:04:10.720> on<00:04:10.920> the<00:04:11.040> upper 00:04:11.309 --> 00:04:11.319 align:start position:0% web 2 will likely click on the upper 00:04:11.319 --> 00:04:13.229 align:start position:0% web 2 will likely click on the upper right<00:04:11.560> corner<00:04:12.360> and<00:04:12.480> they're<00:04:12.640> logged<00:04:12.920> in 00:04:13.229 --> 00:04:13.239 align:start position:0% right corner and they're logged in 00:04:13.239 --> 00:04:15.509 align:start position:0% right corner and they're logged in account<00:04:14.159> don't<00:04:14.360> do<00:04:14.560> what<00:04:14.720> curve<00:04:15.040> does<00:04:15.319> and<00:04:15.439> a 00:04:15.509 --> 00:04:15.519 align:start position:0% account don't do what curve does and a 00:04:15.519 --> 00:04:17.789 align:start position:0% account don't do what curve does and a few<00:04:15.840> others<00:04:16.280> that<00:04:16.560> instantly<00:04:17.040> log<00:04:17.359> out<00:04:17.600> it's 00:04:17.789 --> 00:04:17.799 align:start position:0% few others that instantly log out it's 00:04:17.799 --> 00:04:21.590 align:start position:0% few others that instantly log out it's quite<00:04:18.000> jarring<00:04:18.799> disorienting<00:04:19.720> and<00:04:20.600> instead 00:04:21.590 --> 00:04:21.600 align:start position:0% quite jarring disorienting and instead 00:04:21.600 --> 00:04:23.670 align:start position:0% quite jarring disorienting and instead um<00:04:21.759> offer<00:04:22.160> an<00:04:22.280> interstitial<00:04:22.919> menu<00:04:23.320> this<00:04:23.400> is<00:04:23.520> an 00:04:23.670 --> 00:04:23.680 align:start position:0% um offer an interstitial menu this is an 00:04:23.680 --> 00:04:26.310 align:start position:0% um offer an interstitial menu this is an example<00:04:24.080> from<00:04:24.280> arbitrum<00:04:24.880> bridge<00:04:25.840> where 00:04:26.310 --> 00:04:26.320 align:start position:0% example from arbitrum bridge where 00:04:26.320 --> 00:04:28.350 align:start position:0% example from arbitrum bridge where people<00:04:26.600> can<00:04:26.880> access<00:04:27.320> their<00:04:27.560> settings<00:04:28.120> and 00:04:28.350 --> 00:04:28.360 align:start position:0% people can access their settings and 00:04:28.360 --> 00:04:30.510 align:start position:0% people can access their settings and other<00:04:28.720> options 00:04:30.510 --> 00:04:30.520 align:start position:0% other options 00:04:30.520 --> 00:04:33.350 align:start position:0% other options rounding<00:04:30.960> out<00:04:31.240> this<00:04:31.479> topic<00:04:32.039> of<00:04:32.360> connect 00:04:33.350 --> 00:04:33.360 align:start position:0% rounding out this topic of connect 00:04:33.360 --> 00:04:35.590 align:start position:0% rounding out this topic of connect consider<00:04:33.720> using<00:04:34.000> a<00:04:34.199> pass<00:04:34.560> key<00:04:34.840> this<00:04:34.919> is<00:04:35.080> a 00:04:35.590 --> 00:04:35.600 align:start position:0% consider using a pass key this is a 00:04:35.600 --> 00:04:38.350 align:start position:0% consider using a pass key this is a really<00:04:36.280> awesome<00:04:37.199> Innovation<00:04:38.039> that<00:04:38.160> we're 00:04:38.350 --> 00:04:38.360 align:start position:0% really awesome Innovation that we're 00:04:38.360 --> 00:04:41.270 align:start position:0% really awesome Innovation that we're seeing<00:04:38.759> more<00:04:39.039> people<00:04:39.720> adopt<00:04:40.720> um<00:04:40.880> and<00:04:41.000> I<00:04:41.120> hope 00:04:41.270 --> 00:04:41.280 align:start position:0% seeing more people adopt um and I hope 00:04:41.280 --> 00:04:42.909 align:start position:0% seeing more people adopt um and I hope to<00:04:41.440> see<00:04:41.880> further 00:04:42.909 --> 00:04:42.919 align:start position:0% to see further 00:04:42.919 --> 00:04:46.150 align:start position:0% to see further streamline<00:04:43.919> techniques<00:04:44.680> as<00:04:44.800> we<00:04:44.960> move 00:04:46.150 --> 00:04:46.160 align:start position:0% streamline techniques as we move 00:04:46.160 --> 00:04:49.230 align:start position:0% streamline techniques as we move forward<00:04:47.160> all<00:04:47.360> right<00:04:47.600> moving<00:04:48.000> forward<00:04:48.600> to 00:04:49.230 --> 00:04:49.240 align:start position:0% forward all right moving forward to 00:04:49.240 --> 00:04:51.790 align:start position:0% forward all right moving forward to configure<00:04:50.240> this<00:04:50.440> step<00:04:50.759> is<00:04:50.919> all<00:04:51.120> about<00:04:51.440> setting 00:04:51.790 --> 00:04:51.800 align:start position:0% configure this step is all about setting 00:04:51.800 --> 00:04:54.710 align:start position:0% configure this step is all about setting up<00:04:52.000> the<00:04:52.440> transaction<00:04:53.440> it's<00:04:53.720> about<00:04:54.160> selecting 00:04:54.710 --> 00:04:54.720 align:start position:0% up the transaction it's about selecting 00:04:54.720 --> 00:04:57.550 align:start position:0% up the transaction it's about selecting the<00:04:55.039> asset<00:04:56.039> entering<00:04:56.479> an<00:04:56.680> amount<00:04:57.360> and 00:04:57.550 --> 00:04:57.560 align:start position:0% the asset entering an amount and 00:04:57.560 --> 00:04:59.710 align:start position:0% the asset entering an amount and choosing<00:04:57.960> a<00:04:58.120> network<00:04:58.840> and<00:04:59.199> sometimes 00:04:59.710 --> 00:04:59.720 align:start position:0% choosing a network and sometimes 00:04:59.720 --> 00:05:01.710 align:start position:0% choosing a network and sometimes configuring<00:05:00.160> more<00:05:00.320> advanced 00:05:01.710 --> 00:05:01.720 align:start position:0% configuring more advanced 00:05:01.720 --> 00:05:04.909 align:start position:0% configuring more advanced options<00:05:02.720> and<00:05:02.880> here<00:05:03.120> the<00:05:03.240> two<00:05:03.479> themes<00:05:03.880> are<00:05:04.720> too 00:05:04.909 --> 00:05:04.919 align:start position:0% options and here the two themes are too 00:05:04.919 --> 00:05:07.070 align:start position:0% options and here the two themes are too many<00:05:05.160> choices<00:05:05.639> being<00:05:05.960> overwhelming<00:05:06.960> and 00:05:07.070 --> 00:05:07.080 align:start position:0% many choices being overwhelming and 00:05:07.080 --> 00:05:10.550 align:start position:0% many choices being overwhelming and using<00:05:07.520> technical<00:05:08.080> jargon<00:05:08.919> can<00:05:09.919> can 00:05:10.550 --> 00:05:10.560 align:start position:0% using technical jargon can can 00:05:10.560 --> 00:05:12.710 align:start position:0% using technical jargon can can intimidate 00:05:12.710 --> 00:05:12.720 align:start position:0% intimidate 00:05:12.720 --> 00:05:15.790 align:start position:0% intimidate users<00:05:13.720> let's<00:05:13.960> start<00:05:14.280> with 00:05:15.790 --> 00:05:15.800 align:start position:0% users let's start with 00:05:15.800 --> 00:05:18.870 align:start position:0% users let's start with personalization<00:05:16.800> Pop<00:05:17.120> Quiz<00:05:18.000> do<00:05:18.160> you<00:05:18.319> notice<00:05:18.639> a 00:05:18.870 --> 00:05:18.880 align:start position:0% personalization Pop Quiz do you notice a 00:05:18.880 --> 00:05:21.830 align:start position:0% personalization Pop Quiz do you notice a difference<00:05:19.479> between<00:05:20.080> the<00:05:20.240> logged<00:05:20.600> out<00:05:20.960> stage 00:05:21.830 --> 00:05:21.840 align:start position:0% difference between the logged out stage 00:05:21.840 --> 00:05:23.749 align:start position:0% difference between the logged out stage and<00:05:22.000> the<00:05:22.160> logged<00:05:22.479> in 00:05:23.749 --> 00:05:23.759 align:start position:0% and the logged in 00:05:23.759 --> 00:05:26.990 align:start position:0% and the logged in stage<00:05:24.759> if<00:05:24.880> you<00:05:25.080> answered<00:05:25.600> no<00:05:26.080> you<00:05:26.199> are 00:05:26.990 --> 00:05:27.000 align:start position:0% stage if you answered no you are 00:05:27.000 --> 00:05:29.430 align:start position:0% stage if you answered no you are correct<00:05:28.000> uh<00:05:28.240> this<00:05:28.360> is<00:05:28.440> a<00:05:28.600> missed<00:05:28.919> opportunity 00:05:29.430 --> 00:05:29.440 align:start position:0% correct uh this is a missed opportunity 00:05:29.440 --> 00:05:32.670 align:start position:0% correct uh this is a missed opportunity on<00:05:29.800> fortunately<00:05:30.520> on<00:05:30.759> boring<00:05:31.160> Dow's<00:05:31.800> part 00:05:32.670 --> 00:05:32.680 align:start position:0% on fortunately on boring Dow's part 00:05:32.680 --> 00:05:35.909 align:start position:0% on fortunately on boring Dow's part where<00:05:33.360> uh<00:05:33.560> it's<00:05:33.840> not<00:05:34.240> suggesting<00:05:35.080> a<00:05:35.240> token<00:05:35.720> or 00:05:35.909 --> 00:05:35.919 align:start position:0% where uh it's not suggesting a token or 00:05:35.919 --> 00:05:37.390 align:start position:0% where uh it's not suggesting a token or a 00:05:37.390 --> 00:05:37.400 align:start position:0% a 00:05:37.400 --> 00:05:40.230 align:start position:0% a network<00:05:38.400> instead<00:05:38.960> do<00:05:39.199> what<00:05:39.319> unisoft<00:05:39.919> does 00:05:40.230 --> 00:05:40.240 align:start position:0% network instead do what unisoft does 00:05:40.240 --> 00:05:42.790 align:start position:0% network instead do what unisoft does here<00:05:40.880> where<00:05:41.120> it's<00:05:41.479> suggesting<00:05:42.039> tokens<00:05:42.440> in<00:05:42.600> my 00:05:42.790 --> 00:05:42.800 align:start position:0% here where it's suggesting tokens in my 00:05:42.800 --> 00:05:45.189 align:start position:0% here where it's suggesting tokens in my wallet<00:05:43.440> and<00:05:43.680> even<00:05:44.080> suggesting<00:05:44.840> prior 00:05:45.189 --> 00:05:45.199 align:start position:0% wallet and even suggesting prior 00:05:45.199 --> 00:05:48.270 align:start position:0% wallet and even suggesting prior searches<00:05:45.800> from<00:05:46.240> previous<00:05:46.960> sessions<00:05:47.960> so<00:05:48.120> it 00:05:48.270 --> 00:05:48.280 align:start position:0% searches from previous sessions so it 00:05:48.280 --> 00:05:50.510 align:start position:0% searches from previous sessions so it really<00:05:48.520> feels<00:05:48.919> like<00:05:49.160> they<00:05:49.360> know 00:05:50.510 --> 00:05:50.520 align:start position:0% really feels like they know 00:05:50.520 --> 00:05:54.189 align:start position:0% really feels like they know me<00:05:51.520> another<00:05:52.360> thoughtful<00:05:52.880> approach<00:05:53.880> is 00:05:54.189 --> 00:05:54.199 align:start position:0% me another thoughtful approach is 00:05:54.199 --> 00:05:57.189 align:start position:0% me another thoughtful approach is personalizing<00:05:54.960> by<00:05:55.240> Persona<00:05:56.039> so<00:05:56.240> look<00:05:56.400> at<00:05:56.800> here 00:05:57.189 --> 00:05:57.199 align:start position:0% personalizing by Persona so look at here 00:05:57.199 --> 00:06:00.749 align:start position:0% personalizing by Persona so look at here how<00:05:57.960> blur<00:05:58.800> has<00:05:59.039> two<00:05:59.280> different<00:05:59.759> user<00:06:00.120> types 00:06:00.749 --> 00:06:00.759 align:start position:0% how blur has two different user types 00:06:00.759 --> 00:06:02.749 align:start position:0% how blur has two different user types there's<00:06:01.000> the<00:06:01.160> trader<00:06:01.880> who<00:06:02.039> wants<00:06:02.280> a<00:06:02.440> more 00:06:02.749 --> 00:06:02.759 align:start position:0% there's the trader who wants a more 00:06:02.759 --> 00:06:05.430 align:start position:0% there's the trader who wants a more information<00:06:03.280> dense<00:06:03.639> View<00:06:04.400> and<00:06:04.600> The<00:06:04.759> Collector 00:06:05.430 --> 00:06:05.440 align:start position:0% information dense View and The Collector 00:06:05.440 --> 00:06:08.309 align:start position:0% information dense View and The Collector who<00:06:05.600> wants<00:06:05.800> a<00:06:06.000> more<00:06:06.240> curated 00:06:08.309 --> 00:06:08.319 align:start position:0% who wants a more curated 00:06:08.319 --> 00:06:12.749 align:start position:0% who wants a more curated experience<00:06:09.360> similarly<00:06:10.680> similarly<00:06:11.680> on<00:06:11.919> bridge 00:06:12.749 --> 00:06:12.759 align:start position:0% experience similarly similarly on bridge 00:06:12.759 --> 00:06:15.350 align:start position:0% experience similarly similarly on bridge there's<00:06:12.960> an<00:06:13.240> expert<00:06:13.759> mode<00:06:14.759> um<00:06:14.880> and<00:06:15.039> this<00:06:15.160> is 00:06:15.350 --> 00:06:15.360 align:start position:0% there's an expert mode um and this is 00:06:15.360 --> 00:06:17.309 align:start position:0% there's an expert mode um and this is great<00:06:15.520> great<00:06:15.840> if<00:06:15.960> you<00:06:16.080> feel<00:06:16.360> like<00:06:16.560> you<00:06:16.880> might 00:06:17.309 --> 00:06:17.319 align:start position:0% great great if you feel like you might 00:06:17.319 --> 00:06:19.830 align:start position:0% great great if you feel like you might be<00:06:17.599> alienating<00:06:18.479> some<00:06:18.680> of<00:06:18.800> your<00:06:19.000> power<00:06:19.280> users 00:06:19.830 --> 00:06:19.840 align:start position:0% be alienating some of your power users 00:06:19.840 --> 00:06:22.430 align:start position:0% be alienating some of your power users by<00:06:20.039> simplifying<00:06:20.720> too<00:06:21.039> much<00:06:21.880> this<00:06:22.039> way<00:06:22.280> they 00:06:22.430 --> 00:06:22.440 align:start position:0% by simplifying too much this way they 00:06:22.440 --> 00:06:26.350 align:start position:0% by simplifying too much this way they can<00:06:22.720> easily<00:06:23.240> access<00:06:23.720> those<00:06:23.919> more<00:06:24.160> advanced 00:06:26.350 --> 00:06:26.360 align:start position:0% can easily access those more advanced 00:06:26.360 --> 00:06:28.950 align:start position:0% can easily access those more advanced features<00:06:27.360> starting<00:06:27.720> with<00:06:27.919> good<00:06:28.120> defaults 00:06:28.950 --> 00:06:28.960 align:start position:0% features starting with good defaults 00:06:28.960 --> 00:06:31.350 align:start position:0% features starting with good defaults should<00:06:29.199> minim<00:06:29.919> the<00:06:30.080> cognitive<00:06:30.479> load<00:06:30.960> but<00:06:31.160> what 00:06:31.350 --> 00:06:31.360 align:start position:0% should minim the cognitive load but what 00:06:31.360 --> 00:06:34.510 align:start position:0% should minim the cognitive load but what happens<00:06:32.039> when<00:06:32.440> people<00:06:33.240> encounter<00:06:33.800> errors<00:06:34.400> we 00:06:34.510 --> 00:06:34.520 align:start position:0% happens when people encounter errors we 00:06:34.520 --> 00:06:36.870 align:start position:0% happens when people encounter errors we need<00:06:34.680> to<00:06:34.919> enable<00:06:35.479> better<00:06:35.840> recovery<00:06:36.599> and 00:06:36.870 --> 00:06:36.880 align:start position:0% need to enable better recovery and 00:06:36.880 --> 00:06:39.150 align:start position:0% need to enable better recovery and hopefully<00:06:37.280> prevent<00:06:37.720> them<00:06:38.520> let<00:06:38.639> me<00:06:38.800> start<00:06:39.039> with 00:06:39.150 --> 00:06:39.160 align:start position:0% hopefully prevent them let me start with 00:06:39.160 --> 00:06:41.830 align:start position:0% hopefully prevent them let me start with a<00:06:39.360> great<00:06:39.680> example<00:06:40.160> of<00:06:40.479> error<00:06:40.919> prevention<00:06:41.680> here 00:06:41.830 --> 00:06:41.840 align:start position:0% a great example of error prevention here 00:06:41.840 --> 00:06:45.189 align:start position:0% a great example of error prevention here on<00:06:42.120> Hop<00:06:42.840> it's<00:06:43.080> suggesting<00:06:43.919> a<00:06:44.120> minimum<00:06:44.599> amount 00:06:45.189 --> 00:06:45.199 align:start position:0% on Hop it's suggesting a minimum amount 00:06:45.199 --> 00:06:48.150 align:start position:0% on Hop it's suggesting a minimum amount for<00:06:45.400> me<00:06:45.599> to<00:06:45.840> send<00:06:46.199> so<00:06:46.400> I<00:06:46.560> don't<00:06:46.919> get<00:06:47.199> an<00:06:47.440> insuff 00:06:48.150 --> 00:06:48.160 align:start position:0% for me to send so I don't get an insuff 00:06:48.160 --> 00:06:50.870 align:start position:0% for me to send so I don't get an insuff insufficient<00:06:48.800> funds 00:06:50.870 --> 00:06:50.880 align:start position:0% insufficient funds 00:06:50.880 --> 00:06:53.189 align:start position:0% insufficient funds error<00:06:51.880> be<00:06:52.039> sure<00:06:52.240> to<00:06:52.440> check<00:06:52.680> your<00:06:52.880> error 00:06:53.189 --> 00:06:53.199 align:start position:0% error be sure to check your error 00:06:53.199 --> 00:06:55.469 align:start position:0% error be sure to check your error messages<00:06:53.759> this<00:06:53.880> is<00:06:54.120> a<00:06:54.800> a<00:06:54.919> really<00:06:55.160> great 00:06:55.469 --> 00:06:55.479 align:start position:0% messages this is a a really great 00:06:55.479 --> 00:06:58.270 align:start position:0% messages this is a a really great example<00:06:56.039> of<00:06:56.639> how<00:06:56.879> somebody<00:06:57.599> may<00:06:57.879> have 00:06:58.270 --> 00:06:58.280 align:start position:0% example of how somebody may have 00:06:58.280 --> 00:07:01.350 align:start position:0% example of how somebody may have forgotten<00:06:58.879> to<00:06:59.800> translate<00:07:00.479> this<00:07:00.720> into 00:07:01.350 --> 00:07:01.360 align:start position:0% forgotten to translate this into 00:07:01.360 --> 00:07:03.390 align:start position:0% forgotten to translate this into something<00:07:01.800> that<00:07:01.960> makes<00:07:02.280> sense<00:07:02.800> explaining 00:07:03.390 --> 00:07:03.400 align:start position:0% something that makes sense explaining 00:07:03.400 --> 00:07:05.230 align:start position:0% something that makes sense explaining what<00:07:03.639> happened<00:07:04.160> and<00:07:04.360> what<00:07:04.520> the<00:07:04.639> user<00:07:04.879> needs<00:07:05.120> to 00:07:05.230 --> 00:07:05.240 align:start position:0% what happened and what the user needs to 00:07:05.240 --> 00:07:06.510 align:start position:0% what happened and what the user needs to do<00:07:05.479> to<00:07:05.680> fix 00:07:06.510 --> 00:07:06.520 align:start position:0% do to fix 00:07:06.520 --> 00:07:09.589 align:start position:0% do to fix it<00:07:07.520> and<00:07:07.759> double<00:07:08.160> check<00:07:08.560> that<00:07:09.319> what<00:07:09.440> you're 00:07:09.589 --> 00:07:09.599 align:start position:0% it and double check that what you're 00:07:09.599 --> 00:07:13.150 align:start position:0% it and double check that what you're saying<00:07:10.120> to<00:07:10.360> fix<00:07:10.599> it<00:07:10.960> actually 00:07:13.150 --> 00:07:13.160 align:start position:0% saying to fix it actually 00:07:13.160 --> 00:07:16.629 align:start position:0% saying to fix it actually works<00:07:14.160> instead<00:07:14.680> deep<00:07:14.960> link<00:07:15.240> into<00:07:15.560> the<00:07:15.759> wallet 00:07:16.629 --> 00:07:16.639 align:start position:0% works instead deep link into the wallet 00:07:16.639 --> 00:07:20.830 align:start position:0% works instead deep link into the wallet to<00:07:17.639> overcome<00:07:18.240> that<00:07:18.440> issue<00:07:18.879> recover<00:07:19.520> here<00:07:20.280> as 00:07:20.830 --> 00:07:20.840 align:start position:0% to overcome that issue recover here as 00:07:20.840 --> 00:07:23.309 align:start position:0% to overcome that issue recover here as igen<00:07:21.199> layer<00:07:21.520> does<00:07:21.960> by<00:07:22.680> switching<00:07:23.080> to<00:07:23.199> a 00:07:23.309 --> 00:07:23.319 align:start position:0% igen layer does by switching to a 00:07:23.319 --> 00:07:25.390 align:start position:0% igen layer does by switching to a supported<00:07:23.759> Network<00:07:24.080> in<00:07:24.240> this 00:07:25.390 --> 00:07:25.400 align:start position:0% supported Network in this 00:07:25.400 --> 00:07:28.390 align:start position:0% supported Network in this case<00:07:26.400> I<00:07:26.520> recommend<00:07:27.120> Progressive<00:07:27.680> disclosure 00:07:28.390 --> 00:07:28.400 align:start position:0% case I recommend Progressive disclosure 00:07:28.400 --> 00:07:30.990 align:start position:0% case I recommend Progressive disclosure also<00:07:28.720> to<00:07:28.919> simplify<00:07:29.400> the<00:07:29.560> the 00:07:30.990 --> 00:07:31.000 align:start position:0% also to simplify the the 00:07:31.000 --> 00:07:33.309 align:start position:0% also to simplify the the interface<00:07:32.000> here<00:07:32.160> on<00:07:32.319> llama<00:07:32.759> swap<00:07:33.199> the 00:07:33.309 --> 00:07:33.319 align:start position:0% interface here on llama swap the 00:07:33.319 --> 00:07:35.790 align:start position:0% interface here on llama swap the slippage<00:07:33.879> options<00:07:34.560> are<00:07:34.840> visible<00:07:35.199> at<00:07:35.440> all 00:07:35.790 --> 00:07:35.800 align:start position:0% slippage options are visible at all 00:07:35.800 --> 00:07:39.510 align:start position:0% slippage options are visible at all times<00:07:36.879> which<00:07:37.879> it<00:07:38.000> makes<00:07:38.280> the<00:07:38.479> interface<00:07:39.039> too 00:07:39.510 --> 00:07:39.520 align:start position:0% times which it makes the interface too 00:07:39.520 --> 00:07:42.990 align:start position:0% times which it makes the interface too cluttered<00:07:40.440> and<00:07:40.960> it<00:07:41.080> can<00:07:41.360> increase<00:07:42.360> the<00:07:42.599> drop 00:07:42.990 --> 00:07:43.000 align:start position:0% cluttered and it can increase the drop 00:07:43.000 --> 00:07:44.309 align:start position:0% cluttered and it can increase the drop off 00:07:44.309 --> 00:07:44.319 align:start position:0% off 00:07:44.319 --> 00:07:47.110 align:start position:0% off right<00:07:45.319> here's<00:07:45.639> another<00:07:45.960> example<00:07:46.319> on<00:07:46.520> beefy 00:07:47.110 --> 00:07:47.120 align:start position:0% right here's another example on beefy 00:07:47.120 --> 00:07:48.790 align:start position:0% right here's another example on beefy where<00:07:47.240> it's<00:07:47.400> showing<00:07:47.879> the<00:07:48.039> increments<00:07:48.599> from 00:07:48.790 --> 00:07:48.800 align:start position:0% where it's showing the increments from 00:07:48.800 --> 00:07:51.790 align:start position:0% where it's showing the increments from 0o<00:07:49.199> to<00:07:49.639> 100<00:07:50.199> probably<00:07:50.599> not<00:07:50.759> a<00:07:50.960> widely<00:07:51.280> used 00:07:51.790 --> 00:07:51.800 align:start position:0% 0o to 100 probably not a widely used 00:07:51.800 --> 00:07:54.149 align:start position:0% 0o to 100 probably not a widely used feature<00:07:52.800> and<00:07:53.159> it<00:07:53.280> makes<00:07:53.560> it<00:07:53.720> look<00:07:53.840> a<00:07:53.919> little 00:07:54.149 --> 00:07:54.159 align:start position:0% feature and it makes it look a little 00:07:54.159 --> 00:07:57.510 align:start position:0% feature and it makes it look a little messy<00:07:55.159> instead<00:07:55.919> check<00:07:56.120> out<00:07:56.319> how<00:07:56.520> Thor<00:07:56.879> swap 00:07:57.510 --> 00:07:57.520 align:start position:0% messy instead check out how Thor swap 00:07:57.520 --> 00:07:59.510 align:start position:0% messy instead check out how Thor swap buries<00:07:58.039> those<00:07:58.319> options<00:07:58.800> underneath<00:07:59.159> the<00:07:59.280> m 00:07:59.510 --> 00:07:59.520 align:start position:0% buries those options underneath the m 00:07:59.520 --> 00:08:00.950 align:start position:0% buries those options underneath the m Max 00:08:00.950 --> 00:08:00.960 align:start position:0% Max 00:08:00.960 --> 00:08:03.790 align:start position:0% Max button<00:08:01.960> so<00:08:02.120> for<00:08:02.360> the<00:08:02.560> items<00:08:02.960> that<00:08:03.120> are<00:08:03.440> visible 00:08:03.790 --> 00:08:03.800 align:start position:0% button so for the items that are visible 00:08:03.800 --> 00:08:06.550 align:start position:0% button so for the items that are visible in<00:08:03.919> your<00:08:04.159> interface<00:08:04.919> I<00:08:05.199> recommend<00:08:06.199> showing 00:08:06.550 --> 00:08:06.560 align:start position:0% in your interface I recommend showing 00:08:06.560 --> 00:08:08.830 align:start position:0% in your interface I recommend showing some<00:08:06.800> education<00:08:07.520> providing<00:08:07.840> more<00:08:08.159> context<00:08:08.639> to 00:08:08.830 --> 00:08:08.840 align:start position:0% some education providing more context to 00:08:08.840 --> 00:08:11.309 align:start position:0% some education providing more context to increase<00:08:09.400> confidence<00:08:09.960> in<00:08:10.120> the 00:08:11.309 --> 00:08:11.319 align:start position:0% increase confidence in the 00:08:11.319 --> 00:08:14.070 align:start position:0% increase confidence in the transaction<00:08:12.319> so<00:08:12.520> let's<00:08:12.759> avoid<00:08:13.080> using<00:08:13.440> jargon 00:08:14.070 --> 00:08:14.080 align:start position:0% transaction so let's avoid using jargon 00:08:14.080 --> 00:08:17.230 align:start position:0% transaction so let's avoid using jargon here's<00:08:14.280> an<00:08:14.520> example<00:08:15.520> from<00:08:15.800> rocket<00:08:16.240> pool<00:08:16.879> where 00:08:17.230 --> 00:08:17.240 align:start position:0% here's an example from rocket pool where 00:08:17.240 --> 00:08:19.830 align:start position:0% here's an example from rocket pool where it's<00:08:17.479> using<00:08:18.360> a<00:08:18.520> term<00:08:18.840> that<00:08:19.080> probably<00:08:19.479> everyone 00:08:19.830 --> 00:08:19.840 align:start position:0% it's using a term that probably everyone 00:08:19.840 --> 00:08:22.670 align:start position:0% it's using a term that probably everyone in<00:08:20.039> this<00:08:20.240> room<00:08:20.599> knows<00:08:21.199> main<00:08:21.560> net<00:08:22.400> but<00:08:22.560> it 00:08:22.670 --> 00:08:22.680 align:start position:0% in this room knows main net but it 00:08:22.680 --> 00:08:25.149 align:start position:0% in this room knows main net but it doesn't<00:08:23.120> map<00:08:23.520> to<00:08:23.879> an<00:08:24.080> option<00:08:24.440> within<00:08:24.759> most 00:08:25.149 --> 00:08:25.159 align:start position:0% doesn't map to an option within most 00:08:25.159 --> 00:08:27.629 align:start position:0% doesn't map to an option within most wallets<00:08:26.159> so<00:08:26.360> instead<00:08:26.720> use<00:08:26.960> straightforward 00:08:27.629 --> 00:08:27.639 align:start position:0% wallets so instead use straightforward 00:08:27.639 --> 00:08:30.430 align:start position:0% wallets so instead use straightforward language 00:08:30.430 --> 00:08:30.440 align:start position:0% language 00:08:30.440 --> 00:08:33.670 align:start position:0% language tool<00:08:30.800> tips<00:08:31.000> are<00:08:31.159> a<00:08:31.319> great<00:08:32.000> option<00:08:32.640> to<00:08:33.240> explain 00:08:33.670 --> 00:08:33.680 align:start position:0% tool tips are a great option to explain 00:08:33.680 --> 00:08:34.509 align:start position:0% tool tips are a great option to explain in 00:08:34.509 --> 00:08:34.519 align:start position:0% in 00:08:34.519 --> 00:08:37.909 align:start position:0% in detail<00:08:35.519> everything<00:08:36.279> that<00:08:36.440> a<00:08:36.680> transaction<00:08:37.399> it 00:08:37.909 --> 00:08:37.919 align:start position:0% detail everything that a transaction it 00:08:37.919 --> 00:08:40.269 align:start position:0% detail everything that a transaction it uh 00:08:40.269 --> 00:08:40.279 align:start position:0% uh 00:08:40.279 --> 00:08:43.029 align:start position:0% uh has<00:08:41.279> I<00:08:41.440> also<00:08:41.680> recommend<00:08:42.240> including<00:08:42.839> a 00:08:43.029 --> 00:08:43.039 align:start position:0% has I also recommend including a 00:08:43.039 --> 00:08:45.590 align:start position:0% has I also recommend including a confirmation<00:08:43.640> screen<00:08:44.440> that<00:08:44.600> gives<00:08:44.959> the<00:08:45.080> user 00:08:45.590 --> 00:08:45.600 align:start position:0% confirmation screen that gives the user 00:08:45.600 --> 00:08:48.389 align:start position:0% confirmation screen that gives the user an<00:08:45.800> opportunity<00:08:46.680> to<00:08:46.959> review<00:08:47.600> all<00:08:47.760> of<00:08:47.920> the 00:08:48.389 --> 00:08:48.399 align:start position:0% an opportunity to review all of the 00:08:48.399 --> 00:08:52.150 align:start position:0% an opportunity to review all of the details<00:08:49.399> before<00:08:49.720> moving 00:08:52.150 --> 00:08:52.160 align:start position:0% 00:08:52.160 --> 00:08:54.670 align:start position:0% forward<00:08:53.160> assuming<00:08:53.640> all<00:08:53.760> the<00:08:53.920> details<00:08:54.279> in<00:08:54.480> that 00:08:54.670 --> 00:08:54.680 align:start position:0% forward assuming all the details in that 00:08:54.680 --> 00:08:56.790 align:start position:0% forward assuming all the details in that transaction<00:08:55.279> look<00:08:55.600> good<00:08:55.959> we're<00:08:56.279> ready<00:08:56.519> to 00:08:56.790 --> 00:08:56.800 align:start position:0% transaction look good we're ready to 00:08:56.800 --> 00:09:00.470 align:start position:0% transaction look good we're ready to transact<00:08:57.640> this<00:08:57.760> is<00:08:58.000> the<00:08:58.200> core<00:08:58.720> of<00:08:58.920> all 00:09:00.470 --> 00:09:00.480 align:start position:0% transact this is the core of all 00:09:00.480 --> 00:09:03.110 align:start position:0% transact this is the core of all applications<00:09:01.480> um<00:09:01.720> it's<00:09:01.959> where<00:09:02.519> people 00:09:03.110 --> 00:09:03.120 align:start position:0% applications um it's where people 00:09:03.120 --> 00:09:07.069 align:start position:0% applications um it's where people authorize<00:09:04.120> access<00:09:04.440> to<00:09:04.640> their<00:09:04.920> funds<00:09:05.920> and 00:09:07.069 --> 00:09:07.079 align:start position:0% authorize access to their funds and 00:09:07.079 --> 00:09:09.470 align:start position:0% authorize access to their funds and transfer<00:09:08.079> it's<00:09:08.320> critical<00:09:08.800> that<00:09:08.959> people<00:09:09.160> feel 00:09:09.470 --> 00:09:09.480 align:start position:0% transfer it's critical that people feel 00:09:09.480 --> 00:09:10.430 align:start position:0% transfer it's critical that people feel safe 00:09:10.430 --> 00:09:10.440 align:start position:0% safe 00:09:10.440 --> 00:09:13.630 align:start position:0% safe here<00:09:11.440> unfortunately<00:09:12.320> lengthy<00:09:12.800> approvals<00:09:13.440> can 00:09:13.630 --> 00:09:13.640 align:start position:0% here unfortunately lengthy approvals can 00:09:13.640 --> 00:09:15.630 align:start position:0% here unfortunately lengthy approvals can scare<00:09:14.079> and 00:09:15.630 --> 00:09:15.640 align:start position:0% scare and 00:09:15.640 --> 00:09:18.829 align:start position:0% scare and confuse<00:09:16.640> the<00:09:16.839> best<00:09:17.160> antidote<00:09:18.040> antidote<00:09:18.600> to 00:09:18.829 --> 00:09:18.839 align:start position:0% confuse the best antidote antidote to 00:09:18.839 --> 00:09:21.630 align:start position:0% confuse the best antidote antidote to that<00:09:19.279> is<00:09:19.399> to<00:09:19.560> convey 00:09:21.630 --> 00:09:21.640 align:start position:0% that is to convey 00:09:21.640 --> 00:09:25.389 align:start position:0% that is to convey progress<00:09:22.640> okay<00:09:22.800> who's<00:09:23.040> used<00:09:23.440> a<00:09:23.800> in<00:09:23.959> this<00:09:24.399> room 00:09:25.389 --> 00:09:25.399 align:start position:0% progress okay who's used a in this room 00:09:25.399 --> 00:09:27.910 align:start position:0% progress okay who's used a in this room probably<00:09:25.920> everyone<00:09:26.680> right<00:09:27.120> it's<00:09:27.360> like<00:09:27.680> one<00:09:27.760> of 00:09:27.910 --> 00:09:27.920 align:start position:0% probably everyone right it's like one of 00:09:27.920 --> 00:09:30.590 align:start position:0% probably everyone right it's like one of the<00:09:28.079> oldest<00:09:28.600> most<00:09:28.800> popular<00:09:29.160> d<00:09:29.600> out<00:09:29.880> there<00:09:30.399> but 00:09:30.590 --> 00:09:30.600 align:start position:0% the oldest most popular d out there but 00:09:30.600 --> 00:09:33.470 align:start position:0% the oldest most popular d out there but unfortunately<00:09:31.480> it<00:09:31.600> uses<00:09:32.079> buttons<00:09:32.440> in<00:09:32.560> a<00:09:32.760> very 00:09:33.470 --> 00:09:33.480 align:start position:0% unfortunately it uses buttons in a very 00:09:33.480 --> 00:09:35.949 align:start position:0% unfortunately it uses buttons in a very non-standard<00:09:34.240> way<00:09:34.519> this<00:09:34.600> is<00:09:34.760> not<00:09:34.959> the<00:09:35.200> best 00:09:35.949 --> 00:09:35.959 align:start position:0% non-standard way this is not the best 00:09:35.959 --> 00:09:38.310 align:start position:0% non-standard way this is not the best component<00:09:36.920> for<00:09:37.160> showing<00:09:37.560> a<00:09:37.720> multi-step 00:09:38.310 --> 00:09:38.320 align:start position:0% component for showing a multi-step 00:09:38.320 --> 00:09:40.910 align:start position:0% component for showing a multi-step transaction<00:09:39.000> you<00:09:39.120> see<00:09:39.320> how<00:09:39.560> they<00:09:40.120> appear<00:09:40.680> and 00:09:40.910 --> 00:09:40.920 align:start position:0% transaction you see how they appear and 00:09:40.920 --> 00:09:44.350 align:start position:0% transaction you see how they appear and disappear<00:09:41.920> without<00:09:42.279> any<00:09:42.480> kind<00:09:42.600> of 00:09:44.350 --> 00:09:44.360 align:start position:0% disappear without any kind of 00:09:44.360 --> 00:09:46.630 align:start position:0% disappear without any kind of confirmation<00:09:45.360> what's<00:09:45.519> a<00:09:45.640> better<00:09:45.959> pattern<00:09:46.519> is 00:09:46.630 --> 00:09:46.640 align:start position:0% confirmation what's a better pattern is 00:09:46.640 --> 00:09:50.069 align:start position:0% confirmation what's a better pattern is what<00:09:46.800> Unis<00:09:47.160> swap<00:09:47.720> does<00:09:48.720> a<00:09:48.920> stepper<00:09:49.760> right<00:09:49.920> it 00:09:50.069 --> 00:09:50.079 align:start position:0% what Unis swap does a stepper right it 00:09:50.079 --> 00:09:53.150 align:start position:0% what Unis swap does a stepper right it shows<00:09:50.920> what<00:09:51.040> are<00:09:51.240> the<00:09:51.440> actions<00:09:52.000> that<00:09:52.360> are 00:09:53.150 --> 00:09:53.160 align:start position:0% shows what are the actions that are 00:09:53.160 --> 00:09:56.670 align:start position:0% shows what are the actions that are required<00:09:54.160> what<00:09:54.279> are<00:09:54.480> the<00:09:54.680> status<00:09:55.640> pending<00:09:56.440> and 00:09:56.670 --> 00:09:56.680 align:start position:0% required what are the status pending and 00:09:56.680 --> 00:10:00.150 align:start position:0% required what are the status pending and confirmed 00:10:00.150 --> 00:10:00.160 align:start position:0% 00:10:00.160 --> 00:10:02.590 align:start position:0% I<00:10:00.320> also<00:10:00.640> recommend<00:10:01.200> showing<00:10:01.640> in<00:10:02.040> context 00:10:02.590 --> 00:10:02.600 align:start position:0% I also recommend showing in context 00:10:02.600 --> 00:10:04.630 align:start position:0% I also recommend showing in context feedback<00:10:03.200> through<00:10:03.440> toast<00:10:03.920> messages<00:10:04.440> as 00:10:04.630 --> 00:10:04.640 align:start position:0% feedback through toast messages as 00:10:04.640 --> 00:10:07.710 align:start position:0% feedback through toast messages as Aerodrome<00:10:05.480> does 00:10:07.710 --> 00:10:07.720 align:start position:0% Aerodrome does 00:10:07.720 --> 00:10:10.949 align:start position:0% Aerodrome does here<00:10:08.720> don't<00:10:09.079> misrepresent<00:10:10.000> status<00:10:10.519> so<00:10:10.760> here's 00:10:10.949 --> 00:10:10.959 align:start position:0% here don't misrepresent status so here's 00:10:10.959 --> 00:10:13.310 align:start position:0% here don't misrepresent status so here's an<00:10:11.200> example<00:10:11.720> from<00:10:11.920> Lio<00:10:12.880> which<00:10:13.040> is 00:10:13.310 --> 00:10:13.320 align:start position:0% an example from Lio which is 00:10:13.320 --> 00:10:15.150 align:start position:0% an example from Lio which is optimistically 00:10:15.150 --> 00:10:15.160 align:start position:0% optimistically 00:10:15.160 --> 00:10:17.430 align:start position:0% optimistically presenting<00:10:16.160> modals<00:10:16.720> saying<00:10:17.079> you<00:10:17.240> are 00:10:17.430 --> 00:10:17.440 align:start position:0% presenting modals saying you are 00:10:17.440 --> 00:10:20.790 align:start position:0% presenting modals saying you are unlocking<00:10:18.120> you<00:10:18.240> are<00:10:19.240> wrapping<00:10:20.240> uh<00:10:20.399> but<00:10:20.519> it's 00:10:20.790 --> 00:10:20.800 align:start position:0% unlocking you are wrapping uh but it's 00:10:20.800 --> 00:10:22.750 align:start position:0% unlocking you are wrapping uh but it's before<00:10:21.160> I've<00:10:21.360> even<00:10:21.600> had<00:10:21.720> an<00:10:21.959> opportunity<00:10:22.560> to 00:10:22.750 --> 00:10:22.760 align:start position:0% before I've even had an opportunity to 00:10:22.760 --> 00:10:24.710 align:start position:0% before I've even had an opportunity to confirm<00:10:23.120> in<00:10:23.279> my<00:10:23.480> wallet<00:10:23.880> so<00:10:24.040> it's<00:10:24.200> not<00:10:24.360> really 00:10:24.710 --> 00:10:24.720 align:start position:0% confirm in my wallet so it's not really 00:10:24.720 --> 00:10:26.670 align:start position:0% confirm in my wallet so it's not really accurate<00:10:25.279> and<00:10:25.399> it<00:10:25.519> reduces<00:10:26.040> my<00:10:26.240> trust<00:10:26.519> in 00:10:26.670 --> 00:10:26.680 align:start position:0% accurate and it reduces my trust in 00:10:26.680 --> 00:10:27.590 align:start position:0% accurate and it reduces my trust in their 00:10:27.590 --> 00:10:27.600 align:start position:0% their 00:10:27.600 --> 00:10:30.069 align:start position:0% their system<00:10:28.600> instead 00:10:30.069 --> 00:10:30.079 align:start position:0% system instead 00:10:30.079 --> 00:10:33.150 align:start position:0% system instead uh<00:10:30.240> do<00:10:30.560> as<00:10:31.160> as<00:10:31.320> moonwell<00:10:31.920> does<00:10:32.680> which 00:10:33.150 --> 00:10:33.160 align:start position:0% uh do as as moonwell does which 00:10:33.160 --> 00:10:35.910 align:start position:0% uh do as as moonwell does which encourages<00:10:34.160> once<00:10:34.519> I've<00:10:34.800> reached<00:10:35.200> the<00:10:35.360> pending 00:10:35.910 --> 00:10:35.920 align:start position:0% encourages once I've reached the pending 00:10:35.920 --> 00:10:42.110 align:start position:0% encourages once I've reached the pending status<00:10:36.839> to<00:10:37.399> continue<00:10:37.920> using<00:10:38.720> the 00:10:42.110 --> 00:10:42.120 align:start position:0% 00:10:42.120 --> 00:10:43.990 align:start position:0% application<00:10:43.120> okay<00:10:43.320> this<00:10:43.440> one's<00:10:43.680> a<00:10:43.760> little 00:10:43.990 --> 00:10:44.000 align:start position:0% application okay this one's a little 00:10:44.000 --> 00:10:46.030 align:start position:0% application okay this one's a little controversial<00:10:44.680> but<00:10:44.839> rounding<00:10:45.360> out<00:10:45.839> the 00:10:46.030 --> 00:10:46.040 align:start position:0% controversial but rounding out the 00:10:46.040 --> 00:10:50.670 align:start position:0% controversial but rounding out the transact<00:10:47.320> phase<00:10:48.519> um<00:10:49.519> let's<00:10:49.800> not<00:10:50.000> do<00:10:50.279> infinite 00:10:50.670 --> 00:10:50.680 align:start position:0% transact phase um let's not do infinite 00:10:50.680 --> 00:10:53.670 align:start position:0% transact phase um let's not do infinite approvals<00:10:51.399> you<00:10:51.519> see<00:10:51.800> this<00:10:52.160> long<00:10:52.560> scary<00:10:53.000> Red 00:10:53.670 --> 00:10:53.680 align:start position:0% approvals you see this long scary Red 00:10:53.680 --> 00:10:56.750 align:start position:0% approvals you see this long scary Red text<00:10:54.680> uh<00:10:54.959> this<00:10:55.600> you<00:10:55.760> know<00:10:56.160> with<00:10:56.279> the<00:10:56.440> current 00:10:56.750 --> 00:10:56.760 align:start position:0% text uh this you know with the current 00:10:56.760 --> 00:10:59.269 align:start position:0% text uh this you know with the current constraints<00:10:57.200> we're<00:10:57.399> in<00:10:57.680> right<00:10:57.880> now<00:10:58.760> um<00:10:59.040> May 00:10:59.269 --> 00:10:59.279 align:start position:0% constraints we're in right now um May 00:10:59.279 --> 00:11:00.710 align:start position:0% constraints we're in right now um May maybe<00:10:59.480> a<00:10:59.519> lot<00:10:59.639> of<00:10:59.800> this<00:10:59.920> will<00:11:00.079> be<00:11:00.240> solved<00:11:00.600> with 00:11:00.710 --> 00:11:00.720 align:start position:0% maybe a lot of this will be solved with 00:11:00.720 --> 00:11:03.509 align:start position:0% maybe a lot of this will be solved with smart<00:11:01.279> wallets<00:11:02.279> uh<00:11:02.399> but<00:11:02.560> until<00:11:02.959> then<00:11:03.320> let's 00:11:03.509 --> 00:11:03.519 align:start position:0% smart wallets uh but until then let's 00:11:03.519 --> 00:11:07.150 align:start position:0% smart wallets uh but until then let's use<00:11:03.920> exact<00:11:05.000> amounts<00:11:06.000> so<00:11:06.240> that<00:11:06.480> it<00:11:06.639> maps<00:11:07.000> to 00:11:07.150 --> 00:11:07.160 align:start position:0% use exact amounts so that it maps to 00:11:07.160 --> 00:11:09.629 align:start position:0% use exact amounts so that it maps to what<00:11:07.360> the<00:11:07.480> user<00:11:07.920> entered<00:11:08.360> into<00:11:08.600> the<00:11:08.800> system 00:11:09.629 --> 00:11:09.639 align:start position:0% what the user entered into the system 00:11:09.639 --> 00:11:12.870 align:start position:0% what the user entered into the system and<00:11:09.760> it's<00:11:09.920> also<00:11:10.120> more 00:11:12.870 --> 00:11:12.880 align:start position:0% 00:11:12.880 --> 00:11:16.350 align:start position:0% secure<00:11:13.880> now<00:11:14.160> the<00:11:14.320> final<00:11:14.680> stage<00:11:15.279> track<00:11:16.040> this<00:11:16.160> is 00:11:16.350 --> 00:11:16.360 align:start position:0% secure now the final stage track this is 00:11:16.360 --> 00:11:18.790 align:start position:0% secure now the final stage track this is all<00:11:16.639> about<00:11:17.160> monitoring<00:11:17.760> the<00:11:17.959> status<00:11:18.600> so 00:11:18.790 --> 00:11:18.800 align:start position:0% all about monitoring the status so 00:11:18.800 --> 00:11:20.910 align:start position:0% all about monitoring the status so people<00:11:19.079> know<00:11:19.440> what<00:11:19.720> happened<00:11:20.279> and<00:11:20.480> what<00:11:20.680> they 00:11:20.910 --> 00:11:20.920 align:start position:0% people know what happened and what they 00:11:20.920 --> 00:11:23.430 align:start position:0% people know what happened and what they can<00:11:21.160> do 00:11:23.430 --> 00:11:23.440 align:start position:0% can do 00:11:23.440 --> 00:11:26.910 align:start position:0% can do next<00:11:24.440> here<00:11:24.839> we<00:11:25.040> observe<00:11:25.760> limited<00:11:26.279> access<00:11:26.600> to 00:11:26.910 --> 00:11:26.920 align:start position:0% next here we observe limited access to 00:11:26.920 --> 00:11:31.269 align:start position:0% next here we observe limited access to historical<00:11:27.800> and<00:11:28.000> ongoing<00:11:28.519> performance 00:11:31.269 --> 00:11:31.279 align:start position:0% 00:11:31.279 --> 00:11:33.430 align:start position:0% here<00:11:31.399> are<00:11:31.639> the<00:11:31.920> three<00:11:32.440> stages<00:11:33.160> of<00:11:33.279> the 00:11:33.430 --> 00:11:33.440 align:start position:0% here are the three stages of the 00:11:33.440 --> 00:11:35.550 align:start position:0% here are the three stages of the tracking<00:11:33.839> life<00:11:34.120> cycle<00:11:34.360> in<00:11:34.519> most<00:11:34.760> STS<00:11:35.320> There's 00:11:35.550 --> 00:11:35.560 align:start position:0% tracking life cycle in most STS There's 00:11:35.560 --> 00:11:37.750 align:start position:0% tracking life cycle in most STS There's real<00:11:35.880> time<00:11:36.279> ongoing<00:11:36.920> historical<00:11:37.519> let<00:11:37.600> me 00:11:37.750 --> 00:11:37.760 align:start position:0% real time ongoing historical let me 00:11:37.760 --> 00:11:38.710 align:start position:0% real time ongoing historical let me break<00:11:37.920> it 00:11:38.710 --> 00:11:38.720 align:start position:0% break it 00:11:38.720 --> 00:11:41.590 align:start position:0% break it down<00:11:39.720> for<00:11:39.959> real<00:11:40.320> time<00:11:40.600> we<00:11:40.800> covered<00:11:41.240> that<00:11:41.440> in 00:11:41.590 --> 00:11:41.600 align:start position:0% down for real time we covered that in 00:11:41.600 --> 00:11:44.829 align:start position:0% down for real time we covered that in the<00:11:41.800> previous<00:11:42.560> section<00:11:43.600> transact<00:11:44.600> and<00:11:44.760> this 00:11:44.829 --> 00:11:44.839 align:start position:0% the previous section transact and this 00:11:44.839 --> 00:11:47.710 align:start position:0% the previous section transact and this is<00:11:45.000> all<00:11:45.160> about<00:11:45.519> in<00:11:45.959> the<00:11:46.120> moment<00:11:46.680> when<00:11:46.839> you're 00:11:47.710 --> 00:11:47.720 align:start position:0% is all about in the moment when you're 00:11:47.720 --> 00:11:51.790 align:start position:0% is all about in the moment when you're investing<00:11:48.720> you<00:11:49.200> receive<00:11:49.880> that<00:11:50.519> feedback 00:11:51.790 --> 00:11:51.800 align:start position:0% investing you receive that feedback 00:11:51.800 --> 00:11:54.790 align:start position:0% investing you receive that feedback right<00:11:52.800> but<00:11:52.959> on<00:11:53.320> going<00:11:53.639> is<00:11:53.839> missing<00:11:54.440> right<00:11:54.639> we 00:11:54.790 --> 00:11:54.800 align:start position:0% right but on going is missing right we 00:11:54.800 --> 00:11:56.550 align:start position:0% right but on going is missing right we we<00:11:54.880> want<00:11:55.000> to<00:11:55.560> understand<00:11:55.760> the<00:11:55.920> day-to-day 00:11:56.550 --> 00:11:56.560 align:start position:0% we want to understand the day-to-day 00:11:56.560 --> 00:11:58.990 align:start position:0% we want to understand the day-to-day performance<00:11:57.079> of<00:11:57.399> Investments<00:11:58.399> including 00:11:58.990 --> 00:11:59.000 align:start position:0% performance of Investments including 00:11:59.000 --> 00:12:01.590 align:start position:0% performance of Investments including return<00:11:59.240> returns<00:11:59.639> and<00:11:59.800> the<00:12:00.320> yield<00:12:01.320> uh<00:12:01.440> the 00:12:01.590 --> 00:12:01.600 align:start position:0% return returns and the yield uh the 00:12:01.600 --> 00:12:04.190 align:start position:0% return returns and the yield uh the patterns<00:12:02.000> we<00:12:02.120> see<00:12:02.320> here<00:12:02.480> are<00:12:02.720> dashboards 00:12:04.190 --> 00:12:04.200 align:start position:0% patterns we see here are dashboards 00:12:04.200 --> 00:12:06.470 align:start position:0% patterns we see here are dashboards notifications<00:12:05.200> um<00:12:05.399> this<00:12:05.519> helps<00:12:05.880> people<00:12:06.240> make 00:12:06.470 --> 00:12:06.480 align:start position:0% notifications um this helps people make 00:12:06.480 --> 00:12:09.990 align:start position:0% notifications um this helps people make investment<00:12:06.959> decisions<00:12:07.639> what<00:12:07.760> to<00:12:07.920> do 00:12:09.990 --> 00:12:10.000 align:start position:0% investment decisions what to do 00:12:10.000 --> 00:12:13.470 align:start position:0% investment decisions what to do next<00:12:11.000> and<00:12:11.120> then<00:12:11.600> the<00:12:11.839> history<00:12:12.480> we're<00:12:13.120> this<00:12:13.240> is 00:12:13.470 --> 00:12:13.480 align:start position:0% next and then the history we're this is 00:12:13.480 --> 00:12:14.550 align:start position:0% next and then the history we're this is all<00:12:13.639> about 00:12:14.550 --> 00:12:14.560 align:start position:0% all about 00:12:14.560 --> 00:12:16.670 align:start position:0% all about recordkeeping<00:12:15.560> um<00:12:15.720> of<00:12:15.880> the<00:12:16.040> past 00:12:16.670 --> 00:12:16.680 align:start position:0% recordkeeping um of the past 00:12:16.680 --> 00:12:19.269 align:start position:0% recordkeeping um of the past transactions<00:12:17.680> account<00:12:18.040> statements<00:12:18.959> and<00:12:19.120> this 00:12:19.269 --> 00:12:19.279 align:start position:0% transactions account statements and this 00:12:19.279 --> 00:12:21.590 align:start position:0% transactions account statements and this enables 00:12:21.590 --> 00:12:21.600 align:start position:0% enables 00:12:21.600 --> 00:12:24.110 align:start position:0% enables accounting<00:12:22.600> it's<00:12:22.839> critical<00:12:23.279> that<00:12:23.399> we<00:12:23.600> support 00:12:24.110 --> 00:12:24.120 align:start position:0% accounting it's critical that we support 00:12:24.120 --> 00:12:27.230 align:start position:0% accounting it's critical that we support each<00:12:24.360> step<00:12:24.600> of<00:12:24.760> this<00:12:24.959> journey<00:12:25.880> in<00:12:26.079> our 00:12:27.230 --> 00:12:27.240 align:start position:0% each step of this journey in our 00:12:27.240 --> 00:12:30.110 align:start position:0% each step of this journey in our debth<00:12:28.240> so<00:12:28.720> how<00:12:28.839> do<00:12:29.000> we<00:12:29.320> support<00:12:29.639> ongoing 00:12:30.110 --> 00:12:30.120 align:start position:0% debth so how do we support ongoing 00:12:30.120 --> 00:12:32.110 align:start position:0% debth so how do we support ongoing performance 00:12:32.110 --> 00:12:32.120 align:start position:0% performance 00:12:32.120 --> 00:12:35.990 align:start position:0% performance tracking<00:12:33.120> let's<00:12:33.440> provide<00:12:34.000> apy<00:12:34.839> history<00:12:35.839> uh 00:12:35.990 --> 00:12:36.000 align:start position:0% tracking let's provide apy history uh 00:12:36.000 --> 00:12:38.550 align:start position:0% tracking let's provide apy history uh this<00:12:36.120> is<00:12:36.199> an<00:12:36.399> example<00:12:36.760> from<00:12:36.959> a<00:12:37.639> it's<00:12:37.959> very<00:12:38.199> rare 00:12:38.550 --> 00:12:38.560 align:start position:0% this is an example from a it's very rare 00:12:38.560 --> 00:12:41.110 align:start position:0% this is an example from a it's very rare I<00:12:38.639> did<00:12:38.800> not<00:12:39.000> see<00:12:39.440> many<00:12:39.720> of<00:12:40.000> these<00:12:40.440> in<00:12:40.600> my<00:12:40.760> audit 00:12:41.110 --> 00:12:41.120 align:start position:0% I did not see many of these in my audit 00:12:41.120 --> 00:12:43.790 align:start position:0% I did not see many of these in my audit please<00:12:41.320> share<00:12:41.720> examples<00:12:42.160> if<00:12:42.279> you<00:12:42.480> have<00:12:42.800> them 00:12:43.790 --> 00:12:43.800 align:start position:0% please share examples if you have them 00:12:43.800 --> 00:12:47.030 align:start position:0% please share examples if you have them um<00:12:44.680> you<00:12:44.839> know<00:12:45.199> anecdotally<00:12:46.040> a<00:12:46.160> friend<00:12:46.320> of<00:12:46.480> mine 00:12:47.030 --> 00:12:47.040 align:start position:0% um you know anecdotally a friend of mine 00:12:47.040 --> 00:12:50.550 align:start position:0% um you know anecdotally a friend of mine takes<00:12:47.399> screenshots<00:12:48.399> of<00:12:49.000> the<00:12:49.199> apps<00:12:49.480> where<00:12:49.639> he's 00:12:50.550 --> 00:12:50.560 align:start position:0% takes screenshots of the apps where he's 00:12:50.560 --> 00:12:54.670 align:start position:0% takes screenshots of the apps where he's invested<00:12:51.560> uh<00:12:51.800> to<00:12:52.399> see<00:12:52.760> whether<00:12:52.959> or<00:12:53.079> not<00:12:53.680> his 00:12:54.670 --> 00:12:54.680 align:start position:0% invested uh to see whether or not his 00:12:54.680 --> 00:12:59.230 align:start position:0% invested uh to see whether or not his apy<00:12:55.360> has<00:12:55.519> gone<00:12:55.839> down<00:12:56.600> which<00:12:56.720> is<00:12:56.839> not<00:12:57.120> ideal 00:12:59.230 --> 00:12:59.240 align:start position:0% apy has gone down which is not ideal 00:12:59.240 --> 00:13:01.430 align:start position:0% apy has gone down which is not ideal let's<00:12:59.480> also<00:13:00.079> summarize<00:13:00.639> the<00:13:00.760> portfolio 00:13:01.430 --> 00:13:01.440 align:start position:0% let's also summarize the portfolio 00:13:01.440 --> 00:13:03.670 align:start position:0% let's also summarize the portfolio insights<00:13:02.240> this<00:13:02.360> is<00:13:02.480> from<00:13:02.720> Aerodrome<00:13:03.519> a 00:13:03.670 --> 00:13:03.680 align:start position:0% insights this is from Aerodrome a 00:13:03.680 --> 00:13:06.430 align:start position:0% insights this is from Aerodrome a dashboard<00:13:04.320> that<00:13:04.440> shows<00:13:04.920> kind<00:13:05.040> of<00:13:05.160> the<00:13:05.440> return 00:13:06.430 --> 00:13:06.440 align:start position:0% dashboard that shows kind of the return 00:13:06.440 --> 00:13:08.629 align:start position:0% dashboard that shows kind of the return and<00:13:06.839> the<00:13:07.160> emissions<00:13:07.839> and<00:13:08.079> other<00:13:08.279> things<00:13:08.480> that 00:13:08.629 --> 00:13:08.639 align:start position:0% and the emissions and other things that 00:13:08.639 --> 00:13:10.030 align:start position:0% and the emissions and other things that I 00:13:10.030 --> 00:13:10.040 align:start position:0% I 00:13:10.040 --> 00:13:12.870 align:start position:0% I earned<00:13:11.040> this<00:13:11.199> is<00:13:11.600> definitely<00:13:12.000> not<00:13:12.199> the<00:13:12.399> best 00:13:12.870 --> 00:13:12.880 align:start position:0% earned this is definitely not the best 00:13:12.880 --> 00:13:16.389 align:start position:0% earned this is definitely not the best but<00:13:13.160> I<00:13:13.680> I<00:13:13.920> challenge<00:13:14.519> you<00:13:14.800> to<00:13:15.240> provide<00:13:15.680> better 00:13:16.389 --> 00:13:16.399 align:start position:0% but I I challenge you to provide better 00:13:16.399 --> 00:13:20.069 align:start position:0% but I I challenge you to provide better examples<00:13:17.680> um<00:13:18.680> I<00:13:18.760> want<00:13:18.880> to<00:13:19.000> leave<00:13:19.519> rounding<00:13:19.880> out 00:13:20.069 --> 00:13:20.079 align:start position:0% examples um I want to leave rounding out 00:13:20.079 --> 00:13:21.750 align:start position:0% examples um I want to leave rounding out this<00:13:20.199> ongoing<00:13:20.639> performance<00:13:21.160> topic<00:13:21.480> I<00:13:21.560> feel 00:13:21.750 --> 00:13:21.760 align:start position:0% this ongoing performance topic I feel 00:13:21.760 --> 00:13:23.949 align:start position:0% this ongoing performance topic I feel like<00:13:21.880> a<00:13:22.040> missed<00:13:22.360> opportunity<00:13:23.000> here<00:13:23.480> is<00:13:23.680> push 00:13:23.949 --> 00:13:23.959 align:start position:0% like a missed opportunity here is push 00:13:23.959 --> 00:13:25.990 align:start position:0% like a missed opportunity here is push notifications<00:13:24.639> for<00:13:24.880> crypto<00:13:25.680> I<00:13:25.760> think<00:13:25.920> there 00:13:25.990 --> 00:13:26.000 align:start position:0% notifications for crypto I think there 00:13:26.000 --> 00:13:28.710 align:start position:0% notifications for crypto I think there are<00:13:26.079> a<00:13:26.199> few<00:13:26.440> Solutions<00:13:26.959> out<00:13:27.240> there<00:13:28.120> but<00:13:28.480> it's 00:13:28.710 --> 00:13:28.720 align:start position:0% are a few Solutions out there but it's 00:13:28.720 --> 00:13:31.350 align:start position:0% are a few Solutions out there but it's very<00:13:29.199> much<00:13:29.440> lacking<00:13:30.440> um<00:13:30.600> here's<00:13:30.800> an<00:13:31.000> example 00:13:31.350 --> 00:13:31.360 align:start position:0% very much lacking um here's an example 00:13:31.360 --> 00:13:33.990 align:start position:0% very much lacking um here's an example from<00:13:31.519> a<00:13:31.639> trafi<00:13:32.320> account<00:13:32.800> I<00:13:33.120> received<00:13:33.440> a<00:13:33.800> an 00:13:33.990 --> 00:13:34.000 align:start position:0% from a trafi account I received a an 00:13:34.000 --> 00:13:36.629 align:start position:0% from a trafi account I received a an email<00:13:34.959> notifying<00:13:35.560> me<00:13:35.839> that<00:13:35.959> the<00:13:36.079> yield<00:13:36.399> went 00:13:36.629 --> 00:13:36.639 align:start position:0% email notifying me that the yield went 00:13:36.639 --> 00:13:40.110 align:start position:0% email notifying me that the yield went down<00:13:36.880> on<00:13:37.079> one<00:13:37.160> of<00:13:37.279> my<00:13:37.800> accounts<00:13:38.800> um<00:13:39.480> you<00:13:39.639> know 00:13:40.110 --> 00:13:40.120 align:start position:0% down on one of my accounts um you know 00:13:40.120 --> 00:13:42.310 align:start position:0% down on one of my accounts um you know how<00:13:40.240> do<00:13:40.399> we<00:13:40.560> know<00:13:41.000> if<00:13:41.120> we're<00:13:41.320> about<00:13:41.480> to<00:13:41.639> get 00:13:42.310 --> 00:13:42.320 align:start position:0% how do we know if we're about to get 00:13:42.320 --> 00:13:45.670 align:start position:0% how do we know if we're about to get wrecked<00:13:43.320> that's<00:13:43.800> that's<00:13:44.000> kind<00:13:44.120> of<00:13:44.279> a<00:13:44.720> core<00:13:45.279> use 00:13:45.670 --> 00:13:45.680 align:start position:0% wrecked that's that's kind of a core use 00:13:45.680 --> 00:13:46.829 align:start position:0% wrecked that's that's kind of a core use case<00:13:45.880> for<00:13:46.079> a 00:13:46.829 --> 00:13:46.839 align:start position:0% case for a 00:13:46.839 --> 00:13:50.389 align:start position:0% case for a notification<00:13:47.839> um<00:13:48.600> and<00:13:49.160> I<00:13:49.399> I<00:13:49.680> i'<00:13:49.839> welcome<00:13:50.240> some 00:13:50.389 --> 00:13:50.399 align:start position:0% notification um and I I i' welcome some 00:13:50.399 --> 00:13:52.310 align:start position:0% notification um and I I i' welcome some solutions 00:13:52.310 --> 00:13:52.320 align:start position:0% solutions 00:13:52.320 --> 00:13:55.470 align:start position:0% solutions there<00:13:53.320> finally<00:13:54.199> raise<00:13:54.519> your<00:13:54.759> hand<00:13:55.160> if<00:13:55.279> you've 00:13:55.470 --> 00:13:55.480 align:start position:0% there finally raise your hand if you've 00:13:55.480 --> 00:13:59.710 align:start position:0% there finally raise your hand if you've ever<00:13:55.680> tried<00:13:55.959> doing<00:13:56.480> taxes<00:13:57.079> on<00:13:57.279> your<00:13:57.519> crypto 00:13:59.710 --> 00:13:59.720 align:start position:0% ever tried doing taxes on your crypto 00:13:59.720 --> 00:14:01.710 align:start position:0% ever tried doing taxes on your crypto it's<00:13:59.839> a<00:14:00.040> nightmare 00:14:01.710 --> 00:14:01.720 align:start position:0% it's a nightmare 00:14:01.720 --> 00:14:04.910 align:start position:0% it's a nightmare right<00:14:02.720> uh<00:14:03.040> so<00:14:03.279> on<00:14:03.440> uniswap<00:14:04.440> you<00:14:04.560> could<00:14:04.720> see 00:14:04.910 --> 00:14:04.920 align:start position:0% right uh so on uniswap you could see 00:14:04.920 --> 00:14:06.670 align:start position:0% right uh so on uniswap you could see that<00:14:05.040> there's<00:14:05.279> transaction<00:14:05.880> history<00:14:06.560> but 00:14:06.670 --> 00:14:06.680 align:start position:0% that there's transaction history but 00:14:06.680 --> 00:14:11.310 align:start position:0% that there's transaction history but this<00:14:06.800> is<00:14:06.959> not<00:14:07.240> a<00:14:07.440> common<00:14:07.720> feature<00:14:08.079> in<00:14:08.240> most 00:14:11.310 --> 00:14:11.320 align:start position:0% 00:14:11.320 --> 00:14:14.670 align:start position:0% apps<00:14:12.320> and<00:14:12.519> here<00:14:12.680> on<00:14:12.839> dbank<00:14:13.360> you<00:14:13.519> can<00:14:13.680> see<00:14:14.519> an 00:14:14.670 --> 00:14:14.680 align:start position:0% apps and here on dbank you can see an 00:14:14.680 --> 00:14:16.629 align:start position:0% apps and here on dbank you can see an example<00:14:15.040> of<00:14:15.240> aggregating<00:14:15.839> statuses<00:14:16.440> but 00:14:16.629 --> 00:14:16.639 align:start position:0% example of aggregating statuses but 00:14:16.639 --> 00:14:18.590 align:start position:0% example of aggregating statuses but again<00:14:16.920> this<00:14:17.040> is<00:14:17.360> this<00:14:17.480> is<00:14:17.560> a<00:14:17.720> third<00:14:18.000> party<00:14:18.440> it's 00:14:18.590 --> 00:14:18.600 align:start position:0% again this is this is a third party it's 00:14:18.600 --> 00:14:21.749 align:start position:0% again this is this is a third party it's a<00:14:18.720> little<00:14:18.920> lagging<00:14:19.800> and<00:14:20.800> it<00:14:21.120> the<00:14:21.320> source<00:14:21.560> of 00:14:21.749 --> 00:14:21.759 align:start position:0% a little lagging and it the source of 00:14:21.759 --> 00:14:24.189 align:start position:0% a little lagging and it the source of Truth<00:14:22.079> should<00:14:22.279> be<00:14:22.639> on<00:14:22.839> your<00:14:23.079> dap 00:14:24.189 --> 00:14:24.199 align:start position:0% Truth should be on your dap 00:14:24.199 --> 00:14:27.110 align:start position:0% Truth should be on your dap itself<00:14:25.199> all<00:14:25.399> right<00:14:25.600> so<00:14:25.759> we<00:14:25.920> covered<00:14:26.360> all<00:14:26.560> of 00:14:27.110 --> 00:14:27.120 align:start position:0% itself all right so we covered all of 00:14:27.120 --> 00:14:31.749 align:start position:0% itself all right so we covered all of that<00:14:28.120> woo<00:14:29.279> so<00:14:29.519> here's<00:14:29.959> the<00:14:30.480> big<00:14:30.720> takeaway<00:14:31.360> here 00:14:31.749 --> 00:14:31.759 align:start position:0% that woo so here's the big takeaway here 00:14:31.759 --> 00:14:34.030 align:start position:0% that woo so here's the big takeaway here I<00:14:31.880> hope<00:14:32.079> that<00:14:32.240> you<00:14:32.360> can<00:14:32.600> Implement<00:14:33.600> some<00:14:33.800> of 00:14:34.030 --> 00:14:34.040 align:start position:0% I hope that you can Implement some of 00:14:34.040 --> 00:14:36.670 align:start position:0% I hope that you can Implement some of these<00:14:34.720> best<00:14:35.040> practices<00:14:35.639> in<00:14:35.800> your<00:14:35.959> dab<00:14:36.279> today 00:14:36.670 --> 00:14:36.680 align:start position:0% these best practices in your dab today 00:14:36.680 --> 00:14:42.030 align:start position:0% these best practices in your dab today to<00:14:36.880> enable<00:14:37.360> better<00:14:37.639> adoption<00:14:38.639> and 00:14:42.030 --> 00:14:42.040 align:start position:0% 00:14:42.040 --> 00:14:44.670 align:start position:0% retention<00:14:43.040> well<00:14:43.399> I'll<00:14:43.519> let<00:14:43.759> people<00:14:44.360> finish 00:14:44.670 --> 00:14:44.680 align:start position:0% retention well I'll let people finish 00:14:44.680 --> 00:14:48.030 align:start position:0% retention well I'll let people finish taking<00:14:45.079> their<00:14:45.320> pictures<00:14:46.320> um<00:14:46.759> U<00:14:46.959> please<00:14:47.720> share 00:14:48.030 --> 00:14:48.040 align:start position:0% taking their pictures um U please share 00:14:48.040 --> 00:14:51.949 align:start position:0% taking their pictures um U please share your<00:14:48.639> feedback<00:14:49.639> on<00:14:50.320> on<00:14:50.560> X<00:14:51.240> but<00:14:51.480> first<00:14:51.759> I<00:14:51.839> want 00:14:51.949 --> 00:14:51.959 align:start position:0% your feedback on on X but first I want 00:14:51.959 --> 00:14:54.829 align:start position:0% your feedback on on X but first I want to<00:14:52.079> leave<00:14:52.279> you<00:14:52.560> with<00:14:52.839> one<00:14:53.360> final<00:14:53.959> idea<00:14:54.680> what 00:14:54.829 --> 00:14:54.839 align:start position:0% to leave you with one final idea what 00:14:54.839 --> 00:14:57.269 align:start position:0% to leave you with one final idea what could<00:14:54.959> we<00:14:55.120> build<00:14:55.560> together<00:14:55.959> if<00:14:56.120> we're 00:14:57.269 --> 00:14:57.279 align:start position:0% could we build together if we're 00:14:57.279 --> 00:15:00.870 align:start position:0% could we build together if we're not<00:14:58.279> building<00:14:58.600> in<00:14:58.800> Sil 00:15:00.870 --> 00:15:00.880 align:start position:0% not building in Sil 00:15:00.880 --> 00:15:03.749 align:start position:0% not building in Sil I<00:15:01.040> propose<00:15:01.440> that<00:15:01.560> we<00:15:01.720> align<00:15:02.160> on<00:15:02.399> web<00:15:02.680> 3<00:15:03.199> design 00:15:03.749 --> 00:15:03.759 align:start position:0% I propose that we align on web 3 design 00:15:03.759 --> 00:15:06.430 align:start position:0% I propose that we align on web 3 design standards<00:15:04.759> imagine<00:15:05.160> a<00:15:05.399> world<00:15:05.920> where<00:15:06.160> every 00:15:06.430 --> 00:15:06.440 align:start position:0% standards imagine a world where every 00:15:06.440 --> 00:15:08.629 align:start position:0% standards imagine a world where every dap<00:15:06.800> developer<00:15:07.600> had<00:15:07.920> access<00:15:08.440> to 00:15:08.629 --> 00:15:08.639 align:start position:0% dap developer had access to 00:15:08.639 --> 00:15:10.670 align:start position:0% dap developer had access to plug-and-play<00:15:09.120> components<00:15:10.040> that<00:15:10.160> were<00:15:10.320> fully 00:15:10.670 --> 00:15:10.680 align:start position:0% plug-and-play components that were fully 00:15:10.680 --> 00:15:17.150 align:start position:0% plug-and-play components that were fully user<00:15:11.199> tested<00:15:12.199> responsive<00:15:13.160> open 00:15:17.150 --> 00:15:17.160 align:start position:0% 00:15:17.160 --> 00:15:19.670 align:start position:0% source<00:15:18.160> right<00:15:18.440> it<00:15:18.600> would<00:15:18.839> enable<00:15:19.320> greater 00:15:19.670 --> 00:15:19.680 align:start position:0% source right it would enable greater 00:15:19.680 --> 00:15:22.430 align:start position:0% source right it would enable greater efficiency<00:15:20.399> you<00:15:20.519> could<00:15:20.759> focus<00:15:21.360> on<00:15:21.560> your<00:15:21.880> core 00:15:22.430 --> 00:15:22.440 align:start position:0% efficiency you could focus on your core 00:15:22.440 --> 00:15:25.430 align:start position:0% efficiency you could focus on your core project<00:15:23.040> area<00:15:24.040> it's<00:15:24.199> a<00:15:24.399> proven<00:15:24.839> model<00:15:25.279> we've 00:15:25.430 --> 00:15:25.440 align:start position:0% project area it's a proven model we've 00:15:25.440 --> 00:15:28.509 align:start position:0% project area it's a proven model we've seen<00:15:25.839> this<00:15:26.120> with<00:15:26.360> Android<00:15:26.800> and<00:15:27.079> iOS<00:15:28.079> and<00:15:28.279> also 00:15:28.509 --> 00:15:28.519 align:start position:0% seen this with Android and iOS and also 00:15:28.519 --> 00:15:31.430 align:start position:0% seen this with Android and iOS and also the<00:15:28.680> very<00:15:29.160> popular<00:15:29.600> bootstrap 00:15:31.430 --> 00:15:31.440 align:start position:0% the very popular bootstrap 00:15:31.440 --> 00:15:34.430 align:start position:0% the very popular bootstrap framework<00:15:32.440> and<00:15:32.680> finally<00:15:33.160> it's<00:15:33.680> ecosystem 00:15:34.430 --> 00:15:34.440 align:start position:0% framework and finally it's ecosystem 00:15:34.440 --> 00:15:36.829 align:start position:0% framework and finally it's ecosystem strengthening<00:15:35.440> it<00:15:35.560> would<00:15:35.800> help<00:15:36.240> on<00:15:36.440> board<00:15:36.720> the 00:15:36.829 --> 00:15:36.839 align:start position:0% strengthening it would help on board the 00:15:36.839 --> 00:15:39.110 align:start position:0% strengthening it would help on board the next<00:15:37.160> billion<00:15:38.120> because<00:15:38.399> they<00:15:38.519> would<00:15:38.759> become 00:15:39.110 --> 00:15:39.120 align:start position:0% next billion because they would become 00:15:39.120 --> 00:15:41.110 align:start position:0% next billion because they would become familiar<00:15:39.560> with<00:15:39.720> the<00:15:39.880> patterns<00:15:40.319> across<00:15:40.839> every 00:15:41.110 --> 00:15:41.120 align:start position:0% familiar with the patterns across every 00:15:41.120 --> 00:15:47.550 align:start position:0% familiar with the patterns across every single<00:15:41.480> deck<00:15:41.959> rather<00:15:42.199> than<00:15:42.319> learning<00:15:42.839> bespoke 00:15:47.550 --> 00:15:47.560 align:start position:0% 00:15:47.560 --> 00:15:49.230 align:start position:0% implementation<00:15:48.560> there<00:15:48.680> are<00:15:48.800> a<00:15:48.920> number<00:15:49.120> of 00:15:49.230 --> 00:15:49.240 align:start position:0% implementation there are a number of 00:15:49.240 --> 00:15:52.269 align:start position:0% implementation there are a number of tools<00:15:49.680> that<00:15:49.880> exist<00:15:50.600> today<00:15:51.600> um<00:15:52.000> you<00:15:52.120> know 00:15:52.269 --> 00:15:52.279 align:start position:0% tools that exist today um you know 00:15:52.279 --> 00:15:53.590 align:start position:0% tools that exist today um you know they're<00:15:52.480> pros<00:15:52.720> and 00:15:53.590 --> 00:15:53.600 align:start position:0% they're pros and 00:15:53.600 --> 00:15:56.749 align:start position:0% they're pros and cons<00:15:54.600> of<00:15:54.880> the<00:15:55.000> wallet<00:15:55.360> Integrations<00:15:55.959> and<00:15:56.120> sdks 00:15:56.749 --> 00:15:56.759 align:start position:0% cons of the wallet Integrations and sdks 00:15:56.759 --> 00:15:58.509 align:start position:0% cons of the wallet Integrations and sdks out<00:15:57.040> there<00:15:57.519> you<00:15:57.639> know<00:15:57.839> some<00:15:58.000> of<00:15:58.120> them<00:15:58.279> are 00:15:58.509 --> 00:15:58.519 align:start position:0% out there you know some of them are 00:15:58.519 --> 00:16:01.629 align:start position:0% out there you know some of them are promoting<00:15:59.399> certain<00:15:59.800> wallets<00:16:00.199> or<00:16:00.480> chains<00:16:01.480> um 00:16:01.629 --> 00:16:01.639 align:start position:0% promoting certain wallets or chains um 00:16:01.639 --> 00:16:03.389 align:start position:0% promoting certain wallets or chains um but<00:16:01.759> I<00:16:01.880> think<00:16:02.040> we<00:16:02.199> need<00:16:02.639> a<00:16:02.839> neutral 00:16:03.389 --> 00:16:03.399 align:start position:0% but I think we need a neutral 00:16:03.399 --> 00:16:04.870 align:start position:0% but I think we need a neutral community-driven 00:16:04.870 --> 00:16:04.880 align:start position:0% community-driven 00:16:04.880 --> 00:16:08.670 align:start position:0% community-driven solution<00:16:05.880> so<00:16:06.800> I'm<00:16:07.000> looking<00:16:07.560> for<00:16:07.920> people<00:16:08.360> to 00:16:08.670 --> 00:16:08.680 align:start position:0% solution so I'm looking for people to 00:16:08.680 --> 00:16:10.670 align:start position:0% solution so I'm looking for people to build<00:16:08.959> this<00:16:09.319> together<00:16:09.639> with<00:16:09.800> me<00:16:10.199> front-end 00:16:10.670 --> 00:16:10.680 align:start position:0% build this together with me front-end 00:16:10.680 --> 00:16:13.590 align:start position:0% build this together with me front-end developers<00:16:11.319> designers<00:16:12.360> researchers<00:16:13.360> please 00:16:13.590 --> 00:16:13.600 align:start position:0% developers designers researchers please 00:16:13.600 --> 00:16:15.509 align:start position:0% developers designers researchers please reach<00:16:13.920> out<00:16:14.160> if<00:16:14.279> you'd<00:16:14.480> like<00:16:14.600> to<00:16:14.720> be<00:16:14.839> a<00:16:14.959> part<00:16:15.160> of 00:16:15.509 --> 00:16:15.519 align:start position:0% reach out if you'd like to be a part of 00:16:15.519 --> 00:16:21.990 align:start position:0% reach out if you'd like to be a part of this<00:16:16.519> thank<00:16:16.680> you<00:16:16.839> so<00:16:17.079> much 00:16:21.990 --> 00:16:22.000 align:start position:0% 00:16:22.000 --> 00:16:24.550 align:start position:0% kapuna<00:16:23.000> great 00:16:24.550 --> 00:16:24.560 align:start position:0% kapuna great 00:16:24.560 --> 00:16:28.269 align:start position:0% kapuna great talk<00:16:25.560> amazing<00:16:26.040> Rebecca<00:16:26.880> okay<00:16:27.120> let's<00:16:27.759> uh<00:16:28.040> ask 00:16:28.269 --> 00:16:28.279 align:start position:0% talk amazing Rebecca okay let's uh ask 00:16:28.279 --> 00:16:30.470 align:start position:0% talk amazing Rebecca okay let's uh ask some<00:16:28.480> questions<00:16:29.399> uh<00:16:29.560> if<00:16:29.680> you<00:16:29.920> guys<00:16:30.120> have<00:16:30.279> a 00:16:30.470 --> 00:16:30.480 align:start position:0% some questions uh if you guys have a 00:16:30.480 --> 00:16:32.550 align:start position:0% some questions uh if you guys have a question<00:16:31.319> uh<00:16:31.480> you<00:16:31.680> have<00:16:31.800> to<00:16:32.000> you<00:16:32.160> you<00:16:32.319> have<00:16:32.440> to 00:16:32.550 --> 00:16:32.560 align:start position:0% question uh you have to you you have to 00:16:32.560 --> 00:16:34.910 align:start position:0% question uh you have to you you have to use<00:16:32.759> the<00:16:32.959> code<00:16:33.680> to<00:16:33.839> post<00:16:34.079> it<00:16:34.199> on<00:16:34.360> the<00:16:34.519> app<00:16:34.720> and<00:16:34.839> I 00:16:34.910 --> 00:16:34.920 align:start position:0% use the code to post it on the app and I 00:16:34.920 --> 00:16:37.189 align:start position:0% use the code to post it on the app and I will<00:16:35.079> read<00:16:35.279> it<00:16:35.399> out<00:16:36.279> okay<00:16:36.480> let's<00:16:36.680> start<00:16:37.079> with 00:16:37.189 --> 00:16:37.199 align:start position:0% will read it out okay let's start with 00:16:37.199 --> 00:16:40.790 align:start position:0% will read it out okay let's start with the<00:16:37.839> most<00:16:38.600> voted<00:16:39.279> question<00:16:39.720> so<00:16:40.000> first<00:16:40.240> one<00:16:40.519> is 00:16:40.790 --> 00:16:40.800 align:start position:0% the most voted question so first one is 00:16:40.800 --> 00:16:43.069 align:start position:0% the most voted question so first one is about<00:16:41.079> using<00:16:41.399> tool<00:16:41.680> tips<00:16:41.920> on<00:16:42.120> mobile<00:16:42.800> what<00:16:42.920> is 00:16:43.069 --> 00:16:43.079 align:start position:0% about using tool tips on mobile what is 00:16:43.079 --> 00:16:44.949 align:start position:0% about using tool tips on mobile what is this<00:16:43.560> alternative<00:16:44.079> because<00:16:44.440> it's<00:16:44.600> hard<00:16:44.880> to 00:16:44.949 --> 00:16:44.959 align:start position:0% this alternative because it's hard to 00:16:44.959 --> 00:16:47.470 align:start position:0% this alternative because it's hard to use<00:16:45.120> to<00:16:45.360> tips<00:16:45.560> on<00:16:45.959> mobile<00:16:46.959> it's<00:16:47.120> a<00:16:47.240> good 00:16:47.470 --> 00:16:47.480 align:start position:0% use to tips on mobile it's a good 00:16:47.480 --> 00:16:50.150 align:start position:0% use to tips on mobile it's a good question<00:16:48.440> um<00:16:48.639> I've<00:16:48.759> seen<00:16:49.279> different<00:16:49.680> patterns 00:16:50.150 --> 00:16:50.160 align:start position:0% question um I've seen different patterns 00:16:50.160 --> 00:16:52.069 align:start position:0% question um I've seen different patterns Implement<00:16:50.680> like<00:16:50.800> a<00:16:50.959> mobile<00:16:51.399> version<00:16:51.959> which 00:16:52.069 --> 00:16:52.079 align:start position:0% Implement like a mobile version which 00:16:52.079 --> 00:16:55.710 align:start position:0% Implement like a mobile version which would<00:16:52.240> be<00:16:52.440> like<00:16:52.639> a 00:16:55.710 --> 00:16:55.720 align:start position:0% 00:16:55.720 --> 00:16:59.030 align:start position:0% modal<00:16:56.720> uh<00:16:57.519> or<00:16:57.759> like<00:16:57.880> a<00:16:58.040> bottom<00:16:58.319> sheet<00:16:58.600> I<00:16:58.720> guess 00:16:59.030 --> 00:16:59.040 align:start position:0% modal uh or like a bottom sheet I guess 00:16:59.040 --> 00:17:00.710 align:start position:0% modal uh or like a bottom sheet I guess if<00:16:59.160> it's<00:16:59.279> a<00:16:59.399> native 00:17:00.710 --> 00:17:00.720 align:start position:0% if it's a native 00:17:00.720 --> 00:17:04.470 align:start position:0% if it's a native app<00:17:01.720> okay<00:17:02.680> uh<00:17:03.000> do<00:17:03.120> you<00:17:03.240> think<00:17:03.440> wallet 00:17:04.470 --> 00:17:04.480 align:start position:0% app okay uh do you think wallet 00:17:04.480 --> 00:17:08.309 align:start position:0% app okay uh do you think wallet popups<00:17:05.559> so<00:17:06.559> are<00:17:07.280> this<00:17:07.400> is<00:17:07.600> fair<00:17:07.959> you<00:17:08.039> know 00:17:08.309 --> 00:17:08.319 align:start position:0% popups so are this is fair you know 00:17:08.319 --> 00:17:10.870 align:start position:0% popups so are this is fair you know actually<00:17:09.000> I<00:17:09.559> uh<00:17:09.679> what<00:17:09.799> was<00:17:09.959> the<00:17:10.160> stat<00:17:10.559> only 00:17:10.870 --> 00:17:10.880 align:start position:0% actually I uh what was the stat only 00:17:10.880 --> 00:17:13.029 align:start position:0% actually I uh what was the stat only like<00:17:11.039> 10%<00:17:11.720> of<00:17:11.839> the<00:17:11.959> most<00:17:12.240> popular<00:17:12.600> daps 00:17:13.029 --> 00:17:13.039 align:start position:0% like 10% of the most popular daps 00:17:13.039 --> 00:17:16.949 align:start position:0% like 10% of the most popular daps actually<00:17:13.400> do<00:17:13.799> have<00:17:14.880> uh<00:17:15.880> a<00:17:16.000> mobile<00:17:16.360> optimized 00:17:16.949 --> 00:17:16.959 align:start position:0% actually do have uh a mobile optimized 00:17:16.959 --> 00:17:18.549 align:start position:0% actually do have uh a mobile optimized experience<00:17:17.400> so<00:17:17.600> definitely<00:17:18.199> it's<00:17:18.319> an 00:17:18.549 --> 00:17:18.559 align:start position:0% experience so definitely it's an 00:17:18.559 --> 00:17:20.390 align:start position:0% experience so definitely it's an opportunity<00:17:19.160> for<00:17:19.360> us<00:17:19.559> to<00:17:19.760> build<00:17:20.079> more 00:17:20.390 --> 00:17:20.400 align:start position:0% opportunity for us to build more 00:17:20.400 --> 00:17:21.510 align:start position:0% opportunity for us to build more responsive 00:17:21.510 --> 00:17:21.520 align:start position:0% responsive 00:17:21.520 --> 00:17:23.669 align:start position:0% responsive libraries<00:17:22.520> um<00:17:22.880> I<00:17:23.000> think<00:17:23.280> you<00:17:23.400> know<00:17:23.520> they 00:17:23.669 --> 00:17:23.679 align:start position:0% libraries um I think you know they 00:17:23.679 --> 00:17:25.189 align:start position:0% libraries um I think you know they different<00:17:23.919> use<00:17:24.240> cases<00:17:24.640> right<00:17:24.760> there's<00:17:24.959> some 00:17:25.189 --> 00:17:25.199 align:start position:0% different use cases right there's some 00:17:25.199 --> 00:17:29.150 align:start position:0% different use cases right there's some serious<00:17:25.640> traders<00:17:26.079> who<00:17:26.240> prefer<00:17:27.120> desktop<00:17:28.120> um 00:17:29.150 --> 00:17:29.160 align:start position:0% serious traders who prefer desktop um 00:17:29.160 --> 00:17:32.190 align:start position:0% serious traders who prefer desktop um you<00:17:29.320> know<00:17:29.600> and<00:17:29.880> so<00:17:30.400> my<00:17:30.679> audits<00:17:31.160> were<00:17:31.720> desktop 00:17:32.190 --> 00:17:32.200 align:start position:0% you know and so my audits were desktop 00:17:32.200 --> 00:17:34.830 align:start position:0% you know and so my audits were desktop components<00:17:32.799> but<00:17:33.039> clearly<00:17:33.720> there's<00:17:34.720> uh 00:17:34.830 --> 00:17:34.840 align:start position:0% components but clearly there's uh 00:17:34.840 --> 00:17:36.510 align:start position:0% components but clearly there's uh definitely<00:17:35.160> a<00:17:35.240> lot<00:17:35.360> of<00:17:35.480> Need<00:17:35.760> For<00:17:35.960> Mobile<00:17:36.360> as 00:17:36.510 --> 00:17:36.520 align:start position:0% definitely a lot of Need For Mobile as 00:17:36.520 --> 00:17:40.549 align:start position:0% definitely a lot of Need For Mobile as well<00:17:36.880> so<00:17:37.240> sorry<00:17:37.559> this<00:17:38.440> the<00:17:39.440> wallet<00:17:39.880> popups<00:17:40.280> for 00:17:40.549 --> 00:17:40.559 align:start position:0% well so sorry this the wallet popups for 00:17:40.559 --> 00:17:42.830 align:start position:0% well so sorry this the wallet popups for approval<00:17:41.000> or<00:17:41.280> but<00:17:41.640> um<00:17:41.760> so<00:17:41.960> the<00:17:42.080> next<00:17:42.360> question 00:17:42.830 --> 00:17:42.840 align:start position:0% approval or but um so the next question 00:17:42.840 --> 00:17:44.710 align:start position:0% approval or but um so the next question is<00:17:43.320> don't<00:17:43.520> you<00:17:43.640> need<00:17:43.840> product<00:17:44.160> Market<00:17:44.480> fit 00:17:44.710 --> 00:17:44.720 align:start position:0% is don't you need product Market fit 00:17:44.720 --> 00:17:46.950 align:start position:0% is don't you need product Market fit before<00:17:45.080> you<00:17:45.200> can<00:17:45.480> consider 00:17:46.950 --> 00:17:46.960 align:start position:0% before you can consider 00:17:46.960 --> 00:17:51.390 align:start position:0% before you can consider uxix<00:17:47.960> oh<00:17:48.440> that<00:17:48.559> is<00:17:48.720> a<00:17:48.880> great<00:17:49.200> question<00:17:50.160> I<00:17:51.160> I 00:17:51.390 --> 00:17:51.400 align:start position:0% uxix oh that is a great question I I 00:17:51.400 --> 00:17:53.990 align:start position:0% uxix oh that is a great question I I definitely<00:17:52.400> uh<00:17:52.600> agree<00:17:53.000> on<00:17:53.200> that<00:17:53.400> and<00:17:53.600> there's 00:17:53.990 --> 00:17:54.000 align:start position:0% definitely uh agree on that and there's 00:17:54.000 --> 00:17:57.310 align:start position:0% definitely uh agree on that and there's there<00:17:54.480> there<00:17:54.600> was<00:17:54.720> a<00:17:54.919> really<00:17:55.200> great<00:17:55.640> talk<00:17:56.640> um 00:17:57.310 --> 00:17:57.320 align:start position:0% there there was a really great talk um 00:17:57.320 --> 00:17:59.870 align:start position:0% there there was a really great talk um yesterday<00:17:58.039> about<00:17:58.480> how<00:17:58.640> to<00:17:59.000> quickly<00:17:59.360> validate 00:17:59.870 --> 00:17:59.880 align:start position:0% yesterday about how to quickly validate 00:17:59.880 --> 00:18:02.190 align:start position:0% yesterday about how to quickly validate ideas<00:18:00.400> by<00:18:00.600> just<00:18:00.880> really<00:18:01.120> mocking<00:18:01.559> up<00:18:01.840> two 00:18:02.190 --> 00:18:02.200 align:start position:0% ideas by just really mocking up two 00:18:02.200 --> 00:18:06.230 align:start position:0% ideas by just really mocking up two parts<00:18:02.640> of<00:18:02.919> the<00:18:03.240> flow<00:18:04.240> the<00:18:05.039> point<00:18:05.240> of<00:18:05.679> Discovery 00:18:06.230 --> 00:18:06.240 align:start position:0% parts of the flow the point of Discovery 00:18:06.240 --> 00:18:09.270 align:start position:0% parts of the flow the point of Discovery and<00:18:06.360> then<00:18:06.520> the<00:18:06.640> point<00:18:06.880> of<00:18:07.360> value 00:18:09.270 --> 00:18:09.280 align:start position:0% and then the point of value 00:18:09.280 --> 00:18:11.990 align:start position:0% and then the point of value um<00:18:10.280> and<00:18:10.440> then<00:18:10.880> you<00:18:11.000> can<00:18:11.240> decide<00:18:11.679> whether<00:18:11.840> or 00:18:11.990 --> 00:18:12.000 align:start position:0% um and then you can decide whether or 00:18:12.000 --> 00:18:13.990 align:start position:0% um and then you can decide whether or not<00:18:12.159> to<00:18:12.360> build<00:18:12.720> the<00:18:12.840> middle<00:18:13.159> of<00:18:13.320> the<00:18:13.520> product 00:18:13.990 --> 00:18:14.000 align:start position:0% not to build the middle of the product 00:18:14.000 --> 00:18:15.549 align:start position:0% not to build the middle of the product experience<00:18:14.559> so<00:18:14.919> it<00:18:15.039> could<00:18:15.159> save<00:18:15.400> you 00:18:15.549 --> 00:18:15.559 align:start position:0% experience so it could save you 00:18:15.559 --> 00:18:17.830 align:start position:0% experience so it could save you potentially<00:18:16.000> a<00:18:16.120> lot<00:18:16.280> of 00:18:17.830 --> 00:18:17.840 align:start position:0% potentially a lot of 00:18:17.840 --> 00:18:20.470 align:start position:0% potentially a lot of effort<00:18:18.840> okay<00:18:19.360> the<00:18:19.480> next<00:18:19.760> question<00:18:20.039> is<00:18:20.240> should 00:18:20.470 --> 00:18:20.480 align:start position:0% effort okay the next question is should 00:18:20.480 --> 00:18:24.190 align:start position:0% effort okay the next question is should user<00:18:20.799> know<00:18:21.559> uh<00:18:21.760> they<00:18:21.840> are<00:18:22.000> using 00:18:24.190 --> 00:18:24.200 align:start position:0% user know uh they are using 00:18:24.200 --> 00:18:28.110 align:start position:0% user know uh they are using crypto<00:18:25.200> yeah<00:18:25.440> there<00:18:26.280> um<00:18:26.640> so<00:18:26.840> many<00:18:27.400> great 00:18:28.110 --> 00:18:28.120 align:start position:0% crypto yeah there um so many great 00:18:28.120 --> 00:18:31.190 align:start position:0% crypto yeah there um so many great topics<00:18:28.520> about<00:18:29.039> this<00:18:29.799> uh<00:18:30.000> or<00:18:30.320> talks<00:18:30.720> about<00:18:31.000> this 00:18:31.190 --> 00:18:31.200 align:start position:0% topics about this uh or talks about this 00:18:31.200 --> 00:18:33.669 align:start position:0% topics about this uh or talks about this at<00:18:31.400> this<00:18:31.600> conference<00:18:32.400> specifically<00:18:33.400> uh<00:18:33.559> I 00:18:33.669 --> 00:18:33.679 align:start position:0% at this conference specifically uh I 00:18:33.679 --> 00:18:36.230 align:start position:0% at this conference specifically uh I think<00:18:34.440> longer<00:18:34.799> term<00:18:35.120> as<00:18:35.280> we're<00:18:35.640> looking<00:18:36.000> at 00:18:36.230 --> 00:18:36.240 align:start position:0% think longer term as we're looking at 00:18:36.240 --> 00:18:38.350 align:start position:0% think longer term as we're looking at onboarding<00:18:36.799> the<00:18:36.919> next<00:18:37.159> billion<00:18:37.559> it's<00:18:38.080> not 00:18:38.350 --> 00:18:38.360 align:start position:0% onboarding the next billion it's not 00:18:38.360 --> 00:18:40.870 align:start position:0% onboarding the next billion it's not necessarily<00:18:38.960> what<00:18:39.080> I<00:18:39.159> shared<00:18:39.520> today<00:18:40.159> it's<00:18:40.760> it 00:18:40.870 --> 00:18:40.880 align:start position:0% necessarily what I shared today it's it 00:18:40.880 --> 00:18:42.830 align:start position:0% necessarily what I shared today it's it is<00:18:41.159> abstracting<00:18:41.840> it<00:18:42.000> and<00:18:42.159> making<00:18:42.400> it<00:18:42.559> so 00:18:42.830 --> 00:18:42.840 align:start position:0% is abstracting it and making it so 00:18:42.840 --> 00:18:45.230 align:start position:0% is abstracting it and making it so simple<00:18:43.400> probably<00:18:43.880> likely 00:18:45.230 --> 00:18:45.240 align:start position:0% simple probably likely 00:18:45.240 --> 00:18:49.430 align:start position:0% simple probably likely behind<00:18:46.240> um<00:18:46.559> you<00:18:46.679> know<00:18:46.840> a<00:18:47.000> very<00:18:47.480> simple 00:18:49.430 --> 00:18:49.440 align:start position:0% behind um you know a very simple 00:18:49.440 --> 00:18:52.350 align:start position:0% behind um you know a very simple interface<00:18:50.440> okay<00:18:51.120> um<00:18:51.440> next<00:18:51.720> question<00:18:51.960> is<00:18:52.120> about 00:18:52.350 --> 00:18:52.360 align:start position:0% interface okay um next question is about 00:18:52.360 --> 00:18:54.549 align:start position:0% interface okay um next question is about using<00:18:52.799> tables<00:18:53.360> on<00:18:53.559> mobile<00:18:54.080> how<00:18:54.240> do<00:18:54.360> you 00:18:54.549 --> 00:18:54.559 align:start position:0% using tables on mobile how do you 00:18:54.559 --> 00:18:56.230 align:start position:0% using tables on mobile how do you approach 00:18:56.230 --> 00:18:56.240 align:start position:0% approach 00:18:56.240 --> 00:19:00.669 align:start position:0% approach that<00:18:57.240> there<00:18:57.400> are<00:18:58.840> various<00:18:59.240> options<00:18:59.720> I 00:19:00.669 --> 00:19:00.679 align:start position:0% that there are various options I 00:19:00.679 --> 00:19:03.909 align:start position:0% that there are various options I guess<00:19:01.679> uh<00:19:02.360> you<00:19:02.480> could<00:19:02.679> either<00:19:02.960> stack<00:19:03.720> I<00:19:03.760> don't 00:19:03.909 --> 00:19:03.919 align:start position:0% guess uh you could either stack I don't 00:19:03.919 --> 00:19:07.070 align:start position:0% guess uh you could either stack I don't know<00:19:04.760> there<00:19:05.760> I'm<00:19:05.880> not<00:19:06.039> sure<00:19:06.240> if<00:19:06.400> I'm<00:19:06.600> the<00:19:06.880> best 00:19:07.070 --> 00:19:07.080 align:start position:0% know there I'm not sure if I'm the best 00:19:07.080 --> 00:19:09.710 align:start position:0% know there I'm not sure if I'm the best person<00:19:07.360> to<00:19:07.559> share<00:19:07.880> this<00:19:08.120> right<00:19:08.280> now<00:19:08.600> but<00:19:08.960> yeah 00:19:09.710 --> 00:19:09.720 align:start position:0% person to share this right now but yeah 00:19:09.720 --> 00:19:11.029 align:start position:0% person to share this right now but yeah they're<00:19:10.000> they're<00:19:10.200> different<00:19:10.480> patterns<00:19:10.880> that 00:19:11.029 --> 00:19:11.039 align:start position:0% they're they're different patterns that 00:19:11.039 --> 00:19:15.549 align:start position:0% they're they're different patterns that you<00:19:11.120> could<00:19:11.400> look<00:19:12.000> up<00:19:13.000> okay<00:19:14.000> uh<00:19:14.280> when<00:19:14.440> you<00:19:14.600> think 00:19:15.549 --> 00:19:15.559 align:start position:0% you could look up okay uh when you think 00:19:15.559 --> 00:19:17.430 align:start position:0% you could look up okay uh when you think uh<00:19:15.720> when<00:19:15.880> do<00:19:15.960> you<00:19:16.080> think<00:19:16.280> chain<00:19:16.559> obstruction 00:19:17.430 --> 00:19:17.440 align:start position:0% uh when do you think chain obstruction 00:19:17.440 --> 00:19:19.190 align:start position:0% uh when do you think chain obstruction will<00:19:17.640> be<00:19:17.840> the<00:19:18.000> new<00:19:18.200> normal<00:19:18.520> in 00:19:19.190 --> 00:19:19.200 align:start position:0% will be the new normal in 00:19:19.200 --> 00:19:21.750 align:start position:0% will be the new normal in D 00:19:21.750 --> 00:19:21.760 align:start position:0% D 00:19:21.760 --> 00:19:26.270 align:start position:0% D chain<00:19:22.760> I<00:19:22.919> wonder<00:19:23.320> if<00:19:23.480> it's<00:19:23.679> a<00:19:23.960> h<00:19:24.320> what's<00:19:24.520> the 00:19:26.270 --> 00:19:26.280 align:start position:0% chain I wonder if it's a h what's the 00:19:26.280 --> 00:19:29.590 align:start position:0% chain I wonder if it's a h what's the hindrance<00:19:27.280> I'm<00:19:28.080> not<00:19:28.480> quite<00:19:28.760> quite<00:19:28.919> sure<00:19:29.200> about 00:19:29.590 --> 00:19:29.600 align:start position:0% hindrance I'm not quite quite sure about 00:19:29.600 --> 00:19:31.350 align:start position:0% hindrance I'm not quite quite sure about that<00:19:30.120> I<00:19:30.320> guess<00:19:30.480> is 00:19:31.350 --> 00:19:31.360 align:start position:0% that I guess is 00:19:31.360 --> 00:19:34.710 align:start position:0% that I guess is this<00:19:32.360> who<00:19:32.600> wrote<00:19:33.320> just<00:19:33.559> want<00:19:33.679> to<00:19:33.880> somebody 00:19:34.710 --> 00:19:34.720 align:start position:0% this who wrote just want to somebody 00:19:34.720 --> 00:19:37.270 align:start position:0% this who wrote just want to somebody what<00:19:34.840> is<00:19:35.120> hindrance<00:19:36.120> oh<00:19:36.360> yeah<00:19:36.559> like<00:19:37.039> what<00:19:37.159> is 00:19:37.270 --> 00:19:37.280 align:start position:0% what is hindrance oh yeah like what is 00:19:37.280 --> 00:19:39.789 align:start position:0% what is hindrance oh yeah like what is the<00:19:37.440> hindrance 00:19:39.789 --> 00:19:39.799 align:start position:0% the hindrance 00:19:39.799 --> 00:19:42.549 align:start position:0% the hindrance of<00:19:40.799> what<00:19:40.919> is<00:19:41.080> preventing<00:19:41.520> people<00:19:41.799> from 00:19:42.549 --> 00:19:42.559 align:start position:0% of what is preventing people from 00:19:42.559 --> 00:19:43.990 align:start position:0% of what is preventing people from distracting<00:19:43.159> is<00:19:43.280> somebody<00:19:43.480> who<00:19:43.600> asked<00:19:43.840> this 00:19:43.990 --> 00:19:44.000 align:start position:0% distracting is somebody who asked this 00:19:44.000 --> 00:19:55.510 align:start position:0% distracting is somebody who asked this question<00:19:44.320> here 00:19:55.510 --> 00:19:55.520 align:start position:0% 00:19:55.520 --> 00:19:57.909 align:start position:0% maybe<00:19:56.520> oh<00:19:56.760> okay<00:19:56.919> so<00:19:57.120> this<00:19:57.240> is<00:19:57.480> kind<00:19:57.600> of<00:19:57.760> like 00:19:57.909 --> 00:19:57.919 align:start position:0% maybe oh okay so this is kind of like 00:19:57.919 --> 00:20:00.110 align:start position:0% maybe oh okay so this is kind of like the<00:19:58.039> other<00:19:58.280> question<00:19:58.799> around<00:19:59.039> it 00:20:00.110 --> 00:20:00.120 align:start position:0% the other question around it 00:20:00.120 --> 00:20:03.029 align:start position:0% the other question around it being<00:20:01.120> like<00:20:01.280> all<00:20:01.440> of<00:20:01.640> the<00:20:02.200> uh<00:20:02.400> complexity 00:20:03.029 --> 00:20:03.039 align:start position:0% being like all of the uh complexity 00:20:03.039 --> 00:20:11.710 align:start position:0% being like all of the uh complexity being<00:20:04.159> hidden 00:20:11.710 --> 00:20:11.720 align:start position:0% 00:20:11.720 --> 00:20:14.590 align:start position:0% okay<00:20:12.720> yeah<00:20:13.200> I'm<00:20:13.400> with<00:20:13.600> you<00:20:13.960> I<00:20:14.080> think<00:20:14.320> it 00:20:14.590 --> 00:20:14.600 align:start position:0% okay yeah I'm with you I think it 00:20:14.600 --> 00:20:17.190 align:start position:0% okay yeah I'm with you I think it there's<00:20:15.600> that<00:20:15.760> is<00:20:15.960> the<00:20:16.120> future<00:20:16.760> and<00:20:17.000> I<00:20:17.080> think 00:20:17.190 --> 00:20:17.200 align:start position:0% there's that is the future and I think 00:20:17.200 --> 00:20:19.830 align:start position:0% there's that is the future and I think we'll<00:20:17.400> see<00:20:17.600> a<00:20:17.720> lot<00:20:17.880> of<00:20:18.600> advancements<00:20:19.559> when 00:20:19.830 --> 00:20:19.840 align:start position:0% we'll see a lot of advancements when 00:20:19.840 --> 00:20:23.710 align:start position:0% we'll see a lot of advancements when Petra<00:20:20.240> is<00:20:20.360> upgraded<00:20:21.360> in<00:20:21.600> q1<00:20:22.320> so<00:20:23.320> let's<00:20:23.520> stay 00:20:23.710 --> 00:20:23.720 align:start position:0% Petra is upgraded in q1 so let's stay 00:20:23.720 --> 00:20:25.350 align:start position:0% Petra is upgraded in q1 so let's stay tuned<00:20:24.159> I<00:20:24.240> think<00:20:24.360> what<00:20:24.480> I<00:20:24.559> shared<00:20:24.840> today<00:20:25.159> was 00:20:25.350 --> 00:20:25.360 align:start position:0% tuned I think what I shared today was 00:20:25.360 --> 00:20:27.390 align:start position:0% tuned I think what I shared today was focused<00:20:25.760> on<00:20:26.400> the<00:20:26.600> technology<00:20:27.159> that's 00:20:27.390 --> 00:20:27.400 align:start position:0% focused on the technology that's 00:20:27.400 --> 00:20:29.549 align:start position:0% focused on the technology that's available<00:20:27.960> right<00:20:28.120> now<00:20:28.440> what<00:20:28.760> can<00:20:28.880> build<00:20:29.120> today 00:20:29.549 --> 00:20:29.559 align:start position:0% available right now what can build today 00:20:29.559 --> 00:20:31.830 align:start position:0% available right now what can build today but<00:20:29.760> that's<00:20:30.039> definitely<00:20:30.919> soon<00:20:31.520> and<00:20:31.640> then 00:20:31.830 --> 00:20:31.840 align:start position:0% but that's definitely soon and then 00:20:31.840 --> 00:20:34.190 align:start position:0% but that's definitely soon and then later<00:20:32.559> I<00:20:32.640> think<00:20:32.840> is<00:20:33.039> the<00:20:33.240> standards<00:20:33.760> where<00:20:34.000> we 00:20:34.190 --> 00:20:34.200 align:start position:0% later I think is the standards where we 00:20:34.200 --> 00:20:36.950 align:start position:0% later I think is the standards where we kind<00:20:34.320> of<00:20:34.640> as<00:20:34.760> a<00:20:34.919> community<00:20:35.440> agree<00:20:35.760> on<00:20:36.400> the<00:20:36.640> best 00:20:36.950 --> 00:20:36.960 align:start position:0% kind of as a community agree on the best 00:20:36.960 --> 00:20:39.950 align:start position:0% kind of as a community agree on the best practices<00:20:37.640> and<00:20:37.960> how<00:20:38.080> to<00:20:38.280> implement<00:20:39.000> common 00:20:39.950 --> 00:20:39.960 align:start position:0% practices and how to implement common 00:20:39.960 --> 00:20:43.870 align:start position:0% practices and how to implement common patterns<00:20:40.960> okay<00:20:41.799> uh<00:20:42.240> next<00:20:42.559> question<00:20:43.000> is<00:20:43.600> should 00:20:43.870 --> 00:20:43.880 align:start position:0% patterns okay uh next question is should 00:20:43.880 --> 00:20:48.270 align:start position:0% patterns okay uh next question is should we<00:20:44.159> be<00:20:44.360> moving<00:20:44.799> towards<00:20:45.720> um<00:20:46.520> embedded<00:20:47.520> wallets 00:20:48.270 --> 00:20:48.280 align:start position:0% we be moving towards um embedded wallets 00:20:48.280 --> 00:20:50.510 align:start position:0% we be moving towards um embedded wallets uh<00:20:48.360> inside<00:20:48.799> apps<00:20:49.080> that<00:20:49.200> are<00:20:49.360> less<00:20:49.600> portable<00:20:50.240> or 00:20:50.510 --> 00:20:50.520 align:start position:0% uh inside apps that are less portable or 00:20:50.520 --> 00:20:53.230 align:start position:0% uh inside apps that are less portable or continue<00:20:50.919> to<00:20:51.080> push<00:20:51.280> in<00:20:51.919> portable<00:20:52.400> horizontal 00:20:53.230 --> 00:20:53.240 align:start position:0% continue to push in portable horizontal 00:20:53.240 --> 00:20:55.470 align:start position:0% continue to push in portable horizontal wallets<00:20:54.240> uh<00:20:54.360> which<00:20:54.480> are<00:20:54.679> not<00:20:54.840> perfectly 00:20:55.470 --> 00:20:55.480 align:start position:0% wallets uh which are not perfectly 00:20:55.480 --> 00:20:58.990 align:start position:0% wallets uh which are not perfectly suited<00:20:55.799> for<00:20:55.960> each<00:20:56.600> app<00:20:57.600> which<00:20:57.679> are<00:20:57.840> not<00:20:58.080> what 00:20:58.990 --> 00:20:59.000 align:start position:0% suited for each app which are not what 00:20:59.000 --> 00:21:02.270 align:start position:0% suited for each app which are not what perfectly<00:20:59.360> suitable<00:20:59.799> for<00:21:00.039> each<00:21:00.320> app<00:21:01.280> yeah 00:21:02.270 --> 00:21:02.280 align:start position:0% perfectly suitable for each app yeah 00:21:02.280 --> 00:21:05.549 align:start position:0% perfectly suitable for each app yeah like<00:21:02.520> metamask<00:21:03.600> versus<00:21:04.600> um<00:21:04.919> you<00:21:05.039> know<00:21:05.440> the 00:21:05.549 --> 00:21:05.559 align:start position:0% like metamask versus um you know the 00:21:05.559 --> 00:21:07.190 align:start position:0% like metamask versus um you know the wallets<00:21:05.960> that<00:21:06.080> you<00:21:06.280> get<00:21:06.559> inside<00:21:06.840> of<00:21:06.919> your 00:21:07.190 --> 00:21:07.200 align:start position:0% wallets that you get inside of your 00:21:07.200 --> 00:21:11.029 align:start position:0% wallets that you get inside of your application<00:21:08.200> yeah<00:21:08.919> I<00:21:09.919> I<00:21:10.080> watched<00:21:10.600> one<00:21:10.760> of<00:21:10.880> the 00:21:11.029 --> 00:21:11.039 align:start position:0% application yeah I I watched one of the 00:21:11.039 --> 00:21:13.149 align:start position:0% application yeah I I watched one of the talks<00:21:11.400> about<00:21:11.720> this<00:21:11.960> and<00:21:12.159> I<00:21:12.279> guess<00:21:12.640> like<00:21:12.960> right 00:21:13.149 --> 00:21:13.159 align:start position:0% talks about this and I guess like right 00:21:13.159 --> 00:21:15.310 align:start position:0% talks about this and I guess like right now<00:21:13.440> it<00:21:13.600> seems 00:21:15.310 --> 00:21:15.320 align:start position:0% now it seems 00:21:15.320 --> 00:21:18.630 align:start position:0% now it seems like<00:21:16.320> there<00:21:16.880> you<00:21:17.000> know<00:21:17.520> wall<00:21:17.840> some<00:21:18.120> wallets 00:21:18.630 --> 00:21:18.640 align:start position:0% like there you know wall some wallets 00:21:18.640 --> 00:21:21.230 align:start position:0% like there you know wall some wallets like<00:21:18.840> privy<00:21:19.240> and<00:21:19.360> others<00:21:19.679> that<00:21:19.840> will<00:21:20.159> create 00:21:21.230 --> 00:21:21.240 align:start position:0% like privy and others that will create 00:21:21.240 --> 00:21:25.390 align:start position:0% like privy and others that will create per<00:21:22.240> uh<00:21:22.799> dep<00:21:23.360> but<00:21:24.120> the<00:21:24.320> vision<00:21:24.679> I<00:21:24.760> think<00:21:24.960> is<00:21:25.120> to 00:21:25.390 --> 00:21:25.400 align:start position:0% per uh dep but the vision I think is to 00:21:25.400 --> 00:21:29.310 align:start position:0% per uh dep but the vision I think is to consolidate<00:21:26.039> across 00:21:29.310 --> 00:21:29.320 align:start position:0% 00:21:29.320 --> 00:21:31.909 align:start position:0% okay<00:21:29.720> the<00:21:29.880> focus<00:21:30.159> of<00:21:30.320> this<00:21:30.520> was<00:21:30.720> dap<00:21:31.080> ux<00:21:31.640> not 00:21:31.909 --> 00:21:31.919 align:start position:0% okay the focus of this was dap ux not 00:21:31.919 --> 00:21:34.789 align:start position:0% okay the focus of this was dap ux not wallet<00:21:32.440> so<00:21:33.120> okay<00:21:33.440> I<00:21:33.520> think<00:21:33.760> that's<00:21:34.200> uh<00:21:34.400> it<00:21:34.559> for 00:21:34.789 --> 00:21:34.799 align:start position:0% wallet so okay I think that's uh it for 00:21:34.799 --> 00:21:37.470 align:start position:0% wallet so okay I think that's uh it for the<00:21:35.000> time<00:21:35.360> for<00:21:35.600> the<00:21:35.760> Q&A<00:21:36.760> uh<00:21:37.000> thank<00:21:37.159> you<00:21:37.320> very 00:21:37.470 --> 00:21:37.480 align:start position:0% the time for the Q&A uh thank you very 00:21:37.480 --> 00:21:39.230 align:start position:0% the time for the Q&A uh thank you very much<00:21:37.679> Rebecca<00:21:38.559> thank<00:21:38.720> you<00:21:38.840> everybody<00:21:39.120> who 00:21:39.230 --> 00:21:39.240 align:start position:0% much Rebecca thank you everybody who 00:21:39.240 --> 00:21:42.149 align:start position:0% much Rebecca thank you everybody who asked<00:21:39.559> questions<00:21:40.080> and<00:21:40.520> uh<00:21:40.720> next<00:21:41.320> uh<00:21:41.640> talk<00:21:41.960> is 00:21:42.149 --> 00:21:42.159 align:start position:0% asked questions and uh next uh talk is 00:21:42.159 --> 00:21:46.919 align:start position:0% asked questions and uh next uh talk is in<00:21:42.360> five<00:21:42.520> minutes<00:21:42.960> see<00:21:43.159> you<00:21:43.919> okay