WEBVTT Kind: captions Language: en 00:00:05.130 --> 00:00:09.270 align:start position:0% how's<00:00:06.130> it<00:00:06.160> going<00:00:06.850> I'm<00:00:07.090> James<00:00:08.280> here 00:00:09.270 --> 00:00:09.280 align:start position:0% how's it going I'm James here 00:00:09.280 --> 00:00:14.190 align:start position:0% how's it going I'm James here representing<00:00:09.820> abridged<00:00:11.370> this<00:00:12.370> talk<00:00:12.700> is<00:00:13.200> sort 00:00:14.190 --> 00:00:14.200 align:start position:0% representing abridged this talk is sort 00:00:14.200 --> 00:00:16.289 align:start position:0% representing abridged this talk is sort of<00:00:14.230> it's<00:00:14.530> called<00:00:14.889> beyond<00:00:15.129> burner<00:00:15.340> intuitive 00:00:16.289 --> 00:00:16.299 align:start position:0% of it's called beyond burner intuitive 00:00:16.299 --> 00:00:17.850 align:start position:0% of it's called beyond burner intuitive design<00:00:16.420> and<00:00:16.869> incremental<00:00:17.380> decentralisation 00:00:17.850 --> 00:00:17.860 align:start position:0% design and incremental decentralisation 00:00:17.860 --> 00:00:21.630 align:start position:0% design and incremental decentralisation so<00:00:18.460> really<00:00:19.390> focused<00:00:19.720> on<00:00:19.840> UX<00:00:20.440> issues<00:00:20.640> bridges 00:00:21.630 --> 00:00:21.640 align:start position:0% so really focused on UX issues bridges 00:00:21.640 --> 00:00:24.690 align:start position:0% so really focused on UX issues bridges is<00:00:21.730> a<00:00:22.020> development<00:00:23.020> toolkit<00:00:23.470> and<00:00:23.860> we<00:00:24.310> focused 00:00:24.690 --> 00:00:24.700 align:start position:0% is a development toolkit and we focused 00:00:24.700 --> 00:00:26.970 align:start position:0% is a development toolkit and we focused on<00:00:24.990> intuitive<00:00:25.990> design<00:00:26.110> for<00:00:26.620> blocking 00:00:26.970 --> 00:00:26.980 align:start position:0% on intuitive design for blocking 00:00:26.980 --> 00:00:31.350 align:start position:0% on intuitive design for blocking applications<00:00:27.520> to<00:00:28.270> onboard<00:00:28.660> new<00:00:29.350> users<00:00:30.360> my 00:00:31.350 --> 00:00:31.360 align:start position:0% applications to onboard new users my 00:00:31.360 --> 00:00:32.729 align:start position:0% applications to onboard new users my background<00:00:31.780> if<00:00:31.900> you<00:00:31.990> if<00:00:32.230> you've<00:00:32.410> seen<00:00:32.619> me 00:00:32.729 --> 00:00:32.739 align:start position:0% background if you if you've seen me 00:00:32.739 --> 00:00:34.860 align:start position:0% background if you if you've seen me before<00:00:32.860> I<00:00:33.100> was<00:00:33.579> with<00:00:34.000> the<00:00:34.300> grants<00:00:34.600> team<00:00:34.780> you 00:00:34.860 --> 00:00:34.870 align:start position:0% before I was with the grants team you 00:00:34.870 --> 00:00:37.319 align:start position:0% before I was with the grants team you may<00:00:34.989> know<00:00:35.289> me<00:00:35.410> from<00:00:35.440> there<00:00:35.739> at<00:00:35.890> the<00:00:35.980> EF<00:00:36.329> but 00:00:37.319 --> 00:00:37.329 align:start position:0% may know me from there at the EF but 00:00:37.329 --> 00:00:38.759 align:start position:0% may know me from there at the EF but this<00:00:37.510> is<00:00:37.690> sort<00:00:38.079> of<00:00:38.109> the<00:00:38.199> new<00:00:38.289> project<00:00:38.710> that 00:00:38.759 --> 00:00:38.769 align:start position:0% this is sort of the new project that 00:00:38.769 --> 00:00:43.319 align:start position:0% this is sort of the new project that I've<00:00:39.760> been<00:00:39.820> working<00:00:40.089> on<00:00:40.300> since<00:00:40.839> April<00:00:42.059> so<00:00:43.059> a 00:00:43.319 --> 00:00:43.329 align:start position:0% I've been working on since April so a 00:00:43.329 --> 00:00:44.939 align:start position:0% I've been working on since April so a little<00:00:43.749> overview<00:00:44.079> we'll<00:00:44.620> go<00:00:44.769> over<00:00:44.859> what 00:00:44.939 --> 00:00:44.949 align:start position:0% little overview we'll go over what 00:00:44.949 --> 00:00:47.939 align:start position:0% little overview we'll go over what beyond<00:00:45.429> burner<00:00:45.670> really<00:00:46.120> means<00:00:46.949> the 00:00:47.939 --> 00:00:47.949 align:start position:0% beyond burner really means the 00:00:47.949 --> 00:00:49.340 align:start position:0% beyond burner really means the significance<00:00:48.460> of<00:00:48.519> the<00:00:48.609> application<00:00:49.089> layer 00:00:49.340 --> 00:00:49.350 align:start position:0% significance of the application layer 00:00:49.350 --> 00:00:52.860 align:start position:0% significance of the application layer the<00:00:50.350> current<00:00:50.920> state<00:00:51.249> of<00:00:51.429> where<00:00:52.149> we<00:00:52.269> are<00:00:52.449> within 00:00:52.860 --> 00:00:52.870 align:start position:0% the current state of where we are within 00:00:52.870 --> 00:00:55.469 align:start position:0% the current state of where we are within adoption<00:00:53.739> and<00:00:53.890> then<00:00:54.519> what<00:00:54.940> fixing<00:00:55.390> these 00:00:55.469 --> 00:00:55.479 align:start position:0% adoption and then what fixing these 00:00:55.479 --> 00:00:58.259 align:start position:0% adoption and then what fixing these issues<00:00:55.809> actually<00:00:56.109> looks<00:00:56.260> like<00:00:56.440> so<00:00:57.429> why<00:00:57.969> beyond 00:00:58.259 --> 00:00:58.269 align:start position:0% issues actually looks like so why beyond 00:00:58.269 --> 00:01:02.129 align:start position:0% issues actually looks like so why beyond burner<00:00:59.370> so<00:01:00.370> the<00:01:00.729> BR<00:01:00.969> the<00:01:01.269> beyond<00:01:01.809> burner<00:01:02.019> is 00:01:02.129 --> 00:01:02.139 align:start position:0% burner so the BR the beyond burner is 00:01:02.139 --> 00:01:04.259 align:start position:0% burner so the BR the beyond burner is the<00:01:02.440> beyond<00:01:02.979> Berger<00:01:03.370> narrative<00:01:03.789> plus<00:01:04.059> the 00:01:04.259 --> 00:01:04.269 align:start position:0% the beyond Berger narrative plus the 00:01:04.269 --> 00:01:08.250 align:start position:0% the beyond Berger narrative plus the burner<00:01:04.449> wallet<00:01:05.760> both<00:01:06.760> of<00:01:06.970> these<00:01:07.200> sort<00:01:08.200> of 00:01:08.250 --> 00:01:08.260 align:start position:0% burner wallet both of these sort of 00:01:08.260 --> 00:01:10.050 align:start position:0% burner wallet both of these sort of industries<00:01:08.980> which<00:01:09.160> is<00:01:09.310> the<00:01:09.760> cryptocurrency 00:01:10.050 --> 00:01:10.060 align:start position:0% industries which is the cryptocurrency 00:01:10.060 --> 00:01:13.380 align:start position:0% industries which is the cryptocurrency space<00:01:10.900> as<00:01:11.080> well<00:01:11.200> as<00:01:11.380> the<00:01:11.850> alternative<00:01:12.850> meets 00:01:13.380 --> 00:01:13.390 align:start position:0% space as well as the alternative meets 00:01:13.390 --> 00:01:15.150 align:start position:0% space as well as the alternative meets industry<00:01:13.660> or<00:01:13.990> sort<00:01:14.200> of<00:01:14.290> holistic<00:01:14.680> solutions 00:01:15.150 --> 00:01:15.160 align:start position:0% industry or sort of holistic solutions 00:01:15.160 --> 00:01:18.560 align:start position:0% industry or sort of holistic solutions that<00:01:15.940> are<00:01:16.330> trying<00:01:16.810> to<00:01:16.900> disrupt<00:01:17.290> incumbent 00:01:18.560 --> 00:01:18.570 align:start position:0% that are trying to disrupt incumbent 00:01:18.570 --> 00:01:21.840 align:start position:0% that are trying to disrupt incumbent systems<00:01:19.570> and<00:01:19.870> they<00:01:20.440> sort<00:01:20.650> of<00:01:20.770> face<00:01:21.190> similar 00:01:21.840 --> 00:01:21.850 align:start position:0% systems and they sort of face similar 00:01:21.850 --> 00:01:24.660 align:start position:0% systems and they sort of face similar adoption<00:01:22.510> hurdles<00:01:22.900> which<00:01:23.440> is<00:01:23.620> mainly<00:01:24.370> like 00:01:24.660 --> 00:01:24.670 align:start position:0% adoption hurdles which is mainly like 00:01:24.670 --> 00:01:28.710 align:start position:0% adoption hurdles which is mainly like unfamiliar<00:01:25.530> like<00:01:27.480> experiences<00:01:28.480> and<00:01:28.660> an 00:01:28.710 --> 00:01:28.720 align:start position:0% unfamiliar like experiences and an 00:01:28.720 --> 00:01:31.290 align:start position:0% unfamiliar like experiences and an unfamiliar<00:01:29.110> product<00:01:29.770> which<00:01:30.670> is<00:01:30.970> also 00:01:31.290 --> 00:01:31.300 align:start position:0% unfamiliar product which is also 00:01:31.300 --> 00:01:33.990 align:start position:0% unfamiliar product which is also somewhat<00:01:31.690> inconvenient<00:01:32.560> for<00:01:32.920> people<00:01:33.190> who 00:01:33.990 --> 00:01:34.000 align:start position:0% somewhat inconvenient for people who 00:01:34.000 --> 00:01:38.340 align:start position:0% somewhat inconvenient for people who want<00:01:34.270> to<00:01:34.920> get<00:01:35.920> at<00:01:36.220> like<00:01:36.490> use<00:01:36.790> it<00:01:37.020> and<00:01:38.020> they 00:01:38.340 --> 00:01:38.350 align:start position:0% want to get at like use it and they 00:01:38.350 --> 00:01:41.220 align:start position:0% want to get at like use it and they don't<00:01:38.470> know<00:01:38.590> how<00:01:39.240> so<00:01:40.240> it<00:01:40.480> creates<00:01:40.870> the 00:01:41.220 --> 00:01:41.230 align:start position:0% don't know how so it creates the 00:01:41.230 --> 00:01:42.930 align:start position:0% don't know how so it creates the unfamiliarity<00:01:41.680> and<00:01:42.040> inconvenience<00:01:42.610> creates 00:01:42.930 --> 00:01:42.940 align:start position:0% unfamiliarity and inconvenience creates 00:01:42.940 --> 00:01:46.290 align:start position:0% unfamiliarity and inconvenience creates this<00:01:43.090> comfort<00:01:43.540> and<00:01:43.980> friction<00:01:44.980> for<00:01:45.670> their<00:01:46.120> end 00:01:46.290 --> 00:01:46.300 align:start position:0% this comfort and friction for their end 00:01:46.300 --> 00:01:50.010 align:start position:0% this comfort and friction for their end users<00:01:47.790> at<00:01:48.790> a<00:01:48.880> high<00:01:49.060> level<00:01:49.090> it's<00:01:49.630> kind<00:01:49.780> of<00:01:49.870> like 00:01:50.010 --> 00:01:50.020 align:start position:0% users at a high level it's kind of like 00:01:50.020 --> 00:01:52.530 align:start position:0% users at a high level it's kind of like I<00:01:50.140> like<00:01:50.350> meat<00:01:50.650> I<00:01:50.920> you<00:01:51.670> know<00:01:51.760> I<00:01:51.940> don't<00:01:52.150> know<00:01:52.270> what 00:01:52.530 --> 00:01:52.540 align:start position:0% I like meat I you know I don't know what 00:01:52.540 --> 00:01:56.040 align:start position:0% I like meat I you know I don't know what this<00:01:52.720> vegan<00:01:52.900> stuff<00:01:53.560> is<00:01:54.000> and<00:01:55.000> and<00:01:55.630> I<00:01:55.780> don't<00:01:55.930> know 00:01:56.040 --> 00:01:56.050 align:start position:0% this vegan stuff is and and I don't know 00:01:56.050 --> 00:01:57.660 align:start position:0% this vegan stuff is and and I don't know I<00:01:56.320> don't<00:01:56.560> really<00:01:56.800> like<00:01:56.950> the<00:01:57.070> taste<00:01:57.220> of<00:01:57.400> it<00:01:57.490> or 00:01:57.660 --> 00:01:57.670 align:start position:0% I don't really like the taste of it or 00:01:57.670 --> 00:01:58.080 align:start position:0% I don't really like the taste of it or something 00:01:58.080 --> 00:01:58.090 align:start position:0% something 00:01:58.090 --> 00:02:00.330 align:start position:0% something for<00:01:58.930> aetherium<00:01:59.410> it's<00:01:59.650> like<00:01:59.830> I<00:02:00.040> don't<00:02:00.280> know 00:02:00.330 --> 00:02:00.340 align:start position:0% for aetherium it's like I don't know 00:02:00.340 --> 00:02:02.010 align:start position:0% for aetherium it's like I don't know what<00:02:00.430> a<00:02:00.490> private<00:02:00.760> key<00:02:00.909> is<00:02:00.940> what<00:02:01.240> is<00:02:01.360> gas<00:02:01.630> and 00:02:02.010 --> 00:02:02.020 align:start position:0% what a private key is what is gas and 00:02:02.020 --> 00:02:05.370 align:start position:0% what a private key is what is gas and why<00:02:02.860> does<00:02:03.040> it<00:02:03.070> take<00:02:03.310> so<00:02:03.340> long<00:02:03.550> to<00:02:04.000> use<00:02:04.420> these 00:02:05.370 --> 00:02:05.380 align:start position:0% why does it take so long to use these 00:02:05.380 --> 00:02:09.240 align:start position:0% why does it take so long to use these applications<00:02:07.590> on<00:02:08.590> top<00:02:08.619> of<00:02:08.890> that<00:02:08.979> we're<00:02:09.129> also 00:02:09.240 --> 00:02:09.250 align:start position:0% applications on top of that we're also 00:02:09.250 --> 00:02:10.889 align:start position:0% applications on top of that we're also building<00:02:09.550> somewhat<00:02:09.970> in<00:02:10.090> a<00:02:10.149> desert<00:02:10.360> we<00:02:10.750> don't 00:02:10.889 --> 00:02:10.899 align:start position:0% building somewhat in a desert we don't 00:02:10.899 --> 00:02:13.080 align:start position:0% building somewhat in a desert we don't really<00:02:11.019> have<00:02:11.230> a<00:02:11.260> lot<00:02:11.409> of<00:02:11.530> user<00:02:11.709> data<00:02:11.910> to<00:02:12.910> pull 00:02:13.080 --> 00:02:13.090 align:start position:0% really have a lot of user data to pull 00:02:13.090 --> 00:02:17.600 align:start position:0% really have a lot of user data to pull from<00:02:13.210> to<00:02:13.300> make<00:02:13.600> many<00:02:14.290> design<00:02:14.800> decisions<00:02:15.390> so 00:02:17.600 --> 00:02:17.610 align:start position:0% from to make many design decisions so 00:02:17.610 --> 00:02:20.940 align:start position:0% from to make many design decisions so the<00:02:18.900> and<00:02:19.900> then<00:02:20.080> another<00:02:20.290> thing<00:02:20.530> is<00:02:20.680> this<00:02:20.830> is 00:02:20.940 --> 00:02:20.950 align:start position:0% the and then another thing is this is 00:02:20.950 --> 00:02:22.649 align:start position:0% the and then another thing is this is just<00:02:20.980> another<00:02:21.310> sort<00:02:21.610> of<00:02:21.670> example<00:02:22.000> where<00:02:22.540> we 00:02:22.649 --> 00:02:22.659 align:start position:0% just another sort of example where we 00:02:22.659 --> 00:02:25.649 align:start position:0% just another sort of example where we are<00:02:22.810> aetherium<00:02:23.739> has<00:02:24.069> about<00:02:24.310> 0.01<00:02:25.090> percent<00:02:25.299> of 00:02:25.649 --> 00:02:25.659 align:start position:0% are aetherium has about 0.01 percent of 00:02:25.659 --> 00:02:27.509 align:start position:0% are aetherium has about 0.01 percent of the<00:02:26.230> user<00:02:26.409> base<00:02:26.590> of<00:02:26.769> facebook<00:02:27.099> that's<00:02:27.189> the 00:02:27.509 --> 00:02:27.519 align:start position:0% the user base of facebook that's the 00:02:27.519 --> 00:02:29.910 align:start position:0% the user base of facebook that's the daily<00:02:28.060> activity<00:02:28.420> users<00:02:28.780> or<00:02:29.140> monthly<00:02:29.379> active 00:02:29.910 --> 00:02:29.920 align:start position:0% daily activity users or monthly active 00:02:29.920 --> 00:02:31.860 align:start position:0% daily activity users or monthly active users<00:02:29.950> on<00:02:30.459> meta<00:02:31.060> mask<00:02:31.299> divided<00:02:31.750> by<00:02:31.810> the 00:02:31.860 --> 00:02:31.870 align:start position:0% users on meta mask divided by the 00:02:31.870 --> 00:02:34.619 align:start position:0% users on meta mask divided by the monthly<00:02:32.560> active<00:02:32.799> at<00:02:32.890> Facebook<00:02:33.189> and<00:02:33.370> then<00:02:33.629> need 00:02:34.619 --> 00:02:34.629 align:start position:0% monthly active at Facebook and then need 00:02:34.629 --> 00:02:36.210 align:start position:0% monthly active at Facebook and then need alternatives<00:02:35.200> are<00:02:35.319> sort<00:02:35.739> of<00:02:35.769> significantly 00:02:36.210 --> 00:02:36.220 align:start position:0% alternatives are sort of significantly 00:02:36.220 --> 00:02:37.770 align:start position:0% alternatives are sort of significantly ahead<00:02:36.310> of<00:02:36.519> that<00:02:36.640> with<00:02:37.180> the<00:02:37.299> beyond<00:02:37.540> burger 00:02:37.770 --> 00:02:37.780 align:start position:0% ahead of that with the beyond burger 00:02:37.780 --> 00:02:39.000 align:start position:0% ahead of that with the beyond burger narrative<00:02:38.110> they've<00:02:38.230> kind<00:02:38.440> of<00:02:38.470> they've<00:02:38.799> gained 00:02:39.000 --> 00:02:39.010 align:start position:0% narrative they've kind of they've gained 00:02:39.010 --> 00:02:42.000 align:start position:0% narrative they've kind of they've gained a<00:02:39.099> half<00:02:40.000> of<00:02:40.150> a<00:02:40.239> percentage<00:02:40.599> of<00:02:40.720> the<00:02:40.840> market<00:02:41.010> of 00:02:42.000 --> 00:02:42.010 align:start position:0% a half of a percentage of the market of 00:02:42.010 --> 00:02:43.740 align:start position:0% a half of a percentage of the market of the<00:02:42.159> meat<00:02:42.310> industry<00:02:42.430> which<00:02:42.940> is<00:02:43.090> pretty<00:02:43.599> great 00:02:43.740 --> 00:02:43.750 align:start position:0% the meat industry which is pretty great 00:02:43.750 --> 00:02:45.780 align:start position:0% the meat industry which is pretty great so<00:02:43.989> we<00:02:44.230> needs<00:02:44.409> a<00:02:44.500> 50x<00:02:45.220> dough<00:02:45.310> user<00:02:45.519> base<00:02:45.640> in 00:02:45.780 --> 00:02:45.790 align:start position:0% so we needs a 50x dough user base in 00:02:45.790 --> 00:02:49.280 align:start position:0% so we needs a 50x dough user base in order<00:02:46.000> to<00:02:46.599> match<00:02:46.840> what<00:02:47.290> they've<00:02:47.439> done<00:02:47.620> there 00:02:49.280 --> 00:02:49.290 align:start position:0% order to match what they've done there 00:02:49.290 --> 00:02:51.479 align:start position:0% order to match what they've done there so<00:02:50.290> again<00:02:50.530> they<00:02:50.680> be<00:02:50.769> on<00:02:50.859> burger<00:02:51.159> a<00:02:51.190> narrative 00:02:51.479 --> 00:02:51.489 align:start position:0% so again they be on burger a narrative 00:02:51.489 --> 00:02:53.130 align:start position:0% so again they be on burger a narrative they<00:02:52.090> kind<00:02:52.269> of<00:02:52.299> broke<00:02:52.420> through<00:02:52.629> that<00:02:52.720> stigma 00:02:53.130 --> 00:02:53.140 align:start position:0% they kind of broke through that stigma 00:02:53.140 --> 00:02:57.539 align:start position:0% they kind of broke through that stigma of<00:02:54.030> meat<00:02:55.030> of<00:02:55.840> imitating<00:02:56.739> that<00:02:56.829> meat<00:02:57.069> flavor<00:02:57.370> so 00:02:57.539 --> 00:02:57.549 align:start position:0% of meat of imitating that meat flavor so 00:02:57.549 --> 00:02:59.399 align:start position:0% of meat of imitating that meat flavor so you<00:02:57.579> can<00:02:57.790> be<00:02:58.030> a<00:02:58.060> mediator<00:02:58.389> go<00:02:59.019> to<00:02:59.109> Burger<00:02:59.379> King 00:02:59.399 --> 00:02:59.409 align:start position:0% you can be a mediator go to Burger King 00:02:59.409 --> 00:03:01.199 align:start position:0% you can be a mediator go to Burger King and<00:02:59.590> buy<00:03:00.040> a<00:03:00.069> beyond<00:03:00.370> burger<00:03:00.670> and<00:03:00.819> be<00:03:00.970> as 00:03:01.199 --> 00:03:01.209 align:start position:0% and buy a beyond burger and be as 00:03:01.209 --> 00:03:03.869 align:start position:0% and buy a beyond burger and be as satisfied<00:03:01.720> and<00:03:01.900> it<00:03:02.560> sort<00:03:03.370> of<00:03:03.400> points<00:03:03.639> to<00:03:03.760> the 00:03:03.869 --> 00:03:03.879 align:start position:0% satisfied and it sort of points to the 00:03:03.879 --> 00:03:05.640 align:start position:0% satisfied and it sort of points to the fact<00:03:04.030> that<00:03:04.120> users<00:03:04.480> will<00:03:04.900> choose<00:03:05.230> holistic 00:03:05.640 --> 00:03:05.650 align:start position:0% fact that users will choose holistic 00:03:05.650 --> 00:03:07.349 align:start position:0% fact that users will choose holistic solutions<00:03:06.069> if<00:03:06.370> it's<00:03:06.790> convenient<00:03:07.269> and 00:03:07.349 --> 00:03:07.359 align:start position:0% solutions if it's convenient and 00:03:07.359 --> 00:03:09.720 align:start position:0% solutions if it's convenient and comfortable<00:03:07.540> for<00:03:07.959> them<00:03:08.069> and<00:03:09.069> that's<00:03:09.250> sort<00:03:09.639> of 00:03:09.720 --> 00:03:09.730 align:start position:0% comfortable for them and that's sort of 00:03:09.730 --> 00:03:11.460 align:start position:0% comfortable for them and that's sort of what<00:03:09.849> we<00:03:09.970> need<00:03:10.180> to<00:03:10.299> get<00:03:10.450> to<00:03:10.629> for<00:03:11.170> aetherium 00:03:11.460 --> 00:03:11.470 align:start position:0% what we need to get to for aetherium 00:03:11.470 --> 00:03:13.740 align:start position:0% what we need to get to for aetherium applications<00:03:12.069> to<00:03:12.220> actually<00:03:12.489> be<00:03:12.609> adopted<00:03:13.599> by 00:03:13.740 --> 00:03:13.750 align:start position:0% applications to actually be adopted by 00:03:13.750 --> 00:03:17.369 align:start position:0% applications to actually be adopted by end-users<00:03:14.440> we<00:03:14.560> can't<00:03:14.799> sort<00:03:15.040> of<00:03:15.129> shove<00:03:16.379> this 00:03:17.369 --> 00:03:17.379 align:start position:0% end-users we can't sort of shove this 00:03:17.379 --> 00:03:19.140 align:start position:0% end-users we can't sort of shove this sort<00:03:17.920> of<00:03:17.950> decentralisation<00:03:18.459> down<00:03:18.819> people's 00:03:19.140 --> 00:03:19.150 align:start position:0% sort of decentralisation down people's 00:03:19.150 --> 00:03:23.699 align:start position:0% sort of decentralisation down people's throats<00:03:19.389> right<00:03:19.599> it's<00:03:19.810> not<00:03:20.549> not<00:03:21.549> as<00:03:21.669> useful<00:03:22.709> and 00:03:23.699 --> 00:03:23.709 align:start position:0% throats right it's not not as useful and 00:03:23.709 --> 00:03:25.619 align:start position:0% throats right it's not not as useful and so<00:03:24.250> the<00:03:24.459> first<00:03:24.609> I<00:03:24.849> think<00:03:24.879> the<00:03:25.060> first<00:03:25.120> real 00:03:25.619 --> 00:03:25.629 align:start position:0% so the first I think the first real 00:03:25.629 --> 00:03:27.089 align:start position:0% so the first I think the first real iteration<00:03:26.109> of<00:03:26.199> this<00:03:26.319> was<00:03:26.500> the<00:03:26.620> burner<00:03:26.769> wallet 00:03:27.089 --> 00:03:27.099 align:start position:0% iteration of this was the burner wallet 00:03:27.099 --> 00:03:29.300 align:start position:0% iteration of this was the burner wallet with<00:03:27.609> Austin<00:03:27.940> Griffith<00:03:28.239> he<00:03:28.449> kind<00:03:28.629> of<00:03:28.690> made 00:03:29.300 --> 00:03:29.310 align:start position:0% with Austin Griffith he kind of made 00:03:29.310 --> 00:03:32.069 align:start position:0% with Austin Griffith he kind of made onboarding<00:03:30.310> a<00:03:30.430> thing<00:03:30.790> a<00:03:31.120> teeth<00:03:31.419> Denver<00:03:31.840> in 00:03:32.069 --> 00:03:32.079 align:start position:0% onboarding a thing a teeth Denver in 00:03:32.079 --> 00:03:34.319 align:start position:0% onboarding a thing a teeth Denver in 2019<00:03:32.769> that<00:03:32.980> was<00:03:33.069> the<00:03:33.160> largest<00:03:33.329> point-of-sale 00:03:34.319 --> 00:03:34.329 align:start position:0% 2019 that was the largest point-of-sale 00:03:34.329 --> 00:03:35.520 align:start position:0% 2019 that was the largest point-of-sale system<00:03:34.660> that<00:03:34.780> has<00:03:34.870> been<00:03:35.049> spun<00:03:35.260> up<00:03:35.379> in<00:03:35.470> a 00:03:35.520 --> 00:03:35.530 align:start position:0% system that has been spun up in a 00:03:35.530 --> 00:03:39.089 align:start position:0% system that has been spun up in a theorem<00:03:35.829> ecosystem<00:03:36.449> since<00:03:37.449> inception<00:03:38.099> it 00:03:39.089 --> 00:03:39.099 align:start position:0% theorem ecosystem since inception it 00:03:39.099 --> 00:03:42.180 align:start position:0% theorem ecosystem since inception it created<00:03:39.639> instant<00:03:40.239> value<00:03:40.709> for<00:03:41.709> people<00:03:42.069> that 00:03:42.180 --> 00:03:42.190 align:start position:0% created instant value for people that 00:03:42.190 --> 00:03:43.439 align:start position:0% created instant value for people that were<00:03:42.280> on<00:03:42.400> the<00:03:42.519> ground<00:03:42.669> that<00:03:42.849> are<00:03:42.940> wanting<00:03:43.359> to 00:03:43.439 --> 00:03:43.449 align:start position:0% were on the ground that are wanting to 00:03:43.449 --> 00:03:47.610 align:start position:0% were on the ground that are wanting to use<00:03:43.569> that<00:03:43.599> network<00:03:44.519> and<00:03:45.519> so<00:03:46.120> how<00:03:46.599> do<00:03:47.470> you 00:03:47.610 --> 00:03:47.620 align:start position:0% use that network and so how do you 00:03:47.620 --> 00:03:50.250 align:start position:0% use that network and so how do you onboard<00:03:48.030> well<00:03:49.030> you<00:03:49.209> have<00:03:49.329> to<00:03:49.449> inspire<00:03:49.989> trust 00:03:50.250 --> 00:03:50.260 align:start position:0% onboard well you have to inspire trust 00:03:50.260 --> 00:03:52.589 align:start position:0% onboard well you have to inspire trust within<00:03:50.650> your<00:03:50.769> user<00:03:50.980> base<00:03:51.069> and<00:03:51.400> it<00:03:52.090> also<00:03:52.239> has<00:03:52.480> to 00:03:52.589 --> 00:03:52.599 align:start position:0% within your user base and it also has to 00:03:52.599 --> 00:03:56.309 align:start position:0% within your user base and it also has to be<00:03:52.629> efficient<00:03:53.139> and<00:03:53.949> convenient<00:03:54.220> right<00:03:55.319> the 00:03:56.309 --> 00:03:56.319 align:start position:0% be efficient and convenient right the 00:03:56.319 --> 00:03:59.569 align:start position:0% be efficient and convenient right the old<00:03:56.500> paradigm<00:03:56.829> of<00:03:57.099> key<00:03:57.310> management<00:03:57.669> is 00:03:59.569 --> 00:03:59.579 align:start position:0% old paradigm of key management is 00:03:59.579 --> 00:04:04.500 align:start position:0% old paradigm of key management is challenging<00:04:00.579> I<00:04:01.650> see<00:04:02.650> the<00:04:02.829> future<00:04:02.980> as<00:04:03.510> key 00:04:04.500 --> 00:04:04.510 align:start position:0% challenging I see the future as key 00:04:04.510 --> 00:04:06.119 align:start position:0% challenging I see the future as key management<00:04:04.840> private<00:04:05.319> key<00:04:05.409> management<00:04:05.709> as 00:04:06.119 --> 00:04:06.129 align:start position:0% management private key management as 00:04:06.129 --> 00:04:08.909 align:start position:0% management private key management as being<00:04:06.340> sort<00:04:06.669> of<00:04:06.730> sub-sect<00:04:07.239> to<00:04:07.449> a<00:04:08.260> new<00:04:08.590> contract 00:04:08.909 --> 00:04:08.919 align:start position:0% being sort of sub-sect to a new contract 00:04:08.919 --> 00:04:11.270 align:start position:0% being sort of sub-sect to a new contract based<00:04:09.220> management<00:04:09.699> system<00:04:10.000> my<00:04:10.540> mom<00:04:10.780> won't 00:04:11.270 --> 00:04:11.280 align:start position:0% based management system my mom won't 00:04:11.280 --> 00:04:14.099 align:start position:0% based management system my mom won't likely<00:04:12.280> ever<00:04:12.459> download<00:04:12.909> a<00:04:12.940> private<00:04:13.329> key<00:04:13.449> most 00:04:14.099 --> 00:04:14.109 align:start position:0% likely ever download a private key most 00:04:14.109 --> 00:04:17.430 align:start position:0% likely ever download a private key most likely<00:04:14.440> right<00:04:15.269> the<00:04:16.269> new<00:04:16.810> paradigm<00:04:17.169> that<00:04:17.199> we're 00:04:17.430 --> 00:04:17.440 align:start position:0% likely right the new paradigm that we're 00:04:17.440 --> 00:04:19.199 align:start position:0% likely right the new paradigm that we're suggesting<00:04:17.799> and<00:04:17.919> beyond<00:04:18.099> burner<00:04:18.310> is<00:04:18.579> to<00:04:19.060> use 00:04:19.199 --> 00:04:19.209 align:start position:0% suggesting and beyond burner is to use 00:04:19.209 --> 00:04:21.930 align:start position:0% suggesting and beyond burner is to use these<00:04:19.449> burner<00:04:20.320> wallet<00:04:20.739> keys<00:04:20.979> or<00:04:21.340> ephemeral 00:04:21.930 --> 00:04:21.940 align:start position:0% these burner wallet keys or ephemeral 00:04:21.940 --> 00:04:24.839 align:start position:0% these burner wallet keys or ephemeral keys<00:04:22.120> with<00:04:22.900> a<00:04:22.930> contract<00:04:23.440> account<00:04:23.740> and<00:04:24.070> so<00:04:24.729> it's 00:04:24.839 --> 00:04:24.849 align:start position:0% keys with a contract account and so it's 00:04:24.849 --> 00:04:25.980 align:start position:0% keys with a contract account and so it's essentially<00:04:25.150> a<00:04:25.210> multi<00:04:25.479> sitting<00:04:25.690> that<00:04:25.780> you<00:04:25.870> can 00:04:25.980 --> 00:04:25.990 align:start position:0% essentially a multi sitting that you can 00:04:25.990 --> 00:04:27.629 align:start position:0% essentially a multi sitting that you can control<00:04:26.289> funds<00:04:26.770> with<00:04:27.219> a<00:04:27.250> number<00:04:27.520> of<00:04:27.550> different 00:04:27.629 --> 00:04:27.639 align:start position:0% control funds with a number of different 00:04:27.639 --> 00:04:30.360 align:start position:0% control funds with a number of different keys<00:04:28.090> and<00:04:28.450> all<00:04:29.380> of<00:04:29.500> those 00:04:30.360 --> 00:04:30.370 align:start position:0% keys and all of those 00:04:30.370 --> 00:04:34.350 align:start position:0% keys and all of those are<00:04:31.680> potentially<00:04:32.680> temporary<00:04:33.130> right<00:04:33.850> so 00:04:34.350 --> 00:04:34.360 align:start position:0% are potentially temporary right so 00:04:34.360 --> 00:04:35.610 align:start position:0% are potentially temporary right so there's<00:04:34.479> essentially<00:04:34.840> there's<00:04:35.410> sort<00:04:35.560> of 00:04:35.610 --> 00:04:35.620 align:start position:0% there's essentially there's sort of 00:04:35.620 --> 00:04:36.960 align:start position:0% there's essentially there's sort of burner<00:04:35.830> keys<00:04:36.100> that<00:04:36.190> are<00:04:36.250> tied<00:04:36.490> to<00:04:36.520> it<00:04:36.699> to<00:04:36.940> a 00:04:36.960 --> 00:04:36.970 align:start position:0% burner keys that are tied to it to a 00:04:36.970 --> 00:04:40.650 align:start position:0% burner keys that are tied to it to a contract<00:04:38.550> this<00:04:39.550> is<00:04:39.729> a<00:04:39.940> design<00:04:40.210> that's<00:04:40.389> really 00:04:40.650 --> 00:04:40.660 align:start position:0% contract this is a design that's really 00:04:40.660 --> 00:04:42.300 align:start position:0% contract this is a design that's really been<00:04:40.840> pioneered<00:04:41.320> somewhat<00:04:41.740> by<00:04:41.860> James<00:04:42.070> Young 00:04:42.300 --> 00:04:42.310 align:start position:0% been pioneered somewhat by James Young 00:04:42.310 --> 00:04:44.610 align:start position:0% been pioneered somewhat by James Young and<00:04:43.270> this<00:04:43.510> is<00:04:43.690> sort<00:04:43.990> of<00:04:44.020> a<00:04:44.110> quote<00:04:44.290> from<00:04:44.470> hem 00:04:44.610 --> 00:04:44.620 align:start position:0% and this is sort of a quote from hem 00:04:44.620 --> 00:04:46.409 align:start position:0% and this is sort of a quote from hem programmable<00:04:45.070> money<00:04:45.220> deserves<00:04:45.760> programmable 00:04:46.409 --> 00:04:46.419 align:start position:0% programmable money deserves programmable 00:04:46.419 --> 00:04:50.730 align:start position:0% programmable money deserves programmable access<00:04:47.190> which<00:04:48.190> I<00:04:48.460> fully<00:04:49.389> agree<00:04:49.780> and<00:04:50.199> I<00:04:50.560> think 00:04:50.730 --> 00:04:50.740 align:start position:0% access which I fully agree and I think 00:04:50.740 --> 00:04:53.270 align:start position:0% access which I fully agree and I think it's<00:04:50.860> a<00:04:51.060> pretty<00:04:52.060> sort<00:04:52.419> of<00:04:52.510> exciting<00:04:52.900> new 00:04:53.270 --> 00:04:53.280 align:start position:0% it's a pretty sort of exciting new 00:04:53.280 --> 00:04:56.610 align:start position:0% it's a pretty sort of exciting new frontier<00:04:54.280> to<00:04:54.970> be<00:04:55.060> developed<00:04:55.419> and<00:04:56.229> so<00:04:56.380> why 00:04:56.610 --> 00:04:56.620 align:start position:0% frontier to be developed and so why 00:04:56.620 --> 00:04:58.110 align:start position:0% frontier to be developed and so why beyond<00:04:56.949> burner<00:04:57.160> the<00:04:57.310> burner<00:04:57.340> wallet<00:04:57.760> is<00:04:57.910> an 00:04:58.110 --> 00:04:58.120 align:start position:0% beyond burner the burner wallet is an 00:04:58.120 --> 00:05:00.570 align:start position:0% beyond burner the burner wallet is an instance<00:04:58.540> of<00:04:58.720> the<00:04:59.169> beyond<00:04:59.470> Berger<00:04:59.800> narrative 00:05:00.570 --> 00:05:00.580 align:start position:0% instance of the beyond Berger narrative 00:05:00.580 --> 00:05:02.250 align:start position:0% instance of the beyond Berger narrative and<00:05:00.850> the<00:05:00.940> success<00:05:01.270> of<00:05:01.389> the<00:05:01.479> out<00:05:01.600> beyond<00:05:01.900> Berger 00:05:02.250 --> 00:05:02.260 align:start position:0% and the success of the out beyond Berger 00:05:02.260 --> 00:05:07.620 align:start position:0% and the success of the out beyond Berger within<00:05:03.130> the<00:05:03.220> etherium<00:05:03.610> ecosystem<00:05:05.370> so<00:05:06.570> why<00:05:07.570> do 00:05:07.620 --> 00:05:07.630 align:start position:0% within the etherium ecosystem so why do 00:05:07.630 --> 00:05:09.420 align:start position:0% within the etherium ecosystem so why do we<00:05:07.750> care<00:05:08.050> about<00:05:08.110> mass<00:05:08.410> adoption<00:05:08.650> I<00:05:09.010> think<00:05:09.220> we 00:05:09.420 --> 00:05:09.430 align:start position:0% we care about mass adoption I think we 00:05:09.430 --> 00:05:10.740 align:start position:0% we care about mass adoption I think we need<00:05:09.580> to<00:05:09.669> talk<00:05:09.940> a<00:05:09.970> little<00:05:10.180> bit<00:05:10.300> about<00:05:10.330> the<00:05:10.570> city 00:05:10.740 --> 00:05:10.750 align:start position:0% need to talk a little bit about the city 00:05:10.750 --> 00:05:13.020 align:start position:0% need to talk a little bit about the city was<00:05:10.870> the<00:05:11.080> application<00:05:11.470> layer<00:05:12.030> the 00:05:13.020 --> 00:05:13.030 align:start position:0% was the application layer the 00:05:13.030 --> 00:05:14.400 align:start position:0% was the application layer the application<00:05:13.060> layer<00:05:13.600> is<00:05:13.750> where<00:05:13.960> value<00:05:14.350> is 00:05:14.400 --> 00:05:14.410 align:start position:0% application layer is where value is 00:05:14.410 --> 00:05:18.390 align:start position:0% application layer is where value is delivered<00:05:14.919> to<00:05:15.400> end-users<00:05:15.750> and<00:05:17.100> so<00:05:18.100> that's 00:05:18.390 --> 00:05:18.400 align:start position:0% delivered to end-users and so that's 00:05:18.400 --> 00:05:20.100 align:start position:0% delivered to end-users and so that's really<00:05:19.150> fundamentally<00:05:19.630> important<00:05:19.930> if<00:05:20.020> we 00:05:20.100 --> 00:05:20.110 align:start position:0% really fundamentally important if we 00:05:20.110 --> 00:05:22.469 align:start position:0% really fundamentally important if we don't<00:05:20.289> have<00:05:20.440> that<00:05:20.800> value<00:05:21.520> delivered<00:05:22.060> all<00:05:22.270> of 00:05:22.469 --> 00:05:22.479 align:start position:0% don't have that value delivered all of 00:05:22.479 --> 00:05:23.520 align:start position:0% don't have that value delivered all of the<00:05:22.750> work<00:05:22.870> that<00:05:22.900> we're<00:05:23.139> doing<00:05:23.169> in<00:05:23.350> the<00:05:23.410> back 00:05:23.520 --> 00:05:23.530 align:start position:0% the work that we're doing in the back 00:05:23.530 --> 00:05:25.980 align:start position:0% the work that we're doing in the back end<00:05:23.770> with<00:05:24.010> scaling<00:05:24.370> it's<00:05:24.490> charting<00:05:24.970> etc<00:05:25.330> will 00:05:25.980 --> 00:05:25.990 align:start position:0% end with scaling it's charting etc will 00:05:25.990 --> 00:05:27.420 align:start position:0% end with scaling it's charting etc will go<00:05:26.110> to<00:05:26.169> waste<00:05:26.350> or<00:05:26.560> it's<00:05:26.860> just<00:05:27.070> kind<00:05:27.220> of<00:05:27.250> we're 00:05:27.420 --> 00:05:27.430 align:start position:0% go to waste or it's just kind of we're 00:05:27.430 --> 00:05:30.270 align:start position:0% go to waste or it's just kind of we're developing<00:05:27.789> in<00:05:27.910> a<00:05:27.970> silo<00:05:28.620> so<00:05:29.620> what<00:05:30.100> does<00:05:30.190> it 00:05:30.270 --> 00:05:30.280 align:start position:0% developing in a silo so what does it 00:05:30.280 --> 00:05:31.650 align:start position:0% developing in a silo so what does it look<00:05:30.340> like<00:05:30.460> today<00:05:30.669> well<00:05:31.000> it's<00:05:31.120> mainly<00:05:31.240> defy 00:05:31.650 --> 00:05:31.660 align:start position:0% look like today well it's mainly defy 00:05:31.660 --> 00:05:33.840 align:start position:0% look like today well it's mainly defy right<00:05:32.169> the<00:05:32.680> killer<00:05:32.919> app<00:05:33.130> of<00:05:33.310> aetherium<00:05:33.699> is 00:05:33.840 --> 00:05:33.850 align:start position:0% right the killer app of aetherium is 00:05:33.850 --> 00:05:37.650 align:start position:0% right the killer app of aetherium is like<00:05:34.000> maker<00:05:34.360> and<00:05:34.780> I<00:05:35.229> SEOs<00:05:35.940> it's<00:05:36.940> it's<00:05:37.330> you<00:05:37.630> know 00:05:37.650 --> 00:05:37.660 align:start position:0% like maker and I SEOs it's it's you know 00:05:37.660 --> 00:05:39.540 align:start position:0% like maker and I SEOs it's it's you know it's<00:05:38.260> it's<00:05:38.440> pretty<00:05:38.710> maybe<00:05:39.070> prediction 00:05:39.540 --> 00:05:39.550 align:start position:0% it's it's pretty maybe prediction 00:05:39.550 --> 00:05:40.650 align:start position:0% it's it's pretty maybe prediction markets<00:05:39.849> but<00:05:39.940> that<00:05:40.120> hasn't<00:05:40.300> really<00:05:40.479> even 00:05:40.650 --> 00:05:40.660 align:start position:0% markets but that hasn't really even 00:05:40.660 --> 00:05:43.800 align:start position:0% markets but that hasn't really even really<00:05:41.440> caught<00:05:41.650> on<00:05:41.800> yet<00:05:42.330> so<00:05:43.330> mainly<00:05:43.510> it's<00:05:43.690> like 00:05:43.800 --> 00:05:43.810 align:start position:0% really caught on yet so mainly it's like 00:05:43.810 --> 00:05:46.580 align:start position:0% really caught on yet so mainly it's like you're<00:05:44.050> trying<00:05:44.200> to<00:05:44.349> make<00:05:44.530> and<00:05:44.860> save<00:05:45.070> money 00:05:46.580 --> 00:05:46.590 align:start position:0% you're trying to make and save money 00:05:46.590 --> 00:05:50.730 align:start position:0% you're trying to make and save money the<00:05:47.590> future<00:05:48.220> of<00:05:48.490> aetherium<00:05:49.090> it<00:05:49.630> was<00:05:50.139> is<00:05:50.710> a 00:05:50.730 --> 00:05:50.740 align:start position:0% the future of aetherium it was is a 00:05:50.740 --> 00:05:51.870 align:start position:0% the future of aetherium it was is a different<00:05:51.190> like<00:05:51.370> we<00:05:51.639> have<00:05:51.729> a<00:05:51.760> lot<00:05:51.849> of 00:05:51.870 --> 00:05:51.880 align:start position:0% different like we have a lot of 00:05:51.880 --> 00:05:54.060 align:start position:0% different like we have a lot of idealistic<00:05:52.349> idealistic<00:05:53.349> the<00:05:53.590> philosophies 00:05:54.060 --> 00:05:54.070 align:start position:0% idealistic idealistic the philosophies 00:05:54.070 --> 00:05:56.040 align:start position:0% idealistic idealistic the philosophies around<00:05:54.340> the<00:05:54.400> future<00:05:54.729> and<00:05:55.090> your<00:05:55.300> Dean<00:05:55.510> had<00:05:56.020> a 00:05:56.040 --> 00:05:56.050 align:start position:0% around the future and your Dean had a 00:05:56.050 --> 00:05:59.189 align:start position:0% around the future and your Dean had a nice<00:05:56.229> little<00:05:56.410> Twitter<00:05:57.570> rampage<00:05:58.570> about<00:05:58.840> about 00:05:59.189 --> 00:05:59.199 align:start position:0% nice little Twitter rampage about about 00:05:59.199 --> 00:06:01.830 align:start position:0% nice little Twitter rampage about about this<00:05:59.380> obviously<00:05:59.860> so<00:06:00.099> what<00:06:00.419> trolling<00:06:01.419> the<00:06:01.570> idea 00:06:01.830 --> 00:06:01.840 align:start position:0% this obviously so what trolling the idea 00:06:01.840 --> 00:06:04.379 align:start position:0% this obviously so what trolling the idea of<00:06:01.930> this<00:06:02.020> but<00:06:02.440> a<00:06:02.650> lot<00:06:02.949> of<00:06:02.979> I<00:06:03.160> SEOs<00:06:03.550> did<00:06:04.030> come<00:06:04.270> out 00:06:04.379 --> 00:06:04.389 align:start position:0% of this but a lot of I SEOs did come out 00:06:04.389 --> 00:06:06.540 align:start position:0% of this but a lot of I SEOs did come out and<00:06:04.449> 2017<00:06:05.050> very<00:06:05.440> serious<00:06:05.800> about<00:06:05.889> the<00:06:06.220> menteng 00:06:06.540 --> 00:06:06.550 align:start position:0% and 2017 very serious about the menteng 00:06:06.550 --> 00:06:07.920 align:start position:0% and 2017 very serious about the menteng new<00:06:06.669> business<00:06:06.970> models<00:06:07.300> around<00:06:07.330> blockchain 00:06:07.920 --> 00:06:07.930 align:start position:0% new business models around blockchain 00:06:07.930 --> 00:06:10.290 align:start position:0% new business models around blockchain around<00:06:08.500> an<00:06:08.590> immutable<00:06:08.979> ledger<00:06:09.340> system<00:06:09.789> to 00:06:10.290 --> 00:06:10.300 align:start position:0% around an immutable ledger system to 00:06:10.300 --> 00:06:13.589 align:start position:0% around an immutable ledger system to actually<00:06:10.479> like<00:06:10.720> solve<00:06:11.610> real<00:06:12.610> world<00:06:13.060> problems 00:06:13.589 --> 00:06:13.599 align:start position:0% actually like solve real world problems 00:06:13.599 --> 00:06:17.460 align:start position:0% actually like solve real world problems we<00:06:14.440> also<00:06:14.590> have<00:06:14.770> the<00:06:14.860> unbanked<00:06:15.729> essentially<00:06:16.660> we 00:06:17.460 --> 00:06:17.470 align:start position:0% we also have the unbanked essentially we 00:06:17.470 --> 00:06:18.629 align:start position:0% we also have the unbanked essentially we have<00:06:17.620> the<00:06:17.740> potential<00:06:18.070> to<00:06:18.340> create<00:06:18.430> better 00:06:18.629 --> 00:06:18.639 align:start position:0% have the potential to create better 00:06:18.639 --> 00:06:21.650 align:start position:0% have the potential to create better systems<00:06:19.150> if<00:06:19.389> we<00:06:19.960> gain<00:06:20.139> this<00:06:20.289> adoption<00:06:20.800> right 00:06:21.650 --> 00:06:21.660 align:start position:0% systems if we gain this adoption right 00:06:21.660 --> 00:06:24.089 align:start position:0% systems if we gain this adoption right and<00:06:22.660> so<00:06:22.960> what<00:06:23.080> does<00:06:23.169> user<00:06:23.500> adoption<00:06:23.680> look<00:06:23.919> like 00:06:24.089 --> 00:06:24.099 align:start position:0% and so what does user adoption look like 00:06:24.099 --> 00:06:26.219 align:start position:0% and so what does user adoption look like mainly<00:06:24.699> makes<00:06:25.000> money<00:06:25.180> creates<00:06:25.660> better 00:06:26.219 --> 00:06:26.229 align:start position:0% mainly makes money creates better 00:06:26.229 --> 00:06:28.500 align:start position:0% mainly makes money creates better systems<00:06:26.650> and<00:06:27.580> that<00:06:27.729> could<00:06:27.910> also<00:06:28.030> mean<00:06:28.300> like 00:06:28.500 --> 00:06:28.510 align:start position:0% systems and that could also mean like 00:06:28.510 --> 00:06:31.020 align:start position:0% systems and that could also mean like providing<00:06:29.139> knowledge<00:06:29.590> or<00:06:30.099> comfort<00:06:30.699> or<00:06:30.849> like 00:06:31.020 --> 00:06:31.030 align:start position:0% providing knowledge or comfort or like 00:06:31.030 --> 00:06:33.659 align:start position:0% providing knowledge or comfort or like social<00:06:31.389> belonging<00:06:32.190> dopamine<00:06:33.190> to<00:06:33.430> the 00:06:33.659 --> 00:06:33.669 align:start position:0% social belonging dopamine to the 00:06:33.669 --> 00:06:35.370 align:start position:0% social belonging dopamine to the end-user<00:06:34.060> like<00:06:34.240> all<00:06:34.419> of<00:06:34.510> that<00:06:34.539> stuff<00:06:34.870> is<00:06:35.020> is 00:06:35.370 --> 00:06:35.380 align:start position:0% end-user like all of that stuff is is 00:06:35.380 --> 00:06:37.650 align:start position:0% end-user like all of that stuff is is essentially<00:06:35.949> value<00:06:36.310> for<00:06:36.520> them<00:06:36.639> and<00:06:36.940> fun<00:06:37.330> is 00:06:37.650 --> 00:06:37.660 align:start position:0% essentially value for them and fun is 00:06:37.660 --> 00:06:39.360 align:start position:0% essentially value for them and fun is also<00:06:37.960> so<00:06:38.469> we've<00:06:38.590> included<00:06:38.830> in<00:06:39.039> that<00:06:39.130> value 00:06:39.360 --> 00:06:39.370 align:start position:0% also so we've included in that value 00:06:39.370 --> 00:06:41.339 align:start position:0% also so we've included in that value proposition<00:06:39.490> potentially<00:06:40.360> and<00:06:41.080> for 00:06:41.339 --> 00:06:41.349 align:start position:0% proposition potentially and for 00:06:41.349 --> 00:06:44.250 align:start position:0% proposition potentially and for developers<00:06:42.150> if<00:06:43.150> you<00:06:43.360> get<00:06:43.719> user 00:06:44.250 --> 00:06:44.260 align:start position:0% developers if you get user 00:06:44.260 --> 00:06:45.540 align:start position:0% developers if you get user that<00:06:44.530> means<00:06:44.710> you<00:06:44.830> can<00:06:44.980> actually<00:06:45.100> make<00:06:45.370> money 00:06:45.540 --> 00:06:45.550 align:start position:0% that means you can actually make money 00:06:45.550 --> 00:06:49.110 align:start position:0% that means you can actually make money which<00:06:45.940> is<00:06:46.120> a<00:06:46.150> huge<00:06:46.420> thing<00:06:46.860> because<00:06:47.860> today<00:06:48.250> the 00:06:49.110 --> 00:06:49.120 align:start position:0% which is a huge thing because today the 00:06:49.120 --> 00:06:51.630 align:start position:0% which is a huge thing because today the money<00:06:49.360> is<00:06:49.540> really<00:06:49.750> reserved<00:06:50.110> for<00:06:50.640> exchanges 00:06:51.630 --> 00:06:51.640 align:start position:0% money is really reserved for exchanges 00:06:51.640 --> 00:06:54.450 align:start position:0% money is really reserved for exchanges right<00:06:52.270> who<00:06:52.960> no<00:06:53.260> one<00:06:53.410> is<00:06:53.620> making<00:06:53.920> real<00:06:54.220> revenue 00:06:54.450 --> 00:06:54.460 align:start position:0% right who no one is making real revenue 00:06:54.460 --> 00:06:56.730 align:start position:0% right who no one is making real revenue aside<00:06:54.730> from<00:06:54.820> exchanges<00:06:55.390> and<00:06:55.740> consultants 00:06:56.730 --> 00:06:56.740 align:start position:0% aside from exchanges and consultants 00:06:56.740 --> 00:07:00.090 align:start position:0% aside from exchanges and consultants more<00:06:57.310> or<00:06:57.370> less<00:06:57.490> right<00:06:57.850> and<00:06:58.810> so<00:06:59.230> that's<00:06:59.650> sort<00:06:59.950> of 00:07:00.090 --> 00:07:00.100 align:start position:0% more or less right and so that's sort of 00:07:00.100 --> 00:07:03.090 align:start position:0% more or less right and so that's sort of the<00:07:00.460> exciting<00:07:01.150> proposition<00:07:01.420> is<00:07:02.320> that<00:07:02.440> you 00:07:03.090 --> 00:07:03.100 align:start position:0% the exciting proposition is that you 00:07:03.100 --> 00:07:05.220 align:start position:0% the exciting proposition is that you could<00:07:03.310> make<00:07:03.610> a<00:07:03.640> sustainable<00:07:03.970> ecosystem<00:07:04.630> if 00:07:05.220 --> 00:07:05.230 align:start position:0% could make a sustainable ecosystem if 00:07:05.230 --> 00:07:06.750 align:start position:0% could make a sustainable ecosystem if you<00:07:05.350> actually<00:07:05.500> develop<00:07:05.740> systems<00:07:06.340> or 00:07:06.750 --> 00:07:06.760 align:start position:0% you actually develop systems or 00:07:06.760 --> 00:07:07.920 align:start position:0% you actually develop systems or developers<00:07:07.270> are<00:07:07.420> able<00:07:07.630> to<00:07:07.660> build 00:07:07.920 --> 00:07:07.930 align:start position:0% developers are able to build 00:07:07.930 --> 00:07:11.090 align:start position:0% developers are able to build applications<00:07:08.110> to<00:07:08.710> attract<00:07:09.250> real<00:07:09.520> end-users 00:07:11.090 --> 00:07:11.100 align:start position:0% applications to attract real end-users 00:07:11.100 --> 00:07:14.370 align:start position:0% applications to attract real end-users and<00:07:12.100> so<00:07:12.550> to<00:07:13.450> the<00:07:13.540> current<00:07:13.900> state<00:07:14.200> of 00:07:14.370 --> 00:07:14.380 align:start position:0% and so to the current state of 00:07:14.380 --> 00:07:19.020 align:start position:0% and so to the current state of development<00:07:16.290> where<00:07:17.290> are<00:07:17.410> we<00:07:17.530> so<00:07:18.370> like<00:07:18.940> I 00:07:19.020 --> 00:07:19.030 align:start position:0% development where are we so like I 00:07:19.030 --> 00:07:20.520 align:start position:0% development where are we so like I started<00:07:19.420> mentioned<00:07:19.780> earlier<00:07:20.020> we're<00:07:20.230> really 00:07:20.520 --> 00:07:20.530 align:start position:0% started mentioned earlier we're really 00:07:20.530 --> 00:07:22.980 align:start position:0% started mentioned earlier we're really focused<00:07:20.980> on<00:07:21.040> scalability<00:07:21.370> this<00:07:22.210> has<00:07:22.420> been<00:07:22.810> the 00:07:22.980 --> 00:07:22.990 align:start position:0% focused on scalability this has been the 00:07:22.990 --> 00:07:25.260 align:start position:0% focused on scalability this has been the Holy<00:07:23.140> Grail<00:07:23.410> and<00:07:23.530> this<00:07:23.650> is<00:07:23.770> probably<00:07:23.980> 90%<00:07:24.970> of 00:07:25.260 --> 00:07:25.270 align:start position:0% Holy Grail and this is probably 90% of 00:07:25.270 --> 00:07:27.510 align:start position:0% Holy Grail and this is probably 90% of the<00:07:25.360> talks<00:07:25.570> that<00:07:25.690> you've<00:07:26.020> heard<00:07:26.440> at<00:07:27.070> DEFCON 00:07:27.510 --> 00:07:27.520 align:start position:0% the talks that you've heard at DEFCON 00:07:27.520 --> 00:07:29.820 align:start position:0% the talks that you've heard at DEFCON thus<00:07:27.850> far<00:07:28.110> but<00:07:29.110> again<00:07:29.410> we're<00:07:29.590> sort<00:07:29.740> of 00:07:29.820 --> 00:07:29.830 align:start position:0% thus far but again we're sort of 00:07:29.830 --> 00:07:33.840 align:start position:0% thus far but again we're sort of building<00:07:30.190> in<00:07:30.430> a<00:07:30.760> desert<00:07:31.560> where<00:07:32.560> we're<00:07:33.460> sort<00:07:33.790> of 00:07:33.840 --> 00:07:33.850 align:start position:0% building in a desert where we're sort of 00:07:33.850 --> 00:07:34.950 align:start position:0% building in a desert where we're sort of siloed<00:07:34.240> we<00:07:34.420> don't<00:07:34.570> have<00:07:34.660> a<00:07:34.690> lot<00:07:34.840> of 00:07:34.950 --> 00:07:34.960 align:start position:0% siloed we don't have a lot of 00:07:34.960 --> 00:07:37.260 align:start position:0% siloed we don't have a lot of interaction<00:07:35.890> within<00:07:36.490> these<00:07:36.790> systems<00:07:36.970> that 00:07:37.260 --> 00:07:37.270 align:start position:0% interaction within these systems that 00:07:37.270 --> 00:07:41.190 align:start position:0% interaction within these systems that were<00:07:37.390> that<00:07:37.660> were<00:07:37.920> coming<00:07:38.920> up<00:07:38.950> with<00:07:39.130> and<00:07:40.200> even 00:07:41.190 --> 00:07:41.200 align:start position:0% were that were coming up with and even 00:07:41.200 --> 00:07:44.880 align:start position:0% were that were coming up with and even the<00:07:41.920> core<00:07:42.340> of<00:07:42.370> our<00:07:42.700> ecosystem<00:07:43.630> you<00:07:44.530> know<00:07:44.650> we 00:07:44.880 --> 00:07:44.890 align:start position:0% the core of our ecosystem you know we 00:07:44.890 --> 00:07:45.750 align:start position:0% the core of our ecosystem you know we still<00:07:45.040> haven't<00:07:45.250> adopted 00:07:45.750 --> 00:07:45.760 align:start position:0% still haven't adopted 00:07:45.760 --> 00:07:48.510 align:start position:0% still haven't adopted etherium<00:07:46.240> to<00:07:46.390> like<00:07:46.540> pay<00:07:46.750> for<00:07:47.020> things<00:07:47.520> within 00:07:48.510 --> 00:07:48.520 align:start position:0% etherium to like pay for things within 00:07:48.520 --> 00:07:51.060 align:start position:0% etherium to like pay for things within our<00:07:49.000> existing<00:07:49.360> infrastructures<00:07:50.170> right<00:07:50.890> and 00:07:51.060 --> 00:07:51.070 align:start position:0% our existing infrastructures right and 00:07:51.070 --> 00:07:52.590 align:start position:0% our existing infrastructures right and within<00:07:51.400> the<00:07:51.580> the<00:07:51.820> companies<00:07:52.210> who<00:07:52.330> are<00:07:52.420> really 00:07:52.590 --> 00:07:52.600 align:start position:0% within the the companies who are really 00:07:52.600 --> 00:07:55.950 align:start position:0% within the the companies who are really pioneering<00:07:52.990> this<00:07:53.940> it<00:07:54.940> would<00:07:55.180> be<00:07:55.690> great<00:07:55.930> to 00:07:55.950 --> 00:07:55.960 align:start position:0% pioneering this it would be great to 00:07:55.960 --> 00:07:58.470 align:start position:0% pioneering this it would be great to sort<00:07:56.290> of<00:07:56.380> have<00:07:57.130> a<00:07:57.160> bit<00:07:57.550> more<00:07:57.580> dogfooding<00:07:58.180> right 00:07:58.470 --> 00:07:58.480 align:start position:0% sort of have a bit more dogfooding right 00:07:58.480 --> 00:08:02.490 align:start position:0% sort of have a bit more dogfooding right for<00:07:59.290> these<00:07:59.410> things<00:07:59.680> to<00:07:59.800> happen<00:07:59.950> and<00:08:00.940> so<00:08:01.150> I<00:08:01.750> also 00:08:02.490 --> 00:08:02.500 align:start position:0% for these things to happen and so I also 00:08:02.500 --> 00:08:06.330 align:start position:0% for these things to happen and so I also propose<00:08:03.010> that<00:08:03.250> we're<00:08:04.240> sort<00:08:04.630> of<00:08:04.720> focused<00:08:05.290> on<00:08:05.560> at 00:08:06.330 --> 00:08:06.340 align:start position:0% propose that we're sort of focused on at 00:08:06.340 --> 00:08:08.060 align:start position:0% propose that we're sort of focused on at least<00:08:06.700> from<00:08:07.000> a<00:08:07.120> narrative<00:08:07.570> perspective 00:08:08.060 --> 00:08:08.070 align:start position:0% least from a narrative perspective 00:08:08.070 --> 00:08:11.130 align:start position:0% least from a narrative perspective potentially<00:08:09.090> the<00:08:10.090> back<00:08:10.300> end<00:08:10.570> more<00:08:10.900> than<00:08:11.050> we 00:08:11.130 --> 00:08:11.140 align:start position:0% potentially the back end more than we 00:08:11.140 --> 00:08:12.870 align:start position:0% potentially the back end more than we need<00:08:11.350> to<00:08:11.380> be<00:08:11.650> because<00:08:12.100> the<00:08:12.370> front<00:08:12.580> end<00:08:12.730> should 00:08:12.870 --> 00:08:12.880 align:start position:0% need to be because the front end should 00:08:12.880 --> 00:08:16.710 align:start position:0% need to be because the front end should be<00:08:12.970> driving<00:08:13.210> the<00:08:13.420> back<00:08:13.540> end<00:08:13.890> solutions<00:08:15.720> this 00:08:16.710 --> 00:08:16.720 align:start position:0% be driving the back end solutions this 00:08:16.720 --> 00:08:18.300 align:start position:0% be driving the back end solutions this is<00:08:16.780> another<00:08:16.990> quote<00:08:17.230> from<00:08:17.380> James<00:08:17.620> working<00:08:18.190> with 00:08:18.300 --> 00:08:18.310 align:start position:0% is another quote from James working with 00:08:18.310 --> 00:08:20.040 align:start position:0% is another quote from James working with him<00:08:18.460> it's<00:08:19.000> really<00:08:19.210> great<00:08:19.390> he<00:08:19.570> just<00:08:19.750> has<00:08:19.840> like<00:08:20.020> a 00:08:20.040 --> 00:08:20.050 align:start position:0% him it's really great he just has like a 00:08:20.050 --> 00:08:21.110 align:start position:0% him it's really great he just has like a lot<00:08:20.140> of<00:08:20.260> wisdom<00:08:20.470> to<00:08:20.560> share 00:08:21.110 --> 00:08:21.120 align:start position:0% lot of wisdom to share 00:08:21.120 --> 00:08:22.950 align:start position:0% lot of wisdom to share but<00:08:22.120> don't<00:08:22.300> like<00:08:22.420> the<00:08:22.510> perfect<00:08:22.660> be<00:08:22.840> the<00:08:22.870> enemy 00:08:22.950 --> 00:08:22.960 align:start position:0% but don't like the perfect be the enemy 00:08:22.960 --> 00:08:24.180 align:start position:0% but don't like the perfect be the enemy of<00:08:23.260> good 00:08:24.180 --> 00:08:24.190 align:start position:0% of good 00:08:24.190 --> 00:08:26.850 align:start position:0% of good probably<00:08:24.910> not<00:08:25.000> original<00:08:25.360> but<00:08:25.830> attributing<00:08:26.830> it 00:08:26.850 --> 00:08:26.860 align:start position:0% probably not original but attributing it 00:08:26.860 --> 00:08:30.060 align:start position:0% probably not original but attributing it to<00:08:26.920> him<00:08:27.240> so<00:08:28.240> the<00:08:28.690> current<00:08:28.960> state<00:08:29.110> twenty<00:08:29.920> five 00:08:30.060 --> 00:08:30.070 align:start position:0% to him so the current state twenty five 00:08:30.070 --> 00:08:31.590 align:start position:0% to him so the current state twenty five billion<00:08:30.340> dollars<00:08:30.640> was<00:08:30.760> raised<00:08:30.910> in<00:08:31.000> 2017<00:08:31.570> or 00:08:31.590 --> 00:08:31.600 align:start position:0% billion dollars was raised in 2017 or 00:08:31.600 --> 00:08:34.650 align:start position:0% billion dollars was raised in 2017 or since<00:08:31.930> 2017<00:08:32.560> there's<00:08:33.370> about<00:08:33.490> ten<00:08:33.880> apps<00:08:34.150> with 00:08:34.650 --> 00:08:34.660 align:start position:0% since 2017 there's about ten apps with 00:08:34.660 --> 00:08:38.089 align:start position:0% since 2017 there's about ten apps with 20<00:08:35.200> or<00:08:35.500> 2,000<00:08:35.950> users<00:08:36.190> each<00:08:36.310> on<00:08:36.520> the<00:08:37.090> daily 00:08:38.089 --> 00:08:38.099 align:start position:0% 20 or 2,000 users each on the daily 00:08:38.099 --> 00:08:40.620 align:start position:0% 20 or 2,000 users each on the daily again<00:08:39.099> 0.01<00:08:39.849> percent<00:08:40.000> of<00:08:40.180> the<00:08:40.240> Facebook<00:08:40.570> user 00:08:40.620 --> 00:08:40.630 align:start position:0% again 0.01 percent of the Facebook user 00:08:40.630 --> 00:08:45.180 align:start position:0% again 0.01 percent of the Facebook user base<00:08:42.570> very<00:08:43.570> few<00:08:43.990> have<00:08:44.169> product<00:08:44.650> market<00:08:44.710> fit<00:08:44.890> if 00:08:45.180 --> 00:08:45.190 align:start position:0% base very few have product market fit if 00:08:45.190 --> 00:08:50.270 align:start position:0% base very few have product market fit if any<00:08:47.550> so<00:08:48.550> we're<00:08:48.670> well<00:08:48.760> within<00:08:48.790> the<00:08:49.030> chasm<00:08:49.390> right 00:08:50.270 --> 00:08:50.280 align:start position:0% any so we're well within the chasm right 00:08:50.280 --> 00:08:53.760 align:start position:0% any so we're well within the chasm right and<00:08:51.280> the<00:08:52.030> reason<00:08:52.210> for<00:08:52.510> this<00:08:52.630> too<00:08:52.840> is<00:08:53.080> the 00:08:53.760 --> 00:08:53.770 align:start position:0% and the reason for this too is the 00:08:53.770 --> 00:08:55.830 align:start position:0% and the reason for this too is the developer<00:08:54.250> challenges<00:08:54.640> this<00:08:55.390> is<00:08:55.450> a<00:08:55.540> survey 00:08:55.830 --> 00:08:55.840 align:start position:0% developer challenges this is a survey 00:08:55.840 --> 00:08:57.630 align:start position:0% developer challenges this is a survey build<00:08:56.050> by<00:08:56.170> fluence<00:08:56.560> in<00:08:56.770> 2019<00:08:57.250> if<00:08:57.340> you<00:08:57.400> haven't 00:08:57.630 --> 00:08:57.640 align:start position:0% build by fluence in 2019 if you haven't 00:08:57.640 --> 00:08:58.050 align:start position:0% build by fluence in 2019 if you haven't seen<00:08:57.820> it 00:08:58.050 --> 00:08:58.060 align:start position:0% seen it 00:08:58.060 --> 00:08:59.880 align:start position:0% seen it I<00:08:58.090> think<00:08:58.720> it's<00:08:58.870> probably<00:08:59.020> the<00:08:59.140> best<00:08:59.290> UX<00:08:59.620> survey 00:08:59.880 --> 00:08:59.890 align:start position:0% I think it's probably the best UX survey 00:08:59.890 --> 00:09:02.310 align:start position:0% I think it's probably the best UX survey out<00:08:59.980> there<00:09:00.160> today<00:09:00.390> and<00:09:01.390> they<00:09:01.810> kind<00:09:01.990> of<00:09:02.020> just<00:09:02.200> go 00:09:02.310 --> 00:09:02.320 align:start position:0% out there today and they kind of just go 00:09:02.320 --> 00:09:04.470 align:start position:0% out there today and they kind of just go over<00:09:02.470> all<00:09:02.800> of<00:09:02.980> the<00:09:03.130> issues<00:09:03.640> with<00:09:03.970> developing 00:09:04.470 --> 00:09:04.480 align:start position:0% over all of the issues with developing 00:09:04.480 --> 00:09:07.680 align:start position:0% over all of the issues with developing blocking<00:09:05.350> apps<00:09:05.670> it's<00:09:06.670> it's<00:09:07.180> really<00:09:07.510> difficult 00:09:07.680 --> 00:09:07.690 align:start position:0% blocking apps it's it's really difficult 00:09:07.690 --> 00:09:11.100 align:start position:0% blocking apps it's it's really difficult it's<00:09:08.470> you<00:09:09.160> know<00:09:09.280> we're<00:09:09.790> both<00:09:09.970> developing<00:09:10.570> this 00:09:11.100 --> 00:09:11.110 align:start position:0% it's you know we're both developing this 00:09:11.110 --> 00:09:12.870 align:start position:0% it's you know we're both developing this new<00:09:11.410> interface<00:09:12.040> and<00:09:12.070> then<00:09:12.400> you<00:09:12.490> have<00:09:12.640> the 00:09:12.870 --> 00:09:12.880 align:start position:0% new interface and then you have the 00:09:12.880 --> 00:09:14.250 align:start position:0% new interface and then you have the tools<00:09:13.120> that<00:09:13.300> you're<00:09:13.570> also<00:09:13.810> developing<00:09:14.110> at<00:09:14.200> the 00:09:14.250 --> 00:09:14.260 align:start position:0% tools that you're also developing at the 00:09:14.260 --> 00:09:17.100 align:start position:0% tools that you're also developing at the same<00:09:14.440> time<00:09:14.680> and<00:09:15.510> there's<00:09:16.510> a<00:09:16.570> lot<00:09:16.660> of<00:09:16.780> issues<00:09:16.870> so 00:09:17.100 --> 00:09:17.110 align:start position:0% same time and there's a lot of issues so 00:09:17.110 --> 00:09:19.290 align:start position:0% same time and there's a lot of issues so again<00:09:17.320> you're<00:09:17.530> coming<00:09:17.980> back<00:09:18.070> to<00:09:18.280> you<00:09:19.210> know 00:09:19.290 --> 00:09:19.300 align:start position:0% again you're coming back to you know 00:09:19.300 --> 00:09:21.450 align:start position:0% again you're coming back to you know we're<00:09:19.840> sort<00:09:20.050> of<00:09:20.200> forcing<00:09:20.620> private<00:09:21.070> keys<00:09:21.220> down 00:09:21.450 --> 00:09:21.460 align:start position:0% we're sort of forcing private keys down 00:09:21.460 --> 00:09:24.660 align:start position:0% we're sort of forcing private keys down and<00:09:21.760> users<00:09:22.300> throats<00:09:22.570> more<00:09:22.780> or<00:09:22.840> less<00:09:23.550> this<00:09:24.550> is 00:09:24.660 --> 00:09:24.670 align:start position:0% and users throats more or less this is 00:09:24.670 --> 00:09:27.840 align:start position:0% and users throats more or less this is also<00:09:24.880> a<00:09:25.110> stat<00:09:26.110> that<00:09:26.140> I<00:09:26.350> saw<00:09:26.530> it<00:09:26.680> on<00:09:27.670> another 00:09:27.840 --> 00:09:27.850 align:start position:0% also a stat that I saw it on another 00:09:27.850 --> 00:09:29.250 align:start position:0% also a stat that I saw it on another presentation<00:09:28.300> that<00:09:28.570> I<00:09:28.600> thought<00:09:28.750> was<00:09:28.870> really 00:09:29.250 --> 00:09:29.260 align:start position:0% presentation that I thought was really 00:09:29.260 --> 00:09:31.020 align:start position:0% presentation that I thought was really interesting<00:09:29.650> I<00:09:29.920> believe<00:09:30.430> it<00:09:30.580> comes<00:09:30.730> from<00:09:30.940> the 00:09:31.020 --> 00:09:31.030 align:start position:0% interesting I believe it comes from the 00:09:31.030 --> 00:09:35.460 align:start position:0% interesting I believe it comes from the cryptic<00:09:31.300> radius<00:09:31.570> study<00:09:32.820> so<00:09:34.080> how<00:09:35.080> do<00:09:35.140> you<00:09:35.260> fix 00:09:35.460 --> 00:09:35.470 align:start position:0% cryptic radius study so how do you fix 00:09:35.470 --> 00:09:38.120 align:start position:0% cryptic radius study so how do you fix in<00:09:35.770> user<00:09:36.160> issues<00:09:36.430> and<00:09:36.640> I'm<00:09:37.120> gonna<00:09:37.270> go<00:09:37.360> back<00:09:37.630> to 00:09:38.120 --> 00:09:38.130 align:start position:0% in user issues and I'm gonna go back to 00:09:38.130 --> 00:09:42.420 align:start position:0% in user issues and I'm gonna go back to onboarding<00:09:39.130> and<00:09:39.430> scaling<00:09:40.420> and<00:09:41.260> MOOC<00:09:42.100> but 00:09:42.420 --> 00:09:42.430 align:start position:0% onboarding and scaling and MOOC but 00:09:42.430 --> 00:09:45.240 align:start position:0% onboarding and scaling and MOOC but focus<00:09:42.790> on<00:09:42.850> that<00:09:43.000> onboarding<00:09:43.450> side<00:09:44.250> because 00:09:45.240 --> 00:09:45.250 align:start position:0% focus on that onboarding side because 00:09:45.250 --> 00:09:47.310 align:start position:0% focus on that onboarding side because this<00:09:45.340> is<00:09:45.520> beyond<00:09:45.820> burner<00:09:46.090> again<00:09:46.570> so<00:09:47.170> it's 00:09:47.310 --> 00:09:47.320 align:start position:0% this is beyond burner again so it's 00:09:47.320 --> 00:09:48.870 align:start position:0% this is beyond burner again so it's again<00:09:47.410> focused<00:09:47.770> on<00:09:47.830> that<00:09:47.980> account<00:09:48.250> contract 00:09:48.870 --> 00:09:48.880 align:start position:0% again focused on that account contract 00:09:48.880 --> 00:09:51.660 align:start position:0% again focused on that account contract with<00:09:49.540> ephemeral<00:09:50.110> keys<00:09:50.350> to<00:09:51.040> create<00:09:51.640> a 00:09:51.660 --> 00:09:51.670 align:start position:0% with ephemeral keys to create a 00:09:51.670 --> 00:09:55.590 align:start position:0% with ephemeral keys to create a programmable<00:09:52.210> access<00:09:52.660> of<00:09:52.810> funds<00:09:53.850> and<00:09:54.850> if<00:09:55.270> you 00:09:55.590 --> 00:09:55.600 align:start position:0% programmable access of funds and if you 00:09:55.600 --> 00:09:57.390 align:start position:0% programmable access of funds and if you don't<00:09:55.840> have<00:09:56.080> effective<00:09:56.320> onboarding<00:09:56.710> there's 00:09:57.390 --> 00:09:57.400 align:start position:0% don't have effective onboarding there's 00:09:57.400 --> 00:09:58.770 align:start position:0% don't have effective onboarding there's no<00:09:57.610> reason<00:09:57.940> to<00:09:58.000> have<00:09:58.090> a<00:09:58.150> state<00:09:58.360> channel<00:09:58.660> or<00:09:58.750> a 00:09:58.770 --> 00:09:58.780 align:start position:0% no reason to have a state channel or a 00:09:58.780 --> 00:10:00.780 align:start position:0% no reason to have a state channel or a second<00:09:59.050> layer<00:09:59.140> solution<00:09:59.530> there's<00:10:00.310> no<00:10:00.430> there's 00:10:00.780 --> 00:10:00.790 align:start position:0% second layer solution there's no there's 00:10:00.790 --> 00:10:03.210 align:start position:0% second layer solution there's no there's no<00:10:00.850> real<00:10:00.940> need<00:10:01.240> for<00:10:01.300> e<00:10:01.810> 2.0<00:10:02.380> if<00:10:02.500> we<00:10:02.890> don't<00:10:03.070> have 00:10:03.210 --> 00:10:03.220 align:start position:0% no real need for e 2.0 if we don't have 00:10:03.220 --> 00:10:07.410 align:start position:0% no real need for e 2.0 if we don't have enough<00:10:03.640> end<00:10:03.820> users<00:10:04.060> to<00:10:04.120> drive<00:10:04.330> traffic<00:10:06.420> the 00:10:07.410 --> 00:10:07.420 align:start position:0% enough end users to drive traffic the 00:10:07.420 --> 00:10:08.670 align:start position:0% enough end users to drive traffic the approach<00:10:07.690> to<00:10:07.900> really<00:10:08.080> understand<00:10:08.440> this<00:10:08.530> is 00:10:08.670 --> 00:10:08.680 align:start position:0% approach to really understand this is 00:10:08.680 --> 00:10:10.080 align:start position:0% approach to really understand this is you<00:10:08.770> had<00:10:08.890> to<00:10:08.950> know<00:10:09.100> your<00:10:09.250> user<00:10:09.430> base<00:10:09.550> create 00:10:10.080 --> 00:10:10.090 align:start position:0% you had to know your user base create 00:10:10.090 --> 00:10:12.540 align:start position:0% you had to know your user base create intuitive<00:10:10.570> interfaces<00:10:11.020> and<00:10:11.410> then<00:10:12.070> iterate 00:10:12.540 --> 00:10:12.550 align:start position:0% intuitive interfaces and then iterate 00:10:12.550 --> 00:10:14.670 align:start position:0% intuitive interfaces and then iterate with<00:10:12.700> the<00:10:12.850> feedback<00:10:13.180> that<00:10:13.210> you're<00:10:13.390> given<00:10:13.720> and 00:10:14.670 --> 00:10:14.680 align:start position:0% with the feedback that you're given and 00:10:14.680 --> 00:10:17.610 align:start position:0% with the feedback that you're given and that<00:10:15.520> a<00:10:15.580> lot<00:10:15.850> of<00:10:15.910> that<00:10:16.000> means<00:10:16.180> to<00:10:16.390> ship<00:10:16.660> quickly 00:10:17.610 --> 00:10:17.620 align:start position:0% that a lot of that means to ship quickly 00:10:17.620 --> 00:10:21.150 align:start position:0% that a lot of that means to ship quickly and<00:10:18.010> and<00:10:18.430> gather<00:10:19.000> information<00:10:19.380> as<00:10:20.380> quickly<00:10:20.860> as 00:10:21.150 --> 00:10:21.160 align:start position:0% and and gather information as quickly as 00:10:21.160 --> 00:10:21.600 align:start position:0% and and gather information as quickly as possible 00:10:21.600 --> 00:10:21.610 align:start position:0% possible 00:10:21.610 --> 00:10:24.090 align:start position:0% possible mmm<00:10:22.420> and<00:10:22.510> so<00:10:22.780> again<00:10:23.200> sort<00:10:23.590> of<00:10:23.650> iterate<00:10:23.980> why 00:10:24.090 --> 00:10:24.100 align:start position:0% mmm and so again sort of iterate why 00:10:24.100 --> 00:10:25.980 align:start position:0% mmm and so again sort of iterate why onboarding<00:10:24.460> sucks<00:10:24.760> it's<00:10:25.420> uncomfortable<00:10:25.720> and 00:10:25.980 --> 00:10:25.990 align:start position:0% onboarding sucks it's uncomfortable and 00:10:25.990 --> 00:10:27.600 align:start position:0% onboarding sucks it's uncomfortable and inconvenient<00:10:26.590> primarily<00:10:27.310> and<00:10:27.430> I<00:10:27.460> think 00:10:27.600 --> 00:10:27.610 align:start position:0% inconvenient primarily and I think 00:10:27.610 --> 00:10:29.250 align:start position:0% inconvenient primarily and I think everyone<00:10:27.880> can<00:10:27.970> kind<00:10:28.150> of<00:10:28.180> appreciate<00:10:28.840> that<00:10:29.050> I'm 00:10:29.250 --> 00:10:29.260 align:start position:0% everyone can kind of appreciate that I'm 00:10:29.260 --> 00:10:31.200 align:start position:0% everyone can kind of appreciate that I'm sure<00:10:29.410> everyone<00:10:29.680> has<00:10:29.770> tried<00:10:29.890> to<00:10:30.100> like<00:10:30.280> talk<00:10:31.000> to 00:10:31.200 --> 00:10:31.210 align:start position:0% sure everyone has tried to like talk to 00:10:31.210 --> 00:10:32.610 align:start position:0% sure everyone has tried to like talk to someone<00:10:31.420> like<00:10:31.510> hey<00:10:31.810> yeah<00:10:32.020> that's<00:10:32.170> like<00:10:32.410> great 00:10:32.610 --> 00:10:32.620 align:start position:0% someone like hey yeah that's like great 00:10:32.620 --> 00:10:34.140 align:start position:0% someone like hey yeah that's like great you<00:10:32.680> know<00:10:32.950> come<00:10:33.130> on<00:10:33.250> to<00:10:33.550> the<00:10:33.610> meta<00:10:33.820> mask<00:10:34.000> or 00:10:34.140 --> 00:10:34.150 align:start position:0% you know come on to the meta mask or 00:10:34.150 --> 00:10:35.520 align:start position:0% you know come on to the meta mask or something<00:10:34.180> and<00:10:34.570> whoever<00:10:35.080> you're<00:10:35.230> talking<00:10:35.350> to 00:10:35.520 --> 00:10:35.530 align:start position:0% something and whoever you're talking to 00:10:35.530 --> 00:10:36.900 align:start position:0% something and whoever you're talking to is<00:10:35.620> like<00:10:35.920> now<00:10:36.070> I'm<00:10:36.220> not<00:10:36.370> really<00:10:36.460> sure<00:10:36.700> like 00:10:36.900 --> 00:10:36.910 align:start position:0% is like now I'm not really sure like 00:10:36.910 --> 00:10:38.070 align:start position:0% is like now I'm not really sure like compounds<00:10:37.390> kind<00:10:37.570> of<00:10:37.630> weird<00:10:37.750> I<00:10:37.840> don't<00:10:37.900> really 00:10:38.070 --> 00:10:38.080 align:start position:0% compounds kind of weird I don't really 00:10:38.080 --> 00:10:40.550 align:start position:0% compounds kind of weird I don't really want<00:10:38.230> to<00:10:38.260> download<00:10:38.440> this<00:10:38.710> thing<00:10:39.480> so 00:10:40.550 --> 00:10:40.560 align:start position:0% want to download this thing so 00:10:40.560 --> 00:10:42.360 align:start position:0% want to download this thing so hypothesis<00:10:41.560> that<00:10:41.620> we<00:10:41.740> developed<00:10:42.070> a<00:10:42.160> bridge 00:10:42.360 --> 00:10:42.370 align:start position:0% hypothesis that we developed a bridge 00:10:42.370 --> 00:10:45.510 align:start position:0% hypothesis that we developed a bridge was<00:10:42.670> okay<00:10:43.240> if<00:10:43.420> we<00:10:43.690> just<00:10:44.320> use<00:10:44.530> web<00:10:45.010> to<00:10:45.250> like 00:10:45.510 --> 00:10:45.520 align:start position:0% was okay if we just use web to like 00:10:45.520 --> 00:10:48.540 align:start position:0% was okay if we just use web to like flows<00:10:45.870> like<00:10:46.870> Atos<00:10:47.410> authentication<00:10:48.280> for 00:10:48.540 --> 00:10:48.550 align:start position:0% flows like Atos authentication for 00:10:48.550 --> 00:10:50.640 align:start position:0% flows like Atos authentication for instance<00:10:48.910> we<00:10:49.720> could<00:10:49.840> maybe<00:10:50.080> on<00:10:50.290> board<00:10:50.530> more 00:10:50.640 --> 00:10:50.650 align:start position:0% instance we could maybe on board more 00:10:50.650 --> 00:10:54.960 align:start position:0% instance we could maybe on board more users<00:10:50.980> and<00:10:51.370> that<00:10:51.490> could<00:10:52.140> happen<00:10:53.280> and<00:10:54.280> so<00:10:54.520> we 00:10:54.960 --> 00:10:54.970 align:start position:0% users and that could happen and so we 00:10:54.970 --> 00:10:57.510 align:start position:0% users and that could happen and so we sort<00:10:55.540> of<00:10:55.600> went<00:10:56.200> on<00:10:56.350> a<00:10:56.380> rampage<00:10:56.860> we<00:10:57.100> came<00:10:57.370> with 00:10:57.510 --> 00:10:57.520 align:start position:0% sort of went on a rampage we came with 00:10:57.520 --> 00:11:01.680 align:start position:0% sort of went on a rampage we came with an<00:10:57.610> SDK<00:10:58.120> in<00:10:58.450> June<00:10:59.410> and<00:11:00.000> on<00:11:01.000> been<00:11:01.480> like 00:11:01.680 --> 00:11:01.690 align:start position:0% an SDK in June and on been like 00:11:01.690 --> 00:11:03.150 align:start position:0% an SDK in June and on been like integrated<00:11:02.500> it<00:11:02.590> with<00:11:02.620> as<00:11:02.800> many<00:11:02.980> applications 00:11:03.150 --> 00:11:03.160 align:start position:0% integrated it with as many applications 00:11:03.160 --> 00:11:05.100 align:start position:0% integrated it with as many applications as<00:11:03.520> we<00:11:03.670> could<00:11:03.880> we<00:11:04.030> hit<00:11:04.210> like<00:11:04.390> eight<00:11:04.900> or<00:11:04.960> nine 00:11:05.100 --> 00:11:05.110 align:start position:0% as we could we hit like eight or nine 00:11:05.110 --> 00:11:09.080 align:start position:0% as we could we hit like eight or nine essentially<00:11:06.030> and<00:11:07.140> so<00:11:08.140> all<00:11:08.770> of<00:11:08.800> these 00:11:09.080 --> 00:11:09.090 align:start position:0% essentially and so all of these 00:11:09.090 --> 00:11:11.150 align:start position:0% essentially and so all of these applications<00:11:10.090> sort<00:11:10.300> of<00:11:10.360> have<00:11:10.570> a<00:11:10.600> bridge 00:11:11.150 --> 00:11:11.160 align:start position:0% applications sort of have a bridge 00:11:11.160 --> 00:11:14.030 align:start position:0% applications sort of have a bridge tooling<00:11:11.790> integrated<00:11:12.360> into<00:11:12.570> it<00:11:12.720> and<00:11:12.900> the<00:11:13.860> most 00:11:14.030 --> 00:11:14.040 align:start position:0% tooling integrated into it and the most 00:11:14.040 --> 00:11:16.610 align:start position:0% tooling integrated into it and the most popular<00:11:14.610> have<00:11:15.270> been<00:11:15.510> Yolo<00:11:15.960> wrecked<00:11:16.200> into 00:11:16.610 --> 00:11:16.620 align:start position:0% popular have been Yolo wrecked into 00:11:16.620 --> 00:11:19.550 align:start position:0% popular have been Yolo wrecked into house<00:11:17.660> they<00:11:18.660> actually<00:11:18.900> have<00:11:18.990> real<00:11:19.140> end<00:11:19.290> users 00:11:19.550 --> 00:11:19.560 align:start position:0% house they actually have real end users 00:11:19.560 --> 00:11:22.250 align:start position:0% house they actually have real end users if<00:11:19.740> you<00:11:19.770> want<00:11:20.070> to<00:11:20.190> actually<00:11:20.700> experience<00:11:21.480> what 00:11:22.250 --> 00:11:22.260 align:start position:0% if you want to actually experience what 00:11:22.260 --> 00:11:24.320 align:start position:0% if you want to actually experience what this<00:11:22.920> account<00:11:23.340> contract<00:11:23.700> assign<00:11:23.910> feels<00:11:24.120> like 00:11:24.320 --> 00:11:24.330 align:start position:0% this account contract assign feels like 00:11:24.330 --> 00:11:27.470 align:start position:0% this account contract assign feels like definitely<00:11:25.200> check<00:11:25.560> these<00:11:25.710> both<00:11:26.280> out<00:11:26.550> your<00:11:27.180> ex 00:11:27.470 --> 00:11:27.480 align:start position:0% definitely check these both out your ex 00:11:27.480 --> 00:11:29.240 align:start position:0% definitely check these both out your ex is<00:11:27.570> just<00:11:27.660> a<00:11:27.840> binary<00:11:28.110> options<00:11:28.590> trading<00:11:28.830> you 00:11:29.240 --> 00:11:29.250 align:start position:0% is just a binary options trading you 00:11:29.250 --> 00:11:31.550 align:start position:0% is just a binary options trading you know<00:11:29.340> betting<00:11:30.030> platform<00:11:30.600> and<00:11:30.780> then<00:11:31.140> Dow<00:11:31.350> house 00:11:31.550 --> 00:11:31.560 align:start position:0% know betting platform and then Dow house 00:11:31.560 --> 00:11:34.760 align:start position:0% know betting platform and then Dow house is<00:11:31.860> going<00:11:32.310> to<00:11:32.430> be<00:11:32.550> a<00:11:32.790> Dow<00:11:33.360> you<00:11:34.200> spin<00:11:34.410> up<00:11:34.530> a<00:11:34.560> like 00:11:34.760 --> 00:11:34.770 align:start position:0% is going to be a Dow you spin up a like 00:11:34.770 --> 00:11:37.040 align:start position:0% is going to be a Dow you spin up a like the<00:11:34.860> house<00:11:35.010> right<00:11:35.430> so<00:11:35.670> it's<00:11:36.480> they<00:11:36.840> have<00:11:36.900> like 00:11:37.040 --> 00:11:37.050 align:start position:0% the house right so it's they have like 00:11:37.050 --> 00:11:38.930 align:start position:0% the house right so it's they have like 10<00:11:37.290> different<00:11:37.410> dolls<00:11:37.800> moving<00:11:38.520> along<00:11:38.730> there 00:11:38.930 --> 00:11:38.940 align:start position:0% 10 different dolls moving along there 00:11:38.940 --> 00:11:42.140 align:start position:0% 10 different dolls moving along there which<00:11:39.060> is<00:11:39.210> pretty<00:11:39.570> exciting<00:11:40.490> and<00:11:41.490> what<00:11:42.060> we 00:11:42.140 --> 00:11:42.150 align:start position:0% which is pretty exciting and what we 00:11:42.150 --> 00:11:45.320 align:start position:0% which is pretty exciting and what we found<00:11:42.330> from<00:11:42.600> that<00:11:42.660> is<00:11:43.440> sort<00:11:43.680> of<00:11:43.940> all<00:11:44.940> of<00:11:45.120> this 00:11:45.320 --> 00:11:45.330 align:start position:0% found from that is sort of all of this 00:11:45.330 --> 00:11:49.250 align:start position:0% found from that is sort of all of this feedback<00:11:46.970> was<00:11:47.970> that<00:11:48.000> there's<00:11:48.390> two<00:11:48.690> types<00:11:49.020> of 00:11:49.250 --> 00:11:49.260 align:start position:0% feedback was that there's two types of 00:11:49.260 --> 00:11:50.990 align:start position:0% feedback was that there's two types of users<00:11:49.710> that<00:11:49.740> you're<00:11:49.980> looking<00:11:50.280> at<00:11:50.430> when<00:11:50.910> you're 00:11:50.990 --> 00:11:51.000 align:start position:0% users that you're looking at when you're 00:11:51.000 --> 00:11:53.540 align:start position:0% users that you're looking at when you're developing<00:11:51.380> blockchain<00:11:52.380> applications<00:11:52.920> one 00:11:53.540 --> 00:11:53.550 align:start position:0% developing blockchain applications one 00:11:53.550 --> 00:11:58.310 align:start position:0% developing blockchain applications one is<00:11:53.670> for<00:11:53.880> web<00:11:54.000> 3<00:11:54.300> and<00:11:54.690> the<00:11:54.930> others<00:11:55.110> for<00:11:55.320> web<00:11:55.440> -<00:11:57.320> so 00:11:58.310 --> 00:11:58.320 align:start position:0% is for web 3 and the others for web - so 00:11:58.320 --> 00:12:00.530 align:start position:0% is for web 3 and the others for web - so like<00:11:58.620> web<00:11:58.800> 3<00:11:58.950> users<00:11:59.280> are<00:11:59.400> really<00:11:59.610> interested 00:12:00.530 --> 00:12:00.540 align:start position:0% like web 3 users are really interested 00:12:00.540 --> 00:12:05.750 align:start position:0% like web 3 users are really interested in<00:12:01.160> you<00:12:02.160> know<00:12:02.190> privacy<00:12:03.800> web<00:12:04.800> 3<00:12:05.070> provider<00:12:05.520> they 00:12:05.750 --> 00:12:05.760 align:start position:0% in you know privacy web 3 provider they 00:12:05.760 --> 00:12:08.420 align:start position:0% in you know privacy web 3 provider they prefer<00:12:06.030> meta<00:12:06.210> mask<00:12:06.450> and<00:12:06.800> self<00:12:07.800> sovereignty<00:12:08.190> of 00:12:08.420 --> 00:12:08.430 align:start position:0% prefer meta mask and self sovereignty of 00:12:08.430 --> 00:12:12.740 align:start position:0% prefer meta mask and self sovereignty of course<00:12:09.530> it's<00:12:10.530> I<00:12:11.180> spoke<00:12:12.180> with<00:12:12.300> Nate<00:12:12.480> grittier 00:12:12.740 --> 00:12:12.750 align:start position:0% course it's I spoke with Nate grittier 00:12:12.750 --> 00:12:15.650 align:start position:0% course it's I spoke with Nate grittier who<00:12:13.200> is<00:12:13.410> building<00:12:14.100> in<00:12:14.730> what<00:12:15.090> 3<00:12:15.240> as<00:12:15.360> well<00:12:15.480> and 00:12:15.650 --> 00:12:15.660 align:start position:0% who is building in what 3 as well and 00:12:15.660 --> 00:12:17.390 align:start position:0% who is building in what 3 as well and he's<00:12:15.750> kind<00:12:16.050> of<00:12:16.080> describes<00:12:16.350> as<00:12:16.470> coddling<00:12:17.310> an 00:12:17.390 --> 00:12:17.400 align:start position:0% he's kind of describes as coddling an 00:12:17.400 --> 00:12:19.370 align:start position:0% he's kind of describes as coddling an ember<00:12:17.760> and<00:12:17.910> a<00:12:17.970> damp<00:12:18.180> forest<00:12:18.690> where<00:12:19.260> you're 00:12:19.370 --> 00:12:19.380 align:start position:0% ember and a damp forest where you're 00:12:19.380 --> 00:12:20.810 align:start position:0% ember and a damp forest where you're just<00:12:19.560> trying<00:12:19.830> to<00:12:19.890> get<00:12:20.070> it<00:12:20.250> to<00:12:20.340> kind<00:12:20.610> of<00:12:20.700> like 00:12:20.810 --> 00:12:20.820 align:start position:0% just trying to get it to kind of like 00:12:20.820 --> 00:12:23.990 align:start position:0% just trying to get it to kind of like keep<00:12:21.120> heating<00:12:21.450> up<00:12:21.720> right<00:12:22.470> and<00:12:22.650> of<00:12:23.580> course<00:12:23.670> he's 00:12:23.990 --> 00:12:24.000 align:start position:0% keep heating up right and of course he's 00:12:24.000 --> 00:12:26.570 align:start position:0% keep heating up right and of course he's like<00:12:24.180> meta<00:12:24.390> mask<00:12:24.600> users<00:12:24.900> for<00:12:25.860> web<00:12:25.980> 2<00:12:26.220> users 00:12:26.570 --> 00:12:26.580 align:start position:0% like meta mask users for web 2 users 00:12:26.580 --> 00:12:29.240 align:start position:0% like meta mask users for web 2 users though<00:12:26.820> they<00:12:27.180> kind<00:12:27.510> of<00:12:27.620> they<00:12:28.620> likely<00:12:28.920> don't 00:12:29.240 --> 00:12:29.250 align:start position:0% though they kind of they likely don't 00:12:29.250 --> 00:12:30.830 align:start position:0% though they kind of they likely don't care<00:12:29.610> as<00:12:29.700> much<00:12:29.760> they're<00:12:30.180> they're<00:12:30.450> looking<00:12:30.540> for 00:12:30.830 --> 00:12:30.840 align:start position:0% care as much they're they're looking for 00:12:30.840 --> 00:12:32.150 align:start position:0% care as much they're they're looking for just<00:12:30.990> like<00:12:31.110> intuitive<00:12:31.500> fun<00:12:31.650> things<00:12:31.860> to<00:12:31.980> use 00:12:32.150 --> 00:12:32.160 align:start position:0% just like intuitive fun things to use 00:12:32.160 --> 00:12:34.370 align:start position:0% just like intuitive fun things to use which<00:12:32.340> burner<00:12:33.150> and<00:12:33.480> like<00:12:33.690> the<00:12:33.840> abridged<00:12:34.140> like 00:12:34.370 --> 00:12:34.380 align:start position:0% which burner and like the abridged like 00:12:34.380 --> 00:12:37.010 align:start position:0% which burner and like the abridged like smart<00:12:35.280> contracts<00:12:35.760> or<00:12:35.910> account<00:12:36.270> contracts<00:12:36.630> is 00:12:37.010 --> 00:12:37.020 align:start position:0% smart contracts or account contracts is 00:12:37.020 --> 00:12:40.070 align:start position:0% smart contracts or account contracts is potentially<00:12:37.860> a<00:12:37.890> more<00:12:38.040> viable<00:12:38.220> solution<00:12:39.080> and 00:12:40.070 --> 00:12:40.080 align:start position:0% potentially a more viable solution and 00:12:40.080 --> 00:12:42.200 align:start position:0% potentially a more viable solution and so<00:12:40.440> the<00:12:40.710> common<00:12:40.950> denominator<00:12:41.460> everyone<00:12:41.940> wants 00:12:42.200 --> 00:12:42.210 align:start position:0% so the common denominator everyone wants 00:12:42.210 --> 00:12:43.460 align:start position:0% so the common denominator everyone wants a<00:12:42.270> seamless<00:12:42.540> experience<00:12:42.720> they<00:12:43.170> don't<00:12:43.290> want<00:12:43.410> to 00:12:43.460 --> 00:12:43.470 align:start position:0% a seamless experience they don't want to 00:12:43.470 --> 00:12:44.900 align:start position:0% a seamless experience they don't want to think<00:12:43.590> they<00:12:43.890> want<00:12:44.250> to<00:12:44.340> they<00:12:44.550> don't<00:12:44.580> want<00:12:44.820> to 00:12:44.900 --> 00:12:44.910 align:start position:0% think they want to they don't want to 00:12:44.910 --> 00:12:46.940 align:start position:0% think they want to they don't want to trust<00:12:45.270> what<00:12:45.630> what<00:12:45.870> you're<00:12:45.990> doing<00:12:46.320> and<00:12:46.500> they 00:12:46.940 --> 00:12:46.950 align:start position:0% trust what what you're doing and they 00:12:46.950 --> 00:12:49.940 align:start position:0% trust what what you're doing and they don't<00:12:47.100> want<00:12:47.330> to<00:12:48.330> waste<00:12:48.450> time<00:12:48.810> in<00:12:49.320> the 00:12:49.940 --> 00:12:49.950 align:start position:0% don't want to waste time in the 00:12:49.950 --> 00:12:51.410 align:start position:0% don't want to waste time in the onboarding<00:12:50.370> process<00:12:50.400> otherwise<00:12:51.060> you<00:12:51.240> won't 00:12:51.410 --> 00:12:51.420 align:start position:0% onboarding process otherwise you won't 00:12:51.420 --> 00:12:53.180 align:start position:0% onboarding process otherwise you won't you<00:12:52.020> won't<00:12:52.170> get<00:12:52.380> there<00:12:52.530> you<00:12:52.740> won't<00:12:52.800> be<00:12:52.980> able<00:12:53.130> to 00:12:53.180 --> 00:12:53.190 align:start position:0% you won't get there you won't be able to 00:12:53.190 --> 00:12:54.830 align:start position:0% you won't get there you won't be able to show<00:12:53.610> the<00:12:53.790> value<00:12:54.060> of<00:12:54.150> what<00:12:54.270> the<00:12:54.360> application 00:12:54.830 --> 00:12:54.840 align:start position:0% show the value of what the application 00:12:54.840 --> 00:12:59.690 align:start position:0% show the value of what the application is<00:12:55.280> so<00:12:56.280> to<00:12:57.030> us<00:12:57.180> that<00:12:57.450> looks<00:12:57.660> like<00:12:57.900> at<00:12:58.800> least<00:12:58.860> at 00:12:59.690 --> 00:12:59.700 align:start position:0% is so to us that looks like at least at 00:12:59.700 --> 00:13:01.610 align:start position:0% is so to us that looks like at least at first<00:13:00.030> when<00:13:00.420> someone<00:13:00.780> is<00:13:00.870> getting<00:13:01.140> used<00:13:01.470> to 00:13:01.610 --> 00:13:01.620 align:start position:0% first when someone is getting used to 00:13:01.620 --> 00:13:03.290 align:start position:0% first when someone is getting used to understanding<00:13:02.220> what<00:13:02.370> decentralization<00:13:02.970> and 00:13:03.290 --> 00:13:03.300 align:start position:0% understanding what decentralization and 00:13:03.300 --> 00:13:06.500 align:start position:0% understanding what decentralization and what<00:13:03.390> web<00:13:03.750> 3<00:13:04.050> provides<00:13:04.740> or<00:13:05.060> aetherium<00:13:06.060> offers 00:13:06.500 --> 00:13:06.510 align:start position:0% what web 3 provides or aetherium offers 00:13:06.510 --> 00:13:09.380 align:start position:0% what web 3 provides or aetherium offers no<00:13:07.410> seed<00:13:07.710> phrase<00:13:07.980> download<00:13:08.400> native<00:13:09.210> mobile 00:13:09.380 --> 00:13:09.390 align:start position:0% no seed phrase download native mobile 00:13:09.390 --> 00:13:12.620 align:start position:0% no seed phrase download native mobile apps<00:13:09.690> are<00:13:10.020> really<00:13:10.350> nice<00:13:10.730> all<00:13:11.730> the<00:13:12.240> onboarding 00:13:12.620 --> 00:13:12.630 align:start position:0% apps are really nice all the onboarding 00:13:12.630 --> 00:13:14.510 align:start position:0% apps are really nice all the onboarding occurs<00:13:12.990> within<00:13:13.230> the<00:13:13.410> application<00:13:14.070> so<00:13:14.310> no 00:13:14.510 --> 00:13:14.520 align:start position:0% occurs within the application so no 00:13:14.520 --> 00:13:16.760 align:start position:0% occurs within the application so no needing<00:13:14.970> to<00:13:15.090> switch<00:13:15.330> screens<00:13:15.720> and<00:13:16.260> then 00:13:16.760 --> 00:13:16.770 align:start position:0% needing to switch screens and then 00:13:16.770 --> 00:13:18.230 align:start position:0% needing to switch screens and then account<00:13:17.100> recovery<00:13:17.460> options<00:13:17.940> are<00:13:18.060> also 00:13:18.230 --> 00:13:18.240 align:start position:0% account recovery options are also 00:13:18.240 --> 00:13:19.660 align:start position:0% account recovery options are also included 00:13:19.660 --> 00:13:19.670 align:start position:0% included 00:13:19.670 --> 00:13:24.700 align:start position:0% included within<00:13:20.270> your<00:13:21.190> management<00:13:22.190> system<00:13:23.470> so<00:13:24.470> again 00:13:24.700 --> 00:13:24.710 align:start position:0% within your management system so again 00:13:24.710 --> 00:13:27.910 align:start position:0% within your management system so again we<00:13:25.580> want<00:13:25.760> to<00:13:25.880> create<00:13:26.360> instant<00:13:26.810> value<00:13:26.960> for<00:13:27.830> the 00:13:27.910 --> 00:13:27.920 align:start position:0% we want to create instant value for the 00:13:27.920 --> 00:13:30.850 align:start position:0% we want to create instant value for the end-user<00:13:28.250> and<00:13:28.780> the<00:13:29.780> account<00:13:30.140> contracts<00:13:30.620> are 00:13:30.850 --> 00:13:30.860 align:start position:0% end-user and the account contracts are 00:13:30.860 --> 00:13:33.700 align:start position:0% end-user and the account contracts are really<00:13:31.360> the<00:13:32.360> way<00:13:32.600> potentially<00:13:33.140> to<00:13:33.410> do<00:13:33.530> that 00:13:33.700 --> 00:13:33.710 align:start position:0% really the way potentially to do that 00:13:33.710 --> 00:13:35.290 align:start position:0% really the way potentially to do that it's<00:13:34.010> a<00:13:34.340> more<00:13:34.580> flexible<00:13:34.760> way<00:13:35.000> in<00:13:35.210> the 00:13:35.290 --> 00:13:35.300 align:start position:0% it's a more flexible way in the 00:13:35.300 --> 00:13:37.150 align:start position:0% it's a more flexible way in the ephemeral<00:13:35.690> Keys<00:13:35.900> essentially<00:13:36.740> the<00:13:36.890> account 00:13:37.150 --> 00:13:37.160 align:start position:0% ephemeral Keys essentially the account 00:13:37.160 --> 00:13:41.620 align:start position:0% ephemeral Keys essentially the account contracts<00:13:37.610> is<00:13:37.820> in<00:13:38.690> particular<00:13:40.180> useful<00:13:41.180> these 00:13:41.620 --> 00:13:41.630 align:start position:0% contracts is in particular useful these 00:13:41.630 --> 00:13:44.170 align:start position:0% contracts is in particular useful these you<00:13:41.810> can<00:13:42.020> recover<00:13:42.500> your<00:13:43.130> funds<00:13:43.640> and<00:13:43.940> you<00:13:44.030> can 00:13:44.170 --> 00:13:44.180 align:start position:0% you can recover your funds and you can 00:13:44.180 --> 00:13:47.020 align:start position:0% you can recover your funds and you can also<00:13:44.380> uniquely<00:13:45.380> permission<00:13:45.860> each<00:13:46.010> key<00:13:46.310> for 00:13:47.020 --> 00:13:47.030 align:start position:0% also uniquely permission each key for 00:13:47.030 --> 00:13:49.390 align:start position:0% also uniquely permission each key for different<00:13:47.270> use<00:13:47.390> cases<00:13:47.630> right<00:13:48.530> so<00:13:48.800> each<00:13:49.100> queue 00:13:49.390 --> 00:13:49.400 align:start position:0% different use cases right so each queue 00:13:49.400 --> 00:13:51.730 align:start position:0% different use cases right so each queue could<00:13:49.490> have<00:13:49.610> different<00:13:49.820> access<00:13:50.810> and<00:13:51.050> this<00:13:51.560> is 00:13:51.730 --> 00:13:51.740 align:start position:0% could have different access and this is 00:13:51.740 --> 00:13:53.710 align:start position:0% could have different access and this is sort<00:13:52.100> of<00:13:52.130> what<00:13:52.370> beyond<00:13:52.730> burner<00:13:52.970> really<00:13:53.450> aims 00:13:53.710 --> 00:13:53.720 align:start position:0% sort of what beyond burner really aims 00:13:53.720 --> 00:13:57.340 align:start position:0% sort of what beyond burner really aims at<00:13:54.020> you<00:13:54.830> have<00:13:55.010> a<00:13:55.250> account<00:13:55.940> contract<00:13:56.630> that<00:13:56.960> has 00:13:57.340 --> 00:13:57.350 align:start position:0% at you have a account contract that has 00:13:57.350 --> 00:13:58.930 align:start position:0% at you have a account contract that has multiple<00:13:57.530> keys<00:13:57.950> all<00:13:58.370> for<00:13:58.610> different<00:13:58.760> reasons 00:13:58.930 --> 00:13:58.940 align:start position:0% multiple keys all for different reasons 00:13:58.940 --> 00:14:02.260 align:start position:0% multiple keys all for different reasons you<00:13:59.930> have<00:14:00.020> your<00:14:00.140> phone<00:14:00.350> your<00:14:00.680> computer<00:14:01.270> your 00:14:02.260 --> 00:14:02.270 align:start position:0% you have your phone your computer your 00:14:02.270 --> 00:14:04.480 align:start position:0% you have your phone your computer your guardian<00:14:02.660> your<00:14:02.840> mom<00:14:03.020> or<00:14:03.320> girlfriend<00:14:03.890> or<00:14:04.010> you 00:14:04.480 --> 00:14:04.490 align:start position:0% guardian your mom or girlfriend or you 00:14:04.490 --> 00:14:07.240 align:start position:0% guardian your mom or girlfriend or you know<00:14:04.610> whoever<00:14:05.170> maybe<00:14:06.170> you<00:14:06.320> have<00:14:06.470> a<00:14:06.500> Portis<00:14:07.070> or 00:14:07.240 --> 00:14:07.250 align:start position:0% know whoever maybe you have a Portis or 00:14:07.250 --> 00:14:09.610 align:start position:0% know whoever maybe you have a Portis or tourist<00:14:07.580> integration<00:14:08.060> as<00:14:08.180> well<00:14:08.210> as<00:14:08.810> a<00:14:09.050> sort<00:14:09.560> of 00:14:09.610 --> 00:14:09.620 align:start position:0% tourist integration as well as a sort of 00:14:09.620 --> 00:14:12.880 align:start position:0% tourist integration as well as a sort of master<00:14:10.010> reset<00:14:10.840> EULA<00:14:11.840> Rex<00:14:12.230> maybe<00:14:12.590> you're 00:14:12.880 --> 00:14:12.890 align:start position:0% master reset EULA Rex maybe you're 00:14:12.890 --> 00:14:14.290 align:start position:0% master reset EULA Rex maybe you're interested<00:14:13.190> in<00:14:13.280> playing<00:14:13.460> you<00:14:13.700> also<00:14:13.850> play<00:14:14.060> gods 00:14:14.290 --> 00:14:14.300 align:start position:0% interested in playing you also play gods 00:14:14.300 --> 00:14:16.060 align:start position:0% interested in playing you also play gods unchained<00:14:14.750> and<00:14:15.080> you're<00:14:15.500> part<00:14:15.680> of<00:14:15.740> meta<00:14:15.890> card 00:14:16.060 --> 00:14:16.070 align:start position:0% unchained and you're part of meta card 00:14:16.070 --> 00:14:18.360 align:start position:0% unchained and you're part of meta card data<00:14:16.220> all<00:14:16.910> of<00:14:17.000> those<00:14:17.300> could<00:14:17.600> have<00:14:17.630> different 00:14:18.360 --> 00:14:18.370 align:start position:0% data all of those could have different 00:14:18.370 --> 00:14:22.840 align:start position:0% data all of those could have different levels<00:14:19.370> of<00:14:19.490> fund<00:14:20.330> access<00:14:20.950> and<00:14:21.950> that's<00:14:22.670> all 00:14:22.840 --> 00:14:22.850 align:start position:0% levels of fund access and that's all 00:14:22.850 --> 00:14:25.210 align:start position:0% levels of fund access and that's all programmable<00:14:23.420> so<00:14:23.900> if<00:14:24.260> you<00:14:24.500> end<00:14:24.890> up<00:14:25.010> losing 00:14:25.210 --> 00:14:25.220 align:start position:0% programmable so if you end up losing 00:14:25.220 --> 00:14:27.880 align:start position:0% programmable so if you end up losing your<00:14:26.090> phone<00:14:26.410> thankfully<00:14:27.410> you<00:14:27.500> have<00:14:27.530> all<00:14:27.740> these 00:14:27.880 --> 00:14:27.890 align:start position:0% your phone thankfully you have all these 00:14:27.890 --> 00:14:30.370 align:start position:0% your phone thankfully you have all these other<00:14:27.950> keys<00:14:28.640> that<00:14:28.880> you<00:14:28.940> can<00:14:29.000> build<00:14:29.300> your<00:14:30.020> your 00:14:30.370 --> 00:14:30.380 align:start position:0% other keys that you can build your your 00:14:30.380 --> 00:14:32.320 align:start position:0% other keys that you can build your your next<00:14:30.530> phone<00:14:30.710> with<00:14:30.890> you<00:14:31.070> can<00:14:31.220> recover<00:14:31.460> your 00:14:32.320 --> 00:14:32.330 align:start position:0% next phone with you can recover your 00:14:32.330 --> 00:14:35.410 align:start position:0% next phone with you can recover your funds<00:14:32.630> through<00:14:33.470> through<00:14:34.250> a<00:14:34.700> social<00:14:35.120> recovery 00:14:35.410 --> 00:14:35.420 align:start position:0% funds through through a social recovery 00:14:35.420 --> 00:14:40.290 align:start position:0% funds through through a social recovery process<00:14:36.730> and<00:14:37.730> again<00:14:38.480> this<00:14:38.930> this<00:14:39.500> system<00:14:39.830> has<00:14:39.980> a 00:14:40.290 --> 00:14:40.300 align:start position:0% process and again this this system has a 00:14:40.300 --> 00:14:43.030 align:start position:0% process and again this this system has a lot<00:14:41.300> of<00:14:41.630> possibilities<00:14:42.410> that<00:14:42.440> have<00:14:42.650> yet<00:14:42.740> to<00:14:42.800> be 00:14:43.030 --> 00:14:43.040 align:start position:0% lot of possibilities that have yet to be 00:14:43.040 --> 00:14:45.960 align:start position:0% lot of possibilities that have yet to be developed<00:14:43.220> in<00:14:43.610> terms<00:14:43.790> of<00:14:44.150> a<00:14:44.590> planking<00:14:45.590> and 00:14:45.960 --> 00:14:45.970 align:start position:0% developed in terms of a planking and 00:14:45.970 --> 00:14:49.750 align:start position:0% developed in terms of a planking and recovery<00:14:46.970> flows<00:14:47.620> so<00:14:48.620> if<00:14:49.280> you're<00:14:49.550> interested 00:14:49.750 --> 00:14:49.760 align:start position:0% recovery flows so if you're interested 00:14:49.760 --> 00:14:51.250 align:start position:0% recovery flows so if you're interested in<00:14:50.060> sort<00:14:50.330> of<00:14:50.360> building<00:14:50.720> that<00:14:50.810> kind<00:14:51.020> of<00:14:51.080> stuff 00:14:51.250 --> 00:14:51.260 align:start position:0% in sort of building that kind of stuff 00:14:51.260 --> 00:14:55.240 align:start position:0% in sort of building that kind of stuff please<00:14:51.500> come<00:14:51.830> talk<00:14:51.950> to<00:14:52.010> me<00:14:52.100> after<00:14:52.340> this<00:14:53.620> and<00:14:54.620> so 00:14:55.240 --> 00:14:55.250 align:start position:0% please come talk to me after this and so 00:14:55.250 --> 00:14:56.350 align:start position:0% please come talk to me after this and so this<00:14:55.370> kind<00:14:55.490> of<00:14:55.610> comes<00:14:55.730> on<00:14:55.850> to<00:14:55.940> incremental 00:14:56.350 --> 00:14:56.360 align:start position:0% this kind of comes on to incremental 00:14:56.360 --> 00:14:58.270 align:start position:0% this kind of comes on to incremental decentralisation<00:14:56.780> again<00:14:57.320> you<00:14:57.770> want<00:14:58.220> to 00:14:58.270 --> 00:14:58.280 align:start position:0% decentralisation again you want to 00:14:58.280 --> 00:14:59.740 align:start position:0% decentralisation again you want to soften<00:14:58.520> landing<00:14:58.880> pad<00:14:59.000> for<00:14:59.180> users<00:14:59.450> to<00:14:59.570> come 00:14:59.740 --> 00:14:59.750 align:start position:0% soften landing pad for users to come 00:14:59.750 --> 00:15:00.820 align:start position:0% soften landing pad for users to come into<00:14:59.900> the<00:15:00.050> ecosystem<00:15:00.530> and<00:15:00.620> sort<00:15:00.800> of 00:15:00.820 --> 00:15:00.830 align:start position:0% into the ecosystem and sort of 00:15:00.830 --> 00:15:02.860 align:start position:0% into the ecosystem and sort of understand<00:15:01.370> what's<00:15:01.550> going<00:15:01.820> on<00:15:01.970> before<00:15:02.540> you 00:15:02.860 --> 00:15:02.870 align:start position:0% understand what's going on before you 00:15:02.870 --> 00:15:07.090 align:start position:0% understand what's going on before you just<00:15:03.050> put<00:15:03.650> them<00:15:03.740> in<00:15:03.800> the<00:15:03.920> deep<00:15:04.070> end<00:15:04.180> and<00:15:06.100> that 00:15:07.090 --> 00:15:07.100 align:start position:0% just put them in the deep end and that 00:15:07.100 --> 00:15:09.130 align:start position:0% just put them in the deep end and that comes<00:15:07.700> down<00:15:07.790> to<00:15:07.910> sort<00:15:08.270> of<00:15:08.300> providing<00:15:09.050> that 00:15:09.130 --> 00:15:09.140 align:start position:0% comes down to sort of providing that 00:15:09.140 --> 00:15:11.980 align:start position:0% comes down to sort of providing that layer<00:15:09.470> of<00:15:09.500> trust<00:15:10.070> and<00:15:10.370> sort<00:15:10.700> of<00:15:10.990> onboarding 00:15:11.980 --> 00:15:11.990 align:start position:0% layer of trust and sort of onboarding 00:15:11.990 --> 00:15:13.570 align:start position:0% layer of trust and sort of onboarding them<00:15:12.110> into<00:15:12.290> something<00:15:12.470> that<00:15:12.890> looks<00:15:13.040> familiar 00:15:13.570 --> 00:15:13.580 align:start position:0% them into something that looks familiar 00:15:13.580 --> 00:15:15.550 align:start position:0% them into something that looks familiar while<00:15:14.030> also<00:15:14.270> giving<00:15:14.630> them<00:15:14.720> full<00:15:15.050> access<00:15:15.230> of 00:15:15.550 --> 00:15:15.560 align:start position:0% while also giving them full access of 00:15:15.560 --> 00:15:20.350 align:start position:0% while also giving them full access of their<00:15:15.680> funds<00:15:16.240> but<00:15:17.240> but<00:15:18.200> not<00:15:18.410> not<00:15:19.400> showing<00:15:20.240> them 00:15:20.350 --> 00:15:20.360 align:start position:0% their funds but but not not showing them 00:15:20.360 --> 00:15:22.410 align:start position:0% their funds but but not not showing them a<00:15:20.390> completely<00:15:20.930> new<00:15:21.170> system<00:15:21.410> at<00:15:21.860> the<00:15:21.980> beginning 00:15:22.410 --> 00:15:22.420 align:start position:0% a completely new system at the beginning 00:15:22.420 --> 00:15:26.680 align:start position:0% a completely new system at the beginning and<00:15:23.420> this<00:15:24.410> also<00:15:24.650> to<00:15:25.550> some<00:15:25.730> extent<00:15:26.060> I<00:15:26.210> think 00:15:26.680 --> 00:15:26.690 align:start position:0% and this also to some extent I think 00:15:26.690 --> 00:15:28.950 align:start position:0% and this also to some extent I think that<00:15:27.110> DAPs 00:15:28.950 --> 00:15:28.960 align:start position:0% that DAPs 00:15:28.960 --> 00:15:31.600 align:start position:0% that DAPs full<00:15:29.960> decentralized<00:15:30.920> full<00:15:31.400> stack 00:15:31.600 --> 00:15:31.610 align:start position:0% full decentralized full stack 00:15:31.610 --> 00:15:32.970 align:start position:0% full decentralized full stack decentralized<00:15:32.120> apps 00:15:32.970 --> 00:15:32.980 align:start position:0% decentralized apps 00:15:32.980 --> 00:15:35.040 align:start position:0% decentralized apps have<00:15:33.220> a<00:15:33.250> very<00:15:33.700> simple<00:15:34.269> chance<00:15:34.480> of<00:15:34.660> actually 00:15:35.040 --> 00:15:35.050 align:start position:0% have a very simple chance of actually 00:15:35.050 --> 00:15:37.050 align:start position:0% have a very simple chance of actually succeeding<00:15:35.260> in<00:15:35.920> the<00:15:35.980> near<00:15:36.130> term<00:15:36.339> it's<00:15:36.880> more 00:15:37.050 --> 00:15:37.060 align:start position:0% succeeding in the near term it's more 00:15:37.060 --> 00:15:39.150 align:start position:0% succeeding in the near term it's more about<00:15:37.209> like<00:15:37.360> aetherium<00:15:37.930> applications<00:15:38.560> where 00:15:39.150 --> 00:15:39.160 align:start position:0% about like aetherium applications where 00:15:39.160 --> 00:15:41.280 align:start position:0% about like aetherium applications where you<00:15:39.190> have<00:15:39.370> hybrid<00:15:39.670> solutions<00:15:40.300> that<00:15:40.899> are<00:15:40.990> using 00:15:41.280 --> 00:15:41.290 align:start position:0% you have hybrid solutions that are using 00:15:41.290 --> 00:15:44.250 align:start position:0% you have hybrid solutions that are using like<00:15:41.410> AWS<00:15:41.800> and<00:15:42.070> firebase<00:15:42.399> or<00:15:42.930> you<00:15:43.930> know<00:15:44.019> other 00:15:44.250 --> 00:15:44.260 align:start position:0% like AWS and firebase or you know other 00:15:44.260 --> 00:15:48.360 align:start position:0% like AWS and firebase or you know other sort<00:15:44.740> of<00:15:44.769> like<00:15:45.570> Simpsons<00:15:46.570> to<00:15:47.050> get<00:15:47.290> things<00:15:47.709> that 00:15:48.360 --> 00:15:48.370 align:start position:0% sort of like Simpsons to get things that 00:15:48.370 --> 00:15:52.259 align:start position:0% sort of like Simpsons to get things that people<00:15:48.639> want<00:15:49.000> to<00:15:49.060> use<00:15:50.639> the<00:15:51.639> second<00:15:52.000> piece<00:15:52.240> of 00:15:52.259 --> 00:15:52.269 align:start position:0% people want to use the second piece of 00:15:52.269 --> 00:15:54.269 align:start position:0% people want to use the second piece of the<00:15:52.660> onboarding<00:15:53.139> puzzle<00:15:53.440> is<00:15:53.529> Fiat<00:15:53.829> ramps<00:15:54.160> of 00:15:54.269 --> 00:15:54.279 align:start position:0% the onboarding puzzle is Fiat ramps of 00:15:54.279 --> 00:15:57.620 align:start position:0% the onboarding puzzle is Fiat ramps of course<00:15:54.490> and<00:15:54.820> you<00:15:55.389> have<00:15:55.420> like<00:15:55.660> wire<00:15:56.260> moon<00:15:56.560> pay 00:15:57.620 --> 00:15:57.630 align:start position:0% course and you have like wire moon pay 00:15:57.630 --> 00:16:00.150 align:start position:0% course and you have like wire moon pay ramp<00:15:58.630> Network<00:15:59.019> and<00:15:59.380> carbon<00:15:59.800> all<00:16:00.010> these 00:16:00.150 --> 00:16:00.160 align:start position:0% ramp Network and carbon all these 00:16:00.160 --> 00:16:01.949 align:start position:0% ramp Network and carbon all these different<00:16:00.519> solutions<00:16:01.360> that<00:16:01.600> I<00:16:01.660> think<00:16:01.839> they're 00:16:01.949 --> 00:16:01.959 align:start position:0% different solutions that I think they're 00:16:01.959 --> 00:16:03.269 align:start position:0% different solutions that I think they're all<00:16:02.050> sort<00:16:02.290> of<00:16:02.350> competing<00:16:02.649> the<00:16:02.800> same<00:16:03.010> space 00:16:03.269 --> 00:16:03.279 align:start position:0% all sort of competing the same space 00:16:03.279 --> 00:16:04.259 align:start position:0% all sort of competing the same space it's<00:16:03.490> really<00:16:03.699> great<00:16:03.820> that<00:16:03.880> that's<00:16:04.120> a 00:16:04.259 --> 00:16:04.269 align:start position:0% it's really great that that's a 00:16:04.269 --> 00:16:07.019 align:start position:0% it's really great that that's a competitive<00:16:04.930> area<00:16:05.380> right<00:16:06.130> now<00:16:06.279> and<00:16:06.490> then 00:16:07.019 --> 00:16:07.029 align:start position:0% competitive area right now and then 00:16:07.029 --> 00:16:10.199 align:start position:0% competitive area right now and then lastly<00:16:07.779> if<00:16:08.110> you<00:16:08.230> have<00:16:08.260> apps<00:16:08.860> you<00:16:09.610> need<00:16:09.880> off 00:16:10.199 --> 00:16:10.209 align:start position:0% lastly if you have apps you need off 00:16:10.209 --> 00:16:13.980 align:start position:0% lastly if you have apps you need off chains<00:16:10.720> actions<00:16:11.490> if<00:16:12.490> you<00:16:12.910> have<00:16:13.089> users<00:16:13.540> or<00:16:13.810> on 00:16:13.980 --> 00:16:13.990 align:start position:0% chains actions if you have users or on 00:16:13.990 --> 00:16:15.689 align:start position:0% chains actions if you have users or on your<00:16:14.199> app<00:16:14.350> you<00:16:14.620> you<00:16:14.800> likely<00:16:15.250> need<00:16:15.310> all<00:16:15.459> Change 00:16:15.689 --> 00:16:15.699 align:start position:0% your app you you likely need all Change 00:16:15.699 --> 00:16:17.189 align:start position:0% your app you you likely need all Change transactions<00:16:16.240> in<00:16:16.360> order<00:16:16.540> to<00:16:16.630> make<00:16:16.779> a<00:16:16.810> seamless 00:16:17.189 --> 00:16:17.199 align:start position:0% transactions in order to make a seamless 00:16:17.199 --> 00:16:18.960 align:start position:0% transactions in order to make a seamless experience<00:16:17.380> and<00:16:18.279> all<00:16:18.430> these<00:16:18.579> teams<00:16:18.760> are<00:16:18.880> doing 00:16:18.960 --> 00:16:18.970 align:start position:0% experience and all these teams are doing 00:16:18.970 --> 00:16:21.449 align:start position:0% experience and all these teams are doing a<00:16:19.089> lot<00:16:19.240> of<00:16:19.360> really<00:16:19.570> great<00:16:19.720> work<00:16:20.130> to<00:16:21.130> provide 00:16:21.449 --> 00:16:21.459 align:start position:0% a lot of really great work to provide 00:16:21.459 --> 00:16:23.850 align:start position:0% a lot of really great work to provide like<00:16:21.699> fully<00:16:22.089> decentralized<00:16:22.300> solutions<00:16:22.990> for 00:16:23.850 --> 00:16:23.860 align:start position:0% like fully decentralized solutions for 00:16:23.860 --> 00:16:26.519 align:start position:0% like fully decentralized solutions for days<00:16:23.980> off<00:16:24.130> change<00:16:24.339> transactions<00:16:25.199> at<00:16:26.199> abridge 00:16:26.519 --> 00:16:26.529 align:start position:0% days off change transactions at abridge 00:16:26.529 --> 00:16:29.879 align:start position:0% days off change transactions at abridge we<00:16:26.769> actually<00:16:27.310> have<00:16:27.490> a<00:16:27.519> off<00:16:28.060> chain<00:16:28.769> system<00:16:29.769> as 00:16:29.879 --> 00:16:29.889 align:start position:0% we actually have a off chain system as 00:16:29.889 --> 00:16:31.199 align:start position:0% we actually have a off chain system as well<00:16:30.040> but<00:16:30.279> but<00:16:30.550> it<00:16:30.670> does<00:16:30.790> have<00:16:30.910> a<00:16:30.940> degree<00:16:31.180> of 00:16:31.199 --> 00:16:31.209 align:start position:0% well but but it does have a degree of 00:16:31.209 --> 00:16:34.470 align:start position:0% well but but it does have a degree of trust<00:16:31.480> it's<00:16:32.079> using<00:16:32.380> a<00:16:32.440> central<00:16:32.769> hub<00:16:33.389> that<00:16:34.389> you 00:16:34.470 --> 00:16:34.480 align:start position:0% trust it's using a central hub that you 00:16:34.480 --> 00:16:35.819 align:start position:0% trust it's using a central hub that you could<00:16:34.720> potentially<00:16:34.930> conclude<00:16:35.350> with<00:16:35.529> there's 00:16:35.819 --> 00:16:35.829 align:start position:0% could potentially conclude with there's 00:16:35.829 --> 00:16:38.000 align:start position:0% could potentially conclude with there's I'm<00:16:36.040> not<00:16:36.070> going<00:16:36.279> to<00:16:36.339> get<00:16:36.459> too<00:16:36.790> deep<00:16:37.209> into<00:16:37.390> that 00:16:38.000 --> 00:16:38.010 align:start position:0% I'm not going to get too deep into that 00:16:38.010 --> 00:16:40.199 align:start position:0% I'm not going to get too deep into that but<00:16:39.010> that's<00:16:39.610> that's<00:16:39.850> kind<00:16:40.029> of<00:16:40.089> like 00:16:40.199 --> 00:16:40.209 align:start position:0% but that's that's kind of like 00:16:40.209 --> 00:16:44.189 align:start position:0% but that's that's kind of like essentially<00:16:41.050> the<00:16:41.290> the<00:16:41.620> idea<00:16:42.029> and<00:16:43.029> so<00:16:43.630> to<00:16:43.990> fix 00:16:44.189 --> 00:16:44.199 align:start position:0% essentially the the idea and so to fix 00:16:44.199 --> 00:16:46.050 align:start position:0% essentially the the idea and so to fix the<00:16:44.290> UX<00:16:44.470> issues<00:16:44.620> again<00:16:45.100> you<00:16:45.850> just<00:16:45.940> need 00:16:46.050 --> 00:16:46.060 align:start position:0% the UX issues again you just need 00:16:46.060 --> 00:16:47.910 align:start position:0% the UX issues again you just need onboarding<00:16:46.660> and<00:16:46.810> enough<00:16:47.290> chain<00:16:47.470> transaction 00:16:47.910 --> 00:16:47.920 align:start position:0% onboarding and enough chain transaction 00:16:47.920 --> 00:16:49.860 align:start position:0% onboarding and enough chain transaction so<00:16:48.010> that's<00:16:48.130> kind<00:16:48.339> of<00:16:48.430> the<00:16:49.209> combination<00:16:49.480> that 00:16:49.860 --> 00:16:49.870 align:start position:0% so that's kind of the combination that 00:16:49.870 --> 00:16:51.780 align:start position:0% so that's kind of the combination that you<00:16:50.560> need<00:16:50.949> in<00:16:51.100> order<00:16:51.190> to<00:16:51.310> make<00:16:51.490> a<00:16:51.519> seamless 00:16:51.780 --> 00:16:51.790 align:start position:0% you need in order to make a seamless 00:16:51.790 --> 00:16:54.780 align:start position:0% you need in order to make a seamless application<00:16:52.420> flow<00:16:53.170> and<00:16:54.040> if<00:16:54.130> you<00:16:54.220> want<00:16:54.430> to<00:16:54.519> see 00:16:54.780 --> 00:16:54.790 align:start position:0% application flow and if you want to see 00:16:54.790 --> 00:16:57.750 align:start position:0% application flow and if you want to see another<00:16:55.209> example<00:16:55.660> you<00:16:56.500> can<00:16:56.680> like<00:16:57.040> scan<00:16:57.519> this 00:16:57.750 --> 00:16:57.760 align:start position:0% another example you can like scan this 00:16:57.760 --> 00:17:00.290 align:start position:0% another example you can like scan this app<00:16:58.449> this<00:16:58.630> is<00:16:58.720> actually<00:16:59.019> a<00:16:59.079> native<00:16:59.410> mobile<00:16:59.560> app 00:17:00.290 --> 00:17:00.300 align:start position:0% app this is actually a native mobile app 00:17:00.300 --> 00:17:03.240 align:start position:0% app this is actually a native mobile app I<00:17:01.300> don't<00:17:01.810> know<00:17:01.959> like<00:17:02.680> how<00:17:02.829> many<00:17:02.920> people<00:17:03.160> have 00:17:03.240 --> 00:17:03.250 align:start position:0% I don't know like how many people have 00:17:03.250 --> 00:17:04.439 align:start position:0% I don't know like how many people have actually<00:17:03.370> used<00:17:03.699> like<00:17:03.880> a<00:17:03.910> native<00:17:04.240> mobile 00:17:04.439 --> 00:17:04.449 align:start position:0% actually used like a native mobile 00:17:04.449 --> 00:17:07.110 align:start position:0% actually used like a native mobile aetherium<00:17:04.929> app<00:17:05.020> that's<00:17:05.199> not<00:17:05.380> a<00:17:05.410> wallet<00:17:06.120> anyone 00:17:07.110 --> 00:17:07.120 align:start position:0% aetherium app that's not a wallet anyone 00:17:07.120 --> 00:17:11.549 align:start position:0% aetherium app that's not a wallet anyone ok<00:17:08.079> sweet<00:17:08.949> couple<00:17:09.939> all<00:17:10.720> right 00:17:11.549 --> 00:17:11.559 align:start position:0% ok sweet couple all right 00:17:11.559 --> 00:17:13.289 align:start position:0% ok sweet couple all right so<00:17:11.949> but<00:17:12.339> this<00:17:12.400> is<00:17:12.459> a<00:17:12.549> native<00:17:12.669> mobile<00:17:12.880> app<00:17:13.059> that 00:17:13.289 --> 00:17:13.299 align:start position:0% so but this is a native mobile app that 00:17:13.299 --> 00:17:18.210 align:start position:0% so but this is a native mobile app that has<00:17:14.429> a<00:17:16.199> account<00:17:17.199> contract<00:17:17.679> as<00:17:17.799> well<00:17:17.829> as<00:17:18.069> the 00:17:18.210 --> 00:17:18.220 align:start position:0% has a account contract as well as the 00:17:18.220 --> 00:17:20.309 align:start position:0% has a account contract as well as the bridge<00:17:18.730> sort<00:17:19.059> of<00:17:19.150> off<00:17:19.449> chain<00:17:19.900> solution 00:17:20.309 --> 00:17:20.319 align:start position:0% bridge sort of off chain solution 00:17:20.319 --> 00:17:22.500 align:start position:0% bridge sort of off chain solution integrated<00:17:21.160> into<00:17:21.309> it<00:17:21.429> that<00:17:21.760> you<00:17:21.880> can<00:17:22.030> sort<00:17:22.449> of 00:17:22.500 --> 00:17:22.510 align:start position:0% integrated into it that you can sort of 00:17:22.510 --> 00:17:23.789 align:start position:0% integrated into it that you can sort of play<00:17:22.630> around<00:17:22.660> with<00:17:22.900> it's<00:17:23.350> like<00:17:23.559> social 00:17:23.789 --> 00:17:23.799 align:start position:0% play around with it's like social 00:17:23.799 --> 00:17:30.539 align:start position:0% play around with it's like social tipping<00:17:24.459> for<00:17:25.120> content<00:17:28.350> so<00:17:29.350> the<00:17:30.160> takeaways 00:17:30.539 --> 00:17:30.549 align:start position:0% tipping for content so the takeaways 00:17:30.549 --> 00:17:32.640 align:start position:0% tipping for content so the takeaways here<00:17:30.630> the<00:17:31.630> theorem<00:17:31.870> is<00:17:31.960> really<00:17:32.230> difficult<00:17:32.530> to 00:17:32.640 --> 00:17:32.650 align:start position:0% here the theorem is really difficult to 00:17:32.650 --> 00:17:35.580 align:start position:0% here the theorem is really difficult to use<00:17:32.679> for<00:17:33.280> a<00:17:34.150> lot<00:17:34.480> of<00:17:34.540> reasons 00:17:35.580 --> 00:17:35.590 align:start position:0% use for a lot of reasons 00:17:35.590 --> 00:17:37.590 align:start position:0% use for a lot of reasons while<00:17:36.400> decentralization<00:17:36.970> is<00:17:37.179> really<00:17:37.450> really 00:17:37.590 --> 00:17:37.600 align:start position:0% while decentralization is really really 00:17:37.600 --> 00:17:40.230 align:start position:0% while decentralization is really really important<00:17:38.049> it<00:17:38.169> also<00:17:38.370> inhibits<00:17:39.370> to<00:17:40.059> some 00:17:40.230 --> 00:17:40.240 align:start position:0% important it also inhibits to some 00:17:40.240 --> 00:17:42.960 align:start position:0% important it also inhibits to some extent<00:17:40.570> user<00:17:41.350> adoption<00:17:41.650> if<00:17:42.070> it's<00:17:42.429> going<00:17:42.700> to<00:17:42.820> be 00:17:42.960 --> 00:17:42.970 align:start position:0% extent user adoption if it's going to be 00:17:42.970 --> 00:17:45.000 align:start position:0% extent user adoption if it's going to be taken<00:17:43.630> to<00:17:43.659> the<00:17:43.809> nth<00:17:43.929> degree<00:17:44.080> from<00:17:44.799> the 00:17:45.000 --> 00:17:45.010 align:start position:0% taken to the nth degree from the 00:17:45.010 --> 00:17:47.550 align:start position:0% taken to the nth degree from the beginning<00:17:45.810> there's<00:17:46.810> also<00:17:46.930> really<00:17:47.500> difficult 00:17:47.550 --> 00:17:47.560 align:start position:0% beginning there's also really difficult 00:17:47.560 --> 00:17:50.250 align:start position:0% beginning there's also really difficult tools<00:17:48.240> under<00:17:49.240> developed<00:17:49.600> tools<00:17:49.780> to<00:17:50.110> use 00:17:50.250 --> 00:17:50.260 align:start position:0% tools under developed tools to use 00:17:50.260 --> 00:17:52.340 align:start position:0% tools under developed tools to use within<00:17:50.590> the<00:17:50.800> ecosystem<00:17:51.010> to<00:17:51.310> develop<00:17:51.850> these 00:17:52.340 --> 00:17:52.350 align:start position:0% within the ecosystem to develop these 00:17:52.350 --> 00:17:54.810 align:start position:0% within the ecosystem to develop these applications<00:17:53.350> and<00:17:53.590> we<00:17:53.950> have<00:17:54.070> no<00:17:54.220> user<00:17:54.430> data<00:17:54.670> to 00:17:54.810 --> 00:17:54.820 align:start position:0% applications and we have no user data to 00:17:54.820 --> 00:17:57.540 align:start position:0% applications and we have no user data to actually<00:17:55.120> say<00:17:55.330> what<00:17:56.200> tools<00:17:56.530> are<00:17:56.830> really 00:17:57.540 --> 00:17:57.550 align:start position:0% actually say what tools are really 00:17:57.550 --> 00:18:07.020 align:start position:0% actually say what tools are really useful<00:17:57.940> right<00:17:59.730> the<00:18:01.230> okay<00:18:02.230> the<00:18:03.090> need<00:18:04.090> to<00:18:06.030> create 00:18:07.020 --> 00:18:07.030 align:start position:0% useful right the okay the need to create 00:18:07.030 --> 00:18:08.760 align:start position:0% useful right the okay the need to create trust<00:18:07.420> right<00:18:07.750> we<00:18:07.840> need<00:18:07.960> to<00:18:08.050> create<00:18:08.260> trust<00:18:08.530> for 00:18:08.760 --> 00:18:08.770 align:start position:0% trust right we need to create trust for 00:18:08.770 --> 00:18:10.950 align:start position:0% trust right we need to create trust for the<00:18:08.830> end-users<00:18:09.310> through<00:18:10.180> more<00:18:10.570> intuitive 00:18:10.950 --> 00:18:10.960 align:start position:0% the end-users through more intuitive 00:18:10.960 --> 00:18:12.270 align:start position:0% the end-users through more intuitive design<00:18:11.050> to<00:18:11.350> make<00:18:11.440> it<00:18:11.620> convenient<00:18:12.130> and 00:18:12.270 --> 00:18:12.280 align:start position:0% design to make it convenient and 00:18:12.280 --> 00:18:14.690 align:start position:0% design to make it convenient and comfortable<00:18:12.430> and<00:18:12.910> programmable<00:18:13.600> access<00:18:14.260> is 00:18:14.690 --> 00:18:14.700 align:start position:0% comfortable and programmable access is 00:18:14.700 --> 00:18:18.530 align:start position:0% comfortable and programmable access is potentially<00:18:15.700> a<00:18:15.910> way<00:18:16.240> in<00:18:16.990> which<00:18:17.290> to<00:18:17.410> do<00:18:17.500> this 00:18:18.530 --> 00:18:18.540 align:start position:0% potentially a way in which to do this 00:18:18.540 --> 00:18:22.890 align:start position:0% potentially a way in which to do this through<00:18:19.540> account<00:18:19.780> contracts<00:18:20.190> and<00:18:21.190> so<00:18:21.490> I<00:18:21.900> sort 00:18:22.890 --> 00:18:22.900 align:start position:0% through account contracts and so I sort 00:18:22.900 --> 00:18:25.050 align:start position:0% through account contracts and so I sort of<00:18:22.960> been<00:18:23.110> proposing<00:18:23.620> the<00:18:24.280> ecosystem<00:18:24.790> should 00:18:25.050 --> 00:18:25.060 align:start position:0% of been proposing the ecosystem should 00:18:25.060 --> 00:18:29.040 align:start position:0% of been proposing the ecosystem should spend<00:18:25.390> about<00:18:25.600> as<00:18:25.810> much<00:18:25.960> time<00:18:26.200> on<00:18:26.670> this<00:18:27.670> issue 00:18:29.040 --> 00:18:29.050 align:start position:0% spend about as much time on this issue 00:18:29.050 --> 00:18:32.000 align:start position:0% spend about as much time on this issue maybe<00:18:30.040> not<00:18:30.220> as<00:18:30.400> much<00:18:30.670> obviously<00:18:31.120> I<00:18:31.210> think<00:18:31.360> the 00:18:32.000 --> 00:18:32.010 align:start position:0% maybe not as much obviously I think the 00:18:32.010 --> 00:18:35.190 align:start position:0% maybe not as much obviously I think the nuances<00:18:33.010> of<00:18:33.340> connecting<00:18:34.330> 82.0<00:18:34.870> is<00:18:34.990> going<00:18:35.140> to 00:18:35.190 --> 00:18:35.200 align:start position:0% nuances of connecting 82.0 is going to 00:18:35.200 --> 00:18:36.900 align:start position:0% nuances of connecting 82.0 is going to be<00:18:35.290> quite<00:18:36.280> a<00:18:36.310> task 00:18:36.900 --> 00:18:36.910 align:start position:0% be quite a task 00:18:36.910 --> 00:18:39.540 align:start position:0% be quite a task but<00:18:37.480> getting<00:18:38.320> nailing<00:18:38.770> down<00:18:38.890> this<00:18:39.070> flow<00:18:39.310> also 00:18:39.540 --> 00:18:39.550 align:start position:0% but getting nailing down this flow also 00:18:39.550 --> 00:18:40.890 align:start position:0% but getting nailing down this flow also requires<00:18:39.970> a<00:18:40.060> significant<00:18:40.480> amount<00:18:40.660> of<00:18:40.720> effort 00:18:40.890 --> 00:18:40.900 align:start position:0% requires a significant amount of effort 00:18:40.900 --> 00:18:43.950 align:start position:0% requires a significant amount of effort and<00:18:41.200> iteration<00:18:42.190> and<00:18:43.150> it<00:18:43.330> won't<00:18:43.750> happen 00:18:43.950 --> 00:18:43.960 align:start position:0% and iteration and it won't happen 00:18:43.960 --> 00:18:45.170 align:start position:0% and iteration and it won't happen overnight 00:18:45.170 --> 00:18:45.180 align:start position:0% overnight 00:18:45.180 --> 00:18:47.850 align:start position:0% overnight we<00:18:46.180> need<00:18:46.330> sort<00:18:46.750> of<00:18:46.810> I'm<00:18:47.020> sort<00:18:47.470> of<00:18:47.500> encouraging 00:18:47.850 --> 00:18:47.860 align:start position:0% we need sort of I'm sort of encouraging 00:18:47.860 --> 00:18:49.560 align:start position:0% we need sort of I'm sort of encouraging pragmatic<00:18:48.340> development<00:18:48.820> and<00:18:49.000> hybrid 00:18:49.560 --> 00:18:49.570 align:start position:0% pragmatic development and hybrid 00:18:49.570 --> 00:18:52.560 align:start position:0% pragmatic development and hybrid architectures<00:18:50.160> and<00:18:51.160> sort<00:18:51.820> of<00:18:51.910> continuing<00:18:52.540> to 00:18:52.560 --> 00:18:52.570 align:start position:0% architectures and sort of continuing to 00:18:52.570 --> 00:18:54.930 align:start position:0% architectures and sort of continuing to ship<00:18:52.870> solutions<00:18:53.860> to<00:18:54.040> gather<00:18:54.220> that<00:18:54.430> user 00:18:54.930 --> 00:18:54.940 align:start position:0% ship solutions to gather that user 00:18:54.940 --> 00:18:58.650 align:start position:0% ship solutions to gather that user feedback<00:18:55.180> and<00:18:56.280> and<00:18:57.280> sort<00:18:57.430> of<00:18:57.520> focus<00:18:58.090> on<00:18:58.210> end 00:18:58.650 --> 00:18:58.660 align:start position:0% feedback and and sort of focus on end 00:18:58.660 --> 00:19:03.270 align:start position:0% feedback and and sort of focus on end users<00:18:59.520> rather<00:19:00.520> than<00:19:00.820> maybe<00:19:01.390> the<00:19:02.350> most 00:19:03.270 --> 00:19:03.280 align:start position:0% users rather than maybe the most 00:19:03.280 --> 00:19:07.590 align:start position:0% users rather than maybe the most idealistic<00:19:03.840> situation<00:19:04.840> possible<00:19:06.000> so<00:19:07.000> that's 00:19:07.590 --> 00:19:07.600 align:start position:0% idealistic situation possible so that's 00:19:07.600 --> 00:19:10.770 align:start position:0% idealistic situation possible so that's this<00:19:08.230> is<00:19:08.290> me<00:19:08.680> on<00:19:09.010> the<00:19:09.070> Twitter<00:19:09.520> and<00:19:09.780> it's 00:19:10.770 --> 00:19:10.780 align:start position:0% this is me on the Twitter and it's 00:19:10.780 --> 00:19:12.510 align:start position:0% this is me on the Twitter and it's abridged<00:19:11.200> if<00:19:11.800> you<00:19:11.890> want<00:19:12.040> to<00:19:12.100> check<00:19:12.220> out<00:19:12.370> what 00:19:12.510 --> 00:19:12.520 align:start position:0% abridged if you want to check out what 00:19:12.520 --> 00:19:13.970 align:start position:0% abridged if you want to check out what we're<00:19:12.640> doing 00:19:13.970 --> 00:19:13.980 align:start position:0% we're doing 00:19:13.980 --> 00:19:17.600 align:start position:0% we're doing yeah<00:19:14.980> that's<00:19:15.610> that'll<00:19:16.360> do 00:19:17.600 --> 00:19:17.610 align:start position:0% yeah that's that'll do 00:19:17.610 --> 00:19:27.700 align:start position:0% yeah that's that'll do [Applause] 00:19:27.700 --> 00:19:27.710 align:start position:0% 00:19:27.710 --> 00:19:29.770 align:start position:0% you