WEBVTT Kind: captions Language: en 00:00:00.310 --> 00:00:05.200 align:start position:0% so<00:00:02.499> what<00:00:03.499> is<00:00:03.649> a<00:00:03.679> design<00:00:03.919> system<00:00:04.490> traditionally 00:00:05.200 --> 00:00:05.210 align:start position:0% so what is a design system traditionally 00:00:05.210 --> 00:00:07.900 align:start position:0% so what is a design system traditionally design<00:00:05.540> systems<00:00:06.020> are<00:00:06.350> a<00:00:07.010> set<00:00:07.310> of<00:00:07.340> reusable 00:00:07.900 --> 00:00:07.910 align:start position:0% design systems are a set of reusable 00:00:07.910 --> 00:00:10.509 align:start position:0% design systems are a set of reusable components<00:00:08.510> that<00:00:08.750> are<00:00:09.020> backed<00:00:09.290> by<00:00:09.410> some<00:00:10.280> sort 00:00:10.509 --> 00:00:10.519 align:start position:0% components that are backed by some sort 00:00:10.519 --> 00:00:13.540 align:start position:0% components that are backed by some sort of<00:00:10.610> standards<00:00:11.060> or<00:00:11.180> guidelines<00:00:12.220> these<00:00:13.220> can<00:00:13.430> be 00:00:13.540 --> 00:00:13.550 align:start position:0% of standards or guidelines these can be 00:00:13.550 --> 00:00:15.250 align:start position:0% of standards or guidelines these can be assembled<00:00:13.820> together<00:00:14.120> to<00:00:14.540> build<00:00:14.720> any<00:00:14.900> number 00:00:15.250 --> 00:00:15.260 align:start position:0% assembled together to build any number 00:00:15.260 --> 00:00:19.620 align:start position:0% assembled together to build any number of<00:00:15.349> applications<00:00:15.980> and<00:00:17.679> they<00:00:18.679> kind<00:00:18.919> of<00:00:19.009> enabled 00:00:19.620 --> 00:00:19.630 align:start position:0% of applications and they kind of enabled 00:00:19.630 --> 00:00:22.509 align:start position:0% of applications and they kind of enabled products<00:00:20.630> to<00:00:20.779> prototype<00:00:21.650> and<00:00:21.949> test<00:00:22.009> their 00:00:22.509 --> 00:00:22.519 align:start position:0% products to prototype and test their 00:00:22.519 --> 00:00:26.649 align:start position:0% products to prototype and test their products<00:00:22.909> faster<00:00:24.039> so<00:00:25.119> the<00:00:26.119> some<00:00:26.390> of<00:00:26.419> the 00:00:26.649 --> 00:00:26.659 align:start position:0% products faster so the some of the 00:00:26.659 --> 00:00:28.630 align:start position:0% products faster so the some of the design<00:00:27.649> systems<00:00:27.980> that<00:00:28.009> were<00:00:28.220> familiar<00:00:28.399> with 00:00:28.630 --> 00:00:28.640 align:start position:0% design systems that were familiar with 00:00:28.640 --> 00:00:30.639 align:start position:0% design systems that were familiar with today<00:00:28.759> are<00:00:29.210> such<00:00:29.539> things<00:00:29.720> as<00:00:29.899> material<00:00:30.380> design 00:00:30.639 --> 00:00:30.649 align:start position:0% today are such things as material design 00:00:30.649 --> 00:00:34.240 align:start position:0% today are such things as material design angular<00:00:31.279> and<00:00:31.550> bootstrap<00:00:32.300> and<00:00:32.920> as<00:00:33.920> we<00:00:34.129> know 00:00:34.240 --> 00:00:34.250 align:start position:0% angular and bootstrap and as we know 00:00:34.250 --> 00:00:37.360 align:start position:0% angular and bootstrap and as we know today<00:00:34.309> web<00:00:34.760> users<00:00:35.230> for<00:00:36.230> web<00:00:36.410> 3<00:00:36.649> have<00:00:36.859> to<00:00:37.010> learn 00:00:37.360 --> 00:00:37.370 align:start position:0% today web users for web 3 have to learn 00:00:37.370 --> 00:00:39.540 align:start position:0% today web users for web 3 have to learn very<00:00:37.430> new<00:00:37.910> concepts<00:00:38.420> mental<00:00:38.870> models<00:00:39.199> and 00:00:39.540 --> 00:00:39.550 align:start position:0% very new concepts mental models and 00:00:39.550 --> 00:00:42.189 align:start position:0% very new concepts mental models and patterns<00:00:40.550> with<00:00:40.760> each<00:00:40.969> application<00:00:41.719> that<00:00:42.050> they 00:00:42.189 --> 00:00:42.199 align:start position:0% patterns with each application that they 00:00:42.199 --> 00:00:45.040 align:start position:0% patterns with each application that they use<00:00:42.379> on<00:00:42.710> web<00:00:42.890> 3<00:00:43.160> and<00:00:43.579> like<00:00:44.359> the<00:00:44.449> early<00:00:44.719> days<00:00:44.899> of 00:00:45.040 --> 00:00:45.050 align:start position:0% use on web 3 and like the early days of 00:00:45.050 --> 00:00:47.079 align:start position:0% use on web 3 and like the early days of the<00:00:45.589> Internet 00:00:47.079 --> 00:00:47.089 align:start position:0% the Internet 00:00:47.089 --> 00:00:49.169 align:start position:0% the Internet we're<00:00:47.510> coming<00:00:47.750> up<00:00:47.839> with<00:00:47.899> new<00:00:48.140> patterns<00:00:48.350> and 00:00:49.169 --> 00:00:49.179 align:start position:0% we're coming up with new patterns and 00:00:49.179 --> 00:00:51.340 align:start position:0% we're coming up with new patterns and eventually<00:00:50.179> we'll<00:00:50.570> get<00:00:50.690> to<00:00:50.809> a<00:00:50.839> place<00:00:51.050> where 00:00:51.340 --> 00:00:51.350 align:start position:0% eventually we'll get to a place where 00:00:51.350 --> 00:00:54.759 align:start position:0% eventually we'll get to a place where designers<00:00:51.649> kind<00:00:51.980> of<00:00:52.070> coalesce<00:00:52.429> into<00:00:53.230> a<00:00:54.230> set<00:00:54.649> of 00:00:54.759 --> 00:00:54.769 align:start position:0% designers kind of coalesce into a set of 00:00:54.769 --> 00:00:56.829 align:start position:0% designers kind of coalesce into a set of standards<00:00:55.160> making<00:00:55.370> users<00:00:55.879> to<00:00:56.210> bounce<00:00:56.449> from 00:00:56.829 --> 00:00:56.839 align:start position:0% standards making users to bounce from 00:00:56.839 --> 00:01:02.680 align:start position:0% standards making users to bounce from one<00:00:57.109> application<00:00:57.710> to<00:00:58.159> the<00:00:58.370> next<00:00:59.199> so<00:01:00.249> in<00:01:01.690> an 00:01:02.680 --> 00:01:02.690 align:start position:0% one application to the next so in an 00:01:02.690 --> 00:01:04.479 align:start position:0% one application to the next so in an aspect<00:01:03.140> what<00:01:03.440> 3<00:01:03.620> is<00:01:03.739> kind<00:01:03.920> of<00:01:03.949> taking<00:01:04.220> us<00:01:04.340> back 00:01:04.479 --> 00:01:04.489 align:start position:0% aspect what 3 is kind of taking us back 00:01:04.489 --> 00:01:06.240 align:start position:0% aspect what 3 is kind of taking us back to<00:01:04.670> where<00:01:04.820> user<00:01:05.030> experience<00:01:05.540> was<00:01:05.660> in<00:01:05.780> the<00:01:05.810> 90s 00:01:06.240 --> 00:01:06.250 align:start position:0% to where user experience was in the 90s 00:01:06.250 --> 00:01:08.350 align:start position:0% to where user experience was in the 90s there's<00:01:07.250> a<00:01:07.310> lot<00:01:07.460> of<00:01:07.550> excitement<00:01:07.850> a<00:01:08.090> lot<00:01:08.270> of 00:01:08.350 --> 00:01:08.360 align:start position:0% there's a lot of excitement a lot of 00:01:08.360 --> 00:01:10.360 align:start position:0% there's a lot of excitement a lot of experimentation<00:01:08.960> going<00:01:09.140> on<00:01:09.500> but<00:01:09.980> we<00:01:10.100> need<00:01:10.250> to 00:01:10.360 --> 00:01:10.370 align:start position:0% experimentation going on but we need to 00:01:10.370 --> 00:01:12.310 align:start position:0% experimentation going on but we need to establish<00:01:10.490> some<00:01:10.880> new<00:01:11.180> patterns<00:01:11.390> to<00:01:11.840> serve<00:01:12.080> our 00:01:12.310 --> 00:01:12.320 align:start position:0% establish some new patterns to serve our 00:01:12.320 --> 00:01:14.440 align:start position:0% establish some new patterns to serve our users<00:01:12.410> and<00:01:12.980> get<00:01:13.430> them<00:01:13.580> to<00:01:13.760> the<00:01:13.910> hurdles<00:01:14.210> of<00:01:14.330> web 00:01:14.440 --> 00:01:14.450 align:start position:0% users and get them to the hurdles of web 00:01:14.450 --> 00:01:18.400 align:start position:0% users and get them to the hurdles of web 3<00:01:15.460> so<00:01:16.460> I'm<00:01:17.210> gonna<00:01:17.420> be<00:01:17.570> introducing<00:01:17.750> the<00:01:18.110> web<00:01:18.230> 3 00:01:18.400 --> 00:01:18.410 align:start position:0% 3 so I'm gonna be introducing the web 3 00:01:18.410 --> 00:01:20.980 align:start position:0% 3 so I'm gonna be introducing the web 3 design<00:01:18.680> system<00:01:18.980> team<00:01:19.450> what<00:01:20.450> we<00:01:20.570> are<00:01:20.750> is<00:01:20.960> a 00:01:20.980 --> 00:01:20.990 align:start position:0% design system team what we are is a 00:01:20.990 --> 00:01:23.320 align:start position:0% design system team what we are is a federated<00:01:21.500> design<00:01:21.860> systems<00:01:22.280> team<00:01:22.490> but<00:01:22.760> that 00:01:23.320 --> 00:01:23.330 align:start position:0% federated design systems team but that 00:01:23.330 --> 00:01:24.610 align:start position:0% federated design systems team but that means<00:01:23.570> is<00:01:23.750> we<00:01:23.930> each<00:01:24.110> work<00:01:24.350> for<00:01:24.530> different 00:01:24.610 --> 00:01:24.620 align:start position:0% means is we each work for different 00:01:24.620 --> 00:01:27.040 align:start position:0% means is we each work for different organizations<00:01:25.040> and<00:01:25.670> we've<00:01:26.270> kind<00:01:26.480> of<00:01:26.600> through 00:01:27.040 --> 00:01:27.050 align:start position:0% organizations and we've kind of through 00:01:27.050 --> 00:01:28.630 align:start position:0% organizations and we've kind of through community<00:01:27.500> efforts<00:01:27.830> come<00:01:28.010> together<00:01:28.190> to 00:01:28.630 --> 00:01:28.640 align:start position:0% community efforts come together to 00:01:28.640 --> 00:01:31.120 align:start position:0% community efforts come together to spearhead<00:01:29.060> they<00:01:29.270> use<00:01:29.480> UX<00:01:30.350> and<00:01:30.620> usability 00:01:31.120 --> 00:01:31.130 align:start position:0% spearhead they use UX and usability 00:01:31.130 --> 00:01:33.940 align:start position:0% spearhead they use UX and usability issues<00:01:31.460> in<00:01:31.730> the<00:01:31.820> ecosystem<00:01:32.390> our<00:01:33.320> goal<00:01:33.650> is<00:01:33.920> to 00:01:33.940 --> 00:01:33.950 align:start position:0% issues in the ecosystem our goal is to 00:01:33.950 --> 00:01:36.750 align:start position:0% issues in the ecosystem our goal is to create<00:01:34.610> a<00:01:35.000> resource<00:01:35.570> in<00:01:35.810> an<00:01:35.900> open-source 00:01:36.750 --> 00:01:36.760 align:start position:0% create a resource in an open-source 00:01:36.760 --> 00:01:39.670 align:start position:0% create a resource in an open-source format<00:01:37.760> that<00:01:37.940> anyone<00:01:38.270> can<00:01:38.480> make<00:01:38.990> it<00:01:39.200> on<00:01:39.350> their 00:01:39.670 --> 00:01:39.680 align:start position:0% format that anyone can make it on their 00:01:39.680 --> 00:01:39.880 align:start position:0% format that anyone can make it on their own 00:01:39.880 --> 00:01:39.890 align:start position:0% own 00:01:39.890 --> 00:01:42.760 align:start position:0% own and<00:01:40.130> rely<00:01:40.910> upon<00:01:40.940> when<00:01:41.570> their<00:01:41.720> whether<00:01:42.590> you're 00:01:42.760 --> 00:01:42.770 align:start position:0% and rely upon when their whether you're 00:01:42.770 --> 00:01:45.040 align:start position:0% and rely upon when their whether you're a<00:01:42.800> designer<00:01:43.160> or<00:01:43.400> developer<00:01:43.520> to<00:01:44.240> prototype<00:01:44.600> and 00:01:45.040 --> 00:01:45.050 align:start position:0% a designer or developer to prototype and 00:01:45.050 --> 00:01:48.220 align:start position:0% a designer or developer to prototype and test<00:01:45.110> our<00:01:45.440> products<00:01:45.830> faster<00:01:46.690> we<00:01:47.690> hope<00:01:47.930> to<00:01:48.110> do 00:01:48.220 --> 00:01:48.230 align:start position:0% test our products faster we hope to do 00:01:48.230 --> 00:01:52.600 align:start position:0% test our products faster we hope to do this<00:01:48.410> through<00:01:49.000> a<00:01:50.920> well<00:01:51.920> researched<00:01:52.160> and 00:01:52.600 --> 00:01:52.610 align:start position:0% this through a well researched and 00:01:52.610 --> 00:01:54.730 align:start position:0% this through a well researched and validated<00:01:53.120> component<00:01:53.660> library<00:01:53.990> but<00:01:54.590> we've 00:01:54.730 --> 00:01:54.740 align:start position:0% validated component library but we've 00:01:54.740 --> 00:01:56.230 align:start position:0% validated component library but we've been<00:01:54.890> very<00:01:55.010> mindful<00:01:55.340> of<00:01:55.640> jumping<00:01:55.940> into<00:01:56.090> the 00:01:56.230 --> 00:01:56.240 align:start position:0% been very mindful of jumping into the 00:01:56.240 --> 00:01:58.510 align:start position:0% been very mindful of jumping into the components<00:01:56.950> because<00:01:57.950> let's<00:01:58.160> be<00:01:58.280> realistic 00:01:58.510 --> 00:01:58.520 align:start position:0% components because let's be realistic 00:01:58.520 --> 00:02:00.580 align:start position:0% components because let's be realistic there's<00:01:59.330> not<00:01:59.540> a<00:01:59.570> lot<00:01:59.810> of<00:01:59.840> user<00:02:00.140> data<00:02:00.230> out<00:02:00.560> there 00:02:00.580 --> 00:02:00.590 align:start position:0% there's not a lot of user data out there 00:02:00.590 --> 00:02:05.470 align:start position:0% there's not a lot of user data out there and<00:02:02.650> traditional<00:02:03.650> UX<00:02:04.190> research<00:02:04.790> methods<00:02:05.180> kind 00:02:05.470 --> 00:02:05.480 align:start position:0% and traditional UX research methods kind 00:02:05.480 --> 00:02:07.510 align:start position:0% and traditional UX research methods kind of<00:02:05.570> start<00:02:05.810> to<00:02:05.840> fall<00:02:06.050> apart<00:02:06.350> when<00:02:06.440> you<00:02:06.560> put<00:02:07.370> them 00:02:07.510 --> 00:02:07.520 align:start position:0% of start to fall apart when you put them 00:02:07.520 --> 00:02:09.340 align:start position:0% of start to fall apart when you put them in<00:02:07.700> front<00:02:07.940> of<00:02:08.060> people<00:02:08.390> with<00:02:08.899> about<00:02:09.110> three 00:02:09.340 --> 00:02:09.350 align:start position:0% in front of people with about three 00:02:09.350 --> 00:02:11.080 align:start position:0% in front of people with about three ecosystem 00:02:11.080 --> 00:02:11.090 align:start position:0% ecosystem 00:02:11.090 --> 00:02:14.470 align:start position:0% ecosystem so<00:02:12.640> currently<00:02:13.640> we've<00:02:13.940> been<00:02:14.090> working<00:02:14.450> with 00:02:14.470 --> 00:02:14.480 align:start position:0% so currently we've been working with 00:02:14.480 --> 00:02:17.229 align:start position:0% so currently we've been working with some<00:02:14.630> of<00:02:14.870> the<00:02:15.110> top<00:02:15.319> teams<00:02:15.530> and<00:02:15.800> projects<00:02:16.239> that 00:02:17.229 --> 00:02:17.239 align:start position:0% some of the top teams and projects that 00:02:17.239 --> 00:02:19.270 align:start position:0% some of the top teams and projects that have<00:02:17.540> actually<00:02:18.020> been<00:02:18.140> working<00:02:18.200> on<00:02:18.800> solving 00:02:19.270 --> 00:02:19.280 align:start position:0% have actually been working on solving 00:02:19.280 --> 00:02:21.190 align:start position:0% have actually been working on solving the<00:02:19.610> UX<00:02:19.849> issues<00:02:20.000> in<00:02:20.270> the<00:02:20.360> space<00:02:20.630> for<00:02:20.900> the<00:02:20.989> past 00:02:21.190 --> 00:02:21.200 align:start position:0% the UX issues in the space for the past 00:02:21.200 --> 00:02:24.309 align:start position:0% the UX issues in the space for the past few<00:02:21.380> years<00:02:21.580> so<00:02:22.580> we're<00:02:22.880> learning<00:02:23.060> from<00:02:23.319> the 00:02:24.309 --> 00:02:24.319 align:start position:0% few years so we're learning from the 00:02:24.319 --> 00:02:26.080 align:start position:0% few years so we're learning from the challenges<00:02:25.130> and<00:02:25.400> the<00:02:25.520> issues<00:02:25.760> that<00:02:25.790> they<00:02:26.060> face 00:02:26.080 --> 00:02:26.090 align:start position:0% challenges and the issues that they face 00:02:26.090 --> 00:02:30.880 align:start position:0% challenges and the issues that they face and<00:02:26.690> trying<00:02:27.290> to<00:02:27.380> bring<00:02:29.110> everything<00:02:30.110> in<00:02:30.680> a 00:02:30.880 --> 00:02:30.890 align:start position:0% and trying to bring everything in a 00:02:30.890 --> 00:02:32.979 align:start position:0% and trying to bring everything in a cohesive<00:02:31.400> manner<00:02:31.670> so<00:02:32.030> not<00:02:32.480> people<00:02:32.870> are 00:02:32.979 --> 00:02:32.989 align:start position:0% cohesive manner so not people are 00:02:32.989 --> 00:02:39.009 align:start position:0% cohesive manner so not people are creating<00:02:33.470> siloed<00:02:33.860> solutions<00:02:37.120> our<00:02:38.120> goal<00:02:38.480> is<00:02:38.720> to 00:02:39.009 --> 00:02:39.019 align:start position:0% creating siloed solutions our goal is to 00:02:39.019 --> 00:02:41.410 align:start position:0% creating siloed solutions our goal is to open<00:02:39.650> up<00:02:40.040> our<00:02:40.220> project<00:02:40.819> to<00:02:40.940> anyone<00:02:41.300> who's 00:02:41.410 --> 00:02:41.420 align:start position:0% open up our project to anyone who's 00:02:41.420 --> 00:02:43.390 align:start position:0% open up our project to anyone who's creating<00:02:41.989> any<00:02:42.110> components<00:02:42.709> or<00:02:42.830> any<00:02:42.980> research 00:02:43.390 --> 00:02:43.400 align:start position:0% creating any components or any research 00:02:43.400 --> 00:02:45.699 align:start position:0% creating any components or any research to<00:02:43.640> kind<00:02:43.819> of<00:02:43.910> help<00:02:44.870> us<00:02:45.019> facilitate<00:02:45.170> that 00:02:45.699 --> 00:02:45.709 align:start position:0% to kind of help us facilitate that 00:02:45.709 --> 00:02:47.710 align:start position:0% to kind of help us facilitate that better<00:02:46.040> I'm<00:02:46.610> gonna<00:02:46.790> pass<00:02:47.000> it<00:02:47.120> off<00:02:47.209> to<00:02:47.330> Beltran 00:02:47.710 --> 00:02:47.720 align:start position:0% better I'm gonna pass it off to Beltran 00:02:47.720 --> 00:02:57.940 align:start position:0% better I'm gonna pass it off to Beltran to<00:02:48.080> speak<00:02:48.530> about<00:02:49.209> the<00:02:50.209> problem<00:02:50.510> space<00:02:56.950> thank 00:02:57.940 --> 00:02:57.950 align:start position:0% to speak about the problem space thank 00:02:57.950 --> 00:02:59.500 align:start position:0% to speak about the problem space thank you<00:02:58.040> at<00:02:58.489> the<00:02:58.610> beginning<00:02:58.910> of<00:02:59.000> the<00:02:59.150> year<00:02:59.299> we 00:02:59.500 --> 00:02:59.510 align:start position:0% you at the beginning of the year we 00:02:59.510 --> 00:03:01.539 align:start position:0% you at the beginning of the year we published<00:02:59.900> the<00:03:00.110> web<00:03:00.380> 3<00:03:00.590> design<00:03:00.920> principles 00:03:01.539 --> 00:03:01.549 align:start position:0% published the web 3 design principles 00:03:01.549 --> 00:03:05.620 align:start position:0% published the web 3 design principles that<00:03:03.250> try<00:03:04.250> to<00:03:04.310> propose<00:03:05.000> some<00:03:05.360> of<00:03:05.510> the 00:03:05.620 --> 00:03:05.630 align:start position:0% that try to propose some of the 00:03:05.630 --> 00:03:08.500 align:start position:0% that try to propose some of the components<00:03:06.200> or<00:03:06.760> hinted<00:03:07.760> at<00:03:07.970> some<00:03:08.299> of<00:03:08.420> the 00:03:08.500 --> 00:03:08.510 align:start position:0% components or hinted at some of the 00:03:08.510 --> 00:03:10.750 align:start position:0% components or hinted at some of the possible<00:03:08.900> components<00:03:09.590> however<00:03:10.010> like<00:03:10.400> you 00:03:10.750 --> 00:03:10.760 align:start position:0% possible components however like you 00:03:10.760 --> 00:03:14.259 align:start position:0% possible components however like you said<00:03:11.030> the<00:03:11.930> research<00:03:12.440> was<00:03:13.040> much<00:03:13.549> lighter<00:03:13.910> than 00:03:14.259 --> 00:03:14.269 align:start position:0% said the research was much lighter than 00:03:14.269 --> 00:03:17.020 align:start position:0% said the research was much lighter than the<00:03:14.510> Thoreau<00:03:15.380> one<00:03:15.769> that<00:03:15.980> we<00:03:16.070> are<00:03:16.190> doing<00:03:16.459> right 00:03:17.020 --> 00:03:17.030 align:start position:0% the Thoreau one that we are doing right 00:03:17.030 --> 00:03:20.170 align:start position:0% the Thoreau one that we are doing right now<00:03:17.060> and<00:03:17.480> we<00:03:18.320> are<00:03:18.470> interviewing<00:03:19.010> everybody<00:03:19.880> in 00:03:20.170 --> 00:03:20.180 align:start position:0% now and we are interviewing everybody in 00:03:20.180 --> 00:03:23.050 align:start position:0% now and we are interviewing everybody in the<00:03:20.420> space<00:03:20.660> that<00:03:20.870> has<00:03:21.019> topped<00:03:21.350> to<00:03:21.829> users<00:03:22.250> with 00:03:23.050 --> 00:03:23.060 align:start position:0% the space that has topped to users with 00:03:23.060 --> 00:03:25.300 align:start position:0% the space that has topped to users with intention<00:03:23.600> of<00:03:23.690> mapping<00:03:24.170> up<00:03:24.380> those<00:03:24.680> problems 00:03:25.300 --> 00:03:25.310 align:start position:0% intention of mapping up those problems 00:03:25.310 --> 00:03:27.910 align:start position:0% intention of mapping up those problems and<00:03:25.579> the<00:03:26.120> users<00:03:26.420> face<00:03:26.630> and<00:03:26.989> the<00:03:27.590> current 00:03:27.910 --> 00:03:27.920 align:start position:0% and the users face and the current 00:03:27.920 --> 00:03:32.170 align:start position:0% and the users face and the current solutions<00:03:28.400> to<00:03:28.700> later<00:03:29.769> create<00:03:30.769> this<00:03:31.310> web 00:03:32.170 --> 00:03:32.180 align:start position:0% solutions to later create this web 00:03:32.180 --> 00:03:34.210 align:start position:0% solutions to later create this web design<00:03:32.780> system<00:03:33.109> this<00:03:33.290> library<00:03:33.500> of<00:03:33.739> components 00:03:34.210 --> 00:03:34.220 align:start position:0% design system this library of components 00:03:34.220 --> 00:03:36.400 align:start position:0% design system this library of components and<00:03:34.370> the<00:03:34.519> and<00:03:34.819> the<00:03:35.030> guidelines<00:03:35.569> of<00:03:35.780> of<00:03:35.930> best 00:03:36.400 --> 00:03:36.410 align:start position:0% and the and the guidelines of of best 00:03:36.410 --> 00:03:40.210 align:start position:0% and the and the guidelines of of best user<00:03:37.130> practices<00:03:37.910> so<00:03:38.660> you<00:03:39.380> know<00:03:39.560> all<00:03:39.920> of<00:03:39.980> the 00:03:40.210 --> 00:03:40.220 align:start position:0% user practices so you know all of the 00:03:40.220 --> 00:03:41.890 align:start position:0% user practices so you know all of the problems<00:03:40.639> there's<00:03:40.910> a<00:03:41.000> plenty<00:03:41.480> of<00:03:41.720> them 00:03:41.890 --> 00:03:41.900 align:start position:0% problems there's a plenty of them 00:03:41.900 --> 00:03:46.780 align:start position:0% problems there's a plenty of them today's<00:03:42.709> a<00:03:42.739> very<00:03:42.920> confusing<00:03:43.670> space<00:03:45.340> we<00:03:46.340> can 00:03:46.780 --> 00:03:46.790 align:start position:0% today's a very confusing space we can 00:03:46.790 --> 00:03:49.059 align:start position:0% today's a very confusing space we can share<00:03:47.120> some<00:03:47.150> we<00:03:47.989> don't<00:03:48.139> have<00:03:48.350> any<00:03:48.470> components 00:03:49.059 --> 00:03:49.069 align:start position:0% share some we don't have any components 00:03:49.069 --> 00:03:52.000 align:start position:0% share some we don't have any components I<00:03:49.190> was<00:03:49.519> saying<00:03:49.819> yet<00:03:50.540> but<00:03:50.989> what<00:03:51.350> we<00:03:51.530> can<00:03:51.739> share 00:03:52.000 --> 00:03:52.010 align:start position:0% I was saying yet but what we can share 00:03:52.010 --> 00:03:53.680 align:start position:0% I was saying yet but what we can share is<00:03:52.100> the<00:03:52.220> second<00:03:52.579> best<00:03:52.760> thing<00:03:52.880> which<00:03:53.299> is<00:03:53.510> a 00:03:53.680 --> 00:03:53.690 align:start position:0% is the second best thing which is a 00:03:53.690 --> 00:03:56.319 align:start position:0% is the second best thing which is a mental<00:03:54.380> framework<00:03:55.010> about<00:03:55.250> how<00:03:55.549> to<00:03:55.609> go<00:03:56.299> about 00:03:56.319 --> 00:03:56.329 align:start position:0% mental framework about how to go about 00:03:56.329 --> 00:03:58.930 align:start position:0% mental framework about how to go about and<00:03:56.750> think<00:03:57.049> and<00:03:57.260> solve<00:03:57.590> these<00:03:57.829> problems<00:03:58.489> okay 00:03:58.930 --> 00:03:58.940 align:start position:0% and think and solve these problems okay 00:03:58.940 --> 00:04:01.900 align:start position:0% and think and solve these problems okay and<00:03:59.180> we've<00:04:00.079> asked<00:04:00.350> these<00:04:00.470> companies<00:04:00.889> what<00:04:01.760> are 00:04:01.900 --> 00:04:01.910 align:start position:0% and we've asked these companies what are 00:04:01.910 --> 00:04:04.509 align:start position:0% and we've asked these companies what are the<00:04:02.030> questions<00:04:02.209> the<00:04:02.540> users<00:04:02.870> have<00:04:03.079> and<00:04:03.350> we<00:04:03.889> try 00:04:04.509 --> 00:04:04.519 align:start position:0% the questions the users have and we try 00:04:04.519 --> 00:04:07.120 align:start position:0% the questions the users have and we try to<00:04:04.579> map<00:04:05.269> them<00:04:05.480> out<00:04:05.630> and<00:04:05.900> gather<00:04:06.470> them<00:04:06.739> some<00:04:06.980> are 00:04:07.120 --> 00:04:07.130 align:start position:0% to map them out and gather them some are 00:04:07.130 --> 00:04:09.460 align:start position:0% to map them out and gather them some are fun<00:04:07.370> like<00:04:07.639> how<00:04:08.180> do<00:04:08.239> I<00:04:08.420> find<00:04:08.690> these<00:04:08.840> projects<00:04:09.350> in 00:04:09.460 --> 00:04:09.470 align:start position:0% fun like how do I find these projects in 00:04:09.470 --> 00:04:12.129 align:start position:0% fun like how do I find these projects in the<00:04:09.590> other<00:04:09.799> Internet<00:04:10.790> or<00:04:11.030> some<00:04:11.780> are<00:04:11.900> very 00:04:12.129 --> 00:04:12.139 align:start position:0% the other Internet or some are very 00:04:12.139 --> 00:04:14.800 align:start position:0% the other Internet or some are very important<00:04:12.620> like<00:04:12.859> why<00:04:13.400> should<00:04:13.700> I<00:04:13.819> care<00:04:14.180> this<00:04:14.660> is 00:04:14.800 --> 00:04:14.810 align:start position:0% important like why should I care this is 00:04:14.810 --> 00:04:17.319 align:start position:0% important like why should I care this is questions<00:04:15.319> that<00:04:15.560> users<00:04:15.920> really<00:04:15.950> ask<00:04:16.430> and<00:04:16.760> so 00:04:17.319 --> 00:04:17.329 align:start position:0% questions that users really ask and so 00:04:17.329 --> 00:04:20.469 align:start position:0% questions that users really ask and so we<00:04:17.780> try<00:04:18.440> to<00:04:18.470> make<00:04:18.769> sense<00:04:18.799> of<00:04:19.459> all<00:04:20.150> these 00:04:20.469 --> 00:04:20.479 align:start position:0% we try to make sense of all these 00:04:20.479 --> 00:04:23.300 align:start position:0% we try to make sense of all these questions<00:04:21.080> and<00:04:21.320> we<00:04:21.979> came<00:04:22.340> up<00:04:22.370> with 00:04:23.300 --> 00:04:23.310 align:start position:0% questions and we came up with 00:04:23.310 --> 00:04:26.240 align:start position:0% questions and we came up with pattern<00:04:24.090> that<00:04:24.300> we<00:04:24.450> call<00:04:24.720> the<00:04:25.380> problem<00:04:26.010> space 00:04:26.240 --> 00:04:26.250 align:start position:0% pattern that we call the problem space 00:04:26.250 --> 00:04:28.700 align:start position:0% pattern that we call the problem space to<00:04:26.520> map<00:04:26.670> them<00:04:26.880> up<00:04:26.970> in<00:04:27.150> a<00:04:27.240> problem<00:04:27.420> space<00:04:27.840> and<00:04:28.110> we 00:04:28.700 --> 00:04:28.710 align:start position:0% to map them up in a problem space and we 00:04:28.710 --> 00:04:30.440 align:start position:0% to map them up in a problem space and we found<00:04:28.920> there's<00:04:29.190> the<00:04:29.700> problems<00:04:30.060> can<00:04:30.270> be 00:04:30.440 --> 00:04:30.450 align:start position:0% found there's the problems can be 00:04:30.450 --> 00:04:33.350 align:start position:0% found there's the problems can be categorizing<00:04:31.110> two<00:04:31.290> buckets<00:04:31.860> like<00:04:32.360> problems 00:04:33.350 --> 00:04:33.360 align:start position:0% categorizing two buckets like problems 00:04:33.360 --> 00:04:35.690 align:start position:0% categorizing two buckets like problems that<00:04:33.570> are<00:04:33.720> relating<00:04:34.350> to<00:04:34.530> technicalities<00:04:35.490> of 00:04:35.690 --> 00:04:35.700 align:start position:0% that are relating to technicalities of 00:04:35.700 --> 00:04:38.150 align:start position:0% that are relating to technicalities of the<00:04:35.970> blockchain<00:04:36.210> or<00:04:36.919> decentralization<00:04:37.919> in 00:04:38.150 --> 00:04:38.160 align:start position:0% the blockchain or decentralization in 00:04:38.160 --> 00:04:41.060 align:start position:0% the blockchain or decentralization in itself<00:04:38.460> and<00:04:39.380> fundamental<00:04:40.380> other<00:04:40.620> problems 00:04:41.060 --> 00:04:41.070 align:start position:0% itself and fundamental other problems 00:04:41.070 --> 00:04:44.120 align:start position:0% itself and fundamental other problems that<00:04:41.130> are<00:04:41.370> fundamental<00:04:42.300> to<00:04:42.600> the<00:04:43.530> explanation 00:04:44.120 --> 00:04:44.130 align:start position:0% that are fundamental to the explanation 00:04:44.130 --> 00:04:46.340 align:start position:0% that are fundamental to the explanation about<00:04:44.220> decentralization<00:04:44.700> and<00:04:45.600> of<00:04:46.110> course 00:04:46.340 --> 00:04:46.350 align:start position:0% about decentralization and of course 00:04:46.350 --> 00:04:48.200 align:start position:0% about decentralization and of course there's<00:04:46.530> some<00:04:46.710> obvious<00:04:46.889> overlap<00:04:47.700> and<00:04:48.000> and 00:04:48.200 --> 00:04:48.210 align:start position:0% there's some obvious overlap and and 00:04:48.210 --> 00:04:49.970 align:start position:0% there's some obvious overlap and and there<00:04:48.510> are<00:04:48.540> also<00:04:48.780> subcategories<00:04:49.560> we<00:04:49.680> will<00:04:49.830> see 00:04:49.970 --> 00:04:49.980 align:start position:0% there are also subcategories we will see 00:04:49.980 --> 00:04:52.879 align:start position:0% there are also subcategories we will see so<00:04:50.490> we<00:04:50.790> put<00:04:51.240> these<00:04:51.570> questions<00:04:51.930> we<00:04:52.470> map<00:04:52.710> them 00:04:52.879 --> 00:04:52.889 align:start position:0% so we put these questions we map them 00:04:52.889 --> 00:04:54.860 align:start position:0% so we put these questions we map them into<00:04:52.950> this<00:04:53.340> problem<00:04:54.030> space<00:04:54.389> into<00:04:54.720> this 00:04:54.860 --> 00:04:54.870 align:start position:0% into this problem space into this 00:04:54.870 --> 00:04:58.130 align:start position:0% into this problem space into this diagram<00:04:55.410> and<00:04:56.060> in<00:04:57.060> the<00:04:57.240> technical<00:04:57.660> bucket<00:04:58.020> so 00:04:58.130 --> 00:04:58.140 align:start position:0% diagram and in the technical bucket so 00:04:58.140 --> 00:05:00.110 align:start position:0% diagram and in the technical bucket so you<00:04:58.230> have<00:04:58.380> questions<00:04:58.770> like<00:04:58.919> what<00:04:59.520> is<00:04:59.550> gas<00:04:59.820> what 00:05:00.110 --> 00:05:00.120 align:start position:0% you have questions like what is gas what 00:05:00.120 --> 00:05:02.540 align:start position:0% you have questions like what is gas what is<00:05:00.210> gas<00:05:00.419> price<00:05:00.720> what<00:05:01.320> is<00:05:01.440> how<00:05:01.680> do<00:05:01.740> I<00:05:01.919> get<00:05:02.010> et 00:05:02.540 --> 00:05:02.550 align:start position:0% is gas price what is how do I get et 00:05:02.550 --> 00:05:05.900 align:start position:0% is gas price what is how do I get et cetera<00:05:02.730> and<00:05:03.150> in<00:05:03.480> the<00:05:03.600> fundamental<00:05:04.760> part<00:05:05.760> of 00:05:05.900 --> 00:05:05.910 align:start position:0% cetera and in the fundamental part of 00:05:05.910 --> 00:05:07.520 align:start position:0% cetera and in the fundamental part of the<00:05:06.030> centralization<00:05:06.450> we<00:05:07.020> find<00:05:07.260> questions 00:05:07.520 --> 00:05:07.530 align:start position:0% the centralization we find questions 00:05:07.530 --> 00:05:09.890 align:start position:0% the centralization we find questions that<00:05:07.830> are<00:05:07.919> more<00:05:08.010> important<00:05:08.370> like<00:05:08.460> how<00:05:09.419> core 00:05:09.890 --> 00:05:09.900 align:start position:0% that are more important like how core 00:05:09.900 --> 00:05:14.030 align:start position:0% that are more important like how core can<00:05:10.230> you<00:05:10.440> reset<00:05:11.010> my<00:05:11.640> private<00:05:12.210> key<00:05:12.450> which<00:05:13.040> speak 00:05:14.030 --> 00:05:14.040 align:start position:0% can you reset my private key which speak 00:05:14.040 --> 00:05:17.210 align:start position:0% can you reset my private key which speak to<00:05:14.400> the<00:05:14.610> misunderstanding<00:05:14.960> of<00:05:15.960> users<00:05:16.530> of<00:05:16.770> the 00:05:17.210 --> 00:05:17.220 align:start position:0% to the misunderstanding of users of the 00:05:17.220 --> 00:05:20.690 align:start position:0% to the misunderstanding of users of the purpose<00:05:17.700> of<00:05:17.940> decentralized<00:05:18.900> technology<00:05:19.700> and 00:05:20.690 --> 00:05:20.700 align:start position:0% purpose of decentralized technology and 00:05:20.700 --> 00:05:23.230 align:start position:0% purpose of decentralized technology and I<00:05:21.120> was<00:05:21.210> mentioning<00:05:21.680> subcategories<00:05:22.680> of<00:05:22.830> course 00:05:23.230 --> 00:05:23.240 align:start position:0% I was mentioning subcategories of course 00:05:23.240 --> 00:05:26.570 align:start position:0% I was mentioning subcategories of course there<00:05:24.240> is<00:05:24.360> consensus<00:05:25.110> among<00:05:25.560> many<00:05:26.310> of<00:05:26.460> the 00:05:26.570 --> 00:05:26.580 align:start position:0% there is consensus among many of the 00:05:26.580 --> 00:05:29.420 align:start position:0% there is consensus among many of the interviewed<00:05:27.060> people<00:05:27.240> that<00:05:28.430> decentralization 00:05:29.420 --> 00:05:29.430 align:start position:0% interviewed people that decentralization 00:05:29.430 --> 00:05:31.730 align:start position:0% interviewed people that decentralization like<00:05:29.790> Akhil<00:05:30.120> was<00:05:30.330> mentioning<00:05:30.780> requires<00:05:31.380> new 00:05:31.730 --> 00:05:31.740 align:start position:0% like Akhil was mentioning requires new 00:05:31.740 --> 00:05:34.610 align:start position:0% like Akhil was mentioning requires new mental<00:05:32.160> models<00:05:32.610> and<00:05:32.850> besides<00:05:33.510> this<00:05:33.840> we<00:05:34.440> also 00:05:34.610 --> 00:05:34.620 align:start position:0% mental models and besides this we also 00:05:34.620 --> 00:05:38.230 align:start position:0% mental models and besides this we also have<00:05:35.100> new<00:05:36.060> complicated<00:05:36.690> concepts<00:05:37.169> like<00:05:37.530> gas 00:05:38.230 --> 00:05:38.240 align:start position:0% have new complicated concepts like gas 00:05:38.240 --> 00:05:40.760 align:start position:0% have new complicated concepts like gas transactions<00:05:39.240> the<00:05:39.510> tokens<00:05:40.020> private<00:05:40.560> keys 00:05:40.760 --> 00:05:40.770 align:start position:0% transactions the tokens private keys 00:05:40.770 --> 00:05:42.830 align:start position:0% transactions the tokens private keys these<00:05:41.280> are<00:05:41.490> completely<00:05:41.940> new<00:05:42.180> to<00:05:42.210> the<00:05:42.450> users 00:05:42.830 --> 00:05:42.840 align:start position:0% these are completely new to the users 00:05:42.840 --> 00:05:45.710 align:start position:0% these are completely new to the users are<00:05:43.080> and<00:05:43.470> they<00:05:43.680> are<00:05:43.800> unfamiliar<00:05:44.280> and<00:05:44.610> so<00:05:45.060> not 00:05:45.710 --> 00:05:45.720 align:start position:0% are and they are unfamiliar and so not 00:05:45.720 --> 00:05:47.990 align:start position:0% are and they are unfamiliar and so not only<00:05:45.900> they<00:05:46.320> are<00:05:46.350> complicated<00:05:47.280> concepts<00:05:47.729> but 00:05:47.990 --> 00:05:48.000 align:start position:0% only they are complicated concepts but 00:05:48.000 --> 00:05:49.670 align:start position:0% only they are complicated concepts but it<00:05:48.150> appears<00:05:48.479> today<00:05:48.720> we<00:05:48.900> are<00:05:48.960> doing<00:05:49.229> a<00:05:49.289> very<00:05:49.440> bad 00:05:49.670 --> 00:05:49.680 align:start position:0% it appears today we are doing a very bad 00:05:49.680 --> 00:05:54.529 align:start position:0% it appears today we are doing a very bad job<00:05:49.740> at<00:05:50.070> explaining<00:05:50.190> them<00:05:50.789> and<00:05:51.530> so<00:05:53.539> advancing 00:05:54.529 --> 00:05:54.539 align:start position:0% job at explaining them and so advancing 00:05:54.539 --> 00:05:57.740 align:start position:0% job at explaining them and so advancing the<00:05:55.110> possible<00:05:55.650> solutions<00:05:56.220> that<00:05:56.460> the<00:05:56.750> creators 00:05:57.740 --> 00:05:57.750 align:start position:0% the possible solutions that the creators 00:05:57.750 --> 00:06:00.710 align:start position:0% the possible solutions that the creators the<00:05:58.080> developers<00:05:58.590> and<00:05:58.710> designers<00:05:58.860> are<00:05:59.720> using 00:06:00.710 --> 00:06:00.720 align:start position:0% the developers and designers are using 00:06:00.720 --> 00:06:02.570 align:start position:0% the developers and designers are using and<00:06:00.930> they're<00:06:01.080> seeing<00:06:01.410> that<00:06:01.590> work<00:06:01.890> into<00:06:02.280> this 00:06:02.570 --> 00:06:02.580 align:start position:0% and they're seeing that work into this 00:06:02.580 --> 00:06:05.360 align:start position:0% and they're seeing that work into this problem<00:06:02.910> space<00:06:03.360> we<00:06:03.930> found<00:06:04.289> out<00:06:04.530> this<00:06:04.890> that<00:06:05.280> we 00:06:05.360 --> 00:06:05.370 align:start position:0% problem space we found out this that we 00:06:05.370 --> 00:06:07.850 align:start position:0% problem space we found out this that we call<00:06:05.550> the<00:06:05.669> solution<00:06:06.060> space<00:06:06.300> which<00:06:07.110> reduces 00:06:07.850 --> 00:06:07.860 align:start position:0% call the solution space which reduces 00:06:07.860 --> 00:06:09.500 align:start position:0% call the solution space which reduces the<00:06:08.039> possible<00:06:08.430> solutions<00:06:08.850> to<00:06:08.910> -<00:06:09.150> which<00:06:09.360> is 00:06:09.500 --> 00:06:09.510 align:start position:0% the possible solutions to - which is 00:06:09.510 --> 00:06:11.840 align:start position:0% the possible solutions to - which is either<00:06:09.780> hide<00:06:10.260> the<00:06:11.010> complexity<00:06:11.669> of<00:06:11.700> the 00:06:11.840 --> 00:06:11.850 align:start position:0% either hide the complexity of the 00:06:11.850 --> 00:06:15.500 align:start position:0% either hide the complexity of the technology<00:06:11.970> or<00:06:12.950> explain<00:06:13.950> it<00:06:14.130> better<00:06:14.789> and<00:06:15.210> we 00:06:15.500 --> 00:06:15.510 align:start position:0% technology or explain it better and we 00:06:15.510 --> 00:06:17.570 align:start position:0% technology or explain it better and we will<00:06:15.660> see<00:06:15.780> in<00:06:15.930> a<00:06:16.020> bit<00:06:16.050> in<00:06:16.710> a<00:06:16.890> minute<00:06:17.010> how<00:06:17.340> to<00:06:17.370> do 00:06:17.570 --> 00:06:17.580 align:start position:0% will see in a bit in a minute how to do 00:06:17.580 --> 00:06:19.420 align:start position:0% will see in a bit in a minute how to do it<00:06:17.700> so<00:06:18.090> let's<00:06:18.270> see<00:06:18.330> an<00:06:18.419> example<00:06:18.900> for<00:06:19.050> example 00:06:19.420 --> 00:06:19.430 align:start position:0% it so let's see an example for example 00:06:19.430 --> 00:06:23.029 align:start position:0% it so let's see an example for example all<00:06:20.430> these<00:06:20.669> problems<00:06:21.240> are<00:06:21.450> multi-dimensional 00:06:23.029 --> 00:06:23.039 align:start position:0% all these problems are multi-dimensional 00:06:23.039 --> 00:06:24.830 align:start position:0% all these problems are multi-dimensional it<00:06:23.190> means<00:06:23.430> that<00:06:23.580> the<00:06:23.669> questions<00:06:24.210> relating<00:06:24.660> for 00:06:24.830 --> 00:06:24.840 align:start position:0% it means that the questions relating for 00:06:24.840 --> 00:06:27.740 align:start position:0% it means that the questions relating for example<00:06:25.200> to<00:06:25.320> gas<00:06:25.560> fall<00:06:26.400> in<00:06:26.760> various<00:06:27.330> of<00:06:27.510> those 00:06:27.740 --> 00:06:27.750 align:start position:0% example to gas fall in various of those 00:06:27.750 --> 00:06:29.480 align:start position:0% example to gas fall in various of those buckets<00:06:28.260> and<00:06:28.440> in<00:06:28.560> various<00:06:29.010> possible 00:06:29.480 --> 00:06:29.490 align:start position:0% buckets and in various possible 00:06:29.490 --> 00:06:32.140 align:start position:0% buckets and in various possible solutions<00:06:30.120> for<00:06:30.300> example<00:06:30.840> in<00:06:31.140> the<00:06:31.320> bottom<00:06:31.860> part 00:06:32.140 --> 00:06:32.150 align:start position:0% solutions for example in the bottom part 00:06:32.150 --> 00:06:34.909 align:start position:0% solutions for example in the bottom part the<00:06:33.150> questions<00:06:33.539> what<00:06:33.780> is<00:06:33.900> gas<00:06:34.140> what<00:06:34.620> is<00:06:34.740> gas 00:06:34.909 --> 00:06:34.919 align:start position:0% the questions what is gas what is gas 00:06:34.919 --> 00:06:36.559 align:start position:0% the questions what is gas what is gas price<00:06:35.220> etc 00:06:36.559 --> 00:06:36.569 align:start position:0% price etc 00:06:36.569 --> 00:06:38.450 align:start position:0% price etc those<00:06:36.779> are<00:06:37.080> technicalities<00:06:37.800> that<00:06:38.339> if 00:06:38.450 --> 00:06:38.460 align:start position:0% those are technicalities that if 00:06:38.460 --> 00:06:40.790 align:start position:0% those are technicalities that if possible<00:06:38.969> we<00:06:39.149> should<00:06:39.330> hide<00:06:39.539> and<00:06:39.869> the<00:06:40.139> mr.<00:06:40.559> team 00:06:40.790 --> 00:06:40.800 align:start position:0% possible we should hide and the mr. team 00:06:40.800 --> 00:06:44.149 align:start position:0% possible we should hide and the mr. team has<00:06:41.399> taught<00:06:41.909> us<00:06:41.939> how<00:06:42.149> to<00:06:42.919> hide<00:06:43.919> them 00:06:44.149 --> 00:06:44.159 align:start position:0% has taught us how to hide them 00:06:44.159 --> 00:06:46.669 align:start position:0% has taught us how to hide them progressively<00:06:44.639> from<00:06:44.939> from<00:06:45.569> the<00:06:45.689> user<00:06:45.869> then 00:06:46.669 --> 00:06:46.679 align:start position:0% progressively from from the user then 00:06:46.679 --> 00:06:48.559 align:start position:0% progressively from from the user then there<00:06:46.860> are<00:06:46.949> a<00:06:46.979> question<00:06:47.309> like<00:06:47.490> why<00:06:48.029> does<00:06:48.330> have 00:06:48.559 --> 00:06:48.569 align:start position:0% there are a question like why does have 00:06:48.569 --> 00:06:51.139 align:start position:0% there are a question like why does have gas<00:06:49.199> have<00:06:49.559> varying<00:06:50.099> different<00:06:50.789> costs<00:06:51.089> at 00:06:51.139 --> 00:06:51.149 align:start position:0% gas have varying different costs at 00:06:51.149 --> 00:06:54.230 align:start position:0% gas have varying different costs at different<00:06:51.449> times<00:06:51.689> this<00:06:52.490> although<00:06:53.490> we<00:06:53.729> hope<00:06:53.969> to 00:06:54.230 --> 00:06:54.240 align:start position:0% different times this although we hope to 00:06:54.240 --> 00:06:56.600 align:start position:0% different times this although we hope to be<00:06:54.539> able<00:06:54.569> to<00:06:54.809> hide<00:06:55.110> it<00:06:55.139> one<00:06:55.499> day<00:06:55.709> today<00:06:56.339> there's 00:06:56.600 --> 00:06:56.610 align:start position:0% be able to hide it one day today there's 00:06:56.610 --> 00:06:59.209 align:start position:0% be able to hide it one day today there's not<00:06:56.789> a<00:06:56.849> technical<00:06:57.389> solution<00:06:57.539> yet<00:06:58.020> and<00:06:58.229> if<00:06:58.800> the 00:06:59.209 --> 00:06:59.219 align:start position:0% not a technical solution yet and if the 00:06:59.219 --> 00:07:01.219 align:start position:0% not a technical solution yet and if the user<00:06:59.490> sees<00:06:59.939> different<00:07:00.479> fees<00:07:00.719> in<00:07:00.899> different 00:07:01.219 --> 00:07:01.229 align:start position:0% user sees different fees in different 00:07:01.229 --> 00:07:03.109 align:start position:0% user sees different fees in different moments<00:07:01.649> for<00:07:01.800> the<00:07:01.889> same<00:07:02.069> action<00:07:02.490> they<00:07:02.909> will 00:07:03.109 --> 00:07:03.119 align:start position:0% moments for the same action they will 00:07:03.119 --> 00:07:06.799 align:start position:0% moments for the same action they will still<00:07:03.509> be<00:07:03.749> asking<00:07:03.979> why<00:07:04.979> is<00:07:05.369> it<00:07:05.969> different<00:07:06.599> so 00:07:06.799 --> 00:07:06.809 align:start position:0% still be asking why is it different so 00:07:06.809 --> 00:07:09.019 align:start position:0% still be asking why is it different so you<00:07:06.869> need<00:07:07.050> simply<00:07:07.800> to<00:07:07.919> be<00:07:08.129> explaining<00:07:08.610> what<00:07:08.939> is 00:07:09.019 --> 00:07:09.029 align:start position:0% you need simply to be explaining what is 00:07:09.029 --> 00:07:11.269 align:start position:0% you need simply to be explaining what is happening<00:07:09.539> in<00:07:09.719> the<00:07:09.899> back<00:07:10.080> and<00:07:10.379> on<00:07:10.889> the<00:07:11.009> top 00:07:11.269 --> 00:07:11.279 align:start position:0% happening in the back and on the top 00:07:11.279 --> 00:07:13.570 align:start position:0% happening in the back and on the top part<00:07:11.610> there<00:07:12.209> are<00:07:12.330> questions<00:07:12.839> that<00:07:13.139> relate<00:07:13.469> to 00:07:13.570 --> 00:07:13.580 align:start position:0% part there are questions that relate to 00:07:13.580 --> 00:07:15.320 align:start position:0% part there are questions that relate to misunderstanding<00:07:14.580> of<00:07:14.699> decentralization 00:07:15.320 --> 00:07:15.330 align:start position:0% misunderstanding of decentralization 00:07:15.330 --> 00:07:17.779 align:start position:0% misunderstanding of decentralization itself<00:07:15.809> like<00:07:15.990> why<00:07:16.499> do<00:07:16.559> I<00:07:16.800> have<00:07:16.830> to<00:07:17.099> pay<00:07:17.249> gas<00:07:17.520> or 00:07:17.779 --> 00:07:17.789 align:start position:0% itself like why do I have to pay gas or 00:07:17.789 --> 00:07:20.510 align:start position:0% itself like why do I have to pay gas or does<00:07:18.330> the<00:07:18.509> theorem<00:07:19.499> foundation<00:07:20.099> get<00:07:20.309> the<00:07:20.399> gas 00:07:20.510 --> 00:07:20.520 align:start position:0% does the theorem foundation get the gas 00:07:20.520 --> 00:07:23.149 align:start position:0% does the theorem foundation get the gas so<00:07:20.639> why<00:07:20.879> do<00:07:20.939> I<00:07:21.209> have<00:07:21.330> to<00:07:21.449> pay<00:07:21.599> the<00:07:21.809> tap<00:07:22.050> a<00:07:22.319> gas<00:07:22.709> - 00:07:23.149 --> 00:07:23.159 align:start position:0% so why do I have to pay the tap a gas - 00:07:23.159 --> 00:07:25.939 align:start position:0% so why do I have to pay the tap a gas - so<00:07:23.729> these<00:07:24.119> things<00:07:24.479> you<00:07:24.719> need<00:07:24.959> right<00:07:25.499> now<00:07:25.649> only 00:07:25.939 --> 00:07:25.949 align:start position:0% so these things you need right now only 00:07:25.949 --> 00:07:29.089 align:start position:0% so these things you need right now only to<00:07:26.219> find<00:07:26.610> better<00:07:26.789> solutions<00:07:26.959> and<00:07:28.099> this 00:07:29.089 --> 00:07:29.099 align:start position:0% to find better solutions and this 00:07:29.099 --> 00:07:32.619 align:start position:0% to find better solutions and this solution<00:07:29.339> space<00:07:29.939> can<00:07:30.779> help<00:07:31.349> you<00:07:31.740> make<00:07:32.279> better 00:07:32.619 --> 00:07:32.629 align:start position:0% solution space can help you make better 00:07:32.629 --> 00:07:36.259 align:start position:0% solution space can help you make better design<00:07:33.629> decisions<00:07:34.469> and<00:07:34.679> it<00:07:35.550> will<00:07:35.879> help<00:07:36.089> us 00:07:36.259 --> 00:07:36.269 align:start position:0% design decisions and it will help us 00:07:36.269 --> 00:07:39.619 align:start position:0% design decisions and it will help us design<00:07:36.779> decisions<00:07:37.469> for<00:07:37.679> the<00:07:38.149> components<00:07:39.149> so 00:07:39.619 --> 00:07:39.629 align:start position:0% design decisions for the components so 00:07:39.629 --> 00:07:42.199 align:start position:0% design decisions for the components so the<00:07:39.929> key<00:07:40.110> insights<00:07:40.499> is<00:07:40.800> on<00:07:41.309> the<00:07:41.699> bottom<00:07:41.969> part 00:07:42.199 --> 00:07:42.209 align:start position:0% the key insights is on the bottom part 00:07:42.209 --> 00:07:44.509 align:start position:0% the key insights is on the bottom part the<00:07:42.569> technicality<00:07:43.199> is<00:07:43.259> hide<00:07:43.619> or<00:07:43.830> obstructing 00:07:44.509 --> 00:07:44.519 align:start position:0% the technicality is hide or obstructing 00:07:44.519 --> 00:07:46.609 align:start position:0% the technicality is hide or obstructing away<00:07:44.789> and<00:07:45.059> we<00:07:45.180> have<00:07:45.330> patterns<00:07:45.779> that<00:07:46.319> a<00:07:46.349> cube 00:07:46.609 --> 00:07:46.619 align:start position:0% away and we have patterns that a cube 00:07:46.619 --> 00:07:49.339 align:start position:0% away and we have patterns that a cube will<00:07:46.769> mention<00:07:46.979> that<00:07:47.809> today<00:07:48.809> helped<00:07:49.110> us<00:07:49.199> for 00:07:49.339 --> 00:07:49.349 align:start position:0% will mention that today helped us for 00:07:49.349 --> 00:07:52.639 align:start position:0% will mention that today helped us for example<00:07:49.439> hide<00:07:49.830> gas<00:07:50.009> or<00:07:50.779> there<00:07:51.779> is<00:07:51.869> a<00:07:51.899> consensus 00:07:52.639 --> 00:07:52.649 align:start position:0% example hide gas or there is a consensus 00:07:52.649 --> 00:07:54.559 align:start position:0% example hide gas or there is a consensus among<00:07:52.949> the<00:07:52.979> interviewed<00:07:53.519> people<00:07:53.669> that<00:07:54.149> it<00:07:54.509> is 00:07:54.559 --> 00:07:54.569 align:start position:0% among the interviewed people that it is 00:07:54.569 --> 00:07:57.769 align:start position:0% among the interviewed people that it is OK<00:07:55.289> for<00:07:55.319> newcomers<00:07:56.249> to<00:07:56.490> have<00:07:56.909> different 00:07:57.769 --> 00:07:57.779 align:start position:0% OK for newcomers to have different 00:07:57.779 --> 00:08:00.799 align:start position:0% OK for newcomers to have different degrees<00:07:57.990> of<00:07:58.259> centralization<00:07:59.159> okay<00:08:00.089> that<00:08:00.659> you 00:08:00.799 --> 00:08:00.809 align:start position:0% degrees of centralization okay that you 00:08:00.809 --> 00:08:03.109 align:start position:0% degrees of centralization okay that you can't<00:08:01.079> put<00:08:01.409> a<00:08:01.649> centralized<00:08:02.219> service<00:08:02.579> to 00:08:03.109 --> 00:08:03.119 align:start position:0% can't put a centralized service to 00:08:03.119 --> 00:08:06.109 align:start position:0% can't put a centralized service to simplify<00:08:03.779> the<00:08:04.529> experience<00:08:05.339> of<00:08:05.430> the<00:08:05.579> newcomer 00:08:06.109 --> 00:08:06.119 align:start position:0% simplify the experience of the newcomer 00:08:06.119 --> 00:08:10.069 align:start position:0% simplify the experience of the newcomer but<00:08:06.990> as<00:08:07.379> soon<00:08:07.860> as<00:08:08.009> possible<00:08:08.579> on<00:08:08.819> boredom<00:08:09.689> onto 00:08:10.069 --> 00:08:10.079 align:start position:0% but as soon as possible on boredom onto 00:08:10.079 --> 00:08:12.529 align:start position:0% but as soon as possible on boredom onto the<00:08:10.229> real<00:08:10.469> decentralize<00:08:11.309> and<00:08:11.639> educate<00:08:12.269> them 00:08:12.529 --> 00:08:12.539 align:start position:0% the real decentralize and educate them 00:08:12.539 --> 00:08:16.059 align:start position:0% the real decentralize and educate them for<00:08:13.379> -<00:08:13.589> to<00:08:13.889> do<00:08:14.219> that<00:08:14.399> real<00:08:15.180> decentralization 00:08:16.059 --> 00:08:16.069 align:start position:0% for - to do that real decentralization 00:08:16.069 --> 00:08:19.009 align:start position:0% for - to do that real decentralization for<00:08:17.069> technicalities<00:08:17.759> that<00:08:17.789> cannot<00:08:18.300> be<00:08:18.629> hidden 00:08:19.009 --> 00:08:19.019 align:start position:0% for technicalities that cannot be hidden 00:08:19.019 --> 00:08:22.069 align:start position:0% for technicalities that cannot be hidden yet<00:08:19.379> we<00:08:20.099> hope<00:08:20.369> one<00:08:20.639> day<00:08:20.819> we<00:08:21.209> can<00:08:21.389> push<00:08:21.659> it<00:08:21.869> down 00:08:22.069 --> 00:08:22.079 align:start position:0% yet we hope one day we can push it down 00:08:22.079 --> 00:08:24.350 align:start position:0% yet we hope one day we can push it down into<00:08:22.289> the<00:08:22.589> hybrid<00:08:23.279> bucket<00:08:23.639> but<00:08:24.029> today<00:08:24.300> you 00:08:24.350 --> 00:08:24.360 align:start position:0% into the hybrid bucket but today you 00:08:24.360 --> 00:08:26.869 align:start position:0% into the hybrid bucket but today you should<00:08:24.779> use<00:08:25.110> analogies<00:08:25.949> that<00:08:25.979> they<00:08:26.279> earn<00:08:26.430> they 00:08:26.869 --> 00:08:26.879 align:start position:0% should use analogies that they earn they 00:08:26.879 --> 00:08:29.199 align:start position:0% should use analogies that they earn they know<00:08:27.119> so<00:08:27.719> if<00:08:27.869> it's<00:08:28.019> a<00:08:28.110> financial<00:08:28.319> application 00:08:29.199 --> 00:08:29.209 align:start position:0% know so if it's a financial application 00:08:29.209 --> 00:08:31.759 align:start position:0% know so if it's a financial application use<00:08:30.209> or<00:08:30.479> look<00:08:30.719> at<00:08:30.869> patterns<00:08:31.349> they're<00:08:31.559> useful 00:08:31.759 --> 00:08:31.769 align:start position:0% use or look at patterns they're useful 00:08:31.769 --> 00:08:34.040 align:start position:0% use or look at patterns they're useful for<00:08:32.099> example<00:08:32.310> in<00:08:32.490> banking<00:08:33.000> and<00:08:33.149> most 00:08:34.040 --> 00:08:34.050 align:start position:0% for example in banking and most 00:08:34.050 --> 00:08:36.110 align:start position:0% for example in banking and most importantly<00:08:34.649> for<00:08:34.979> the<00:08:35.099> fundamental<00:08:35.759> parts<00:08:36.029> of 00:08:36.110 --> 00:08:36.120 align:start position:0% importantly for the fundamental parts of 00:08:36.120 --> 00:08:37.850 align:start position:0% importantly for the fundamental parts of the<00:08:36.209> centralization<00:08:36.659> these<00:08:37.259> questions 00:08:37.850 --> 00:08:37.860 align:start position:0% the centralization these questions 00:08:37.860 --> 00:08:41.360 align:start position:0% the centralization these questions overarching<00:08:38.819> unimportant<00:08:40.039> you<00:08:41.039> should<00:08:41.219> not 00:08:41.360 --> 00:08:41.370 align:start position:0% overarching unimportant you should not 00:08:41.370 --> 00:08:43.550 align:start position:0% overarching unimportant you should not hide<00:08:41.610> them<00:08:41.849> and<00:08:42.029> you<00:08:42.839> should<00:08:43.019> explain<00:08:43.349> them 00:08:43.550 --> 00:08:43.560 align:start position:0% hide them and you should explain them 00:08:43.560 --> 00:08:45.740 align:start position:0% hide them and you should explain them better<00:08:43.740> and<00:08:43.949> to<00:08:44.039> explain<00:08:44.370> them<00:08:44.610> better<00:08:44.939> you 00:08:45.740 --> 00:08:45.750 align:start position:0% better and to explain them better you 00:08:45.750 --> 00:08:47.010 align:start position:0% better and to explain them better you have<00:08:46.110> to 00:08:47.010 --> 00:08:47.020 align:start position:0% have to 00:08:47.020 --> 00:08:49.620 align:start position:0% have to start<00:08:47.200> with<00:08:47.440> why<00:08:47.740> why<00:08:48.250> is<00:08:48.310> it<00:08:48.730> important<00:08:49.450> why 00:08:49.620 --> 00:08:49.630 align:start position:0% start with why why is it important why 00:08:49.630 --> 00:08:52.590 align:start position:0% start with why why is it important why are<00:08:49.660> we<00:08:50.200> motivated<00:08:50.860> by<00:08:51.010> this<00:08:51.070> and<00:08:51.600> something 00:08:52.590 --> 00:08:52.600 align:start position:0% are we motivated by this and something 00:08:52.600 --> 00:08:56.490 align:start position:0% are we motivated by this and something that<00:08:52.780> came<00:08:52.990> up<00:08:53.140> from<00:08:53.560> many<00:08:53.920> is<00:08:54.190> that<00:08:55.140> the<00:08:56.140> you 00:08:56.490 --> 00:08:56.500 align:start position:0% that came up from many is that the you 00:08:56.500 --> 00:08:58.710 align:start position:0% that came up from many is that the you should<00:08:56.710> start<00:08:57.070> explaining<00:08:57.670> the<00:08:57.820> benefits<00:08:58.060> and 00:08:58.710 --> 00:08:58.720 align:start position:0% should start explaining the benefits and 00:08:58.720 --> 00:09:00.660 align:start position:0% should start explaining the benefits and not<00:08:59.350> the<00:08:59.500> technology<00:09:00.100> this<00:09:00.220> is<00:09:00.370> something 00:09:00.660 --> 00:09:00.670 align:start position:0% not the technology this is something 00:09:00.670 --> 00:09:03.300 align:start position:0% not the technology this is something dabs<00:09:00.910> are<00:09:01.120> completely<00:09:01.600> finding<00:09:01.900> and<00:09:02.020> doing<00:09:02.310> so 00:09:03.300 --> 00:09:03.310 align:start position:0% dabs are completely finding and doing so 00:09:03.310 --> 00:09:05.130 align:start position:0% dabs are completely finding and doing so we<00:09:03.550> quickly<00:09:03.760> went<00:09:04.180> over<00:09:04.360> the<00:09:04.510> issues<00:09:04.810> with<00:09:04.930> gas 00:09:05.130 --> 00:09:05.140 align:start position:0% we quickly went over the issues with gas 00:09:05.140 --> 00:09:07.590 align:start position:0% we quickly went over the issues with gas but<00:09:05.410> the<00:09:05.590> underlying<00:09:06.550> issues<00:09:06.880> for<00:09:07.330> the 00:09:07.590 --> 00:09:07.600 align:start position:0% but the underlying issues for the 00:09:07.600 --> 00:09:09.390 align:start position:0% but the underlying issues for the problem<00:09:07.870> space<00:09:08.050> are<00:09:08.290> that<00:09:08.500> it's<00:09:08.770> a<00:09:08.950> very<00:09:09.130> novel 00:09:09.390 --> 00:09:09.400 align:start position:0% problem space are that it's a very novel 00:09:09.400 --> 00:09:10.470 align:start position:0% problem space are that it's a very novel experience<00:09:09.970> people<00:09:10.150> don't<00:09:10.390> really 00:09:10.470 --> 00:09:10.480 align:start position:0% experience people don't really 00:09:10.480 --> 00:09:12.270 align:start position:0% experience people don't really understand<00:09:10.990> what<00:09:11.080> they<00:09:11.650> have<00:09:11.680> to<00:09:11.890> pay<00:09:12.040> fees 00:09:12.270 --> 00:09:12.280 align:start position:0% understand what they have to pay fees 00:09:12.280 --> 00:09:14.660 align:start position:0% understand what they have to pay fees were<00:09:12.580> interfacing<00:09:13.300> with<00:09:13.330> the<00:09:13.540> technology 00:09:14.660 --> 00:09:14.670 align:start position:0% were interfacing with the technology 00:09:14.670 --> 00:09:17.760 align:start position:0% were interfacing with the technology also<00:09:15.670> as<00:09:15.850> Beltran<00:09:16.420> was<00:09:16.510> mentioning<00:09:16.990> there's 00:09:17.760 --> 00:09:17.770 align:start position:0% also as Beltran was mentioning there's 00:09:17.770 --> 00:09:19.560 align:start position:0% also as Beltran was mentioning there's variations<00:09:18.310> in<00:09:18.550> gas<00:09:18.730> prices<00:09:18.760> and<00:09:19.300> that's<00:09:19.390> not 00:09:19.560 --> 00:09:19.570 align:start position:0% variations in gas prices and that's not 00:09:19.570 --> 00:09:21.720 align:start position:0% variations in gas prices and that's not really<00:09:19.780> conducive<00:09:19.960> for<00:09:20.500> mass<00:09:20.710> adoption<00:09:21.370> use 00:09:21.720 --> 00:09:21.730 align:start position:0% really conducive for mass adoption use 00:09:21.730 --> 00:09:23.940 align:start position:0% really conducive for mass adoption use cases<00:09:21.970> and<00:09:22.330> another<00:09:22.990> thing<00:09:23.230> is<00:09:23.380> the<00:09:23.500> concept 00:09:23.940 --> 00:09:23.950 align:start position:0% cases and another thing is the concept 00:09:23.950 --> 00:09:25.560 align:start position:0% cases and another thing is the concept and<00:09:24.040> the<00:09:24.130> terminology<00:09:24.670> of<00:09:24.700> gas<00:09:24.940> itself<00:09:25.390> is 00:09:25.560 --> 00:09:25.570 align:start position:0% and the terminology of gas itself is 00:09:25.570 --> 00:09:27.300 align:start position:0% and the terminology of gas itself is very<00:09:25.750> counterintuitive<00:09:26.260> and<00:09:26.920> the<00:09:26.980> analogy 00:09:27.300 --> 00:09:27.310 align:start position:0% very counterintuitive and the analogy 00:09:27.310 --> 00:09:29.520 align:start position:0% very counterintuitive and the analogy doesn't<00:09:27.550> match<00:09:27.760> up<00:09:27.790> with<00:09:28.090> speed<00:09:28.530> versus 00:09:29.520 --> 00:09:29.530 align:start position:0% doesn't match up with speed versus 00:09:29.530 --> 00:09:32.040 align:start position:0% doesn't match up with speed versus distance<00:09:29.980> but<00:09:30.850> we've<00:09:31.150> been<00:09:31.300> starting<00:09:31.600> to<00:09:31.720> see 00:09:32.040 --> 00:09:32.050 align:start position:0% distance but we've been starting to see 00:09:32.050 --> 00:09:33.570 align:start position:0% distance but we've been starting to see a<00:09:32.080> lot<00:09:32.290> of<00:09:32.410> emerging<00:09:32.740> patterns<00:09:33.100> come<00:09:33.250> out<00:09:33.400> from 00:09:33.570 --> 00:09:33.580 align:start position:0% a lot of emerging patterns come out from 00:09:33.580 --> 00:09:34.950 align:start position:0% a lot of emerging patterns come out from the<00:09:33.670> research<00:09:33.970> that<00:09:34.000> we're<00:09:34.270> doing<00:09:34.300> through 00:09:34.950 --> 00:09:34.960 align:start position:0% the research that we're doing through 00:09:34.960 --> 00:09:37.140 align:start position:0% the research that we're doing through the<00:09:35.080> community<00:09:35.440> efforts<00:09:35.800> and<00:09:36.040> those<00:09:36.910> things 00:09:37.140 --> 00:09:37.150 align:start position:0% the community efforts and those things 00:09:37.150 --> 00:09:39.270 align:start position:0% the community efforts and those things are<00:09:37.330> such<00:09:37.600> as<00:09:37.750> extracting<00:09:38.410> gas<00:09:38.590> interactions 00:09:39.270 --> 00:09:39.280 align:start position:0% are such as extracting gas interactions 00:09:39.280 --> 00:09:41.580 align:start position:0% are such as extracting gas interactions for<00:09:39.520> new<00:09:40.390> users<00:09:40.840> so<00:09:41.080> things<00:09:41.320> such<00:09:41.440> as 00:09:41.580 --> 00:09:41.590 align:start position:0% for new users so things such as 00:09:41.590 --> 00:09:43.230 align:start position:0% for new users so things such as universal<00:09:42.070> logins<00:09:42.430> relays<00:09:42.850> or<00:09:43.090> meta 00:09:43.230 --> 00:09:43.240 align:start position:0% universal logins relays or meta 00:09:43.240 --> 00:09:45.930 align:start position:0% universal logins relays or meta transactions<00:09:43.870> and<00:09:44.140> then<00:09:44.860> other<00:09:45.130> options<00:09:45.610> have 00:09:45.930 --> 00:09:45.940 align:start position:0% transactions and then other options have 00:09:45.940 --> 00:09:48.360 align:start position:0% transactions and then other options have kind<00:09:46.450> of<00:09:46.510> emerged<00:09:47.020> from<00:09:47.230> places<00:09:48.010> like<00:09:48.040> meta 00:09:48.360 --> 00:09:48.370 align:start position:0% kind of emerged from places like meta 00:09:48.370 --> 00:09:50.550 align:start position:0% kind of emerged from places like meta mask<00:09:48.640> and<00:09:49.000> my<00:09:49.330> crypto<00:09:49.720> where<00:09:49.930> you<00:09:50.380> give 00:09:50.550 --> 00:09:50.560 align:start position:0% mask and my crypto where you give 00:09:50.560 --> 00:09:52.500 align:start position:0% mask and my crypto where you give modular<00:09:51.100> options<00:09:51.580> for<00:09:51.850> people<00:09:51.970> to<00:09:52.180> have<00:09:52.300> low 00:09:52.500 --> 00:09:52.510 align:start position:0% modular options for people to have low 00:09:52.510 --> 00:09:55.380 align:start position:0% modular options for people to have low fast<00:09:52.930> or<00:09:53.200> varying<00:09:54.190> speeds<00:09:54.490> and<00:09:54.700> one<00:09:55.180> key 00:09:55.380 --> 00:09:55.390 align:start position:0% fast or varying speeds and one key 00:09:55.390 --> 00:09:57.540 align:start position:0% fast or varying speeds and one key insight<00:09:56.140> was<00:09:56.320> that<00:09:56.530> we<00:09:56.650> need<00:09:56.800> to<00:09:56.920> some<00:09:57.340> way 00:09:57.540 --> 00:09:57.550 align:start position:0% insight was that we need to some way 00:09:57.550 --> 00:09:59.400 align:start position:0% insight was that we need to some way standardize<00:09:58.150> gas<00:09:58.420> moving<00:09:58.870> forward<00:09:59.170> for<00:09:59.350> the 00:09:59.400 --> 00:09:59.410 align:start position:0% standardize gas moving forward for the 00:09:59.410 --> 00:10:03.210 align:start position:0% standardize gas moving forward for the entire<00:09:59.770> ecosystem<00:10:01.620> key<00:10:02.620> management<00:10:02.920> has<00:10:03.190> a 00:10:03.210 --> 00:10:03.220 align:start position:0% entire ecosystem key management has a 00:10:03.220 --> 00:10:04.710 align:start position:0% entire ecosystem key management has a similar<00:10:03.610> problem<00:10:03.820> space<00:10:04.150> where<00:10:04.330> people<00:10:04.570> don't 00:10:04.710 --> 00:10:04.720 align:start position:0% similar problem space where people don't 00:10:04.720 --> 00:10:06.060 align:start position:0% similar problem space where people don't really<00:10:04.840> understand<00:10:05.320> can<00:10:05.500> you<00:10:05.620> reset<00:10:05.950> my 00:10:06.060 --> 00:10:06.070 align:start position:0% really understand can you reset my 00:10:06.070 --> 00:10:07.980 align:start position:0% really understand can you reset my password<00:10:06.210> we<00:10:07.210> need<00:10:07.240> to<00:10:07.450> do<00:10:07.510> a<00:10:07.570> better<00:10:07.720> job<00:10:07.810> of 00:10:07.980 --> 00:10:07.990 align:start position:0% password we need to do a better job of 00:10:07.990 --> 00:10:10.680 align:start position:0% password we need to do a better job of explaining<00:10:08.230> how<00:10:09.090> and<00:10:10.090> why<00:10:10.270> they<00:10:10.450> should<00:10:10.480> be 00:10:10.680 --> 00:10:10.690 align:start position:0% explaining how and why they should be 00:10:10.690 --> 00:10:12.300 align:start position:0% explaining how and why they should be backing<00:10:11.080> our<00:10:11.290> private<00:10:11.650> keys<00:10:11.800> and<00:10:12.010> maybe<00:10:12.130> just 00:10:12.300 --> 00:10:12.310 align:start position:0% backing our private keys and maybe just 00:10:12.310 --> 00:10:13.770 align:start position:0% backing our private keys and maybe just kind<00:10:12.550> of<00:10:12.610> get<00:10:12.760> rid<00:10:12.790> of<00:10:13.000> seat<00:10:13.240> phrases<00:10:13.630> all 00:10:13.770 --> 00:10:13.780 align:start position:0% kind of get rid of seat phrases all 00:10:13.780 --> 00:10:16.230 align:start position:0% kind of get rid of seat phrases all together<00:10:14.220> so<00:10:15.220> the<00:10:15.340> problem<00:10:15.640> space<00:10:15.790> with<00:10:16.030> the 00:10:16.230 --> 00:10:16.240 align:start position:0% together so the problem space with the 00:10:16.240 --> 00:10:17.970 align:start position:0% together so the problem space with the key<00:10:16.510> management<00:10:16.690> is<00:10:16.990> it<00:10:17.170> disrupts<00:10:17.830> the 00:10:17.970 --> 00:10:17.980 align:start position:0% key management is it disrupts the 00:10:17.980 --> 00:10:20.270 align:start position:0% key management is it disrupts the onboarding<00:10:18.430> flow<00:10:18.580> of<00:10:18.880> the<00:10:19.420> whole<00:10:19.600> interface 00:10:20.270 --> 00:10:20.280 align:start position:0% onboarding flow of the whole interface 00:10:20.280 --> 00:10:22.710 align:start position:0% onboarding flow of the whole interface people<00:10:21.280> don't<00:10:21.430> really<00:10:21.640> know<00:10:21.790> when<00:10:22.270> or<00:10:22.510> why<00:10:22.690> or 00:10:22.710 --> 00:10:22.720 align:start position:0% people don't really know when or why or 00:10:22.720 --> 00:10:24.540 align:start position:0% people don't really know when or why or why<00:10:23.140> they<00:10:23.320> should<00:10:23.500> be<00:10:23.650> backing<00:10:24.100> up<00:10:24.310> keys 00:10:24.540 --> 00:10:24.550 align:start position:0% why they should be backing up keys 00:10:24.550 --> 00:10:26.490 align:start position:0% why they should be backing up keys there's<00:10:25.150> a<00:10:25.240> confusion<00:10:25.660> between<00:10:25.900> passwords 00:10:26.490 --> 00:10:26.500 align:start position:0% there's a confusion between passwords 00:10:26.500 --> 00:10:28.470 align:start position:0% there's a confusion between passwords and<00:10:26.710> private<00:10:27.010> keys<00:10:27.190> and<00:10:27.490> people<00:10:28.090> kind<00:10:28.240> of<00:10:28.330> give 00:10:28.470 --> 00:10:28.480 align:start position:0% and private keys and people kind of give 00:10:28.480 --> 00:10:30.720 align:start position:0% and private keys and people kind of give them<00:10:28.630> wages<00:10:29.200> for<00:10:29.440> air<00:10:29.740> drops<00:10:30.100> and<00:10:30.370> lose<00:10:30.550> all 00:10:30.720 --> 00:10:30.730 align:start position:0% them wages for air drops and lose all 00:10:30.730 --> 00:10:32.940 align:start position:0% them wages for air drops and lose all their<00:10:30.850> finances<00:10:31.420> and<00:10:31.750> the<00:10:32.350> biggest<00:10:32.620> issue<00:10:32.740> is 00:10:32.940 --> 00:10:32.950 align:start position:0% their finances and the biggest issue is 00:10:32.950 --> 00:10:34.800 align:start position:0% their finances and the biggest issue is there's<00:10:33.190> a<00:10:33.250> lack<00:10:33.430> of<00:10:33.460> recoverability<00:10:34.120> so 00:10:34.800 --> 00:10:34.810 align:start position:0% there's a lack of recoverability so 00:10:34.810 --> 00:10:37.550 align:start position:0% there's a lack of recoverability so emerging<00:10:35.200> patterns<00:10:35.560> are<00:10:35.910> progressive<00:10:36.910> you 00:10:37.550 --> 00:10:37.560 align:start position:0% emerging patterns are progressive you 00:10:37.560 --> 00:10:39.840 align:start position:0% emerging patterns are progressive you tiered<00:10:38.560> your<00:10:38.740> security<00:10:39.070> models<00:10:39.370> so<00:10:39.550> you<00:10:39.640> kind 00:10:39.840 --> 00:10:39.850 align:start position:0% tiered your security models so you kind 00:10:39.850 --> 00:10:43.590 align:start position:0% tiered your security models so you kind of<00:10:40.530> work<00:10:41.530> the<00:10:41.740> user<00:10:41.920> into<00:10:42.460> knowing<00:10:42.850> what<00:10:43.570> a 00:10:43.590 --> 00:10:43.600 align:start position:0% of work the user into knowing what a 00:10:43.600 --> 00:10:45.810 align:start position:0% of work the user into knowing what a private<00:10:44.050> key<00:10:44.200> is<00:10:44.380> through<00:10:45.100> progressive 00:10:45.810 --> 00:10:45.820 align:start position:0% private key is through progressive 00:10:45.820 --> 00:10:47.970 align:start position:0% private key is through progressive models<00:10:46.360> like<00:10:46.510> universal<00:10:46.990> logins<00:10:47.230> is<00:10:47.350> using<00:10:47.710> or 00:10:47.970 --> 00:10:47.980 align:start position:0% models like universal logins is using or 00:10:47.980 --> 00:10:49.650 align:start position:0% models like universal logins is using or maybe<00:10:48.280> use<00:10:48.520> some<00:10:48.550> disposable<00:10:49.090> keys<00:10:49.480> that 00:10:49.650 --> 00:10:49.660 align:start position:0% maybe use some disposable keys that 00:10:49.660 --> 00:10:51.240 align:start position:0% maybe use some disposable keys that users<00:10:50.020> don't<00:10:50.140> actually<00:10:50.350> have<00:10:50.530> to<00:10:50.590> backup<00:10:51.010> or 00:10:51.240 --> 00:10:51.250 align:start position:0% users don't actually have to backup or 00:10:51.250 --> 00:10:53.160 align:start position:0% users don't actually have to backup or maybe<00:10:51.700> do<00:10:51.910> multiple<00:10:52.330> device<00:10:52.570> private<00:10:52.900> keys<00:10:53.050> on 00:10:53.160 --> 00:10:53.170 align:start position:0% maybe do multiple device private keys on 00:10:53.170 --> 00:10:55.890 align:start position:0% maybe do multiple device private keys on local<00:10:53.470> wallets<00:10:54.510> transactions<00:10:55.510> people<00:10:55.750> don't 00:10:55.890 --> 00:10:55.900 align:start position:0% local wallets transactions people don't 00:10:55.900 --> 00:10:57.030 align:start position:0% local wallets transactions people don't really<00:10:55.990> understand<00:10:56.440> why<00:10:56.590> it's<00:10:56.770> taking<00:10:56.800> so 00:10:57.030 --> 00:10:57.040 align:start position:0% really understand why it's taking so 00:10:57.040 --> 00:10:58.920 align:start position:0% really understand why it's taking so long<00:10:57.190> and<00:10:57.640> we<00:10:57.730> need<00:10:57.850> to<00:10:57.940> get<00:10:58.090> rid<00:10:58.570> of<00:10:58.630> things 00:10:58.920 --> 00:10:58.930 align:start position:0% long and we need to get rid of things 00:10:58.930 --> 00:11:00.980 align:start position:0% long and we need to get rid of things such<00:10:59.140> as<00:10:59.170> the<00:10:59.380> nonce 00:11:00.980 --> 00:11:00.990 align:start position:0% such as the nonce 00:11:00.990 --> 00:11:03.960 align:start position:0% such as the nonce so<00:11:01.990> people<00:11:02.890> don't<00:11:03.040> really<00:11:03.160> understand<00:11:03.760> one 00:11:03.960 --> 00:11:03.970 align:start position:0% so people don't really understand one 00:11:03.970 --> 00:11:05.250 align:start position:0% so people don't really understand one key<00:11:04.120> inside<00:11:04.390> that<00:11:04.510> we<00:11:04.600> got<00:11:04.720> from<00:11:04.870> the<00:11:05.020> larger 00:11:05.250 --> 00:11:05.260 align:start position:0% key inside that we got from the larger 00:11:05.260 --> 00:11:06.750 align:start position:0% key inside that we got from the larger projects<00:11:05.650> was<00:11:05.830> that<00:11:06.070> they<00:11:06.220> don't<00:11:06.400> understand 00:11:06.750 --> 00:11:06.760 align:start position:0% projects was that they don't understand 00:11:06.760 --> 00:11:08.070 align:start position:0% projects was that they don't understand the<00:11:06.880> relationship<00:11:06.970> between<00:11:07.570> what<00:11:08.020> the 00:11:08.070 --> 00:11:08.080 align:start position:0% the relationship between what the 00:11:08.080 --> 00:11:10.890 align:start position:0% the relationship between what the transaction<00:11:08.470> is<00:11:08.770> what<00:11:08.980> a<00:11:09.010> wallet<00:11:09.430> is<00:11:09.630> how<00:11:10.630> that 00:11:10.890 --> 00:11:10.900 align:start position:0% transaction is what a wallet is how that 00:11:10.900 --> 00:11:12.150 align:start position:0% transaction is what a wallet is how that relates<00:11:11.170> to<00:11:11.230> the<00:11:11.320> blockchain<00:11:11.620> and<00:11:11.860> what 00:11:12.150 --> 00:11:12.160 align:start position:0% relates to the blockchain and what 00:11:12.160 --> 00:11:13.920 align:start position:0% relates to the blockchain and what things<00:11:12.370> like<00:11:12.520> either<00:11:12.940> scan<00:11:13.270> actually<00:11:13.570> enables 00:11:13.920 --> 00:11:13.930 align:start position:0% things like either scan actually enables 00:11:13.930 --> 00:11:15.720 align:start position:0% things like either scan actually enables for<00:11:14.260> them<00:11:14.350> to<00:11:14.470> do<00:11:14.590> because<00:11:15.100> a<00:11:15.250> lot<00:11:15.520> of<00:11:15.640> the 00:11:15.720 --> 00:11:15.730 align:start position:0% for them to do because a lot of the 00:11:15.730 --> 00:11:17.910 align:start position:0% for them to do because a lot of the support<00:11:15.880> tickets<00:11:16.390> end<00:11:16.630> up<00:11:16.780> into<00:11:17.020> either<00:11:17.470> scans 00:11:17.910 --> 00:11:17.920 align:start position:0% support tickets end up into either scans 00:11:17.920 --> 00:11:20.340 align:start position:0% support tickets end up into either scans mailboxes<00:11:18.580> where<00:11:18.790> people<00:11:19.150> don't<00:11:19.900> really<00:11:20.140> know 00:11:20.340 --> 00:11:20.350 align:start position:0% mailboxes where people don't really know 00:11:20.350 --> 00:11:22.170 align:start position:0% mailboxes where people don't really know that<00:11:20.560> they're<00:11:20.710> not<00:11:20.740> responsible<00:11:21.640> responsible 00:11:22.170 --> 00:11:22.180 align:start position:0% that they're not responsible responsible 00:11:22.180 --> 00:11:24.630 align:start position:0% that they're not responsible responsible for<00:11:22.390> anything<00:11:22.920> emerging<00:11:23.920> patterns<00:11:24.280> is<00:11:24.400> out<00:11:24.550> of 00:11:24.630 --> 00:11:24.640 align:start position:0% for anything emerging patterns is out of 00:11:24.640 --> 00:11:26.280 align:start position:0% for anything emerging patterns is out of this<00:11:24.790> space<00:11:25.030> are<00:11:25.270> giving<00:11:25.630> human<00:11:25.930> readability 00:11:26.280 --> 00:11:26.290 align:start position:0% this space are giving human readability 00:11:26.290 --> 00:11:28.320 align:start position:0% this space are giving human readability and<00:11:26.530> transparency<00:11:27.340> to<00:11:27.460> their<00:11:27.790> transactions 00:11:28.320 --> 00:11:28.330 align:start position:0% and transparency to their transactions 00:11:28.330 --> 00:11:30.390 align:start position:0% and transparency to their transactions so<00:11:28.480> things<00:11:28.750> like<00:11:28.900> NAT<00:11:29.410> spec<00:11:29.770> and<00:11:29.980> R<00:11:30.010> aspect 00:11:30.390 --> 00:11:30.400 align:start position:0% so things like NAT spec and R aspect 00:11:30.400 --> 00:11:32.700 align:start position:0% so things like NAT spec and R aspect that<00:11:30.490> are<00:11:30.610> coming<00:11:30.850> out<00:11:31.000> and<00:11:31.720> then<00:11:32.410> from<00:11:32.620> the 00:11:32.700 --> 00:11:32.710 align:start position:0% that are coming out and then from the 00:11:32.710 --> 00:11:35.340 align:start position:0% that are coming out and then from the front<00:11:32.920> do<00:11:33.460> UI<00:11:33.700> perspective<00:11:34.390> maybe<00:11:34.810> giving<00:11:35.200> in 00:11:35.340 --> 00:11:35.350 align:start position:0% front do UI perspective maybe giving in 00:11:35.350 --> 00:11:40.440 align:start position:0% front do UI perspective maybe giving in that<00:11:35.530> history<00:11:35.860> and<00:11:36.120> transaction<00:11:37.120> context<00:11:39.450> two 00:11:40.440 --> 00:11:40.450 align:start position:0% that history and transaction context two 00:11:40.450 --> 00:11:42.480 align:start position:0% that history and transaction context two main<00:11:40.660> insights<00:11:41.110> beyond<00:11:41.650> the<00:11:41.770> questions<00:11:42.160> are 00:11:42.480 --> 00:11:42.490 align:start position:0% main insights beyond the questions are 00:11:42.490 --> 00:11:45.180 align:start position:0% main insights beyond the questions are everybody<00:11:43.390> thinks<00:11:43.900> that<00:11:43.930> mobile<00:11:44.500> will<00:11:44.800> be<00:11:44.980> the 00:11:45.180 --> 00:11:45.190 align:start position:0% everybody thinks that mobile will be the 00:11:45.190 --> 00:11:47.850 align:start position:0% everybody thinks that mobile will be the future<00:11:45.640> of<00:11:45.970> onboarding<00:11:46.780> the<00:11:47.170> next<00:11:47.500> wave<00:11:47.710> of 00:11:47.850 --> 00:11:47.860 align:start position:0% future of onboarding the next wave of 00:11:47.860 --> 00:11:49.410 align:start position:0% future of onboarding the next wave of users<00:11:48.220> but<00:11:48.460> everybody<00:11:48.880> is<00:11:49.000> working<00:11:49.180> on 00:11:49.410 --> 00:11:49.420 align:start position:0% users but everybody is working on 00:11:49.420 --> 00:11:53.010 align:start position:0% users but everybody is working on desktop<00:11:49.900> ok<00:11:50.230> some<00:11:50.890> exceptions<00:11:51.520> apply<00:11:51.820> and<00:11:52.150> the 00:11:53.010 --> 00:11:53.020 align:start position:0% desktop ok some exceptions apply and the 00:11:53.020 --> 00:11:55.620 align:start position:0% desktop ok some exceptions apply and the second<00:11:53.470> most<00:11:53.650> important<00:11:54.220> one<00:11:54.400> relates<00:11:55.390> to 00:11:55.620 --> 00:11:55.630 align:start position:0% second most important one relates to 00:11:55.630 --> 00:11:57.960 align:start position:0% second most important one relates to what<00:11:56.230> we<00:11:56.380> are<00:11:56.470> trying<00:11:56.770> to<00:11:56.830> do<00:11:57.010> also<00:11:57.160> with<00:11:57.310> a<00:11:57.460> def 00:11:57.960 --> 00:11:57.970 align:start position:0% what we are trying to do also with a def 00:11:57.970 --> 00:11:59.760 align:start position:0% what we are trying to do also with a def con<00:11:58.180> track<00:11:58.450> design<00:11:59.200> track<00:11:59.440> which<00:11:59.740> is 00:11:59.760 --> 00:11:59.770 align:start position:0% con track design track which is 00:11:59.770 --> 00:12:02.370 align:start position:0% con track design track which is everybody<00:12:00.760> agrees<00:12:01.090> that<00:12:01.120> designers<00:12:01.960> need<00:12:02.200> to 00:12:02.370 --> 00:12:02.380 align:start position:0% everybody agrees that designers need to 00:12:02.380 --> 00:12:04.320 align:start position:0% everybody agrees that designers need to be<00:12:02.560> in<00:12:02.680> the<00:12:02.800> room<00:12:02.950> since<00:12:03.280> day<00:12:03.460> one<00:12:03.790> since<00:12:04.120> they 00:12:04.320 --> 00:12:04.330 align:start position:0% be in the room since day one since they 00:12:04.330 --> 00:12:07.560 align:start position:0% be in the room since day one since they zero<00:12:04.690> actually<00:12:04.960> okay<00:12:05.770> simple<00:12:06.640> smart 00:12:07.560 --> 00:12:07.570 align:start position:0% zero actually okay simple smart 00:12:07.570 --> 00:12:10.740 align:start position:0% zero actually okay simple smart contracts<00:12:08.200> create<00:12:08.680> complex<00:12:09.430> UX<00:12:09.940> patterns<00:12:10.450> so 00:12:10.740 --> 00:12:10.750 align:start position:0% contracts create complex UX patterns so 00:12:10.750 --> 00:12:13.770 align:start position:0% contracts create complex UX patterns so get<00:12:11.320> a<00:12:11.350> designer<00:12:11.770> in<00:12:12.430> your<00:12:12.730> team<00:12:13.000> from<00:12:13.360> day<00:12:13.540> one 00:12:13.770 --> 00:12:13.780 align:start position:0% get a designer in your team from day one 00:12:13.780 --> 00:12:17.430 align:start position:0% get a designer in your team from day one and<00:12:14.110> I'll<00:12:14.440> pass<00:12:14.680> it<00:12:14.890> to<00:12:14.920> Gustavo<00:12:16.200> yeah<00:12:17.200> thank 00:12:17.430 --> 00:12:17.440 align:start position:0% and I'll pass it to Gustavo yeah thank 00:12:17.440 --> 00:12:20.040 align:start position:0% and I'll pass it to Gustavo yeah thank you<00:12:17.500> and<00:12:17.790> we<00:12:18.790> will<00:12:18.970> have<00:12:19.120> also<00:12:19.300> another<00:12:19.720> slide 00:12:20.040 --> 00:12:20.050 align:start position:0% you and we will have also another slide 00:12:20.050 --> 00:12:22.200 align:start position:0% you and we will have also another slide where<00:12:20.320> you<00:12:20.440> can<00:12:20.680> take<00:12:21.280> a<00:12:21.310> screenshot<00:12:21.610> to<00:12:21.910> come 00:12:22.200 --> 00:12:22.210 align:start position:0% where you can take a screenshot to come 00:12:22.210 --> 00:12:23.220 align:start position:0% where you can take a screenshot to come and<00:12:22.420> talk<00:12:22.900> to<00:12:22.930> us 00:12:23.220 --> 00:12:23.230 align:start position:0% and talk to us 00:12:23.230 --> 00:12:25.020 align:start position:0% and talk to us we<00:12:23.710> want<00:12:23.920> to<00:12:23.980> interview<00:12:24.340> you<00:12:24.400> get<00:12:24.850> your 00:12:25.020 --> 00:12:25.030 align:start position:0% we want to interview you get your 00:12:25.030 --> 00:12:26.850 align:start position:0% we want to interview you get your insights<00:12:25.450> and<00:12:25.660> we<00:12:25.990> will<00:12:26.140> be<00:12:26.290> posting<00:12:26.470> this 00:12:26.850 --> 00:12:26.860 align:start position:0% insights and we will be posting this 00:12:26.860 --> 00:12:29.070 align:start position:0% insights and we will be posting this mental<00:12:27.220> framework<00:12:27.610> and<00:12:27.850> also<00:12:28.270> the<00:12:28.720> future 00:12:29.070 --> 00:12:29.080 align:start position:0% mental framework and also the future 00:12:29.080 --> 00:12:39.870 align:start position:0% mental framework and also the future components<00:12:35.040> thank<00:12:36.040> you<00:12:38.460> thank<00:12:39.460> you<00:12:39.490> Beltran 00:12:39.870 --> 00:12:39.880 align:start position:0% components thank you thank you Beltran 00:12:39.880 --> 00:12:41.670 align:start position:0% components thank you thank you Beltran Akhil<00:12:40.180> my<00:12:40.630> name<00:12:40.720> is<00:12:40.780> Gustavo<00:12:41.230> guys<00:12:41.410> I'm<00:12:41.560> here 00:12:41.670 --> 00:12:41.680 align:start position:0% Akhil my name is Gustavo guys I'm here 00:12:41.680 --> 00:12:43.200 align:start position:0% Akhil my name is Gustavo guys I'm here with<00:12:41.740> consensus<00:12:42.370> design<00:12:42.700> and<00:12:42.880> I'm<00:12:42.940> gonna<00:12:43.030> talk 00:12:43.200 --> 00:12:43.210 align:start position:0% with consensus design and I'm gonna talk 00:12:43.210 --> 00:12:44.280 align:start position:0% with consensus design and I'm gonna talk to<00:12:43.240> you<00:12:43.420> I'm<00:12:43.660> gonna<00:12:43.750> show<00:12:43.990> you<00:12:44.080> guys<00:12:44.140> a<00:12:44.230> little 00:12:44.280 --> 00:12:44.290 align:start position:0% to you I'm gonna show you guys a little 00:12:44.290 --> 00:12:46.590 align:start position:0% to you I'm gonna show you guys a little bit<00:12:44.530> of<00:12:44.650> what<00:12:44.830> we<00:12:44.950> are<00:12:45.190> working<00:12:45.340> with<00:12:45.580> and<00:12:45.880> what 00:12:46.590 --> 00:12:46.600 align:start position:0% bit of what we are working with and what 00:12:46.600 --> 00:12:48.120 align:start position:0% bit of what we are working with and what we<00:12:46.690> hope<00:12:46.900> to<00:12:46.960> accomplish<00:12:47.110> in<00:12:47.500> the<00:12:47.590> space<00:12:47.830> and 00:12:48.120 --> 00:12:48.130 align:start position:0% we hope to accomplish in the space and 00:12:48.130 --> 00:12:49.710 align:start position:0% we hope to accomplish in the space and bring<00:12:48.400> into<00:12:48.730> the<00:12:48.880> this<00:12:49.150> initiative<00:12:49.600> and 00:12:49.710 --> 00:12:49.720 align:start position:0% bring into the this initiative and 00:12:49.720 --> 00:12:52.350 align:start position:0% bring into the this initiative and design<00:12:49.960> systems<00:12:50.320> we<00:12:51.100> are<00:12:51.520> calling<00:12:51.940> a<00:12:52.030> Trimble 00:12:52.350 --> 00:12:52.360 align:start position:0% design systems we are calling a Trimble 00:12:52.360 --> 00:12:55.260 align:start position:0% design systems we are calling a Trimble and<00:12:52.800> our<00:12:53.800> mission<00:12:54.250> is<00:12:54.400> to<00:12:54.430> make<00:12:54.880> it<00:12:55.000> easier<00:12:55.240> for 00:12:55.260 --> 00:12:55.270 align:start position:0% and our mission is to make it easier for 00:12:55.270 --> 00:12:56.760 align:start position:0% and our mission is to make it easier for developers<00:12:55.510> to<00:12:56.020> build<00:12:56.140> depths<00:12:56.530> without 00:12:56.760 --> 00:12:56.770 align:start position:0% developers to build depths without 00:12:56.770 --> 00:12:59.250 align:start position:0% developers to build depths without standing<00:12:57.130> UX<00:12:57.460> the<00:12:58.390> way<00:12:58.480> we're<00:12:58.630> doing<00:12:58.750> this<00:12:58.900> is 00:12:59.250 --> 00:12:59.260 align:start position:0% standing UX the way we're doing this is 00:12:59.260 --> 00:13:01.740 align:start position:0% standing UX the way we're doing this is by<00:12:59.770> partnering<00:13:00.220> with<00:13:00.400> some<00:13:01.090> of<00:13:01.330> the<00:13:01.600> leading 00:13:01.740 --> 00:13:01.750 align:start position:0% by partnering with some of the leading 00:13:01.750 --> 00:13:03.150 align:start position:0% by partnering with some of the leading companies<00:13:02.110> in<00:13:02.140> the<00:13:02.350> space<00:13:02.560> and<00:13:02.770> their<00:13:02.890> design 00:13:03.150 --> 00:13:03.160 align:start position:0% companies in the space and their design 00:13:03.160 --> 00:13:05.040 align:start position:0% companies in the space and their design teams<00:13:03.400> to<00:13:03.670> learn<00:13:04.360> about<00:13:04.510> their<00:13:04.750> insights 00:13:05.040 --> 00:13:05.050 align:start position:0% teams to learn about their insights 00:13:05.050 --> 00:13:07.130 align:start position:0% teams to learn about their insights learn<00:13:05.260> about<00:13:05.440> the<00:13:05.590> users<00:13:05.920> and<00:13:06.160> what<00:13:06.760> their 00:13:07.130 --> 00:13:07.140 align:start position:0% learn about the users and what their 00:13:07.140 --> 00:13:09.690 align:start position:0% learn about the users and what their what<00:13:08.140> their<00:13:08.320> struggles<00:13:08.500> are<00:13:08.740> and<00:13:08.770> how<00:13:09.430> these 00:13:09.690 --> 00:13:09.700 align:start position:0% what their struggles are and how these 00:13:09.700 --> 00:13:11.970 align:start position:0% what their struggles are and how these companies<00:13:09.970> have<00:13:10.240> been<00:13:10.330> solving<00:13:10.630> them<00:13:10.810> we<00:13:11.530> are 00:13:11.970 --> 00:13:11.980 align:start position:0% companies have been solving them we are 00:13:11.980 --> 00:13:13.410 align:start position:0% companies have been solving them we are going<00:13:12.130> to<00:13:12.190> take<00:13:12.340> this<00:13:12.430> insight<00:13:12.790> and<00:13:13.000> build<00:13:13.210> a 00:13:13.410 --> 00:13:13.420 align:start position:0% going to take this insight and build a 00:13:13.420 --> 00:13:14.040 align:start position:0% going to take this insight and build a reactor 00:13:14.040 --> 00:13:14.050 align:start position:0% reactor 00:13:14.050 --> 00:13:17.009 align:start position:0% reactor library<00:13:14.440> for<00:13:14.890> users<00:13:15.730> or<00:13:15.880> for<00:13:15.910> developers<00:13:16.660> to 00:13:17.009 --> 00:13:17.019 align:start position:0% library for users or for developers to 00:13:17.019 --> 00:13:19.530 align:start position:0% library for users or for developers to start<00:13:17.080> building<00:13:17.529> depths<00:13:18.130> with<00:13:18.310> some<00:13:18.670> patterns 00:13:19.530 --> 00:13:19.540 align:start position:0% start building depths with some patterns 00:13:19.540 --> 00:13:21.180 align:start position:0% start building depths with some patterns to<00:13:19.660> start<00:13:19.899> with<00:13:20.019> and<00:13:20.230> you<00:13:20.290> don't<00:13:20.380> have<00:13:20.560> to<00:13:20.680> do<00:13:21.160> a 00:13:21.180 --> 00:13:21.190 align:start position:0% to start with and you don't have to do a 00:13:21.190 --> 00:13:23.880 align:start position:0% to start with and you don't have to do a lot<00:13:21.459> of<00:13:21.490> guessing<00:13:21.880> from<00:13:21.970> day<00:13:22.149> one<00:13:22.740> some<00:13:23.740> of<00:13:23.769> the 00:13:23.880 --> 00:13:23.890 align:start position:0% lot of guessing from day one some of the 00:13:23.890 --> 00:13:26.610 align:start position:0% lot of guessing from day one some of the stuff<00:13:24.040> we<00:13:24.160> hear<00:13:24.279> about<00:13:24.399> is<00:13:24.700> gas<00:13:25.420> gas<00:13:26.350> and 00:13:26.610 --> 00:13:26.620 align:start position:0% stuff we hear about is gas gas and 00:13:26.620 --> 00:13:28.079 align:start position:0% stuff we hear about is gas gas and transactions<00:13:27.190> so<00:13:27.339> madam<00:13:27.580> s<00:13:27.670> has<00:13:27.820> been<00:13:27.940> doing 00:13:28.079 --> 00:13:28.089 align:start position:0% transactions so madam s has been doing 00:13:28.089 --> 00:13:31.199 align:start position:0% transactions so madam s has been doing wonderful<00:13:28.240> work<00:13:28.480> with<00:13:28.990> these<00:13:30.089> with<00:13:31.089> these 00:13:31.199 --> 00:13:31.209 align:start position:0% wonderful work with these with these 00:13:31.209 --> 00:13:32.699 align:start position:0% wonderful work with these with these teams<00:13:31.480> and<00:13:31.750> we<00:13:31.899> want<00:13:32.079> to<00:13:32.140> take<00:13:32.260> their<00:13:32.410> insights 00:13:32.699 --> 00:13:32.709 align:start position:0% teams and we want to take their insights 00:13:32.709 --> 00:13:34.920 align:start position:0% teams and we want to take their insights we<00:13:32.800> want<00:13:32.920> to<00:13:32.980> build<00:13:33.130> things<00:13:33.279> like<00:13:33.930> transaction 00:13:34.920 --> 00:13:34.930 align:start position:0% we want to build things like transaction 00:13:34.930 --> 00:13:37.259 align:start position:0% we want to build things like transaction components<00:13:35.620> into<00:13:36.040> Rimbaud<00:13:36.640> that<00:13:36.940> you<00:13:37.060> can 00:13:37.259 --> 00:13:37.269 align:start position:0% components into Rimbaud that you can 00:13:37.269 --> 00:13:39.780 align:start position:0% components into Rimbaud that you can import<00:13:37.870> and<00:13:38.200> start<00:13:38.440> using<00:13:38.560> from<00:13:38.829> day<00:13:38.980> one<00:13:39.160> we 00:13:39.780 --> 00:13:39.790 align:start position:0% import and start using from day one we 00:13:39.790 --> 00:13:42.780 align:start position:0% import and start using from day one we are<00:13:40.360> talking<00:13:40.720> with<00:13:40.930> bounties<00:13:41.860> to<00:13:41.890> figure<00:13:42.670> out 00:13:42.780 --> 00:13:42.790 align:start position:0% are talking with bounties to figure out 00:13:42.790 --> 00:13:44.040 align:start position:0% are talking with bounties to figure out what<00:13:43.060> their<00:13:43.180> users<00:13:43.329> are<00:13:43.570> wondering<00:13:43.899> what 00:13:44.040 --> 00:13:44.050 align:start position:0% what their users are wondering what 00:13:44.050 --> 00:13:45.600 align:start position:0% what their users are wondering what happens<00:13:44.350> when<00:13:44.620> something<00:13:45.130> goes<00:13:45.250> to<00:13:45.519> the 00:13:45.600 --> 00:13:45.610 align:start position:0% happens when something goes to the 00:13:45.610 --> 00:13:48.120 align:start position:0% happens when something goes to the blockchain<00:13:45.790> what's<00:13:46.570> that<00:13:46.720> all<00:13:46.839> about<00:13:47.040> so<00:13:48.040> we 00:13:48.120 --> 00:13:48.130 align:start position:0% blockchain what's that all about so we 00:13:48.130 --> 00:13:49.680 align:start position:0% blockchain what's that all about so we want<00:13:48.279> to<00:13:48.370> build<00:13:48.940> things<00:13:49.029> like<00:13:49.180> prompts<00:13:49.600> and 00:13:49.680 --> 00:13:49.690 align:start position:0% want to build things like prompts and 00:13:49.690 --> 00:13:51.509 align:start position:0% want to build things like prompts and alerts<00:13:49.930> to<00:13:50.110> educate<00:13:50.440> users<00:13:50.560> in<00:13:50.920> it<00:13:51.040> and<00:13:51.279> get 00:13:51.509 --> 00:13:51.519 align:start position:0% alerts to educate users in it and get 00:13:51.519 --> 00:13:53.819 align:start position:0% alerts to educate users in it and get them<00:13:51.610> to<00:13:51.700> developers<00:13:52.120> from<00:13:52.329> day<00:13:52.450> one<00:13:52.660> we<00:13:53.410> are 00:13:53.819 --> 00:13:53.829 align:start position:0% them to developers from day one we are 00:13:53.829 --> 00:13:56.970 align:start position:0% them to developers from day one we are talking<00:13:54.519> with<00:13:55.140> companies<00:13:56.140> like<00:13:56.290> you<00:13:56.410> port<00:13:56.649> to 00:13:56.970 --> 00:13:56.980 align:start position:0% talking with companies like you port to 00:13:56.980 --> 00:14:00.259 align:start position:0% talking with companies like you port to manage<00:13:57.370> identity<00:13:57.850> and<00:13:58.060> we<00:13:58.959> want<00:13:59.170> to<00:13:59.380> take 00:14:00.259 --> 00:14:00.269 align:start position:0% manage identity and we want to take 00:14:00.269 --> 00:14:02.639 align:start position:0% manage identity and we want to take their<00:14:01.269> insights<00:14:01.660> and<00:14:01.930> build<00:14:02.410> them<00:14:02.529> into 00:14:02.639 --> 00:14:02.649 align:start position:0% their insights and build them into 00:14:02.649 --> 00:14:04.530 align:start position:0% their insights and build them into Rimbaud<00:14:03.130> as<00:14:03.279> well<00:14:03.459> want<00:14:03.700> to<00:14:03.760> build<00:14:03.940> an<00:14:04.510> e 00:14:04.530 --> 00:14:04.540 align:start position:0% Rimbaud as well want to build an e 00:14:04.540 --> 00:14:06.240 align:start position:0% Rimbaud as well want to build an e components<00:14:05.079> to<00:14:05.200> Rimbaud<00:14:05.440> that<00:14:05.620> you<00:14:05.709> can<00:14:05.890> start 00:14:06.240 --> 00:14:06.250 align:start position:0% components to Rimbaud that you can start 00:14:06.250 --> 00:14:08.880 align:start position:0% components to Rimbaud that you can start using<00:14:06.339> from<00:14:06.820> day<00:14:06.970> one<00:14:07.180> so<00:14:07.959> that's<00:14:08.680> some<00:14:08.800> of<00:14:08.860> the 00:14:08.880 --> 00:14:08.890 align:start position:0% using from day one so that's some of the 00:14:08.890 --> 00:14:10.110 align:start position:0% using from day one so that's some of the things<00:14:09.100> are<00:14:09.190> we<00:14:09.250> working<00:14:09.550> on<00:14:09.640> if<00:14:09.850> you're 00:14:10.110 --> 00:14:10.120 align:start position:0% things are we working on if you're 00:14:10.120 --> 00:14:11.850 align:start position:0% things are we working on if you're interested<00:14:10.660> please<00:14:11.079> visit<00:14:11.410> rim<00:14:11.680> bolt 00:14:11.850 --> 00:14:11.860 align:start position:0% interested please visit rim bolt 00:14:11.860 --> 00:14:13.380 align:start position:0% interested please visit rim bolt consensus<00:14:12.399> at<00:14:12.550> design<00:14:12.820> and<00:14:13.029> join<00:14:13.269> our 00:14:13.380 --> 00:14:13.390 align:start position:0% consensus at design and join our 00:14:13.390 --> 00:14:16.079 align:start position:0% consensus at design and join our spectrum<00:14:13.750> chat<00:14:14.160> and<00:14:15.160> tell<00:14:15.700> us<00:14:15.790> what<00:14:15.880> you<00:14:15.940> think 00:14:16.079 --> 00:14:16.089 align:start position:0% spectrum chat and tell us what you think 00:14:16.089 --> 00:14:17.790 align:start position:0% spectrum chat and tell us what you think tell<00:14:16.329> us<00:14:16.450> about<00:14:16.630> your<00:14:16.930> pains<00:14:17.170> your<00:14:17.410> hopes<00:14:17.649> and 00:14:17.790 --> 00:14:17.800 align:start position:0% tell us about your pains your hopes and 00:14:17.800 --> 00:14:19.110 align:start position:0% tell us about your pains your hopes and your<00:14:17.890> dreams<00:14:17.980> and<00:14:18.430> want<00:14:18.640> to<00:14:18.670> build<00:14:18.790> this<00:14:18.970> with 00:14:19.110 --> 00:14:19.120 align:start position:0% your dreams and want to build this with 00:14:19.120 --> 00:14:25.650 align:start position:0% your dreams and want to build this with you<00:14:19.329> so<00:14:19.540> give<00:14:19.779> us<00:14:19.870> your<00:14:19.990> feedback<00:14:20.110> so<00:14:24.660> now 00:14:25.650 --> 00:14:25.660 align:start position:0% you so give us your feedback so now 00:14:25.660 --> 00:14:26.930 align:start position:0% you so give us your feedback so now we're<00:14:25.839> just<00:14:25.870> gonna<00:14:26.050> do<00:14:26.260> a<00:14:26.290> little<00:14:26.500> panel 00:14:26.930 --> 00:14:26.940 align:start position:0% we're just gonna do a little panel 00:14:26.940 --> 00:14:29.490 align:start position:0% we're just gonna do a little panel discussion<00:14:27.940> and<00:14:28.209> pose<00:14:28.540> some<00:14:28.779> questions<00:14:28.810> to 00:14:29.490 --> 00:14:29.500 align:start position:0% discussion and pose some questions to 00:14:29.500 --> 00:14:32.310 align:start position:0% discussion and pose some questions to you<00:14:29.860> both<00:14:30.630> what<00:14:31.630> do<00:14:31.690> you<00:14:31.750> think<00:14:31.899> is<00:14:31.990> the<00:14:32.110> role 00:14:32.310 --> 00:14:32.320 align:start position:0% you both what do you think is the role 00:14:32.320 --> 00:14:37.680 align:start position:0% you both what do you think is the role of<00:14:32.350> designers<00:14:33.100> in<00:14:33.279> this<00:14:33.370> space<00:14:36.060> thank<00:14:37.060> you<00:14:37.180> so 00:14:37.680 --> 00:14:37.690 align:start position:0% of designers in this space thank you so 00:14:37.690 --> 00:14:41.600 align:start position:0% of designers in this space thank you so we<00:14:38.380> are<00:14:38.529> here<00:14:38.740> to<00:14:38.950> simplify<00:14:39.610> your<00:14:39.640> lives<00:14:40.089> and 00:14:41.600 --> 00:14:41.610 align:start position:0% we are here to simplify your lives and 00:14:41.610 --> 00:14:44.790 align:start position:0% we are here to simplify your lives and we<00:14:42.610> want<00:14:42.940> to<00:14:43.060> show<00:14:43.300> you<00:14:43.329> that<00:14:43.630> design<00:14:44.110> or<00:14:44.560> you 00:14:44.790 --> 00:14:44.800 align:start position:0% we want to show you that design or you 00:14:44.800 --> 00:14:46.350 align:start position:0% we want to show you that design or you should<00:14:45.010> start<00:14:45.279> thinking<00:14:45.430> that<00:14:45.730> design<00:14:46.029> is<00:14:46.180> not 00:14:46.350 --> 00:14:46.360 align:start position:0% should start thinking that design is not 00:14:46.360 --> 00:14:48.360 align:start position:0% should start thinking that design is not UI<00:14:46.660> this<00:14:46.810> is<00:14:47.170> a<00:14:47.200> very<00:14:47.560> important 00:14:48.360 --> 00:14:48.370 align:start position:0% UI this is a very important 00:14:48.370 --> 00:14:52.920 align:start position:0% UI this is a very important misconception<00:14:49.120> of<00:14:50.370> everybody<00:14:51.370> and<00:14:51.930> design 00:14:52.920 --> 00:14:52.930 align:start position:0% misconception of everybody and design 00:14:52.930 --> 00:14:55.019 align:start position:0% misconception of everybody and design actually<00:14:53.410> has<00:14:53.589> a<00:14:53.620> lot<00:14:53.860> of<00:14:53.890> tools<00:14:54.310> there's<00:14:54.970> a 00:14:55.019 --> 00:14:55.029 align:start position:0% actually has a lot of tools there's a 00:14:55.029 --> 00:14:56.880 align:start position:0% actually has a lot of tools there's a lot<00:14:55.329> different<00:14:55.750> types<00:14:55.990> of<00:14:56.200> design<00:14:56.529> and<00:14:56.680> I<00:14:56.740> can 00:14:56.880 --> 00:14:56.890 align:start position:0% lot different types of design and I can 00:14:56.890 --> 00:14:58.769 align:start position:0% lot different types of design and I can help<00:14:57.070> you<00:14:57.220> at<00:14:57.339> different<00:14:57.670> moments<00:14:57.820> of<00:14:58.300> your<00:14:58.480> of 00:14:58.769 --> 00:14:58.779 align:start position:0% help you at different moments of your of 00:14:58.779 --> 00:15:01.189 align:start position:0% help you at different moments of your of your<00:14:59.140> project<00:14:59.560> there<00:14:59.709> is<00:14:59.740> service<00:15:00.459> design 00:15:01.189 --> 00:15:01.199 align:start position:0% your project there is service design 00:15:01.199 --> 00:15:05.010 align:start position:0% your project there is service design system<00:15:02.199> design<00:15:02.620> behavioral<00:15:03.610> design<00:15:03.820> and<00:15:04.360> all 00:15:05.010 --> 00:15:05.020 align:start position:0% system design behavioral design and all 00:15:05.020 --> 00:15:06.720 align:start position:0% system design behavioral design and all these<00:15:05.440> can<00:15:05.770> help<00:15:05.949> you<00:15:06.130> in<00:15:06.250> different<00:15:06.430> moments 00:15:06.720 --> 00:15:06.730 align:start position:0% these can help you in different moments 00:15:06.730 --> 00:15:11.360 align:start position:0% these can help you in different moments of<00:15:07.060> your<00:15:07.240> of<00:15:07.510> your<00:15:08.579> creation<00:15:09.579> of<00:15:09.760> of<00:15:10.660> your 00:15:11.360 --> 00:15:11.370 align:start position:0% of your of your creation of of your 00:15:11.370 --> 00:15:13.769 align:start position:0% of your of your creation of of your adapts<00:15:12.370> or<00:15:12.640> your<00:15:13.060> application<00:15:13.570> of<00:15:13.660> your 00:15:13.769 --> 00:15:13.779 align:start position:0% adapts or your application of your 00:15:13.779 --> 00:15:16.920 align:start position:0% adapts or your application of your projects<00:15:14.170> so<00:15:14.500> get<00:15:14.829> a<00:15:14.860> design<00:15:15.310> co-founder<00:15:16.029> come 00:15:16.920 --> 00:15:16.930 align:start position:0% projects so get a design co-founder come 00:15:16.930 --> 00:15:19.829 align:start position:0% projects so get a design co-founder come to<00:15:17.199> the<00:15:17.500> UX<00:15:17.949> audits<00:15:18.519> and<00:15:18.730> see<00:15:19.209> how<00:15:19.480> your 00:15:19.829 --> 00:15:19.839 align:start position:0% to the UX audits and see how your 00:15:19.839 --> 00:15:22.410 align:start position:0% to the UX audits and see how your mindset<00:15:20.380> can<00:15:20.740> change<00:15:21.040> after<00:15:21.579> one<00:15:21.910> hour<00:15:22.120> or 00:15:22.410 --> 00:15:22.420 align:start position:0% mindset can change after one hour or 00:15:22.420 --> 00:15:25.319 align:start position:0% mindset can change after one hour or spending<00:15:23.370> with<00:15:24.370> a<00:15:24.399> designer<00:15:24.790> helping<00:15:25.240> you 00:15:25.319 --> 00:15:25.329 align:start position:0% spending with a designer helping you 00:15:25.329 --> 00:15:26.910 align:start position:0% spending with a designer helping you through<00:15:25.600> your<00:15:25.810> own<00:15:25.870> depth<00:15:26.260> so<00:15:26.620> I<00:15:26.649> think<00:15:26.770> you 00:15:26.910 --> 00:15:26.920 align:start position:0% through your own depth so I think you 00:15:26.920 --> 00:15:28.439 align:start position:0% through your own depth so I think you made<00:15:27.040> a<00:15:27.070> really<00:15:27.160> good<00:15:27.490> point<00:15:27.670> about<00:15:27.850> service 00:15:28.439 --> 00:15:28.449 align:start position:0% made a really good point about service 00:15:28.449 --> 00:15:30.750 align:start position:0% made a really good point about service design<00:15:28.660> and<00:15:29.110> like<00:15:29.290> systems<00:15:30.190> design<00:15:30.520> how<00:15:30.699> do 00:15:30.750 --> 00:15:30.760 align:start position:0% design and like systems design how do 00:15:30.760 --> 00:15:32.670 align:start position:0% design and like systems design how do you<00:15:30.940> think<00:15:31.300> we<00:15:31.480> can<00:15:31.690> get<00:15:31.899> that<00:15:32.140> seed<00:15:32.440> on<00:15:32.589> the 00:15:32.670 --> 00:15:32.680 align:start position:0% you think we can get that seed on the 00:15:32.680 --> 00:15:34.650 align:start position:0% you think we can get that seed on the table<00:15:33.070> as<00:15:33.250> designers<00:15:34.089> when<00:15:34.240> people<00:15:34.540> are 00:15:34.650 --> 00:15:34.660 align:start position:0% table as designers when people are 00:15:34.660 --> 00:15:37.050 align:start position:0% table as designers when people are creating<00:15:35.170> these<00:15:35.370> ecosystems<00:15:36.370> and<00:15:36.490> platforms 00:15:37.050 --> 00:15:37.060 align:start position:0% creating these ecosystems and platforms 00:15:37.060 --> 00:15:39.210 align:start position:0% creating these ecosystems and platforms and<00:15:37.270> protocols<00:15:37.839> how<00:15:38.199> do<00:15:38.260> we<00:15:38.410> how<00:15:38.920> do<00:15:38.980> we<00:15:39.100> engage 00:15:39.210 --> 00:15:39.220 align:start position:0% and protocols how do we how do we engage 00:15:39.220 --> 00:15:47.430 align:start position:0% and protocols how do we how do we engage the<00:15:39.579> people<00:15:39.730> as<00:15:40.000> designers<00:15:44.160> for<00:15:45.160> sure<00:15:46.440> DEFCON 00:15:47.430 --> 00:15:47.440 align:start position:0% the people as designers for sure DEFCON 00:15:47.440 --> 00:15:49.670 align:start position:0% the people as designers for sure DEFCON is<00:15:47.470> working<00:15:48.370> a<00:15:48.520> bit<00:15:48.670> for<00:15:48.880> that<00:15:48.910> I<00:15:49.060> hope<00:15:49.390> that 00:15:49.670 --> 00:15:49.680 align:start position:0% is working a bit for that I hope that 00:15:49.680 --> 00:15:52.620 align:start position:0% is working a bit for that I hope that developers<00:15:50.680> are<00:15:50.829> working<00:15:51.130> up<00:15:51.579> waking<00:15:52.270> up<00:15:52.449> to 00:15:52.620 --> 00:15:52.630 align:start position:0% developers are working up waking up to 00:15:52.630 --> 00:15:54.960 align:start position:0% developers are working up waking up to that<00:15:52.660> through<00:15:53.529> the<00:15:53.649> design<00:15:53.949> system<00:15:54.399> we<00:15:54.730> are 00:15:54.960 --> 00:15:54.970 align:start position:0% that through the design system we are 00:15:54.970 --> 00:15:57.569 align:start position:0% that through the design system we are making<00:15:55.810> trying<00:15:56.290> to<00:15:56.410> make<00:15:56.620> your<00:15:56.860> life<00:15:57.130> easier 00:15:57.569 --> 00:15:57.579 align:start position:0% making trying to make your life easier 00:15:57.579 --> 00:16:00.090 align:start position:0% making trying to make your life easier and<00:15:57.819> maybe<00:15:58.120> you<00:15:58.390> discover<00:15:58.899> it<00:15:59.110> through<00:15:59.949> that 00:16:00.090 --> 00:16:00.100 align:start position:0% and maybe you discover it through that 00:16:00.100 --> 00:16:03.720 align:start position:0% and maybe you discover it through that as<00:16:00.250> well<00:16:00.430> come<00:16:01.060> to<00:16:01.649> rainbow<00:16:02.649> consensus<00:16:03.370> design 00:16:03.720 --> 00:16:03.730 align:start position:0% as well come to rainbow consensus design 00:16:03.730 --> 00:16:06.240 align:start position:0% as well come to rainbow consensus design and<00:16:04.060> to<00:16:04.270> on<00:16:04.420> complex<00:16:04.959> and<00:16:05.319> and<00:16:05.589> here<00:16:05.949> and<00:16:06.100> ask 00:16:06.240 --> 00:16:06.250 align:start position:0% and to on complex and and here and ask 00:16:06.250 --> 00:16:10.290 align:start position:0% and to on complex and and here and ask and<00:16:06.819> ask<00:16:07.089> questions<00:16:07.779> and<00:16:07.990> again<00:16:08.920> just<00:16:09.730> talk<00:16:10.060> to 00:16:10.290 --> 00:16:10.300 align:start position:0% and ask questions and again just talk to 00:16:10.300 --> 00:16:12.990 align:start position:0% and ask questions and again just talk to designers<00:16:11.020> from<00:16:11.649> day<00:16:11.920> one<00:16:12.130> if<00:16:12.339> you<00:16:12.459> want 00:16:12.990 --> 00:16:13.000 align:start position:0% designers from day one if you want 00:16:13.000 --> 00:16:14.939 align:start position:0% designers from day one if you want bring<00:16:13.360> the<00:16:13.600> designer<00:16:13.990> into<00:16:14.350> your<00:16:14.500> team<00:16:14.740> you 00:16:14.939 --> 00:16:14.949 align:start position:0% bring the designer into your team you 00:16:14.949 --> 00:16:18.569 align:start position:0% bring the designer into your team you will<00:16:15.130> see<00:16:15.310> how<00:16:15.490> it<00:16:15.569> works<00:16:16.980> yeah<00:16:17.980> Bob<00:16:18.279> just<00:16:18.520> so 00:16:18.569 --> 00:16:18.579 align:start position:0% will see how it works yeah Bob just so 00:16:18.579 --> 00:16:20.370 align:start position:0% will see how it works yeah Bob just so you<00:16:18.670> guys<00:16:18.790> said<00:16:19.000> I<00:16:19.029> think<00:16:19.300> we<00:16:19.660> have<00:16:19.779> design<00:16:20.230> at 00:16:20.370 --> 00:16:20.380 align:start position:0% you guys said I think we have design at 00:16:20.380 --> 00:16:22.410 align:start position:0% you guys said I think we have design at DEFCON<00:16:20.770> today<00:16:21.220> this<00:16:21.459> year<00:16:21.760> so<00:16:22.000> I<00:16:22.029> think<00:16:22.149> that's 00:16:22.410 --> 00:16:22.420 align:start position:0% DEFCON today this year so I think that's 00:16:22.420 --> 00:16:24.120 align:start position:0% DEFCON today this year so I think that's a<00:16:22.480> great<00:16:22.600> start<00:16:22.779> let's<00:16:23.110> bring<00:16:23.290> designers<00:16:23.890> into 00:16:24.120 --> 00:16:24.130 align:start position:0% a great start let's bring designers into 00:16:24.130 --> 00:16:26.100 align:start position:0% a great start let's bring designers into the<00:16:24.220> space<00:16:24.459> let's<00:16:25.240> involve<00:16:25.480> designers<00:16:25.959> from 00:16:26.100 --> 00:16:26.110 align:start position:0% the space let's involve designers from 00:16:26.110 --> 00:16:28.139 align:start position:0% the space let's involve designers from day<00:16:26.230> one<00:16:26.440> let's<00:16:27.100> start<00:16:27.250> talking<00:16:27.550> about<00:16:27.880> design 00:16:28.139 --> 00:16:28.149 align:start position:0% day one let's start talking about design 00:16:28.149 --> 00:16:29.699 align:start position:0% day one let's start talking about design talking<00:16:28.480> about<00:16:28.630> design<00:16:28.899> systems<00:16:29.319> and<00:16:29.500> get<00:16:29.620> the 00:16:29.699 --> 00:16:29.709 align:start position:0% talking about design systems and get the 00:16:29.709 --> 00:16:31.019 align:start position:0% talking about design systems and get the conversation<00:16:30.010> going<00:16:30.279> and<00:16:30.520> I<00:16:30.699> think<00:16:30.880> that's 00:16:31.019 --> 00:16:31.029 align:start position:0% conversation going and I think that's 00:16:31.029 --> 00:16:33.030 align:start position:0% conversation going and I think that's how<00:16:31.149> we<00:16:31.209> really<00:16:31.510> incorporate<00:16:32.140> this<00:16:32.500> into<00:16:32.770> the 00:16:33.030 --> 00:16:33.040 align:start position:0% how we really incorporate this into the 00:16:33.040 --> 00:16:35.850 align:start position:0% how we really incorporate this into the ecosystem<00:16:33.459> and<00:16:33.880> into<00:16:34.149> the<00:16:34.319> watching<00:16:35.319> space<00:16:35.560> so 00:16:35.850 --> 00:16:35.860 align:start position:0% ecosystem and into the watching space so 00:16:35.860 --> 00:16:37.530 align:start position:0% ecosystem and into the watching space so now<00:16:35.890> we<00:16:36.220> have<00:16:36.399> designers<00:16:36.819> in<00:16:36.940> this<00:16:37.060> space<00:16:37.270> how 00:16:37.530 --> 00:16:37.540 align:start position:0% now we have designers in this space how 00:16:37.540 --> 00:16:38.970 align:start position:0% now we have designers in this space how do<00:16:37.600> you<00:16:37.720> think<00:16:37.839> we<00:16:38.020> bring<00:16:38.170> more<00:16:38.350> users<00:16:38.740> into 00:16:38.970 --> 00:16:38.980 align:start position:0% do you think we bring more users into 00:16:38.980 --> 00:16:41.699 align:start position:0% do you think we bring more users into the<00:16:39.100> space<00:16:39.480> well<00:16:40.480> I'm<00:16:40.750> biased<00:16:41.110> I'm<00:16:41.290> a<00:16:41.380> designer 00:16:41.699 --> 00:16:41.709 align:start position:0% the space well I'm biased I'm a designer 00:16:41.709 --> 00:16:44.040 align:start position:0% the space well I'm biased I'm a designer so<00:16:42.100> my<00:16:42.459> point<00:16:42.699> of<00:16:42.790> view<00:16:42.910> is<00:16:43.089> that<00:16:43.120> design<00:16:43.839> kind 00:16:44.040 --> 00:16:44.050 align:start position:0% so my point of view is that design kind 00:16:44.050 --> 00:16:45.660 align:start position:0% so my point of view is that design kind of<00:16:44.230> can<00:16:44.620> help<00:16:44.829> solve<00:16:45.040> everything<00:16:45.490> I<00:16:45.610> think 00:16:45.660 --> 00:16:45.670 align:start position:0% of can help solve everything I think 00:16:45.670 --> 00:16:47.400 align:start position:0% of can help solve everything I think it's<00:16:45.850> a<00:16:46.060> problem-solving<00:16:46.810> mindset<00:16:47.199> and<00:16:47.350> I 00:16:47.400 --> 00:16:47.410 align:start position:0% it's a problem-solving mindset and I 00:16:47.410 --> 00:16:49.470 align:start position:0% it's a problem-solving mindset and I think<00:16:47.649> we<00:16:47.770> need<00:16:47.890> designers<00:16:48.240> tackling<00:16:49.240> our 00:16:49.470 --> 00:16:49.480 align:start position:0% think we need designers tackling our 00:16:49.480 --> 00:16:53.069 align:start position:0% think we need designers tackling our biggest<00:16:49.660> problems<00:16:50.490> so<00:16:51.490> how<00:16:52.300> do<00:16:52.360> we<00:16:52.449> do<00:16:52.690> that<00:16:52.839> so 00:16:53.069 --> 00:16:53.079 align:start position:0% biggest problems so how do we do that so 00:16:53.079 --> 00:16:55.319 align:start position:0% biggest problems so how do we do that so I<00:16:53.199> think<00:16:53.500> we<00:16:53.709> are<00:16:53.920> our<00:16:54.640> design<00:16:54.970> teams<00:16:55.149> are 00:16:55.319 --> 00:16:55.329 align:start position:0% I think we are our design teams are 00:16:55.329 --> 00:16:56.880 align:start position:0% I think we are our design teams are tackling<00:16:55.839> a<00:16:55.959> lot<00:16:56.110> of<00:16:56.199> these<00:16:56.290> problems<00:16:56.529> are 00:16:56.880 --> 00:16:56.890 align:start position:0% tackling a lot of these problems are 00:16:56.890 --> 00:16:59.819 align:start position:0% tackling a lot of these problems are tackling<00:16:57.220> like<00:16:57.459> thinking<00:16:58.329> about<00:16:58.420> users<00:16:59.110> first 00:16:59.819 --> 00:16:59.829 align:start position:0% tackling like thinking about users first 00:16:59.829 --> 00:17:01.380 align:start position:0% tackling like thinking about users first and<00:17:00.130> thinking<00:17:00.399> about<00:17:00.490> how<00:17:00.730> blotching<00:17:01.120> affects 00:17:01.380 --> 00:17:01.390 align:start position:0% and thinking about how blotching affects 00:17:01.390 --> 00:17:03.360 align:start position:0% and thinking about how blotching affects their<00:17:01.569> lives<00:17:01.720> and<00:17:02.020> say<00:17:02.140> as<00:17:02.680> opposed<00:17:03.040> to<00:17:03.130> just 00:17:03.360 --> 00:17:03.370 align:start position:0% their lives and say as opposed to just 00:17:03.370 --> 00:17:04.919 align:start position:0% their lives and say as opposed to just the<00:17:03.520> technology<00:17:04.000> we<00:17:04.179> need<00:17:04.300> the<00:17:04.510> cig<00:17:04.689> knowledge 00:17:04.919 --> 00:17:04.929 align:start position:0% the technology we need the cig knowledge 00:17:04.929 --> 00:17:07.730 align:start position:0% the technology we need the cig knowledge to<00:17:05.079> be<00:17:05.169> used<00:17:05.350> by<00:17:05.470> humans<00:17:05.890> and<00:17:06.069> I<00:17:06.910> think<00:17:07.209> that 00:17:07.730 --> 00:17:07.740 align:start position:0% to be used by humans and I think that 00:17:07.740 --> 00:17:09.780 align:start position:0% to be used by humans and I think that designers<00:17:08.740> bring<00:17:08.980> that<00:17:09.100> into<00:17:09.309> the<00:17:09.429> space<00:17:09.610> to 00:17:09.780 --> 00:17:09.790 align:start position:0% designers bring that into the space to 00:17:09.790 --> 00:17:11.579 align:start position:0% designers bring that into the space to hear<00:17:09.910> about<00:17:10.089> people<00:17:10.569> first<00:17:10.750> yeah<00:17:11.290> so<00:17:11.439> I<00:17:11.470> think 00:17:11.579 --> 00:17:11.589 align:start position:0% hear about people first yeah so I think 00:17:11.589 --> 00:17:13.620 align:start position:0% hear about people first yeah so I think like<00:17:11.890> you<00:17:12.250> touch<00:17:12.490> on<00:17:12.699> like<00:17:12.910> empathy<00:17:13.209> and 00:17:13.620 --> 00:17:13.630 align:start position:0% like you touch on like empathy and 00:17:13.630 --> 00:17:15.870 align:start position:0% like you touch on like empathy and taking<00:17:14.350> it<00:17:14.439> from<00:17:14.530> the<00:17:14.740> users<00:17:15.069> perspective<00:17:15.339> so 00:17:15.870 --> 00:17:15.880 align:start position:0% taking it from the users perspective so 00:17:15.880 --> 00:17:18.600 align:start position:0% taking it from the users perspective so how<00:17:16.449> can<00:17:16.510> non-designers<00:17:17.470> kind<00:17:18.010> of<00:17:18.100> facilitate 00:17:18.600 --> 00:17:18.610 align:start position:0% how can non-designers kind of facilitate 00:17:18.610 --> 00:17:21.090 align:start position:0% how can non-designers kind of facilitate that<00:17:18.910> too<00:17:19.209> because<00:17:19.689> I<00:17:19.929> think<00:17:20.350> that's<00:17:20.740> a<00:17:20.829> key 00:17:21.090 --> 00:17:21.100 align:start position:0% that too because I think that's a key 00:17:21.100 --> 00:17:23.840 align:start position:0% that too because I think that's a key skill<00:17:21.880> set<00:17:22.179> that<00:17:22.360> anyone<00:17:22.660> can<00:17:22.780> kind<00:17:23.050> of<00:17:23.110> a 00:17:23.840 --> 00:17:23.850 align:start position:0% skill set that anyone can kind of a 00:17:23.850 --> 00:17:27.569 align:start position:0% skill set that anyone can kind of a balloon<00:17:25.199> at<00:17:26.199> the<00:17:26.230> room<00:17:26.439> to<00:17:27.040> kind<00:17:27.189> of<00:17:27.250> enable 00:17:27.569 --> 00:17:27.579 align:start position:0% balloon at the room to kind of enable 00:17:27.579 --> 00:17:29.010 align:start position:0% balloon at the room to kind of enable that<00:17:27.699> process<00:17:28.120> something<00:17:28.390> they<00:17:28.569> should<00:17:28.929> be 00:17:29.010 --> 00:17:29.020 align:start position:0% that process something they should be 00:17:29.020 --> 00:17:32.490 align:start position:0% that process something they should be looking<00:17:29.260> at<00:17:29.410> some<00:17:29.710> readings<00:17:31.320> yeah<00:17:32.320> I<00:17:32.350> think 00:17:32.490 --> 00:17:32.500 align:start position:0% looking at some readings yeah I think 00:17:32.500 --> 00:17:36.180 align:start position:0% looking at some readings yeah I think like<00:17:32.800> look<00:17:33.190> at<00:17:33.309> design<00:17:33.610> look<00:17:33.850> at<00:17:34.030> I<00:17:34.659> mean<00:17:35.190> from 00:17:36.180 --> 00:17:36.190 align:start position:0% like look at design look at I mean from 00:17:36.190 --> 00:17:38.430 align:start position:0% like look at design look at I mean from a<00:17:36.250> designer's<00:17:37.210> point<00:17:37.419> of<00:17:37.510> view<00:17:37.659> like<00:17:37.870> let's 00:17:38.430 --> 00:17:38.440 align:start position:0% a designer's point of view like let's 00:17:38.440 --> 00:17:39.900 align:start position:0% a designer's point of view like let's think<00:17:38.620> about<00:17:38.770> the<00:17:39.040> users<00:17:39.309> first<00:17:39.520> listing 00:17:39.900 --> 00:17:39.910 align:start position:0% think about the users first listing 00:17:39.910 --> 00:17:41.190 align:start position:0% think about the users first listing about<00:17:40.060> their<00:17:40.180> lives<00:17:40.360> let's<00:17:40.600> think<00:17:40.690> about<00:17:40.840> our 00:17:41.190 --> 00:17:41.200 align:start position:0% about their lives let's think about our 00:17:41.200 --> 00:17:43.680 align:start position:0% about their lives let's think about our grandpa's<00:17:41.800> and<00:17:42.160> our<00:17:42.640> nieces<00:17:42.940> and<00:17:43.270> our<00:17:43.360> sisters 00:17:43.680 --> 00:17:43.690 align:start position:0% grandpa's and our nieces and our sisters 00:17:43.690 --> 00:17:45.300 align:start position:0% grandpa's and our nieces and our sisters and<00:17:43.900> our<00:17:43.960> moms<00:17:44.170> and<00:17:44.410> how<00:17:44.530> blotching<00:17:45.010> is<00:17:45.130> going 00:17:45.300 --> 00:17:45.310 align:start position:0% and our moms and how blotching is going 00:17:45.310 --> 00:17:47.970 align:start position:0% and our moms and how blotching is going to<00:17:45.430> have<00:17:45.580> like<00:17:45.880> help<00:17:46.120> their<00:17:46.270> lives<00:17:46.770> we<00:17:47.770> need 00:17:47.970 --> 00:17:47.980 align:start position:0% to have like help their lives we need 00:17:47.980 --> 00:17:49.770 align:start position:0% to have like help their lives we need this<00:17:48.130> to<00:17:48.280> be<00:17:48.310> usable<00:17:48.760> by<00:17:48.970> everyone<00:17:49.300> so<00:17:49.330> let's 00:17:49.770 --> 00:17:49.780 align:start position:0% this to be usable by everyone so let's 00:17:49.780 --> 00:17:51.360 align:start position:0% this to be usable by everyone so let's let's<00:17:50.170> start<00:17:50.230> there<00:17:50.560> we<00:17:50.680> need<00:17:50.830> we<00:17:51.130> need<00:17:51.160> to 00:17:51.360 --> 00:17:51.370 align:start position:0% let's start there we need we need to 00:17:51.370 --> 00:17:53.550 align:start position:0% let's start there we need we need to like<00:17:51.580> think<00:17:51.940> about<00:17:52.150> the<00:17:52.780> end-user<00:17:53.080> and<00:17:53.440> what 00:17:53.550 --> 00:17:53.560 align:start position:0% like think about the end-user and what 00:17:53.560 --> 00:17:55.050 align:start position:0% like think about the end-user and what does<00:17:53.650> the<00:17:53.740> space<00:17:53.950> look<00:17:54.130> like<00:17:54.310> in<00:17:54.460> ten<00:17:54.610> years<00:17:54.850> I 00:17:55.050 --> 00:17:55.060 align:start position:0% does the space look like in ten years I 00:17:55.060 --> 00:17:56.700 align:start position:0% does the space look like in ten years I think<00:17:55.180> you<00:17:55.630> also<00:17:55.780> have<00:17:55.990> to<00:17:56.080> be<00:17:56.170> mindful<00:17:56.380> of<00:17:56.650> not 00:17:56.700 --> 00:17:56.710 align:start position:0% think you also have to be mindful of not 00:17:56.710 --> 00:17:58.290 align:start position:0% think you also have to be mindful of not marginalizing<00:17:57.610> the<00:17:57.760> people<00:17:58.060> that<00:17:58.210> were 00:17:58.290 --> 00:17:58.300 align:start position:0% marginalizing the people that were 00:17:58.300 --> 00:18:00.480 align:start position:0% marginalizing the people that were building<00:17:58.600> a<00:17:58.630> technology<00:17:58.780> for<00:17:59.320> so<00:17:59.560> we're 00:18:00.480 --> 00:18:00.490 align:start position:0% building a technology for so we're 00:18:00.490 --> 00:18:03.900 align:start position:0% building a technology for so we're building<00:18:00.670> this<00:18:01.150> new<00:18:01.630> paradigm<00:18:02.020> of<00:18:02.910> financial 00:18:03.900 --> 00:18:03.910 align:start position:0% building this new paradigm of financial 00:18:03.910 --> 00:18:06.270 align:start position:0% building this new paradigm of financial ecosystem<00:18:04.120> are<00:18:04.720> we<00:18:04.870> marginalizing<00:18:05.710> maybe 00:18:06.270 --> 00:18:06.280 align:start position:0% ecosystem are we marginalizing maybe 00:18:06.280 --> 00:18:07.920 align:start position:0% ecosystem are we marginalizing maybe four<00:18:06.730> billion<00:18:06.940> people<00:18:07.240> while<00:18:07.660> we're<00:18:07.840> doing 00:18:07.920 --> 00:18:07.930 align:start position:0% four billion people while we're doing 00:18:07.930 --> 00:18:09.780 align:start position:0% four billion people while we're doing this<00:18:08.170> so<00:18:08.440> maybe<00:18:08.890> having<00:18:09.280> those<00:18:09.520> conversations 00:18:09.780 --> 00:18:09.790 align:start position:0% this so maybe having those conversations 00:18:09.790 --> 00:18:11.870 align:start position:0% this so maybe having those conversations while<00:18:10.420> developing<00:18:10.930> these<00:18:11.110> protocols<00:18:11.560> as<00:18:11.710> well 00:18:11.870 --> 00:18:11.880 align:start position:0% while developing these protocols as well 00:18:11.880 --> 00:18:15.990 align:start position:0% while developing these protocols as well so<00:18:12.880> maybe<00:18:13.750> you<00:18:13.960> could<00:18:14.280> give<00:18:15.280> a<00:18:15.310> viewpoint<00:18:15.820> on 00:18:15.990 --> 00:18:16.000 align:start position:0% so maybe you could give a viewpoint on 00:18:16.000 --> 00:18:18.030 align:start position:0% so maybe you could give a viewpoint on do<00:18:16.150> you<00:18:16.240> guys<00:18:16.420> think<00:18:16.690> we're<00:18:16.840> at<00:18:16.960> like<00:18:17.170> the 00:18:18.030 --> 00:18:18.040 align:start position:0% do you guys think we're at like the 00:18:18.040 --> 00:18:21.750 align:start position:0% do you guys think we're at like the beginning<00:18:18.790> of<00:18:18.880> the<00:18:19.000> web<00:18:19.180> again<00:18:19.420> or<00:18:19.740> yeah<00:18:20.740> so<00:18:21.070> we 00:18:21.750 --> 00:18:21.760 align:start position:0% beginning of the web again or yeah so we 00:18:21.760 --> 00:18:23.940 align:start position:0% beginning of the web again or yeah so we are<00:18:21.910> starting<00:18:22.360> a<00:18:22.450> new<00:18:22.480> adventure<00:18:23.140> and<00:18:23.770> it 00:18:23.940 --> 00:18:23.950 align:start position:0% are starting a new adventure and it 00:18:23.950 --> 00:18:26.520 align:start position:0% are starting a new adventure and it feels<00:18:24.250> kind<00:18:24.640> of<00:18:25.000> stepping<00:18:25.630> back<00:18:25.660> there<00:18:26.380> are 00:18:26.520 --> 00:18:26.530 align:start position:0% feels kind of stepping back there are 00:18:26.530 --> 00:18:30.420 align:start position:0% feels kind of stepping back there are some<00:18:27.540> similar<00:18:28.540> things<00:18:28.840> on<00:18:29.080> some<00:18:29.320> new<00:18:29.890> things<00:18:30.250> I 00:18:30.420 --> 00:18:30.430 align:start position:0% some similar things on some new things I 00:18:30.430 --> 00:18:33.720 align:start position:0% some similar things on some new things I think<00:18:30.720> we<00:18:31.720> show<00:18:31.960> the<00:18:32.320> slide<00:18:32.620> of<00:18:32.950> the<00:18:33.250> early 00:18:33.720 --> 00:18:33.730 align:start position:0% think we show the slide of the early 00:18:33.730 --> 00:18:38.460 align:start position:0% think we show the slide of the early Geocities<00:18:35.430> super<00:18:36.430> ugly<00:18:36.660> problems<00:18:37.660> okay<00:18:37.990> that 00:18:38.460 --> 00:18:38.470 align:start position:0% Geocities super ugly problems okay that 00:18:38.470 --> 00:18:41.370 align:start position:0% Geocities super ugly problems okay that was<00:18:38.650> because<00:18:39.010> people<00:18:39.090> the<00:18:40.090> the<00:18:40.120> new<00:18:40.780> creators 00:18:41.370 --> 00:18:41.380 align:start position:0% was because people the the new creators 00:18:41.380 --> 00:18:43.980 align:start position:0% was because people the the new creators did<00:18:41.740> not<00:18:42.010> know<00:18:42.400> about<00:18:42.850> kind<00:18:43.270> of<00:18:43.360> the<00:18:43.450> standards 00:18:43.980 --> 00:18:43.990 align:start position:0% did not know about kind of the standards 00:18:43.990 --> 00:18:47.010 align:start position:0% did not know about kind of the standards to<00:18:44.620> to<00:18:45.430> communicate<00:18:45.700> and<00:18:46.180> to<00:18:46.270> tell<00:18:46.480> on<00:18:46.720> the<00:18:46.840> web 00:18:47.010 --> 00:18:47.020 align:start position:0% to to communicate and to tell on the web 00:18:47.020 --> 00:18:49.170 align:start position:0% to to communicate and to tell on the web and<00:18:47.200> I've<00:18:47.560> been<00:18:47.890> teaching<00:18:48.180> usability 00:18:49.170 --> 00:18:49.180 align:start position:0% and I've been teaching usability 00:18:49.180 --> 00:18:51.750 align:start position:0% and I've been teaching usability engineering<00:18:49.300> Jakob<00:18:50.140> Nielsen<00:18:50.640> engineers<00:18:51.640> I 00:18:51.750 --> 00:18:51.760 align:start position:0% engineering Jakob Nielsen engineers I 00:18:51.760 --> 00:18:54.300 align:start position:0% engineering Jakob Nielsen engineers I remember<00:18:52.210> that<00:18:52.360> and<00:18:52.570> today<00:18:53.440> it<00:18:53.560> feels<00:18:53.770> similar 00:18:54.300 --> 00:18:54.310 align:start position:0% remember that and today it feels similar 00:18:54.310 --> 00:18:56.010 align:start position:0% remember that and today it feels similar in<00:18:54.430> the<00:18:54.520> sense<00:18:54.730> that<00:18:54.790> we<00:18:55.030> don't<00:18:55.390> know<00:18:55.690> the 00:18:56.010 --> 00:18:56.020 align:start position:0% in the sense that we don't know the 00:18:56.020 --> 00:18:58.020 align:start position:0% in the sense that we don't know the standards<00:18:56.590> yet<00:18:56.890> we<00:18:57.070> are<00:18:57.190> still<00:18:57.430> looking<00:18:57.640> for 00:18:58.020 --> 00:18:58.030 align:start position:0% standards yet we are still looking for 00:18:58.030 --> 00:18:58.380 align:start position:0% standards yet we are still looking for them 00:18:58.380 --> 00:18:58.390 align:start position:0% them 00:18:58.390 --> 00:19:00.300 align:start position:0% them but<00:18:58.810> there<00:18:58.990> is<00:18:59.080> a<00:18:59.110> very<00:18:59.500> important<00:19:00.100> difference 00:19:00.300 --> 00:19:00.310 align:start position:0% but there is a very important difference 00:19:00.310 --> 00:19:03.510 align:start position:0% but there is a very important difference from<00:19:00.850> the<00:19:01.030> early<00:19:01.300> stages<00:19:01.570> of<00:19:01.780> the<00:19:02.020> of<00:19:02.410> the<00:19:02.830> web 00:19:03.510 --> 00:19:03.520 align:start position:0% from the early stages of the of the web 00:19:03.520 --> 00:19:05.220 align:start position:0% from the early stages of the of the web which<00:19:03.970> is<00:19:04.000> at<00:19:04.420> the<00:19:04.510> beginning<00:19:04.630> of<00:19:04.960> the<00:19:05.080> web 00:19:05.220 --> 00:19:05.230 align:start position:0% which is at the beginning of the web 00:19:05.230 --> 00:19:07.950 align:start position:0% which is at the beginning of the web everybody<00:19:06.070> knew<00:19:06.370> what<00:19:06.760> it<00:19:06.910> was<00:19:07.030> for<00:19:07.420> and<00:19:07.780> they 00:19:07.950 --> 00:19:07.960 align:start position:0% everybody knew what it was for and they 00:19:07.960 --> 00:19:10.740 align:start position:0% everybody knew what it was for and they wanted<00:19:08.560> it<00:19:08.710> everybody<00:19:09.430> wanted<00:19:09.880> to<00:19:09.910> tap<00:19:10.360> on<00:19:10.570> to 00:19:10.740 --> 00:19:10.750 align:start position:0% wanted it everybody wanted to tap on to 00:19:10.750 --> 00:19:13.830 align:start position:0% wanted it everybody wanted to tap on to this<00:19:10.930> global<00:19:11.700> connected<00:19:12.700> a<00:19:12.910> mindset<00:19:13.660> of 00:19:13.830 --> 00:19:13.840 align:start position:0% this global connected a mindset of 00:19:13.840 --> 00:19:17.190 align:start position:0% this global connected a mindset of culture<00:19:14.620> commerce<00:19:15.130> etc<00:19:15.280> today<00:19:15.850> instead<00:19:16.480> users 00:19:17.190 --> 00:19:17.200 align:start position:0% culture commerce etc today instead users 00:19:17.200 --> 00:19:20.610 align:start position:0% culture commerce etc today instead users ask<00:19:17.530> why<00:19:18.340> do<00:19:18.400> I<00:19:18.610> care<00:19:18.970> so<00:19:19.240> we<00:19:19.960> have<00:19:20.200> a 00:19:20.610 --> 00:19:20.620 align:start position:0% ask why do I care so we have a 00:19:20.620 --> 00:19:24.030 align:start position:0% ask why do I care so we have a difference<00:19:21.570> today<00:19:22.570> that<00:19:23.050> we<00:19:23.170> need<00:19:23.350> we<00:19:23.770> need<00:19:23.800> to 00:19:24.030 --> 00:19:24.040 align:start position:0% difference today that we need we need to 00:19:24.040 --> 00:19:26.340 align:start position:0% difference today that we need we need to solve<00:19:24.220> this<00:19:24.400> centralization<00:19:24.820> is<00:19:25.480> a<00:19:25.660> cultural 00:19:26.340 --> 00:19:26.350 align:start position:0% solve this centralization is a cultural 00:19:26.350 --> 00:19:29.070 align:start position:0% solve this centralization is a cultural movement<00:19:26.860> and<00:19:27.070> as<00:19:27.520> designers<00:19:28.180> we<00:19:28.210> need<00:19:28.510> to<00:19:28.660> and 00:19:29.070 --> 00:19:29.080 align:start position:0% movement and as designers we need to and 00:19:29.080 --> 00:19:30.810 align:start position:0% movement and as designers we need to and developers<00:19:29.620> also<00:19:29.920> in<00:19:30.010> the<00:19:30.100> space<00:19:30.340> we<00:19:30.550> need<00:19:30.580> to 00:19:30.810 --> 00:19:30.820 align:start position:0% developers also in the space we need to 00:19:30.820 --> 00:19:32.990 align:start position:0% developers also in the space we need to make<00:19:30.970> a<00:19:31.000> concerted<00:19:31.450> effort<00:19:31.840> to<00:19:32.290> bring 00:19:32.990 --> 00:19:33.000 align:start position:0% make a concerted effort to bring 00:19:33.000 --> 00:19:38.130 align:start position:0% make a concerted effort to bring societies<00:19:34.000> to<00:19:34.360> this<00:19:34.630> new<00:19:35.320> new<00:19:35.740> idea<00:19:37.110> yeah<00:19:38.110> I 00:19:38.130 --> 00:19:38.140 align:start position:0% societies to this new new idea yeah I 00:19:38.140 --> 00:19:41.130 align:start position:0% societies to this new new idea yeah I think<00:19:38.350> in<00:19:39.100> terms<00:19:39.340> of<00:19:39.490> being<00:19:39.700> back<00:19:40.000> being<00:19:40.930> back 00:19:41.130 --> 00:19:41.140 align:start position:0% think in terms of being back being back 00:19:41.140 --> 00:19:43.320 align:start position:0% think in terms of being back being back in<00:19:41.290> the<00:19:41.410> like<00:19:41.590> web<00:19:41.800> 1.0<00:19:42.310> world<00:19:42.520> I<00:19:42.790> think<00:19:42.910> in 00:19:43.320 --> 00:19:43.330 align:start position:0% in the like web 1.0 world I think in 00:19:43.330 --> 00:19:44.700 align:start position:0% in the like web 1.0 world I think in terms<00:19:43.510> of<00:19:43.660> design<00:19:43.960> design<00:19:44.260> and<00:19:44.440> you<00:19:44.560> I<00:19:44.590> don't 00:19:44.700 --> 00:19:44.710 align:start position:0% terms of design design and you I don't 00:19:44.710 --> 00:19:46.410 align:start position:0% terms of design design and you I don't think<00:19:45.010> a<00:19:45.190> lot<00:19:45.310> has<00:19:45.370> changed<00:19:45.520> we<00:19:45.970> do<00:19:46.090> have<00:19:46.240> new 00:19:46.410 --> 00:19:46.420 align:start position:0% think a lot has changed we do have new 00:19:46.420 --> 00:19:48.780 align:start position:0% think a lot has changed we do have new paradigms<00:19:46.870> and<00:19:47.080> new<00:19:47.200> UX<00:19:47.650> workflows<00:19:48.430> and<00:19:48.700> you 00:19:48.780 --> 00:19:48.790 align:start position:0% paradigms and new UX workflows and you 00:19:48.790 --> 00:19:50.670 align:start position:0% paradigms and new UX workflows and you problems<00:19:49.180> that<00:19:49.270> we<00:19:49.330> have<00:19:49.420> to<00:19:49.510> tackle<00:19:49.680> however 00:19:50.670 --> 00:19:50.680 align:start position:0% problems that we have to tackle however 00:19:50.680 --> 00:19:53.040 align:start position:0% problems that we have to tackle however I<00:19:51.130> think<00:19:51.430> one<00:19:51.790> of<00:19:51.820> the<00:19:51.970> biggest<00:19:52.270> things<00:19:52.510> aside 00:19:53.040 --> 00:19:53.050 align:start position:0% I think one of the biggest things aside 00:19:53.050 --> 00:19:53.820 align:start position:0% I think one of the biggest things aside from 00:19:53.820 --> 00:19:53.830 align:start position:0% from 00:19:53.830 --> 00:19:56.370 align:start position:0% from UI<00:19:53.950> and<00:19:54.279> UX<00:19:54.399> and<00:19:54.820> visual<00:19:55.120> things<00:19:55.390> it's<00:19:55.690> these 00:19:56.370 --> 00:19:56.380 align:start position:0% UI and UX and visual things it's these 00:19:56.380 --> 00:19:59.639 align:start position:0% UI and UX and visual things it's these new<00:19:57.510> let's<00:19:58.510> say<00:19:58.630> like<00:19:58.809> ideas<00:19:59.289> that<00:19:59.470> we<00:19:59.529> have 00:19:59.639 --> 00:19:59.649 align:start position:0% new let's say like ideas that we have 00:19:59.649 --> 00:20:01.139 align:start position:0% new let's say like ideas that we have instill<00:19:59.980> into<00:20:00.159> our<00:20:00.250> users<00:20:00.519> the<00:20:00.610> idea<00:20:00.909> of<00:20:01.000> being 00:20:01.139 --> 00:20:01.149 align:start position:0% instill into our users the idea of being 00:20:01.149 --> 00:20:03.360 align:start position:0% instill into our users the idea of being responsible<00:20:01.690> for<00:20:02.019> your<00:20:02.620> Kezia<00:20:03.100> do<00:20:03.190> you<00:20:03.279> have 00:20:03.360 --> 00:20:03.370 align:start position:0% responsible for your Kezia do you have 00:20:03.370 --> 00:20:04.860 align:start position:0% responsible for your Kezia do you have like<00:20:03.490> owning<00:20:03.700> your<00:20:03.880> data<00:20:04.120> the<00:20:04.330> idea<00:20:04.539> of<00:20:04.630> being 00:20:04.860 --> 00:20:04.870 align:start position:0% like owning your data the idea of being 00:20:04.870 --> 00:20:06.210 align:start position:0% like owning your data the idea of being like<00:20:05.019> the<00:20:05.140> only<00:20:05.350> person<00:20:05.649> in<00:20:05.740> control<00:20:06.070> and 00:20:06.210 --> 00:20:06.220 align:start position:0% like the only person in control and 00:20:06.220 --> 00:20:08.009 align:start position:0% like the only person in control and nobody<00:20:06.490> else<00:20:06.669> can<00:20:06.820> help<00:20:06.909> you<00:20:07.149> those<00:20:07.720> things 00:20:08.009 --> 00:20:08.019 align:start position:0% nobody else can help you those things 00:20:08.019 --> 00:20:10.230 align:start position:0% nobody else can help you those things are<00:20:08.200> 100%<00:20:08.769> new<00:20:09.100> to<00:20:09.250> our<00:20:09.370> space<00:20:09.610> and<00:20:09.880> we<00:20:09.940> need<00:20:10.029> to 00:20:10.230 --> 00:20:10.240 align:start position:0% are 100% new to our space and we need to 00:20:10.240 --> 00:20:11.940 align:start position:0% are 100% new to our space and we need to do<00:20:10.360> a<00:20:10.390> really<00:20:10.779> really<00:20:10.809> good<00:20:11.200> job<00:20:11.380> of<00:20:11.620> instill 00:20:11.940 --> 00:20:11.950 align:start position:0% do a really really good job of instill 00:20:11.950 --> 00:20:13.380 align:start position:0% do a really really good job of instill in<00:20:12.100> our<00:20:12.130> users<00:20:12.519> if<00:20:12.730> we're<00:20:13.120> going<00:20:13.210> to<00:20:13.269> move 00:20:13.380 --> 00:20:13.390 align:start position:0% in our users if we're going to move 00:20:13.390 --> 00:20:15.899 align:start position:0% in our users if we're going to move forward<00:20:13.600> just<00:20:13.960> to<00:20:14.830> put<00:20:15.220> a<00:20:15.250> counterweight<00:20:15.610> to 00:20:15.899 --> 00:20:15.909 align:start position:0% forward just to put a counterweight to 00:20:15.909 --> 00:20:17.549 align:start position:0% forward just to put a counterweight to that<00:20:16.059> do<00:20:16.330> you<00:20:16.419> think<00:20:16.570> we<00:20:16.779> should<00:20:17.049> be<00:20:17.200> bringing 00:20:17.549 --> 00:20:17.559 align:start position:0% that do you think we should be bringing 00:20:17.559 --> 00:20:21.870 align:start position:0% that do you think we should be bringing in<00:20:18.450> existing<00:20:19.830> mental<00:20:20.830> models<00:20:21.309> from<00:20:21.460> web<00:20:21.669> tool 00:20:21.870 --> 00:20:21.880 align:start position:0% in existing mental models from web tool 00:20:21.880 --> 00:20:23.639 align:start position:0% in existing mental models from web tool even<00:20:22.570> though<00:20:22.779> we're<00:20:22.929> designing<00:20:23.320> these<00:20:23.529> new 00:20:23.639 --> 00:20:23.649 align:start position:0% even though we're designing these new 00:20:23.649 --> 00:20:25.860 align:start position:0% even though we're designing these new systems<00:20:24.039> or<00:20:24.190> do<00:20:24.640> we<00:20:24.760> have<00:20:24.940> the<00:20:25.090> opportunity<00:20:25.690> to 00:20:25.860 --> 00:20:25.870 align:start position:0% systems or do we have the opportunity to 00:20:25.870 --> 00:20:27.060 align:start position:0% systems or do we have the opportunity to kind<00:20:26.019> of<00:20:26.049> step<00:20:26.289> back<00:20:26.440> and<00:20:26.500> look<00:20:26.769> at<00:20:26.830> it<00:20:26.919> from 00:20:27.060 --> 00:20:27.070 align:start position:0% kind of step back and look at it from 00:20:27.070 --> 00:20:28.860 align:start position:0% kind of step back and look at it from first<00:20:27.340> principles<00:20:27.880> and<00:20:28.090> kind<00:20:28.600> of<00:20:28.690> try<00:20:28.840> to 00:20:28.860 --> 00:20:28.870 align:start position:0% first principles and kind of try to 00:20:28.870 --> 00:20:31.529 align:start position:0% first principles and kind of try to redesign<00:20:29.559> the<00:20:29.710> whole<00:20:29.740> thing<00:20:30.100> leading<00:20:30.549> that's 00:20:31.529 --> 00:20:31.539 align:start position:0% redesign the whole thing leading that's 00:20:31.539 --> 00:20:33.210 align:start position:0% redesign the whole thing leading that's conducive<00:20:31.960> to<00:20:32.320> what<00:20:32.590> we're<00:20:32.919> trying<00:20:33.039> to<00:20:33.159> do 00:20:33.210 --> 00:20:33.220 align:start position:0% conducive to what we're trying to do 00:20:33.220 --> 00:20:36.419 align:start position:0% conducive to what we're trying to do here<00:20:33.429> or<00:20:33.549> is<00:20:33.730> you<00:20:33.850> think<00:20:34.059> this<00:20:34.950> I<00:20:35.950> think<00:20:36.279> we<00:20:36.399> can 00:20:36.419 --> 00:20:36.429 align:start position:0% here or is you think this I think we can 00:20:36.429 --> 00:20:38.039 align:start position:0% here or is you think this I think we can we<00:20:36.789> can<00:20:36.909> definitely<00:20:37.000> build<00:20:37.360> bring<00:20:37.960> in 00:20:38.039 --> 00:20:38.049 align:start position:0% we can definitely build bring in 00:20:38.049 --> 00:20:40.529 align:start position:0% we can definitely build bring in whatever<00:20:38.230> works<00:20:38.669> we<00:20:39.669> see<00:20:39.909> right<00:20:40.269> now<00:20:40.389> we're 00:20:40.529 --> 00:20:40.539 align:start position:0% whatever works we see right now we're 00:20:40.539 --> 00:20:42.090 align:start position:0% whatever works we see right now we're like<00:20:40.659> kind<00:20:40.840> of<00:20:40.929> like<00:20:41.080> in<00:20:41.230> the<00:20:41.320> fork<00:20:41.889> in<00:20:42.010> the 00:20:42.090 --> 00:20:42.100 align:start position:0% like kind of like in the fork in the 00:20:42.100 --> 00:20:44.419 align:start position:0% like kind of like in the fork in the road<00:20:42.220> where<00:20:42.460> we<00:20:42.490> see<00:20:42.700> a<00:20:42.730> lot<00:20:42.940> of<00:20:42.970> things<00:20:43.269> we're 00:20:44.419 --> 00:20:44.429 align:start position:0% road where we see a lot of things we're 00:20:44.429 --> 00:20:46.560 align:start position:0% road where we see a lot of things we're centralizing<00:20:45.429> some<00:20:45.639> services<00:20:46.090> all<00:20:46.240> a<00:20:46.269> sudden 00:20:46.560 --> 00:20:46.570 align:start position:0% centralizing some services all a sudden 00:20:46.570 --> 00:20:49.110 align:start position:0% centralizing some services all a sudden becomes<00:20:46.899> all<00:20:47.860> of<00:20:47.980> a<00:20:48.010> sudden<00:20:48.250> like<00:20:48.460> we<00:20:48.850> can<00:20:48.970> get 00:20:49.110 --> 00:20:49.120 align:start position:0% becomes all of a sudden like we can get 00:20:49.120 --> 00:20:50.519 align:start position:0% becomes all of a sudden like we can get carried<00:20:49.389> away<00:20:49.450> and<00:20:49.720> kind<00:20:49.840> of<00:20:49.960> get<00:20:50.110> rid<00:20:50.289> of<00:20:50.320> all 00:20:50.519 --> 00:20:50.529 align:start position:0% carried away and kind of get rid of all 00:20:50.529 --> 00:20:51.600 align:start position:0% carried away and kind of get rid of all the<00:20:50.679> benefits<00:20:50.830> that<00:20:51.190> we<00:20:51.309> get<00:20:51.429> through 00:20:51.600 --> 00:20:51.610 align:start position:0% the benefits that we get through 00:20:51.610 --> 00:20:53.879 align:start position:0% the benefits that we get through blockchain<00:20:51.970> like<00:20:52.210> see<00:20:53.080> phrase<00:20:53.289> our<00:20:53.440> hearts<00:20:53.740> so 00:20:53.879 --> 00:20:53.889 align:start position:0% blockchain like see phrase our hearts so 00:20:53.889 --> 00:20:55.350 align:start position:0% blockchain like see phrase our hearts so let's<00:20:54.070> just<00:20:54.279> like<00:20:54.399> use<00:20:54.580> passwords<00:20:55.029> and<00:20:55.240> then 00:20:55.350 --> 00:20:55.360 align:start position:0% let's just like use passwords and then 00:20:55.360 --> 00:20:57.149 align:start position:0% let's just like use passwords and then we<00:20:55.570> we<00:20:55.929> lose<00:20:56.139> like<00:20:56.380> the<00:20:56.500> user<00:20:56.679> owning<00:20:57.039> their 00:20:57.149 --> 00:20:57.159 align:start position:0% we we lose like the user owning their 00:20:57.159 --> 00:20:59.100 align:start position:0% we we lose like the user owning their data<00:20:57.340> and<00:20:57.580> their<00:20:57.669> user<00:20:57.820> being<00:20:58.059> responsible<00:20:58.539> so 00:20:59.100 --> 00:20:59.110 align:start position:0% data and their user being responsible so 00:20:59.110 --> 00:21:00.269 align:start position:0% data and their user being responsible so I<00:20:59.139> think<00:20:59.230> we<00:20:59.409> just<00:20:59.500> need<00:20:59.590> to<00:20:59.679> be<00:20:59.830> mindful<00:21:00.039> of 00:21:00.269 --> 00:21:00.279 align:start position:0% I think we just need to be mindful of 00:21:00.279 --> 00:21:02.759 align:start position:0% I think we just need to be mindful of that<00:21:00.340> and<00:21:01.200> yeah<00:21:02.200> we<00:21:02.350> have<00:21:02.380> like<00:21:02.679> an 00:21:02.759 --> 00:21:02.769 align:start position:0% that and yeah we have like an 00:21:02.769 --> 00:21:05.340 align:start position:0% that and yeah we have like an opportunity<00:21:03.220> right<00:21:03.340> now<00:21:03.399> to<00:21:03.809> to<00:21:04.809> set<00:21:05.019> the<00:21:05.139> path 00:21:05.340 --> 00:21:05.350 align:start position:0% opportunity right now to to set the path 00:21:05.350 --> 00:21:06.990 align:start position:0% opportunity right now to to set the path and<00:21:05.529> we<00:21:05.620> need<00:21:05.769> to<00:21:05.889> like<00:21:06.070> really<00:21:06.850> make 00:21:06.990 --> 00:21:07.000 align:start position:0% and we need to like really make 00:21:07.000 --> 00:21:08.519 align:start position:0% and we need to like really make blockchain<00:21:07.389> useful<00:21:07.720> and<00:21:07.870> remember<00:21:08.200> like<00:21:08.350> what 00:21:08.519 --> 00:21:08.529 align:start position:0% blockchain useful and remember like what 00:21:08.529 --> 00:21:10.019 align:start position:0% blockchain useful and remember like what it's<00:21:08.649> here<00:21:08.799> for<00:21:09.010> and<00:21:09.220> like<00:21:09.399> what<00:21:09.580> the<00:21:09.700> value<00:21:10.000> is 00:21:10.019 --> 00:21:10.029 align:start position:0% it's here for and like what the value is 00:21:10.029 --> 00:21:12.500 align:start position:0% it's here for and like what the value is and<00:21:10.419> keep<00:21:10.600> that<00:21:10.809> and<00:21:11.080> do<00:21:11.409> our<00:21:11.559> best<00:21:11.590> job<00:21:11.980> to 00:21:12.500 --> 00:21:12.510 align:start position:0% and keep that and do our best job to 00:21:12.510 --> 00:21:15.690 align:start position:0% and keep that and do our best job to keep<00:21:13.510> that<00:21:13.779> and<00:21:14.019> not<00:21:14.169> not<00:21:14.559> not<00:21:15.130> relinquish<00:21:15.549> it 00:21:15.690 --> 00:21:15.700 align:start position:0% keep that and not not not relinquish it 00:21:15.700 --> 00:21:18.210 align:start position:0% keep that and not not not relinquish it and<00:21:15.909> you<00:21:16.269> know<00:21:16.620> by<00:21:17.620> just<00:21:17.830> making<00:21:18.070> things 00:21:18.210 --> 00:21:18.220 align:start position:0% and you know by just making things 00:21:18.220 --> 00:21:20.340 align:start position:0% and you know by just making things easier<00:21:18.820> for<00:21:19.000> users<00:21:19.149> like<00:21:19.480> we<00:21:19.600> can<00:21:19.779> we<00:21:20.049> can<00:21:20.200> try 00:21:20.340 --> 00:21:20.350 align:start position:0% easier for users like we can we can try 00:21:20.350 --> 00:21:21.960 align:start position:0% easier for users like we can we can try harder<00:21:20.590> and<00:21:20.710> we<00:21:20.769> can<00:21:20.919> make<00:21:21.070> people<00:21:21.429> learn<00:21:21.760> this 00:21:21.960 --> 00:21:21.970 align:start position:0% harder and we can make people learn this 00:21:21.970 --> 00:21:27.120 align:start position:0% harder and we can make people learn this stuff<00:21:22.860> I<00:21:24.929> think<00:21:25.929> we've<00:21:26.200> had<00:21:26.500> these<00:21:26.679> internal 00:21:27.120 --> 00:21:27.130 align:start position:0% stuff I think we've had these internal 00:21:27.130 --> 00:21:28.590 align:start position:0% stuff I think we've had these internal conversations<00:21:27.730> all<00:21:27.850> the<00:21:27.880> time<00:21:28.029> so<00:21:28.330> maybe<00:21:28.450> we 00:21:28.590 --> 00:21:28.600 align:start position:0% conversations all the time so maybe we 00:21:28.600 --> 00:21:30.149 align:start position:0% conversations all the time so maybe we can<00:21:28.750> give<00:21:28.870> an<00:21:28.960> opportunity<00:21:29.169> to<00:21:29.529> the<00:21:29.830> audience 00:21:30.149 --> 00:21:30.159 align:start position:0% can give an opportunity to the audience 00:21:30.159 --> 00:21:31.110 align:start position:0% can give an opportunity to the audience if<00:21:30.279> they<00:21:30.309> have<00:21:30.460> any<00:21:30.580> questions 00:21:31.110 --> 00:21:31.120 align:start position:0% if they have any questions 00:21:31.120 --> 00:21:35.370 align:start position:0% if they have any questions I<00:21:31.330> see<00:21:31.690> her<00:21:31.809> hand<00:21:32.110> back<00:21:32.320> there<00:21:32.769> or<00:21:33.779> no<00:21:34.779> okay 00:21:35.370 --> 00:21:35.380 align:start position:0% I see her hand back there or no okay 00:21:35.380 --> 00:21:45.779 align:start position:0% I see her hand back there or no okay back<00:21:35.679> there<00:21:43.799> so<00:21:44.799> to<00:21:44.860> repeat<00:21:45.279> the<00:21:45.399> question 00:21:45.779 --> 00:21:45.789 align:start position:0% back there so to repeat the question 00:21:45.789 --> 00:21:49.970 align:start position:0% back there so to repeat the question what<00:21:46.539> is<00:21:46.720> the<00:21:47.649> thoughts<00:21:47.980> between<00:21:48.639> explicit 00:21:49.970 --> 00:21:49.980 align:start position:0% what is the thoughts between explicit 00:21:49.980 --> 00:21:53.490 align:start position:0% what is the thoughts between explicit education<00:21:50.980> rather<00:21:51.789> than<00:21:52.240> implicit<00:21:52.840> good 00:21:53.490 --> 00:21:53.500 align:start position:0% education rather than implicit good 00:21:53.500 --> 00:21:58.049 align:start position:0% education rather than implicit good design<00:21:53.909> yeah<00:21:54.909> we<00:21:55.149> struggle<00:21:56.110> with<00:21:56.380> that<00:21:56.909> in<00:21:57.909> our 00:21:58.049 --> 00:21:58.059 align:start position:0% design yeah we struggle with that in our 00:21:58.059 --> 00:21:59.970 align:start position:0% design yeah we struggle with that in our day<00:21:58.269> to<00:21:58.330> day<00:21:58.480> jobs<00:21:58.870> because<00:21:59.230> of<00:21:59.350> course<00:21:59.590> good 00:21:59.970 --> 00:21:59.980 align:start position:0% day to day jobs because of course good 00:21:59.980 --> 00:22:03.870 align:start position:0% day to day jobs because of course good design<00:22:00.370> should<00:22:00.669> not<00:22:01.539> need<00:22:01.899> explanations<00:22:02.880> but 00:22:03.870 --> 00:22:03.880 align:start position:0% design should not need explanations but 00:22:03.880 --> 00:22:05.940 align:start position:0% design should not need explanations but in<00:22:04.299> this<00:22:04.600> case<00:22:04.870> we<00:22:05.080> need<00:22:05.200> to<00:22:05.260> put<00:22:05.529> onto<00:22:05.710> the 00:22:05.940 --> 00:22:05.950 align:start position:0% in this case we need to put onto the 00:22:05.950 --> 00:22:07.139 align:start position:0% in this case we need to put onto the balance<00:22:06.309> that<00:22:06.520> we 00:22:07.139 --> 00:22:07.149 align:start position:0% balance that we 00:22:07.149 --> 00:22:10.469 align:start position:0% balance that we they<00:22:07.239> are<00:22:07.419> giving<00:22:07.989> new<00:22:08.549> unfamiliar<00:22:09.549> concepts 00:22:10.469 --> 00:22:10.479 align:start position:0% they are giving new unfamiliar concepts 00:22:10.479 --> 00:22:13.109 align:start position:0% they are giving new unfamiliar concepts to<00:22:10.690> the<00:22:10.899> users<00:22:11.349> and<00:22:11.559> all<00:22:11.979> at<00:22:12.249> once<00:22:12.489> it's<00:22:13.029> like 00:22:13.109 --> 00:22:13.119 align:start position:0% to the users and all at once it's like 00:22:13.119 --> 00:22:17.249 align:start position:0% to the users and all at once it's like the<00:22:13.359> firehose<00:22:13.839> so<00:22:14.169> one<00:22:15.070> good<00:22:15.429> design<00:22:15.999> way<00:22:16.929> of 00:22:17.249 --> 00:22:17.259 align:start position:0% the firehose so one good design way of 00:22:17.259 --> 00:22:21.029 align:start position:0% the firehose so one good design way of doing<00:22:17.679> this<00:22:18.009> is<00:22:18.249> to<00:22:18.759> progressively<00:22:19.719> show<00:22:20.710> and 00:22:21.029 --> 00:22:21.039 align:start position:0% doing this is to progressively show and 00:22:21.039 --> 00:22:22.919 align:start position:0% doing this is to progressively show and explain<00:22:21.399> what<00:22:21.849> these<00:22:21.999> things<00:22:22.299> are<00:22:22.539> and<00:22:22.779> what 00:22:22.919 --> 00:22:22.929 align:start position:0% explain what these things are and what 00:22:22.929 --> 00:22:25.680 align:start position:0% explain what these things are and what they<00:22:23.049> are<00:22:23.080> important<00:22:23.619> are<00:22:23.799> so<00:22:24.099> it's<00:22:25.029> a<00:22:25.239> balance 00:22:25.680 --> 00:22:25.690 align:start position:0% they are important are so it's a balance 00:22:25.690 --> 00:22:29.759 align:start position:0% they are important are so it's a balance that<00:22:25.839> we<00:22:26.019> need<00:22:26.259> to<00:22:26.379> struggle<00:22:26.859> every<00:22:27.429> day<00:22:28.769> I 00:22:29.759 --> 00:22:29.769 align:start position:0% that we need to struggle every day I 00:22:29.769 --> 00:22:31.529 align:start position:0% that we need to struggle every day I don't<00:22:30.549> think<00:22:30.700> they're<00:22:30.789> made<00:22:30.909> to<00:22:30.940> exclusive<00:22:31.450> I 00:22:31.529 --> 00:22:31.539 align:start position:0% don't think they're made to exclusive I 00:22:31.539 --> 00:22:33.839 align:start position:0% don't think they're made to exclusive I think<00:22:31.779> good<00:22:32.139> education<00:22:32.649> is<00:22:32.799> also<00:22:33.249> good<00:22:33.519> design 00:22:33.839 --> 00:22:33.849 align:start position:0% think good education is also good design 00:22:33.849 --> 00:22:35.310 align:start position:0% think good education is also good design I<00:22:33.879> think<00:22:34.029> like<00:22:34.359> on<00:22:34.570> top<00:22:34.779> of<00:22:34.929> like<00:22:35.109> making 00:22:35.310 --> 00:22:35.320 align:start position:0% I think like on top of like making 00:22:35.320 --> 00:22:37.049 align:start position:0% I think like on top of like making making<00:22:35.769> things<00:22:36.009> pretty<00:22:36.159> and<00:22:36.460> make<00:22:36.580> making 00:22:37.049 --> 00:22:37.059 align:start position:0% making things pretty and make making 00:22:37.059 --> 00:22:38.789 align:start position:0% making things pretty and make making things<00:22:37.239> easier<00:22:37.539> and<00:22:37.719> reducing<00:22:38.379> friction<00:22:38.529> we 00:22:38.789 --> 00:22:38.799 align:start position:0% things easier and reducing friction we 00:22:38.799 --> 00:22:41.039 align:start position:0% things easier and reducing friction we have<00:22:38.889> to<00:22:38.979> be<00:22:39.070> mindful<00:22:39.279> of<00:22:39.869> necessary<00:22:40.869> friction 00:22:41.039 --> 00:22:41.049 align:start position:0% have to be mindful of necessary friction 00:22:41.049 --> 00:22:44.190 align:start position:0% have to be mindful of necessary friction we<00:22:41.499> need<00:22:41.649> to<00:22:41.769> educate<00:22:42.279> we<00:22:42.849> need<00:22:42.999> to<00:22:43.210> talk<00:22:44.080> about 00:22:44.190 --> 00:22:44.200 align:start position:0% we need to educate we need to talk about 00:22:44.200 --> 00:22:45.810 align:start position:0% we need to educate we need to talk about blockchain<00:22:44.529> and<00:22:44.739> talk<00:22:45.009> about<00:22:45.219> this<00:22:45.369> stuff<00:22:45.580> and 00:22:45.810 --> 00:22:45.820 align:start position:0% blockchain and talk about this stuff and 00:22:45.820 --> 00:22:47.159 align:start position:0% blockchain and talk about this stuff and talk<00:22:45.999> to<00:22:46.119> your<00:22:46.299> moms<00:22:46.479> and<00:22:46.659> your<00:22:46.839> sisters<00:22:47.139> and 00:22:47.159 --> 00:22:47.169 align:start position:0% talk to your moms and your sisters and 00:22:47.169 --> 00:22:50.099 align:start position:0% talk to your moms and your sisters and your<00:22:47.499> nieces<00:22:47.739> about<00:22:48.099> blockchain<00:22:48.369> and<00:22:49.109> read 00:22:50.099 --> 00:22:50.109 align:start position:0% your nieces about blockchain and read 00:22:50.109 --> 00:22:51.899 align:start position:0% your nieces about blockchain and read articles<00:22:50.529> and<00:22:50.919> we<00:22:50.979> need<00:22:51.129> to<00:22:51.219> like<00:22:51.399> and<00:22:51.580> we<00:22:51.759> need 00:22:51.899 --> 00:22:51.909 align:start position:0% articles and we need to like and we need 00:22:51.909 --> 00:22:53.669 align:start position:0% articles and we need to like and we need to<00:22:51.999> instill<00:22:52.210> it<00:22:52.330> in<00:22:52.389> the<00:22:52.479> culture<00:22:52.809> we<00:22:53.349> need<00:22:53.499> to 00:22:53.669 --> 00:22:53.679 align:start position:0% to instill it in the culture we need to 00:22:53.679 --> 00:22:55.489 align:start position:0% to instill it in the culture we need to have<00:22:54.159> people<00:22:54.279> talking<00:22:54.669> about<00:22:54.759> it<00:22:55.029> we<00:22:55.149> need<00:22:55.299> to 00:22:55.489 --> 00:22:55.499 align:start position:0% have people talking about it we need to 00:22:55.499 --> 00:22:57.779 align:start position:0% have people talking about it we need to educate<00:22:56.499> people<00:22:56.830> and<00:22:57.129> why<00:22:57.219> it's<00:22:57.369> important 00:22:57.779 --> 00:22:57.789 align:start position:0% educate people and why it's important 00:22:57.789 --> 00:22:59.759 align:start position:0% educate people and why it's important and<00:22:57.849> why<00:22:58.419> all<00:22:58.659> this<00:22:58.749> friction<00:22:58.929> is<00:22:59.139> necessary 00:22:59.759 --> 00:22:59.769 align:start position:0% and why all this friction is necessary 00:22:59.769 --> 00:23:02.159 align:start position:0% and why all this friction is necessary in<00:22:59.919> order<00:23:00.039> to<00:23:00.539> build<00:23:01.539> the<00:23:01.719> future<00:23:01.839> that<00:23:02.109> we 00:23:02.159 --> 00:23:02.169 align:start position:0% in order to build the future that we 00:23:02.169 --> 00:23:03.869 align:start position:0% in order to build the future that we want<00:23:02.289> to<00:23:02.440> have<00:23:02.619> and<00:23:02.889> not<00:23:02.979> like<00:23:03.249> step<00:23:03.549> back<00:23:03.669> into 00:23:03.869 --> 00:23:03.879 align:start position:0% want to have and not like step back into 00:23:03.879 --> 00:23:04.859 align:start position:0% want to have and not like step back into web<00:23:04.149> 2.0 00:23:04.859 --> 00:23:04.869 align:start position:0% web 2.0 00:23:04.869 --> 00:23:07.349 align:start position:0% web 2.0 I<00:23:04.899> think<00:23:05.169> another<00:23:05.320> key<00:23:05.619> point<00:23:05.889> there<00:23:06.070> is<00:23:06.359> when 00:23:07.349 --> 00:23:07.359 align:start position:0% I think another key point there is when 00:23:07.359 --> 00:23:08.759 align:start position:0% I think another key point there is when we're<00:23:07.509> educating<00:23:08.019> people<00:23:08.109> we<00:23:08.379> need<00:23:08.529> to<00:23:08.619> make 00:23:08.759 --> 00:23:08.769 align:start position:0% we're educating people we need to make 00:23:08.769 --> 00:23:11.419 align:start position:0% we're educating people we need to make sure<00:23:08.799> that<00:23:09.339> there's<00:23:10.330> some<00:23:10.570> sort<00:23:10.869> of 00:23:11.419 --> 00:23:11.429 align:start position:0% sure that there's some sort of 00:23:11.429 --> 00:23:13.589 align:start position:0% sure that there's some sort of centralization<00:23:12.429> to<00:23:12.909> this<00:23:13.059> decentralized 00:23:13.589 --> 00:23:13.599 align:start position:0% centralization to this decentralized 00:23:13.599 --> 00:23:15.719 align:start position:0% centralization to this decentralized ecosystem<00:23:14.469> where<00:23:14.619> people<00:23:14.950> have<00:23:15.099> a<00:23:15.129> common 00:23:15.719 --> 00:23:15.729 align:start position:0% ecosystem where people have a common 00:23:15.729 --> 00:23:17.399 align:start position:0% ecosystem where people have a common terminology<00:23:16.330> and<00:23:16.479> a<00:23:16.539> common<00:23:17.169> set<00:23:17.289> of 00:23:17.399 --> 00:23:17.409 align:start position:0% terminology and a common set of 00:23:17.409 --> 00:23:18.599 align:start position:0% terminology and a common set of frameworks<00:23:17.619> to<00:23:17.889> kind<00:23:18.129> of<00:23:18.159> actually<00:23:18.460> wrap 00:23:18.599 --> 00:23:18.609 align:start position:0% frameworks to kind of actually wrap 00:23:18.609 --> 00:23:19.950 align:start position:0% frameworks to kind of actually wrap their<00:23:18.759> heads<00:23:18.909> around<00:23:18.999> because<00:23:19.570> if<00:23:19.690> each 00:23:19.950 --> 00:23:19.960 align:start position:0% their heads around because if each 00:23:19.960 --> 00:23:21.539 align:start position:0% their heads around because if each project<00:23:20.440> is<00:23:20.559> creating<00:23:20.889> their<00:23:21.009> own<00:23:21.039> set<00:23:21.429> of 00:23:21.539 --> 00:23:21.549 align:start position:0% project is creating their own set of 00:23:21.549 --> 00:23:23.430 align:start position:0% project is creating their own set of standards<00:23:21.909> and<00:23:22.029> education<00:23:22.570> it<00:23:23.139> gets<00:23:23.379> very 00:23:23.430 --> 00:23:23.440 align:start position:0% standards and education it gets very 00:23:23.440 --> 00:23:25.739 align:start position:0% standards and education it gets very confusing<00:23:23.710> for<00:23:24.369> users<00:23:24.639> to<00:23:24.940> bounce<00:23:25.419> from<00:23:25.570> one 00:23:25.739 --> 00:23:25.749 align:start position:0% confusing for users to bounce from one 00:23:25.749 --> 00:23:28.169 align:start position:0% confusing for users to bounce from one to<00:23:25.869> the<00:23:25.899> other<00:23:25.989> so<00:23:26.349> that's<00:23:27.099> why<00:23:27.369> having 00:23:28.169 --> 00:23:28.179 align:start position:0% to the other so that's why having 00:23:28.179 --> 00:23:29.969 align:start position:0% to the other so that's why having opportunities<00:23:28.929> for<00:23:29.139> people<00:23:29.320> to<00:23:29.469> come<00:23:29.739> in<00:23:29.889> a 00:23:29.969 --> 00:23:29.979 align:start position:0% opportunities for people to come in a 00:23:29.979 --> 00:23:31.469 align:start position:0% opportunities for people to come in a room<00:23:30.129> together<00:23:30.339> and<00:23:30.669> have<00:23:31.269> these<00:23:31.419> discussions 00:23:31.469 --> 00:23:31.479 align:start position:0% room together and have these discussions 00:23:31.479 --> 00:23:33.719 align:start position:0% room together and have these discussions is<00:23:32.080> very<00:23:32.229> imperative<00:23:32.649> at<00:23:32.979> this<00:23:33.099> point<00:23:33.309> in<00:23:33.429> in 00:23:33.719 --> 00:23:33.729 align:start position:0% is very imperative at this point in in 00:23:33.729 --> 00:23:36.479 align:start position:0% is very imperative at this point in in our<00:23:34.149> lifecycle<00:23:34.839> for<00:23:35.559> the<00:23:35.679> ecosystem<00:23:35.950> and 00:23:36.479 --> 00:23:36.489 align:start position:0% our lifecycle for the ecosystem and 00:23:36.489 --> 00:23:38.099 align:start position:0% our lifecycle for the ecosystem and hopefully<00:23:37.389> you<00:23:37.479> can<00:23:37.599> start<00:23:37.809> doing<00:23:37.960> a<00:23:37.989> better 00:23:38.099 --> 00:23:38.109 align:start position:0% hopefully you can start doing a better 00:23:38.109 --> 00:23:39.810 align:start position:0% hopefully you can start doing a better job<00:23:38.320> with<00:23:38.529> that<00:23:38.559> any<00:23:38.979> other<00:23:39.190> additional 00:23:39.810 --> 00:23:39.820 align:start position:0% job with that any other additional 00:23:39.820 --> 00:23:47.669 align:start position:0% job with that any other additional questions<00:23:39.879> you<00:23:40.389> were<00:23:40.779> here<00:23:46.200> all<00:23:47.200> right<00:23:47.440> no 00:23:47.669 --> 00:23:47.679 align:start position:0% questions you were here all right no 00:23:47.679 --> 00:23:49.379 align:start position:0% questions you were here all right no plants<00:23:47.979> as<00:23:48.039> of<00:23:48.159> yet<00:23:48.339> but<00:23:48.519> everything<00:23:48.969> is<00:23:49.089> open 00:23:49.379 --> 00:23:49.389 align:start position:0% plants as of yet but everything is open 00:23:49.389 --> 00:23:51.629 align:start position:0% plants as of yet but everything is open we<00:23:49.989> really<00:23:50.559> want<00:23:50.739> all<00:23:50.919> the<00:23:51.039> people<00:23:51.309> we<00:23:51.399> can<00:23:51.519> get 00:23:51.629 --> 00:23:51.639 align:start position:0% we really want all the people we can get 00:23:51.639 --> 00:23:54.299 align:start position:0% we really want all the people we can get in<00:23:51.700> the<00:23:51.759> community<00:23:51.909> and<00:23:52.919> if<00:23:53.919> you<00:23:53.979> reaiiy 00:23:54.299 --> 00:23:54.309 align:start position:0% in the community and if you reaiiy 00:23:54.309 --> 00:23:55.680 align:start position:0% in the community and if you reaiiy manned<00:23:54.519> the<00:23:54.580> blocking<00:23:54.879> space<00:23:55.089> is<00:23:55.239> moving<00:23:55.509> so 00:23:55.680 --> 00:23:55.690 align:start position:0% manned the blocking space is moving so 00:23:55.690 --> 00:23:57.029 align:start position:0% manned the blocking space is moving so fast<00:23:55.960> that<00:23:56.229> we<00:23:56.469> need<00:23:56.649> to<00:23:56.769> know<00:23:56.889> what 00:23:57.029 --> 00:23:57.039 align:start position:0% fast that we need to know what 00:23:57.039 --> 00:23:58.259 align:start position:0% fast that we need to know what developers<00:23:57.369> are<00:23:57.519> thinking<00:23:57.820> about<00:23:57.999> and<00:23:58.179> what 00:23:58.259 --> 00:23:58.269 align:start position:0% developers are thinking about and what 00:23:58.269 --> 00:23:59.999 align:start position:0% developers are thinking about and what they're<00:23:58.389> looking<00:23:58.509> ahead<00:23:58.779> and<00:23:59.109> start<00:23:59.649> you<00:23:59.919> know 00:23:59.999 --> 00:24:00.009 align:start position:0% they're looking ahead and start you know 00:24:00.009 --> 00:24:02.159 align:start position:0% they're looking ahead and start you know tackling<00:24:00.399> things<00:24:00.639> before<00:24:01.029> before<00:24:01.929> we<00:24:02.019> even 00:24:02.159 --> 00:24:02.169 align:start position:0% tackling things before before we even 00:24:02.169 --> 00:24:06.029 align:start position:0% tackling things before before we even get<00:24:02.320> there<00:24:03.629> I'm<00:24:04.629> biased<00:24:05.049> of<00:24:05.229> course<00:24:05.440> but<00:24:05.649> ENS 00:24:06.029 --> 00:24:06.039 align:start position:0% get there I'm biased of course but ENS 00:24:06.039 --> 00:24:07.259 align:start position:0% get there I'm biased of course but ENS should<00:24:06.190> be<00:24:06.309> everywhere<00:24:06.669> you<00:24:06.820> know<00:24:06.940> if<00:24:07.119> you 00:24:07.259 --> 00:24:07.269 align:start position:0% should be everywhere you know if you 00:24:07.269 --> 00:24:10.739 align:start position:0% should be everywhere you know if you have<00:24:07.450> users<00:24:08.009> if<00:24:09.009> you<00:24:09.099> have<00:24:09.429> users<00:24:09.909> you<00:24:10.509> need<00:24:10.690> e 00:24:10.739 --> 00:24:10.749 align:start position:0% have users if you have users you need e 00:24:10.749 --> 00:24:13.049 align:start position:0% have users if you have users you need e and<00:24:11.019> s<00:24:11.169> if<00:24:11.349> you<00:24:11.440> have<00:24:11.469> complicated<00:24:12.190> hashes<00:24:12.879> or 00:24:13.049 --> 00:24:13.059 align:start position:0% and s if you have complicated hashes or 00:24:13.059 --> 00:24:14.999 align:start position:0% and s if you have complicated hashes or something<00:24:13.450> you<00:24:13.570> can<00:24:13.749> resolve<00:24:14.229> into<00:24:14.529> a<00:24:14.559> simple 00:24:14.999 --> 00:24:15.009 align:start position:0% something you can resolve into a simple 00:24:15.009 --> 00:24:33.650 align:start position:0% something you can resolve into a simple string<00:24:16.469> other<00:24:17.469> questions<00:24:17.859> yes 00:24:33.650 --> 00:24:33.660 align:start position:0% 00:24:33.660 --> 00:24:37.140 align:start position:0% good<00:24:34.660> question<00:24:35.020> how<00:24:35.290> do<00:24:35.350> we<00:24:35.530> as<00:24:36.010> designer<00:24:36.430> keep 00:24:37.140 --> 00:24:37.150 align:start position:0% good question how do we as designer keep 00:24:37.150 --> 00:24:39.000 align:start position:0% good question how do we as designer keep up<00:24:37.360> with<00:24:37.570> a<00:24:37.600> constantly<00:24:38.410> and<00:24:38.740> rapidly 00:24:39.000 --> 00:24:39.010 align:start position:0% up with a constantly and rapidly 00:24:39.010 --> 00:24:41.610 align:start position:0% up with a constantly and rapidly evolving<00:24:39.910> ecosystem<00:24:40.720> the<00:24:41.410> blockchain 00:24:41.610 --> 00:24:41.620 align:start position:0% evolving ecosystem the blockchain 00:24:41.620 --> 00:24:46.020 align:start position:0% evolving ecosystem the blockchain ecosystem<00:24:42.660> we<00:24:43.660> don't<00:24:43.990> sleep<00:24:44.260> we<00:24:44.860> we<00:24:45.430> part<00:24:45.700> we 00:24:46.020 --> 00:24:46.030 align:start position:0% ecosystem we don't sleep we we part we 00:24:46.030 --> 00:24:50.640 align:start position:0% ecosystem we don't sleep we we part we party<00:24:46.510> hard<00:24:46.800> we<00:24:47.820> rape<00:24:48.820> fun<00:24:49.090> we<00:24:49.600> I<00:24:49.960> think<00:24:50.410> it's 00:24:50.640 --> 00:24:50.650 align:start position:0% party hard we rape fun we I think it's 00:24:50.650 --> 00:24:52.710 align:start position:0% party hard we rape fun we I think it's important<00:24:51.220> also<00:24:51.400> for<00:24:51.610> designers<00:24:52.390> to<00:24:52.540> be 00:24:52.710 --> 00:24:52.720 align:start position:0% important also for designers to be 00:24:52.720 --> 00:24:54.780 align:start position:0% important also for designers to be educated<00:24:53.320> to<00:24:53.440> technology<00:24:54.040> in<00:24:54.250> this<00:24:54.340> case<00:24:54.400> this 00:24:54.780 --> 00:24:54.790 align:start position:0% educated to technology in this case this 00:24:54.790 --> 00:24:56.580 align:start position:0% educated to technology in this case this is<00:24:54.850> my<00:24:55.090> personal<00:24:55.330> opinion<00:24:55.870> is<00:24:56.020> one<00:24:56.200> of<00:24:56.380> the 00:24:56.580 --> 00:24:56.590 align:start position:0% is my personal opinion is one of the 00:24:56.590 --> 00:24:58.950 align:start position:0% is my personal opinion is one of the debates<00:24:57.160> of<00:24:57.580> the<00:24:57.880> space<00:24:58.150> also<00:24:58.450> there's<00:24:58.750> a<00:24:58.840> lot 00:24:58.950 --> 00:24:58.960 align:start position:0% debates of the space also there's a lot 00:24:58.960 --> 00:25:01.980 align:start position:0% debates of the space also there's a lot of<00:24:59.140> new<00:24:59.380> designers<00:24:59.950> coming<00:25:00.460> in<00:25:00.670> who<00:25:01.300> don't 00:25:01.980 --> 00:25:01.990 align:start position:0% of new designers coming in who don't 00:25:01.990 --> 00:25:04.200 align:start position:0% of new designers coming in who don't understand<00:25:02.590> the<00:25:02.710> technology<00:25:03.280> as<00:25:03.460> deeply<00:25:03.910> but 00:25:04.200 --> 00:25:04.210 align:start position:0% understand the technology as deeply but 00:25:04.210 --> 00:25:07.080 align:start position:0% understand the technology as deeply but in<00:25:04.390> I<00:25:04.690> am<00:25:05.560> one<00:25:06.010> of<00:25:06.040> those<00:25:06.430> I<00:25:06.490> think<00:25:06.670> it's 00:25:07.080 --> 00:25:07.090 align:start position:0% in I am one of those I think it's 00:25:07.090 --> 00:25:08.730 align:start position:0% in I am one of those I think it's important<00:25:07.630> for<00:25:07.660> designers<00:25:08.050> and<00:25:08.350> for 00:25:08.730 --> 00:25:08.740 align:start position:0% important for designers and for 00:25:08.740 --> 00:25:10.950 align:start position:0% important for designers and for everybody<00:25:08.980> to<00:25:09.610> learn<00:25:10.180> about<00:25:10.360> technology<00:25:10.600> in 00:25:10.950 --> 00:25:10.960 align:start position:0% everybody to learn about technology in 00:25:10.960 --> 00:25:12.450 align:start position:0% everybody to learn about technology in general<00:25:10.990> also<00:25:11.440> be<00:25:11.560> mindful<00:25:11.800> we<00:25:12.100> were<00:25:12.220> supposed 00:25:12.450 --> 00:25:12.460 align:start position:0% general also be mindful we were supposed 00:25:12.460 --> 00:25:14.040 align:start position:0% general also be mindful we were supposed to<00:25:12.520> have<00:25:12.640> four<00:25:12.850> people<00:25:13.120> here<00:25:13.240> today<00:25:13.390> only 00:25:14.040 --> 00:25:14.050 align:start position:0% to have four people here today only 00:25:14.050 --> 00:25:20.630 align:start position:0% to have four people here today only three<00:25:14.200> made<00:25:14.440> it<00:25:14.590> so<00:25:15.540> she<00:25:16.540> was<00:25:16.800> party<00:25:17.800> hard 00:25:20.630 --> 00:25:20.640 align:start position:0% 00:25:20.640 --> 00:25:38.580 align:start position:0% additional<00:25:21.640> questions<00:25:22.290> yeah<00:25:36.540> designer<00:25:37.590> tools 00:25:38.580 --> 00:25:38.590 align:start position:0% additional questions yeah designer tools 00:25:38.590 --> 00:25:40.500 align:start position:0% additional questions yeah designer tools for<00:25:38.860> the<00:25:39.040> cooperation<00:25:39.610> between<00:25:39.790> designers 00:25:40.500 --> 00:25:40.510 align:start position:0% for the cooperation between designers 00:25:40.510 --> 00:25:43.110 align:start position:0% for the cooperation between designers and<00:25:40.840> developers<00:25:40.930> in<00:25:41.920> our<00:25:42.100> interviews<00:25:42.730> we<00:25:42.970> are 00:25:43.110 --> 00:25:43.120 align:start position:0% and developers in our interviews we are 00:25:43.120 --> 00:25:45.660 align:start position:0% and developers in our interviews we are analyzing<00:25:43.690> that<00:25:43.870> and<00:25:43.930> how<00:25:44.290> to<00:25:44.670> better 00:25:45.660 --> 00:25:45.670 align:start position:0% analyzing that and how to better 00:25:45.670 --> 00:25:49.320 align:start position:0% analyzing that and how to better integrate<00:25:46.000> and<00:25:46.480> make<00:25:47.580> concerted<00:25:48.580> effort<00:25:49.150> that 00:25:49.320 --> 00:25:49.330 align:start position:0% integrate and make concerted effort that 00:25:49.330 --> 00:25:52.800 align:start position:0% integrate and make concerted effort that designers<00:25:49.960> are<00:25:50.200> since<00:25:50.590> day<00:25:50.800> one<00:25:51.130> on<00:25:51.810> working 00:25:52.800 --> 00:25:52.810 align:start position:0% designers are since day one on working 00:25:52.810 --> 00:25:56.040 align:start position:0% designers are since day one on working together<00:25:52.960> with<00:25:53.880> so<00:25:54.880> one<00:25:55.150> key<00:25:55.390> insight<00:25:55.720> we<00:25:55.870> got 00:25:56.040 --> 00:25:56.050 align:start position:0% together with so one key insight we got 00:25:56.050 --> 00:25:58.590 align:start position:0% together with so one key insight we got from<00:25:56.260> the<00:25:56.380> interviews<00:25:56.740> was<00:25:57.240> when<00:25:58.240> people<00:25:58.510> are 00:25:58.590 --> 00:25:58.600 align:start position:0% from the interviews was when people are 00:25:58.600 --> 00:26:00.120 align:start position:0% from the interviews was when people are prototyping<00:25:59.140> these<00:25:59.320> tools<00:25:59.590> they're<00:25:59.860> using 00:26:00.120 --> 00:26:00.130 align:start position:0% prototyping these tools they're using 00:26:00.130 --> 00:26:02.160 align:start position:0% prototyping these tools they're using figma<00:26:00.430> or<00:26:00.550> these<00:26:00.700> existing<00:26:01.300> tools<00:26:01.540> but<00:26:02.020> that 00:26:02.160 --> 00:26:02.170 align:start position:0% figma or these existing tools but that 00:26:02.170 --> 00:26:04.290 align:start position:0% figma or these existing tools but that doesn't<00:26:02.470> really<00:26:02.590> give<00:26:02.830> you<00:26:02.980> a<00:26:03.010> realistic<00:26:03.640> user 00:26:04.290 --> 00:26:04.300 align:start position:0% doesn't really give you a realistic user 00:26:04.300 --> 00:26:05.640 align:start position:0% doesn't really give you a realistic user feedback<00:26:04.570> because<00:26:04.990> people<00:26:05.230> aren't<00:26:05.350> waiting 00:26:05.640 --> 00:26:05.650 align:start position:0% feedback because people aren't waiting 00:26:05.650 --> 00:26:07.680 align:start position:0% feedback because people aren't waiting for<00:26:05.980> those<00:26:06.130> load-times<00:26:06.400> or<00:26:06.940> when<00:26:07.390> they<00:26:07.480> click 00:26:07.680 --> 00:26:07.690 align:start position:0% for those load-times or when they click 00:26:07.690 --> 00:26:08.880 align:start position:0% for those load-times or when they click everything<00:26:08.050> seems<00:26:08.260> so<00:26:08.410> smooth<00:26:08.650> they're<00:26:08.800> like 00:26:08.880 --> 00:26:08.890 align:start position:0% everything seems so smooth they're like 00:26:08.890 --> 00:26:10.770 align:start position:0% everything seems so smooth they're like yeah<00:26:08.980> this<00:26:09.160> is<00:26:09.280> awesome<00:26:09.400> from<00:26:10.210> the<00:26:10.390> existing 00:26:10.770 --> 00:26:10.780 align:start position:0% yeah this is awesome from the existing 00:26:10.780 --> 00:26:12.210 align:start position:0% yeah this is awesome from the existing patterns<00:26:11.140> but<00:26:11.260> you<00:26:11.320> need<00:26:11.560> to<00:26:11.650> have<00:26:11.800> some<00:26:12.100> sort 00:26:12.210 --> 00:26:12.220 align:start position:0% patterns but you need to have some sort 00:26:12.220 --> 00:26:13.710 align:start position:0% patterns but you need to have some sort of<00:26:12.310> test<00:26:12.550> network<00:26:12.850> or<00:26:13.030> some<00:26:13.150> sort<00:26:13.690> of 00:26:13.710 --> 00:26:13.720 align:start position:0% of test network or some sort of 00:26:13.720 --> 00:26:15.990 align:start position:0% of test network or some sort of application<00:26:14.710> that<00:26:15.250> kind<00:26:15.400> of<00:26:15.430> facilitates 00:26:15.990 --> 00:26:16.000 align:start position:0% application that kind of facilitates 00:26:16.000 --> 00:26:36.529 align:start position:0% application that kind of facilitates that 00:26:36.529 --> 00:26:36.539 align:start position:0% 00:26:36.539 --> 00:26:39.029 align:start position:0% so<00:26:37.539> he's<00:26:37.720> basically<00:26:37.870> saying<00:26:38.350> that<00:26:38.679> people 00:26:39.029 --> 00:26:39.039 align:start position:0% so he's basically saying that people 00:26:39.039 --> 00:26:40.289 align:start position:0% so he's basically saying that people don't<00:26:39.190> really<00:26:39.580> need<00:26:39.700> to<00:26:39.820> understand 00:26:40.289 --> 00:26:40.299 align:start position:0% don't really need to understand 00:26:40.299 --> 00:26:43.049 align:start position:0% don't really need to understand protocols<00:26:41.110> in<00:26:41.410> web<00:26:41.650> tool<00:26:41.830> but<00:26:42.490> it's<00:26:42.730> kind<00:26:43.000> of 00:26:43.049 --> 00:26:43.059 align:start position:0% protocols in web tool but it's kind of 00:26:43.059 --> 00:26:44.669 align:start position:0% protocols in web tool but it's kind of imperative<00:26:43.539> for<00:26:43.809> the<00:26:43.929> decentralized 00:26:44.669 --> 00:26:44.679 align:start position:0% imperative for the decentralized 00:26:44.679 --> 00:26:45.960 align:start position:0% imperative for the decentralized technology<00:26:44.980> stack<00:26:45.490> for<00:26:45.700> people<00:26:45.880> to 00:26:45.960 --> 00:26:45.970 align:start position:0% technology stack for people to 00:26:45.970 --> 00:26:48.090 align:start position:0% technology stack for people to understand<00:26:46.360> these<00:26:46.929> to<00:26:47.380> actually<00:26:47.740> benefit 00:26:48.090 --> 00:26:48.100 align:start position:0% understand these to actually benefit 00:26:48.100 --> 00:26:57.600 align:start position:0% understand these to actually benefit from<00:26:48.250> the<00:26:48.370> valley<00:26:55.260> exactly<00:26:56.260> we<00:26:56.710> also<00:26:56.860> asked<00:26:57.190> do 00:26:57.600 --> 00:26:57.610 align:start position:0% from the valley exactly we also asked do 00:26:57.610 --> 00:26:59.940 align:start position:0% from the valley exactly we also asked do users<00:26:58.600> need<00:26:58.840> to<00:26:58.870> know<00:26:59.140> about<00:26:59.320> the<00:26:59.530> blockchain 00:26:59.940 --> 00:26:59.950 align:start position:0% users need to know about the blockchain 00:26:59.950 --> 00:27:02.700 align:start position:0% users need to know about the blockchain and<00:27:00.159> to<00:27:00.610> all<00:27:00.789> the<00:27:00.970> people<00:27:01.240> that<00:27:01.330> we<00:27:01.710> interface 00:27:02.700 --> 00:27:02.710 align:start position:0% and to all the people that we interface 00:27:02.710 --> 00:27:04.830 align:start position:0% and to all the people that we interface and<00:27:02.919> so<00:27:03.130> sorry<00:27:03.460> to<00:27:03.640> just<00:27:03.820> step<00:27:04.510> back<00:27:04.630> he's 00:27:04.830 --> 00:27:04.840 align:start position:0% and so sorry to just step back he's 00:27:04.840 --> 00:27:07.230 align:start position:0% and so sorry to just step back he's saying<00:27:05.049> is<00:27:05.169> it<00:27:05.289> limiting<00:27:05.770> isn't<00:27:06.730> having<00:27:07.150> to 00:27:07.230 --> 00:27:07.240 align:start position:0% saying is it limiting isn't having to 00:27:07.240 --> 00:27:09.000 align:start position:0% saying is it limiting isn't having to know<00:27:07.360> that<00:27:07.539> is<00:27:07.659> it<00:27:07.809> limiting<00:27:08.230> to<00:27:08.380> mass<00:27:08.620> mass 00:27:09.000 --> 00:27:09.010 align:start position:0% know that is it limiting to mass mass 00:27:09.010 --> 00:27:10.520 align:start position:0% know that is it limiting to mass mass adoption<00:27:09.250> or<00:27:09.580> will<00:27:09.730> we<00:27:09.850> ever<00:27:10.000> get<00:27:10.240> to<00:27:10.390> a<00:27:10.419> point 00:27:10.520 --> 00:27:10.530 align:start position:0% adoption or will we ever get to a point 00:27:10.530 --> 00:27:14.610 align:start position:0% adoption or will we ever get to a point I<00:27:11.669> have<00:27:12.669> faith<00:27:12.970> in<00:27:13.210> us<00:27:13.360> that<00:27:13.630> we<00:27:13.690> will<00:27:13.960> bring<00:27:14.409> it 00:27:14.610 --> 00:27:14.620 align:start position:0% I have faith in us that we will bring it 00:27:14.620 --> 00:27:16.830 align:start position:0% I have faith in us that we will bring it and<00:27:14.770> today<00:27:15.010> we<00:27:15.190> had<00:27:15.400> an<00:27:15.789> awesome<00:27:16.059> onboarding 00:27:16.830 --> 00:27:16.840 align:start position:0% and today we had an awesome onboarding 00:27:16.840 --> 00:27:19.529 align:start position:0% and today we had an awesome onboarding tract<00:27:17.500> onboarding<00:27:18.370> breakout<00:27:18.850> where<00:27:19.120> a<00:27:19.150> lot<00:27:19.510> of 00:27:19.529 --> 00:27:19.539 align:start position:0% tract onboarding breakout where a lot of 00:27:19.539 --> 00:27:21.690 align:start position:0% tract onboarding breakout where a lot of people<00:27:19.720> tried<00:27:20.470> and<00:27:20.770> tackle<00:27:21.159> to<00:27:21.280> solve<00:27:21.549> these 00:27:21.690 --> 00:27:21.700 align:start position:0% people tried and tackle to solve these 00:27:21.700 --> 00:27:24.060 align:start position:0% people tried and tackle to solve these problems<00:27:21.760> to<00:27:22.330> hide<00:27:22.600> and<00:27:22.929> bring<00:27:23.440> everything<00:27:23.799> in 00:27:24.060 --> 00:27:24.070 align:start position:0% problems to hide and bring everything in 00:27:24.070 --> 00:27:26.149 align:start position:0% problems to hide and bring everything in the<00:27:24.190> height<00:27:24.400> bucket<00:27:24.880> okay<00:27:25.150> you<00:27:25.570> have<00:27:25.750> here 00:27:26.149 --> 00:27:26.159 align:start position:0% the height bucket okay you have here 00:27:26.159 --> 00:27:28.740 align:start position:0% the height bucket okay you have here universal<00:27:27.159> logins<00:27:27.580> Alex<00:27:28.120> to<00:27:28.179> understand<00:27:28.539> he 00:27:28.740 --> 00:27:28.750 align:start position:0% universal logins Alex to understand he 00:27:28.750 --> 00:27:30.419 align:start position:0% universal logins Alex to understand he created<00:27:29.169> also<00:27:29.380> an<00:27:29.590> awesome<00:27:29.679> tool<00:27:29.950> to<00:27:30.130> hide<00:27:30.400> a 00:27:30.419 --> 00:27:30.429 align:start position:0% created also an awesome tool to hide a 00:27:30.429 --> 00:27:32.970 align:start position:0% created also an awesome tool to hide a lot<00:27:30.880> of<00:27:31.030> that<00:27:31.179> complexity<00:27:31.690> gasps<00:27:32.110> etc<00:27:32.740> and 00:27:32.970 --> 00:27:32.980 align:start position:0% lot of that complexity gasps etc and 00:27:32.980 --> 00:27:35.460 align:start position:0% lot of that complexity gasps etc and private<00:27:33.460> keys<00:27:33.640> and<00:27:33.850> I<00:27:34.600> think<00:27:34.960> we<00:27:35.080> will<00:27:35.230> get 00:27:35.460 --> 00:27:35.470 align:start position:0% private keys and I think we will get 00:27:35.470 --> 00:27:38.039 align:start position:0% private keys and I think we will get there<00:27:35.710> but<00:27:36.280> there<00:27:36.700> is<00:27:36.789> this<00:27:37.030> layer<00:27:37.480> that<00:27:37.870> is 00:27:38.039 --> 00:27:38.049 align:start position:0% there but there is this layer that is 00:27:38.049 --> 00:27:40.710 align:start position:0% there but there is this layer that is unavoidable<00:27:39.039> to<00:27:39.370> explain<00:27:39.730> why<00:27:40.120> we<00:27:40.450> are<00:27:40.570> doing 00:27:40.710 --> 00:27:40.720 align:start position:0% unavoidable to explain why we are doing 00:27:40.720 --> 00:27:43.399 align:start position:0% unavoidable to explain why we are doing this<00:27:41.020> and<00:27:41.320> why<00:27:41.500> our<00:27:41.740> decentralized<00:27:42.299> a 00:27:43.399 --> 00:27:43.409 align:start position:0% this and why our decentralized a 00:27:43.409 --> 00:27:45.539 align:start position:0% this and why our decentralized a Facebook<00:27:44.409> will<00:27:44.679> be<00:27:44.710> a<00:27:44.860> better<00:27:45.280> than 00:27:45.539 --> 00:27:45.549 align:start position:0% Facebook will be a better than 00:27:45.549 --> 00:27:48.299 align:start position:0% Facebook will be a better than decentralized<00:27:46.390> version<00:27:46.960> and<00:27:47.110> so<00:27:47.260> that<00:27:47.470> is<00:27:47.650> you 00:27:48.299 --> 00:27:48.309 align:start position:0% decentralized version and so that is you 00:27:48.309 --> 00:27:51.390 align:start position:0% decentralized version and so that is you need<00:27:48.490> to<00:27:48.520> explain<00:27:49.179> and<00:27:49.510> maybe<00:27:50.409> hopefully<00:27:50.950> not 00:27:51.390 --> 00:27:51.400 align:start position:0% need to explain and maybe hopefully not 00:27:51.400 --> 00:27:52.950 align:start position:0% need to explain and maybe hopefully not you<00:27:51.640> need<00:27:51.820> to<00:27:51.850> explain<00:27:52.120> some<00:27:52.360> technicality 00:27:52.950 --> 00:27:52.960 align:start position:0% you need to explain some technicality 00:27:52.960 --> 00:27:55.289 align:start position:0% you need to explain some technicality hopefully<00:27:53.380> you<00:27:53.559> don't<00:27:53.740> need<00:27:54.010> also<00:27:54.549> when<00:27:55.000> other 00:27:55.289 --> 00:27:55.299 align:start position:0% hopefully you don't need also when other 00:27:55.299 --> 00:27:58.110 align:start position:0% hopefully you don't need also when other scalability<00:27:56.200> solutions<00:27:56.679> and<00:27:57.039> side<00:27:57.820> chains 00:27:58.110 --> 00:27:58.120 align:start position:0% scalability solutions and side chains 00:27:58.120 --> 00:28:01.289 align:start position:0% scalability solutions and side chains and<00:27:59.370> state<00:28:00.370> channels<00:28:00.700> come<00:28:00.850> in<00:28:00.940> I<00:28:01.030> think<00:28:01.150> is 00:28:01.289 --> 00:28:01.299 align:start position:0% and state channels come in I think is 00:28:01.299 --> 00:28:02.730 align:start position:0% and state channels come in I think is going<00:28:01.419> to<00:28:01.480> change<00:28:01.539> the<00:28:01.990> dynamics<00:28:02.440> of<00:28:02.530> the<00:28:02.590> user 00:28:02.730 --> 00:28:02.740 align:start position:0% going to change the dynamics of the user 00:28:02.740 --> 00:28:03.990 align:start position:0% going to change the dynamics of the user interfaces<00:28:03.340> and<00:28:03.460> kind<00:28:03.640> of<00:28:03.669> make<00:28:03.820> it<00:28:03.909> more 00:28:03.990 --> 00:28:04.000 align:start position:0% interfaces and kind of make it more 00:28:04.000 --> 00:28:05.640 align:start position:0% interfaces and kind of make it more palatable<00:28:04.299> for<00:28:04.630> users<00:28:05.049> because<00:28:05.500> not 00:28:05.640 --> 00:28:05.650 align:start position:0% palatable for users because not 00:28:05.650 --> 00:28:07.710 align:start position:0% palatable for users because not everything<00:28:05.919> needs<00:28:06.220> to<00:28:06.309> be<00:28:06.370> decentralized<00:28:06.909> you 00:28:07.710 --> 00:28:07.720 align:start position:0% everything needs to be decentralized you 00:28:07.720 --> 00:28:09.149 align:start position:0% everything needs to be decentralized you can<00:28:07.929> play<00:28:08.260> around<00:28:08.320> with<00:28:08.530> that<00:28:08.710> so<00:28:08.950> I<00:28:08.980> think 00:28:09.149 --> 00:28:09.159 align:start position:0% can play around with that so I think 00:28:09.159 --> 00:28:10.950 align:start position:0% can play around with that so I think it's<00:28:09.730> exciting<00:28:10.150> to<00:28:10.270> see<00:28:10.299> where<00:28:10.570> we're<00:28:10.720> going 00:28:10.950 --> 00:28:10.960 align:start position:0% it's exciting to see where we're going 00:28:10.960 --> 00:28:13.919 align:start position:0% it's exciting to see where we're going and<00:28:12.030> just<00:28:13.030> last<00:28:13.210> question<00:28:13.539> we<00:28:13.630> have<00:28:13.750> five 00:28:13.919 --> 00:28:13.929 align:start position:0% and just last question we have five 00:28:13.929 --> 00:28:26.880 align:start position:0% and just last question we have five seconds<00:28:14.289> right<00:28:14.500> there 00:28:26.880 --> 00:28:26.890 align:start position:0% 00:28:26.890 --> 00:28:30.760 align:start position:0% yeah<00:28:28.750> yeah<00:28:29.750> like<00:28:29.960> that's<00:28:30.140> one<00:28:30.410> of<00:28:30.530> our<00:28:30.620> biggest 00:28:30.760 --> 00:28:30.770 align:start position:0% yeah yeah like that's one of our biggest 00:28:30.770 --> 00:28:32.320 align:start position:0% yeah yeah like that's one of our biggest things<00:28:31.070> right<00:28:31.250> like<00:28:31.280> onboarding<00:28:31.910> like<00:28:32.210> the 00:28:32.320 --> 00:28:32.330 align:start position:0% things right like onboarding like the 00:28:32.330 --> 00:28:33.760 align:start position:0% things right like onboarding like the first<00:28:32.540> step<00:28:32.750> the<00:28:32.870> most<00:28:33.050> important<00:28:33.440> step<00:28:33.620> is 00:28:33.760 --> 00:28:33.770 align:start position:0% first step the most important step is 00:28:33.770 --> 00:28:34.990 align:start position:0% first step the most important step is like<00:28:33.920> one<00:28:34.190> of<00:28:34.220> the<00:28:34.310> hardest<00:28:34.520> steps<00:28:34.880> in 00:28:34.990 --> 00:28:35.000 align:start position:0% like one of the hardest steps in 00:28:35.000 --> 00:28:37.150 align:start position:0% like one of the hardest steps in blockchain<00:28:35.300> right<00:28:35.450> now<00:28:35.570> so<00:28:36.110> we<00:28:36.530> are<00:28:36.890> all 00:28:37.150 --> 00:28:37.160 align:start position:0% blockchain right now so we are all 00:28:37.160 --> 00:28:38.860 align:start position:0% blockchain right now so we are all working<00:28:37.490> super<00:28:37.820> hard<00:28:37.970> to<00:28:38.240> fix<00:28:38.390> onboarding<00:28:38.780> if 00:28:38.860 --> 00:28:38.870 align:start position:0% working super hard to fix onboarding if 00:28:38.870 --> 00:28:40.360 align:start position:0% working super hard to fix onboarding if you<00:28:38.930> guys<00:28:39.020> are<00:28:39.140> we<00:28:39.200> going<00:28:39.380> to<00:28:39.440> def<00:28:39.620> like<00:28:39.950> into 00:28:40.360 --> 00:28:40.370 align:start position:0% you guys are we going to def like into 00:28:40.370 --> 00:28:42.520 align:start position:0% you guys are we going to def like into the<00:28:40.460> talks<00:28:40.670> there's<00:28:40.940> like<00:28:41.200> universal<00:28:42.200> logins 00:28:42.520 --> 00:28:42.530 align:start position:0% the talks there's like universal logins 00:28:42.530 --> 00:28:43.810 align:start position:0% the talks there's like universal logins and<00:28:42.650> there's<00:28:42.800> like<00:28:42.920> tons<00:28:43.130> of<00:28:43.190> solutions<00:28:43.610> like 00:28:43.810 --> 00:28:43.820 align:start position:0% and there's like tons of solutions like 00:28:43.820 --> 00:28:45.670 align:start position:0% and there's like tons of solutions like popping<00:28:44.180> in<00:28:44.270> left<00:28:44.510> and<00:28:44.630> right<00:28:44.810> sorry<00:28:45.230> were<00:28:45.620> you 00:28:45.670 --> 00:28:45.680 align:start position:0% popping in left and right sorry were you 00:28:45.680 --> 00:28:46.720 align:start position:0% popping in left and right sorry were you talking<00:28:45.770> about<00:28:46.070> actually<00:28:46.310> onboarding<00:28:46.640> new 00:28:46.720 --> 00:28:46.730 align:start position:0% talking about actually onboarding new 00:28:46.730 --> 00:28:48.790 align:start position:0% talking about actually onboarding new designers<00:28:47.090> into<00:28:47.360> the<00:28:47.450> space<00:28:47.660> yeah<00:28:47.900> so<00:28:48.110> these 00:28:48.790 --> 00:28:48.800 align:start position:0% designers into the space yeah so these 00:28:48.800 --> 00:28:50.710 align:start position:0% designers into the space yeah so these these<00:28:49.130> efforts<00:28:49.430> like<00:28:49.880> Conflux<00:28:50.390> what 00:28:50.710 --> 00:28:50.720 align:start position:0% these efforts like Conflux what 00:28:50.720 --> 00:28:52.600 align:start position:0% these efforts like Conflux what consensus<00:28:51.500> I<00:28:51.650> think<00:28:51.920> just<00:28:52.130> on<00:28:52.250> wording<00:28:52.520> like 00:28:52.600 --> 00:28:52.610 align:start position:0% consensus I think just on wording like 00:28:52.610 --> 00:28:54.190 align:start position:0% consensus I think just on wording like 70<00:28:52.910> designers<00:28:53.270> in<00:28:53.420> the<00:28:53.480> past<00:28:53.660> few<00:28:53.810> years<00:28:53.870> so 00:28:54.190 --> 00:28:54.200 align:start position:0% 70 designers in the past few years so 00:28:54.200 --> 00:28:56.380 align:start position:0% 70 designers in the past few years so there's<00:28:55.160> a<00:28:55.250> lot<00:28:55.370> of<00:28:55.490> people<00:28:55.730> that<00:28:55.880> are<00:28:56.000> doing 00:28:56.380 --> 00:28:56.390 align:start position:0% there's a lot of people that are doing 00:28:56.390 --> 00:28:59.200 align:start position:0% there's a lot of people that are doing great<00:28:56.630> stuff<00:28:56.860> and<00:28:57.860> you<00:28:58.370> saw<00:28:58.700> workshops 00:28:59.200 --> 00:28:59.210 align:start position:0% great stuff and you saw workshops 00:28:59.210 --> 00:29:01.210 align:start position:0% great stuff and you saw workshops happening<00:28:59.660> over<00:28:59.960> Def<00:29:00.140> Con<00:29:00.350> there<00:29:00.650> is<00:29:00.800> Gendry 00:29:01.210 --> 00:29:01.220 align:start position:0% happening over Def Con there is Gendry 00:29:01.220 --> 00:29:03.070 align:start position:0% happening over Def Con there is Gendry and<00:29:01.460> nos<00:29:01.640> that<00:29:02.000> did<00:29:02.210> the<00:29:02.300> mechanism<00:29:02.840> design 00:29:03.070 --> 00:29:03.080 align:start position:0% and nos that did the mechanism design 00:29:03.080 --> 00:29:06.460 align:start position:0% and nos that did the mechanism design for<00:29:03.260> you<00:29:03.380> and<00:29:04.250> the<00:29:04.400> UX<00:29:04.700> implications<00:29:05.300> Lex<00:29:06.290> was 00:29:06.460 --> 00:29:06.470 align:start position:0% for you and the UX implications Lex was 00:29:06.470 --> 00:29:08.110 align:start position:0% for you and the UX implications Lex was there<00:29:06.650> with<00:29:06.800> his<00:29:06.920> universal<00:29:07.370> logins<00:29:07.700> and<00:29:07.820> kind 00:29:08.110 --> 00:29:08.120 align:start position:0% there with his universal logins and kind 00:29:08.120 --> 00:29:09.700 align:start position:0% there with his universal logins and kind of<00:29:08.180> bringing<00:29:08.450> that<00:29:08.540> UX<00:29:08.840> voice<00:29:09.110> and<00:29:09.440> that<00:29:09.530> thing 00:29:09.700 --> 00:29:09.710 align:start position:0% of bringing that UX voice and that thing 00:29:09.710 --> 00:29:11.530 align:start position:0% of bringing that UX voice and that thing is<00:29:09.800> just<00:29:09.860> gonna<00:29:10.040> get<00:29:10.220> better<00:29:10.370> from<00:29:10.580> here<00:29:10.790> thank 00:29:11.530 --> 00:29:11.540 align:start position:0% is just gonna get better from here thank 00:29:11.540 --> 00:29:13.150 align:start position:0% is just gonna get better from here thank you<00:29:11.660> for<00:29:11.840> everyone<00:29:12.050> for<00:29:12.170> your<00:29:12.320> time<00:29:12.620> and<00:29:12.800> be 00:29:13.150 --> 00:29:13.160 align:start position:0% you for everyone for your time and be 00:29:13.160 --> 00:29:15.470 align:start position:0% you for everyone for your time and be sure<00:29:13.340> to<00:29:13.370> reach<00:29:13.610> out<00:29:13.760> to<00:29:13.790> us 00:29:15.470 --> 00:29:15.480 align:start position:0% sure to reach out to us 00:29:15.480 --> 00:29:19.509 align:start position:0% sure to reach out to us [Applause]