WEBVTT Kind: captions Language: en 00:00:00.260 --> 00:00:01.119 align:start position:0% [Applause] 00:00:01.119 --> 00:00:01.129 align:start position:0% [Applause] 00:00:01.129 --> 00:00:05.420 align:start position:0% [Applause] everyone<00:00:02.990> thank<00:00:03.990> you<00:00:04.049> so<00:00:04.110> much<00:00:04.410> for<00:00:04.589> coming<00:00:04.890> my 00:00:05.420 --> 00:00:05.430 align:start position:0% everyone thank you so much for coming my 00:00:05.430 --> 00:00:07.309 align:start position:0% everyone thank you so much for coming my name<00:00:05.609> is<00:00:05.759> Bobby<00:00:06.029> from<00:00:06.509> the<00:00:06.690> meta<00:00:06.839> mask<00:00:07.020> team 00:00:07.309 --> 00:00:07.319 align:start position:0% name is Bobby from the meta mask team 00:00:07.319 --> 00:00:09.470 align:start position:0% name is Bobby from the meta mask team got<00:00:08.040> Jenny<00:00:08.280> and<00:00:08.519> Bruno<00:00:08.760> backstage<00:00:09.150> with<00:00:09.330> me 00:00:09.470 --> 00:00:09.480 align:start position:0% got Jenny and Bruno backstage with me 00:00:09.480 --> 00:00:12.560 align:start position:0% got Jenny and Bruno backstage with me and<00:00:09.719> we<00:00:09.840> are<00:00:09.870> very<00:00:10.290> excited<00:00:10.769> to<00:00:10.800> be<00:00:10.889> here<00:00:11.010> today 00:00:12.560 --> 00:00:12.570 align:start position:0% and we are very excited to be here today 00:00:12.570 --> 00:00:14.150 align:start position:0% and we are very excited to be here today in<00:00:12.750> the<00:00:12.870> next<00:00:13.080> 25<00:00:13.380> minutes<00:00:13.590> we're<00:00:13.799> gonna<00:00:13.889> tell 00:00:14.150 --> 00:00:14.160 align:start position:0% in the next 25 minutes we're gonna tell 00:00:14.160 --> 00:00:15.680 align:start position:0% in the next 25 minutes we're gonna tell you<00:00:14.190> a<00:00:14.309> little<00:00:14.670> bit<00:00:14.759> about<00:00:14.969> what<00:00:15.450> we've<00:00:15.570> been 00:00:15.680 --> 00:00:15.690 align:start position:0% you a little bit about what we've been 00:00:15.690 --> 00:00:17.870 align:start position:0% you a little bit about what we've been working<00:00:15.839> on<00:00:16.080> for<00:00:16.289> the<00:00:16.410> past<00:00:16.470> year<00:00:16.740> some<00:00:17.640> of<00:00:17.670> the 00:00:17.870 --> 00:00:17.880 align:start position:0% working on for the past year some of the 00:00:17.880 --> 00:00:19.519 align:start position:0% working on for the past year some of the principles<00:00:18.359> that<00:00:18.449> guide<00:00:18.720> our<00:00:18.750> development 00:00:19.519 --> 00:00:19.529 align:start position:0% principles that guide our development 00:00:19.529 --> 00:00:21.650 align:start position:0% principles that guide our development and<00:00:19.680> what<00:00:20.250> you<00:00:20.340> can<00:00:20.490> expect<00:00:20.789> to<00:00:20.910> see<00:00:21.210> over<00:00:21.539> the 00:00:21.650 --> 00:00:21.660 align:start position:0% and what you can expect to see over the 00:00:21.660 --> 00:00:24.349 align:start position:0% and what you can expect to see over the course<00:00:21.779> of<00:00:22.050> the<00:00:22.109> next<00:00:22.199> year<00:00:22.789> no<00:00:23.789> dinosaur<00:00:24.269> is 00:00:24.349 --> 00:00:24.359 align:start position:0% course of the next year no dinosaur is 00:00:24.359 --> 00:00:26.179 align:start position:0% course of the next year no dinosaur is nothing<00:00:24.630> fancy<00:00:24.810> just<00:00:25.050> a<00:00:25.619> couple<00:00:25.859> projects 00:00:26.179 --> 00:00:26.189 align:start position:0% nothing fancy just a couple projects 00:00:26.189 --> 00:00:28.099 align:start position:0% nothing fancy just a couple projects that<00:00:26.279> were<00:00:26.369> very<00:00:26.460> excited<00:00:26.939> about<00:00:27.000> so<00:00:27.960> let's 00:00:28.099 --> 00:00:28.109 align:start position:0% that were very excited about so let's 00:00:28.109 --> 00:00:30.470 align:start position:0% that were very excited about so let's start<00:00:28.289> with<00:00:28.349> some<00:00:28.500> numbers<00:00:29.330> since<00:00:30.330> our 00:00:30.470 --> 00:00:30.480 align:start position:0% start with some numbers since our 00:00:30.480 --> 00:00:33.620 align:start position:0% start with some numbers since our teammates<00:00:30.929> last<00:00:31.439> took<00:00:31.769> this<00:00:31.949> stage<00:00:32.250> in<00:00:32.850> Cancun 00:00:33.620 --> 00:00:33.630 align:start position:0% teammates last took this stage in Cancun 00:00:33.630 --> 00:00:36.470 align:start position:0% teammates last took this stage in Cancun we've<00:00:34.350> shipped<00:00:34.649> 46<00:00:35.460> versions<00:00:35.940> of<00:00:36.090> meta<00:00:36.239> masks 00:00:36.470 --> 00:00:36.480 align:start position:0% we've shipped 46 versions of meta masks 00:00:36.480 --> 00:00:39.590 align:start position:0% we've shipped 46 versions of meta masks made<00:00:37.320> up<00:00:37.440> of<00:00:37.530> almost<00:00:37.800> 900<00:00:38.430> pull<00:00:38.610> requests<00:00:39.120> from 00:00:39.590 --> 00:00:39.600 align:start position:0% made up of almost 900 pull requests from 00:00:39.600 --> 00:00:41.780 align:start position:0% made up of almost 900 pull requests from over<00:00:39.930> a<00:00:39.960> hundred<00:00:40.100> individual<00:00:41.100> contributors 00:00:41.780 --> 00:00:41.790 align:start position:0% over a hundred individual contributors 00:00:41.790 --> 00:00:43.970 align:start position:0% over a hundred individual contributors now<00:00:42.600> that<00:00:42.750> last<00:00:42.960> number<00:00:43.200> is<00:00:43.440> really<00:00:43.800> really 00:00:43.970 --> 00:00:43.980 align:start position:0% now that last number is really really 00:00:43.980 --> 00:00:45.889 align:start position:0% now that last number is really really exciting<00:00:44.430> for<00:00:44.550> us<00:00:44.610> we<00:00:45.059> are<00:00:45.180> thankful<00:00:45.539> every 00:00:45.889 --> 00:00:45.899 align:start position:0% exciting for us we are thankful every 00:00:45.899 --> 00:00:49.369 align:start position:0% exciting for us we are thankful every day<00:00:45.930> for<00:00:46.469> the<00:00:47.039> support<00:00:47.600> enthusiasm<00:00:48.600> feedback 00:00:49.369 --> 00:00:49.379 align:start position:0% day for the support enthusiasm feedback 00:00:49.379 --> 00:00:52.010 align:start position:0% day for the support enthusiasm feedback and<00:00:49.730> patience<00:00:50.730> of<00:00:50.910> this<00:00:51.180> community<00:00:51.570> so 00:00:52.010 --> 00:00:52.020 align:start position:0% and patience of this community so 00:00:52.020 --> 00:00:55.639 align:start position:0% and patience of this community so seriously<00:00:52.350> thank<00:00:52.649> you<00:00:54.050> yeah<00:00:55.050> you<00:00:55.289> can<00:00:55.320> applaud 00:00:55.639 --> 00:00:55.649 align:start position:0% seriously thank you yeah you can applaud 00:00:55.649 --> 00:00:57.790 align:start position:0% seriously thank you yeah you can applaud for<00:00:55.710> yourselves<00:00:56.129> that's<00:00:56.309> cool<00:00:56.579> with<00:00:56.670> me<00:00:56.730> cool 00:00:57.790 --> 00:00:57.800 align:start position:0% for yourselves that's cool with me cool 00:00:57.800 --> 00:01:00.110 align:start position:0% for yourselves that's cool with me cool the<00:00:58.800> team<00:00:59.039> has<00:00:59.250> almost<00:00:59.460> doubled<00:00:59.760> in<00:01:00.090> size 00:01:00.110 --> 00:01:00.120 align:start position:0% the team has almost doubled in size 00:01:00.120 --> 00:01:03.880 align:start position:0% the team has almost doubled in size we've<00:01:00.809> gone<00:01:00.960> from<00:01:01.170> 10<00:01:01.590> full-time<00:01:02.039> Fox's<00:01:02.699> to<00:01:02.940> 18 00:01:03.880 --> 00:01:03.890 align:start position:0% we've gone from 10 full-time Fox's to 18 00:01:03.890 --> 00:01:06.950 align:start position:0% we've gone from 10 full-time Fox's to 18 we've<00:01:04.890> made<00:01:05.129> room<00:01:05.339> for<00:01:05.640> a<00:01:05.939> support<00:01:06.420> team<00:01:06.659> to 00:01:06.950 --> 00:01:06.960 align:start position:0% we've made room for a support team to 00:01:06.960 --> 00:01:09.080 align:start position:0% we've made room for a support team to handle<00:01:07.260> this<00:01:07.380> huge<00:01:07.650> influx<00:01:07.890> of<00:01:08.280> user<00:01:08.460> requests 00:01:09.080 --> 00:01:09.090 align:start position:0% handle this huge influx of user requests 00:01:09.090 --> 00:01:11.240 align:start position:0% handle this huge influx of user requests and<00:01:09.299> we<00:01:09.750> now<00:01:09.869> contain<00:01:10.320> a<00:01:10.530> small<00:01:10.860> research 00:01:11.240 --> 00:01:11.250 align:start position:0% and we now contain a small research 00:01:11.250 --> 00:01:13.160 align:start position:0% and we now contain a small research development<00:01:11.880> team<00:01:12.030> called<00:01:12.330> meta<00:01:12.600> mask<00:01:12.780> labs 00:01:13.160 --> 00:01:13.170 align:start position:0% development team called meta mask labs 00:01:13.170 --> 00:01:15.200 align:start position:0% development team called meta mask labs which<00:01:13.770> Jenny<00:01:14.430> will<00:01:14.580> talk<00:01:14.700> about<00:01:14.909> in<00:01:15.000> just<00:01:15.090> a 00:01:15.200 --> 00:01:15.210 align:start position:0% which Jenny will talk about in just a 00:01:15.210 --> 00:01:18.649 align:start position:0% which Jenny will talk about in just a moment<00:01:15.530> we<00:01:16.530> span<00:01:16.830> 10<00:01:17.220> time<00:01:17.640> zones<00:01:18.000> and<00:01:18.540> I'm 00:01:18.649 --> 00:01:18.659 align:start position:0% moment we span 10 time zones and I'm 00:01:18.659 --> 00:01:19.910 align:start position:0% moment we span 10 time zones and I'm sure<00:01:18.810> some<00:01:19.020> of<00:01:19.110> you<00:01:19.200> are<00:01:19.229> familiar<00:01:19.439> with<00:01:19.799> the 00:01:19.910 --> 00:01:19.920 align:start position:0% sure some of you are familiar with the 00:01:19.920 --> 00:01:22.219 align:start position:0% sure some of you are familiar with the pros<00:01:20.130> and<00:01:20.400> the<00:01:20.460> cons<00:01:20.520> of<00:01:21.000> that<00:01:21.150> we<00:01:21.930> think<00:01:22.110> it's 00:01:22.219 --> 00:01:22.229 align:start position:0% pros and the cons of that we think it's 00:01:22.229 --> 00:01:23.899 align:start position:0% pros and the cons of that we think it's a<00:01:22.380> very<00:01:22.560> important<00:01:23.130> ingredient<00:01:23.369> one 00:01:23.899 --> 00:01:23.909 align:start position:0% a very important ingredient one 00:01:23.909 --> 00:01:25.730 align:start position:0% a very important ingredient one important<00:01:24.450> ingredient<00:01:24.600> and<00:01:25.080> building<00:01:25.680> a 00:01:25.730 --> 00:01:25.740 align:start position:0% important ingredient and building a 00:01:25.740 --> 00:01:27.260 align:start position:0% important ingredient and building a product<00:01:26.100> that<00:01:26.310> works<00:01:26.430> for<00:01:26.759> a<00:01:26.790> variety<00:01:26.970> of 00:01:27.260 --> 00:01:27.270 align:start position:0% product that works for a variety of 00:01:27.270 --> 00:01:32.420 align:start position:0% product that works for a variety of people<00:01:30.079> so<00:01:31.079> let's<00:01:31.860> talk<00:01:31.979> about<00:01:32.040> what<00:01:32.310> we've 00:01:32.420 --> 00:01:32.430 align:start position:0% people so let's talk about what we've 00:01:32.430 --> 00:01:36.020 align:start position:0% people so let's talk about what we've built<00:01:33.680> meta<00:01:34.680> mask<00:01:34.890> aims<00:01:35.250> to<00:01:35.640> make<00:01:35.790> the 00:01:36.020 --> 00:01:36.030 align:start position:0% built meta mask aims to make the 00:01:36.030 --> 00:01:39.830 align:start position:0% built meta mask aims to make the decentralized<00:01:36.630> web<00:01:36.930> usable<00:01:37.710> and<00:01:38.060> a<00:01:39.060> huge<00:01:39.600> part 00:01:39.830 --> 00:01:39.840 align:start position:0% decentralized web usable and a huge part 00:01:39.840 --> 00:01:41.330 align:start position:0% decentralized web usable and a huge part of<00:01:39.900> that<00:01:39.960> is<00:01:40.200> making<00:01:40.439> sure<00:01:40.680> developers<00:01:41.159> have 00:01:41.330 --> 00:01:41.340 align:start position:0% of that is making sure developers have 00:01:41.340 --> 00:01:42.889 align:start position:0% of that is making sure developers have tools<00:01:41.640> to<00:01:41.850> build<00:01:42.150> better<00:01:42.390> and<00:01:42.750> better 00:01:42.889 --> 00:01:42.899 align:start position:0% tools to build better and better 00:01:42.899 --> 00:01:44.990 align:start position:0% tools to build better and better applications<00:01:43.619> but<00:01:44.369> we<00:01:44.430> also<00:01:44.579> have<00:01:44.759> a<00:01:44.790> big 00:01:44.990 --> 00:01:45.000 align:start position:0% applications but we also have a big 00:01:45.000 --> 00:01:46.749 align:start position:0% applications but we also have a big responsibility<00:01:45.390> for<00:01:45.810> the<00:01:45.869> end<00:01:46.020> user<00:01:46.259> and<00:01:46.619> for 00:01:46.749 --> 00:01:46.759 align:start position:0% responsibility for the end user and for 00:01:46.759 --> 00:01:48.980 align:start position:0% responsibility for the end user and for the<00:01:47.759> end<00:01:47.880> user<00:01:48.060> we're<00:01:48.329> thinking<00:01:48.570> a<00:01:48.659> lot<00:01:48.780> about 00:01:48.980 --> 00:01:48.990 align:start position:0% the end user we're thinking a lot about 00:01:48.990 --> 00:01:52.660 align:start position:0% the end user we're thinking a lot about user<00:01:49.530> experience<00:01:50.360> security<00:01:51.360> and<00:01:51.540> education 00:01:52.660 --> 00:01:52.670 align:start position:0% user experience security and education 00:01:52.670 --> 00:01:55.880 align:start position:0% user experience security and education now<00:01:53.670> these<00:01:53.850> three<00:01:54.270> are<00:01:54.509> not<00:01:54.810> really<00:01:55.320> separable 00:01:55.880 --> 00:01:55.890 align:start position:0% now these three are not really separable 00:01:55.890 --> 00:01:58.370 align:start position:0% now these three are not really separable right<00:01:56.490> you<00:01:56.790> have<00:01:56.909> to<00:01:57.060> be<00:01:57.210> safe<00:01:57.600> in<00:01:57.960> order<00:01:58.200> to 00:01:58.370 --> 00:01:58.380 align:start position:0% right you have to be safe in order to 00:01:58.380 --> 00:02:01.940 align:start position:0% right you have to be safe in order to have<00:01:58.530> a<00:01:58.770> basic<00:01:59.189> good<00:01:59.520> experience<00:02:00.439> often<00:02:01.439> times 00:02:01.940 --> 00:02:01.950 align:start position:0% have a basic good experience often times 00:02:01.950 --> 00:02:04.310 align:start position:0% have a basic good experience often times not<00:02:02.159> always<00:02:02.579> but<00:02:02.759> often<00:02:02.969> the<00:02:03.750> more<00:02:03.930> you<00:02:04.079> know 00:02:04.310 --> 00:02:04.320 align:start position:0% not always but often the more you know 00:02:04.320 --> 00:02:07.550 align:start position:0% not always but often the more you know the<00:02:04.799> safer<00:02:05.159> you<00:02:05.250> are<00:02:05.280> and<00:02:05.670> we<00:02:06.659> think<00:02:06.899> a<00:02:07.049> good<00:02:07.290> UX 00:02:07.550 --> 00:02:07.560 align:start position:0% the safer you are and we think a good UX 00:02:07.560 --> 00:02:09.800 align:start position:0% the safer you are and we think a good UX should<00:02:08.039> help<00:02:08.250> educate<00:02:08.789> the<00:02:08.879> user<00:02:09.030> so<00:02:09.690> their 00:02:09.800 --> 00:02:09.810 align:start position:0% should help educate the user so their 00:02:09.810 --> 00:02:11.119 align:start position:0% should help educate the user so their expectations<00:02:10.470> are<00:02:10.590> met<00:02:10.739> and<00:02:10.950> their 00:02:11.119 --> 00:02:11.129 align:start position:0% expectations are met and their 00:02:11.129 --> 00:02:12.770 align:start position:0% expectations are met and their experience<00:02:11.700> is<00:02:11.879> smooth 00:02:12.770 --> 00:02:12.780 align:start position:0% experience is smooth 00:02:12.780 --> 00:02:15.590 align:start position:0% experience is smooth now<00:02:13.530> there<00:02:14.160> are<00:02:14.310> certainly<00:02:14.940> projects<00:02:15.450> out 00:02:15.590 --> 00:02:15.600 align:start position:0% now there are certainly projects out 00:02:15.600 --> 00:02:17.480 align:start position:0% now there are certainly projects out there<00:02:15.630> that<00:02:15.990> we're<00:02:16.080> super<00:02:16.500> keen<00:02:16.680> on<00:02:16.830> that<00:02:17.070> will 00:02:17.480 --> 00:02:17.490 align:start position:0% there that we're super keen on that will 00:02:17.490 --> 00:02:19.100 align:start position:0% there that we're super keen on that will totally<00:02:17.670> shift<00:02:18.150> the<00:02:18.330> paradigm<00:02:18.510> in<00:02:18.900> some<00:02:19.020> of 00:02:19.100 --> 00:02:19.110 align:start position:0% totally shift the paradigm in some of 00:02:19.110 --> 00:02:21.560 align:start position:0% totally shift the paradigm in some of these<00:02:19.170> areas<00:02:19.410> right<00:02:20.160> if<00:02:20.370> users<00:02:21.150> didn't<00:02:21.480> have 00:02:21.560 --> 00:02:21.570 align:start position:0% these areas right if users didn't have 00:02:21.570 --> 00:02:23.690 align:start position:0% these areas right if users didn't have to<00:02:21.660> be<00:02:21.750> educated<00:02:22.260> about<00:02:22.320> gas<00:02:22.650> we<00:02:23.040> would<00:02:23.250> save<00:02:23.490> a 00:02:23.690 --> 00:02:23.700 align:start position:0% to be educated about gas we would save a 00:02:23.700 --> 00:02:25.790 align:start position:0% to be educated about gas we would save a lot<00:02:23.730> of<00:02:23.880> time<00:02:24.180> and<00:02:24.540> energy<00:02:24.930> and<00:02:25.170> design 00:02:25.790 --> 00:02:25.800 align:start position:0% lot of time and energy and design 00:02:25.800 --> 00:02:28.250 align:start position:0% lot of time and energy and design iterations<00:02:26.280> but<00:02:27.210> we<00:02:27.300> also<00:02:27.420> recognize<00:02:27.660> the 00:02:28.250 --> 00:02:28.260 align:start position:0% iterations but we also recognize the 00:02:28.260 --> 00:02:30.380 align:start position:0% iterations but we also recognize the need<00:02:28.500> to<00:02:29.100> deliver<00:02:29.550> incremental<00:02:30.209> progress 00:02:30.380 --> 00:02:30.390 align:start position:0% need to deliver incremental progress 00:02:30.390 --> 00:02:34.490 align:start position:0% need to deliver incremental progress today<00:02:31.580> so<00:02:32.580> many<00:02:33.570> of<00:02:33.690> our<00:02:33.750> user<00:02:34.020> facing 00:02:34.490 --> 00:02:34.500 align:start position:0% today so many of our user facing 00:02:34.500 --> 00:02:36.199 align:start position:0% today so many of our user facing features<00:02:34.830> from<00:02:35.280> the<00:02:35.370> past<00:02:35.580> year<00:02:35.790> can<00:02:36.120> be 00:02:36.199 --> 00:02:36.209 align:start position:0% features from the past year can be 00:02:36.209 --> 00:02:38.530 align:start position:0% features from the past year can be placed<00:02:36.450> somewhere<00:02:36.870> around<00:02:37.230> this<00:02:37.800> continuum 00:02:38.530 --> 00:02:38.540 align:start position:0% placed somewhere around this continuum 00:02:38.540 --> 00:02:40.460 align:start position:0% placed somewhere around this continuum there's<00:02:39.540> some<00:02:39.660> stuff<00:02:39.840> that's<00:02:39.870> not<00:02:40.140> up<00:02:40.290> here 00:02:40.460 --> 00:02:40.470 align:start position:0% there's some stuff that's not up here 00:02:40.470 --> 00:02:43.430 align:start position:0% there's some stuff that's not up here our<00:02:41.250> progress<00:02:41.790> towards<00:02:42.209> 100%<00:02:42.870> test<00:02:43.380> coverage 00:02:43.430 --> 00:02:43.440 align:start position:0% our progress towards 100% test coverage 00:02:43.440 --> 00:02:47.810 align:start position:0% our progress towards 100% test coverage our<00:02:44.150> migration<00:02:45.150> to<00:02:45.660> typescript<00:02:46.400> but<00:02:47.400> a<00:02:47.580> lot<00:02:47.790> of 00:02:47.810 --> 00:02:47.820 align:start position:0% our migration to typescript but a lot of 00:02:47.820 --> 00:02:49.670 align:start position:0% our migration to typescript but a lot of our<00:02:47.970> user<00:02:48.120> facing<00:02:48.390> features<00:02:48.660> again<00:02:49.020> help 00:02:49.670 --> 00:02:49.680 align:start position:0% our user facing features again help 00:02:49.680 --> 00:02:51.199 align:start position:0% our user facing features again help promote<00:02:49.980> something<00:02:50.370> either<00:02:50.610> directly<00:02:51.120> or 00:02:51.199 --> 00:02:51.209 align:start position:0% promote something either directly or 00:02:51.209 --> 00:02:54.140 align:start position:0% promote something either directly or indirectly<00:02:51.540> on<00:02:51.989> this<00:02:52.110> continuum<00:02:52.560> so<00:02:53.430> I'd<00:02:54.030> like 00:02:54.140 --> 00:02:54.150 align:start position:0% indirectly on this continuum so I'd like 00:02:54.150 --> 00:02:55.520 align:start position:0% indirectly on this continuum so I'd like to<00:02:54.209> highlight<00:02:54.450> a<00:02:54.600> couple<00:02:54.690> of<00:02:54.989> those<00:02:55.200> that<00:02:55.410> are 00:02:55.520 --> 00:02:55.530 align:start position:0% to highlight a couple of those that are 00:02:55.530 --> 00:02:57.800 align:start position:0% to highlight a couple of those that are probably<00:02:55.880> particularly<00:02:56.880> relevant<00:02:57.420> to<00:02:57.660> some 00:02:57.800 --> 00:02:57.810 align:start position:0% probably particularly relevant to some 00:02:57.810 --> 00:03:00.470 align:start position:0% probably particularly relevant to some of<00:02:57.900> you<00:02:57.989> out<00:02:58.110> there<00:02:58.140> and<00:02:59.300> hopefully<00:03:00.300> you<00:03:00.360> learn 00:03:00.470 --> 00:03:00.480 align:start position:0% of you out there and hopefully you learn 00:03:00.480 --> 00:03:04.040 align:start position:0% of you out there and hopefully you learn something<00:03:00.690> so<00:03:02.360> as<00:03:03.360> many<00:03:03.600> of<00:03:03.660> you<00:03:03.750> might<00:03:03.900> know 00:03:04.040 --> 00:03:04.050 align:start position:0% something so as many of you might know 00:03:04.050 --> 00:03:06.830 align:start position:0% something so as many of you might know meta<00:03:04.650> mask<00:03:04.860> now<00:03:05.100> supports<00:03:05.670> treasure<00:03:06.480> and 00:03:06.830 --> 00:03:06.840 align:start position:0% meta mask now supports treasure and 00:03:06.840 --> 00:03:09.710 align:start position:0% meta mask now supports treasure and ledger<00:03:07.050> hardware<00:03:07.530> wallets<00:03:07.800> you<00:03:08.190> can<00:03:08.570> you<00:03:09.570> can 00:03:09.710 --> 00:03:09.720 align:start position:0% ledger hardware wallets you can you can 00:03:09.720 --> 00:03:11.120 align:start position:0% ledger hardware wallets you can you can applaud<00:03:09.930> for<00:03:09.989> tri-zone<00:03:10.290> measure<00:03:10.650> for<00:03:10.950> sure 00:03:11.120 --> 00:03:11.130 align:start position:0% applaud for tri-zone measure for sure 00:03:11.130 --> 00:03:13.280 align:start position:0% applaud for tri-zone measure for sure thank<00:03:12.090> you 00:03:13.280 --> 00:03:13.290 align:start position:0% thank you 00:03:13.290 --> 00:03:14.900 align:start position:0% thank you you<00:03:13.709> can<00:03:13.830> plug<00:03:13.980> the<00:03:14.100> device<00:03:14.310> right<00:03:14.580> into<00:03:14.820> your 00:03:14.900 --> 00:03:14.910 align:start position:0% you can plug the device right into your 00:03:14.910 --> 00:03:17.060 align:start position:0% you can plug the device right into your computer<00:03:15.030> and<00:03:15.600> sign<00:03:16.410> messages<00:03:16.890> and 00:03:17.060 --> 00:03:17.070 align:start position:0% computer and sign messages and 00:03:17.070 --> 00:03:18.560 align:start position:0% computer and sign messages and transactions<00:03:17.640> without<00:03:17.910> your<00:03:18.060> keys<00:03:18.239> ever 00:03:18.560 --> 00:03:18.570 align:start position:0% transactions without your keys ever 00:03:18.570 --> 00:03:21.199 align:start position:0% transactions without your keys ever leaving<00:03:18.840> the<00:03:19.110> device<00:03:19.519> this<00:03:20.519> basically<00:03:21.000> means 00:03:21.199 --> 00:03:21.209 align:start position:0% leaving the device this basically means 00:03:21.209 --> 00:03:23.180 align:start position:0% leaving the device this basically means that<00:03:21.390> any<00:03:21.720> DAP<00:03:22.049> that<00:03:22.350> supports<00:03:22.709> meta<00:03:22.950> mask 00:03:23.180 --> 00:03:23.190 align:start position:0% that any DAP that supports meta mask 00:03:23.190 --> 00:03:25.130 align:start position:0% that any DAP that supports meta mask gets<00:03:23.640> Hardware<00:03:24.180> support<00:03:24.510> right<00:03:24.750> out<00:03:24.959> of<00:03:24.989> the 00:03:25.130 --> 00:03:25.140 align:start position:0% gets Hardware support right out of the 00:03:25.140 --> 00:03:27.979 align:start position:0% gets Hardware support right out of the box<00:03:26.000> we<00:03:27.000> have<00:03:27.030> Bruner<00:03:27.420> to<00:03:27.540> thank<00:03:27.750> for<00:03:27.930> this 00:03:27.979 --> 00:03:27.989 align:start position:0% box we have Bruner to thank for this 00:03:27.989 --> 00:03:29.780 align:start position:0% box we have Bruner to thank for this wonderful<00:03:28.230> change<00:03:28.620> you<00:03:29.040> can<00:03:29.250> thank<00:03:29.549> him<00:03:29.640> in<00:03:29.730> a 00:03:29.780 --> 00:03:29.790 align:start position:0% wonderful change you can thank him in a 00:03:29.790 --> 00:03:33.590 align:start position:0% wonderful change you can thank him in a second<00:03:30.060> when<00:03:30.150> it<00:03:30.239> comes<00:03:30.390> on<00:03:30.600> the<00:03:32.480> next<00:03:33.480> project 00:03:33.590 --> 00:03:33.600 align:start position:0% second when it comes on the next project 00:03:33.600 --> 00:03:36.320 align:start position:0% second when it comes on the next project I'd<00:03:33.959> like<00:03:34.080> to<00:03:34.200> highlight<00:03:34.320> is<00:03:34.650> VIP<00:03:35.130> 1102<00:03:35.850> this 00:03:36.320 --> 00:03:36.330 align:start position:0% I'd like to highlight is VIP 1102 this 00:03:36.330 --> 00:03:39.920 align:start position:0% I'd like to highlight is VIP 1102 this is<00:03:36.510> super<00:03:37.049> super<00:03:37.230> exciting<00:03:38.000> the<00:03:39.000> way<00:03:39.150> most<00:03:39.600> web 00:03:39.920 --> 00:03:39.930 align:start position:0% is super super exciting the way most web 00:03:39.930 --> 00:03:43.880 align:start position:0% is super super exciting the way most web 3<00:03:40.200> browsers<00:03:40.620> work<00:03:40.950> today<00:03:41.340> is<00:03:41.780> by<00:03:42.780> exposing<00:03:43.650> the 00:03:43.880 --> 00:03:43.890 align:start position:0% 3 browsers work today is by exposing the 00:03:43.890 --> 00:03:45.680 align:start position:0% 3 browsers work today is by exposing the etherion<00:03:44.310> provider<00:03:44.640> to<00:03:44.910> every<00:03:45.390> site<00:03:45.570> you 00:03:45.680 --> 00:03:45.690 align:start position:0% etherion provider to every site you 00:03:45.690 --> 00:03:47.720 align:start position:0% etherion provider to every site you visit<00:03:45.720> which<00:03:46.380> means<00:03:46.620> your<00:03:47.040> addresses<00:03:47.640> are 00:03:47.720 --> 00:03:47.730 align:start position:0% visit which means your addresses are 00:03:47.730 --> 00:03:49.759 align:start position:0% visit which means your addresses are exposed<00:03:48.090> to<00:03:48.360> every<00:03:48.780> site<00:03:48.959> you<00:03:49.049> visit<00:03:49.079> no 00:03:49.759 --> 00:03:49.769 align:start position:0% exposed to every site you visit no 00:03:49.769 --> 00:03:52.370 align:start position:0% exposed to every site you visit no matter<00:03:49.950> whether<00:03:50.190> that<00:03:50.690> site<00:03:51.690> is<00:03:51.870> even<00:03:52.110> trying 00:03:52.370 --> 00:03:52.380 align:start position:0% matter whether that site is even trying 00:03:52.380 --> 00:03:55.819 align:start position:0% matter whether that site is even trying to<00:03:52.560> access<00:03:52.890> the<00:03:53.010> web<00:03:53.130> 3<00:03:53.280> object<00:03:53.549> or<00:03:53.640> not<00:03:54.829> this 00:03:55.819 --> 00:03:55.829 align:start position:0% to access the web 3 object or not this 00:03:55.829 --> 00:03:58.310 align:start position:0% to access the web 3 object or not this is<00:03:56.329> pretty<00:03:57.329> smooth<00:03:57.630> and<00:03:57.810> sip<00:03:58.049> this<00:03:58.140> makes 00:03:58.310 --> 00:03:58.320 align:start position:0% is pretty smooth and sip this makes 00:03:58.320 --> 00:03:59.960 align:start position:0% is pretty smooth and sip this makes things<00:03:58.440> simple<00:03:58.860> for<00:03:58.890> developers<00:03:59.400> obviously 00:03:59.960 --> 00:03:59.970 align:start position:0% things simple for developers obviously 00:03:59.970 --> 00:04:02.240 align:start position:0% things simple for developers obviously but<00:04:00.180> it<00:04:00.420> is<00:04:00.600> a<00:04:00.630> pretty<00:04:00.930> terrible<00:04:01.590> privacy 00:04:02.240 --> 00:04:02.250 align:start position:0% but it is a pretty terrible privacy 00:04:02.250 --> 00:04:04.580 align:start position:0% but it is a pretty terrible privacy experience<00:04:02.760> for<00:04:02.970> the<00:04:03.060> end<00:04:03.180> user<00:04:03.420> it's<00:04:04.380> very 00:04:04.580 --> 00:04:04.590 align:start position:0% experience for the end user it's very 00:04:04.590 --> 00:04:06.259 align:start position:0% experience for the end user it's very easy<00:04:04.799> to<00:04:05.010> imagine<00:04:05.100> how<00:04:05.579> this<00:04:05.970> could<00:04:06.150> be<00:04:06.180> used 00:04:06.259 --> 00:04:06.269 align:start position:0% easy to imagine how this could be used 00:04:06.269 --> 00:04:09.100 align:start position:0% easy to imagine how this could be used to<00:04:06.750> fingerprint<00:04:07.440> or<00:04:07.680> track<00:04:08.280> or<00:04:08.459> fish 00:04:09.100 --> 00:04:09.110 align:start position:0% to fingerprint or track or fish 00:04:09.110 --> 00:04:12.470 align:start position:0% to fingerprint or track or fish unsuspecting<00:04:10.110> users<00:04:10.380> across<00:04:10.650> the<00:04:10.860> web<00:04:11.030> so<00:04:12.030> EIP 00:04:12.470 --> 00:04:12.480 align:start position:0% unsuspecting users across the web so EIP 00:04:12.480 --> 00:04:15.140 align:start position:0% unsuspecting users across the web so EIP 11:02<00:04:13.079> defines<00:04:13.470> a<00:04:13.709> new<00:04:13.890> standard<00:04:14.340> where 00:04:15.140 --> 00:04:15.150 align:start position:0% 11:02 defines a new standard where 00:04:15.150 --> 00:04:17.509 align:start position:0% 11:02 defines a new standard where rather<00:04:15.570> than<00:04:15.739> expecting<00:04:16.739> these<00:04:16.859> addresses<00:04:17.370> to 00:04:17.509 --> 00:04:17.519 align:start position:0% rather than expecting these addresses to 00:04:17.519 --> 00:04:19.490 align:start position:0% rather than expecting these addresses to be<00:04:17.549> exposed<00:04:17.940> by<00:04:18.180> default<00:04:18.630> the<00:04:18.989> DAP<00:04:19.140> has<00:04:19.350> to 00:04:19.490 --> 00:04:19.500 align:start position:0% be exposed by default the DAP has to 00:04:19.500 --> 00:04:21.110 align:start position:0% be exposed by default the DAP has to request<00:04:19.739> access<00:04:20.100> to<00:04:20.340> them<00:04:20.549> using<00:04:20.940> a<00:04:21.000> new 00:04:21.110 --> 00:04:21.120 align:start position:0% request access to them using a new 00:04:21.120 --> 00:04:24.080 align:start position:0% request access to them using a new provider<00:04:21.450> method<00:04:21.630> aetherium<00:04:22.380> enable<00:04:23.090> when 00:04:24.080 --> 00:04:24.090 align:start position:0% provider method aetherium enable when 00:04:24.090 --> 00:04:25.909 align:start position:0% provider method aetherium enable when the<00:04:24.180> user<00:04:24.360> can<00:04:24.630> sense<00:04:24.840> probably<00:04:25.229> on<00:04:25.530> a<00:04:25.560> UI 00:04:25.909 --> 00:04:25.919 align:start position:0% the user can sense probably on a UI 00:04:25.919 --> 00:04:26.720 align:start position:0% the user can sense probably on a UI similar<00:04:26.400> to<00:04:26.550> the 00:04:26.720 --> 00:04:26.730 align:start position:0% similar to the 00:04:26.730 --> 00:04:28.550 align:start position:0% similar to the we<00:04:26.820> see<00:04:26.940> up<00:04:27.090> here<00:04:27.120> the<00:04:27.840> promise<00:04:28.110> will<00:04:28.230> resolve 00:04:28.550 --> 00:04:28.560 align:start position:0% we see up here the promise will resolve 00:04:28.560 --> 00:04:32.150 align:start position:0% we see up here the promise will resolve with<00:04:28.830> the<00:04:28.860> users<00:04:29.160> address<00:04:30.590> clients<00:04:31.590> like<00:04:31.860> meta 00:04:32.150 --> 00:04:32.160 align:start position:0% with the users address clients like meta 00:04:32.160 --> 00:04:34.580 align:start position:0% with the users address clients like meta masks<00:04:32.400> will<00:04:32.700> also<00:04:33.240> perhaps<00:04:33.450> cache<00:04:34.020> or<00:04:34.380> allow 00:04:34.580 --> 00:04:34.590 align:start position:0% masks will also perhaps cache or allow 00:04:34.590 --> 00:04:38.540 align:start position:0% masks will also perhaps cache or allow the<00:04:34.650> user<00:04:34.980> to<00:04:35.360> let<00:04:36.360> the<00:04:36.950> adapt<00:04:37.950> sort<00:04:38.460> of 00:04:38.540 --> 00:04:38.550 align:start position:0% the user to let the adapt sort of 00:04:38.550 --> 00:04:40.100 align:start position:0% the user to let the adapt sort of continue<00:04:39.210> having<00:04:39.390> access<00:04:39.720> to<00:04:39.780> their<00:04:39.990> address 00:04:40.100 --> 00:04:40.110 align:start position:0% continue having access to their address 00:04:40.110 --> 00:04:42.020 align:start position:0% continue having access to their address in<00:04:40.860> which<00:04:40.980> case<00:04:41.190> the<00:04:41.310> promise<00:04:41.580> will<00:04:41.700> resolve 00:04:42.020 --> 00:04:42.030 align:start position:0% in which case the promise will resolve 00:04:42.030 --> 00:04:44.720 align:start position:0% in which case the promise will resolve immediately<00:04:42.860> so<00:04:43.860> we<00:04:43.890> think<00:04:44.100> this<00:04:44.220> is<00:04:44.280> the<00:04:44.430> best 00:04:44.720 --> 00:04:44.730 align:start position:0% immediately so we think this is the best 00:04:44.730 --> 00:04:47.650 align:start position:0% immediately so we think this is the best balance<00:04:45.270> between<00:04:45.950> developer<00:04:46.950> experience 00:04:47.650 --> 00:04:47.660 align:start position:0% balance between developer experience 00:04:47.660 --> 00:04:50.540 align:start position:0% balance between developer experience onboarding<00:04:48.660> UX<00:04:48.930> and<00:04:49.260> privacy<00:04:50.130> protections 00:04:50.540 --> 00:04:50.550 align:start position:0% onboarding UX and privacy protections 00:04:50.550 --> 00:04:53.450 align:start position:0% onboarding UX and privacy protections for<00:04:50.820> our<00:04:50.880> users<00:04:51.180> a<00:04:51.680> huge<00:04:52.680> shout-out<00:04:53.160> to<00:04:53.340> the 00:04:53.450 --> 00:04:53.460 align:start position:0% for our users a huge shout-out to the 00:04:53.460 --> 00:04:55.340 align:start position:0% for our users a huge shout-out to the teams<00:04:53.640> at<00:04:53.790> status<00:04:54.180> and<00:04:54.390> missed<00:04:54.600> further<00:04:54.990> early 00:04:55.340 --> 00:04:55.350 align:start position:0% teams at status and missed further early 00:04:55.350 --> 00:04:57.770 align:start position:0% teams at status and missed further early support<00:04:55.710> with<00:04:55.890> this<00:04:56.010> proposal<00:04:56.540> shout<00:04:57.540> out<00:04:57.630> to 00:04:57.770 --> 00:04:57.780 align:start position:0% support with this proposal shout out to 00:04:57.780 --> 00:04:58.970 align:start position:0% support with this proposal shout out to everyone<00:04:58.020> in<00:04:58.110> the<00:04:58.230> community<00:04:58.620> who<00:04:58.710> gave<00:04:58.860> us 00:04:58.970 --> 00:04:58.980 align:start position:0% everyone in the community who gave us 00:04:58.980 --> 00:05:00.650 align:start position:0% everyone in the community who gave us really<00:04:59.160> valuable<00:04:59.730> feedback<00:05:00.000> and<00:05:00.330> helped<00:05:00.510> us 00:05:00.650 --> 00:05:00.660 align:start position:0% really valuable feedback and helped us 00:05:00.660 --> 00:05:02.510 align:start position:0% really valuable feedback and helped us create<00:05:01.440> the<00:05:01.590> version<00:05:01.860> that<00:05:01.950> it<00:05:02.100> is<00:05:02.220> today 00:05:02.510 --> 00:05:02.520 align:start position:0% create the version that it is today 00:05:02.520 --> 00:05:05.300 align:start position:0% create the version that it is today and<00:05:03.290> massive<00:05:04.290> massive<00:05:04.500> props<00:05:04.890> to<00:05:05.130> Paul 00:05:05.300 --> 00:05:05.310 align:start position:0% and massive massive props to Paul 00:05:05.310 --> 00:05:07.130 align:start position:0% and massive massive props to Paul Bhushan<00:05:05.700> you<00:05:06.240> might<00:05:06.390> know<00:05:06.480> him<00:05:06.540> as<00:05:06.630> bit<00:05:06.780> pusher 00:05:07.130 --> 00:05:07.140 align:start position:0% Bhushan you might know him as bit pusher 00:05:07.140 --> 00:05:09.380 align:start position:0% Bhushan you might know him as bit pusher for<00:05:07.980> his<00:05:08.100> tireless<00:05:08.370> work<00:05:08.670> making<00:05:09.060> sure<00:05:09.180> people 00:05:09.380 --> 00:05:09.390 align:start position:0% for his tireless work making sure people 00:05:09.390 --> 00:05:10.910 align:start position:0% for his tireless work making sure people have<00:05:09.540> what<00:05:09.960> they<00:05:10.080> need<00:05:10.320> to<00:05:10.530> implement<00:05:10.710> this 00:05:10.910 --> 00:05:10.920 align:start position:0% have what they need to implement this 00:05:10.920 --> 00:05:12.350 align:start position:0% have what they need to implement this change<00:05:10.980> answering<00:05:11.790> questions 00:05:12.350 --> 00:05:12.360 align:start position:0% change answering questions 00:05:12.360 --> 00:05:18.140 align:start position:0% change answering questions staying<00:05:12.840> receptive<00:05:13.200> to<00:05:13.320> feedback<00:05:16.970> this<00:05:17.970> will 00:05:18.140 --> 00:05:18.150 align:start position:0% staying receptive to feedback this will 00:05:18.150 --> 00:05:19.940 align:start position:0% staying receptive to feedback this will be<00:05:18.240> rolling<00:05:18.450> out<00:05:18.510> as<00:05:18.660> an<00:05:18.750> opt-in<00:05:19.170> feature<00:05:19.530> in 00:05:19.940 --> 00:05:19.950 align:start position:0% be rolling out as an opt-in feature in 00:05:19.950 --> 00:05:22.280 align:start position:0% be rolling out as an opt-in feature in meta<00:05:20.160> masks<00:05:20.340> for<00:05:20.730> users<00:05:21.000> starting<00:05:21.510> on<00:05:21.600> Monday 00:05:22.280 --> 00:05:22.290 align:start position:0% meta masks for users starting on Monday 00:05:22.290 --> 00:05:24.530 align:start position:0% meta masks for users starting on Monday so<00:05:22.620> if<00:05:23.010> you<00:05:23.190> haven't<00:05:23.580> taken<00:05:23.940> note<00:05:24.270> of<00:05:24.300> this 00:05:24.530 --> 00:05:24.540 align:start position:0% so if you haven't taken note of this 00:05:24.540 --> 00:05:26.000 align:start position:0% so if you haven't taken note of this take<00:05:24.930> note<00:05:25.140> there's<00:05:25.350> a<00:05:25.440> really<00:05:25.650> succinct 00:05:26.000 --> 00:05:26.010 align:start position:0% take note there's a really succinct 00:05:26.010 --> 00:05:29.000 align:start position:0% take note there's a really succinct guide<00:05:26.310> on<00:05:26.640> our<00:05:26.910> medium<00:05:27.480> account<00:05:27.840> so<00:05:28.110> check<00:05:28.920> it 00:05:29.000 --> 00:05:29.010 align:start position:0% guide on our medium account so check it 00:05:29.010 --> 00:05:30.620 align:start position:0% guide on our medium account so check it out<00:05:29.100> or<00:05:29.370> come<00:05:29.610> chat<00:05:29.790> with<00:05:29.880> us<00:05:29.970> after<00:05:30.210> the<00:05:30.240> after 00:05:30.620 --> 00:05:30.630 align:start position:0% out or come chat with us after the after 00:05:30.630 --> 00:05:36.320 align:start position:0% out or come chat with us after the after the<00:05:30.660> show<00:05:32.150> cool<00:05:34.610> next<00:05:35.610> up<00:05:35.760> this<00:05:35.850> one's<00:05:36.030> simple 00:05:36.320 --> 00:05:36.330 align:start position:0% the show cool next up this one's simple 00:05:36.330 --> 00:05:39.230 align:start position:0% the show cool next up this one's simple so<00:05:37.130> meta<00:05:38.130> mask<00:05:38.310> supports<00:05:38.730> the<00:05:38.850> recently 00:05:39.230 --> 00:05:39.240 align:start position:0% so meta mask supports the recently 00:05:39.240 --> 00:05:41.930 align:start position:0% so meta mask supports the recently merged<00:05:39.480> sign<00:05:40.080> type<00:05:40.290> data<00:05:40.470> spec<00:05:40.800> we're<00:05:41.580> very 00:05:41.930 --> 00:05:41.940 align:start position:0% merged sign type data spec we're very 00:05:41.940 --> 00:05:44.030 align:start position:0% merged sign type data spec we're very excited<00:05:42.390> to<00:05:42.510> finally<00:05:42.690> settle<00:05:43.140> on<00:05:43.260> one<00:05:43.590> signing 00:05:44.030 --> 00:05:44.040 align:start position:0% excited to finally settle on one signing 00:05:44.040 --> 00:05:45.860 align:start position:0% excited to finally settle on one signing method<00:05:44.340> that<00:05:44.490> we<00:05:44.580> think<00:05:44.820> is<00:05:45.000> human<00:05:45.570> readable 00:05:45.860 --> 00:05:45.870 align:start position:0% method that we think is human readable 00:05:45.870 --> 00:05:48.590 align:start position:0% method that we think is human readable and<00:05:46.170> cheap<00:05:46.680> to<00:05:46.800> verify<00:05:47.100> on<00:05:47.340> chain<00:05:47.730> Ben<00:05:48.450> back 00:05:48.590 --> 00:05:48.600 align:start position:0% and cheap to verify on chain Ben back 00:05:48.600 --> 00:05:49.640 align:start position:0% and cheap to verify on chain Ben back and<00:05:48.780> forth<00:05:48.930> on<00:05:49.050> a<00:05:49.140> lot<00:05:49.230> of<00:05:49.260> different<00:05:49.380> ways<00:05:49.620> to 00:05:49.640 --> 00:05:49.650 align:start position:0% and forth on a lot of different ways to 00:05:49.650 --> 00:05:51.620 align:start position:0% and forth on a lot of different ways to do<00:05:49.860> this<00:05:49.980> for<00:05:50.160> a<00:05:50.190> long<00:05:50.400> time<00:05:50.670> and<00:05:50.970> this<00:05:51.150> is<00:05:51.390> the 00:05:51.620 --> 00:05:51.630 align:start position:0% do this for a long time and this is the 00:05:51.630 --> 00:05:52.820 align:start position:0% do this for a long time and this is the signing<00:05:51.900> method<00:05:52.110> that<00:05:52.230> we<00:05:52.320> will<00:05:52.410> encourage 00:05:52.820 --> 00:05:52.830 align:start position:0% signing method that we will encourage 00:05:52.830 --> 00:05:54.530 align:start position:0% signing method that we will encourage all<00:05:53.040> developers<00:05:53.520> to<00:05:53.760> use<00:05:53.940> when<00:05:54.210> they<00:05:54.300> need 00:05:54.530 --> 00:05:54.540 align:start position:0% all developers to use when they need 00:05:54.540 --> 00:05:57.470 align:start position:0% all developers to use when they need their<00:05:54.870> users<00:05:55.710> to<00:05:55.800> sign<00:05:56.040> a<00:05:56.070> piece<00:05:56.250> of<00:05:56.370> data<00:05:56.490> it's 00:05:57.470 --> 00:05:57.480 align:start position:0% their users to sign a piece of data it's 00:05:57.480 --> 00:05:59.450 align:start position:0% their users to sign a piece of data it's also<00:05:57.720> the<00:05:58.020> UI<00:05:58.200> that<00:05:58.500> we<00:05:58.650> will<00:05:58.800> continue<00:05:59.310> to 00:05:59.450 --> 00:05:59.460 align:start position:0% also the UI that we will continue to 00:05:59.460 --> 00:06:03.170 align:start position:0% also the UI that we will continue to test<00:05:59.700> and<00:05:59.970> iterate<00:06:00.620> so<00:06:01.620> that<00:06:02.250> we<00:06:02.550> can<00:06:02.790> kind<00:06:03.060> of 00:06:03.170 --> 00:06:03.180 align:start position:0% test and iterate so that we can kind of 00:06:03.180 --> 00:06:04.760 align:start position:0% test and iterate so that we can kind of hone<00:06:03.420> in<00:06:03.630> on<00:06:03.750> the<00:06:03.900> best<00:06:04.110> way<00:06:04.290> to<00:06:04.320> present<00:06:04.680> this 00:06:04.760 --> 00:06:04.770 align:start position:0% hone in on the best way to present this 00:06:04.770 --> 00:06:08.600 align:start position:0% hone in on the best way to present this interaction<00:06:05.160> to<00:06:05.370> folks<00:06:05.550> out<00:06:05.700> there<00:06:06.050> and<00:06:07.610> then 00:06:08.600 --> 00:06:08.610 align:start position:0% interaction to folks out there and then 00:06:08.610 --> 00:06:12.980 align:start position:0% interaction to folks out there and then last<00:06:09.000> I<00:06:09.990> want<00:06:10.500> to<00:06:10.560> mention<00:06:10.710> VIP<00:06:11.840> 747<00:06:12.840> which 00:06:12.980 --> 00:06:12.990 align:start position:0% last I want to mention VIP 747 which 00:06:12.990 --> 00:06:16.190 align:start position:0% last I want to mention VIP 747 which defines<00:06:13.410> a<00:06:13.710> watch<00:06:14.040> asset<00:06:14.550> method<00:06:15.020> we<00:06:16.020> know 00:06:16.190 --> 00:06:16.200 align:start position:0% defines a watch asset method we know 00:06:16.200 --> 00:06:18.110 align:start position:0% defines a watch asset method we know that<00:06:16.410> many<00:06:16.680> of<00:06:16.800> our<00:06:16.920> users<00:06:17.130> care<00:06:17.670> a<00:06:17.700> lot<00:06:17.910> about 00:06:18.110 --> 00:06:18.120 align:start position:0% that many of our users care a lot about 00:06:18.120 --> 00:06:21.050 align:start position:0% that many of our users care a lot about tokens<00:06:18.660> and<00:06:18.980> not<00:06:19.980> many<00:06:20.490> of<00:06:20.640> our<00:06:20.760> users<00:06:20.910> really 00:06:21.050 --> 00:06:21.060 align:start position:0% tokens and not many of our users really 00:06:21.060 --> 00:06:23.090 align:start position:0% tokens and not many of our users really understand<00:06:21.840> that<00:06:22.050> their<00:06:22.200> tokens<00:06:22.590> are<00:06:22.680> tracts 00:06:23.090 --> 00:06:23.100 align:start position:0% understand that their tokens are tracts 00:06:23.100 --> 00:06:24.710 align:start position:0% understand that their tokens are tracts not<00:06:23.580> necessarily<00:06:24.000> inherently<00:06:24.240> to<00:06:24.600> their 00:06:24.710 --> 00:06:24.720 align:start position:0% not necessarily inherently to their 00:06:24.720 --> 00:06:27.910 align:start position:0% not necessarily inherently to their address<00:06:24.870> but<00:06:25.170> on<00:06:25.320> a<00:06:25.560> contract<00:06:26.010> so<00:06:26.460> rather<00:06:27.330> than 00:06:27.910 --> 00:06:27.920 align:start position:0% address but on a contract so rather than 00:06:27.920 --> 00:06:30.980 align:start position:0% address but on a contract so rather than relying<00:06:28.920> on<00:06:29.220> a<00:06:29.280> centralized<00:06:30.000> token<00:06:30.510> list<00:06:30.690> so 00:06:30.980 --> 00:06:30.990 align:start position:0% relying on a centralized token list so 00:06:30.990 --> 00:06:32.810 align:start position:0% relying on a centralized token list so that<00:06:31.110> we<00:06:31.200> can<00:06:31.380> Auto<00:06:31.710> detect<00:06:32.070> tokens<00:06:32.550> and 00:06:32.810 --> 00:06:32.820 align:start position:0% that we can Auto detect tokens and 00:06:32.820 --> 00:06:34.970 align:start position:0% that we can Auto detect tokens and rather<00:06:33.240> than<00:06:33.450> forcing<00:06:33.960> users<00:06:34.170> to<00:06:34.470> manually 00:06:34.970 --> 00:06:34.980 align:start position:0% rather than forcing users to manually 00:06:34.980 --> 00:06:38.240 align:start position:0% rather than forcing users to manually add<00:06:35.010> these<00:06:35.370> tokens<00:06:35.730> themselves<00:06:36.420> VIP<00:06:37.380> 747 00:06:38.240 --> 00:06:38.250 align:start position:0% add these tokens themselves VIP 747 00:06:38.250 --> 00:06:40.500 align:start position:0% add these tokens themselves VIP 747 proposes<00:06:38.760> a<00:06:38.940> watch<00:06:39.690> asset<00:06:40.170> method 00:06:40.500 --> 00:06:40.510 align:start position:0% proposes a watch asset method 00:06:40.510 --> 00:06:43.860 align:start position:0% proposes a watch asset method that<00:06:40.690> let's<00:06:40.930> adapt<00:06:41.760> suggest<00:06:42.760> an<00:06:43.090> asset<00:06:43.510> to<00:06:43.780> the 00:06:43.860 --> 00:06:43.870 align:start position:0% that let's adapt suggest an asset to the 00:06:43.870 --> 00:06:46.440 align:start position:0% that let's adapt suggest an asset to the users<00:06:44.170> wallet<00:06:44.530> to<00:06:44.710> track<00:06:44.950> so<00:06:45.730> for<00:06:45.880> example<00:06:46.210> I 00:06:46.440 --> 00:06:46.450 align:start position:0% users wallet to track so for example I 00:06:46.450 --> 00:06:49.140 align:start position:0% users wallet to track so for example I could<00:06:47.140> go<00:06:47.380> to<00:06:47.500> an<00:06:47.680> exchange<00:06:47.860> purchase<00:06:48.730> a<00:06:48.820> token 00:06:49.140 --> 00:06:49.150 align:start position:0% could go to an exchange purchase a token 00:06:49.150 --> 00:06:51.300 align:start position:0% could go to an exchange purchase a token and<00:06:49.360> the<00:06:49.540> Matt<00:06:49.720> exchange<00:06:50.140> could<00:06:50.440> suggest<00:06:50.920> it 00:06:51.300 --> 00:06:51.310 align:start position:0% and the Matt exchange could suggest it 00:06:51.310 --> 00:06:53.160 align:start position:0% and the Matt exchange could suggest it could<00:06:51.370> call<00:06:51.790> watch<00:06:52.030> asset<00:06:52.420> and<00:06:52.570> suggest<00:06:52.990> it<00:06:53.140> to 00:06:53.160 --> 00:06:53.170 align:start position:0% could call watch asset and suggest it to 00:06:53.170 --> 00:06:55.170 align:start position:0% could call watch asset and suggest it to meta<00:06:53.380> mask<00:06:53.590> that<00:06:53.770> I'd<00:06:53.890> track<00:06:54.130> this<00:06:54.250> token<00:06:54.610> I'd 00:06:55.170 --> 00:06:55.180 align:start position:0% meta mask that I'd track this token I'd 00:06:55.180 --> 00:06:56.640 align:start position:0% meta mask that I'd track this token I'd probably<00:06:55.360> see<00:06:55.690> a<00:06:55.720> modal<00:06:55.990> like<00:06:56.080> this<00:06:56.260> I'd<00:06:56.500> click 00:06:56.640 --> 00:06:56.650 align:start position:0% probably see a modal like this I'd click 00:06:56.650 --> 00:06:58.050 align:start position:0% probably see a modal like this I'd click Add<00:06:56.830> token<00:06:57.250> and<00:06:57.400> it<00:06:57.460> would<00:06:57.550> be<00:06:57.640> permanently 00:06:58.050 --> 00:06:58.060 align:start position:0% Add token and it would be permanently 00:06:58.060 --> 00:07:00.330 align:start position:0% Add token and it would be permanently added<00:06:58.210> to<00:06:58.420> my<00:06:58.510> meta<00:06:58.690> mask<00:06:58.950> we're<00:06:59.950> super 00:07:00.330 --> 00:07:00.340 align:start position:0% added to my meta mask we're super 00:07:00.340 --> 00:07:01.490 align:start position:0% added to my meta mask we're super excited<00:07:00.640> about<00:07:00.700> this<00:07:00.940> one<00:07:01.120> because 00:07:01.490 --> 00:07:01.500 align:start position:0% excited about this one because 00:07:01.500 --> 00:07:03.330 align:start position:0% excited about this one because theoretically<00:07:02.500> we<00:07:02.680> could<00:07:02.800> use<00:07:02.950> it<00:07:03.070> for<00:07:03.220> other 00:07:03.330 --> 00:07:03.340 align:start position:0% theoretically we could use it for other 00:07:03.340 --> 00:07:05.010 align:start position:0% theoretically we could use it for other asset<00:07:03.820> types<00:07:04.000> going<00:07:04.330> forward<00:07:04.660> like 00:07:05.010 --> 00:07:05.020 align:start position:0% asset types going forward like 00:07:05.020 --> 00:07:08.070 align:start position:0% asset types going forward like subscriptions<00:07:05.740> or<00:07:06.090> even<00:07:07.090> use<00:07:07.480> it<00:07:07.660> to<00:07:07.690> suggest 00:07:08.070 --> 00:07:08.080 align:start position:0% subscriptions or even use it to suggest 00:07:08.080 --> 00:07:10.980 align:start position:0% subscriptions or even use it to suggest say<00:07:08.710> watching<00:07:09.250> a<00:07:09.580> contract<00:07:10.180> account<00:07:10.570> that<00:07:10.870> the 00:07:10.980 --> 00:07:10.990 align:start position:0% say watching a contract account that the 00:07:10.990 --> 00:07:13.320 align:start position:0% say watching a contract account that the user<00:07:11.140> might<00:07:11.350> not<00:07:11.470> watch<00:07:11.620> it<00:07:11.800> so<00:07:12.610> there's<00:07:13.150> a<00:07:13.180> lot 00:07:13.320 --> 00:07:13.330 align:start position:0% user might not watch it so there's a lot 00:07:13.330 --> 00:07:15.330 align:start position:0% user might not watch it so there's a lot of<00:07:13.450> potential<00:07:13.810> for<00:07:13.840> this<00:07:14.050> huge<00:07:14.950> shadow<00:07:15.130> to 00:07:15.330 --> 00:07:15.340 align:start position:0% of potential for this huge shadow to 00:07:15.340 --> 00:07:16.860 align:start position:0% of potential for this huge shadow to estaban<00:07:15.700> me<00:07:15.850> know<00:07:16.000> a<00:07:16.030> new<00:07:16.300> member<00:07:16.510> of<00:07:16.540> our<00:07:16.720> team 00:07:16.860 --> 00:07:16.870 align:start position:0% estaban me know a new member of our team 00:07:16.870 --> 00:07:18.390 align:start position:0% estaban me know a new member of our team and<00:07:17.110> Dan<00:07:17.320> Finley<00:07:17.710> for<00:07:17.890> their<00:07:17.980> work<00:07:18.070> on<00:07:18.250> this 00:07:18.390 --> 00:07:18.400 align:start position:0% and Dan Finley for their work on this 00:07:18.400 --> 00:07:25.140 align:start position:0% and Dan Finley for their work on this proposal<00:07:18.930> so<00:07:20.460> yeah<00:07:21.460> a<00:07:23.640> little<00:07:24.640> bit<00:07:24.730> of<00:07:24.790> a<00:07:24.910> blitz 00:07:25.140 --> 00:07:25.150 align:start position:0% proposal so yeah a little bit of a blitz 00:07:25.150 --> 00:07:26.850 align:start position:0% proposal so yeah a little bit of a blitz through<00:07:25.360> some<00:07:25.540> of<00:07:25.600> those<00:07:25.690> projects<00:07:26.110> but<00:07:26.830> I 00:07:26.850 --> 00:07:26.860 align:start position:0% through some of those projects but I 00:07:26.860 --> 00:07:28.320 align:start position:0% through some of those projects but I hope<00:07:27.070> this<00:07:27.280> was<00:07:27.460> informative<00:07:27.580> worth<00:07:28.180> your 00:07:28.320 --> 00:07:28.330 align:start position:0% hope this was informative worth your 00:07:28.330 --> 00:07:30.930 align:start position:0% hope this was informative worth your time<00:07:28.540> and<00:07:28.870> I<00:07:29.740> would<00:07:30.040> like<00:07:30.190> to<00:07:30.220> now<00:07:30.520> turn<00:07:30.580> it 00:07:30.930 --> 00:07:30.940 align:start position:0% time and I would like to now turn it 00:07:30.940 --> 00:07:32.730 align:start position:0% time and I would like to now turn it over<00:07:31.060> to<00:07:31.360> Jenny<00:07:31.690> to<00:07:31.990> give<00:07:32.110> you<00:07:32.200> a<00:07:32.260> sneak<00:07:32.500> peek 00:07:32.730 --> 00:07:32.740 align:start position:0% over to Jenny to give you a sneak peek 00:07:32.740 --> 00:07:34.140 align:start position:0% over to Jenny to give you a sneak peek of<00:07:32.860> some<00:07:33.130> of<00:07:33.220> the<00:07:33.280> projects<00:07:33.640> you<00:07:33.730> can<00:07:33.850> expect 00:07:34.140 --> 00:07:34.150 align:start position:0% of some of the projects you can expect 00:07:34.150 --> 00:07:40.550 align:start position:0% of some of the projects you can expect to<00:07:34.240> see<00:07:34.420> in<00:07:34.600> the<00:07:34.780> coming<00:07:35.020> year<00:07:35.220> thank<00:07:36.220> you 00:07:40.550 --> 00:07:40.560 align:start position:0% 00:07:40.560 --> 00:07:43.800 align:start position:0% thank<00:07:41.560> you<00:07:42.480> thanks<00:07:43.480> Bobby 00:07:43.800 --> 00:07:43.810 align:start position:0% thank you thanks Bobby 00:07:43.810 --> 00:07:46.740 align:start position:0% thank you thanks Bobby hi<00:07:44.800> I'm<00:07:45.130> Jenny<00:07:45.460> I'm<00:07:45.820> a<00:07:45.880> developer<00:07:46.390> at<00:07:46.510> madame 00:07:46.740 --> 00:07:46.750 align:start position:0% hi I'm Jenny I'm a developer at madame 00:07:46.750 --> 00:07:49.620 align:start position:0% hi I'm Jenny I'm a developer at madame masque<00:07:47.010> and<00:07:48.010> i'm<00:07:48.190> currently<00:07:48.520> here<00:07:48.910> to<00:07:49.360> share 00:07:49.620 --> 00:07:49.630 align:start position:0% masque and i'm currently here to share 00:07:49.630 --> 00:07:51.180 align:start position:0% masque and i'm currently here to share with<00:07:49.810> you<00:07:50.050> some<00:07:50.410> of<00:07:50.500> the<00:07:50.560> projects<00:07:50.980> were 00:07:51.180 --> 00:07:51.190 align:start position:0% with you some of the projects were 00:07:51.190 --> 00:07:53.220 align:start position:0% with you some of the projects were working<00:07:51.520> on<00:07:51.640> including<00:07:52.420> optin<00:07:52.810> metrics 00:07:53.220 --> 00:07:53.230 align:start position:0% working on including optin metrics 00:07:53.230 --> 00:07:55.500 align:start position:0% working on including optin metrics contract<00:07:53.980> account<00:07:54.250> support<00:07:54.430> late<00:07:55.300> client 00:07:55.500 --> 00:07:55.510 align:start position:0% contract account support late client 00:07:55.510 --> 00:07:57.390 align:start position:0% contract account support late client developments<00:07:56.290> multi<00:07:56.890> network<00:07:57.190> integration 00:07:57.390 --> 00:07:57.400 align:start position:0% developments multi network integration 00:07:57.400 --> 00:08:00.620 align:start position:0% developments multi network integration and<00:07:58.030> layer<00:07:58.300> to<00:07:58.570> scaling<00:07:58.840> research<00:07:59.260> plans 00:08:00.620 --> 00:08:00.630 align:start position:0% and layer to scaling research plans 00:08:00.630 --> 00:08:04.080 align:start position:0% and layer to scaling research plans first<00:08:01.630> up<00:08:01.780> is<00:08:01.930> meta<00:08:02.140> metrics<00:08:02.610> meta<00:08:03.610> mask<00:08:03.850> is 00:08:04.080 --> 00:08:04.090 align:start position:0% first up is meta metrics meta mask is 00:08:04.090 --> 00:08:05.970 align:start position:0% first up is meta metrics meta mask is getting<00:08:04.330> smarter<00:08:04.780> we've<00:08:05.470> gotten<00:08:05.800> feedback 00:08:05.970 --> 00:08:05.980 align:start position:0% getting smarter we've gotten feedback 00:08:05.980 --> 00:08:08.130 align:start position:0% getting smarter we've gotten feedback from<00:08:06.250> developers<00:08:07.060> about<00:08:07.090> the<00:08:07.600> pain<00:08:07.780> points 00:08:08.130 --> 00:08:08.140 align:start position:0% from developers about the pain points 00:08:08.140 --> 00:08:10.110 align:start position:0% from developers about the pain points and<00:08:08.200> meta<00:08:08.380> masks<00:08:08.800> onboarding<00:08:09.310> so<00:08:09.760> we<00:08:09.880> know<00:08:10.000> we 00:08:10.110 --> 00:08:10.120 align:start position:0% and meta masks onboarding so we know we 00:08:10.120 --> 00:08:11.940 align:start position:0% and meta masks onboarding so we know we can<00:08:10.150> do<00:08:10.360> better<00:08:10.390> but<00:08:11.260> with<00:08:11.410> over<00:08:11.590> a<00:08:11.710> million 00:08:11.940 --> 00:08:11.950 align:start position:0% can do better but with over a million 00:08:11.950 --> 00:08:14.970 align:start position:0% can do better but with over a million installs<00:08:12.780> how<00:08:13.780> do<00:08:13.840> we<00:08:13.990> cater<00:08:14.230> to<00:08:14.320> users<00:08:14.800> who 00:08:14.970 --> 00:08:14.980 align:start position:0% installs how do we cater to users who 00:08:14.980 --> 00:08:17.460 align:start position:0% installs how do we cater to users who aren't<00:08:15.160> opening<00:08:15.580> github<00:08:15.910> issues<00:08:16.260> how<00:08:17.260> do<00:08:17.320> we 00:08:17.460 --> 00:08:17.470 align:start position:0% aren't opening github issues how do we 00:08:17.470 --> 00:08:19.440 align:start position:0% aren't opening github issues how do we run<00:08:17.860> an<00:08:18.010> operation<00:08:18.400> without<00:08:18.850> overwhelming 00:08:19.440 --> 00:08:19.450 align:start position:0% run an operation without overwhelming 00:08:19.450 --> 00:08:21.210 align:start position:0% run an operation without overwhelming our<00:08:19.600> support<00:08:19.960> team<00:08:20.140> and<00:08:20.380> how<00:08:21.040> do<00:08:21.100> we 00:08:21.210 --> 00:08:21.220 align:start position:0% our support team and how do we 00:08:21.220 --> 00:08:22.980 align:start position:0% our support team and how do we understand<00:08:21.880> our<00:08:22.000> users<00:08:22.120> better<00:08:22.480> while<00:08:22.840> being 00:08:22.980 --> 00:08:22.990 align:start position:0% understand our users better while being 00:08:22.990 --> 00:08:25.650 align:start position:0% understand our users better while being committed<00:08:23.440> to<00:08:23.530> privacy<00:08:24.360> we're<00:08:25.360> building 00:08:25.650 --> 00:08:25.660 align:start position:0% committed to privacy we're building 00:08:25.660 --> 00:08:27.500 align:start position:0% committed to privacy we're building reporting<00:08:26.110> in<00:08:26.290> the<00:08:26.410> UI<00:08:26.560> for<00:08:26.740> user<00:08:27.220> acquisition 00:08:27.500 --> 00:08:27.510 align:start position:0% reporting in the UI for user acquisition 00:08:27.510 --> 00:08:30.030 align:start position:0% reporting in the UI for user acquisition activity<00:08:28.510> and<00:08:28.750> retention<00:08:29.200> which<00:08:29.800> will<00:08:29.950> be 00:08:30.030 --> 00:08:30.040 align:start position:0% activity and retention which will be 00:08:30.040 --> 00:08:34.230 align:start position:0% activity and retention which will be opted<00:08:30.220> in<00:08:30.490> and<00:08:30.760> off<00:08:31.000> by<00:08:31.270> default<00:08:32.940> we<00:08:33.940> will<00:08:33.970> not 00:08:34.230 --> 00:08:34.240 align:start position:0% opted in and off by default we will not 00:08:34.240 --> 00:08:35.219 align:start position:0% opted in and off by default we will not collect<00:08:34.479> any<00:08:34.660> personally<00:08:35.200> identifiable 00:08:35.219 --> 00:08:35.229 align:start position:0% collect any personally identifiable 00:08:35.229 --> 00:08:38.580 align:start position:0% collect any personally identifiable information<00:08:36.510> addresses<00:08:37.510> keys<00:08:37.840> transactions 00:08:38.580 --> 00:08:38.590 align:start position:0% information addresses keys transactions 00:08:38.590 --> 00:08:41.070 align:start position:0% information addresses keys transactions or<00:08:38.800> balances<00:08:39.370> we<00:08:40.330> think<00:08:40.510> this<00:08:40.630> work<00:08:40.840> will<00:08:41.020> help 00:08:41.070 --> 00:08:41.080 align:start position:0% or balances we think this work will help 00:08:41.080 --> 00:08:42.510 align:start position:0% or balances we think this work will help us<00:08:41.260> build<00:08:41.380> better<00:08:41.590> tools<00:08:41.710> for<00:08:42.130> our<00:08:42.160> users 00:08:42.510 --> 00:08:42.520 align:start position:0% us build better tools for our users 00:08:42.520 --> 00:08:47.700 align:start position:0% us build better tools for our users which<00:08:42.940> is<00:08:42.970> what<00:08:43.210> we<00:08:43.300> love<00:08:43.450> to<00:08:43.510> do<00:08:46.320> next<00:08:47.320> up<00:08:47.560> is 00:08:47.700 --> 00:08:47.710 align:start position:0% which is what we love to do next up is 00:08:47.710 --> 00:08:49.920 align:start position:0% which is what we love to do next up is contract<00:08:48.190> accounts<00:08:48.610> I'm<00:08:48.850> currently<00:08:49.630> working 00:08:49.920 --> 00:08:49.930 align:start position:0% contract accounts I'm currently working 00:08:49.930 --> 00:08:51.930 align:start position:0% contract accounts I'm currently working on<00:08:50.230> providing<00:08:50.770> support<00:08:51.160> for<00:08:51.190> contracts<00:08:51.760> as 00:08:51.930 --> 00:08:51.940 align:start position:0% on providing support for contracts as 00:08:51.940 --> 00:08:53.670 align:start position:0% on providing support for contracts as accounts<00:08:52.300> in<00:08:52.420> meadow<00:08:52.600> mask<00:08:52.840> starting<00:08:53.560> with 00:08:53.670 --> 00:08:53.680 align:start position:0% accounts in meadow mask starting with 00:08:53.680 --> 00:08:54.290 align:start position:0% accounts in meadow mask starting with the<00:08:53.770> No 00:08:54.290 --> 00:08:54.300 align:start position:0% the No 00:08:54.300 --> 00:08:56.600 align:start position:0% the No safe<00:08:54.620> you're<00:08:55.620> probably<00:08:55.860> familiar<00:08:56.160> with<00:08:56.399> the 00:08:56.600 --> 00:08:56.610 align:start position:0% safe you're probably familiar with the 00:08:56.610 --> 00:08:59.030 align:start position:0% safe you're probably familiar with the original<00:08:56.790> gnosis<00:08:57.330> multi-sig<00:08:57.899> the<00:08:58.529> safe<00:08:58.740> is<00:08:58.920> an 00:08:59.030 --> 00:08:59.040 align:start position:0% original gnosis multi-sig the safe is an 00:08:59.040 --> 00:09:00.800 align:start position:0% original gnosis multi-sig the safe is an evolution<00:08:59.550> of<00:08:59.610> that<00:08:59.760> project<00:08:59.970> with<00:09:00.480> cheaper 00:09:00.800 --> 00:09:00.810 align:start position:0% evolution of that project with cheaper 00:09:00.810 --> 00:09:02.900 align:start position:0% evolution of that project with cheaper setup<00:09:01.110> transaction<00:09:01.740> costs<00:09:02.160> and<00:09:02.250> extensible 00:09:02.900 --> 00:09:02.910 align:start position:0% setup transaction costs and extensible 00:09:02.910 --> 00:09:04.759 align:start position:0% setup transaction costs and extensible modules<00:09:03.330> you<00:09:04.019> can<00:09:04.050> learn<00:09:04.260> more<00:09:04.440> about<00:09:04.500> the 00:09:04.759 --> 00:09:04.769 align:start position:0% modules you can learn more about the 00:09:04.769 --> 00:09:07.190 align:start position:0% modules you can learn more about the safe<00:09:04.980> at<00:09:05.760> other<00:09:05.970> talks<00:09:06.360> from<00:09:06.570> the<00:09:06.690> gnosis<00:09:06.899> team 00:09:07.190 --> 00:09:07.200 align:start position:0% safe at other talks from the gnosis team 00:09:07.200 --> 00:09:11.000 align:start position:0% safe at other talks from the gnosis team today<00:09:07.649> and<00:09:07.890> Friday<00:09:08.250> during<00:09:08.640> DEFCON<00:09:10.010> I'm 00:09:11.000 --> 00:09:11.010 align:start position:0% today and Friday during DEFCON I'm 00:09:11.010 --> 00:09:12.530 align:start position:0% today and Friday during DEFCON I'm really<00:09:11.279> excited<00:09:11.550> to<00:09:11.760> be<00:09:11.880> building<00:09:12.180> alongside 00:09:12.530 --> 00:09:12.540 align:start position:0% really excited to be building alongside 00:09:12.540 --> 00:09:14.389 align:start position:0% really excited to be building alongside the<00:09:12.959> next<00:09:13.170> generation<00:09:13.589> of<00:09:13.649> tools<00:09:13.920> which<00:09:14.250> will 00:09:14.389 --> 00:09:14.399 align:start position:0% the next generation of tools which will 00:09:14.399 --> 00:09:16.160 align:start position:0% the next generation of tools which will allow<00:09:14.610> for<00:09:14.670> features<00:09:15.209> such<00:09:15.480> as<00:09:15.810> social 00:09:16.160 --> 00:09:16.170 align:start position:0% allow for features such as social 00:09:16.170 --> 00:09:18.560 align:start position:0% allow for features such as social recovery<00:09:16.410> key<00:09:17.130> allowances<00:09:17.730> state<00:09:18.209> channels 00:09:18.560 --> 00:09:18.570 align:start position:0% recovery key allowances state channels 00:09:18.570 --> 00:09:20.900 align:start position:0% recovery key allowances state channels multi-factor<00:09:19.380> off<00:09:19.680> and<00:09:19.980> batch<00:09:20.130> transactions 00:09:20.900 --> 00:09:20.910 align:start position:0% multi-factor off and batch transactions 00:09:20.910 --> 00:09:23.240 align:start position:0% multi-factor off and batch transactions this<00:09:21.870> is<00:09:22.019> really<00:09:22.260> only<00:09:22.440> the<00:09:22.589> beginning<00:09:22.800> and 00:09:23.240 --> 00:09:23.250 align:start position:0% this is really only the beginning and 00:09:23.250 --> 00:09:24.920 align:start position:0% this is really only the beginning and eventually<00:09:24.000> we're<00:09:24.120> planning<00:09:24.390> on<00:09:24.480> supporting 00:09:24.920 --> 00:09:24.930 align:start position:0% eventually we're planning on supporting 00:09:24.930 --> 00:09:28.430 align:start position:0% eventually we're planning on supporting generic<00:09:25.529> identity<00:09:26.010> accounts<00:09:27.050> with<00:09:28.050> similar 00:09:28.430 --> 00:09:28.440 align:start position:0% generic identity accounts with similar 00:09:28.440 --> 00:09:30.829 align:start position:0% generic identity accounts with similar to<00:09:28.649> the<00:09:28.740> pattern<00:09:28.890> described<00:09:29.459> in<00:09:29.610> the<00:09:29.700> IP<00:09:29.850> 747 00:09:30.829 --> 00:09:30.839 align:start position:0% to the pattern described in the IP 747 00:09:30.839 --> 00:09:37.819 align:start position:0% to the pattern described in the IP 747 that<00:09:30.990> Bobbi<00:09:31.470> mentioned<00:09:35.720> mystic<00:09:36.720> Allah<00:09:36.899> meta 00:09:37.819 --> 00:09:37.829 align:start position:0% that Bobbi mentioned mystic Allah meta 00:09:37.829 --> 00:09:41.030 align:start position:0% that Bobbi mentioned mystic Allah meta mask<00:09:38.100> is<00:09:38.570> decentralizing<00:09:39.570> madam<00:09:40.560> asked<00:09:40.709> Labs 00:09:41.030 --> 00:09:41.040 align:start position:0% mask is decentralizing madam asked Labs 00:09:41.040 --> 00:09:44.930 align:start position:0% mask is decentralizing madam asked Labs is<00:09:41.370> working<00:09:41.850> on<00:09:42.600> a<00:09:43.200> project<00:09:43.560> in<00:09:44.100> our<00:09:44.490> R&D 00:09:44.930 --> 00:09:44.940 align:start position:0% is working on a project in our R&D 00:09:44.940 --> 00:09:47.480 align:start position:0% is working on a project in our R&D department<00:09:45.420> called<00:09:45.630> meta<00:09:45.810> mask<00:09:46.019> labs<00:09:46.320> and<00:09:46.680> the 00:09:47.480 --> 00:09:47.490 align:start position:0% department called meta mask labs and the 00:09:47.490 --> 00:09:50.900 align:start position:0% department called meta mask labs and the project<00:09:47.850> is<00:09:47.910> called<00:09:48.120> Musa<00:09:48.480> kala<00:09:49.459> which<00:09:50.459> is<00:09:50.640> a 00:09:50.900 --> 00:09:50.910 align:start position:0% project is called Musa kala which is a 00:09:50.910 --> 00:09:52.940 align:start position:0% project is called Musa kala which is a native<00:09:51.089> browser<00:09:51.600> p2p<00:09:52.050> light<00:09:52.230> client<00:09:52.649> to 00:09:52.940 --> 00:09:52.950 align:start position:0% native browser p2p light client to 00:09:52.950 --> 00:09:54.410 align:start position:0% native browser p2p light client to decrease<00:09:53.279> our<00:09:53.399> reliance<00:09:53.519> on<00:09:53.910> centralized 00:09:54.410 --> 00:09:54.420 align:start position:0% decrease our reliance on centralized 00:09:54.420 --> 00:09:58.280 align:start position:0% decrease our reliance on centralized infrastructure<00:09:54.959> Frank<00:09:55.950> and<00:09:56.220> dima<00:09:56.490> from<00:09:57.290> metal 00:09:58.280 --> 00:09:58.290 align:start position:0% infrastructure Frank and dima from metal 00:09:58.290 --> 00:10:00.680 align:start position:0% infrastructure Frank and dima from metal mask<00:09:58.470> labs<00:09:58.829> will<00:09:59.640> be<00:09:59.760> presenting<00:10:00.209> mu<00:10:00.329> ste<00:10:00.510> kala 00:10:00.680 --> 00:10:00.690 align:start position:0% mask labs will be presenting mu ste kala 00:10:00.690 --> 00:10:03.199 align:start position:0% mask labs will be presenting mu ste kala on<00:10:00.990> November<00:10:01.350> 2nd<00:10:01.709> at<00:10:01.829> 2:30<00:10:02.310> on<00:10:02.579> the<00:10:02.820> prism 00:10:03.199 --> 00:10:03.209 align:start position:0% on November 2nd at 2:30 on the prism 00:10:03.209 --> 00:10:04.940 align:start position:0% on November 2nd at 2:30 on the prism side<00:10:03.390> stage<00:10:03.720> and<00:10:04.140> we<00:10:04.410> encourage<00:10:04.770> you<00:10:04.800> to 00:10:04.940 --> 00:10:04.950 align:start position:0% side stage and we encourage you to 00:10:04.950 --> 00:10:06.530 align:start position:0% side stage and we encourage you to attend<00:10:05.279> this<00:10:05.399> talk<00:10:05.670> if<00:10:05.880> you're<00:10:06.029> curious<00:10:06.180> to 00:10:06.530 --> 00:10:06.540 align:start position:0% attend this talk if you're curious to 00:10:06.540 --> 00:10:07.880 align:start position:0% attend this talk if you're curious to learn<00:10:06.660> more<00:10:06.870> about<00:10:06.990> their<00:10:07.290> amazing<00:10:07.680> progress 00:10:07.880 --> 00:10:07.890 align:start position:0% learn more about their amazing progress 00:10:07.890 --> 00:10:09.889 align:start position:0% learn more about their amazing progress and<00:10:08.310> what<00:10:08.850> it<00:10:08.940> takes<00:10:09.149> to<00:10:09.329> build<00:10:09.480> a<00:10:09.690> browser 00:10:09.889 --> 00:10:09.899 align:start position:0% and what it takes to build a browser 00:10:09.899 --> 00:10:13.100 align:start position:0% and what it takes to build a browser first<00:10:10.260> light<00:10:10.470> client<00:10:11.570> I've<00:10:12.570> watched<00:10:12.779> her<00:10:12.930> talk 00:10:13.100 --> 00:10:13.110 align:start position:0% first light client I've watched her talk 00:10:13.110 --> 00:10:20.380 align:start position:0% first light client I've watched her talk a<00:10:13.140> few<00:10:13.320> times<00:10:13.560> I<00:10:13.800> promise<00:10:14.160> it's<00:10:14.310> really<00:10:14.579> good 00:10:20.380 --> 00:10:20.390 align:start position:0% 00:10:20.390 --> 00:10:23.050 align:start position:0% next<00:10:21.390> up<00:10:21.630> is<00:10:21.839> multi<00:10:22.230> network<00:10:22.560> integration 00:10:23.050 --> 00:10:23.060 align:start position:0% next up is multi network integration 00:10:23.060 --> 00:10:26.600 align:start position:0% next up is multi network integration madam<00:10:24.060> asked<00:10:24.209> is<00:10:24.450> spreading<00:10:25.490> thanks<00:10:26.490> to 00:10:26.600 --> 00:10:26.610 align:start position:0% madam asked is spreading thanks to 00:10:26.610 --> 00:10:29.090 align:start position:0% madam asked is spreading thanks to community<00:10:26.790> input<00:10:27.240> meta<00:10:28.079> mask<00:10:28.320> is<00:10:28.620> moving<00:10:28.950> to 00:10:29.090 --> 00:10:29.100 align:start position:0% community input meta mask is moving to 00:10:29.100 --> 00:10:30.769 align:start position:0% community input meta mask is moving to support<00:10:29.399> multiple<00:10:29.579> eath<00:10:30.029> compatible<00:10:30.600> block 00:10:30.769 --> 00:10:30.779 align:start position:0% support multiple eath compatible block 00:10:30.779 --> 00:10:32.810 align:start position:0% support multiple eath compatible block chains<00:10:31.079> and<00:10:31.350> this<00:10:31.890> is<00:10:32.070> only<00:10:32.190> the<00:10:32.399> beginning 00:10:32.810 --> 00:10:32.820 align:start position:0% chains and this is only the beginning 00:10:32.820 --> 00:10:35.780 align:start position:0% chains and this is only the beginning our<00:10:33.450> end<00:10:33.690> goal<00:10:33.810> is<00:10:34.170> for<00:10:34.350> allow<00:10:34.589> madam<00:10:34.920> asked<00:10:35.100> to 00:10:35.780 --> 00:10:35.790 align:start position:0% our end goal is for allow madam asked to 00:10:35.790 --> 00:10:38.000 align:start position:0% our end goal is for allow madam asked to allow<00:10:36.029> users<00:10:36.329> to<00:10:36.510> simultaneously<00:10:37.470> connect<00:10:37.890> to 00:10:38.000 --> 00:10:38.010 align:start position:0% allow users to simultaneously connect to 00:10:38.010 --> 00:10:40.430 align:start position:0% allow users to simultaneously connect to their<00:10:38.130> own<00:10:38.279> sets<00:10:38.579> of<00:10:38.699> networks<00:10:39.060> and<00:10:39.540> to<00:10:40.260> allow 00:10:40.430 --> 00:10:40.440 align:start position:0% their own sets of networks and to allow 00:10:40.440 --> 00:10:42.290 align:start position:0% their own sets of networks and to allow developers<00:10:40.680> to<00:10:41.070> suggest<00:10:41.640> new<00:10:41.820> networks<00:10:42.149> to 00:10:42.290 --> 00:10:42.300 align:start position:0% developers to suggest new networks to 00:10:42.300 --> 00:10:47.420 align:start position:0% developers to suggest new networks to the<00:10:42.420> user<00:10:44.690> and<00:10:45.690> next<00:10:46.380> up<00:10:46.529> we<00:10:46.740> have<00:10:46.770> our<00:10:47.190> layer 00:10:47.420 --> 00:10:47.430 align:start position:0% the user and next up we have our layer 00:10:47.430 --> 00:10:50.660 align:start position:0% the user and next up we have our layer to<00:10:47.760> scaling<00:10:48.300> research<00:10:48.810> plans<00:10:49.140> meta<00:10:50.100> mask<00:10:50.370> is 00:10:50.660 --> 00:10:50.670 align:start position:0% to scaling research plans meta mask is 00:10:50.670 --> 00:10:54.079 align:start position:0% to scaling research plans meta mask is scaling<00:10:51.620> doctor<00:10:52.620> dr.<00:10:53.220> Vincent<00:10:53.579> Eli<00:10:53.850> has 00:10:54.079 --> 00:10:54.089 align:start position:0% scaling doctor dr. Vincent Eli has 00:10:54.089 --> 00:10:55.639 align:start position:0% scaling doctor dr. Vincent Eli has recently<00:10:54.300> begun<00:10:54.779> work<00:10:55.019> on<00:10:55.230> a<00:10:55.290> research 00:10:55.639 --> 00:10:55.649 align:start position:0% recently begun work on a research 00:10:55.649 --> 00:10:57.920 align:start position:0% recently begun work on a research project<00:10:55.890> in<00:10:56.250> meadow<00:10:56.459> mask<00:10:56.730> to<00:10:57.390> assess<00:10:57.690> how<00:10:57.870> to 00:10:57.920 --> 00:10:57.930 align:start position:0% project in meadow mask to assess how to 00:10:57.930 --> 00:10:59.900 align:start position:0% project in meadow mask to assess how to best<00:10:58.170> support<00:10:58.350> and<00:10:58.769> integrate<00:10:59.220> various<00:10:59.640> layer 00:10:59.900 --> 00:10:59.910 align:start position:0% best support and integrate various layer 00:10:59.910 --> 00:11:02.180 align:start position:0% best support and integrate various layer 2<00:11:00.120> apps<00:11:00.329> and<00:11:00.600> protocols<00:11:01.019> the<00:11:01.680> aim<00:11:01.829> is<00:11:01.949> to<00:11:01.980> be 00:11:02.180 --> 00:11:02.190 align:start position:0% 2 apps and protocols the aim is to be 00:11:02.190 --> 00:11:04.010 align:start position:0% 2 apps and protocols the aim is to be agnostic<00:11:02.459> to<00:11:02.820> implementation<00:11:03.329> while 00:11:04.010 --> 00:11:04.020 align:start position:0% agnostic to implementation while 00:11:04.020 --> 00:11:05.510 align:start position:0% agnostic to implementation while providing<00:11:04.320> a<00:11:04.560> complete<00:11:04.980> and<00:11:05.190> secure 00:11:05.510 --> 00:11:05.520 align:start position:0% providing a complete and secure 00:11:05.520 --> 00:11:06.700 align:start position:0% providing a complete and secure integration<00:11:06.060> into<00:11:06.360> the<00:11:06.449> met 00:11:06.700 --> 00:11:06.710 align:start position:0% integration into the met 00:11:06.710 --> 00:11:09.550 align:start position:0% integration into the met user<00:11:07.130> experience<00:11:07.940> the<00:11:08.540> project<00:11:08.960> is<00:11:09.080> exploring 00:11:09.550 --> 00:11:09.560 align:start position:0% user experience the project is exploring 00:11:09.560 --> 00:11:13.150 align:start position:0% user experience the project is exploring two<00:11:09.800> main<00:11:09.980> paths<00:11:10.960> first<00:11:11.960> full<00:11:12.740> integration 00:11:13.150 --> 00:11:13.160 align:start position:0% two main paths first full integration 00:11:13.160 --> 00:11:15.010 align:start position:0% two main paths first full integration and<00:11:13.580> operation<00:11:14.060> of<00:11:14.120> payment<00:11:14.540> channels<00:11:14.840> for 00:11:15.010 --> 00:11:15.020 align:start position:0% and operation of payment channels for 00:11:15.020 --> 00:11:17.560 align:start position:0% and operation of payment channels for instantly<00:11:15.470> are<00:11:15.560> see<00:11:15.740> 20<00:11:16.040> payments<00:11:16.460> and<00:11:16.640> second 00:11:17.560 --> 00:11:17.570 align:start position:0% instantly are see 20 payments and second 00:11:17.570 --> 00:11:19.960 align:start position:0% instantly are see 20 payments and second a<00:11:17.750> more<00:11:18.440> general<00:11:18.830> specification<00:11:19.580> that<00:11:19.820> will 00:11:19.960 --> 00:11:19.970 align:start position:0% a more general specification that will 00:11:19.970 --> 00:11:21.970 align:start position:0% a more general specification that will allow<00:11:20.120> devs<00:11:20.450> to<00:11:20.720> create<00:11:20.990> layer<00:11:21.260> 2<00:11:21.500> apps<00:11:21.710> that 00:11:21.970 --> 00:11:21.980 align:start position:0% allow devs to create layer 2 apps that 00:11:21.980 --> 00:11:24.640 align:start position:0% allow devs to create layer 2 apps that can<00:11:22.040> be<00:11:22.160> integrated<00:11:22.400> into<00:11:22.850> Madame<00:11:23.180> masque<00:11:23.650> so 00:11:24.640 --> 00:11:24.650 align:start position:0% can be integrated into Madame masque so 00:11:24.650 --> 00:11:26.560 align:start position:0% can be integrated into Madame masque so thank<00:11:25.040> you<00:11:25.130> for<00:11:25.250> having<00:11:25.520> me<00:11:25.670> and<00:11:25.940> now<00:11:26.300> here's 00:11:26.560 --> 00:11:26.570 align:start position:0% thank you for having me and now here's 00:11:26.570 --> 00:11:43.540 align:start position:0% thank you for having me and now here's Bruno<00:11:26.930> with<00:11:27.530> one<00:11:27.710> more<00:11:28.180> thing<00:11:42.070> hello<00:11:43.070> everyone 00:11:43.540 --> 00:11:43.550 align:start position:0% Bruno with one more thing hello everyone 00:11:43.550 --> 00:11:45.880 align:start position:0% Bruno with one more thing hello everyone my<00:11:43.730> name<00:11:43.850> is<00:11:43.880> Bruno<00:11:44.380> I'm<00:11:45.380> also<00:11:45.590> a<00:11:45.740> yellow 00:11:45.880 --> 00:11:45.890 align:start position:0% my name is Bruno I'm also a yellow 00:11:45.890 --> 00:11:48.700 align:start position:0% my name is Bruno I'm also a yellow parameter<00:11:46.550> mask<00:11:46.760> and<00:11:47.600> I'm<00:11:48.110> very<00:11:48.200> excited<00:11:48.650> to 00:11:48.700 --> 00:11:48.710 align:start position:0% parameter mask and I'm very excited to 00:11:48.710 --> 00:11:49.270 align:start position:0% parameter mask and I'm very excited to be<00:11:48.800> here 00:11:49.270 --> 00:11:49.280 align:start position:0% be here 00:11:49.280 --> 00:11:51.100 align:start position:0% be here not<00:11:49.790> just<00:11:50.030> because<00:11:50.180> that<00:11:50.780> gun<00:11:50.960> which<00:11:51.080> is 00:11:51.100 --> 00:11:51.110 align:start position:0% not just because that gun which is 00:11:51.110 --> 00:11:52.960 align:start position:0% not just because that gun which is awesome<00:11:51.560> but<00:11:51.830> also<00:11:51.890> because<00:11:52.400> I<00:11:52.580> have<00:11:52.730> very 00:11:52.960 --> 00:11:52.970 align:start position:0% awesome but also because I have very 00:11:52.970 --> 00:11:56.260 align:start position:0% awesome but also because I have very exciting<00:11:53.240> news<00:11:53.450> for<00:11:53.780> you<00:11:54.700> first<00:11:55.700> of<00:11:55.790> all<00:11:55.910> let 00:11:56.260 --> 00:11:56.270 align:start position:0% exciting news for you first of all let 00:11:56.270 --> 00:11:58.360 align:start position:0% exciting news for you first of all let me<00:11:56.330> give<00:11:56.480> you<00:11:56.540> guys<00:11:56.570> some<00:11:56.750> context<00:11:57.350> as<00:11:58.160> you 00:11:58.360 --> 00:11:58.370 align:start position:0% me give you guys some context as you 00:11:58.370 --> 00:12:00.130 align:start position:0% me give you guys some context as you know<00:11:58.490> madam<00:11:58.940> us<00:11:59.060> is<00:11:59.210> one<00:11:59.360> of<00:11:59.480> the<00:11:59.600> oldest<00:11:59.960> and 00:12:00.130 --> 00:12:00.140 align:start position:0% know madam us is one of the oldest and 00:12:00.140 --> 00:12:01.540 align:start position:0% know madam us is one of the oldest and most<00:12:00.200> popular<00:12:00.470> dream<00:12:01.010> wallets 00:12:01.540 --> 00:12:01.550 align:start position:0% most popular dream wallets 00:12:01.550 --> 00:12:05.230 align:start position:0% most popular dream wallets I<00:12:01.580> was<00:12:02.210> launched<00:12:02.480> in<00:12:02.780> 2015<00:12:03.640> created<00:12:04.640> by<00:12:04.670> Aaron 00:12:05.230 --> 00:12:05.240 align:start position:0% I was launched in 2015 created by Aaron 00:12:05.240 --> 00:12:08.170 align:start position:0% I was launched in 2015 created by Aaron Davis<00:12:05.600> also<00:12:06.020> known<00:12:06.260> as<00:12:06.500> novice<00:12:07.190> along<00:12:08.000> with 00:12:08.170 --> 00:12:08.180 align:start position:0% Davis also known as novice along with 00:12:08.180 --> 00:12:11.580 align:start position:0% Davis also known as novice along with Dan<00:12:08.480> Finley<00:12:08.900> and<00:12:09.170> we<00:12:09.860> passed<00:12:10.130> 1<00:12:10.460> million<00:12:10.700> users 00:12:11.580 --> 00:12:11.590 align:start position:0% Dan Finley and we passed 1 million users 00:12:11.590 --> 00:12:14.350 align:start position:0% Dan Finley and we passed 1 million users since<00:12:12.590> then<00:12:12.800> we<00:12:12.950> learn<00:12:13.160> a<00:12:13.190> lot<00:12:13.370> about<00:12:13.880> what<00:12:14.240> it 00:12:14.350 --> 00:12:14.360 align:start position:0% since then we learn a lot about what it 00:12:14.360 --> 00:12:17.350 align:start position:0% since then we learn a lot about what it takes<00:12:14.630> to<00:12:14.900> create<00:12:15.650> a<00:12:15.800> digital<00:12:16.370> wallet<00:12:16.550> in<00:12:16.970> this 00:12:17.350 --> 00:12:17.360 align:start position:0% takes to create a digital wallet in this 00:12:17.360 --> 00:12:20.680 align:start position:0% takes to create a digital wallet in this fast<00:12:17.870> changing<00:12:18.520> space<00:12:19.520> where<00:12:19.940> you<00:12:20.450> know<00:12:20.540> it's 00:12:20.680 --> 00:12:20.690 align:start position:0% fast changing space where you know it's 00:12:20.690 --> 00:12:23.260 align:start position:0% fast changing space where you know it's constantly<00:12:21.140> evolving<00:12:21.770> but<00:12:22.550> there<00:12:22.880> is<00:12:22.970> one 00:12:23.260 --> 00:12:23.270 align:start position:0% constantly evolving but there is one 00:12:23.270 --> 00:12:25.930 align:start position:0% constantly evolving but there is one thing<00:12:23.480> that<00:12:23.510> the<00:12:23.750> enchain<00:12:24.110> and<00:12:24.530> it<00:12:25.310> still<00:12:25.670> is 00:12:25.930 --> 00:12:25.940 align:start position:0% thing that the enchain and it still is 00:12:25.940 --> 00:12:28.210 align:start position:0% thing that the enchain and it still is we<00:12:26.240> are<00:12:26.330> still<00:12:26.540> a<00:12:26.570> browser<00:12:26.930> extension<00:12:27.110> so<00:12:27.950> that 00:12:28.210 --> 00:12:28.220 align:start position:0% we are still a browser extension so that 00:12:28.220 --> 00:12:31.890 align:start position:0% we are still a browser extension so that means<00:12:28.520> that<00:12:28.670> we<00:12:28.760> are<00:12:28.820> somehow<00:12:30.580> you<00:12:31.580> know 00:12:31.890 --> 00:12:31.900 align:start position:0% means that we are somehow you know 00:12:31.900 --> 00:12:35.830 align:start position:0% means that we are somehow you know restricted<00:12:32.900> by<00:12:33.020> the<00:12:33.080> browser<00:12:33.950> api's<00:12:34.490> so<00:12:35.390> we 00:12:35.830 --> 00:12:35.840 align:start position:0% restricted by the browser api's so we 00:12:35.840 --> 00:12:38.320 align:start position:0% restricted by the browser api's so we start<00:12:36.020> thinking<00:12:36.170> about<00:12:36.290> our<00:12:36.560> future<00:12:36.950> and<00:12:37.400> the 00:12:38.320 --> 00:12:38.330 align:start position:0% start thinking about our future and the 00:12:38.330 --> 00:12:39.910 align:start position:0% start thinking about our future and the first<00:12:38.510> question<00:12:38.780> was<00:12:38.900> like<00:12:38.930> do<00:12:39.470> we<00:12:39.590> want<00:12:39.770> to<00:12:39.860> be 00:12:39.910 --> 00:12:39.920 align:start position:0% first question was like do we want to be 00:12:39.920 --> 00:12:43.600 align:start position:0% first question was like do we want to be just<00:12:40.160> a<00:12:40.280> wallet<00:12:40.510> so<00:12:41.510> we<00:12:42.320> say<00:12:42.530> that<00:12:42.590> that's<00:12:43.370> not 00:12:43.600 --> 00:12:43.610 align:start position:0% just a wallet so we say that that's not 00:12:43.610 --> 00:12:45.360 align:start position:0% just a wallet so we say that that's not the<00:12:44.000> right<00:12:44.120> thing<00:12:44.180> I<00:12:44.570> mean<00:12:44.750> we<00:12:44.930> want<00:12:45.170> to<00:12:45.260> be 00:12:45.360 --> 00:12:45.370 align:start position:0% the right thing I mean we want to be 00:12:45.370 --> 00:12:48.550 align:start position:0% the right thing I mean we want to be bridge<00:12:46.370> to<00:12:46.610> the<00:12:46.700> decentralized<00:12:47.330> way<00:12:47.420> so<00:12:48.260> this 00:12:48.550 --> 00:12:48.560 align:start position:0% bridge to the decentralized way so this 00:12:48.560 --> 00:12:51.460 align:start position:0% bridge to the decentralized way so this is<00:12:48.620> why<00:12:48.920> we<00:12:49.250> decided<00:12:49.640> to<00:12:49.850> create<00:12:50.210> our<00:12:50.630> mobile 00:12:51.460 --> 00:12:51.470 align:start position:0% is why we decided to create our mobile 00:12:51.470 --> 00:12:57.199 align:start position:0% is why we decided to create our mobile apps 00:12:57.199 --> 00:12:57.209 align:start position:0% 00:12:57.209 --> 00:13:01.230 align:start position:0% so<00:12:58.209> let's<00:12:58.630> talk<00:12:58.720> about<00:12:58.779> the<00:12:58.990> challenges<00:13:00.240> first 00:13:01.230 --> 00:13:01.240 align:start position:0% so let's talk about the challenges first 00:13:01.240 --> 00:13:03.180 align:start position:0% so let's talk about the challenges first of<00:13:01.360> all<00:13:01.480> we<00:13:01.750> are<00:13:01.959> aware<00:13:02.259> that<00:13:02.529> we're<00:13:02.860> late<00:13:03.040> to 00:13:03.180 --> 00:13:03.190 align:start position:0% of all we are aware that we're late to 00:13:03.190 --> 00:13:05.610 align:start position:0% of all we are aware that we're late to the<00:13:03.279> game<00:13:03.449> there<00:13:04.449> are<00:13:04.480> other<00:13:04.720> more<00:13:05.110> bullets<00:13:05.560> in 00:13:05.610 --> 00:13:05.620 align:start position:0% the game there are other more bullets in 00:13:05.620 --> 00:13:08.340 align:start position:0% the game there are other more bullets in this<00:13:05.769> pace<00:13:06.329> that<00:13:07.329> there<00:13:07.870> are<00:13:07.959> somehow<00:13:08.199> similar 00:13:08.340 --> 00:13:08.350 align:start position:0% this pace that there are somehow similar 00:13:08.350 --> 00:13:11.160 align:start position:0% this pace that there are somehow similar there<00:13:09.100> are<00:13:09.160> pretty<00:13:09.310> cool<00:13:09.459> too<00:13:09.519> similar<00:13:10.170> we 00:13:11.160 --> 00:13:11.170 align:start position:0% there are pretty cool too similar we 00:13:11.170 --> 00:13:14.249 align:start position:0% there are pretty cool too similar we also<00:13:11.319> know<00:13:11.560> that<00:13:11.589> mobile<00:13:12.430> sorry<00:13:13.329> onboarding 00:13:14.249 --> 00:13:14.259 align:start position:0% also know that mobile sorry onboarding 00:13:14.259 --> 00:13:16.860 align:start position:0% also know that mobile sorry onboarding is<00:13:14.759> still<00:13:15.759> a<00:13:15.790> problem<00:13:16.060> there<00:13:16.360> is<00:13:16.449> a<00:13:16.480> lot<00:13:16.720> of 00:13:16.860 --> 00:13:16.870 align:start position:0% is still a problem there is a lot of 00:13:16.870 --> 00:13:19.340 align:start position:0% is still a problem there is a lot of friction<00:13:17.380> there<00:13:17.680> especially<00:13:18.370> for<00:13:18.519> new<00:13:18.699> users 00:13:19.340 --> 00:13:19.350 align:start position:0% friction there especially for new users 00:13:19.350 --> 00:13:22.980 align:start position:0% friction there especially for new users we<00:13:20.350> know<00:13:20.769> that<00:13:21.190> we<00:13:22.000> because<00:13:22.420> we<00:13:22.540> want<00:13:22.750> to<00:13:22.810> help 00:13:22.980 --> 00:13:22.990 align:start position:0% we know that we because we want to help 00:13:22.990 --> 00:13:25.590 align:start position:0% we know that we because we want to help the<00:13:23.199> space<00:13:24.069> grow<00:13:24.370> we<00:13:24.819> need<00:13:25.060> to<00:13:25.209> learn<00:13:25.360> new 00:13:25.590 --> 00:13:25.600 align:start position:0% the space grow we need to learn new 00:13:25.600 --> 00:13:28.499 align:start position:0% the space grow we need to learn new users<00:13:25.959> explore<00:13:26.560> the<00:13:27.370> ecosystem<00:13:28.149> of<00:13:28.240> the<00:13:28.300> apps 00:13:28.499 --> 00:13:28.509 align:start position:0% users explore the ecosystem of the apps 00:13:28.509 --> 00:13:30.660 align:start position:0% users explore the ecosystem of the apps but<00:13:29.319> at<00:13:29.410> the<00:13:29.470> same<00:13:29.529> time<00:13:29.740> we<00:13:29.920> have<00:13:30.069> like<00:13:30.279> a<00:13:30.310> big 00:13:30.660 --> 00:13:30.670 align:start position:0% but at the same time we have like a big 00:13:30.670 --> 00:13:32.519 align:start position:0% but at the same time we have like a big user<00:13:30.850> base<00:13:31.000> so<00:13:31.389> we<00:13:31.690> need<00:13:31.839> to<00:13:31.990> make<00:13:32.170> sure<00:13:32.350> that 00:13:32.519 --> 00:13:32.529 align:start position:0% user base so we need to make sure that 00:13:32.529 --> 00:13:34.889 align:start position:0% user base so we need to make sure that there<00:13:32.980> is<00:13:33.100> a<00:13:33.430> an<00:13:33.759> easy<00:13:33.850> onboarding<00:13:34.509> process 00:13:34.889 --> 00:13:34.899 align:start position:0% there is a an easy onboarding process 00:13:34.899 --> 00:13:39.420 align:start position:0% there is a an easy onboarding process for<00:13:35.079> the<00:13:35.170> for<00:13:35.949> you<00:13:36.040> guys<00:13:36.329> so<00:13:38.130> when<00:13:39.130> I<00:13:39.160> said<00:13:39.399> that 00:13:39.420 --> 00:13:39.430 align:start position:0% for the for you guys so when I said that 00:13:39.430 --> 00:13:41.910 align:start position:0% for the for you guys so when I said that there<00:13:39.759> is<00:13:39.880> you<00:13:40.779> know<00:13:40.810> a<00:13:40.930> lot<00:13:41.259> of<00:13:41.380> problem<00:13:41.709> with 00:13:41.910 --> 00:13:41.920 align:start position:0% there is you know a lot of problem with 00:13:41.920 --> 00:13:44.759 align:start position:0% there is you know a lot of problem with UX<00:13:42.399> friction<00:13:42.880> just<00:13:43.480> imagine<00:13:44.050> your<00:13:44.290> ankle 00:13:44.759 --> 00:13:44.769 align:start position:0% UX friction just imagine your ankle 00:13:44.769 --> 00:13:46.439 align:start position:0% UX friction just imagine your ankle health<00:13:45.160> reading<00:13:45.699> any<00:13:45.970> of<00:13:46.060> this 00:13:46.439 --> 00:13:46.449 align:start position:0% health reading any of this 00:13:46.449 --> 00:13:50.009 align:start position:0% health reading any of this here's<00:13:47.290> your<00:13:47.500> 12<00:13:47.829> verse<00:13:48.069> mnemonic<00:13:49.019> social 00:13:50.009 --> 00:13:50.019 align:start position:0% here's your 12 verse mnemonic social 00:13:50.019 --> 00:13:53.160 align:start position:0% here's your 12 verse mnemonic social problem<00:13:50.529> amazing<00:13:51.190> can<00:13:51.459> fall<00:13:51.910> supreme<00:13:52.509> enemy 00:13:53.160 --> 00:13:53.170 align:start position:0% problem amazing can fall supreme enemy 00:13:53.170 --> 00:13:56.879 align:start position:0% problem amazing can fall supreme enemy paper<00:13:53.500> amateur<00:13:54.220> picture<00:13:54.759> a<00:13:54.940> sister<00:13:55.630> wink<00:13:56.019> you 00:13:56.879 --> 00:13:56.889 align:start position:0% paper amateur picture a sister wink you 00:13:56.889 --> 00:13:58.800 align:start position:0% paper amateur picture a sister wink you need<00:13:57.069> to<00:13:57.279> back<00:13:57.459> up<00:13:57.670> your<00:13:57.819> seal<00:13:58.060> phrase<00:13:58.329> make 00:13:58.800 --> 00:13:58.810 align:start position:0% need to back up your seal phrase make 00:13:58.810 --> 00:13:59.999 align:start position:0% need to back up your seal phrase make sure<00:13:59.019> you<00:13:59.259> know<00:13:59.319> you<00:13:59.620> don't<00:13:59.800> lose<00:13:59.980> your 00:13:59.999 --> 00:14:00.009 align:start position:0% sure you know you don't lose your 00:14:00.009 --> 00:14:02.970 align:start position:0% sure you know you don't lose your private<00:14:00.610> key<00:14:00.790> here<00:14:01.509> is<00:14:01.750> your<00:14:01.959> pride<00:14:02.259> poly<00:14:02.649> key 00:14:02.970 --> 00:14:02.980 align:start position:0% private key here is your pride poly key 00:14:02.980 --> 00:14:06.660 align:start position:0% private key here is your pride poly key like<00:14:03.790> what<00:14:04.149> this<00:14:05.139> is<00:14:05.319> bad<00:14:05.620> and<00:14:05.980> we<00:14:06.250> gotta<00:14:06.430> fix 00:14:06.660 --> 00:14:06.670 align:start position:0% like what this is bad and we gotta fix 00:14:06.670 --> 00:14:07.249 align:start position:0% like what this is bad and we gotta fix it 00:14:07.249 --> 00:14:07.259 align:start position:0% it 00:14:07.259 --> 00:14:11.639 align:start position:0% it so<00:14:08.910> this<00:14:09.910> is<00:14:10.029> where<00:14:10.209> our<00:14:10.480> UX<00:14:10.959> research<00:14:11.410> team 00:14:11.639 --> 00:14:11.649 align:start position:0% so this is where our UX research team 00:14:11.649 --> 00:14:16.259 align:start position:0% so this is where our UX research team came<00:14:12.160> to<00:14:12.339> rescue<00:14:13.470> our<00:14:14.519> product<00:14:15.519> liberal 00:14:16.259 --> 00:14:16.269 align:start position:0% came to rescue our product liberal 00:14:16.269 --> 00:14:17.879 align:start position:0% came to rescue our product liberal designer<00:14:16.569> Christian<00:14:16.959> Sharia<00:14:17.139> along<00:14:17.709> with 00:14:17.879 --> 00:14:17.889 align:start position:0% designer Christian Sharia along with 00:14:17.889 --> 00:14:19.679 align:start position:0% designer Christian Sharia along with Melissa<00:14:18.040> short<00:14:18.459> they<00:14:19.029> have<00:14:19.209> been<00:14:19.329> working 00:14:19.679 --> 00:14:19.689 align:start position:0% Melissa short they have been working 00:14:19.689 --> 00:14:21.319 align:start position:0% Melissa short they have been working really<00:14:19.870> hard<00:14:19.959> over<00:14:20.319> the<00:14:20.470> past<00:14:20.680> few<00:14:20.800> months 00:14:21.319 --> 00:14:21.329 align:start position:0% really hard over the past few months 00:14:21.329 --> 00:14:23.999 align:start position:0% really hard over the past few months talking<00:14:22.329> to<00:14:22.449> users<00:14:22.839> gathering<00:14:23.319> feedback<00:14:23.500> and 00:14:23.999 --> 00:14:24.009 align:start position:0% talking to users gathering feedback and 00:14:24.009 --> 00:14:27.090 align:start position:0% talking to users gathering feedback and trying<00:14:24.790> different<00:14:25.060> prototypes<00:14:25.959> to<00:14:26.860> see<00:14:27.009> how 00:14:27.090 --> 00:14:27.100 align:start position:0% trying different prototypes to see how 00:14:27.100 --> 00:14:30.179 align:start position:0% trying different prototypes to see how they<00:14:27.250> feel<00:14:27.519> and<00:14:27.850> we<00:14:28.839> finally<00:14:29.259> end<00:14:29.410> up<00:14:29.620> finding 00:14:30.179 --> 00:14:30.189 align:start position:0% they feel and we finally end up finding 00:14:30.189 --> 00:14:33.720 align:start position:0% they feel and we finally end up finding a<00:14:30.550> flow<00:14:31.329> that<00:14:31.779> works<00:14:32.319> pretty<00:14:32.709> good<00:14:32.829> our<00:14:33.310> users 00:14:33.720 --> 00:14:33.730 align:start position:0% a flow that works pretty good our users 00:14:33.730 --> 00:14:35.550 align:start position:0% a flow that works pretty good our users like<00:14:33.880> it<00:14:34.060> and<00:14:34.209> we<00:14:34.300> like<00:14:34.420> it<00:14:34.569> too<00:14:34.720> so<00:14:34.930> we<00:14:35.439> are 00:14:35.550 --> 00:14:35.560 align:start position:0% like it and we like it too so we are 00:14:35.560 --> 00:14:37.679 align:start position:0% like it and we like it too so we are very<00:14:35.769> happy<00:14:35.949> about<00:14:36.130> that<00:14:36.310> and<00:14:36.639> let<00:14:37.420> me<00:14:37.449> show 00:14:37.679 --> 00:14:37.689 align:start position:0% very happy about that and let me show 00:14:37.689 --> 00:14:40.949 align:start position:0% very happy about that and let me show you<00:14:37.750> how<00:14:38.560> it<00:14:38.709> looks<00:14:39.120> so<00:14:40.120> if<00:14:40.420> you<00:14:40.569> see<00:14:40.750> on<00:14:40.870> the 00:14:40.949 --> 00:14:40.959 align:start position:0% you how it looks so if you see on the 00:14:40.959 --> 00:14:43.590 align:start position:0% you how it looks so if you see on the first<00:14:41.170> screen<00:14:41.350> that's<00:14:42.029> like<00:14:43.029> our<00:14:43.240> home<00:14:43.449> screen 00:14:43.590 --> 00:14:43.600 align:start position:0% first screen that's like our home screen 00:14:43.600 --> 00:14:45.689 align:start position:0% first screen that's like our home screen for<00:14:43.899> the<00:14:44.019> app<00:14:44.110> and<00:14:44.319> we<00:14:44.949> have<00:14:45.100> two<00:14:45.220> options<00:14:45.250> the 00:14:45.689 --> 00:14:45.699 align:start position:0% for the app and we have two options the 00:14:45.699 --> 00:14:47.160 align:start position:0% for the app and we have two options the first<00:14:45.730> one<00:14:45.939> is<00:14:46.209> to<00:14:46.300> start<00:14:46.480> flowing<00:14:46.810> now<00:14:46.930> which 00:14:47.160 --> 00:14:47.170 align:start position:0% first one is to start flowing now which 00:14:47.170 --> 00:14:49.620 align:start position:0% first one is to start flowing now which is<00:14:47.319> what<00:14:47.529> a<00:14:47.740> new<00:14:48.189> user<00:14:48.459> should<00:14:48.699> use<00:14:49.000> and<00:14:49.420> then 00:14:49.620 --> 00:14:49.630 align:start position:0% is what a new user should use and then 00:14:49.630 --> 00:14:52.019 align:start position:0% is what a new user should use and then importer<00:14:49.990> wallet<00:14:50.259> for<00:14:50.410> existing<00:14:50.769> users<00:14:51.069> there 00:14:52.019 --> 00:14:52.029 align:start position:0% importer wallet for existing users there 00:14:52.029 --> 00:14:53.220 align:start position:0% importer wallet for existing users there is<00:14:52.120> only<00:14:52.329> one<00:14:52.569> thing<00:14:52.750> that<00:14:52.810> needs<00:14:53.139> to<00:14:53.170> happen 00:14:53.220 --> 00:14:53.230 align:start position:0% is only one thing that needs to happen 00:14:53.230 --> 00:14:55.230 align:start position:0% is only one thing that needs to happen for<00:14:53.649> new<00:14:53.769> users<00:14:54.100> they<00:14:54.370> need<00:14:54.550> to<00:14:54.639> tap<00:14:54.850> that<00:14:55.029> and 00:14:55.230 --> 00:14:55.240 align:start position:0% for new users they need to tap that and 00:14:55.240 --> 00:14:56.730 align:start position:0% for new users they need to tap that and then<00:14:55.509> they<00:14:55.779> should<00:14:55.930> be<00:14:56.019> able<00:14:56.110> to<00:14:56.230> access<00:14:56.470> the 00:14:56.730 --> 00:14:56.740 align:start position:0% then they should be able to access the 00:14:56.740 --> 00:14:58.860 align:start position:0% then they should be able to access the entire<00:14:57.040> all<00:14:57.880> the<00:14:58.029> updates<00:14:58.569> that<00:14:58.779> are 00:14:58.860 --> 00:14:58.870 align:start position:0% entire all the updates that are 00:14:58.870 --> 00:15:01.170 align:start position:0% entire all the updates that are available<00:14:59.079> there<00:14:59.470> and<00:14:59.709> then<00:15:00.519> after<00:15:00.819> that<00:15:00.939> they 00:15:01.170 --> 00:15:01.180 align:start position:0% available there and then after that they 00:15:01.180 --> 00:15:03.150 align:start position:0% available there and then after that they should<00:15:01.360> be<00:15:01.449> able<00:15:01.540> to<00:15:01.870> start<00:15:02.380> using<00:15:02.529> it<00:15:02.800> out<00:15:02.949> and 00:15:03.150 --> 00:15:03.160 align:start position:0% should be able to start using it out and 00:15:03.160 --> 00:15:05.220 align:start position:0% should be able to start using it out and that's<00:15:03.490> it<00:15:03.699> so<00:15:04.269> we're<00:15:04.510> going<00:15:04.630> to<00:15:04.689> handle<00:15:05.050> all 00:15:05.220 --> 00:15:05.230 align:start position:0% that's it so we're going to handle all 00:15:05.230 --> 00:15:06.639 align:start position:0% that's it so we're going to handle all the<00:15:05.350> creation<00:15:05.860> of<00:15:06.010> the 00:15:06.639 --> 00:15:06.649 align:start position:0% the creation of the 00:15:06.649 --> 00:15:08.259 align:start position:0% the creation of the accounts<00:15:07.100> and<00:15:07.279> all<00:15:07.519> their<00:15:07.730> heavy<00:15:07.910> stuff<00:15:08.119> in 00:15:08.259 --> 00:15:08.269 align:start position:0% accounts and all their heavy stuff in 00:15:08.269 --> 00:15:10.299 align:start position:0% accounts and all their heavy stuff in the<00:15:08.360> background<00:15:08.689> and<00:15:09.319> just<00:15:09.949> let's<00:15:10.189> think 00:15:10.299 --> 00:15:10.309 align:start position:0% the background and just let's think 00:15:10.309 --> 00:15:13.059 align:start position:0% the background and just let's think about<00:15:10.569> cryptokeys<00:15:11.569> for<00:15:11.809> example<00:15:12.170> for<00:15:12.829> critter 00:15:13.059 --> 00:15:13.069 align:start position:0% about cryptokeys for example for critter 00:15:13.069 --> 00:15:15.609 align:start position:0% about cryptokeys for example for critter kiddies<00:15:13.339> you<00:15:13.490> just<00:15:13.670> like<00:15:13.850> go<00:15:14.600> to<00:15:14.660> the<00:15:14.930> dap<00:15:15.290> and 00:15:15.609 --> 00:15:15.619 align:start position:0% kiddies you just like go to the dap and 00:15:15.619 --> 00:15:17.949 align:start position:0% kiddies you just like go to the dap and then<00:15:15.829> you<00:15:16.249> can<00:15:16.459> sign<00:15:16.790> up<00:15:16.850> by<00:15:17.059> signing<00:15:17.899> a 00:15:17.949 --> 00:15:17.959 align:start position:0% then you can sign up by signing a 00:15:17.959 --> 00:15:19.480 align:start position:0% then you can sign up by signing a message<00:15:18.290> you<00:15:18.499> don't<00:15:18.529> need<00:15:18.860> either<00:15:19.100> for<00:15:19.459> that 00:15:19.480 --> 00:15:19.490 align:start position:0% message you don't need either for that 00:15:19.490 --> 00:15:21.759 align:start position:0% message you don't need either for that once<00:15:20.300> you're<00:15:20.449> in<00:15:20.480> you<00:15:20.930> are<00:15:20.959> able<00:15:21.230> to<00:15:21.379> start 00:15:21.759 --> 00:15:21.769 align:start position:0% once you're in you are able to start 00:15:21.769 --> 00:15:24.100 align:start position:0% once you're in you are able to start browsing<00:15:21.980> the<00:15:22.819> different<00:15:23.179> collectibles 00:15:24.100 --> 00:15:24.110 align:start position:0% browsing the different collectibles 00:15:24.110 --> 00:15:25.960 align:start position:0% browsing the different collectibles right<00:15:24.290> and<00:15:24.559> you<00:15:25.040> might<00:15:25.189> even<00:15:25.279> find<00:15:25.519> one<00:15:25.790> that 00:15:25.960 --> 00:15:25.970 align:start position:0% right and you might even find one that 00:15:25.970 --> 00:15:28.600 align:start position:0% right and you might even find one that you<00:15:25.999> like<00:15:26.059> so<00:15:26.749> now<00:15:27.139> you<00:15:27.199> have<00:15:27.410> a<00:15:27.439> motivation<00:15:28.129> to 00:15:28.600 --> 00:15:28.610 align:start position:0% you like so now you have a motivation to 00:15:28.610 --> 00:15:30.160 align:start position:0% you like so now you have a motivation to actually<00:15:28.759> pass<00:15:29.179> to<00:15:29.360> the<00:15:29.480> next<00:15:29.689> stage<00:15:29.869> which<00:15:29.899> is 00:15:30.160 --> 00:15:30.170 align:start position:0% actually pass to the next stage which is 00:15:30.170 --> 00:15:32.679 align:start position:0% actually pass to the next stage which is add<00:15:30.619> funds<00:15:30.949> to<00:15:31.009> your<00:15:31.160> wallet<00:15:31.519> so<00:15:32.209> at<00:15:32.480> that<00:15:32.629> time 00:15:32.679 --> 00:15:32.689 align:start position:0% add funds to your wallet so at that time 00:15:32.689 --> 00:15:35.139 align:start position:0% add funds to your wallet so at that time we're<00:15:33.170> going<00:15:33.290> to<00:15:33.379> ask<00:15:33.529> you<00:15:33.769> to<00:15:34.309> have<00:15:34.519> to<00:15:34.910> create 00:15:35.139 --> 00:15:35.149 align:start position:0% we're going to ask you to have to create 00:15:35.149 --> 00:15:37.449 align:start position:0% we're going to ask you to have to create a<00:15:35.179> password<00:15:35.389> and<00:15:35.809> the<00:15:36.709> security<00:15:37.339> of<00:15:37.369> your 00:15:37.449 --> 00:15:37.459 align:start position:0% a password and the security of your 00:15:37.459 --> 00:15:40.689 align:start position:0% a password and the security of your account<00:15:37.819> it<00:15:38.269> will<00:15:38.480> increase<00:15:38.920> as<00:15:39.920> long<00:15:40.249> as<00:15:40.429> you 00:15:40.689 --> 00:15:40.699 align:start position:0% account it will increase as long as you 00:15:40.699 --> 00:15:42.009 align:start position:0% account it will increase as long as you know<00:15:40.790> your<00:15:41.029> account<00:15:41.269> starts<00:15:41.600> holding<00:15:41.899> more 00:15:42.009 --> 00:15:42.019 align:start position:0% know your account starts holding more 00:15:42.019 --> 00:15:44.139 align:start position:0% know your account starts holding more value<00:15:42.379> but<00:15:42.709> it<00:15:42.829> doesn't<00:15:43.100> make<00:15:43.220> sense<00:15:43.249> to<00:15:43.850> make 00:15:44.139 --> 00:15:44.149 align:start position:0% value but it doesn't make sense to make 00:15:44.149 --> 00:15:46.090 align:start position:0% value but it doesn't make sense to make you<00:15:44.329> deal<00:15:44.509> with<00:15:44.569> all<00:15:44.929> this<00:15:45.110> stuff<00:15:45.379> before<00:15:45.800> you 00:15:46.090 --> 00:15:46.100 align:start position:0% you deal with all this stuff before you 00:15:46.100 --> 00:15:48.639 align:start position:0% you deal with all this stuff before you are<00:15:46.249> you<00:15:46.730> know<00:15:46.850> able<00:15:47.269> to<00:15:47.420> see<00:15:47.749> what's<00:15:48.050> going<00:15:48.350> on 00:15:48.639 --> 00:15:48.649 align:start position:0% are you know able to see what's going on 00:15:48.649 --> 00:15:52.840 align:start position:0% are you know able to see what's going on inside<00:15:49.100> the<00:15:49.429> app<00:15:49.670> ecosystem<00:15:50.679> so<00:15:51.679> you<00:15:52.429> know<00:15:52.519> we 00:15:52.840 --> 00:15:52.850 align:start position:0% inside the app ecosystem so you know we 00:15:52.850 --> 00:15:54.790 align:start position:0% inside the app ecosystem so you know we really<00:15:53.329> hope<00:15:53.509> that<00:15:53.540> this<00:15:54.019> new<00:15:54.079> flow<00:15:54.439> is<00:15:54.649> going 00:15:54.790 --> 00:15:54.800 align:start position:0% really hope that this new flow is going 00:15:54.800 --> 00:15:57.340 align:start position:0% really hope that this new flow is going to<00:15:54.920> help<00:15:55.639> bring<00:15:56.119> more<00:15:56.360> people<00:15:56.569> to<00:15:56.809> space<00:15:57.050> and 00:15:57.340 --> 00:15:57.350 align:start position:0% to help bring more people to space and 00:15:57.350 --> 00:15:58.929 align:start position:0% to help bring more people to space and not<00:15:57.559> try<00:15:57.740> to<00:15:57.769> scare<00:15:58.129> them<00:15:58.309> with<00:15:58.339> all<00:15:58.610> the<00:15:58.730> stuff 00:15:58.929 --> 00:15:58.939 align:start position:0% not try to scare them with all the stuff 00:15:58.939 --> 00:16:00.850 align:start position:0% not try to scare them with all the stuff that<00:15:59.089> I<00:15:59.119> mentioned<00:15:59.540> earlier<00:15:59.600> but<00:16:00.529> what<00:16:00.649> about 00:16:00.850 --> 00:16:00.860 align:start position:0% that I mentioned earlier but what about 00:16:00.860 --> 00:16:04.389 align:start position:0% that I mentioned earlier but what about existing<00:16:01.369> users<00:16:02.800> you<00:16:03.800> guys<00:16:03.980> might<00:16:04.369> be 00:16:04.389 --> 00:16:04.399 align:start position:0% existing users you guys might be 00:16:04.399 --> 00:16:06.160 align:start position:0% existing users you guys might be wondering<00:16:04.519> what<00:16:05.149> this<00:16:05.420> perience<00:16:05.869> is<00:16:05.990> gonna 00:16:06.160 --> 00:16:06.170 align:start position:0% wondering what this perience is gonna 00:16:06.170 --> 00:16:08.109 align:start position:0% wondering what this perience is gonna you<00:16:06.619> know<00:16:06.709> look<00:16:06.889> for<00:16:07.129> you<00:16:07.249> I<00:16:07.429> show<00:16:07.819> you<00:16:07.850> some 00:16:08.109 --> 00:16:08.119 align:start position:0% you know look for you I show you some 00:16:08.119 --> 00:16:11.259 align:start position:0% you know look for you I show you some mock-ups<00:16:08.480> about<00:16:08.869> what<00:16:09.439> we<00:16:09.619> did<00:16:09.889> for<00:16:10.670> you<00:16:11.120> know 00:16:11.259 --> 00:16:11.269 align:start position:0% mock-ups about what we did for you know 00:16:11.269 --> 00:16:13.389 align:start position:0% mock-ups about what we did for you know new<00:16:11.509> users<00:16:11.839> but<00:16:12.439> I'm<00:16:12.620> gonna<00:16:12.740> show<00:16:12.920> you<00:16:13.009> what<00:16:13.249> we 00:16:13.389 --> 00:16:13.399 align:start position:0% new users but I'm gonna show you what we 00:16:13.399 --> 00:16:17.999 align:start position:0% new users but I'm gonna show you what we build<00:16:13.699> for<00:16:14.179> you<00:16:15.459> so<00:16:16.459> as<00:16:16.790> you<00:16:16.910> can<00:16:17.029> see<00:16:17.089> on<00:16:17.509> the 00:16:17.999 --> 00:16:18.009 align:start position:0% build for you so as you can see on the 00:16:18.009 --> 00:16:22.090 align:start position:0% build for you so as you can see on the right<00:16:19.009> you<00:16:19.819> have<00:16:19.850> the<00:16:20.439> manimals<00:16:21.439> extension<00:16:21.889> on 00:16:22.090 --> 00:16:22.100 align:start position:0% right you have the manimals extension on 00:16:22.100 --> 00:16:24.549 align:start position:0% right you have the manimals extension on the<00:16:22.399> left<00:16:22.579> you<00:16:22.790> have<00:16:22.819> the<00:16:23.600> new<00:16:24.019> mobile<00:16:24.290> app<00:16:24.410> I'm 00:16:24.549 --> 00:16:24.559 align:start position:0% the left you have the new mobile app I'm 00:16:24.559 --> 00:16:26.799 align:start position:0% the left you have the new mobile app I'm gonna<00:16:24.740> show<00:16:24.949> you<00:16:25.009> what<00:16:25.339> happens<00:16:25.670> when<00:16:25.730> you<00:16:26.029> tap 00:16:26.799 --> 00:16:26.809 align:start position:0% gonna show you what happens when you tap 00:16:26.809 --> 00:16:31.809 align:start position:0% gonna show you what happens when you tap on<00:16:26.839> import<00:16:27.259> wallet<00:16:28.959> so<00:16:30.370> you<00:16:31.370> get<00:16:31.550> the 00:16:31.809 --> 00:16:31.819 align:start position:0% on import wallet so you get the 00:16:31.819 --> 00:16:33.519 align:start position:0% on import wallet so you get the instructions<00:16:32.360> there<00:16:32.480> it's<00:16:32.689> open<00:16:32.870> extension 00:16:33.519 --> 00:16:33.529 align:start position:0% instructions there it's open extension 00:16:33.529 --> 00:16:36.100 align:start position:0% instructions there it's open extension go<00:16:33.769> to<00:16:33.920> settings<00:16:34.309> click<00:16:34.550> on<00:16:35.389> sync<00:16:35.720> with<00:16:35.870> moil 00:16:36.100 --> 00:16:36.110 align:start position:0% go to settings click on sync with moil 00:16:36.110 --> 00:16:39.549 align:start position:0% go to settings click on sync with moil and<00:16:36.379> then<00:16:36.800> you<00:16:36.980> scan<00:16:37.249> the<00:16:37.819> QR<00:16:38.059> code<00:16:38.410> enter<00:16:39.410> your 00:16:39.549 --> 00:16:39.559 align:start position:0% and then you scan the QR code enter your 00:16:39.559 --> 00:16:42.419 align:start position:0% and then you scan the QR code enter your password<00:16:39.740> first<00:16:40.209> generates<00:16:41.209> a<00:16:41.269> QR<00:16:41.509> code<00:16:41.749> and 00:16:42.419 --> 00:16:42.429 align:start position:0% password first generates a QR code and 00:16:42.429 --> 00:16:46.840 align:start position:0% password first generates a QR code and now<00:16:43.429> you<00:16:43.819> scan<00:16:44.059> the<00:16:44.149> QR<00:16:44.360> code<00:16:45.069> right<00:16:46.069> now<00:16:46.100> the 00:16:46.840 --> 00:16:46.850 align:start position:0% now you scan the QR code right now the 00:16:46.850 --> 00:16:49.419 align:start position:0% now you scan the QR code right now the syncing<00:16:47.600> is<00:16:47.689> happening<00:16:48.079> the<00:16:48.709> app<00:16:48.829> is<00:16:49.040> parsing 00:16:49.419 --> 00:16:49.429 align:start position:0% syncing is happening the app is parsing 00:16:49.429 --> 00:16:51.280 align:start position:0% syncing is happening the app is parsing all<00:16:49.549> your<00:16:49.730> account<00:16:49.970> information<00:16:50.149> and<00:16:50.660> after<00:16:51.110> a 00:16:51.280 --> 00:16:51.290 align:start position:0% all your account information and after a 00:16:51.290 --> 00:16:54.519 align:start position:0% all your account information and after a few<00:16:51.529> seconds<00:16:52.509> boom<00:16:53.509> you're<00:16:53.929> all<00:16:54.049> set 00:16:54.519 --> 00:16:54.529 align:start position:0% few seconds boom you're all set 00:16:54.529 --> 00:16:57.730 align:start position:0% few seconds boom you're all set that's<00:16:55.160> it<00:16:55.399> if<00:16:55.579> you<00:16:55.879> look<00:16:56.209> now<00:16:56.240> you<00:16:56.749> have<00:16:56.959> your 00:16:57.730 --> 00:16:57.740 align:start position:0% that's it if you look now you have your 00:16:57.740 --> 00:17:01.299 align:start position:0% that's it if you look now you have your same<00:16:58.579> account<00:16:58.939> on<00:16:59.209> the<00:16:59.809> extension<00:17:00.290> and<00:17:00.529> on<00:17:01.009> the 00:17:01.299 --> 00:17:01.309 align:start position:0% same account on the extension and on the 00:17:01.309 --> 00:17:04.779 align:start position:0% same account on the extension and on the app<00:17:01.600> you<00:17:02.649> will<00:17:03.649> also<00:17:03.829> see<00:17:04.159> what<00:17:04.309> happens<00:17:04.640> to 00:17:04.779 --> 00:17:04.789 align:start position:0% app you will also see what happens to 00:17:04.789 --> 00:17:08.350 align:start position:0% app you will also see what happens to the<00:17:04.850> transactions<00:17:05.679> we<00:17:06.679> are<00:17:06.909> importing<00:17:07.909> your 00:17:08.350 --> 00:17:08.360 align:start position:0% the transactions we are importing your 00:17:08.360 --> 00:17:10.449 align:start position:0% the transactions we are importing your entire<00:17:08.750> transaction<00:17:09.140> history<00:17:09.470> to<00:17:10.130> your<00:17:10.250> phone 00:17:10.449 --> 00:17:10.459 align:start position:0% entire transaction history to your phone 00:17:10.459 --> 00:17:14.470 align:start position:0% entire transaction history to your phone and<00:17:11.140> also<00:17:12.459> not<00:17:13.459> just<00:17:13.669> the<00:17:13.730> transactions<00:17:14.299> but 00:17:14.470 --> 00:17:14.480 align:start position:0% and also not just the transactions but 00:17:14.480 --> 00:17:15.789 align:start position:0% and also not just the transactions but also<00:17:14.659> you<00:17:15.260> know<00:17:15.380> all<00:17:15.559> the<00:17:15.649> information 00:17:15.789 --> 00:17:15.799 align:start position:0% also you know all the information 00:17:15.799 --> 00:17:18.429 align:start position:0% also you know all the information related<00:17:16.279> to<00:17:16.459> in<00:17:16.579> transaction<00:17:16.850> like<00:17:17.299> hash<00:17:17.569> gas 00:17:18.429 --> 00:17:18.439 align:start position:0% related to in transaction like hash gas 00:17:18.439 --> 00:17:20.470 align:start position:0% related to in transaction like hash gas usage<00:17:18.770> and<00:17:19.279> all<00:17:19.579> the<00:17:19.730> stuff 00:17:20.470 --> 00:17:20.480 align:start position:0% usage and all the stuff 00:17:20.480 --> 00:17:22.689 align:start position:0% usage and all the stuff so<00:17:20.929> you<00:17:21.470> have<00:17:21.620> your<00:17:21.829> account<00:17:21.889> your<00:17:22.279> balance 00:17:22.689 --> 00:17:22.699 align:start position:0% so you have your account your balance 00:17:22.699 --> 00:17:24.610 align:start position:0% so you have your account your balance your<00:17:22.789> transactions<00:17:23.329> but<00:17:23.870> what<00:17:24.049> happens<00:17:24.380> when 00:17:24.610 --> 00:17:24.620 align:start position:0% your transactions but what happens when 00:17:24.620 --> 00:17:26.620 align:start position:0% your transactions but what happens when you<00:17:24.679> have<00:17:24.799> more<00:17:25.039> than<00:17:25.159> one<00:17:25.339> account<00:17:25.549> so<00:17:25.880> now 00:17:26.620 --> 00:17:26.630 align:start position:0% you have more than one account so now 00:17:26.630 --> 00:17:29.590 align:start position:0% you have more than one account so now you<00:17:26.689> will<00:17:26.929> see<00:17:27.169> on<00:17:27.380> the<00:17:27.679> Moya<00:17:27.829> lab<00:17:28.100> that<00:17:28.940> we<00:17:29.389> are 00:17:29.590 --> 00:17:29.600 align:start position:0% you will see on the Moya lab that we are 00:17:29.600 --> 00:17:33.549 align:start position:0% you will see on the Moya lab that we are also<00:17:30.580> exporting<00:17:31.580> all<00:17:31.760> your<00:17:32.179> accounts<00:17:32.480> if<00:17:33.440> you 00:17:33.549 --> 00:17:33.559 align:start position:0% also exporting all your accounts if you 00:17:33.559 --> 00:17:35.590 align:start position:0% also exporting all your accounts if you compare<00:17:33.980> the<00:17:34.399> accounts<00:17:34.789> on<00:17:34.909> the<00:17:35.029> more<00:17:35.360> lap 00:17:35.590 --> 00:17:35.600 align:start position:0% compare the accounts on the more lap 00:17:35.600 --> 00:17:37.330 align:start position:0% compare the accounts on the more lap with<00:17:36.200> accounts<00:17:36.559> on<00:17:36.649> the<00:17:36.710> extension<00:17:37.130> there<00:17:37.279> are 00:17:37.330 --> 00:17:37.340 align:start position:0% with accounts on the extension there are 00:17:37.340 --> 00:17:38.740 align:start position:0% with accounts on the extension there are the<00:17:37.460> same<00:17:37.669> they<00:17:37.850> have<00:17:38.000> the<00:17:38.090> same<00:17:38.269> names 00:17:38.740 --> 00:17:38.750 align:start position:0% the same they have the same names 00:17:38.750 --> 00:17:41.200 align:start position:0% the same they have the same names so<00:17:39.289> basically<00:17:39.769> we're<00:17:40.130> porting<00:17:40.669> your<00:17:40.880> entire 00:17:41.200 --> 00:17:41.210 align:start position:0% so basically we're porting your entire 00:17:41.210 --> 00:17:43.240 align:start position:0% so basically we're porting your entire desktop<00:17:41.659> experience<00:17:42.320> into<00:17:42.590> your<00:17:42.710> phone<00:17:42.980> in 00:17:43.240 --> 00:17:43.250 align:start position:0% desktop experience into your phone in 00:17:43.250 --> 00:17:54.909 align:start position:0% desktop experience into your phone in about<00:17:43.490> 15<00:17:43.850> seconds<00:17:50.799> so<00:17:52.690> just<00:17:53.690> to<00:17:53.750> recap<00:17:53.929> this 00:17:54.909 --> 00:17:54.919 align:start position:0% about 15 seconds so just to recap this 00:17:54.919 --> 00:17:56.830 align:start position:0% about 15 seconds so just to recap this is<00:17:55.100> the<00:17:55.490> kind<00:17:55.850> of<00:17:55.909> like<00:17:56.120> flow<00:17:56.450> that<00:17:56.630> we're 00:17:56.830 --> 00:17:56.840 align:start position:0% is the kind of like flow that we're 00:17:56.840 --> 00:17:59.230 align:start position:0% is the kind of like flow that we're going<00:17:57.019> for<00:17:57.289> new<00:17:58.220> users<00:17:58.580> they<00:17:58.789> go<00:17:58.909> straight<00:17:59.210> to 00:17:59.230 --> 00:17:59.240 align:start position:0% going for new users they go straight to 00:17:59.240 --> 00:18:02.860 align:start position:0% going for new users they go straight to that<00:17:59.889> existing<00:18:00.889> users<00:18:01.340> you<00:18:01.610> can<00:18:01.820> import<00:18:02.480> your 00:18:02.860 --> 00:18:02.870 align:start position:0% that existing users you can import your 00:18:02.870 --> 00:18:06.129 align:start position:0% that existing users you can import your wallet<00:18:03.710> using<00:18:04.399> your<00:18:04.580> citrus<00:18:05.059> or<00:18:05.299> you<00:18:05.690> can<00:18:05.840> use 00:18:06.129 --> 00:18:06.139 align:start position:0% wallet using your citrus or you can use 00:18:06.139 --> 00:18:08.470 align:start position:0% wallet using your citrus or you can use the<00:18:06.740> model<00:18:06.980> sync<00:18:07.340> feature<00:18:07.519> that<00:18:07.789> I<00:18:08.000> just<00:18:08.330> show 00:18:08.470 --> 00:18:08.480 align:start position:0% the model sync feature that I just show 00:18:08.480 --> 00:18:11.200 align:start position:0% the model sync feature that I just show you<00:18:09.039> one<00:18:10.039> important<00:18:10.399> thing<00:18:10.580> if<00:18:10.760> you<00:18:10.850> look<00:18:11.029> at 00:18:11.200 --> 00:18:11.210 align:start position:0% you one important thing if you look at 00:18:11.210 --> 00:18:13.419 align:start position:0% you one important thing if you look at how<00:18:11.389> we<00:18:11.450> you<00:18:12.230> know<00:18:12.380> that<00:18:12.740> the<00:18:12.830> diagram<00:18:13.100> looks 00:18:13.419 --> 00:18:13.429 align:start position:0% how we you know that the diagram looks 00:18:13.429 --> 00:18:16.539 align:start position:0% how we you know that the diagram looks like<00:18:13.580> you<00:18:14.299> have<00:18:14.450> the<00:18:14.570> wallet<00:18:14.960> as<00:18:15.169> a<00:18:15.230> side<00:18:15.740> thing 00:18:16.539 --> 00:18:16.549 align:start position:0% like you have the wallet as a side thing 00:18:16.549 --> 00:18:18.639 align:start position:0% like you have the wallet as a side thing right<00:18:16.880> it's<00:18:17.149> even<00:18:17.720> important<00:18:18.200> module<00:18:18.320> of<00:18:18.529> the 00:18:18.639 --> 00:18:18.649 align:start position:0% right it's even important module of the 00:18:18.649 --> 00:18:21.549 align:start position:0% right it's even important module of the app<00:18:18.769> it's<00:18:19.039> necessary<00:18:19.580> that<00:18:20.120> we<00:18:20.840> want<00:18:21.049> to<00:18:21.350> have 00:18:21.549 --> 00:18:21.559 align:start position:0% app it's necessary that we want to have 00:18:21.559 --> 00:18:23.860 align:start position:0% app it's necessary that we want to have our<00:18:21.799> that<00:18:22.279> we<00:18:22.580> want<00:18:22.730> to<00:18:22.789> make<00:18:22.909> the<00:18:23.059> core<00:18:23.330> of<00:18:23.510> the 00:18:23.860 --> 00:18:23.870 align:start position:0% our that we want to make the core of the 00:18:23.870 --> 00:18:26.289 align:start position:0% our that we want to make the core of the app<00:18:24.019> the<00:18:24.500> browser<00:18:24.740> experience<00:18:25.159> so<00:18:25.880> that's 00:18:26.289 --> 00:18:26.299 align:start position:0% app the browser experience so that's 00:18:26.299 --> 00:18:28.810 align:start position:0% app the browser experience so that's something<00:18:26.480> to<00:18:26.659> you<00:18:27.590> know<00:18:27.710> think<00:18:28.519> about<00:18:28.639> it 00:18:28.810 --> 00:18:28.820 align:start position:0% something to you know think about it 00:18:28.820 --> 00:18:30.190 align:start position:0% something to you know think about it when<00:18:29.090> you<00:18:29.210> compare<00:18:29.539> it<00:18:29.600> with<00:18:29.630> the<00:18:29.809> existing 00:18:30.190 --> 00:18:30.200 align:start position:0% when you compare it with the existing 00:18:30.200 --> 00:18:34.629 align:start position:0% when you compare it with the existing options<00:18:30.470> that<00:18:30.590> you<00:18:30.679> have<00:18:32.830> one<00:18:33.830> last<00:18:34.309> thing<00:18:34.429> I 00:18:34.629 --> 00:18:34.639 align:start position:0% options that you have one last thing I 00:18:34.639 --> 00:18:36.549 align:start position:0% options that you have one last thing I want<00:18:34.820> to<00:18:34.880> show<00:18:35.029> you<00:18:35.090> do<00:18:35.750> you<00:18:35.779> guys<00:18:35.960> remember<00:18:36.169> I 00:18:36.549 --> 00:18:36.559 align:start position:0% want to show you do you guys remember I 00:18:36.559 --> 00:18:39.430 align:start position:0% want to show you do you guys remember I said<00:18:36.860> we<00:18:37.159> want<00:18:37.370> to<00:18:37.460> be<00:18:37.669> we<00:18:38.630> we<00:18:38.870> just<00:18:38.899> don't<00:18:39.139> want 00:18:39.430 --> 00:18:39.440 align:start position:0% said we want to be we we just don't want 00:18:39.440 --> 00:18:41.110 align:start position:0% said we want to be we we just don't want to<00:18:39.470> be<00:18:39.590> a<00:18:39.620> wallet<00:18:40.010> but<00:18:40.250> we<00:18:40.700> want<00:18:40.880> to<00:18:40.970> be<00:18:41.090> a 00:18:41.110 --> 00:18:41.120 align:start position:0% to be a wallet but we want to be a 00:18:41.120 --> 00:18:43.509 align:start position:0% to be a wallet but we want to be a bridge<00:18:41.389> to<00:18:41.419> the<00:18:41.659> decentralized<00:18:42.200> web<00:18:42.380> so<00:18:43.159> this 00:18:43.509 --> 00:18:43.519 align:start position:0% bridge to the decentralized web so this 00:18:43.519 --> 00:18:45.159 align:start position:0% bridge to the decentralized web so this picture<00:18:43.669> that<00:18:43.940> I'm<00:18:44.029> gonna<00:18:44.240> show<00:18:44.570> you<00:18:44.630> it's<00:18:44.990> all 00:18:45.159 --> 00:18:45.169 align:start position:0% picture that I'm gonna show you it's all 00:18:45.169 --> 00:18:47.049 align:start position:0% picture that I'm gonna show you it's all about<00:18:45.380> that<00:18:45.590> in<00:18:46.190> my<00:18:46.370> opinion<00:18:46.490> it's<00:18:46.909> a<00:18:47.029> very 00:18:47.049 --> 00:18:47.059 align:start position:0% about that in my opinion it's a very 00:18:47.059 --> 00:18:49.149 align:start position:0% about that in my opinion it's a very important<00:18:47.750> step<00:18:47.929> there's<00:18:48.710> some<00:18:48.860> more 00:18:49.149 --> 00:18:49.159 align:start position:0% important step there's some more 00:18:49.159 --> 00:18:51.509 align:start position:0% important step there's some more decentralized<00:18:49.580> way<00:18:50.059> so<00:18:50.419> let's<00:18:50.690> check<00:18:50.809> it<00:18:50.870> out 00:18:51.509 --> 00:18:51.519 align:start position:0% decentralized way so let's check it out 00:18:51.519 --> 00:18:55.659 align:start position:0% decentralized way so let's check it out if<00:18:52.519> you<00:18:52.669> see<00:18:52.850> that's<00:18:53.809> a<00:18:54.230> website<00:18:55.039> I'm<00:18:55.309> loading 00:18:55.659 --> 00:18:55.669 align:start position:0% if you see that's a website I'm loading 00:18:55.669 --> 00:18:57.549 align:start position:0% if you see that's a website I'm loading on<00:18:55.789> the<00:18:55.909> emitter<00:18:56.090> I'm<00:18:56.179> a<00:18:56.240> small<00:18:56.450> app<00:18:56.659> but 00:18:57.549 --> 00:18:57.559 align:start position:0% on the emitter I'm a small app but 00:18:57.559 --> 00:19:00.159 align:start position:0% on the emitter I'm a small app but actually<00:18:58.340> that's<00:18:58.490> not<00:18:58.639> a<00:18:58.760> normal<00:18:59.210> website<00:18:59.389> if 00:19:00.159 --> 00:19:00.169 align:start position:0% actually that's not a normal website if 00:19:00.169 --> 00:19:02.230 align:start position:0% actually that's not a normal website if you<00:19:00.289> look<00:19:00.440> at<00:19:00.529> the<00:19:00.620> URL<00:19:00.799> you<00:19:01.220> will<00:19:01.429> see<00:19:01.519> that<00:19:02.000> it 00:19:02.230 --> 00:19:02.240 align:start position:0% you look at the URL you will see that it 00:19:02.240 --> 00:19:05.769 align:start position:0% you look at the URL you will see that it ends<00:19:02.720> on<00:19:02.809> dot<00:19:03.110> eath<00:19:03.380> okay<00:19:04.299> that's<00:19:05.299> because 00:19:05.769 --> 00:19:05.779 align:start position:0% ends on dot eath okay that's because 00:19:05.779 --> 00:19:09.129 align:start position:0% ends on dot eath okay that's because it's<00:19:06.200> an<00:19:06.679> e<00:19:07.639> NS<00:19:08.000> name<00:19:08.179> from<00:19:08.480> the<00:19:08.630> etherium<00:19:08.990> name 00:19:09.129 --> 00:19:09.139 align:start position:0% it's an e NS name from the etherium name 00:19:09.139 --> 00:19:12.820 align:start position:0% it's an e NS name from the etherium name service<00:19:09.669> which<00:19:10.669> is<00:19:10.820> really<00:19:11.059> cool<00:19:11.210> that<00:19:12.200> what 00:19:12.820 --> 00:19:12.830 align:start position:0% service which is really cool that what 00:19:12.830 --> 00:19:14.830 align:start position:0% service which is really cool that what happens<00:19:13.130> with<00:19:13.220> the<00:19:13.309> hosting<00:19:13.700> this<00:19:14.539> is<00:19:14.659> not 00:19:14.830 --> 00:19:14.840 align:start position:0% happens with the hosting this is not 00:19:14.840 --> 00:19:16.720 align:start position:0% happens with the hosting this is not like<00:19:15.019> a<00:19:15.049> normal<00:19:15.320> web<00:19:15.679> site<00:19:15.889> that's<00:19:16.070> hosting<00:19:16.519> a 00:19:16.720 --> 00:19:16.730 align:start position:0% like a normal web site that's hosting a 00:19:16.730 --> 00:19:21.310 align:start position:0% like a normal web site that's hosting a regular<00:19:17.029> web<00:19:17.210> server<00:19:17.769> I<00:19:20.019> think<00:19:21.019> you<00:19:21.139> guys 00:19:21.310 --> 00:19:21.320 align:start position:0% regular web server I think you guys 00:19:21.320 --> 00:19:25.600 align:start position:0% regular web server I think you guys heard<00:19:21.620> about<00:19:22.000> ipfs<00:19:23.000> before<00:19:23.330> right<00:19:23.889> so<00:19:24.889> this<00:19:25.490> is 00:19:25.600 --> 00:19:25.610 align:start position:0% heard about ipfs before right so this is 00:19:25.610 --> 00:19:27.009 align:start position:0% heard about ipfs before right so this is where<00:19:25.850> this<00:19:26.149> website<00:19:26.539> is<00:19:26.600> looking<00:19:26.840> right<00:19:26.990> now 00:19:27.009 --> 00:19:27.019 align:start position:0% where this website is looking right now 00:19:27.019 --> 00:19:29.860 align:start position:0% where this website is looking right now it's<00:19:27.830> free<00:19:28.039> and<00:19:28.250> decent<00:19:28.370> relize<00:19:28.760> so<00:19:29.419> if<00:19:29.720> you 00:19:29.860 --> 00:19:29.870 align:start position:0% it's free and decent relize so if you 00:19:29.870 --> 00:19:31.799 align:start position:0% it's free and decent relize so if you are<00:19:29.960> still<00:19:30.169> confused<00:19:30.379> about<00:19:30.710> what's<00:19:31.039> going<00:19:31.309> on 00:19:31.799 --> 00:19:31.809 align:start position:0% are still confused about what's going on 00:19:31.809 --> 00:19:34.600 align:start position:0% are still confused about what's going on let<00:19:32.809> me<00:19:32.840> explain<00:19:33.169> you 00:19:34.600 --> 00:19:34.610 align:start position:0% let me explain you 00:19:34.610 --> 00:19:37.299 align:start position:0% let me explain you we're<00:19:35.570> basically<00:19:35.720> supporting<00:19:36.559> allowing<00:19:37.190> you 00:19:37.299 --> 00:19:37.309 align:start position:0% we're basically supporting allowing you 00:19:37.309 --> 00:19:39.820 align:start position:0% we're basically supporting allowing you to<00:19:37.490> browse<00:19:37.730> ipfs<00:19:38.720> cross<00:19:38.960> websites<00:19:39.500> through 00:19:39.820 --> 00:19:39.830 align:start position:0% to browse ipfs cross websites through 00:19:39.830 --> 00:19:42.610 align:start position:0% to browse ipfs cross websites through ENS<00:19:40.160> names<00:19:40.400> so<00:19:40.940> for<00:19:41.120> example<00:19:41.510> the<00:19:42.200> name<00:19:42.410> that 00:19:42.610 --> 00:19:42.620 align:start position:0% ENS names so for example the name that 00:19:42.620 --> 00:19:44.440 align:start position:0% ENS names so for example the name that you<00:19:42.710> see<00:19:42.890> there<00:19:43.070> if<00:19:43.370> you<00:19:43.520> sold<00:19:43.730> to<00:19:43.940> the<00:19:44.030> ipfs 00:19:44.440 --> 00:19:44.450 align:start position:0% you see there if you sold to the ipfs 00:19:44.450 --> 00:19:46.180 align:start position:0% you see there if you sold to the ipfs Content<00:19:44.809> ID<00:19:44.929> that's<00:19:45.200> below<00:19:45.440> which<00:19:45.890> is<00:19:46.010> also 00:19:46.180 --> 00:19:46.190 align:start position:0% Content ID that's below which is also 00:19:46.190 --> 00:19:49.270 align:start position:0% Content ID that's below which is also known<00:19:46.400> as<00:19:46.580> the<00:19:46.669> ID<00:19:46.790> FS<00:19:47.059> hash<00:19:47.270> and<00:19:48.100> before<00:19:49.100> that 00:19:49.270 --> 00:19:49.280 align:start position:0% known as the ID FS hash and before that 00:19:49.280 --> 00:19:51.520 align:start position:0% known as the ID FS hash and before that you<00:19:49.640> were<00:19:49.910> able<00:19:50.270> to<00:19:50.299> access<00:19:50.570> that<00:19:50.870> same 00:19:51.520 --> 00:19:51.530 align:start position:0% you were able to access that same 00:19:51.530 --> 00:19:53.830 align:start position:0% you were able to access that same content<00:19:51.980> using<00:19:52.490> the<00:19:52.520> IP<00:19:52.790> FS<00:19:53.059> gateway<00:19:53.419> URL<00:19:53.690> if 00:19:53.830 --> 00:19:53.840 align:start position:0% content using the IP FS gateway URL if 00:19:53.840 --> 00:19:55.750 align:start position:0% content using the IP FS gateway URL if you<00:19:53.929> look<00:19:54.080> at<00:19:54.200> the<00:19:54.320> first<00:19:54.799> link<00:19:54.980> you'll<00:19:55.669> see 00:19:55.750 --> 00:19:55.760 align:start position:0% you look at the first link you'll see 00:19:55.760 --> 00:19:58.990 align:start position:0% you look at the first link you'll see says<00:19:56.120> ipfs<00:19:56.660> io<00:19:56.809> /<00:19:57.049> IP<00:19:57.559> FS<00:19:57.830> and<00:19:58.040> then<00:19:58.309> there<00:19:58.850> is<00:19:58.970> a 00:19:58.990 --> 00:19:59.000 align:start position:0% says ipfs io / IP FS and then there is a 00:19:59.000 --> 00:20:01.659 align:start position:0% says ipfs io / IP FS and then there is a net<00:19:59.660> via<00:19:59.750> the<00:19:59.870> cache<00:20:00.110> and<00:20:00.380> the<00:20:00.530> file<00:20:00.710> name<00:20:00.890> if 00:20:01.659 --> 00:20:01.669 align:start position:0% net via the cache and the file name if 00:20:01.669 --> 00:20:03.549 align:start position:0% net via the cache and the file name if you<00:20:01.760> tap<00:20:02.000> there<00:20:02.179> now<00:20:02.900> you<00:20:02.960> will<00:20:03.290> see<00:20:03.410> there<00:20:03.530> is 00:20:03.549 --> 00:20:03.559 align:start position:0% you tap there now you will see there is 00:20:03.559 --> 00:20:05.919 align:start position:0% you tap there now you will see there is a<00:20:03.620> file<00:20:03.919> there<00:20:04.100> ok<00:20:04.460> with<00:20:04.970> the<00:20:05.120> old-style<00:20:05.419> URL 00:20:05.919 --> 00:20:05.929 align:start position:0% a file there ok with the old-style URL 00:20:05.929 --> 00:20:09.220 align:start position:0% a file there ok with the old-style URL now<00:20:06.799> you're<00:20:07.790> gonna<00:20:07.910> see<00:20:08.120> that<00:20:08.330> if<00:20:08.570> I<00:20:08.780> tap<00:20:09.049> on 00:20:09.220 --> 00:20:09.230 align:start position:0% now you're gonna see that if I tap on 00:20:09.230 --> 00:20:11.230 align:start position:0% now you're gonna see that if I tap on the<00:20:09.380> second<00:20:10.100> link<00:20:10.250> you're<00:20:10.850> gonna<00:20:10.970> see<00:20:11.179> the 00:20:11.230 --> 00:20:11.240 align:start position:0% the second link you're gonna see the 00:20:11.240 --> 00:20:13.240 align:start position:0% the second link you're gonna see the same<00:20:11.480> excel<00:20:11.780> file<00:20:12.080> but<00:20:12.679> we<00:20:12.950> are<00:20:13.040> going<00:20:13.190> to 00:20:13.240 --> 00:20:13.250 align:start position:0% same excel file but we are going to 00:20:13.250 --> 00:20:15.909 align:start position:0% same excel file but we are going to accessor<00:20:13.640> 8<00:20:13.730> through<00:20:14.120> a<00:20:14.150> human<00:20:14.809> readable<00:20:15.020> name 00:20:15.909 --> 00:20:15.919 align:start position:0% accessor 8 through a human readable name 00:20:15.919 --> 00:20:17.560 align:start position:0% accessor 8 through a human readable name so<00:20:16.429> you<00:20:16.490> don't<00:20:16.669> have<00:20:16.790> to<00:20:16.970> remember<00:20:17.210> anymore 00:20:17.560 --> 00:20:17.570 align:start position:0% so you don't have to remember anymore 00:20:17.570 --> 00:20:20.470 align:start position:0% so you don't have to remember anymore ipfs<00:20:18.140> gateway<00:20:18.470> urls<00:20:18.799> or<00:20:19.090> ipfs<00:20:20.090> call<00:20:20.330> air 00:20:20.470 --> 00:20:20.480 align:start position:0% ipfs gateway urls or ipfs call air 00:20:20.480 --> 00:20:24.370 align:start position:0% ipfs gateway urls or ipfs call air hashes<00:20:20.929> okay<00:20:21.350> so<00:20:21.799> you<00:20:22.490> guys<00:20:22.700> should<00:20:23.030> go<00:20:23.380> post 00:20:24.370 --> 00:20:24.380 align:start position:0% hashes okay so you guys should go post 00:20:24.380 --> 00:20:27.370 align:start position:0% hashes okay so you guys should go post your<00:20:24.559> own<00:20:24.590> decent<00:20:25.309> revised<00:20:25.700> ab<00:20:25.940> and<00:20:26.290> trace<00:20:27.290> a 00:20:27.370 --> 00:20:27.380 align:start position:0% your own decent revised ab and trace a 00:20:27.380 --> 00:20:28.840 align:start position:0% your own decent revised ab and trace a quick<00:20:27.559> tutorial<00:20:27.710> if<00:20:28.250> you<00:20:28.280> want<00:20:28.610> to<00:20:28.700> take<00:20:28.820> a 00:20:28.840 --> 00:20:28.850 align:start position:0% quick tutorial if you want to take a 00:20:28.850 --> 00:20:31.840 align:start position:0% quick tutorial if you want to take a look<00:20:29.000> about<00:20:29.240> how<00:20:29.600> this<00:20:29.750> works<00:20:29.990> and<00:20:30.919> one<00:20:31.700> thing 00:20:31.840 --> 00:20:31.850 align:start position:0% look about how this works and one thing 00:20:31.850 --> 00:20:34.299 align:start position:0% look about how this works and one thing i<00:20:31.940> would<00:20:32.000> like<00:20:32.090> to<00:20:32.330> add<00:20:32.480> is<00:20:33.070> we're<00:20:34.070> going<00:20:34.220> to 00:20:34.299 --> 00:20:34.309 align:start position:0% i would like to add is we're going to 00:20:34.309 --> 00:20:38.350 align:start position:0% i would like to add is we're going to add<00:20:34.520> a<00:20:34.910> list<00:20:35.450> of<00:20:35.780> available<00:20:36.650> gateways<00:20:37.309> if<00:20:38.059> one 00:20:38.350 --> 00:20:38.360 align:start position:0% add a list of available gateways if one 00:20:38.360 --> 00:20:39.700 align:start position:0% add a list of available gateways if one of<00:20:38.480> the<00:20:38.570> gig<00:20:38.750> which<00:20:38.900> goes<00:20:39.110> down<00:20:39.320> we<00:20:39.559> will 00:20:39.700 --> 00:20:39.710 align:start position:0% of the gig which goes down we will 00:20:39.710 --> 00:20:41.770 align:start position:0% of the gig which goes down we will follow<00:20:39.919> up<00:20:40.010> to<00:20:40.190> a<00:20:40.220> newer<00:20:40.429> one<00:20:40.610> and<00:20:40.880> you<00:20:41.600> can 00:20:41.770 --> 00:20:41.780 align:start position:0% follow up to a newer one and you can 00:20:41.780 --> 00:20:44.289 align:start position:0% follow up to a newer one and you can also<00:20:41.929> set<00:20:42.320> your<00:20:42.350> own<00:20:42.559> ipfs<00:20:43.280> gateway<00:20:43.700> so<00:20:44.000> that's 00:20:44.289 --> 00:20:44.299 align:start position:0% also set your own ipfs gateway so that's 00:20:44.299 --> 00:20:47.530 align:start position:0% also set your own ipfs gateway so that's pretty<00:20:44.450> cool<00:20:44.570> you<00:20:44.690> have<00:20:44.840> options 00:20:47.530 --> 00:20:47.540 align:start position:0% 00:20:47.540 --> 00:20:50.440 align:start position:0% so<00:20:47.929> that's<00:20:48.200> it<00:20:48.290> for<00:20:48.410> oil<00:20:48.679> we're<00:20:49.640> gonna<00:20:49.790> launch 00:20:50.440 --> 00:20:50.450 align:start position:0% so that's it for oil we're gonna launch 00:20:50.450 --> 00:20:52.810 align:start position:0% so that's it for oil we're gonna launch our<00:20:50.630> public<00:20:51.080> beta<00:20:51.200> early<00:20:51.830> next<00:20:51.980> year<00:20:52.070> for 00:20:52.810 --> 00:20:52.820 align:start position:0% our public beta early next year for 00:20:52.820 --> 00:20:55.450 align:start position:0% our public beta early next year for Android<00:20:53.299> and<00:20:53.390> iOS<00:20:53.510> and<00:20:53.960> before<00:20:54.919> you<00:20:55.010> guys<00:20:55.130> ask 00:20:55.450 --> 00:20:55.460 align:start position:0% Android and iOS and before you guys ask 00:20:55.460 --> 00:21:02.020 align:start position:0% Android and iOS and before you guys ask it's<00:20:55.790> gonna<00:20:55.940> be<00:20:56.120> open<00:20:56.240> source 00:21:02.020 --> 00:21:02.030 align:start position:0% 00:21:02.030 --> 00:21:05.740 align:start position:0% also<00:21:02.900> we<00:21:03.860> are<00:21:03.920> hiring<00:21:04.190> so<00:21:04.700> if<00:21:05.180> you<00:21:05.270> guys<00:21:05.450> feel 00:21:05.740 --> 00:21:05.750 align:start position:0% also we are hiring so if you guys feel 00:21:05.750 --> 00:21:07.870 align:start position:0% also we are hiring so if you guys feel like<00:21:05.780> you<00:21:06.590> fight<00:21:06.950> with<00:21:07.160> any<00:21:07.340> of<00:21:07.490> these<00:21:07.610> roles 00:21:07.870 --> 00:21:07.880 align:start position:0% like you fight with any of these roles 00:21:07.880 --> 00:21:10.930 align:start position:0% like you fight with any of these roles please<00:21:08.570> shoot<00:21:08.840> us<00:21:08.990> an<00:21:09.110> email<00:21:09.230> or<00:21:09.710> reach<00:21:10.700> out<00:21:10.880> to 00:21:10.930 --> 00:21:10.940 align:start position:0% please shoot us an email or reach out to 00:21:10.940 --> 00:21:12.910 align:start position:0% please shoot us an email or reach out to any<00:21:11.240> of<00:21:11.360> us<00:21:11.510> we're<00:21:12.050> gonna<00:21:12.170> still<00:21:12.470> be<00:21:12.560> around 00:21:12.910 --> 00:21:12.920 align:start position:0% any of us we're gonna still be around 00:21:12.920 --> 00:21:15.610 align:start position:0% any of us we're gonna still be around for<00:21:13.130> the<00:21:13.190> rest<00:21:13.280> of<00:21:13.430> the<00:21:13.490> conference<00:21:13.910> and<00:21:14.620> the 00:21:15.610 --> 00:21:15.620 align:start position:0% for the rest of the conference and the 00:21:15.620 --> 00:21:17.950 align:start position:0% for the rest of the conference and the very<00:21:15.830> last<00:21:16.070> thing<00:21:16.480> we<00:21:17.480> will<00:21:17.570> love<00:21:17.810> your 00:21:17.950 --> 00:21:17.960 align:start position:0% very last thing we will love your 00:21:17.960 --> 00:21:20.200 align:start position:0% very last thing we will love your feedback<00:21:18.200> so<00:21:18.830> if<00:21:19.250> you<00:21:19.400> guys<00:21:19.550> have<00:21:19.850> some<00:21:20.030> time 00:21:20.200 --> 00:21:20.210 align:start position:0% feedback so if you guys have some time 00:21:20.210 --> 00:21:22.840 align:start position:0% feedback so if you guys have some time please<00:21:20.510> scan<00:21:20.840> this<00:21:20.990> QR<00:21:21.140> code<00:21:21.320> and<00:21:21.770> take<00:21:22.700> this 00:21:22.840 --> 00:21:22.850 align:start position:0% please scan this QR code and take this 00:21:22.850 --> 00:21:24.940 align:start position:0% please scan this QR code and take this quick<00:21:23.240> survey<00:21:23.630> that<00:21:23.840> is<00:21:24.020> going<00:21:24.170> to<00:21:24.230> help<00:21:24.380> up<00:21:24.560> it 00:21:24.940 --> 00:21:24.950 align:start position:0% quick survey that is going to help up it 00:21:24.950 --> 00:21:28.030 align:start position:0% quick survey that is going to help up it help<00:21:25.190> us<00:21:25.460> build<00:21:25.760> better<00:21:25.970> products<00:21:26.920> but<00:21:27.920> in 00:21:28.030 --> 00:21:28.040 align:start position:0% help us build better products but in 00:21:28.040 --> 00:21:29.800 align:start position:0% help us build better products but in exchange<00:21:28.220> of<00:21:28.520> that<00:21:28.700> we're<00:21:29.210> going<00:21:29.450> to<00:21:29.600> choose 00:21:29.800 --> 00:21:29.810 align:start position:0% exchange of that we're going to choose 00:21:29.810 --> 00:21:32.440 align:start position:0% exchange of that we're going to choose lucky<00:21:30.800> winners<00:21:31.100> and<00:21:31.400> we're<00:21:31.700> going<00:21:31.910> to<00:21:31.970> let<00:21:32.240> you 00:21:32.440 --> 00:21:32.450 align:start position:0% lucky winners and we're going to let you 00:21:32.450 --> 00:21:35.020 align:start position:0% lucky winners and we're going to let you pick<00:21:32.720> any<00:21:32.990> item<00:21:33.350> from<00:21:33.380> our<00:21:33.710> new<00:21:34.400> swag<00:21:34.700> store 00:21:35.020 --> 00:21:35.030 align:start position:0% pick any item from our new swag store 00:21:35.030 --> 00:21:38.860 align:start position:0% pick any item from our new swag store swag<00:21:35.570> does<00:21:35.780> Madame<00:21:36.080> s<00:21:36.200> dot<00:21:36.410> IO<00:21:36.560> and<00:21:37.720> that's<00:21:38.720> it 00:21:38.860 --> 00:21:38.870 align:start position:0% swag does Madame s dot IO and that's it 00:21:38.870 --> 00:21:48.190 align:start position:0% swag does Madame s dot IO and that's it thank<00:21:39.110> you<00:21:45.280> I<00:21:46.280> don't<00:21:47.180> know<00:21:47.330> if<00:21:47.360> anyone<00:21:47.810> has<00:21:47.990> any 00:21:48.190 --> 00:21:48.200 align:start position:0% thank you I don't know if anyone has any 00:21:48.200 --> 00:21:53.130 align:start position:0% thank you I don't know if anyone has any questions<00:21:48.350> or<00:21:50.140> should<00:21:51.140> we<00:21:51.230> take<00:21:51.440> questions 00:21:53.130 --> 00:21:53.140 align:start position:0% questions or should we take questions 00:21:53.140 --> 00:21:54.970 align:start position:0% questions or should we take questions yeah<00:21:54.140> we've<00:21:54.260> got<00:21:54.380> a<00:21:54.410> couple<00:21:54.620> minutes<00:21:54.740> for 00:21:54.970 --> 00:21:54.980 align:start position:0% yeah we've got a couple minutes for 00:21:54.980 --> 00:21:55.870 align:start position:0% yeah we've got a couple minutes for questions<00:21:55.220> if<00:21:55.310> people<00:21:55.460> want<00:21:55.610> we've<00:21:55.730> got<00:21:55.850> a 00:21:55.870 --> 00:21:55.880 align:start position:0% questions if people want we've got a 00:21:55.880 --> 00:22:01.990 align:start position:0% questions if people want we've got a hand<00:21:56.150> over<00:21:56.360> there<00:22:00.460> you<00:22:01.460> got<00:22:01.520> a<00:22:01.610> question<00:22:01.790> are 00:22:01.990 --> 00:22:02.000 align:start position:0% hand over there you got a question are 00:22:02.000 --> 00:22:04.780 align:start position:0% hand over there you got a question are you<00:22:02.090> waving<00:22:02.240> I<00:22:03.310> think<00:22:04.310> there's<00:22:04.460> a<00:22:04.520> mic<00:22:04.640> down 00:22:04.780 --> 00:22:04.790 align:start position:0% you waving I think there's a mic down 00:22:04.790 --> 00:22:11.890 align:start position:0% you waving I think there's a mic down front<00:22:05.030> if<00:22:05.120> you<00:22:05.210> want<00:22:05.330> to<00:22:05.390> come 00:22:11.890 --> 00:22:11.900 align:start position:0% 00:22:11.900 --> 00:22:17.510 align:start position:0% go<00:22:12.900> back<00:22:13.080> can't<00:22:13.770> oh<00:22:15.920> hi 00:22:17.510 --> 00:22:17.520 align:start position:0% go back can't oh hi 00:22:17.520 --> 00:22:21.800 align:start position:0% go back can't oh hi Dimitri<00:22:17.940> the<00:22:18.120> spell<00:22:18.300> of<00:22:18.380> gnosis<00:22:20.510> does<00:22:21.510> Madame 00:22:21.800 --> 00:22:21.810 align:start position:0% Dimitri the spell of gnosis does Madame 00:22:21.810 --> 00:22:27.560 align:start position:0% Dimitri the spell of gnosis does Madame ask<00:22:21.960> plans<00:22:22.320> to<00:22:22.920> move<00:22:23.900> from<00:22:24.900> extension<00:22:25.680> to<00:22:26.570> like 00:22:27.560 --> 00:22:27.570 align:start position:0% ask plans to move from extension to like 00:22:27.570 --> 00:22:32.530 align:start position:0% ask plans to move from extension to like from<00:22:27.870> being<00:22:28.080> a<00:22:28.230> browser<00:22:28.470> extension<00:22:28.620> to<00:22:29.580> more 00:22:32.530 --> 00:22:32.540 align:start position:0% 00:22:32.540 --> 00:22:35.660 align:start position:0% to<00:22:33.540> bigger<00:22:33.750> platform<00:22:34.020> like<00:22:34.530> an<00:22:34.710> electron<00:22:35.310> or 00:22:35.660 --> 00:22:35.670 align:start position:0% to bigger platform like an electron or 00:22:35.670 --> 00:22:39.530 align:start position:0% to bigger platform like an electron or or<00:22:36.440> chromium<00:22:37.440> to<00:22:38.430> have<00:22:38.940> it<00:22:39.060> like<00:22:39.240> a<00:22:39.270> full 00:22:39.530 --> 00:22:39.540 align:start position:0% or chromium to have it like a full 00:22:39.540 --> 00:22:41.570 align:start position:0% or chromium to have it like a full feature<00:22:39.750> control<00:22:40.230> over<00:22:40.740> the<00:22:40.890> content<00:22:41.070> of<00:22:41.430> the 00:22:41.570 --> 00:22:41.580 align:start position:0% feature control over the content of the 00:22:41.580 --> 00:22:45.710 align:start position:0% feature control over the content of the user<00:22:42.290> totally<00:22:43.290> we<00:22:43.560> have<00:22:44.510> discussed<00:22:45.510> in<00:22:45.690> the 00:22:45.710 --> 00:22:45.720 align:start position:0% user totally we have discussed in the 00:22:45.720 --> 00:22:46.630 align:start position:0% user totally we have discussed in the past 00:22:46.630 --> 00:22:46.640 align:start position:0% past 00:22:46.640 --> 00:22:48.860 align:start position:0% past bringing<00:22:47.640> madam<00:22:47.970> asked<00:22:48.090> to<00:22:48.300> electron<00:22:48.600> as<00:22:48.750> an 00:22:48.860 --> 00:22:48.870 align:start position:0% bringing madam asked to electron as an 00:22:48.870 --> 00:22:51.920 align:start position:0% bringing madam asked to electron as an electro<00:22:49.110> nap<00:22:49.580> it's<00:22:50.580> definitely<00:22:51.240> still<00:22:51.540> an 00:22:51.920 --> 00:22:51.930 align:start position:0% electro nap it's definitely still an 00:22:51.930 --> 00:22:54.290 align:start position:0% electro nap it's definitely still an impossibility<00:22:52.550> we're<00:22:53.550> not<00:22:53.700> sure<00:22:54.000> that<00:22:54.030> it 00:22:54.290 --> 00:22:54.300 align:start position:0% impossibility we're not sure that it 00:22:54.300 --> 00:22:56.780 align:start position:0% impossibility we're not sure that it will<00:22:54.450> make<00:22:55.350> more<00:22:55.650> people<00:22:55.950> use<00:22:56.400> metamath 00:22:56.780 --> 00:22:56.790 align:start position:0% will make more people use metamath 00:22:56.790 --> 00:22:58.160 align:start position:0% will make more people use metamath necessarily<00:22:57.390> or<00:22:57.510> bring<00:22:57.690> us<00:22:57.780> closer<00:22:58.050> to 00:22:58.160 --> 00:22:58.170 align:start position:0% necessarily or bring us closer to 00:22:58.170 --> 00:23:02.810 align:start position:0% necessarily or bring us closer to serving<00:22:58.710> gaps<00:22:58.920> better<00:23:00.110> but<00:23:01.110> it<00:23:01.410> is<00:23:01.710> still<00:23:02.550> yeah 00:23:02.810 --> 00:23:02.820 align:start position:0% serving gaps better but it is still yeah 00:23:02.820 --> 00:23:04.130 align:start position:0% serving gaps better but it is still yeah it's<00:23:02.970> it's<00:23:03.300> a<00:23:03.390> possibility<00:23:03.690> if<00:23:03.870> you<00:23:03.930> haven't 00:23:04.130 --> 00:23:04.140 align:start position:0% it's it's a possibility if you haven't 00:23:04.140 --> 00:23:06.500 align:start position:0% it's it's a possibility if you haven't ruled<00:23:04.230> it<00:23:04.350> out<00:23:04.410> for<00:23:04.620> sure<00:23:05.300> it's<00:23:06.300> not 00:23:06.500 --> 00:23:06.510 align:start position:0% ruled it out for sure it's not 00:23:06.510 --> 00:23:07.940 align:start position:0% ruled it out for sure it's not necessarily<00:23:07.020> on<00:23:07.140> this<00:23:07.320> list<00:23:07.560> of<00:23:07.680> stuff<00:23:07.920> that 00:23:07.940 --> 00:23:07.950 align:start position:0% necessarily on this list of stuff that 00:23:07.950 --> 00:23:09.860 align:start position:0% necessarily on this list of stuff that we<00:23:08.220> described<00:23:08.610> today<00:23:08.730> but<00:23:09.000> it<00:23:09.330> could<00:23:09.630> happen 00:23:09.860 --> 00:23:09.870 align:start position:0% we described today but it could happen 00:23:09.870 --> 00:23:11.060 align:start position:0% we described today but it could happen at<00:23:09.990> some<00:23:10.110> point<00:23:10.140> and<00:23:10.530> so<00:23:10.710> if<00:23:10.800> that's<00:23:10.890> something 00:23:11.060 --> 00:23:11.070 align:start position:0% at some point and so if that's something 00:23:11.070 --> 00:23:12.410 align:start position:0% at some point and so if that's something you're<00:23:11.190> interested<00:23:11.250> in<00:23:11.550> I<00:23:11.730> mean<00:23:11.850> we<00:23:11.910> engage 00:23:12.410 --> 00:23:12.420 align:start position:0% you're interested in I mean we engage 00:23:12.420 --> 00:23:13.430 align:start position:0% you're interested in I mean we engage with<00:23:12.540> a<00:23:12.630> lot<00:23:12.750> of<00:23:12.780> this<00:23:12.960> sort<00:23:13.050> of<00:23:13.140> stuff<00:23:13.230> on 00:23:13.430 --> 00:23:13.440 align:start position:0% with a lot of this sort of stuff on 00:23:13.440 --> 00:23:15.320 align:start position:0% with a lot of this sort of stuff on github<00:23:13.710> so<00:23:13.860> open<00:23:14.220> an<00:23:14.280> issue<00:23:14.430> there<00:23:15.060> is<00:23:15.150> one 00:23:15.320 --> 00:23:15.330 align:start position:0% github so open an issue there is one 00:23:15.330 --> 00:23:16.790 align:start position:0% github so open an issue there is one already<00:23:15.600> I<00:23:15.690> think<00:23:15.900> so<00:23:16.020> find<00:23:16.230> it<00:23:16.350> give<00:23:16.560> us<00:23:16.650> your 00:23:16.790 --> 00:23:16.800 align:start position:0% already I think so find it give us your 00:23:16.800 --> 00:23:17.930 align:start position:0% already I think so find it give us your thoughts<00:23:16.830> we'd<00:23:17.220> love<00:23:17.340> to<00:23:17.370> have<00:23:17.850> the 00:23:17.930 --> 00:23:17.940 align:start position:0% thoughts we'd love to have the 00:23:17.940 --> 00:23:21.770 align:start position:0% thoughts we'd love to have the discussion<00:23:19.610> hi 00:23:21.770 --> 00:23:21.780 align:start position:0% discussion hi 00:23:21.780 --> 00:23:24.530 align:start position:0% discussion hi I'm<00:23:22.140> willing<00:23:22.560> to<00:23:22.710> represent<00:23:23.030> squishy<00:23:24.030> of<00:23:24.180> LA 00:23:24.530 --> 00:23:24.540 align:start position:0% I'm willing to represent squishy of LA 00:23:24.540 --> 00:23:27.200 align:start position:0% I'm willing to represent squishy of LA token<00:23:24.930> we<00:23:25.710> are<00:23:25.800> top<00:23:26.070> 30<00:23:26.370> a<00:23:26.490> cryptic<00:23:27.150> exchange 00:23:27.200 --> 00:23:27.210 align:start position:0% token we are top 30 a cryptic exchange 00:23:27.210 --> 00:23:32.780 align:start position:0% token we are top 30 a cryptic exchange and<00:23:28.100> security<00:23:29.100> the<00:23:29.850> token<00:23:30.780> trading<00:23:31.230> leader<00:23:31.860> do 00:23:32.780 --> 00:23:32.790 align:start position:0% and security the token trading leader do 00:23:32.790 --> 00:23:35.270 align:start position:0% and security the token trading leader do you<00:23:32.820> have<00:23:33.090> any<00:23:33.240> plans<00:23:33.600> to<00:23:34.170> integrate<00:23:34.770> with 00:23:35.270 --> 00:23:35.280 align:start position:0% you have any plans to integrate with 00:23:35.280 --> 00:23:38.410 align:start position:0% you have any plans to integrate with decentralized<00:23:36.180> exchanges<00:23:37.050> so<00:23:37.590> we're 00:23:38.410 --> 00:23:38.420 align:start position:0% decentralized exchanges so we're 00:23:38.420 --> 00:23:41.570 align:start position:0% decentralized exchanges so we're launching<00:23:39.420> high<00:23:40.140> dps<00:23:40.680> decentralized 00:23:41.570 --> 00:23:41.580 align:start position:0% launching high dps decentralized 00:23:41.580 --> 00:23:48.290 align:start position:0% launching high dps decentralized exchange<00:23:42.680> where<00:23:45.830> people<00:23:46.830> can<00:23:47.190> sign<00:23:47.730> on<00:23:47.940> orders 00:23:48.290 --> 00:23:48.300 align:start position:0% exchange where people can sign on orders 00:23:48.300 --> 00:23:51.310 align:start position:0% exchange where people can sign on orders send<00:23:48.900> them<00:23:49.110> in<00:23:49.260> to<00:23:49.290> order<00:23:49.620> books<00:23:50.010> and<00:23:50.400> this 00:23:51.310 --> 00:23:51.320 align:start position:0% send them in to order books and this 00:23:51.320 --> 00:23:55.580 align:start position:0% send them in to order books and this transaction<00:23:52.320> will<00:23:52.740> be<00:23:52.920> written<00:23:53.780> into<00:23:54.780> smart 00:23:55.580 --> 00:23:55.590 align:start position:0% transaction will be written into smart 00:23:55.590 --> 00:23:58.070 align:start position:0% transaction will be written into smart contract<00:23:56.160> and<00:23:56.670> they<00:23:57.150> need<00:23:57.300> to<00:23:57.450> sign<00:23:57.720> their 00:23:58.070 --> 00:23:58.080 align:start position:0% contract and they need to sign their 00:23:58.080 --> 00:24:01.280 align:start position:0% contract and they need to sign their order<00:23:58.500> with<00:23:58.800> something<00:23:59.310> like<00:23:59.460> metal<00:23:59.880> mask<00:24:00.290> so 00:24:01.280 --> 00:24:01.290 align:start position:0% order with something like metal mask so 00:24:01.290 --> 00:24:04.240 align:start position:0% order with something like metal mask so any<00:24:01.560> plans<00:24:01.830> to<00:24:02.160> integrate<00:24:02.280> with<00:24:02.940> Dex 00:24:04.240 --> 00:24:04.250 align:start position:0% any plans to integrate with Dex 00:24:04.250 --> 00:24:06.620 align:start position:0% any plans to integrate with Dex integrate<00:24:05.250> by<00:24:05.490> pulling<00:24:05.880> them<00:24:06.000> into<00:24:06.210> the<00:24:06.450> meta 00:24:06.620 --> 00:24:06.630 align:start position:0% integrate by pulling them into the meta 00:24:06.630 --> 00:24:09.020 align:start position:0% integrate by pulling them into the meta mask<00:24:06.840> UI<00:24:07.470> is<00:24:07.860> that<00:24:08.010> what<00:24:08.100> you<00:24:08.160> mean<00:24:08.250> yeah<00:24:08.760> so 00:24:09.020 --> 00:24:09.030 align:start position:0% mask UI is that what you mean yeah so 00:24:09.030 --> 00:24:13.940 align:start position:0% mask UI is that what you mean yeah so you<00:24:09.090> can<00:24:09.450> send<00:24:10.010> sign<00:24:11.010> orders<00:24:11.490> from<00:24:12.380> meta<00:24:13.380> masks 00:24:13.940 --> 00:24:13.950 align:start position:0% you can send sign orders from meta masks 00:24:13.950 --> 00:24:17.480 align:start position:0% you can send sign orders from meta masks and<00:24:14.310> send<00:24:14.610> them<00:24:14.760> to<00:24:14.940> our<00:24:15.450> main<00:24:15.960> engine<00:24:16.530> totally 00:24:17.480 --> 00:24:17.490 align:start position:0% and send them to our main engine totally 00:24:17.490 --> 00:24:20.030 align:start position:0% and send them to our main engine totally so<00:24:17.820> we<00:24:18.240> have<00:24:18.360> a<00:24:18.390> very<00:24:18.720> bare-bones<00:24:19.170> integration 00:24:20.030 --> 00:24:20.040 align:start position:0% so we have a very bare-bones integration 00:24:20.040 --> 00:24:21.680 align:start position:0% so we have a very bare-bones integration with<00:24:20.220> shape<00:24:20.460> shift<00:24:20.700> that's<00:24:20.910> been<00:24:21.090> live<00:24:21.300> in 00:24:21.680 --> 00:24:21.690 align:start position:0% with shape shift that's been live in 00:24:21.690 --> 00:24:22.970 align:start position:0% with shape shift that's been live in madam<00:24:21.990> asked<00:24:22.110> for 00:24:22.970 --> 00:24:22.980 align:start position:0% madam asked for 00:24:22.980 --> 00:24:27.950 align:start position:0% madam asked for a<00:24:23.330> year<00:24:24.330> and<00:24:24.419> a<00:24:24.480> half<00:24:24.980> and<00:24:26.240> our<00:24:27.240> metrics<00:24:27.840> at 00:24:27.950 --> 00:24:27.960 align:start position:0% a year and a half and our metrics at 00:24:27.960 --> 00:24:29.990 align:start position:0% a year and a half and our metrics at this<00:24:28.049> point<00:24:28.230> are<00:24:28.290> very<00:24:28.590> very<00:24:28.970> young<00:24:29.970> and 00:24:29.990 --> 00:24:30.000 align:start position:0% this point are very very young and 00:24:30.000 --> 00:24:32.000 align:start position:0% this point are very very young and immature<00:24:30.299> but<00:24:30.600> we<00:24:30.690> do<00:24:30.960> know<00:24:31.140> that<00:24:31.169> fewer<00:24:31.919> than 00:24:32.000 --> 00:24:32.010 align:start position:0% immature but we do know that fewer than 00:24:32.010 --> 00:24:33.799 align:start position:0% immature but we do know that fewer than a<00:24:32.130> hundred<00:24:32.220> people<00:24:32.820> have<00:24:33.000> ever<00:24:33.270> used<00:24:33.630> that 00:24:33.799 --> 00:24:33.809 align:start position:0% a hundred people have ever used that 00:24:33.809 --> 00:24:35.570 align:start position:0% a hundred people have ever used that shapeshift<00:24:34.320> integration<00:24:34.740> which<00:24:35.190> is<00:24:35.340> pretty 00:24:35.570 --> 00:24:35.580 align:start position:0% shapeshift integration which is pretty 00:24:35.580 --> 00:24:38.330 align:start position:0% shapeshift integration which is pretty pretty<00:24:35.790> low<00:24:36.000> so<00:24:36.030> I<00:24:36.660> think<00:24:37.080> that<00:24:37.590> would<00:24:37.770> prop<00:24:38.160> we 00:24:38.330 --> 00:24:38.340 align:start position:0% pretty low so I think that would prop we 00:24:38.340 --> 00:24:39.650 align:start position:0% pretty low so I think that would prop we could<00:24:38.520> probably<00:24:38.790> build<00:24:39.090> some<00:24:39.299> it<00:24:39.419> would<00:24:39.540> be<00:24:39.630> a 00:24:39.650 --> 00:24:39.660 align:start position:0% could probably build some it would be a 00:24:39.660 --> 00:24:41.299 align:start position:0% could probably build some it would be a wonderful<00:24:40.080> experience<00:24:40.260> but<00:24:40.740> in<00:24:40.890> terms<00:24:41.100> of<00:24:41.190> the 00:24:41.299 --> 00:24:41.309 align:start position:0% wonderful experience but in terms of the 00:24:41.309 --> 00:24:43.820 align:start position:0% wonderful experience but in terms of the whole<00:24:41.549> range<00:24:42.030> of<00:24:42.270> like<00:24:42.960> critical<00:24:43.320> stuff<00:24:43.650> there 00:24:43.820 --> 00:24:43.830 align:start position:0% whole range of like critical stuff there 00:24:43.830 --> 00:24:46.400 align:start position:0% whole range of like critical stuff there is<00:24:43.860> to<00:24:44.309> do<00:24:44.460> out<00:24:44.640> there<00:24:44.850> that<00:24:45.450> hasn't<00:24:45.900> you<00:24:46.380> know 00:24:46.400 --> 00:24:46.410 align:start position:0% is to do out there that hasn't you know 00:24:46.410 --> 00:24:48.320 align:start position:0% is to do out there that hasn't you know risen<00:24:46.860> to<00:24:47.010> the<00:24:47.130> to<00:24:47.370> the<00:24:47.460> top<00:24:47.580> of<00:24:47.700> the<00:24:47.760> list<00:24:47.910> but 00:24:48.320 --> 00:24:48.330 align:start position:0% risen to the to the top of the list but 00:24:48.330 --> 00:24:49.280 align:start position:0% risen to the to the top of the list but I<00:24:48.390> will<00:24:48.540> say<00:24:48.630> the<00:24:48.750> same<00:24:48.900> thing<00:24:49.080> to<00:24:49.169> you<00:24:49.260> that 00:24:49.280 --> 00:24:49.290 align:start position:0% I will say the same thing to you that 00:24:49.290 --> 00:24:50.870 align:start position:0% I will say the same thing to you that said<00:24:49.860> to<00:24:49.950> the<00:24:50.040> previous<00:24:50.309> gentleman<00:24:50.429> which<00:24:50.730> is 00:24:50.870 --> 00:24:50.880 align:start position:0% said to the previous gentleman which is 00:24:50.880 --> 00:24:53.180 align:start position:0% said to the previous gentleman which is we<00:24:51.809> pay<00:24:52.080> a<00:24:52.110> lot<00:24:52.260> of<00:24:52.440> attention<00:24:52.590> to<00:24:52.950> what<00:24:53.160> people 00:24:53.180 --> 00:24:53.190 align:start position:0% we pay a lot of attention to what people 00:24:53.190 --> 00:24:55.130 align:start position:0% we pay a lot of attention to what people in<00:24:53.490> the<00:24:53.549> community<00:24:53.880> seem<00:24:54.150> to<00:24:54.360> be<00:24:54.450> enthusiastic 00:24:55.130 --> 00:24:55.140 align:start position:0% in the community seem to be enthusiastic 00:24:55.140 --> 00:24:57.680 align:start position:0% in the community seem to be enthusiastic about<00:24:55.200> so<00:24:55.610> engage<00:24:56.610> us<00:24:56.760> again<00:24:57.000> on<00:24:57.120> github<00:24:57.480> open 00:24:57.680 --> 00:24:57.690 align:start position:0% about so engage us again on github open 00:24:57.690 --> 00:24:59.450 align:start position:0% about so engage us again on github open an<00:24:57.750> issue<00:24:57.870> start<00:24:58.470> the<00:24:58.559> discussion<00:24:58.950> and<00:24:59.100> we'll 00:24:59.450 --> 00:24:59.460 align:start position:0% an issue start the discussion and we'll 00:24:59.460 --> 00:25:01.669 align:start position:0% an issue start the discussion and we'll see<00:24:59.549> what<00:24:59.669> happens<00:24:59.940> up<00:25:00.540> my<00:25:00.990> recommendation 00:25:01.669 --> 00:25:01.679 align:start position:0% see what happens up my recommendation 00:25:01.679 --> 00:25:04.430 align:start position:0% see what happens up my recommendation for<00:25:01.830> that<00:25:01.860> is<00:25:02.190> so<00:25:02.340> to<00:25:02.580> make<00:25:02.820> sure<00:25:02.850> that<00:25:03.440> your 00:25:04.430 --> 00:25:04.440 align:start position:0% for that is so to make sure that your 00:25:04.440 --> 00:25:06.980 align:start position:0% for that is so to make sure that your product<00:25:05.100> or<00:25:05.280> exchange<00:25:05.700> or<00:25:05.850> whatever<00:25:06.120> is<00:25:06.419> more 00:25:06.980 --> 00:25:06.990 align:start position:0% product or exchange or whatever is more 00:25:06.990 --> 00:25:08.780 align:start position:0% product or exchange or whatever is more friendly<00:25:07.290> and<00:25:07.740> it's<00:25:08.130> gonna<00:25:08.280> work<00:25:08.460> fine<00:25:08.730> a 00:25:08.780 --> 00:25:08.790 align:start position:0% friendly and it's gonna work fine a 00:25:08.790 --> 00:25:11.450 align:start position:0% friendly and it's gonna work fine a mohel<00:25:09.150> app<00:25:09.330> so<00:25:09.809> you<00:25:10.530> know<00:25:10.620> if<00:25:10.890> you<00:25:11.100> do<00:25:11.220> a<00:25:11.250> good 00:25:11.450 --> 00:25:11.460 align:start position:0% mohel app so you know if you do a good 00:25:11.460 --> 00:25:13.280 align:start position:0% mohel app so you know if you do a good job<00:25:11.520> people<00:25:12.120> naturally<00:25:12.299> go<00:25:12.720> and<00:25:12.960> use<00:25:13.110> it 00:25:13.280 --> 00:25:13.290 align:start position:0% job people naturally go and use it 00:25:13.290 --> 00:25:15.230 align:start position:0% job people naturally go and use it through<00:25:13.500> the<00:25:14.130> madam<00:25:14.370> of<00:25:14.460> mobile<00:25:14.700> app<00:25:14.850> or<00:25:15.030> any 00:25:15.230 --> 00:25:15.240 align:start position:0% through the madam of mobile app or any 00:25:15.240 --> 00:25:17.980 align:start position:0% through the madam of mobile app or any other<00:25:15.450> option 00:25:17.980 --> 00:25:17.990 align:start position:0% 00:25:17.990 --> 00:25:21.590 align:start position:0% hello<00:25:18.990> I've<00:25:19.830> been<00:25:20.130> using<00:25:20.520> signature<00:25:21.270> schemes 00:25:21.590 --> 00:25:21.600 align:start position:0% hello I've been using signature schemes 00:25:21.600 --> 00:25:23.240 align:start position:0% hello I've been using signature schemes for<00:25:21.809> a<00:25:21.870> long<00:25:21.990> time<00:25:22.230> and<00:25:22.470> a<00:25:22.620> IP<00:25:22.919> cement 00:25:23.240 --> 00:25:23.250 align:start position:0% for a long time and a IP cement 00:25:23.250 --> 00:25:25.159 align:start position:0% for a long time and a IP cement relatives<00:25:23.549> are<00:25:23.700> very<00:25:23.880> good<00:25:24.150> thing<00:25:24.419> for<00:25:24.660> our 00:25:25.159 --> 00:25:25.169 align:start position:0% relatives are very good thing for our 00:25:25.169 --> 00:25:27.530 align:start position:0% relatives are very good thing for our users<00:25:25.890> to<00:25:25.919> be<00:25:26.130> able<00:25:26.280> to<00:25:26.400> sign<00:25:26.669> complex<00:25:27.150> message 00:25:27.530 --> 00:25:27.540 align:start position:0% users to be able to sign complex message 00:25:27.540 --> 00:25:28.810 align:start position:0% users to be able to sign complex message in<00:25:28.020> a<00:25:28.110> clear<00:25:28.380> way 00:25:28.810 --> 00:25:28.820 align:start position:0% in a clear way 00:25:28.820 --> 00:25:30.919 align:start position:0% in a clear way thanks<00:25:29.820> to<00:25:29.940> youth<00:25:30.090> from<00:25:30.299> it<00:25:30.419> amassed<00:25:30.660> or 00:25:30.919 --> 00:25:30.929 align:start position:0% thanks to youth from it amassed or 00:25:30.929 --> 00:25:33.080 align:start position:0% thanks to youth from it amassed or providing<00:25:31.500> this<00:25:31.590> because<00:25:31.890> web<00:25:32.100> 3gs<00:25:32.669> doesn't 00:25:33.080 --> 00:25:33.090 align:start position:0% providing this because web 3gs doesn't 00:25:33.090 --> 00:25:34.850 align:start position:0% providing this because web 3gs doesn't provide<00:25:33.330> an<00:25:33.510> interface<00:25:33.809> based<00:25:34.230> in<00:25:34.350> nature<00:25:34.590> so 00:25:34.850 --> 00:25:34.860 align:start position:0% provide an interface based in nature so 00:25:34.860 --> 00:25:38.210 align:start position:0% provide an interface based in nature so good<00:25:35.610> job<00:25:35.990> except<00:25:36.990> your<00:25:37.590> complainant<00:25:38.100> with 00:25:38.210 --> 00:25:38.220 align:start position:0% good job except your complainant with 00:25:38.220 --> 00:25:39.860 align:start position:0% good job except your complainant with trace<00:25:38.490> or<00:25:38.640> nature<00:25:38.940> but<00:25:39.330> Twitter<00:25:39.540> and<00:25:39.750> ledger 00:25:39.860 --> 00:25:39.870 align:start position:0% trace or nature but Twitter and ledger 00:25:39.870 --> 00:25:41.720 align:start position:0% trace or nature but Twitter and ledger are<00:25:40.020> not<00:25:40.230> able<00:25:40.500> to<00:25:40.650> do<00:25:41.070> this<00:25:41.309> kind<00:25:41.580> of 00:25:41.720 --> 00:25:41.730 align:start position:0% are not able to do this kind of 00:25:41.730 --> 00:25:44.030 align:start position:0% are not able to do this kind of signature<00:25:42.059> right<00:25:42.390> now<00:25:42.570> so<00:25:43.110> when<00:25:43.440> we<00:25:43.770> have<00:25:43.919> the 00:25:44.030 --> 00:25:44.040 align:start position:0% signature right now so when we have the 00:25:44.040 --> 00:25:46.130 align:start position:0% signature right now so when we have the full<00:25:44.220> user<00:25:44.460> experience<00:25:44.970> 712<00:25:45.540> signature<00:25:45.929> we've 00:25:46.130 --> 00:25:46.140 align:start position:0% full user experience 712 signature we've 00:25:46.140 --> 00:25:48.830 align:start position:0% full user experience 712 signature we've ledger<00:25:46.350> great<00:25:47.309> question<00:25:47.700> I'm<00:25:47.880> hoping<00:25:48.270> that<00:25:48.540> by 00:25:48.830 --> 00:25:48.840 align:start position:0% ledger great question I'm hoping that by 00:25:48.840 --> 00:25:50.330 align:start position:0% ledger great question I'm hoping that by asking<00:25:49.200> that<00:25:49.320> question<00:25:49.500> we<00:25:49.860> will<00:25:50.040> encourage 00:25:50.330 --> 00:25:50.340 align:start position:0% asking that question we will encourage 00:25:50.340 --> 00:25:53.150 align:start position:0% asking that question we will encourage treasure<00:25:50.970> and<00:25:51.210> ledger<00:25:51.360> to<00:25:52.010> help<00:25:53.010> their 00:25:53.150 --> 00:25:53.160 align:start position:0% treasure and ledger to help their 00:25:53.160 --> 00:25:54.799 align:start position:0% treasure and ledger to help their hardware<00:25:53.429> wallets<00:25:53.640> support<00:25:54.030> scientist<00:25:54.510> at<00:25:54.630> v3 00:25:54.799 --> 00:25:54.809 align:start position:0% hardware wallets support scientist at v3 00:25:54.809 --> 00:25:57.320 align:start position:0% hardware wallets support scientist at v3 I<00:25:55.799> don't<00:25:56.549> know<00:25:56.610> if<00:25:56.669> runo's<00:25:56.910> anything<00:25:57.179> cloud 00:25:57.320 --> 00:25:57.330 align:start position:0% I don't know if runo's anything cloud 00:25:57.330 --> 00:25:59.780 align:start position:0% I don't know if runo's anything cloud yeah<00:25:57.600> there<00:25:57.840> are<00:25:57.990> open<00:25:58.380> issues<00:25:58.710> on<00:25:58.950> dresser 00:25:59.780 --> 00:25:59.790 align:start position:0% yeah there are open issues on dresser 00:25:59.790 --> 00:26:02.570 align:start position:0% yeah there are open issues on dresser and<00:26:00.059> ledger<00:26:00.320> repos<00:26:01.320> about<00:26:01.740> that<00:26:01.890> you<00:26:02.460> know 00:26:02.570 --> 00:26:02.580 align:start position:0% and ledger repos about that you know 00:26:02.580 --> 00:26:05.780 align:start position:0% and ledger repos about that you know it's<00:26:02.730> out<00:26:02.910> of<00:26:02.940> our<00:26:03.360> control<00:26:03.600> but<00:26:04.340> just<00:26:05.340> about 00:26:05.780 --> 00:26:05.790 align:start position:0% it's out of our control but just about 00:26:05.790 --> 00:26:07.700 align:start position:0% it's out of our control but just about their<00:26:06.000> issues<00:26:06.150> and<00:26:06.630> at<00:26:07.020> some<00:26:07.290> point<00:26:07.500> is<00:26:07.590> gonna 00:26:07.700 --> 00:26:07.710 align:start position:0% their issues and at some point is gonna 00:26:07.710 --> 00:26:09.289 align:start position:0% their issues and at some point is gonna happen<00:26:07.860> I<00:26:08.040> think<00:26:08.280> there<00:26:08.520> I'm<00:26:09.030> pretty<00:26:09.179> sure 00:26:09.289 --> 00:26:09.299 align:start position:0% happen I think there I'm pretty sure 00:26:09.299 --> 00:26:11.150 align:start position:0% happen I think there I'm pretty sure they're<00:26:09.480> the<00:26:09.660> stuff<00:26:09.840> is<00:26:10.020> open<00:26:10.260> source<00:26:10.500> to<00:26:10.860> so 00:26:11.150 --> 00:26:11.160 align:start position:0% they're the stuff is open source to so 00:26:11.160 --> 00:26:13.280 align:start position:0% they're the stuff is open source to so if<00:26:11.429> anyone<00:26:11.850> you<00:26:12.030> know<00:26:12.150> has<00:26:12.450> the<00:26:12.780> time<00:26:12.990> and<00:26:13.230> the 00:26:13.280 --> 00:26:13.290 align:start position:0% if anyone you know has the time and the 00:26:13.290 --> 00:26:14.030 align:start position:0% if anyone you know has the time and the will<00:26:13.410> to<00:26:13.590> do<00:26:13.710> it 00:26:14.030 --> 00:26:14.040 align:start position:0% will to do it 00:26:14.040 --> 00:26:17.060 align:start position:0% will to do it you<00:26:14.309> can<00:26:14.520> country<00:26:15.440> thank<00:26:16.440> you<00:26:16.530> for<00:26:16.650> asking 00:26:17.060 --> 00:26:17.070 align:start position:0% you can country thank you for asking 00:26:17.070 --> 00:26:20.299 align:start position:0% you can country thank you for asking hi<00:26:17.940> guys<00:26:18.150> Everett<00:26:19.049> um<00:26:19.200> from<00:26:19.410> the<00:26:19.590> mist<00:26:19.860> project 00:26:20.299 --> 00:26:20.309 align:start position:0% hi guys Everett um from the mist project 00:26:20.309 --> 00:26:23.060 align:start position:0% hi guys Everett um from the mist project Congrats<00:26:21.179> on<00:26:21.299> your<00:26:21.360> progress<00:26:22.290> is<00:26:22.590> really 00:26:23.060 --> 00:26:23.070 align:start position:0% Congrats on your progress is really 00:26:23.070 --> 00:26:28.090 align:start position:0% Congrats on your progress is really amazing<00:26:23.429> do<00:26:24.390> you<00:26:24.450> have<00:26:24.630> plans<00:26:25.020> to<00:26:25.350> add<00:26:25.730> IPF<00:26:26.730> as 00:26:28.090 --> 00:26:28.100 align:start position:0% amazing do you have plans to add IPF as 00:26:28.100 --> 00:26:32.180 align:start position:0% amazing do you have plans to add IPF as routing<00:26:29.100> to<00:26:29.369> the<00:26:29.659> backstop<00:26:30.659> experience<00:26:31.190> as 00:26:32.180 --> 00:26:32.190 align:start position:0% routing to the backstop experience as 00:26:32.190 --> 00:26:40.249 align:start position:0% routing to the backstop experience as well<00:26:32.429> I<00:26:32.669> heard<00:26:33.659> that<00:26:33.749> man<00:26:35.419> so<00:26:36.419> we<00:26:36.570> do<00:26:36.869> have<00:26:37.080> a<00:26:39.259> a 00:26:40.249 --> 00:26:40.259 align:start position:0% well I heard that man so we do have a a 00:26:40.259 --> 00:26:44.210 align:start position:0% well I heard that man so we do have a a pretty<00:26:41.159> rudimentary<00:26:41.869> ipfs<00:26:42.869> resolution<00:26:43.470> or<00:26:44.039> at 00:26:44.210 --> 00:26:44.220 align:start position:0% pretty rudimentary ipfs resolution or at 00:26:44.220 --> 00:26:46.159 align:start position:0% pretty rudimentary ipfs resolution or at least<00:26:44.340> ENS<00:26:44.730> domain<00:26:45.119> name<00:26:45.240> resolution<00:26:45.690> in<00:26:45.899> the 00:26:46.159 --> 00:26:46.169 align:start position:0% least ENS domain name resolution in the 00:26:46.169 --> 00:26:48.080 align:start position:0% least ENS domain name resolution in the browser<00:26:46.350> extension<00:26:46.889> it's<00:26:47.309> not<00:26:47.490> quite<00:26:47.730> as<00:26:47.850> full 00:26:48.080 --> 00:26:48.090 align:start position:0% browser extension it's not quite as full 00:26:48.090 --> 00:26:49.220 align:start position:0% browser extension it's not quite as full featured<00:26:48.179> as<00:26:48.419> what<00:26:48.570> Brunner<00:26:48.840> just<00:26:48.990> showed<00:26:49.110> in 00:26:49.220 --> 00:26:49.230 align:start position:0% featured as what Brunner just showed in 00:26:49.230 --> 00:26:52.879 align:start position:0% featured as what Brunner just showed in mobile<00:26:49.559> I<00:26:49.740> don't<00:26:50.279> think<00:26:50.429> it<00:26:50.580> actually<00:26:51.379> so<00:26:52.379> yeah 00:26:52.879 --> 00:26:52.889 align:start position:0% mobile I don't think it actually so yeah 00:26:52.889 --> 00:26:55.369 align:start position:0% mobile I don't think it actually so yeah so<00:26:53.429> basically<00:26:54.240> the<00:26:54.539> main<00:26:54.629> difference<00:26:55.049> between 00:26:55.369 --> 00:26:55.379 align:start position:0% so basically the main difference between 00:26:55.379 --> 00:26:56.749 align:start position:0% so basically the main difference between what<00:26:55.799> we<00:26:55.919> have<00:26:55.950> on<00:26:56.190> this<00:26:56.249> station<00:26:56.460> right<00:26:56.639> now 00:26:56.749 --> 00:26:56.759 align:start position:0% what we have on this station right now 00:26:56.759 --> 00:27:00.080 align:start position:0% what we have on this station right now and<00:26:57.149> what<00:26:57.419> we<00:26:57.629> have<00:26:58.320> moil<00:26:58.799> is<00:26:58.950> that<00:26:59.159> because 00:27:00.080 --> 00:27:00.090 align:start position:0% and what we have moil is that because 00:27:00.090 --> 00:27:02.330 align:start position:0% and what we have moil is that because browser<00:27:00.480> restrictions<00:27:01.080> on<00:27:01.200> the<00:27:01.289> extension<00:27:01.649> we 00:27:02.330 --> 00:27:02.340 align:start position:0% browser restrictions on the extension we 00:27:02.340 --> 00:27:05.029 align:start position:0% browser restrictions on the extension we can<00:27:02.580> we<00:27:02.970> can<00:27:03.119> know<00:27:03.360> we<00:27:03.690> can<00:27:03.869> you<00:27:04.499> know<00:27:04.619> change 00:27:05.029 --> 00:27:05.039 align:start position:0% can we can know we can you know change 00:27:05.039 --> 00:27:07.879 align:start position:0% can we can know we can you know change the<00:27:05.610> URL<00:27:05.940> right<00:27:06.179> so<00:27:06.509> we<00:27:06.869> cannot<00:27:07.110> mask<00:27:07.379> that<00:27:07.559> so 00:27:07.879 --> 00:27:07.889 align:start position:0% the URL right so we cannot mask that so 00:27:07.889 --> 00:27:09.889 align:start position:0% the URL right so we cannot mask that so you<00:27:07.980> will<00:27:08.220> still<00:27:08.639> we<00:27:08.909> will<00:27:09.029> do<00:27:09.179> a<00:27:09.210> redirect<00:27:09.480> and 00:27:09.889 --> 00:27:09.899 align:start position:0% you will still we will do a redirect and 00:27:09.899 --> 00:27:13.249 align:start position:0% you will still we will do a redirect and you<00:27:10.230> will<00:27:10.350> see<00:27:10.559> you<00:27:10.619> the<00:27:10.769> IPF<00:27:11.100> sio<00:27:11.369> URL<00:27:11.940> in<00:27:12.840> the 00:27:13.249 --> 00:27:13.259 align:start position:0% you will see you the IPF sio URL in the 00:27:13.259 --> 00:27:15.619 align:start position:0% you will see you the IPF sio URL in the mold<00:27:13.619> rouser<00:27:13.860> the<00:27:14.669> more<00:27:14.999> lab<00:27:15.210> we<00:27:15.360> have<00:27:15.480> way 00:27:15.619 --> 00:27:15.629 align:start position:0% mold rouser the more lab we have way 00:27:15.629 --> 00:27:17.359 align:start position:0% mold rouser the more lab we have way more<00:27:15.659> control<00:27:16.200> of<00:27:16.230> that<00:27:16.440> that's<00:27:16.740> what<00:27:16.919> we<00:27:17.100> are 00:27:17.359 --> 00:27:17.369 align:start position:0% more control of that that's what we are 00:27:17.369 --> 00:27:23.330 align:start position:0% more control of that that's what we are able<00:27:17.549> to<00:27:17.639> do<00:27:17.879> yeah<00:27:18.629> thank<00:27:19.350> you<00:27:21.860> hi<00:27:22.860> this<00:27:23.279> is 00:27:23.330 --> 00:27:23.340 align:start position:0% able to do yeah thank you hi this is 00:27:23.340 --> 00:27:26.570 align:start position:0% able to do yeah thank you hi this is more<00:27:23.789> with<00:27:23.970> Fein<00:27:24.320> my<00:27:25.320> question<00:27:25.769> is<00:27:25.919> I<00:27:26.129> love<00:27:26.460> the 00:27:26.570 --> 00:27:26.580 align:start position:0% more with Fein my question is I love the 00:27:26.580 --> 00:27:28.759 align:start position:0% more with Fein my question is I love the new<00:27:26.700> UX<00:27:27.179> flow<00:27:27.690> you<00:27:27.990> introduced<00:27:28.470> with<00:27:28.679> the 00:27:28.759 --> 00:27:28.769 align:start position:0% new UX flow you introduced with the 00:27:28.769 --> 00:27:31.039 align:start position:0% new UX flow you introduced with the mobile<00:27:28.980> app<00:27:29.249> where<00:27:29.549> you<00:27:29.700> what<00:27:30.539> user<00:27:30.749> doesn't 00:27:31.039 --> 00:27:31.049 align:start position:0% mobile app where you what user doesn't 00:27:31.049 --> 00:27:33.200 align:start position:0% mobile app where you what user doesn't need<00:27:31.470> to<00:27:31.649> create<00:27:31.889> a<00:27:31.950> password<00:27:32.220> up<00:27:32.669> until<00:27:33.029> they 00:27:33.200 --> 00:27:33.210 align:start position:0% need to create a password up until they 00:27:33.210 --> 00:27:35.810 align:start position:0% need to create a password up until they interact<00:27:33.840> do<00:27:34.679> you<00:27:34.769> plan<00:27:34.950> on<00:27:34.980> doing<00:27:35.429> the<00:27:35.639> same 00:27:35.810 --> 00:27:35.820 align:start position:0% interact do you plan on doing the same 00:27:35.820 --> 00:27:37.430 align:start position:0% interact do you plan on doing the same thing<00:27:36.059> for<00:27:36.299> the<00:27:36.450> Chrome<00:27:36.779> extension<00:27:36.809> as<00:27:37.409> well 00:27:37.430 --> 00:27:37.440 align:start position:0% thing for the Chrome extension as well 00:27:37.440 --> 00:27:40.999 align:start position:0% thing for the Chrome extension as well the<00:27:37.919> same<00:27:38.279> flow<00:27:38.519> I<00:27:39.049> think<00:27:40.049> there<00:27:40.710> is<00:27:40.740> a 00:27:40.999 --> 00:27:41.009 align:start position:0% the same flow I think there is a 00:27:41.009 --> 00:27:43.249 align:start position:0% the same flow I think there is a different<00:27:41.820> approach<00:27:42.330> between<00:27:42.659> mobile<00:27:43.110> and 00:27:43.249 --> 00:27:43.259 align:start position:0% different approach between mobile and 00:27:43.259 --> 00:27:45.279 align:start position:0% different approach between mobile and desktop<00:27:43.619> and<00:27:44.070> the<00:27:44.220> main<00:27:44.369> reason<00:27:44.700> is<00:27:44.789> that 00:27:45.279 --> 00:27:45.289 align:start position:0% desktop and the main reason is that 00:27:45.289 --> 00:27:48.200 align:start position:0% desktop and the main reason is that people<00:27:46.289> are<00:27:46.619> ready<00:27:47.070> in<00:27:47.190> a<00:27:47.249> browser<00:27:47.460> right<00:27:47.850> so 00:27:48.200 --> 00:27:48.210 align:start position:0% people are ready in a browser right so 00:27:48.210 --> 00:27:50.359 align:start position:0% people are ready in a browser right so they<00:27:48.509> can<00:27:48.690> make<00:27:48.869> it<00:27:49.019> to<00:27:49.139> the<00:27:49.259> apps<00:27:49.440> just<00:27:50.129> fine 00:27:50.359 --> 00:27:50.369 align:start position:0% they can make it to the apps just fine 00:27:50.369 --> 00:27:52.489 align:start position:0% they can make it to the apps just fine and<00:27:50.700> then<00:27:51.029> the<00:27:51.299> app<00:27:51.450> will<00:27:51.629> handle<00:27:52.019> you<00:27:52.379> know 00:27:52.489 --> 00:27:52.499 align:start position:0% and then the app will handle you know 00:27:52.499 --> 00:27:54.289 align:start position:0% and then the app will handle you know their<00:27:53.009> functionality 00:27:54.289 --> 00:27:54.299 align:start position:0% their functionality 00:27:54.299 --> 00:27:56.419 align:start position:0% their functionality in<00:27:54.360> one<00:27:54.659> way<00:27:54.809> or<00:27:54.840> another<00:27:55.019> right<00:27:55.499> but<00:27:56.100> in<00:27:56.369> a 00:27:56.419 --> 00:27:56.429 align:start position:0% in one way or another right but in a 00:27:56.429 --> 00:27:58.730 align:start position:0% in one way or another right but in a mobile<00:27:56.639> browser<00:27:56.820> you<00:27:57.720> usually<00:27:57.899> put<00:27:58.379> all<00:27:58.590> the 00:27:58.730 --> 00:27:58.740 align:start position:0% mobile browser you usually put all the 00:27:58.740 --> 00:28:00.169 align:start position:0% mobile browser you usually put all the thing<00:27:58.889> that<00:27:59.039> process<00:27:59.399> at<00:27:59.490> the<00:27:59.549> very<00:27:59.759> beginning 00:28:00.169 --> 00:28:00.179 align:start position:0% thing that process at the very beginning 00:28:00.179 --> 00:28:02.720 align:start position:0% thing that process at the very beginning right<00:28:00.269> so<00:28:00.899> that's<00:28:01.470> that's<00:28:01.769> why<00:28:02.009> we<00:28:02.309> feel<00:28:02.519> like 00:28:02.720 --> 00:28:02.730 align:start position:0% right so that's that's why we feel like 00:28:02.730 --> 00:28:04.909 align:start position:0% right so that's that's why we feel like it's<00:28:03.059> necessary<00:28:03.389> to<00:28:03.960> push<00:28:04.230> all<00:28:04.499> the<00:28:04.710> friction 00:28:04.909 --> 00:28:04.919 align:start position:0% it's necessary to push all the friction 00:28:04.919 --> 00:28:07.639 align:start position:0% it's necessary to push all the friction to<00:28:05.460> the<00:28:05.549> right<00:28:05.730> time<00:28:05.999> and<00:28:06.240> not<00:28:06.690> earlier<00:28:07.139> that 00:28:07.639 --> 00:28:07.649 align:start position:0% to the right time and not earlier that 00:28:07.649 --> 00:28:08.930 align:start position:0% to the right time and not earlier that doesn't<00:28:07.830> mean<00:28:08.129> difference<00:28:08.519> between<00:28:08.789> both 00:28:08.930 --> 00:28:08.940 align:start position:0% doesn't mean difference between both 00:28:08.940 --> 00:28:12.200 align:start position:0% doesn't mean difference between both platforms<00:28:09.590> that<00:28:10.590> said<00:28:10.980> I<00:28:11.279> think<00:28:11.580> we<00:28:11.759> have<00:28:11.940> a 00:28:12.200 --> 00:28:12.210 align:start position:0% platforms that said I think we have a 00:28:12.210 --> 00:28:14.509 align:start position:0% platforms that said I think we have a lot<00:28:12.450> that<00:28:12.629> we<00:28:12.840> could<00:28:13.049> do<00:28:13.230> with<00:28:13.559> the<00:28:13.830> desktop 00:28:14.509 --> 00:28:14.519 align:start position:0% lot that we could do with the desktop 00:28:14.519 --> 00:28:16.129 align:start position:0% lot that we could do with the desktop onboarding<00:28:15.090> experience<00:28:15.210> and<00:28:15.809> I<00:28:15.899> hope<00:28:15.990> that 00:28:16.129 --> 00:28:16.139 align:start position:0% onboarding experience and I hope that 00:28:16.139 --> 00:28:17.810 align:start position:0% onboarding experience and I hope that some<00:28:16.320> of<00:28:16.409> the<00:28:16.499> opt-in<00:28:16.860> metrics<00:28:17.309> that<00:28:17.549> Jenny 00:28:17.810 --> 00:28:17.820 align:start position:0% some of the opt-in metrics that Jenny 00:28:17.820 --> 00:28:19.159 align:start position:0% some of the opt-in metrics that Jenny mentioned<00:28:18.029> will<00:28:18.330> help<00:28:18.450> us<00:28:18.600> understand 00:28:19.159 --> 00:28:19.169 align:start position:0% mentioned will help us understand 00:28:19.169 --> 00:28:21.350 align:start position:0% mentioned will help us understand exactly<00:28:19.740> where<00:28:20.159> to<00:28:20.279> improve<00:28:20.580> and<00:28:20.909> I<00:28:21.179> don't 00:28:21.350 --> 00:28:21.360 align:start position:0% exactly where to improve and I don't 00:28:21.360 --> 00:28:23.419 align:start position:0% exactly where to improve and I don't think<00:28:21.659> that<00:28:21.899> our<00:28:22.110> team<00:28:22.289> is<00:28:22.440> like<00:28:22.559> opposed<00:28:23.129> to 00:28:23.419 --> 00:28:23.429 align:start position:0% think that our team is like opposed to 00:28:23.429 --> 00:28:25.100 align:start position:0% think that our team is like opposed to trying<00:28:23.909> some<00:28:24.119> dramatic<00:28:24.240> stuff<00:28:24.600> like<00:28:24.840> what 00:28:25.100 --> 00:28:25.110 align:start position:0% trying some dramatic stuff like what 00:28:25.110 --> 00:28:26.840 align:start position:0% trying some dramatic stuff like what Bruno<00:28:25.619> demonstrated<00:28:26.190> with<00:28:26.340> the<00:28:26.369> with<00:28:26.759> the 00:28:26.840 --> 00:28:26.850 align:start position:0% Bruno demonstrated with the with the 00:28:26.850 --> 00:28:31.669 align:start position:0% Bruno demonstrated with the with the mobile<00:28:26.999> app<00:28:28.009> maybe<00:28:29.009> one<00:28:29.190> more<00:28:30.049> can<00:28:31.049> I<00:28:31.139> ask<00:28:31.320> two 00:28:31.669 --> 00:28:31.679 align:start position:0% mobile app maybe one more can I ask two 00:28:31.679 --> 00:28:33.680 align:start position:0% mobile app maybe one more can I ask two questions<00:28:31.710> sure<00:28:32.519> one<00:28:32.970> more<00:28:33.119> present<00:28:33.509> yeah 00:28:33.680 --> 00:28:33.690 align:start position:0% questions sure one more present yeah 00:28:33.690 --> 00:28:36.649 align:start position:0% questions sure one more present yeah efficient<00:28:34.080> one<00:28:34.860> is<00:28:35.039> that<00:28:35.249> as<00:28:35.700> I<00:28:35.970> know<00:28:36.029> it's 00:28:36.649 --> 00:28:36.659 align:start position:0% efficient one is that as I know it's 00:28:36.659 --> 00:28:40.280 align:start position:0% efficient one is that as I know it's mainly<00:28:36.899> four<00:28:37.169> years<00:28:37.379> 20<00:28:37.830> right<00:28:38.009> now<00:28:38.039> right<00:28:38.580> so 00:28:40.280 --> 00:28:40.290 align:start position:0% mainly four years 20 right now right so 00:28:40.290 --> 00:28:43.010 align:start position:0% mainly four years 20 right now right so mainly<00:28:40.980> for<00:28:41.160> years<00:28:41.490> the<00:28:41.610> 20<00:28:41.970> right<00:28:42.150> now<00:28:42.300> so<00:28:42.840> we 00:28:43.010 --> 00:28:43.020 align:start position:0% mainly for years the 20 right now so we 00:28:43.020 --> 00:28:45.800 align:start position:0% mainly for years the 20 right now so we know<00:28:43.140> integrate<00:28:44.040> like<00:28:44.280> a<00:28:44.310> US<00:28:44.940> or<00:28:45.330> piece<00:28:45.630> age 00:28:45.800 --> 00:28:45.810 align:start position:0% know integrate like a US or piece age 00:28:45.810 --> 00:28:49.400 align:start position:0% know integrate like a US or piece age for<00:28:46.110> other<00:28:46.350> public<00:28:46.770> chain<00:28:47.750> I<00:28:48.750> don't<00:28:49.170> know<00:28:49.230> that 00:28:49.400 --> 00:28:49.410 align:start position:0% for other public chain I don't know that 00:28:49.410 --> 00:28:52.340 align:start position:0% for other public chain I don't know that it's<00:28:49.530> mainly<00:28:50.280> for<00:28:50.640> ERC<00:28:51.030> 20<00:28:51.330> I<00:28:51.570> think<00:28:51.870> like<00:28:52.320> a 00:28:52.340 --> 00:28:52.350 align:start position:0% it's mainly for ERC 20 I think like a 00:28:52.350 --> 00:28:55.430 align:start position:0% it's mainly for ERC 20 I think like a lot<00:28:52.560> of<00:28:52.590> people<00:28:52.710> use<00:28:52.950> it<00:28:53.130> for<00:28:53.670> signing<00:28:54.660> general 00:28:55.430 --> 00:28:55.440 align:start position:0% lot of people use it for signing general 00:28:55.440 --> 00:28:56.810 align:start position:0% lot of people use it for signing general eath<00:28:55.560> transactions<00:28:56.160> or<00:28:56.370> interacting<00:28:56.790> with 00:28:56.810 --> 00:28:56.820 align:start position:0% eath transactions or interacting with 00:28:56.820 --> 00:28:59.360 align:start position:0% eath transactions or interacting with taps<00:28:57.120> that<00:28:57.300> don't<00:28:57.570> involve<00:28:57.780> tokens<00:28:58.170> at<00:28:58.440> all 00:28:59.360 --> 00:28:59.370 align:start position:0% taps that don't involve tokens at all 00:28:59.370 --> 00:29:02.180 align:start position:0% taps that don't involve tokens at all we've<00:28:59.730> got<00:29:00.470> 721<00:29:01.470> support<00:29:01.860> collectable 00:29:02.180 --> 00:29:02.190 align:start position:0% we've got 721 support collectable 00:29:02.190 --> 00:29:03.980 align:start position:0% we've got 721 support collectable support<00:29:02.460> coming<00:29:02.700> down<00:29:02.910> the<00:29:03.150> line<00:29:03.420> and<00:29:03.870> we're 00:29:03.980 --> 00:29:03.990 align:start position:0% support coming down the line and we're 00:29:03.990 --> 00:29:07.820 align:start position:0% support coming down the line and we're pretty<00:29:04.170> much<00:29:04.290> ready<00:29:04.560> ready<00:29:04.980> for<00:29:05.100> that<00:29:06.830> the 00:29:07.820 --> 00:29:07.830 align:start position:0% pretty much ready ready for that the 00:29:07.830 --> 00:29:12.080 align:start position:0% pretty much ready ready for that the second<00:29:08.040> for<00:29:08.130> the<00:29:08.250> question<00:29:08.490> was<00:29:08.670> so<00:29:09.480> it's<00:29:11.090> for 00:29:12.080 --> 00:29:12.090 align:start position:0% second for the question was so it's for 00:29:12.090 --> 00:29:13.610 align:start position:0% second for the question was so it's for other<00:29:12.210> blockchains<00:29:12.600> yeah<00:29:12.810> or<00:29:13.410> other 00:29:13.610 --> 00:29:13.620 align:start position:0% other blockchains yeah or other 00:29:13.620 --> 00:29:15.140 align:start position:0% other blockchains yeah or other blockchain<00:29:14.130> whether<00:29:14.370> you<00:29:14.550> have<00:29:14.700> them<00:29:14.790> yes<00:29:15.000> so 00:29:15.140 --> 00:29:15.150 align:start position:0% blockchain whether you have them yes so 00:29:15.150 --> 00:29:19.790 align:start position:0% blockchain whether you have them yes so we<00:29:15.960> are<00:29:16.290> offering<00:29:16.890> the<00:29:17.190> ability<00:29:17.550> to<00:29:18.800> support 00:29:19.790 --> 00:29:19.800 align:start position:0% we are offering the ability to support 00:29:19.800 --> 00:29:22.010 align:start position:0% we are offering the ability to support any<00:29:20.040> eath<00:29:20.280> our<00:29:20.520> pc<00:29:20.820> compatibl<00:29:21.270> chain<00:29:21.480> as<00:29:21.720> of 00:29:22.010 --> 00:29:22.020 align:start position:0% any eath our pc compatibl chain as of 00:29:22.020 --> 00:29:24.830 align:start position:0% any eath our pc compatibl chain as of this<00:29:22.770> week<00:29:22.980> so<00:29:23.520> you<00:29:23.910> can<00:29:24.060> check<00:29:24.420> that<00:29:24.480> out<00:29:24.630> in 00:29:24.830 --> 00:29:24.840 align:start position:0% this week so you can check that out in 00:29:24.840 --> 00:29:27.080 align:start position:0% this week so you can check that out in our<00:29:24.930> next<00:29:25.140> release<00:29:25.500> yeah 00:29:27.080 --> 00:29:27.090 align:start position:0% our next release yeah 00:29:27.090 --> 00:29:29.480 align:start position:0% our next release yeah another<00:29:27.540> question<00:29:27.900> that<00:29:27.930> I<00:29:28.440> notice<00:29:29.190> you<00:29:29.340> guys 00:29:29.480 --> 00:29:29.490 align:start position:0% another question that I notice you guys 00:29:29.490 --> 00:29:32.060 align:start position:0% another question that I notice you guys recruit<00:29:30.060> new<00:29:30.420> position<00:29:30.930> but<00:29:31.140> all<00:29:31.410> relevant<00:29:31.800> to 00:29:32.060 --> 00:29:32.070 align:start position:0% recruit new position but all relevant to 00:29:32.070 --> 00:29:34.340 align:start position:0% recruit new position but all relevant to tech<00:29:32.280> background<00:29:32.490> so<00:29:33.360> is<00:29:33.570> that<00:29:33.750> your<00:29:33.900> strategy 00:29:34.340 --> 00:29:34.350 align:start position:0% tech background so is that your strategy 00:29:34.350 --> 00:29:36.320 align:start position:0% tech background so is that your strategy is<00:29:34.680> mainly<00:29:35.010> to<00:29:35.130> do<00:29:35.340> the<00:29:35.520> best<00:29:35.670> attack<00:29:36.060> and 00:29:36.320 --> 00:29:36.330 align:start position:0% is mainly to do the best attack and 00:29:36.330 --> 00:29:38.810 align:start position:0% is mainly to do the best attack and don't<00:29:36.960> do<00:29:37.220> promotions<00:29:38.220> like<00:29:38.430> business 00:29:38.810 --> 00:29:38.820 align:start position:0% don't do promotions like business 00:29:38.820 --> 00:29:42.400 align:start position:0% don't do promotions like business development<00:29:39.360> or<00:29:39.690> marketing<00:29:40.200> so<00:29:40.530> proactively 00:29:42.400 --> 00:29:42.410 align:start position:0% development or marketing so proactively 00:29:42.410 --> 00:29:45.680 align:start position:0% development or marketing so proactively we<00:29:43.410> are<00:29:43.590> sort<00:29:43.920> of<00:29:43.980> the<00:29:44.550> students<00:29:44.880> we're<00:29:45.450> sort 00:29:45.680 --> 00:29:45.690 align:start position:0% we are sort of the students we're sort 00:29:45.690 --> 00:29:48.080 align:start position:0% we are sort of the students we're sort of<00:29:45.750> like<00:29:46.040> blessed<00:29:47.040> to<00:29:47.370> have<00:29:47.550> a<00:29:48.000> very 00:29:48.080 --> 00:29:48.090 align:start position:0% of like blessed to have a very 00:29:48.090 --> 00:29:51.290 align:start position:0% of like blessed to have a very charismatic<00:29:48.960> Fox<00:29:49.500> and<00:29:49.770> that<00:29:50.190> he<00:29:50.880> takes<00:29:51.150> care 00:29:51.290 --> 00:29:51.300 align:start position:0% charismatic Fox and that he takes care 00:29:51.300 --> 00:29:53.150 align:start position:0% charismatic Fox and that he takes care of<00:29:51.360> a<00:29:51.480> lot<00:29:51.600> of<00:29:51.630> the<00:29:51.810> marketing<00:29:52.350> for<00:29:53.100> us 00:29:53.150 --> 00:29:53.160 align:start position:0% of a lot of the marketing for us 00:29:53.160 --> 00:29:54.590 align:start position:0% of a lot of the marketing for us business<00:29:53.880> development<00:29:54.330> sort<00:29:54.480> of<00:29:54.540> a 00:29:54.590 --> 00:29:54.600 align:start position:0% business development sort of a 00:29:54.600 --> 00:29:55.760 align:start position:0% business development sort of a responsibility<00:29:54.990> shared<00:29:55.290> by<00:29:55.470> the<00:29:55.530> team 00:29:55.760 --> 00:29:55.770 align:start position:0% responsibility shared by the team 00:29:55.770 --> 00:29:57.560 align:start position:0% responsibility shared by the team there's<00:29:56.100> a<00:29:56.250> bunch<00:29:56.760> of<00:29:56.820> friendly<00:29:57.150> team<00:29:57.330> members 00:29:57.560 --> 00:29:57.570 align:start position:0% there's a bunch of friendly team members 00:29:57.570 --> 00:29:59.270 align:start position:0% there's a bunch of friendly team members to<00:29:57.690> do<00:29:57.780> a<00:29:57.810> pretty<00:29:58.020> solid<00:29:58.290> job<00:29:58.530> of<00:29:58.770> maintaining 00:29:59.270 --> 00:29:59.280 align:start position:0% to do a pretty solid job of maintaining 00:29:59.280 --> 00:30:01.520 align:start position:0% to do a pretty solid job of maintaining relationships<00:29:59.850> with<00:30:00.030> other<00:30:00.240> folks<00:30:00.450> so<00:30:01.410> we 00:30:01.520 --> 00:30:01.530 align:start position:0% relationships with other folks so we 00:30:01.530 --> 00:30:02.810 align:start position:0% relationships with other folks so we aren't<00:30:01.650> looking<00:30:01.800> for<00:30:02.040> those<00:30:02.130> roles<00:30:02.340> yet<00:30:02.580> but 00:30:02.810 --> 00:30:02.820 align:start position:0% aren't looking for those roles yet but 00:30:02.820 --> 00:30:04.400 align:start position:0% aren't looking for those roles yet but we<00:30:02.970> probably<00:30:03.150> will<00:30:03.420> as<00:30:03.600> the<00:30:03.990> team<00:30:04.140> matures 00:30:04.400 --> 00:30:04.410 align:start position:0% we probably will as the team matures 00:30:04.410 --> 00:30:06.320 align:start position:0% we probably will as the team matures okay<00:30:05.100> shout<00:30:05.340> out<00:30:05.490> to<00:30:05.520> chase<00:30:05.910> known<00:30:06.120> for 00:30:06.320 --> 00:30:06.330 align:start position:0% okay shout out to chase known for 00:30:06.330 --> 00:30:08.900 align:start position:0% okay shout out to chase known for setting<00:30:06.630> up<00:30:06.840> the<00:30:06.930> store<00:30:07.140> yeah<00:30:07.830> and<00:30:08.430> one<00:30:08.760> more 00:30:08.900 --> 00:30:08.910 align:start position:0% setting up the store yeah and one more 00:30:08.910 --> 00:30:10.940 align:start position:0% setting up the store yeah and one more plug<00:30:09.150> for<00:30:09.360> this<00:30:09.560> seriously<00:30:10.560> we<00:30:10.680> would<00:30:10.770> love 00:30:10.940 --> 00:30:10.950 align:start position:0% plug for this seriously we would love 00:30:10.950 --> 00:30:13.040 align:start position:0% plug for this seriously we would love your<00:30:11.190> feedback<00:30:11.400> like<00:30:11.820> I<00:30:12.030> know<00:30:12.360> this<00:30:12.660> mic<00:30:12.900> that 00:30:13.040 --> 00:30:13.050 align:start position:0% your feedback like I know this mic that 00:30:13.050 --> 00:30:14.060 align:start position:0% your feedback like I know this mic that gets<00:30:13.200> passed<00:30:13.410> around<00:30:13.560> doesn't<00:30:13.740> make<00:30:13.920> it<00:30:14.010> to 00:30:14.060 --> 00:30:14.070 align:start position:0% gets passed around doesn't make it to 00:30:14.070 --> 00:30:16.490 align:start position:0% gets passed around doesn't make it to everyone<00:30:14.430> you<00:30:15.120> when<00:30:15.630> it<00:30:15.750> can<00:30:15.900> win<00:30:16.050> a<00:30:16.080> hoodie<00:30:16.350> or 00:30:16.490 --> 00:30:16.500 align:start position:0% everyone you when it can win a hoodie or 00:30:16.500 --> 00:30:17.990 align:start position:0% everyone you when it can win a hoodie or whatever<00:30:16.980> but<00:30:17.220> seriously<00:30:17.550> we<00:30:17.640> love<00:30:17.790> your 00:30:17.990 --> 00:30:18.000 align:start position:0% whatever but seriously we love your 00:30:18.000 --> 00:30:20.720 align:start position:0% whatever but seriously we love your feedback<00:30:18.120> so<00:30:18.300> scan<00:30:18.780> away<00:30:19.200> or<00:30:19.860> don't<00:30:20.070> and<00:30:20.280> we'll 00:30:20.720 --> 00:30:20.730 align:start position:0% feedback so scan away or don't and we'll 00:30:20.730 --> 00:30:22.490 align:start position:0% feedback so scan away or don't and we'll be<00:30:20.850> following<00:30:21.240> around<00:30:21.540> with<00:30:21.720> conference<00:30:22.230> with 00:30:22.490 --> 00:30:22.500 align:start position:0% be following around with conference with 00:30:22.500 --> 00:30:25.090 align:start position:0% be following around with conference with printed<00:30:23.490> out<00:30:23.640> versions<00:30:24.090> you<00:30:24.300> can<00:30:24.450> scan<00:30:24.720> - 00:30:25.090 --> 00:30:25.100 align:start position:0% printed out versions you can scan - 00:30:25.100 --> 00:30:29.779 align:start position:0% printed out versions you can scan - thank<00:30:26.100> you<00:30:26.160> for<00:30:26.220> coming<00:30:26.460> thank<00:30:26.670> you<00:30:27.060> guys 00:30:29.779 --> 00:30:29.789 align:start position:0% 00:30:29.789 --> 00:30:40.040 align:start position:0% you 00:30:40.040 --> 00:30:40.050 align:start position:0% 00:30:40.050 --> 00:30:42.110 align:start position:0% you