WEBVTT Kind: captions Language: en 00:00:05.800 --> 00:00:08.070 align:start position:0% thank<00:00:06.190> you<00:00:06.280> everybody<00:00:06.580> for<00:00:06.820> coming<00:00:07.360> and<00:00:07.630> one 00:00:08.070 --> 00:00:08.080 align:start position:0% thank you everybody for coming and one 00:00:08.080 --> 00:00:10.740 align:start position:0% thank you everybody for coming and one this<00:00:08.440> year<00:00:08.710> was<00:00:09.040> really<00:00:09.480> interesting<00:00:10.480> we<00:00:10.600> had 00:00:10.740 --> 00:00:10.750 align:start position:0% this year was really interesting we had 00:00:10.750 --> 00:00:13.020 align:start position:0% this year was really interesting we had so<00:00:11.110> many<00:00:11.380> so<00:00:11.650> many<00:00:11.830> amazing<00:00:12.070> submissions<00:00:12.790> and 00:00:13.020 --> 00:00:13.030 align:start position:0% so many so many amazing submissions and 00:00:13.030 --> 00:00:15.390 align:start position:0% so many so many amazing submissions and we're<00:00:13.930> really<00:00:14.110> excited<00:00:14.440> the<00:00:15.040> judges 00:00:15.390 --> 00:00:15.400 align:start position:0% we're really excited the judges 00:00:15.400 --> 00:00:17.580 align:start position:0% we're really excited the judges deliberated<00:00:16.000> till<00:00:16.390> maybe<00:00:16.779> 2<00:00:17.110> a.m.<00:00:17.380> yesterday 00:00:17.580 --> 00:00:17.590 align:start position:0% deliberated till maybe 2 a.m. yesterday 00:00:17.590 --> 00:00:20.120 align:start position:0% deliberated till maybe 2 a.m. yesterday so<00:00:18.580> it<00:00:18.670> was<00:00:18.820> really<00:00:19.119> really<00:00:19.270> tight<00:00:19.570> this<00:00:19.840> year 00:00:20.120 --> 00:00:20.130 align:start position:0% so it was really really tight this year 00:00:20.130 --> 00:00:22.229 align:start position:0% so it was really really tight this year one<00:00:21.130> of<00:00:21.160> the<00:00:21.310> criteria<00:00:21.790> is<00:00:21.820> that<00:00:22.029> we're<00:00:22.150> going 00:00:22.229 --> 00:00:22.239 align:start position:0% one of the criteria is that we're going 00:00:22.239 --> 00:00:24.060 align:start position:0% one of the criteria is that we're going to<00:00:22.329> discuss<00:00:22.660> in<00:00:22.900> the<00:00:23.050> panel<00:00:23.410> the<00:00:23.590> sessions<00:00:23.950> a 00:00:24.060 --> 00:00:24.070 align:start position:0% to discuss in the panel the sessions a 00:00:24.070 --> 00:00:25.800 align:start position:0% to discuss in the panel the sessions a little<00:00:24.310> different<00:00:24.669> from<00:00:24.790> last<00:00:24.970> year<00:00:25.300> we're 00:00:25.800 --> 00:00:25.810 align:start position:0% little different from last year we're 00:00:25.810 --> 00:00:27.780 align:start position:0% little different from last year we're gonna<00:00:25.900> have<00:00:26.200> a<00:00:26.230> panel<00:00:27.009> with<00:00:27.130> the<00:00:27.220> judges<00:00:27.640> to 00:00:27.780 --> 00:00:27.790 align:start position:0% gonna have a panel with the judges to 00:00:27.790 --> 00:00:29.790 align:start position:0% gonna have a panel with the judges to discuss<00:00:28.180> kind<00:00:28.480> of<00:00:28.570> the<00:00:28.660> state<00:00:28.899> of<00:00:29.079> UX<00:00:29.500> and 00:00:29.790 --> 00:00:29.800 align:start position:0% discuss kind of the state of UX and 00:00:29.800 --> 00:00:32.639 align:start position:0% discuss kind of the state of UX and design<00:00:29.829> as<00:00:30.310> well<00:00:30.939> as<00:00:31.110> and<00:00:32.110> we'll<00:00:32.320> kind<00:00:32.590> of 00:00:32.639 --> 00:00:32.649 align:start position:0% design as well as and we'll kind of 00:00:32.649 --> 00:00:34.560 align:start position:0% design as well as and we'll kind of touch<00:00:32.829> upon<00:00:32.950> all<00:00:33.370> these<00:00:33.520> points<00:00:34.300> of<00:00:34.480> the 00:00:34.560 --> 00:00:34.570 align:start position:0% touch upon all these points of the 00:00:34.570 --> 00:00:38.490 align:start position:0% touch upon all these points of the criteria<00:00:35.110> and<00:00:36.570> our<00:00:37.570> judges<00:00:37.840> I'm<00:00:38.230> really 00:00:38.490 --> 00:00:38.500 align:start position:0% criteria and our judges I'm really 00:00:38.500 --> 00:00:41.130 align:start position:0% criteria and our judges I'm really excited<00:00:38.710> to<00:00:38.920> introduce<00:00:38.950> we<00:00:39.580> have<00:00:39.880> Bennie<00:00:40.540> from 00:00:41.130 --> 00:00:41.140 align:start position:0% excited to introduce we have Bennie from 00:00:41.140 --> 00:00:48.860 align:start position:0% excited to introduce we have Bennie from Krypto<00:00:41.680> kitties<00:00:42.010> and<00:00:42.040> dapper<00:00:42.640> laughs<00:00:47.730> and 00:00:48.860 --> 00:00:48.870 align:start position:0% Krypto kitties and dapper laughs and 00:00:48.870 --> 00:00:52.650 align:start position:0% Krypto kitties and dapper laughs and then<00:00:49.870> we<00:00:50.050> have<00:00:50.260> Alex<00:00:50.770> from<00:00:51.130> coinbase<00:00:51.660> joining 00:00:52.650 --> 00:00:52.660 align:start position:0% then we have Alex from coinbase joining 00:00:52.660 --> 00:00:57.930 align:start position:0% then we have Alex from coinbase joining us<00:00:52.810> from<00:00:53.050> product<00:00:53.380> design<00:00:54.600> and<00:00:56.220> then<00:00:57.220> Graeme 00:00:57.930 --> 00:00:57.940 align:start position:0% us from product design and then Graeme 00:00:57.940 --> 00:00:59.640 align:start position:0% us from product design and then Graeme you<00:00:58.120> and<00:00:58.390> and<00:00:58.720> we're<00:00:58.990> actually<00:00:59.290> really 00:00:59.640 --> 00:00:59.650 align:start position:0% you and and we're actually really 00:00:59.650 --> 00:01:01.470 align:start position:0% you and and we're actually really excited<00:01:00.010> to<00:01:00.100> bring<00:01:00.190> back<00:01:00.430> RJ<00:01:00.820> RJ<00:01:01.030> was<00:01:01.300> the 00:01:01.470 --> 00:01:01.480 align:start position:0% excited to bring back RJ RJ was the 00:01:01.480 --> 00:01:02.819 align:start position:0% excited to bring back RJ RJ was the winner<00:01:01.660> of<00:01:01.990> one<00:01:02.200> of<00:01:02.230> the<00:01:02.380> winners<00:01:02.620> of<00:01:02.650> last 00:01:02.819 --> 00:01:02.829 align:start position:0% winner of one of the winners of last 00:01:02.829 --> 00:01:05.969 align:start position:0% winner of one of the winners of last year<00:01:03.370> and<00:01:03.550> so<00:01:04.329> they're<00:01:05.199> coming<00:01:05.560> back<00:01:05.680> as<00:01:05.950> a 00:01:05.969 --> 00:01:05.979 align:start position:0% year and so they're coming back as a 00:01:05.979 --> 00:01:08.370 align:start position:0% year and so they're coming back as a judge<00:01:06.549> and<00:01:06.939> it's<00:01:07.479> really<00:01:07.869> great<00:01:08.049> to<00:01:08.079> see<00:01:08.229> how 00:01:08.370 --> 00:01:08.380 align:start position:0% judge and it's really great to see how 00:01:08.380 --> 00:01:10.950 align:start position:0% judge and it's really great to see how far<00:01:08.799> everyone<00:01:09.219> has<00:01:09.249> come<00:01:09.549> and<00:01:09.789> ramie<00:01:10.390> uh<00:01:10.509> the 00:01:10.950 --> 00:01:10.960 align:start position:0% far everyone has come and ramie uh the 00:01:10.960 --> 00:01:12.690 align:start position:0% far everyone has come and ramie uh the UX<00:01:11.229> design<00:01:11.560> director<00:01:11.920> is<00:01:12.009> not<00:01:12.159> here<00:01:12.340> today<00:01:12.640> but 00:01:12.690 --> 00:01:12.700 align:start position:0% UX design director is not here today but 00:01:12.700 --> 00:01:14.669 align:start position:0% UX design director is not here today but we<00:01:12.969> have<00:01:13.119> Jillian<00:01:14.020> who<00:01:14.200> is<00:01:14.350> one<00:01:14.499> of<00:01:14.590> the 00:01:14.669 --> 00:01:14.679 align:start position:0% we have Jillian who is one of the 00:01:14.679 --> 00:01:22.649 align:start position:0% we have Jillian who is one of the cofounders<00:01:14.829> of<00:01:15.219> Arjun<00:01:20.999> so<00:01:21.999> we're<00:01:22.179> gonna<00:01:22.299> start 00:01:22.649 --> 00:01:22.659 align:start position:0% cofounders of Arjun so we're gonna start 00:01:22.659 --> 00:01:25.039 align:start position:0% cofounders of Arjun so we're gonna start this<00:01:22.840> panel<00:01:23.380> of<00:01:23.649> just<00:01:24.039> kind<00:01:24.249> of<00:01:24.280> talking<00:01:24.639> about 00:01:25.039 --> 00:01:25.049 align:start position:0% this panel of just kind of talking about 00:01:25.049 --> 00:01:27.959 align:start position:0% this panel of just kind of talking about where<00:01:26.049> are<00:01:26.319> we<00:01:26.619> in<00:01:26.770> the<00:01:26.920> same<00:01:27.130> Buicks<00:01:27.729> I<00:01:27.850> know 00:01:27.959 --> 00:01:27.969 align:start position:0% where are we in the same Buicks I know 00:01:27.969 --> 00:01:29.760 align:start position:0% where are we in the same Buicks I know you've<00:01:28.119> been<00:01:28.149> talking<00:01:28.389> a<00:01:28.689> lot<00:01:28.899> about<00:01:28.929> relaxed 00:01:29.760 --> 00:01:29.770 align:start position:0% you've been talking a lot about relaxed 00:01:29.770 --> 00:01:32.270 align:start position:0% you've been talking a lot about relaxed and<00:01:30.100> design<00:01:30.429> but<00:01:31.119> coming<00:01:31.450> from 00:01:32.270 --> 00:01:32.280 align:start position:0% and design but coming from 00:01:32.280 --> 00:01:34.370 align:start position:0% and design but coming from such<00:01:32.460> product-oriented<00:01:33.479> and<00:01:33.659> you<00:01:34.049> guys<00:01:34.200> have 00:01:34.370 --> 00:01:34.380 align:start position:0% such product-oriented and you guys have 00:01:34.380 --> 00:01:36.950 align:start position:0% such product-oriented and you guys have quite<00:01:34.680> a<00:01:34.920> suite<00:01:35.220> of<00:01:35.460> products<00:01:35.970> you<00:01:36.090> offer<00:01:36.420> you 00:01:36.950 --> 00:01:36.960 align:start position:0% quite a suite of products you offer you 00:01:36.960 --> 00:01:39.500 align:start position:0% quite a suite of products you offer you have<00:01:37.110> a<00:01:37.530> pro<00:01:37.920> you<00:01:38.250> have<00:01:38.280> you<00:01:38.790> guys<00:01:38.940> have<00:01:39.180> a<00:01:39.210> new 00:01:39.500 --> 00:01:39.510 align:start position:0% have a pro you have you guys have a new 00:01:39.510 --> 00:01:41.990 align:start position:0% have a pro you have you guys have a new blockchain<00:01:39.960> to<00:01:40.140> Alice<00:01:40.530> so<00:01:40.740> tell<00:01:41.310> us<00:01:41.340> when<00:01:41.880> you 00:01:41.990 --> 00:01:42.000 align:start position:0% blockchain to Alice so tell us when you 00:01:42.000 --> 00:01:43.999 align:start position:0% blockchain to Alice so tell us when you start<00:01:42.210> with<00:01:42.360> a<00:01:42.450> little<00:01:42.600> bit<00:01:42.780> of<00:01:42.930> where<00:01:43.830> do<00:01:43.920> you 00:01:43.999 --> 00:01:44.009 align:start position:0% start with a little bit of where do you 00:01:44.009 --> 00:01:45.410 align:start position:0% start with a little bit of where do you think<00:01:44.220> they<00:01:44.369> are<00:01:44.520> the<00:01:44.820> designs<00:01:45.180> to<00:01:45.360> be 00:01:45.410 --> 00:01:45.420 align:start position:0% think they are the designs to be 00:01:45.420 --> 00:01:48.950 align:start position:0% think they are the designs to be specifically<00:01:46.140> in<00:01:46.229> one<00:01:46.350> three<00:01:47.330> yeah<00:01:48.330> it's<00:01:48.780> a 00:01:48.950 --> 00:01:48.960 align:start position:0% specifically in one three yeah it's a 00:01:48.960 --> 00:01:53.660 align:start position:0% specifically in one three yeah it's a it's<00:01:49.619> very<00:01:50.130> interesting<00:01:51.680> coming<00:01:52.680> from<00:01:52.710> the 00:01:53.660 --> 00:01:53.670 align:start position:0% it's very interesting coming from the 00:01:53.670 --> 00:01:57.380 align:start position:0% it's very interesting coming from the game<00:01:53.909> space<00:01:54.330> we<00:01:54.840> have<00:01:55.200> almost<00:01:55.680> more<00:01:56.549> than<00:01:56.580> 50% 00:01:57.380 --> 00:01:57.390 align:start position:0% game space we have almost more than 50% 00:01:57.390 --> 00:02:00.289 align:start position:0% game space we have almost more than 50% of<00:01:57.479> the<00:01:57.630> company<00:01:58.530> is<00:01:58.740> focusing<00:01:59.369> on<00:01:59.580> the<00:02:00.119> game 00:02:00.289 --> 00:02:00.299 align:start position:0% of the company is focusing on the game 00:02:00.299 --> 00:02:03.980 align:start position:0% of the company is focusing on the game studio<00:02:00.690> side<00:02:00.990> so<00:02:01.799> designing<00:02:02.310> UX<00:02:02.940> and<00:02:03.330> UI<00:02:03.450> for 00:02:03.980 --> 00:02:03.990 align:start position:0% studio side so designing UX and UI for 00:02:03.990 --> 00:02:07.779 align:start position:0% studio side so designing UX and UI for games<00:02:04.710> is<00:02:05.100> much<00:02:05.670> more<00:02:05.910> different<00:02:06.240> from<00:02:06.270> defy 00:02:07.779 --> 00:02:07.789 align:start position:0% games is much more different from defy 00:02:07.789 --> 00:02:10.070 align:start position:0% games is much more different from defy fortunately<00:02:08.789> we<00:02:08.940> spend<00:02:09.179> a<00:02:09.269> lot<00:02:09.300> of<00:02:09.420> time<00:02:09.750> with 00:02:10.070 --> 00:02:10.080 align:start position:0% fortunately we spend a lot of time with 00:02:10.080 --> 00:02:12.410 align:start position:0% fortunately we spend a lot of time with our<00:02:10.380> top<00:02:10.769> players<00:02:11.070> of<00:02:11.370> crypto<00:02:11.700> P<00:02:11.850> DS<00:02:12.000> and 00:02:12.410 --> 00:02:12.420 align:start position:0% our top players of crypto P DS and 00:02:12.420 --> 00:02:15.080 align:start position:0% our top players of crypto P DS and cheese<00:02:12.660> wizards<00:02:13.050> or<00:02:13.290> new<00:02:13.440> game<00:02:13.680> and<00:02:14.040> we<00:02:14.820> get<00:02:14.970> to 00:02:15.080 --> 00:02:15.090 align:start position:0% cheese wizards or new game and we get to 00:02:15.090 --> 00:02:17.420 align:start position:0% cheese wizards or new game and we get to learn<00:02:15.239> a<00:02:15.300> lot<00:02:15.570> about<00:02:15.890> the<00:02:16.890> different<00:02:17.220> pain 00:02:17.420 --> 00:02:17.430 align:start position:0% learn a lot about the different pain 00:02:17.430 --> 00:02:19.250 align:start position:0% learn a lot about the different pain points<00:02:17.790> that<00:02:17.819> they<00:02:18.060> have<00:02:18.239> and<00:02:18.569> the<00:02:19.110> pain 00:02:19.250 --> 00:02:19.260 align:start position:0% points that they have and the pain 00:02:19.260 --> 00:02:21.050 align:start position:0% points that they have and the pain points<00:02:19.530> that<00:02:19.650> gamers<00:02:20.130> have<00:02:20.400> we're<00:02:20.640> watching 00:02:21.050 --> 00:02:21.060 align:start position:0% points that gamers have we're watching 00:02:21.060 --> 00:02:22.580 align:start position:0% points that gamers have we're watching gamers<00:02:21.330> have<00:02:21.540> is<00:02:21.720> very<00:02:21.930> different<00:02:22.350> from 00:02:22.580 --> 00:02:22.590 align:start position:0% gamers have is very different from 00:02:22.590 --> 00:02:25.070 align:start position:0% gamers have is very different from somebody<00:02:23.340> who<00:02:23.700> wants<00:02:24.000> to<00:02:24.120> make<00:02:24.300> a<00:02:24.540> compound 00:02:25.070 --> 00:02:25.080 align:start position:0% somebody who wants to make a compound 00:02:25.080 --> 00:02:29.180 align:start position:0% somebody who wants to make a compound load<00:02:25.459> or<00:02:26.459> use<00:02:26.819> point<00:02:27.120> base<00:02:27.680> they<00:02:28.680> have<00:02:28.709> a 00:02:29.180 --> 00:02:29.190 align:start position:0% load or use point base they have a 00:02:29.190 --> 00:02:31.220 align:start position:0% load or use point base they have a higher<00:02:29.580> expectation<00:02:29.970> of<00:02:30.600> the<00:02:30.750> flow<00:02:30.989> being 00:02:31.220 --> 00:02:31.230 align:start position:0% higher expectation of the flow being 00:02:31.230 --> 00:02:34.190 align:start position:0% higher expectation of the flow being extremely<00:02:31.709> smooth<00:02:32.130> and<00:02:33.000> so<00:02:33.209> that's<00:02:33.870> kind<00:02:34.140> of 00:02:34.190 --> 00:02:34.200 align:start position:0% extremely smooth and so that's kind of 00:02:34.200 --> 00:02:35.660 align:start position:0% extremely smooth and so that's kind of fact<00:02:34.410> at<00:02:34.530> least<00:02:34.650> from<00:02:34.769> the<00:02:34.890> game<00:02:35.040> side<00:02:35.280> what<00:02:35.550> we 00:02:35.660 --> 00:02:35.670 align:start position:0% fact at least from the game side what we 00:02:35.670 --> 00:02:39.710 align:start position:0% fact at least from the game side what we think<00:02:35.910> about<00:02:36.000> a<00:02:36.150> lot<00:02:36.709> yeah<00:02:37.709> and<00:02:38.299> what<00:02:39.299> are<00:02:39.480> some 00:02:39.710 --> 00:02:39.720 align:start position:0% think about a lot yeah and what are some 00:02:39.720 --> 00:02:41.240 align:start position:0% think about a lot yeah and what are some of<00:02:39.870> the<00:02:39.959> things<00:02:40.140> and<00:02:40.530> maybe<00:02:40.769> that<00:02:40.980> you<00:02:41.070> guys 00:02:41.240 --> 00:02:41.250 align:start position:0% of the things and maybe that you guys 00:02:41.250 --> 00:02:42.949 align:start position:0% of the things and maybe that you guys can<00:02:41.459> kind<00:02:41.610> of<00:02:41.700> come<00:02:41.880> in<00:02:42.030> the<00:02:42.540> things<00:02:42.780> that 00:02:42.949 --> 00:02:42.959 align:start position:0% can kind of come in the things that 00:02:42.959 --> 00:02:44.690 align:start position:0% can kind of come in the things that we're<00:02:43.079> doing<00:02:43.230> right<00:02:43.709> and<00:02:44.010> what<00:02:44.070> things<00:02:44.519> were 00:02:44.690 --> 00:02:44.700 align:start position:0% we're doing right and what things were 00:02:44.700 --> 00:02:45.590 align:start position:0% we're doing right and what things were doing<00:02:44.880> wrong 00:02:45.590 --> 00:02:45.600 align:start position:0% doing wrong 00:02:45.600 --> 00:02:52.100 align:start position:0% doing wrong maybe<00:02:45.810> argent<00:02:49.190> question<00:02:50.190> I<00:02:50.780> think<00:02:51.780> we<00:02:52.049> are 00:02:52.100 --> 00:02:52.110 align:start position:0% maybe argent question I think we are 00:02:52.110 --> 00:02:53.569 align:start position:0% maybe argent question I think we are starting<00:02:52.410> to<00:02:52.530> do<00:02:52.620> a<00:02:52.650> lot<00:02:52.799> of<00:02:52.829> thing<00:02:53.100> right<00:02:53.250> I 00:02:53.569 --> 00:02:53.579 align:start position:0% starting to do a lot of thing right I 00:02:53.579 --> 00:02:55.610 align:start position:0% starting to do a lot of thing right I think<00:02:53.820> maybe<00:02:54.299> to<00:02:54.510> complement<00:02:55.019> your<00:02:55.170> first 00:02:55.610 --> 00:02:55.620 align:start position:0% think maybe to complement your first 00:02:55.620 --> 00:02:57.050 align:start position:0% think maybe to complement your first question<00:02:56.010> I<00:02:56.100> think<00:02:56.280> this<00:02:56.370> is<00:02:56.489> a<00:02:56.519> very<00:02:56.760> exciting 00:02:57.050 --> 00:02:57.060 align:start position:0% question I think this is a very exciting 00:02:57.060 --> 00:02:59.060 align:start position:0% question I think this is a very exciting career<00:02:57.420> because<00:02:57.989> the<00:02:58.110> blockchain<00:02:58.350> material 00:02:59.060 --> 00:02:59.070 align:start position:0% career because the blockchain material 00:02:59.070 --> 00:03:01.220 align:start position:0% career because the blockchain material is<00:02:59.160> still<00:02:59.340> a<00:02:59.370> young<00:02:59.880> technology<00:03:00.239> and<00:03:01.109> I<00:03:01.200> think 00:03:01.220 --> 00:03:01.230 align:start position:0% is still a young technology and I think 00:03:01.230 --> 00:03:05.090 align:start position:0% is still a young technology and I think we<00:03:01.560> are<00:03:01.709> rightly<00:03:02.930> reaching<00:03:03.930> outside<00:03:04.260> of<00:03:04.650> small 00:03:05.090 --> 00:03:05.100 align:start position:0% we are rightly reaching outside of small 00:03:05.100 --> 00:03:07.370 align:start position:0% we are rightly reaching outside of small crypto<00:03:05.489> bubble<00:03:05.820> and<00:03:06.239> I<00:03:06.420> think<00:03:06.690> a<00:03:06.780> lot<00:03:07.079> of<00:03:07.109> that 00:03:07.370 --> 00:03:07.380 align:start position:0% crypto bubble and I think a lot of that 00:03:07.380 --> 00:03:11.030 align:start position:0% crypto bubble and I think a lot of that capability<00:03:08.340> is<00:03:08.579> done<00:03:08.850> through<00:03:09.480> improving<00:03:10.049> the 00:03:11.030 --> 00:03:11.040 align:start position:0% capability is done through improving the 00:03:11.040 --> 00:03:13.009 align:start position:0% capability is done through improving the user<00:03:11.190> experience<00:03:11.310> I<00:03:11.910> think<00:03:12.209> especially<00:03:12.660> if 00:03:13.009 --> 00:03:13.019 align:start position:0% user experience I think especially if 00:03:13.019 --> 00:03:15.380 align:start position:0% user experience I think especially if imagine<00:03:13.470> it<00:03:13.590> comes<00:03:13.829> from<00:03:14.340> the<00:03:14.430> technology<00:03:14.940> and 00:03:15.380 --> 00:03:15.390 align:start position:0% imagine it comes from the technology and 00:03:15.390 --> 00:03:17.479 align:start position:0% imagine it comes from the technology and I<00:03:15.480> think<00:03:15.690> we<00:03:15.750> try<00:03:16.200> to<00:03:16.320> solve<00:03:16.650> problems<00:03:17.130> by<00:03:17.430> the 00:03:17.479 --> 00:03:17.489 align:start position:0% I think we try to solve problems by the 00:03:17.489 --> 00:03:19.610 align:start position:0% I think we try to solve problems by the technology<00:03:18.060> first<00:03:18.420> thing<00:03:18.600> but<00:03:18.989> I<00:03:19.260> think<00:03:19.530> this 00:03:19.610 --> 00:03:19.620 align:start position:0% technology first thing but I think this 00:03:19.620 --> 00:03:21.740 align:start position:0% technology first thing but I think this is<00:03:19.739> really<00:03:19.950> exciting<00:03:20.310> and<00:03:20.609> because<00:03:20.820> we<00:03:21.120> we<00:03:21.600> get 00:03:21.740 --> 00:03:21.750 align:start position:0% is really exciting and because we we get 00:03:21.750 --> 00:03:23.479 align:start position:0% is really exciting and because we we get to<00:03:21.930> show<00:03:22.109> this<00:03:22.290> amazing<00:03:22.680> technology<00:03:22.950> to<00:03:23.370> the 00:03:23.479 --> 00:03:23.489 align:start position:0% to show this amazing technology to the 00:03:23.489 --> 00:03:25.510 align:start position:0% to show this amazing technology to the outside<00:03:23.760> world<00:03:23.940> while<00:03:24.600> still 00:03:25.510 --> 00:03:25.520 align:start position:0% outside world while still 00:03:25.520 --> 00:03:27.280 align:start position:0% outside world while still it's<00:03:26.090> called<00:03:26.300> principle<00:03:26.780> and<00:03:26.900> I<00:03:26.960> think<00:03:27.170> this 00:03:27.280 --> 00:03:27.290 align:start position:0% it's called principle and I think this 00:03:27.290 --> 00:03:28.690 align:start position:0% it's called principle and I think this is<00:03:27.410> something<00:03:27.770> that<00:03:27.800> is<00:03:28.040> that<00:03:28.370> it's<00:03:28.490> very 00:03:28.690 --> 00:03:28.700 align:start position:0% is something that is that it's very 00:03:28.700 --> 00:03:30.940 align:start position:0% is something that is that it's very important<00:03:29.150> is<00:03:29.270> to<00:03:29.300> to<00:03:30.140> being<00:03:30.350> able<00:03:30.470> to<00:03:30.650> reach 00:03:30.940 --> 00:03:30.950 align:start position:0% important is to to being able to reach 00:03:30.950 --> 00:03:33.670 align:start position:0% important is to to being able to reach to<00:03:31.490> people<00:03:31.940> and<00:03:32.090> maybe<00:03:32.390> less<00:03:32.600> tech-savvy<00:03:33.050> but 00:03:33.670 --> 00:03:33.680 align:start position:0% to people and maybe less tech-savvy but 00:03:33.680 --> 00:03:35.590 align:start position:0% to people and maybe less tech-savvy but still<00:03:33.950> maintain<00:03:34.370> a<00:03:34.670> core<00:03:34.910> principle<00:03:35.120> about 00:03:35.590 --> 00:03:35.600 align:start position:0% still maintain a core principle about 00:03:35.600 --> 00:03:38.770 align:start position:0% still maintain a core principle about decentralization<00:03:36.020> I<00:03:37.030> mean<00:03:38.030> all<00:03:38.210> year<00:03:38.510> you're 00:03:38.770 --> 00:03:38.780 align:start position:0% decentralization I mean all year you're 00:03:38.780 --> 00:03:41.640 align:start position:0% decentralization I mean all year you're kind<00:03:39.200> of<00:03:39.260> the<00:03:39.440> design<00:03:39.860> product<00:03:40.760> design 00:03:41.640 --> 00:03:41.650 align:start position:0% kind of the design product design 00:03:41.650 --> 00:03:43.600 align:start position:0% kind of the design product design representative<00:03:42.650> here<00:03:42.860> what<00:03:43.160> are<00:03:43.280> some<00:03:43.460> of<00:03:43.550> the 00:03:43.600 --> 00:03:43.610 align:start position:0% representative here what are some of the 00:03:43.610 --> 00:03:46.450 align:start position:0% representative here what are some of the design<00:03:44.410> opportunities<00:03:45.410> that<00:03:45.590> we<00:03:45.740> we've<00:03:46.250> had 00:03:46.450 --> 00:03:46.460 align:start position:0% design opportunities that we we've had 00:03:46.460 --> 00:03:49.540 align:start position:0% design opportunities that we we've had and<00:03:47.000> what's<00:03:47.300> going<00:03:47.690> on<00:03:47.810> in<00:03:47.900> the<00:03:47.960> space<00:03:48.020> I<00:03:48.550> echo 00:03:49.540 --> 00:03:49.550 align:start position:0% and what's going on in the space I echo 00:03:49.550 --> 00:03:52.510 align:start position:0% and what's going on in the space I echo what<00:03:49.760> you<00:03:49.910> said<00:03:50.440> having<00:03:51.440> sex<00:03:51.860> through<00:03:52.130> your<00:03:52.340> ex 00:03:52.510 --> 00:03:52.520 align:start position:0% what you said having sex through your ex 00:03:52.520 --> 00:03:57.840 align:start position:0% what you said having sex through your ex audit<00:03:52.940> I<00:03:53.330> think<00:03:54.670> we<00:03:55.670> came<00:03:56.150> a<00:03:56.540> really<00:03:57.140> long<00:03:57.350> way 00:03:57.840 --> 00:03:57.850 align:start position:0% audit I think we came a really long way 00:03:57.850 --> 00:04:03.100 align:start position:0% audit I think we came a really long way from<00:03:59.290> you<00:04:00.290> know<00:04:00.410> early<00:04:00.820> big<00:04:02.110> decentralized 00:04:03.100 --> 00:04:03.110 align:start position:0% from you know early big decentralized 00:04:03.110 --> 00:04:06.300 align:start position:0% from you know early big decentralized products<00:04:03.950> that<00:04:04.130> were<00:04:04.250> very<00:04:04.700> much<00:04:04.910> focused<00:04:05.330> on 00:04:06.300 --> 00:04:06.310 align:start position:0% products that were very much focused on 00:04:06.310 --> 00:04:09.430 align:start position:0% products that were very much focused on exploring<00:04:07.310> the<00:04:07.520> technology<00:04:08.330> to<00:04:08.780> building 00:04:09.430 --> 00:04:09.440 align:start position:0% exploring the technology to building 00:04:09.440 --> 00:04:12.520 align:start position:0% exploring the technology to building more<00:04:09.890> and<00:04:09.920> more<00:04:10.160> user-friendly<00:04:10.940> user<00:04:11.870> focus 00:04:12.520 --> 00:04:12.530 align:start position:0% more and more user-friendly user focus 00:04:12.530 --> 00:04:16.030 align:start position:0% more and more user-friendly user focus things<00:04:12.860> we<00:04:13.280> are<00:04:13.480> as<00:04:14.480> complex<00:04:15.080> you<00:04:15.530> guys<00:04:15.740> as 00:04:16.030 --> 00:04:16.040 align:start position:0% things we are as complex you guys as 00:04:16.040 --> 00:04:19.860 align:start position:0% things we are as complex you guys as companies<00:04:16.610> we<00:04:16.790> start<00:04:17.120> to<00:04:17.390> focus<00:04:17.750> more<00:04:18.230> on 00:04:19.860 --> 00:04:19.870 align:start position:0% companies we start to focus more on 00:04:19.870 --> 00:04:24.370 align:start position:0% companies we start to focus more on basically<00:04:20.870> solving<00:04:21.410> user<00:04:21.650> needs<00:04:22.960> finding<00:04:23.960> the 00:04:24.370 --> 00:04:24.380 align:start position:0% basically solving user needs finding the 00:04:24.380 --> 00:04:27.430 align:start position:0% basically solving user needs finding the good<00:04:24.740> company<00:04:25.460> creating<00:04:26.120> good<00:04:26.390> mental<00:04:26.900> models 00:04:27.430 --> 00:04:27.440 align:start position:0% good company creating good mental models 00:04:27.440 --> 00:04:33.100 align:start position:0% good company creating good mental models I<00:04:27.920> think<00:04:28.370> we<00:04:28.550> still<00:04:28.910> have<00:04:30.070> some<00:04:31.070> challenges<00:04:32.110> to 00:04:33.100 --> 00:04:33.110 align:start position:0% I think we still have some challenges to 00:04:33.110 --> 00:04:35.920 align:start position:0% I think we still have some challenges to overcome<00:04:33.140> we're<00:04:34.070> still<00:04:34.340> sort<00:04:35.090> of<00:04:35.240> I<00:04:35.600> seen 00:04:35.920 --> 00:04:35.930 align:start position:0% overcome we're still sort of I seen 00:04:35.930 --> 00:04:39.070 align:start position:0% overcome we're still sort of I seen projects<00:04:36.290> designing<00:04:36.740> for<00:04:37.480> just<00:04:38.480> a<00:04:38.660> fan<00:04:38.900> of 00:04:39.070 --> 00:04:39.080 align:start position:0% projects designing for just a fan of 00:04:39.080 --> 00:04:43.990 align:start position:0% projects designing for just a fan of technology<00:04:39.740> but<00:04:40.700> I<00:04:42.220> think<00:04:43.220> we're<00:04:43.370> going<00:04:43.610> in<00:04:43.880> a 00:04:43.990 --> 00:04:44.000 align:start position:0% technology but I think we're going in a 00:04:44.000 --> 00:04:46.150 align:start position:0% technology but I think we're going in a good<00:04:44.150> direction<00:04:44.210> of<00:04:44.990> putting<00:04:45.380> the<00:04:45.530> user<00:04:45.740> first 00:04:46.150 --> 00:04:46.160 align:start position:0% good direction of putting the user first 00:04:46.160 --> 00:04:50.020 align:start position:0% good direction of putting the user first and<00:04:46.550> having<00:04:47.000> the<00:04:47.240> user<00:04:48.160> introduce<00:04:49.160> like<00:04:49.550> being 00:04:50.020 --> 00:04:50.030 align:start position:0% and having the user introduce like being 00:04:50.030 --> 00:04:52.690 align:start position:0% and having the user introduce like being able<00:04:50.150> to<00:04:50.330> introduce<00:04:50.660> the<00:04:51.050> user<00:04:51.230> to<00:04:51.530> the<00:04:51.770> crypto 00:04:52.690 --> 00:04:52.700 align:start position:0% able to introduce the user to the crypto 00:04:52.700 --> 00:04:57.700 align:start position:0% able to introduce the user to the crypto I<00:04:53.500> mean<00:04:54.500> so<00:04:54.830> going<00:04:55.400> going<00:04:56.360> towards<00:04:56.780> that<00:04:57.020> in 00:04:57.700 --> 00:04:57.710 align:start position:0% I mean so going going towards that in 00:04:57.710 --> 00:04:59.830 align:start position:0% I mean so going going towards that in your<00:04:58.100> company<00:04:58.640> you<00:04:58.700> guys<00:04:58.850> have<00:04:59.060> kind<00:04:59.330> of<00:04:59.420> one 00:04:59.830 --> 00:04:59.840 align:start position:0% your company you guys have kind of one 00:04:59.840 --> 00:05:02.030 align:start position:0% your company you guys have kind of one of<00:04:59.870> the<00:05:00.020> most<00:05:00.170> well<00:05:00.890> adoption 00:05:02.030 --> 00:05:02.040 align:start position:0% of the most well adoption 00:05:02.040 --> 00:05:03.680 align:start position:0% of the most well adoption kind<00:05:02.400> of<00:05:02.460> products<00:05:02.880> with<00:05:03.030> well<00:05:03.240> adoption 00:05:03.680 --> 00:05:03.690 align:start position:0% kind of products with well adoption 00:05:03.690 --> 00:05:07.130 align:start position:0% kind of products with well adoption adopted<00:05:04.490> features<00:05:05.490> so<00:05:05.880> how<00:05:06.630> do<00:05:06.690> what<00:05:06.990> this 00:05:07.130 --> 00:05:07.140 align:start position:0% adopted features so how do what this 00:05:07.140 --> 00:05:08.750 align:start position:0% adopted features so how do what this design<00:05:07.440> look<00:05:07.620> like<00:05:07.800> in<00:05:07.920> your<00:05:08.010> process<00:05:08.580> there's 00:05:08.750 --> 00:05:08.760 align:start position:0% design look like in your process there's 00:05:08.760 --> 00:05:10.730 align:start position:0% design look like in your process there's a<00:05:08.850> lot<00:05:08.970> of<00:05:09.090> kind<00:05:09.240> of<00:05:09.360> as<00:05:09.510> we<00:05:09.990> saw<00:05:10.170> from<00:05:10.290> the<00:05:10.380> UX 00:05:10.730 --> 00:05:10.740 align:start position:0% a lot of kind of as we saw from the UX 00:05:10.740 --> 00:05:12.650 align:start position:0% a lot of kind of as we saw from the UX audits<00:05:11.160> a<00:05:11.370> lot<00:05:11.520> of<00:05:11.640> teams<00:05:11.970> that<00:05:12.090> come<00:05:12.300> in<00:05:12.480> and 00:05:12.650 --> 00:05:12.660 align:start position:0% audits a lot of teams that come in and 00:05:12.660 --> 00:05:14.420 align:start position:0% audits a lot of teams that come in and really<00:05:12.750> we<00:05:13.260> don't<00:05:13.350> have<00:05:13.560> a<00:05:13.590> designer<00:05:13.950> we<00:05:14.250> don't 00:05:14.420 --> 00:05:14.430 align:start position:0% really we don't have a designer we don't 00:05:14.430 --> 00:05:17.000 align:start position:0% really we don't have a designer we don't know<00:05:14.520> what<00:05:14.640> to<00:05:14.760> do<00:05:14.940> so<00:05:15.560> how<00:05:16.560> did<00:05:16.740> that<00:05:16.860> start 00:05:17.000 --> 00:05:17.010 align:start position:0% know what to do so how did that start 00:05:17.010 --> 00:05:18.950 align:start position:0% know what to do so how did that start from<00:05:17.280> you<00:05:17.460> guys<00:05:17.670> and<00:05:18.090> and<00:05:18.480> how<00:05:18.690> does<00:05:18.750> that 00:05:18.950 --> 00:05:18.960 align:start position:0% from you guys and and how does that 00:05:18.960 --> 00:05:26.060 align:start position:0% from you guys and and how does that throat<00:05:19.410> currently<00:05:19.950> in<00:05:20.100> the<00:05:20.190> current<00:05:20.430> state<00:05:25.070> I 00:05:26.060 --> 00:05:26.070 align:start position:0% throat currently in the current state I 00:05:26.070 --> 00:05:29.210 align:start position:0% throat currently in the current state I think<00:05:26.730> first<00:05:27.740> design<00:05:28.740> start<00:05:29.010> by<00:05:29.160> thinking 00:05:29.210 --> 00:05:29.220 align:start position:0% think first design start by thinking 00:05:29.220 --> 00:05:31.670 align:start position:0% think first design start by thinking about<00:05:29.520> the<00:05:29.760> user<00:05:29.940> so<00:05:30.750> in<00:05:30.990> everything<00:05:31.200> we<00:05:31.470> do<00:05:31.650> we 00:05:31.670 --> 00:05:31.680 align:start position:0% about the user so in everything we do we 00:05:31.680 --> 00:05:34.730 align:start position:0% about the user so in everything we do we first<00:05:32.100> really<00:05:32.730> focus<00:05:33.060> on<00:05:33.510> the<00:05:33.690> user<00:05:33.870> and<00:05:34.050> to 00:05:34.730 --> 00:05:34.740 align:start position:0% first really focus on the user and to 00:05:34.740 --> 00:05:36.980 align:start position:0% first really focus on the user and to give<00:05:34.920> an<00:05:35.460> example<00:05:35.670> when<00:05:36.180> we<00:05:36.300> started<00:05:36.360> our<00:05:36.780> gen 00:05:36.980 --> 00:05:36.990 align:start position:0% give an example when we started our gen 00:05:36.990 --> 00:05:38.810 align:start position:0% give an example when we started our gen we're<00:05:37.230> thinking<00:05:37.650> about<00:05:37.740> you<00:05:38.130> know<00:05:38.250> to<00:05:38.400> manage 00:05:38.810 --> 00:05:38.820 align:start position:0% we're thinking about you know to manage 00:05:38.820 --> 00:05:41.120 align:start position:0% we're thinking about you know to manage or<00:05:39.060> your<00:05:39.360> account<00:05:39.690> or<00:05:39.870> your<00:05:39.960> keys<00:05:40.230> and<00:05:40.650> we<00:05:41.010> will 00:05:41.120 --> 00:05:41.130 align:start position:0% or your account or your keys and we will 00:05:41.130 --> 00:05:43.220 align:start position:0% or your account or your keys and we will just<00:05:41.220> try<00:05:41.670> to<00:05:41.790> think<00:05:42.120> what's<00:05:42.660> a<00:05:42.960> user 00:05:43.220 --> 00:05:43.230 align:start position:0% just try to think what's a user 00:05:43.230 --> 00:05:45.020 align:start position:0% just try to think what's a user experience<00:05:43.830> that<00:05:44.070> people<00:05:44.910> actually 00:05:45.020 --> 00:05:45.030 align:start position:0% experience that people actually 00:05:45.030 --> 00:05:46.820 align:start position:0% experience that people actually understand<00:05:45.570> people<00:05:45.900> outside<00:05:46.170> of<00:05:46.230> our<00:05:46.440> bubble 00:05:46.820 --> 00:05:46.830 align:start position:0% understand people outside of our bubble 00:05:46.830 --> 00:05:49.880 align:start position:0% understand people outside of our bubble and<00:05:47.010> we<00:05:47.700> we<00:05:48.360> realize<00:05:48.750> that<00:05:48.780> the<00:05:49.110> user<00:05:49.320> of<00:05:49.470> of 00:05:49.880 --> 00:05:49.890 align:start position:0% and we we realize that the user of of 00:05:49.890 --> 00:05:52.280 align:start position:0% and we we realize that the user of of the<00:05:50.520> experience<00:05:50.940> of<00:05:51.060> banks<00:05:51.630> for<00:05:51.780> example<00:05:52.170> we 00:05:52.280 --> 00:05:52.290 align:start position:0% the experience of banks for example we 00:05:52.290 --> 00:05:53.990 align:start position:0% the experience of banks for example we may<00:05:52.380> not<00:05:52.530> like<00:05:52.710> banks<00:05:53.100> traditional<00:05:53.640> banks 00:05:53.990 --> 00:05:54.000 align:start position:0% may not like banks traditional banks 00:05:54.000 --> 00:05:55.970 align:start position:0% may not like banks traditional banks with<00:05:54.660> the<00:05:54.810> idea<00:05:55.080> that<00:05:55.290> if<00:05:55.530> you<00:05:55.770> lose<00:05:55.920> your 00:05:55.970 --> 00:05:55.980 align:start position:0% with the idea that if you lose your 00:05:55.980 --> 00:05:57.800 align:start position:0% with the idea that if you lose your credit<00:05:56.460> card<00:05:56.700> you<00:05:56.850> lose<00:05:56.970> your<00:05:57.180> wallet<00:05:57.330> you<00:05:57.630> can 00:05:57.800 --> 00:05:57.810 align:start position:0% credit card you lose your wallet you can 00:05:57.810 --> 00:05:59.240 align:start position:0% credit card you lose your wallet you can actually<00:05:57.930> call<00:05:58.320> your<00:05:58.470> bank<00:05:58.710> to<00:05:58.890> give<00:05:59.040> a<00:05:59.070> new 00:05:59.240 --> 00:05:59.250 align:start position:0% actually call your bank to give a new 00:05:59.250 --> 00:06:01.010 align:start position:0% actually call your bank to give a new one<00:05:59.430> we<00:06:00.000> cannot<00:06:00.180> feel<00:06:00.450> that<00:06:00.630> this<00:06:00.780> was<00:06:00.990> a 00:06:01.010 --> 00:06:01.020 align:start position:0% one we cannot feel that this was a 00:06:01.020 --> 00:06:04.160 align:start position:0% one we cannot feel that this was a mental<00:06:01.230> model<00:06:01.680> that<00:06:01.950> users<00:06:02.880> would<00:06:03.720> understand 00:06:04.160 --> 00:06:04.170 align:start position:0% mental model that users would understand 00:06:04.170 --> 00:06:06.350 align:start position:0% mental model that users would understand it<00:06:04.320> so<00:06:04.440> we<00:06:04.560> try<00:06:04.770> to<00:06:04.830> replicate<00:06:05.160> that<00:06:05.610> first<00:06:06.090> is 00:06:06.350 --> 00:06:06.360 align:start position:0% it so we try to replicate that first is 00:06:06.360 --> 00:06:08.210 align:start position:0% it so we try to replicate that first is using<00:06:06.720> the<00:06:06.810> technology<00:06:06.900> that's<00:06:07.680> why<00:06:07.860> we<00:06:08.010> build 00:06:08.210 --> 00:06:08.220 align:start position:0% using the technology that's why we build 00:06:08.220 --> 00:06:10.070 align:start position:0% using the technology that's why we build a<00:06:08.310> smart<00:06:08.550> contract<00:06:08.880> this<00:06:09.000> wallet<00:06:09.330> and<00:06:09.510> then 00:06:10.070 --> 00:06:10.080 align:start position:0% a smart contract this wallet and then 00:06:10.080 --> 00:06:15.380 align:start position:0% a smart contract this wallet and then adding<00:06:10.590> a<00:06:11.420> layer<00:06:12.420> of<00:06:12.770> UX<00:06:13.770> and<00:06:13.980> design<00:06:14.180> on<00:06:15.180> top 00:06:15.380 --> 00:06:15.390 align:start position:0% adding a layer of UX and design on top 00:06:15.390 --> 00:06:17.720 align:start position:0% adding a layer of UX and design on top of<00:06:15.510> it<00:06:15.630> so<00:06:15.840> for<00:06:16.230> us<00:06:16.350> we<00:06:16.560> need<00:06:16.650> the<00:06:17.250> starting 00:06:17.720 --> 00:06:17.730 align:start position:0% of it so for us we need the starting 00:06:17.730 --> 00:06:19.400 align:start position:0% of it so for us we need the starting point<00:06:17.940> is<00:06:18.180> the<00:06:18.210> user<00:06:18.480> trying<00:06:18.960> to<00:06:19.080> solve<00:06:19.290> the 00:06:19.400 --> 00:06:19.410 align:start position:0% point is the user trying to solve the 00:06:19.410 --> 00:06:21.560 align:start position:0% point is the user trying to solve the problem<00:06:19.770> for<00:06:20.040> a<00:06:20.100> user<00:06:20.340> then<00:06:21.180> we<00:06:21.330> use<00:06:21.450> the 00:06:21.560 --> 00:06:21.570 align:start position:0% problem for a user then we use the 00:06:21.570 --> 00:06:24.680 align:start position:0% problem for a user then we use the technology<00:06:21.720> and<00:06:22.380> then<00:06:22.680> we<00:06:22.860> use<00:06:23.150> shiny<00:06:24.150> button 00:06:24.680 --> 00:06:24.690 align:start position:0% technology and then we use shiny button 00:06:24.690 --> 00:06:26.480 align:start position:0% technology and then we use shiny button good<00:06:24.960> design<00:06:25.350> you<00:06:25.380> know<00:06:25.710> flows<00:06:26.070> and<00:06:26.310> stuff 00:06:26.480 --> 00:06:26.490 align:start position:0% good design you know flows and stuff 00:06:26.490 --> 00:06:28.310 align:start position:0% good design you know flows and stuff like<00:06:26.640> that<00:06:26.850> I<00:06:27.270> think<00:06:27.330> the<00:06:27.570> starting<00:06:27.840> point<00:06:28.170> is 00:06:28.310 --> 00:06:28.320 align:start position:0% like that I think the starting point is 00:06:28.320 --> 00:06:30.170 align:start position:0% like that I think the starting point is really<00:06:28.590> to<00:06:28.770> start<00:06:28.830> from<00:06:29.130> the<00:06:29.280> user<00:06:29.430> well 00:06:30.170 --> 00:06:30.180 align:start position:0% really to start from the user well 00:06:30.180 --> 00:06:31.880 align:start position:0% really to start from the user well traditional<00:06:30.900> I<00:06:31.050> think<00:06:31.260> you<00:06:31.320> know<00:06:31.440> in<00:06:31.680> an 00:06:31.880 --> 00:06:31.890 align:start position:0% traditional I think you know in an 00:06:31.890 --> 00:06:33.410 align:start position:0% traditional I think you know in an ecosystem<00:06:32.160> where<00:06:32.610> people<00:06:32.970> are<00:06:33.030> very<00:06:33.150> tech 00:06:33.410 --> 00:06:33.420 align:start position:0% ecosystem where people are very tech 00:06:33.420 --> 00:06:34.610 align:start position:0% ecosystem where people are very tech savvy<00:06:33.450> we<00:06:33.870> tend<00:06:34.050> to<00:06:34.080> start<00:06:34.320> from<00:06:34.500> the 00:06:34.610 --> 00:06:34.620 align:start position:0% savvy we tend to start from the 00:06:34.620 --> 00:06:36.590 align:start position:0% savvy we tend to start from the technology<00:06:35.130> we<00:06:35.550> build<00:06:35.760> a<00:06:35.820> cool<00:06:36.000> technology 00:06:36.590 --> 00:06:36.600 align:start position:0% technology we build a cool technology 00:06:36.600 --> 00:06:38.960 align:start position:0% technology we build a cool technology and<00:06:36.810> then<00:06:37.620> we<00:06:37.710> think<00:06:37.860> okay<00:06:38.190> you<00:06:38.280> know<00:06:38.430> how<00:06:38.790> will 00:06:38.960 --> 00:06:38.970 align:start position:0% and then we think okay you know how will 00:06:38.970 --> 00:06:40.730 align:start position:0% and then we think okay you know how will the<00:06:39.090> user<00:06:39.240> use<00:06:39.630> my<00:06:39.780> technology<00:06:40.080> I<00:06:40.350> think<00:06:40.470> you 00:06:40.730 --> 00:06:40.740 align:start position:0% the user use my technology I think you 00:06:40.740 --> 00:06:42.590 align:start position:0% the user use my technology I think you wish<00:06:40.920> departing<00:06:41.790> you<00:06:41.880> need<00:06:42.000> to<00:06:42.120> be<00:06:42.210> shaped<00:06:42.450> you 00:06:42.590 --> 00:06:42.600 align:start position:0% wish departing you need to be shaped you 00:06:42.600 --> 00:06:44.090 align:start position:0% wish departing you need to be shaped you should<00:06:42.780> be<00:06:42.900> organized<00:06:43.320> solve<00:06:43.500> a<00:06:43.620> problem<00:06:43.950> for 00:06:44.090 --> 00:06:44.100 align:start position:0% should be organized solve a problem for 00:06:44.100 --> 00:06:45.950 align:start position:0% should be organized solve a problem for users<00:06:44.310> and<00:06:44.760> then<00:06:44.880> find<00:06:45.180> the<00:06:45.270> right<00:06:45.450> technology 00:06:45.950 --> 00:06:45.960 align:start position:0% users and then find the right technology 00:06:45.960 --> 00:06:47.540 align:start position:0% users and then find the right technology to<00:06:45.990> solve<00:06:46.260> that<00:06:46.440> you're<00:06:47.160> kind<00:06:47.340> of<00:06:47.370> going 00:06:47.540 --> 00:06:47.550 align:start position:0% to solve that you're kind of going 00:06:47.550 --> 00:06:49.550 align:start position:0% to solve that you're kind of going touching<00:06:48.030> upon<00:06:48.120> the<00:06:48.630> next<00:06:48.900> question<00:06:49.320> here 00:06:49.550 --> 00:06:49.560 align:start position:0% touching upon the next question here 00:06:49.560 --> 00:06:50.800 align:start position:0% touching upon the next question here about<00:06:49.590> users<00:06:50.190> and 00:06:50.800 --> 00:06:50.810 align:start position:0% about users and 00:06:50.810 --> 00:06:51.700 align:start position:0% about users and you're<00:06:50.930> having<00:06:51.110> this<00:06:51.260> really<00:06:51.500> interesting 00:06:51.700 --> 00:06:51.710 align:start position:0% you're having this really interesting 00:06:51.710 --> 00:06:54.430 align:start position:0% you're having this really interesting conversation<00:06:52.610> around<00:06:52.760> how<00:06:53.510> how<00:06:53.990> are<00:06:54.139> you<00:06:54.260> how 00:06:54.430 --> 00:06:54.440 align:start position:0% conversation around how how are you how 00:06:54.440 --> 00:06:57.460 align:start position:0% conversation around how how are you how do<00:06:54.500> you<00:06:54.590> find<00:06:54.889> your<00:06:55.010> users<00:06:55.490> and<00:06:55.910> and<00:06:56.480> and<00:06:57.020> how 00:06:57.460 --> 00:06:57.470 align:start position:0% do you find your users and and and how 00:06:57.470 --> 00:07:00.790 align:start position:0% do you find your users and and and how do<00:06:57.530> you<00:06:57.650> define<00:06:57.980> who<00:06:58.310> your<00:06:58.430> user<00:06:58.820> group<00:06:59.030> is<00:06:59.800> so 00:07:00.790 --> 00:07:00.800 align:start position:0% do you define who your user group is so 00:07:00.800 --> 00:07:02.500 align:start position:0% do you define who your user group is so you<00:07:01.460> know<00:07:01.550> as<00:07:01.669> you<00:07:01.790> know<00:07:01.820> coinbase<00:07:02.210> because<00:07:02.480> a 00:07:02.500 --> 00:07:02.510 align:start position:0% you know as you know coinbase because a 00:07:02.510 --> 00:07:04.690 align:start position:0% you know as you know coinbase because a portfolio<00:07:03.050> of<00:07:03.080> different<00:07:03.590> products<00:07:04.130> and<00:07:04.580> I 00:07:04.690 --> 00:07:04.700 align:start position:0% portfolio of different products and I 00:07:04.700 --> 00:07:07.060 align:start position:0% portfolio of different products and I both<00:07:05.150> custodial<00:07:05.840> and<00:07:05.870> noncustodial<00:07:06.050> and<00:07:07.010> I 00:07:07.060 --> 00:07:07.070 align:start position:0% both custodial and noncustodial and I 00:07:07.070 --> 00:07:08.980 align:start position:0% both custodial and noncustodial and I think<00:07:07.340> what<00:07:07.730> we're<00:07:07.910> doing<00:07:08.210> really<00:07:08.389> well<00:07:08.660> is 00:07:08.980 --> 00:07:08.990 align:start position:0% think what we're doing really well is 00:07:08.990 --> 00:07:11.890 align:start position:0% think what we're doing really well is kind<00:07:09.889> of<00:07:09.950> understanding<00:07:10.580> that<00:07:10.610> not<00:07:11.030> about<00:07:11.360> not 00:07:11.890 --> 00:07:11.900 align:start position:0% kind of understanding that not about not 00:07:11.900 --> 00:07:14.350 align:start position:0% kind of understanding that not about not an<00:07:12.230> entire<00:07:12.740> group<00:07:12.980> of<00:07:13.160> our<00:07:13.280> users<00:07:13.700> is<00:07:13.970> the<00:07:14.000> same 00:07:14.350 --> 00:07:14.360 align:start position:0% an entire group of our users is the same 00:07:14.360 --> 00:07:16.690 align:start position:0% an entire group of our users is the same so<00:07:15.200> we<00:07:15.320> kind<00:07:15.560> of<00:07:15.620> funnel<00:07:16.040> them<00:07:16.190> into<00:07:16.340> their 00:07:16.690 --> 00:07:16.700 align:start position:0% so we kind of funnel them into their 00:07:16.700 --> 00:07:20.920 align:start position:0% so we kind of funnel them into their friends<00:07:17.090> in<00:07:17.750> two<00:07:17.900> different<00:07:18.050> places<00:07:18.470> and<00:07:19.930> with 00:07:20.920 --> 00:07:20.930 align:start position:0% friends in two different places and with 00:07:20.930 --> 00:07:25.060 align:start position:0% friends in two different places and with having<00:07:21.290> that<00:07:21.530> in<00:07:21.740> mind<00:07:21.980> we<00:07:22.730> actually<00:07:23.360> do<00:07:24.350> talk 00:07:25.060 --> 00:07:25.070 align:start position:0% having that in mind we actually do talk 00:07:25.070 --> 00:07:28.120 align:start position:0% having that in mind we actually do talk to<00:07:25.310> our<00:07:25.490> users<00:07:25.970> very<00:07:26.210> early<00:07:26.630> as<00:07:26.780> well<00:07:27.020> we<00:07:27.740> I 00:07:28.120 --> 00:07:28.130 align:start position:0% to our users very early as well we I 00:07:28.130 --> 00:07:30.159 align:start position:0% to our users very early as well we I mean<00:07:28.490> we<00:07:28.729> just<00:07:28.880> had<00:07:29.120> this<00:07:29.270> discussion<00:07:29.540> of<00:07:29.990> like 00:07:30.159 --> 00:07:30.169 align:start position:0% mean we just had this discussion of like 00:07:30.169 --> 00:07:34.540 align:start position:0% mean we just had this discussion of like it<00:07:30.950> is<00:07:31.160> a<00:07:31.580> lot<00:07:32.389> of<00:07:32.540> to<00:07:32.720> say<00:07:33.169> that<00:07:33.530> it<00:07:33.740> is<00:07:33.860> very 00:07:34.540 --> 00:07:34.550 align:start position:0% it is a lot of to say that it is very 00:07:34.550 --> 00:07:37.659 align:start position:0% it is a lot of to say that it is very difficult<00:07:34.790> to<00:07:35.210> find<00:07:35.479> a<00:07:36.050> user<00:07:36.560> group<00:07:36.860> without 00:07:37.659 --> 00:07:37.669 align:start position:0% difficult to find a user group without 00:07:37.669 --> 00:07:41.440 align:start position:0% difficult to find a user group without breaking<00:07:38.419> their<00:07:38.800> privacy<00:07:39.800> and<00:07:39.950> I<00:07:40.340> claim<00:07:41.120> the 00:07:41.440 --> 00:07:41.450 align:start position:0% breaking their privacy and I claim the 00:07:41.450 --> 00:07:44.230 align:start position:0% breaking their privacy and I claim the opposite<00:07:41.930> it's<00:07:42.169> just<00:07:42.460> you<00:07:43.460> basically<00:07:43.880> need<00:07:44.090> to 00:07:44.230 --> 00:07:44.240 align:start position:0% opposite it's just you basically need to 00:07:44.240 --> 00:07:47.140 align:start position:0% opposite it's just you basically need to hassle<00:07:44.660> a<00:07:44.720> little<00:07:45.020> bit<00:07:45.169> and<00:07:45.410> reach<00:07:45.919> out<00:07:46.190> to 00:07:47.140 --> 00:07:47.150 align:start position:0% hassle a little bit and reach out to 00:07:47.150 --> 00:07:49.719 align:start position:0% hassle a little bit and reach out to your<00:07:47.330> community<00:07:47.570> reach<00:07:48.560> out<00:07:48.800> use<00:07:49.280> different 00:07:49.719 --> 00:07:49.729 align:start position:0% your community reach out use different 00:07:49.729 --> 00:07:52.450 align:start position:0% your community reach out use different platforms<00:07:50.389> ask<00:07:51.350> people<00:07:51.889> to<00:07:51.919> come<00:07:52.220> to<00:07:52.340> your 00:07:52.450 --> 00:07:52.460 align:start position:0% platforms ask people to come to your 00:07:52.460 --> 00:07:54.909 align:start position:0% platforms ask people to come to your office<00:07:52.490> or<00:07:53.150> just<00:07:53.510> set<00:07:53.690> up<00:07:53.840> hangouts<00:07:54.320> and<00:07:54.710> just 00:07:54.909 --> 00:07:54.919 align:start position:0% office or just set up hangouts and just 00:07:54.919 --> 00:07:56.710 align:start position:0% office or just set up hangouts and just talk<00:07:55.160> to<00:07:55.190> your<00:07:55.490> user<00:07:55.700> understand<00:07:56.390> what<00:07:56.570> their 00:07:56.710 --> 00:07:56.720 align:start position:0% talk to your user understand what their 00:07:56.720 --> 00:07:58.510 align:start position:0% talk to your user understand what their pain<00:07:56.960> points<00:07:56.990> are<00:07:57.500> understand<00:07:58.130> what<00:07:58.340> they 00:07:58.510 --> 00:07:58.520 align:start position:0% pain points are understand what they 00:07:58.520 --> 00:08:01.810 align:start position:0% pain points are understand what they kind<00:07:58.970> of<00:07:59.030> expect<00:07:59.930> you<00:08:00.260> will<00:08:00.590> learn<00:08:00.860> that<00:08:01.460> maybe 00:08:01.810 --> 00:08:01.820 align:start position:0% kind of expect you will learn that maybe 00:08:01.820 --> 00:08:05.050 align:start position:0% kind of expect you will learn that maybe your<00:08:02.330> initial<00:08:02.870> assumptions<00:08:03.440> are<00:08:04.060> completely 00:08:05.050 --> 00:08:05.060 align:start position:0% your initial assumptions are completely 00:08:05.060 --> 00:08:08.650 align:start position:0% your initial assumptions are completely in<00:08:05.720> a<00:08:05.840> different<00:08:06.380> place<00:08:07.100> than<00:08:07.640> what<00:08:08.450> your 00:08:08.650 --> 00:08:08.660 align:start position:0% in a different place than what your 00:08:08.660 --> 00:08:10.149 align:start position:0% in a different place than what your users 00:08:10.149 --> 00:08:10.159 align:start position:0% users 00:08:10.159 --> 00:08:13.869 align:start position:0% users and<00:08:10.489> I<00:08:11.419> think<00:08:11.989> in<00:08:12.319> our<00:08:12.469> case<00:08:12.860> it's<00:08:13.219> one<00:08:13.489> of<00:08:13.639> the 00:08:13.869 --> 00:08:13.879 align:start position:0% and I think in our case it's one of the 00:08:13.879 --> 00:08:16.379 align:start position:0% and I think in our case it's one of the things<00:08:14.599> that<00:08:14.779> make<00:08:14.989> that<00:08:15.259> builds<00:08:15.649> that 00:08:16.379 --> 00:08:16.389 align:start position:0% things that make that builds that 00:08:16.389 --> 00:08:21.909 align:start position:0% things that make that builds that biggest<00:08:17.389> advantage<00:08:18.080> and<00:08:20.379> then<00:08:21.379> I<00:08:21.409> am<00:08:21.559> excited 00:08:21.909 --> 00:08:21.919 align:start position:0% biggest advantage and then I am excited 00:08:21.919 --> 00:08:23.379 align:start position:0% biggest advantage and then I am excited to<00:08:21.949> get<00:08:22.129> your<00:08:22.309> answer<00:08:22.669> because<00:08:22.879> I've<00:08:23.089> talked 00:08:23.379 --> 00:08:23.389 align:start position:0% to get your answer because I've talked 00:08:23.389 --> 00:08:24.999 align:start position:0% to get your answer because I've talked to<00:08:23.479> your<00:08:23.599> design<00:08:23.899> team<00:08:24.139> and<00:08:24.529> you<00:08:24.619> guys<00:08:24.769> have 00:08:24.999 --> 00:08:25.009 align:start position:0% to your design team and you guys have 00:08:25.009 --> 00:08:26.979 align:start position:0% to your design team and you guys have just<00:08:25.129> started<00:08:25.580> unraveling<00:08:25.969> their<00:08:26.569> research 00:08:26.979 --> 00:08:26.989 align:start position:0% just started unraveling their research 00:08:26.989 --> 00:08:29.049 align:start position:0% just started unraveling their research and<00:08:27.349> reaching<00:08:27.739> out<00:08:27.860> with<00:08:28.129> cheese<00:08:28.489> wizards 00:08:29.049 --> 00:08:29.059 align:start position:0% and reaching out with cheese wizards 00:08:29.059 --> 00:08:33.449 align:start position:0% and reaching out with cheese wizards what<00:08:29.449> does<00:08:29.569> that<00:08:29.599> look<00:08:29.929> like<00:08:29.959> for<00:08:30.229> you<00:08:30.379> guys<00:08:31.479> so 00:08:33.449 --> 00:08:33.459 align:start position:0% what does that look like for you guys so 00:08:33.459 --> 00:08:38.499 align:start position:0% what does that look like for you guys so cheese<00:08:34.459> wizards<00:08:35.180> stemmed<00:08:35.930> from<00:08:36.940> us<00:08:37.940> being<00:08:38.419> in 00:08:38.499 --> 00:08:38.509 align:start position:0% cheese wizards stemmed from us being in 00:08:38.509 --> 00:08:40.629 align:start position:0% cheese wizards stemmed from us being in the<00:08:38.569> room<00:08:38.779> and<00:08:39.169> thinking<00:08:39.560> about<00:08:39.680> what<00:08:40.339> is<00:08:40.459> the 00:08:40.629 --> 00:08:40.639 align:start position:0% the room and thinking about what is the 00:08:40.639 --> 00:08:43.209 align:start position:0% the room and thinking about what is the next<00:08:41.029> weirdest<00:08:41.509> thing<00:08:41.719> with<00:08:41.870> you<00:08:41.959> built<00:08:42.219> both 00:08:43.209 --> 00:08:43.219 align:start position:0% next weirdest thing with you built both 00:08:43.219 --> 00:08:45.220 align:start position:0% next weirdest thing with you built both from<00:08:43.490> a<00:08:43.579> technical<00:08:43.610> standpoint<00:08:44.480> of<00:08:44.899> building 00:08:45.220 --> 00:08:45.230 align:start position:0% from a technical standpoint of building 00:08:45.230 --> 00:08:47.199 align:start position:0% from a technical standpoint of building a<00:08:45.319> battle<00:08:45.649> royale<00:08:45.800> blockchain<00:08:46.370> game<00:08:46.610> and<00:08:46.970> the 00:08:47.199 --> 00:08:47.209 align:start position:0% a battle royale blockchain game and the 00:08:47.209 --> 00:08:50.379 align:start position:0% a battle royale blockchain game and the sense<00:08:47.420> of<00:08:47.569> mixing<00:08:47.990> cheese<00:08:48.230> with<00:08:48.560> wizards<00:08:49.389> so 00:08:50.379 --> 00:08:50.389 align:start position:0% sense of mixing cheese with wizards so 00:08:50.389 --> 00:08:52.809 align:start position:0% sense of mixing cheese with wizards so we<00:08:50.750> have<00:08:50.899> that<00:08:51.139> luxury<00:08:51.769> of<00:08:52.100> thinking 00:08:52.809 --> 00:08:52.819 align:start position:0% we have that luxury of thinking 00:08:52.819 --> 00:08:55.150 align:start position:0% we have that luxury of thinking creatively<00:08:53.300> of<00:08:53.540> you<00:08:54.079> know<00:08:54.199> what<00:08:54.769> we'll<00:08:54.949> take<00:08:55.100> a 00:08:55.150 --> 00:08:55.160 align:start position:0% creatively of you know what we'll take a 00:08:55.160 --> 00:08:58.210 align:start position:0% creatively of you know what we'll take a loss<00:08:55.569> and<00:08:56.569> how<00:08:56.990> can<00:08:57.230> we<00:08:57.350> kind<00:08:57.500> of<00:08:57.589> emanate<00:08:57.980> that 00:08:58.210 --> 00:08:58.220 align:start position:0% loss and how can we kind of emanate that 00:08:58.220 --> 00:09:01.329 align:start position:0% loss and how can we kind of emanate that as<00:08:58.370> a<00:08:58.670> project<00:08:59.620> then<00:09:00.620> we<00:09:00.649> kind<00:09:00.920> of<00:09:01.009> go<00:09:01.100> to<00:09:01.160> the 00:09:01.329 --> 00:09:01.339 align:start position:0% as a project then we kind of go to the 00:09:01.339 --> 00:09:04.509 align:start position:0% as a project then we kind of go to the step<00:09:01.610> of<00:09:01.819> building<00:09:02.350> really<00:09:03.350> fast<00:09:03.740> prototypes 00:09:04.509 --> 00:09:04.519 align:start position:0% step of building really fast prototypes 00:09:04.519 --> 00:09:08.530 align:start position:0% step of building really fast prototypes that<00:09:05.170> are<00:09:06.170> off<00:09:07.040> chain<00:09:07.430> and<00:09:07.730> we<00:09:07.970> like<00:09:08.180> to<00:09:08.209> test 00:09:08.530 --> 00:09:08.540 align:start position:0% that are off chain and we like to test 00:09:08.540 --> 00:09:11.710 align:start position:0% that are off chain and we like to test it<00:09:08.750> we've<00:09:08.990> done<00:09:09.290> probably<00:09:09.889> by<00:09:10.100> now<00:09:10.699> more<00:09:11.540> than 00:09:11.710 --> 00:09:11.720 align:start position:0% it we've done probably by now more than 00:09:11.720 --> 00:09:13.660 align:start position:0% it we've done probably by now more than 10<00:09:12.019> play<00:09:12.319> tests<00:09:12.800> of<00:09:13.009> cheese<00:09:13.279> wizards 00:09:13.660 --> 00:09:13.670 align:start position:0% 10 play tests of cheese wizards 00:09:13.670 --> 00:09:16.650 align:start position:0% 10 play tests of cheese wizards internally<00:09:14.180> and<00:09:14.449> each<00:09:14.930> iteration<00:09:15.199> we<00:09:15.709> kind<00:09:16.160> of 00:09:16.650 --> 00:09:16.660 align:start position:0% internally and each iteration we kind of 00:09:16.660 --> 00:09:19.269 align:start position:0% internally and each iteration we kind of improve<00:09:17.660> the<00:09:18.290> way<00:09:18.410> it<00:09:18.529> looks<00:09:18.740> the<00:09:18.889> way<00:09:19.040> the 00:09:19.269 --> 00:09:19.279 align:start position:0% improve the way it looks the way the 00:09:19.279 --> 00:09:21.819 align:start position:0% improve the way it looks the way the flow<00:09:19.490> goes<00:09:20.050> recently<00:09:21.050> about<00:09:21.290> three<00:09:21.529> weeks<00:09:21.709> ago 00:09:21.819 --> 00:09:21.829 align:start position:0% flow goes recently about three weeks ago 00:09:21.829 --> 00:09:25.090 align:start position:0% flow goes recently about three weeks ago we<00:09:22.670> had<00:09:22.910> the<00:09:23.750> last<00:09:23.930> final<00:09:24.439> plate<00:09:24.649> ask<00:09:24.889> for 00:09:25.090 --> 00:09:25.100 align:start position:0% we had the last final plate ask for 00:09:25.100 --> 00:09:27.280 align:start position:0% we had the last final plate ask for cheese<00:09:25.250> wizards<00:09:25.610> on<00:09:25.790> the<00:09:26.000> rinkeby<00:09:26.300> Network<00:09:26.750> it 00:09:27.280 --> 00:09:27.290 align:start position:0% cheese wizards on the rinkeby Network it 00:09:27.290 --> 00:09:29.530 align:start position:0% cheese wizards on the rinkeby Network it was<00:09:27.560> pretty<00:09:28.040> much<00:09:28.279> it<00:09:28.730> had<00:09:28.910> most<00:09:29.300> of<00:09:29.480> the 00:09:29.530 --> 00:09:29.540 align:start position:0% was pretty much it had most of the 00:09:29.540 --> 00:09:32.499 align:start position:0% was pretty much it had most of the features<00:09:29.870> that<00:09:29.899> we<00:09:30.259> are<00:09:30.290> we<00:09:30.949> have<00:09:31.360> set<00:09:32.360> the 00:09:32.499 --> 00:09:32.509 align:start position:0% features that we are we have set the 00:09:32.509 --> 00:09:35.949 align:start position:0% features that we are we have set the launch<00:09:32.689> for<00:09:32.930> next<00:09:33.170> week<00:09:33.350> and<00:09:34.389> you<00:09:35.389> know<00:09:35.420> what 00:09:35.949 --> 00:09:35.959 align:start position:0% launch for next week and you know what 00:09:35.959 --> 00:09:38.920 align:start position:0% launch for next week and you know what we<00:09:36.079> did<00:09:36.259> was<00:09:36.470> I<00:09:36.740> got<00:09:37.160> a<00:09:37.610> battle<00:09:37.910> cage<00:09:38.269> inside<00:09:38.839> of 00:09:38.920 --> 00:09:38.930 align:start position:0% we did was I got a battle cage inside of 00:09:38.930 --> 00:09:42.249 align:start position:0% we did was I got a battle cage inside of the<00:09:39.050> office<00:09:39.170> and<00:09:40.240> curated<00:09:41.240> duels<00:09:41.720> between 00:09:42.249 --> 00:09:42.259 align:start position:0% the office and curated duels between 00:09:42.259 --> 00:09:44.679 align:start position:0% the office and curated duels between different<00:09:42.680> people<00:09:43.009> in<00:09:43.220> the<00:09:43.310> company<00:09:43.639> and<00:09:44.000> not 00:09:44.679 --> 00:09:44.689 align:start position:0% different people in the company and not 00:09:44.689 --> 00:09:46.600 align:start position:0% different people in the company and not only<00:09:44.839> that<00:09:45.079> we<00:09:45.230> had<00:09:45.439> the<00:09:45.829> use<00:09:46.160> of<00:09:46.339> the<00:09:46.430> user 00:09:46.600 --> 00:09:46.610 align:start position:0% only that we had the use of the user 00:09:46.610 --> 00:09:48.490 align:start position:0% only that we had the use of the user research<00:09:47.029> team<00:09:47.300> that<00:09:47.329> was<00:09:47.660> sitting<00:09:48.050> there<00:09:48.230> and 00:09:48.490 --> 00:09:48.500 align:start position:0% research team that was sitting there and 00:09:48.500 --> 00:09:51.740 align:start position:0% research team that was sitting there and kind<00:09:49.160> of<00:09:49.250> asking<00:09:49.910> questions<00:09:49.970> and 00:09:51.740 --> 00:09:51.750 align:start position:0% kind of asking questions and 00:09:51.750 --> 00:09:53.869 align:start position:0% kind of asking questions and mapping<00:09:52.500> out<00:09:52.620> the<00:09:52.769> user<00:09:52.980> journey<00:09:53.250> and<00:09:53.759> their 00:09:53.869 --> 00:09:53.879 align:start position:0% mapping out the user journey and their 00:09:53.879 --> 00:09:55.759 align:start position:0% mapping out the user journey and their emotions<00:09:54.389> through<00:09:54.629> the<00:09:54.750> entire<00:09:55.050> process<00:09:55.350> of 00:09:55.759 --> 00:09:55.769 align:start position:0% emotions through the entire process of 00:09:55.769 --> 00:09:58.249 align:start position:0% emotions through the entire process of going<00:09:56.009> through<00:09:56.160> the<00:09:56.399> flow<00:09:56.750> and<00:09:57.750> from<00:09:58.079> that 00:09:58.249 --> 00:09:58.259 align:start position:0% going through the flow and from that 00:09:58.259 --> 00:10:00.350 align:start position:0% going through the flow and from that males<00:09:58.470> winds<00:09:59.040> will<00:09:59.189> send<00:09:59.370> the<00:09:59.579> daily<00:09:59.910> surveys 00:10:00.350 --> 00:10:00.360 align:start position:0% males winds will send the daily surveys 00:10:00.360 --> 00:10:03.110 align:start position:0% males winds will send the daily surveys to<00:10:00.689> capture<00:10:01.259> all<00:10:01.410> the<00:10:01.560> information<00:10:02.029> from<00:10:03.029> the 00:10:03.110 --> 00:10:03.120 align:start position:0% to capture all the information from the 00:10:03.120 --> 00:10:05.420 align:start position:0% to capture all the information from the team<00:10:03.389> members<00:10:03.769> we<00:10:04.769> usually<00:10:05.100> start<00:10:05.339> with 00:10:05.420 --> 00:10:05.430 align:start position:0% team members we usually start with 00:10:05.430 --> 00:10:08.900 align:start position:0% team members we usually start with internal<00:10:06.389> then<00:10:06.779> we<00:10:06.959> invite<00:10:07.439> a<00:10:07.769> core<00:10:08.459> group<00:10:08.699> of 00:10:08.900 --> 00:10:08.910 align:start position:0% internal then we invite a core group of 00:10:08.910 --> 00:10:10.910 align:start position:0% internal then we invite a core group of maybe<00:10:09.269> a<00:10:09.389> small<00:10:09.810> sample<00:10:10.139> size<00:10:10.319> of<00:10:10.500> external 00:10:10.910 --> 00:10:10.920 align:start position:0% maybe a small sample size of external 00:10:10.920 --> 00:10:13.009 align:start position:0% maybe a small sample size of external players<00:10:11.189> to<00:10:11.699> come<00:10:11.939> and<00:10:12.149> play<00:10:12.269> and<00:10:12.660> we<00:10:12.750> do<00:10:12.899> the 00:10:13.009 --> 00:10:13.019 align:start position:0% players to come and play and we do the 00:10:13.019 --> 00:10:14.689 align:start position:0% players to come and play and we do the same<00:10:13.170> thing<00:10:13.410> where<00:10:13.620> we<00:10:14.009> measure<00:10:14.220> every<00:10:14.550> day 00:10:14.689 --> 00:10:14.699 align:start position:0% same thing where we measure every day 00:10:14.699 --> 00:10:17.059 align:start position:0% same thing where we measure every day and<00:10:15.000> see<00:10:15.240> where<00:10:15.959> we<00:10:16.110> can<00:10:16.230> improve<00:10:16.379> and<00:10:16.920> then 00:10:17.059 --> 00:10:17.069 align:start position:0% and see where we can improve and then 00:10:17.069 --> 00:10:18.829 align:start position:0% and see where we can improve and then that<00:10:17.279> gets<00:10:17.639> funneled<00:10:17.970> to<00:10:18.180> engineering<00:10:18.720> and 00:10:18.829 --> 00:10:18.839 align:start position:0% that gets funneled to engineering and 00:10:18.839 --> 00:10:22.610 align:start position:0% that gets funneled to engineering and design<00:10:19.220> then<00:10:20.420> now<00:10:21.420> we're<00:10:22.079> at<00:10:22.230> this<00:10:22.379> point 00:10:22.610 --> 00:10:22.620 align:start position:0% design then now we're at this point 00:10:22.620 --> 00:10:24.290 align:start position:0% design then now we're at this point where<00:10:22.800> we've<00:10:23.129> been<00:10:23.310> we<00:10:23.579> have<00:10:23.730> an<00:10:23.850> open<00:10:24.120> beta 00:10:24.290 --> 00:10:24.300 align:start position:0% where we've been we have an open beta 00:10:24.300 --> 00:10:26.600 align:start position:0% where we've been we have an open beta this<00:10:24.540> entire<00:10:24.930> week<00:10:25.170> so<00:10:26.009> we<00:10:26.129> welcome<00:10:26.339> the 00:10:26.600 --> 00:10:26.610 align:start position:0% this entire week so we welcome the 00:10:26.610 --> 00:10:29.780 align:start position:0% this entire week so we welcome the entire<00:10:27.019> space<00:10:28.019> here<00:10:28.379> at<00:10:28.500> Def<00:10:28.680> Con<00:10:28.709> and<00:10:29.279> our 00:10:29.780 --> 00:10:29.790 align:start position:0% entire space here at Def Con and our 00:10:29.790 --> 00:10:32.900 align:start position:0% entire space here at Def Con and our community<00:10:30.269> to<00:10:30.449> play<00:10:30.629> the<00:10:30.750> game<00:10:30.959> and<00:10:31.519> we<00:10:32.519> have<00:10:32.730> a 00:10:32.900 --> 00:10:32.910 align:start position:0% community to play the game and we have a 00:10:32.910 --> 00:10:36.410 align:start position:0% community to play the game and we have a website<00:10:33.209> like<00:10:33.660> any<00:10:34.620> any<00:10:34.949> bugs<00:10:35.459> or<00:10:35.670> issues<00:10:36.120> feel 00:10:36.410 --> 00:10:36.420 align:start position:0% website like any any bugs or issues feel 00:10:36.420 --> 00:10:38.059 align:start position:0% website like any any bugs or issues feel free<00:10:36.600> to<00:10:36.629> fill<00:10:36.839> out<00:10:36.930> the<00:10:37.019> form<00:10:37.290> and<00:10:37.470> that's<00:10:37.829> how 00:10:38.059 --> 00:10:38.069 align:start position:0% free to fill out the form and that's how 00:10:38.069 --> 00:10:39.379 align:start position:0% free to fill out the form and that's how we<00:10:38.129> usually<00:10:38.399> capture<00:10:39.000> a<00:10:39.029> lot<00:10:39.269> of<00:10:39.300> the 00:10:39.379 --> 00:10:39.389 align:start position:0% we usually capture a lot of the 00:10:39.389 --> 00:10:41.480 align:start position:0% we usually capture a lot of the information<00:10:39.959> and<00:10:40.290> funnel<00:10:40.800> it<00:10:40.889> off<00:10:41.040> the<00:10:41.160> design 00:10:41.480 --> 00:10:41.490 align:start position:0% information and funnel it off the design 00:10:41.490 --> 00:10:43.850 align:start position:0% information and funnel it off the design and<00:10:41.939> engineering<00:10:42.329> and<00:10:43.170> then<00:10:43.350> build<00:10:43.560> all<00:10:43.680> those 00:10:43.850 --> 00:10:43.860 align:start position:0% and engineering and then build all those 00:10:43.860 --> 00:10:46.040 align:start position:0% and engineering and then build all those features<00:10:44.100> inside<00:10:44.670> of<00:10:44.759> the<00:10:44.819> game<00:10:45.000> now<00:10:45.839> I<00:10:45.899> want 00:10:46.040 --> 00:10:46.050 align:start position:0% features inside of the game now I want 00:10:46.050 --> 00:10:47.480 align:start position:0% features inside of the game now I want to<00:10:46.110> pull<00:10:46.319> from<00:10:46.350> that<00:10:46.709> like<00:10:47.009> that<00:10:47.220> user 00:10:47.480 --> 00:10:47.490 align:start position:0% to pull from that like that user 00:10:47.490 --> 00:10:50.150 align:start position:0% to pull from that like that user research<00:10:48.000> component<00:10:48.689> of<00:10:48.839> it<00:10:49.019> that<00:10:49.680> that's 00:10:50.150 --> 00:10:50.160 align:start position:0% research component of it that that's 00:10:50.160 --> 00:10:51.920 align:start position:0% research component of it that that's been<00:10:50.399> a<00:10:50.430> big<00:10:50.699> narrative<00:10:50.939> this<00:10:51.420> year<00:10:51.660> at<00:10:51.750> Def 00:10:51.920 --> 00:10:51.930 align:start position:0% been a big narrative this year at Def 00:10:51.930 --> 00:10:53.629 align:start position:0% been a big narrative this year at Def Con<00:10:52.050> last<00:10:52.529> year<00:10:52.769> it<00:10:52.829> was<00:10:52.949> kind<00:10:53.129> of<00:10:53.220> like<00:10:53.370> mass 00:10:53.629 --> 00:10:53.639 align:start position:0% Con last year it was kind of like mass 00:10:53.639 --> 00:10:56.449 align:start position:0% Con last year it was kind of like mass adoption<00:10:53.879> mass<00:10:54.209> adoption<00:10:54.620> and<00:10:55.620> and<00:10:56.009> before 00:10:56.449 --> 00:10:56.459 align:start position:0% adoption mass adoption and and before 00:10:56.459 --> 00:10:58.249 align:start position:0% adoption mass adoption and and before that<00:10:56.490> it<00:10:56.790> was<00:10:56.910> like<00:10:56.939> how<00:10:57.209> do<00:10:57.269> we<00:10:57.509> understand<00:10:57.990> it 00:10:58.249 --> 00:10:58.259 align:start position:0% that it was like how do we understand it 00:10:58.259 --> 00:11:00.499 align:start position:0% that it was like how do we understand it to<00:10:58.379> know<00:10:58.500> her<00:10:58.620> users<00:10:59.009> better<00:10:59.250> and<00:10:59.610> so<00:11:00.149> pulling 00:11:00.499 --> 00:11:00.509 align:start position:0% to know her users better and so pulling 00:11:00.509 --> 00:11:01.790 align:start position:0% to know her users better and so pulling from<00:11:00.839> that<00:11:01.019> we<00:11:01.139> were<00:11:01.259> just<00:11:01.439> talking<00:11:01.500> about 00:11:01.790 --> 00:11:01.800 align:start position:0% from that we were just talking about 00:11:01.800 --> 00:11:04.280 align:start position:0% from that we were just talking about market<00:11:02.279> research<00:11:02.430> versus<00:11:03.209> design<00:11:03.870> research 00:11:04.280 --> 00:11:04.290 align:start position:0% market research versus design research 00:11:04.290 --> 00:11:06.829 align:start position:0% market research versus design research and<00:11:04.850> the<00:11:05.850> team<00:11:06.000> from<00:11:06.120> Sela<00:11:06.389> said<00:11:06.629> it<00:11:06.720> really 00:11:06.829 --> 00:11:06.839 align:start position:0% and the team from Sela said it really 00:11:06.839 --> 00:11:09.019 align:start position:0% and the team from Sela said it really well<00:11:06.990> which<00:11:07.439> is<00:11:07.620> with<00:11:08.250> different<00:11:08.639> Oh<00:11:08.850> with 00:11:09.019 --> 00:11:09.029 align:start position:0% well which is with different Oh with 00:11:09.029 --> 00:11:10.819 align:start position:0% well which is with different Oh with market<00:11:09.389> research<00:11:09.420> you<00:11:10.019> might<00:11:10.199> get<00:11:10.470> a<00:11:10.500> hundred 00:11:10.819 --> 00:11:10.829 align:start position:0% market research you might get a hundred 00:11:10.829 --> 00:11:13.519 align:start position:0% market research you might get a hundred people<00:11:11.100> and<00:11:11.639> get<00:11:12.029> ten<00:11:12.240> insights<00:11:12.600> but<00:11:13.290> with 00:11:13.519 --> 00:11:13.529 align:start position:0% people and get ten insights but with 00:11:13.529 --> 00:11:15.379 align:start position:0% people and get ten insights but with design<00:11:13.829> research<00:11:14.160> you<00:11:14.339> get<00:11:14.459> ten<00:11:14.730> people<00:11:14.970> and 00:11:15.379 --> 00:11:15.389 align:start position:0% design research you get ten people and 00:11:15.389 --> 00:11:16.879 align:start position:0% design research you get ten people and get<00:11:15.569> a<00:11:15.600> hundred<00:11:15.839> insights<00:11:16.290> so<00:11:16.529> you're<00:11:16.649> going 00:11:16.879 --> 00:11:16.889 align:start position:0% get a hundred insights so you're going 00:11:16.889 --> 00:11:18.889 align:start position:0% get a hundred insights so you're going super<00:11:17.220> deep<00:11:17.459> and<00:11:17.730> taking<00:11:18.149> that<00:11:18.269> time<00:11:18.480> to<00:11:18.720> ask 00:11:18.889 --> 00:11:18.899 align:start position:0% super deep and taking that time to ask 00:11:18.899 --> 00:11:22.280 align:start position:0% super deep and taking that time to ask them<00:11:19.610> how<00:11:20.610> we<00:11:21.089> not<00:11:21.360> just<00:11:21.389> questions<00:11:21.899> about 00:11:22.280 --> 00:11:22.290 align:start position:0% them how we not just questions about 00:11:22.290 --> 00:11:24.740 align:start position:0% them how we not just questions about your<00:11:22.439> product<00:11:22.949> but<00:11:23.519> questions<00:11:23.970> around<00:11:24.240> what 00:11:24.740 --> 00:11:24.750 align:start position:0% your product but questions around what 00:11:24.750 --> 00:11:28.129 align:start position:0% your product but questions around what how<00:11:25.170> do<00:11:25.230> you<00:11:25.470> go<00:11:26.370> about<00:11:26.490> your<00:11:27.089> your<00:11:27.449> flow<00:11:27.839> like 00:11:28.129 --> 00:11:28.139 align:start position:0% how do you go about your your flow like 00:11:28.139 --> 00:11:30.019 align:start position:0% how do you go about your your flow like your<00:11:28.290> goal<00:11:28.559> how<00:11:29.129> do<00:11:29.189> you<00:11:29.279> get<00:11:29.430> a<00:11:29.550> person<00:11:29.910> to 00:11:30.019 --> 00:11:30.029 align:start position:0% your goal how do you get a person to 00:11:30.029 --> 00:11:31.699 align:start position:0% your goal how do you get a person to finish<00:11:30.180> that<00:11:30.389> goal<00:11:30.600> maybe<00:11:30.809> it's<00:11:31.019> like<00:11:31.170> going 00:11:31.699 --> 00:11:31.709 align:start position:0% finish that goal maybe it's like going 00:11:31.709 --> 00:11:33.139 align:start position:0% finish that goal maybe it's like going to<00:11:31.740> the<00:11:31.949> bank<00:11:32.100> okay<00:11:32.519> what<00:11:32.699> happens<00:11:32.970> if<00:11:33.059> you 00:11:33.139 --> 00:11:33.149 align:start position:0% to the bank okay what happens if you 00:11:33.149 --> 00:11:35.629 align:start position:0% to the bank okay what happens if you lost<00:11:33.360> your<00:11:33.569> money<00:11:33.720> where<00:11:33.959> do<00:11:34.050> you<00:11:34.139> go<00:11:34.430> and<00:11:35.430> that 00:11:35.629 --> 00:11:35.639 align:start position:0% lost your money where do you go and that 00:11:35.639 --> 00:11:37.160 align:start position:0% lost your money where do you go and that doesn't<00:11:36.180> have<00:11:36.269> to<00:11:36.300> be<00:11:36.449> directly<00:11:36.870> correlated 00:11:37.160 --> 00:11:37.170 align:start position:0% doesn't have to be directly correlated 00:11:37.170 --> 00:11:39.110 align:start position:0% doesn't have to be directly correlated to<00:11:37.559> your<00:11:37.829> product<00:11:38.279> because<00:11:38.879> you're<00:11:39.000> not 00:11:39.110 --> 00:11:39.120 align:start position:0% to your product because you're not 00:11:39.120 --> 00:11:40.819 align:start position:0% to your product because you're not trying<00:11:39.389> to<00:11:39.449> tell<00:11:40.019> them<00:11:40.230> like<00:11:40.379> this<00:11:40.620> is<00:11:40.800> a 00:11:40.819 --> 00:11:40.829 align:start position:0% trying to tell them like this is a 00:11:40.829 --> 00:11:42.110 align:start position:0% trying to tell them like this is a product<00:11:41.100> that's<00:11:41.250> going<00:11:41.550> to<00:11:41.670> solve 00:11:42.110 --> 00:11:42.120 align:start position:0% product that's going to solve 00:11:42.120 --> 00:11:43.999 align:start position:0% product that's going to solve your<00:11:42.449> need<00:11:42.689> if<00:11:43.230> you<00:11:43.379> don't<00:11:43.529> know<00:11:43.680> what<00:11:43.860> those 00:11:43.999 --> 00:11:44.009 align:start position:0% your need if you don't know what those 00:11:44.009 --> 00:11:47.540 align:start position:0% your need if you don't know what those needs<00:11:44.189> are<00:11:44.370> yet<00:11:44.689> so<00:11:45.689> so<00:11:46.079> kind<00:11:46.559> of<00:11:46.680> back<00:11:47.040> to<00:11:47.309> that 00:11:47.540 --> 00:11:47.550 align:start position:0% needs are yet so so kind of back to that 00:11:47.550 --> 00:11:49.790 align:start position:0% needs are yet so so kind of back to that let's<00:11:48.029> go<00:11:48.180> back<00:11:48.360> to<00:11:48.480> use<00:11:48.689> like<00:11:48.899> a<00:11:48.930> usability 00:11:49.790 --> 00:11:49.800 align:start position:0% let's go back to use like a usability 00:11:49.800 --> 00:11:52.280 align:start position:0% let's go back to use like a usability and<00:11:50.040> what<00:11:50.970> I<00:11:50.999> call<00:11:51.209> the<00:11:51.360> responsibility<00:11:51.600> of 00:11:52.280 --> 00:11:52.290 align:start position:0% and what I call the responsibility of 00:11:52.290 --> 00:11:55.220 align:start position:0% and what I call the responsibility of the<00:11:52.529> creator<00:11:52.920> and<00:11:53.249> so<00:11:54.240> you<00:11:54.300> guys<00:11:54.569> have<00:11:54.870> one<00:11:55.110> of 00:11:55.220 --> 00:11:55.230 align:start position:0% the creator and so you guys have one of 00:11:55.230 --> 00:11:56.569 align:start position:0% the creator and so you guys have one of the<00:11:55.319> biggest<00:11:55.589> products<00:11:56.160> you<00:11:56.279> literally 00:11:56.569 --> 00:11:56.579 align:start position:0% the biggest products you literally 00:11:56.579 --> 00:12:01.220 align:start position:0% the biggest products you literally propyl<00:11:57.059> cerium<00:11:57.420> but<00:11:59.059> but<00:12:00.059> what<00:12:00.809> do<00:12:00.899> you<00:12:00.959> guys 00:12:01.220 --> 00:12:01.230 align:start position:0% propyl cerium but but what do you guys 00:12:01.230 --> 00:12:04.040 align:start position:0% propyl cerium but but what do you guys find<00:12:01.529> that<00:12:01.709> for<00:12:02.670> your<00:12:02.819> users<00:12:03.180> what<00:12:03.809> do<00:12:03.959> you 00:12:04.040 --> 00:12:04.050 align:start position:0% find that for your users what do you 00:12:04.050 --> 00:12:06.769 align:start position:0% find that for your users what do you guys<00:12:04.290> try<00:12:04.649> to<00:12:04.709> do<00:12:04.949> to<00:12:05.129> protect<00:12:05.699> them<00:12:05.939> or<00:12:06.209> give 00:12:06.769 --> 00:12:06.779 align:start position:0% guys try to do to protect them or give 00:12:06.779 --> 00:12:09.049 align:start position:0% guys try to do to protect them or give an<00:12:06.930> end<00:12:07.139> of<00:12:07.199> the<00:12:07.319> space<00:12:07.589> what's<00:12:08.009> different<00:12:08.519> in 00:12:09.049 --> 00:12:09.059 align:start position:0% an end of the space what's different in 00:12:09.059 --> 00:12:10.759 align:start position:0% an end of the space what's different in the<00:12:09.180> way<00:12:09.300> that<00:12:09.480> you're<00:12:09.600> creating<00:12:10.230> product 00:12:10.759 --> 00:12:10.769 align:start position:0% the way that you're creating product 00:12:10.769 --> 00:12:13.999 align:start position:0% the way that you're creating product that<00:12:10.889> you<00:12:10.980> think<00:12:11.189> about<00:12:12.470> or<00:12:13.470> do<00:12:13.680> you<00:12:13.769> want<00:12:13.920> to 00:12:13.999 --> 00:12:14.009 align:start position:0% that you think about or do you want to 00:12:14.009 --> 00:12:19.420 align:start position:0% that you think about or do you want to start<00:12:17.059> go<00:12:18.059> ahead 00:12:19.420 --> 00:12:19.430 align:start position:0% start go ahead 00:12:19.430 --> 00:12:22.189 align:start position:0% start go ahead so<00:12:20.430> is<00:12:20.550> it<00:12:20.670> in<00:12:20.790> comparison<00:12:21.120> to<00:12:21.509> how<00:12:21.930> other 00:12:22.189 --> 00:12:22.199 align:start position:0% so is it in comparison to how other 00:12:22.199 --> 00:12:24.949 align:start position:0% so is it in comparison to how other clock<00:12:22.559> changes<00:12:22.889> building<00:12:23.370> built<00:12:23.819> games<00:12:24.600> and 00:12:24.949 --> 00:12:24.959 align:start position:0% clock changes building built games and 00:12:24.959 --> 00:12:27.230 align:start position:0% clock changes building built games and the<00:12:25.529> way<00:12:25.680> that<00:12:25.889> they<00:12:26.040> build<00:12:26.220> process<00:12:26.730> or<00:12:26.999> in 00:12:27.230 --> 00:12:27.240 align:start position:0% the way that they build process or in 00:12:27.240 --> 00:12:30.949 align:start position:0% the way that they build process or in comparison<00:12:27.839> to<00:12:27.990> defy<00:12:28.889> or<00:12:29.459> other<00:12:30.089> lives<00:12:30.540> yeah 00:12:30.949 --> 00:12:30.959 align:start position:0% comparison to defy or other lives yeah 00:12:30.959 --> 00:12:32.420 align:start position:0% comparison to defy or other lives yeah it's<00:12:31.139> hard<00:12:31.259> to<00:12:31.350> kids<00:12:31.529> you<00:12:31.589> guys<00:12:31.769> all<00:12:32.040> have<00:12:32.220> so 00:12:32.420 --> 00:12:32.430 align:start position:0% it's hard to kids you guys all have so 00:12:32.430 --> 00:12:36.710 align:start position:0% it's hard to kids you guys all have so many<00:12:33.860> so<00:12:34.860> I<00:12:35.309> would<00:12:35.670> say<00:12:35.850> I<00:12:35.879> mean<00:12:36.449> I<00:12:36.540> think 00:12:36.710 --> 00:12:36.720 align:start position:0% many so I would say I mean I think 00:12:36.720 --> 00:12:38.900 align:start position:0% many so I would say I mean I think generally<00:12:37.259> a<00:12:37.290> lot<00:12:37.439> of<00:12:37.559> people<00:12:37.889> are<00:12:38.370> thinking 00:12:38.900 --> 00:12:38.910 align:start position:0% generally a lot of people are thinking 00:12:38.910 --> 00:12:42.769 align:start position:0% generally a lot of people are thinking about<00:12:39.269> how<00:12:39.779> they<00:12:40.350> build<00:12:40.589> the<00:12:40.709> product<00:12:41.149> so<00:12:42.149> when 00:12:42.769 --> 00:12:42.779 align:start position:0% about how they build the product so when 00:12:42.779 --> 00:12:43.819 align:start position:0% about how they build the product so when you're<00:12:42.930> building<00:12:43.139> the<00:12:43.319> product<00:12:43.680> there's 00:12:43.819 --> 00:12:43.829 align:start position:0% you're building the product there's 00:12:43.829 --> 00:12:48.470 align:start position:0% you're building the product there's fundamental<00:12:44.779> kind<00:12:45.779> of<00:12:46.040> decide<00:12:47.040> decisions<00:12:47.910> in 00:12:48.470 --> 00:12:48.480 align:start position:0% fundamental kind of decide decisions in 00:12:48.480 --> 00:12:50.989 align:start position:0% fundamental kind of decide decisions in that<00:12:48.870> you<00:12:49.110> cream<00:12:49.410> while<00:12:50.370> you're<00:12:50.550> creating<00:12:50.790> the 00:12:50.989 --> 00:12:50.999 align:start position:0% that you cream while you're creating the 00:12:50.999 --> 00:12:52.669 align:start position:0% that you cream while you're creating the product<00:12:51.389> and<00:12:51.540> that<00:12:51.629> has<00:12:51.929> to<00:12:52.110> do<00:12:52.259> with<00:12:52.290> kind<00:12:52.649> of 00:12:52.669 --> 00:12:52.679 align:start position:0% product and that has to do with kind of 00:12:52.679 --> 00:12:56.239 align:start position:0% product and that has to do with kind of the<00:12:52.829> underlying<00:12:53.249> these<00:12:53.429> are<00:12:53.639> needs<00:12:53.850> I<00:12:55.249> think 00:12:56.239 --> 00:12:56.249 align:start position:0% the underlying these are needs I think 00:12:56.249 --> 00:12:58.249 align:start position:0% the underlying these are needs I think for<00:12:56.399> me<00:12:56.519> it's<00:12:56.610> about<00:12:56.759> of<00:12:57.600> course<00:12:58.019> you<00:12:58.110> make 00:12:58.249 --> 00:12:58.259 align:start position:0% for me it's about of course you make 00:12:58.259 --> 00:12:59.749 align:start position:0% for me it's about of course you make choice<00:12:58.470> when<00:12:58.740> you<00:12:58.800> design<00:12:59.069> a<00:12:59.100> product<00:12:59.399> can<00:12:59.670> you 00:12:59.749 --> 00:12:59.759 align:start position:0% choice when you design a product can you 00:12:59.759 --> 00:13:01.009 align:start position:0% choice when you design a product can you make<00:12:59.910> sure<00:13:00.089> it's<00:13:00.240> not<00:13:00.360> yeah<00:13:00.569> from<00:13:00.720> the<00:13:00.839> user 00:13:01.009 --> 00:13:01.019 align:start position:0% make sure it's not yeah from the user 00:13:01.019 --> 00:13:02.389 align:start position:0% make sure it's not yeah from the user but<00:13:01.259> I<00:13:01.319> think<00:13:01.559> something<00:13:02.100> that's<00:13:02.189> very 00:13:02.389 --> 00:13:02.399 align:start position:0% but I think something that's very 00:13:02.399 --> 00:13:04.639 align:start position:0% but I think something that's very important<00:13:02.879> is<00:13:02.999> to<00:13:03.110> inform<00:13:04.110> the<00:13:04.230> user<00:13:04.379> about 00:13:04.639 --> 00:13:04.649 align:start position:0% important is to inform the user about 00:13:04.649 --> 00:13:06.829 align:start position:0% important is to inform the user about these<00:13:04.920> choices<00:13:05.459> and<00:13:05.610> making<00:13:06.360> sure<00:13:06.569> you're<00:13:06.779> not 00:13:06.829 --> 00:13:06.839 align:start position:0% these choices and making sure you're not 00:13:06.839 --> 00:13:07.699 align:start position:0% these choices and making sure you're not hiding<00:13:07.079> anything 00:13:07.699 --> 00:13:07.709 align:start position:0% hiding anything 00:13:07.709 --> 00:13:09.439 align:start position:0% hiding anything so<00:13:08.009> I<00:13:08.040> think<00:13:08.399> users<00:13:08.550> have<00:13:08.850> to<00:13:08.970> make<00:13:09.120> conscious 00:13:09.439 --> 00:13:09.449 align:start position:0% so I think users have to make conscious 00:13:09.449 --> 00:13:11.689 align:start position:0% so I think users have to make conscious choices<00:13:09.569> and<00:13:10.259> know<00:13:10.439> maybe<00:13:11.100> the<00:13:11.249> compromise 00:13:11.689 --> 00:13:11.699 align:start position:0% choices and know maybe the compromise 00:13:11.699 --> 00:13:13.639 align:start position:0% choices and know maybe the compromise they<00:13:11.910> are<00:13:11.970> making<00:13:12.179> some<00:13:12.600> user<00:13:12.809> eyes<00:13:13.079> are<00:13:13.319> fine 00:13:13.639 --> 00:13:13.649 align:start position:0% they are making some user eyes are fine 00:13:13.649 --> 00:13:16.429 align:start position:0% they are making some user eyes are fine using<00:13:13.920> a<00:13:14.249> custodial<00:13:14.819> service<00:13:15.179> some<00:13:15.870> users<00:13:16.170> may 00:13:16.429 --> 00:13:16.439 align:start position:0% using a custodial service some users may 00:13:16.439 --> 00:13:17.809 align:start position:0% using a custodial service some users may not<00:13:16.589> need<00:13:16.740> so<00:13:16.889> I<00:13:16.949> think<00:13:17.129> it's<00:13:17.249> important<00:13:17.730> that 00:13:17.809 --> 00:13:17.819 align:start position:0% not need so I think it's important that 00:13:17.819 --> 00:13:20.480 align:start position:0% not need so I think it's important that actually<00:13:17.939> we<00:13:18.679> educate<00:13:19.679> we<00:13:19.800> inform<00:13:20.189> the<00:13:20.309> user 00:13:20.480 --> 00:13:20.490 align:start position:0% actually we educate we inform the user 00:13:20.490 --> 00:13:22.669 align:start position:0% actually we educate we inform the user about<00:13:21.480> the<00:13:21.600> choice<00:13:21.779> that<00:13:21.809> he's<00:13:22.110> making<00:13:22.290> in<00:13:22.559> the 00:13:22.669 --> 00:13:22.679 align:start position:0% about the choice that he's making in the 00:13:22.679 --> 00:13:24.799 align:start position:0% about the choice that he's making in the trade-off<00:13:23.100> that<00:13:23.339> you<00:13:23.459> may<00:13:23.639> may<00:13:24.120> get<00:13:24.360> from<00:13:24.629> the 00:13:24.799 --> 00:13:24.809 align:start position:0% trade-off that you may may get from the 00:13:24.809 --> 00:13:26.360 align:start position:0% trade-off that you may may get from the choice<00:13:25.019> that<00:13:25.050> he's<00:13:25.439> making<00:13:25.649> I<00:13:25.949> think<00:13:26.129> this<00:13:26.249> is 00:13:26.360 --> 00:13:26.370 align:start position:0% choice that he's making I think this is 00:13:26.370 --> 00:13:27.919 align:start position:0% choice that he's making I think this is something<00:13:26.610> for<00:13:26.939> us<00:13:27.029> that's<00:13:27.240> very<00:13:27.360> important 00:13:27.919 --> 00:13:27.929 align:start position:0% something for us that's very important 00:13:27.929 --> 00:13:30.410 align:start position:0% something for us that's very important also<00:13:28.920> a<00:13:29.129> thousand<00:13:29.579> but<00:13:29.879> we<00:13:30.029> believe<00:13:30.240> that 00:13:30.410 --> 00:13:30.420 align:start position:0% also a thousand but we believe that 00:13:30.420 --> 00:13:32.119 align:start position:0% also a thousand but we believe that there<00:13:30.569> is<00:13:30.600> a<00:13:30.689> boulder<00:13:31.079> or<00:13:31.230> not<00:13:31.379> to<00:13:31.499> cross<00:13:31.709> so 00:13:32.119 --> 00:13:32.129 align:start position:0% there is a boulder or not to cross so 00:13:32.129 --> 00:13:33.619 align:start position:0% there is a boulder or not to cross so there's<00:13:32.309> some<00:13:32.490> core<00:13:32.730> as<00:13:33.029> I<00:13:33.120> mentioned<00:13:33.509> some 00:13:33.619 --> 00:13:33.629 align:start position:0% there's some core as I mentioned some 00:13:33.629 --> 00:13:35.749 align:start position:0% there's some core as I mentioned some core<00:13:33.929> principle<00:13:34.860> that<00:13:34.889> we<00:13:35.370> don't<00:13:35.550> want<00:13:35.699> to 00:13:35.749 --> 00:13:35.759 align:start position:0% core principle that we don't want to 00:13:35.759 --> 00:13:37.699 align:start position:0% core principle that we don't want to compromise<00:13:35.910> on<00:13:36.449> and<00:13:36.720> then<00:13:37.110> after<00:13:37.350> that<00:13:37.470> all 00:13:37.699 --> 00:13:37.709 align:start position:0% compromise on and then after that all 00:13:37.709 --> 00:13:39.019 align:start position:0% compromise on and then after that all that<00:13:37.829> goes<00:13:38.040> on<00:13:38.160> top<00:13:38.309> of<00:13:38.370> that<00:13:38.490> is<00:13:38.759> really<00:13:38.939> a 00:13:39.019 --> 00:13:39.029 align:start position:0% that goes on top of that is really a 00:13:39.029 --> 00:13:41.180 align:start position:0% that goes on top of that is really a question<00:13:39.449> of<00:13:39.600> of<00:13:39.860> informing<00:13:40.860> the 00:13:41.180 --> 00:13:41.190 align:start position:0% question of of informing the 00:13:41.190 --> 00:13:43.040 align:start position:0% question of of informing the and<00:13:41.730> helping<00:13:42.120> in<00:13:42.270> making<00:13:42.750> a<00:13:42.840> wise<00:13:43.020> choice 00:13:43.040 --> 00:13:43.050 align:start position:0% and helping in making a wise choice 00:13:43.050 --> 00:13:46.070 align:start position:0% and helping in making a wise choice because<00:13:43.680> it's<00:13:43.860> easy<00:13:44.100> to<00:13:44.220> too<00:13:45.060> badly<00:13:45.270> inform<00:13:45.780> or 00:13:46.070 --> 00:13:46.080 align:start position:0% because it's easy to too badly inform or 00:13:46.080 --> 00:13:47.510 align:start position:0% because it's easy to too badly inform or to<00:13:46.200> add<00:13:46.380> something<00:13:46.650> and<00:13:46.920> make<00:13:47.040> decision<00:13:47.430> I 00:13:47.510 --> 00:13:47.520 align:start position:0% to add something and make decision I 00:13:47.520 --> 00:13:48.920 align:start position:0% to add something and make decision I think<00:13:47.700> it's<00:13:47.820> it's<00:13:48.060> actually<00:13:48.210> the<00:13:48.510> UX<00:13:48.780> is 00:13:48.920 --> 00:13:48.930 align:start position:0% think it's it's actually the UX is 00:13:48.930 --> 00:13:51.440 align:start position:0% think it's it's actually the UX is really<00:13:49.710> responsible<00:13:50.160> of<00:13:50.370> that<00:13:50.520> is<00:13:50.670> letting 00:13:51.440 --> 00:13:51.450 align:start position:0% really responsible of that is letting 00:13:51.450 --> 00:13:53.030 align:start position:0% really responsible of that is letting the<00:13:51.570> user<00:13:51.720> be<00:13:52.020> informed<00:13:52.470> about<00:13:52.560> the<00:13:52.680> choices 00:13:53.030 --> 00:13:53.040 align:start position:0% the user be informed about the choices 00:13:53.040 --> 00:13:53.900 align:start position:0% the user be informed about the choices that<00:13:53.190> is<00:13:53.400> making 00:13:53.900 --> 00:13:53.910 align:start position:0% that is making 00:13:53.910 --> 00:13:56.000 align:start position:0% that is making yeah<00:13:54.180> I<00:13:54.240> want<00:13:54.420> to<00:13:54.510> pull<00:13:54.690> that<00:13:54.720> Apple<00:13:55.350> from<00:13:55.830> that 00:13:56.000 --> 00:13:56.010 align:start position:0% yeah I want to pull that Apple from that 00:13:56.010 --> 00:13:57.140 align:start position:0% yeah I want to pull that Apple from that and<00:13:56.190> although<00:13:56.310> we'll<00:13:56.490> get<00:13:56.700> to<00:13:56.850> you<00:13:57.000> because 00:13:57.140 --> 00:13:57.150 align:start position:0% and although we'll get to you because 00:13:57.150 --> 00:13:59.900 align:start position:0% and although we'll get to you because it's<00:13:57.750> there's<00:13:58.260> some<00:13:58.770> ideas<00:13:59.310> around<00:13:59.700> the 00:13:59.900 --> 00:13:59.910 align:start position:0% it's there's some ideas around the 00:13:59.910 --> 00:14:02.210 align:start position:0% it's there's some ideas around the abstraction<00:14:00.570> of<00:14:00.720> information<00:14:01.380> to<00:14:02.010> avoid 00:14:02.210 --> 00:14:02.220 align:start position:0% abstraction of information to avoid 00:14:02.220 --> 00:14:05.150 align:start position:0% abstraction of information to avoid complexity<00:14:02.940> for<00:14:03.270> the<00:14:03.390> user<00:14:03.570> and<00:14:03.990> so<00:14:04.860> I<00:14:04.890> know 00:14:05.150 --> 00:14:05.160 align:start position:0% complexity for the user and so I know 00:14:05.160 --> 00:14:07.490 align:start position:0% complexity for the user and so I know coinbase<00:14:05.610> it<00:14:05.970> has<00:14:06.240> Pro<00:14:06.840> you<00:14:07.140> guys<00:14:07.290> have 00:14:07.490 --> 00:14:07.500 align:start position:0% coinbase it has Pro you guys have 00:14:07.500 --> 00:14:09.260 align:start position:0% coinbase it has Pro you guys have conservative<00:14:08.190> so<00:14:08.280> real<00:14:08.460> non-custodial<00:14:08.790> you 00:14:09.260 --> 00:14:09.270 align:start position:0% conservative so real non-custodial you 00:14:09.270 --> 00:14:10.730 align:start position:0% conservative so real non-custodial you guys<00:14:09.420> have<00:14:09.630> different<00:14:09.990> kinds<00:14:10.260> of<00:14:10.290> users<00:14:10.470> as 00:14:10.730 --> 00:14:10.740 align:start position:0% guys have different kinds of users as 00:14:10.740 --> 00:14:13.370 align:start position:0% guys have different kinds of users as well<00:14:11.120> how<00:14:12.120> this<00:14:12.330> how's<00:14:12.570> that<00:14:12.750> structured<00:14:13.200> for 00:14:13.370 --> 00:14:13.380 align:start position:0% well how this how's that structured for 00:14:13.380 --> 00:14:15.380 align:start position:0% well how this how's that structured for you<00:14:13.470> guys<00:14:13.650> and<00:14:13.950> what<00:14:14.370> have<00:14:14.520> you<00:14:14.700> kind<00:14:14.970> of<00:14:15.060> seen 00:14:15.380 --> 00:14:15.390 align:start position:0% you guys and what have you kind of seen 00:14:15.390 --> 00:14:18.740 align:start position:0% you guys and what have you kind of seen I<00:14:15.870> think<00:14:16.290> the<00:14:16.580> as<00:14:17.580> long<00:14:17.820> as<00:14:18.030> coming<00:14:18.510> from<00:14:18.540> the 00:14:18.740 --> 00:14:18.750 align:start position:0% I think the as long as coming from the 00:14:18.750 --> 00:14:20.300 align:start position:0% I think the as long as coming from the crypto<00:14:19.110> community<00:14:19.530> I<00:14:19.560> would<00:14:19.680> want<00:14:20.010> to<00:14:20.070> say 00:14:20.300 --> 00:14:20.310 align:start position:0% crypto community I would want to say 00:14:20.310 --> 00:14:20.930 align:start position:0% crypto community I would want to say that 00:14:20.930 --> 00:14:20.940 align:start position:0% that 00:14:20.940 --> 00:14:24.680 align:start position:0% that let's<00:14:21.690> do<00:14:21.990> I<00:14:22.380> would<00:14:23.010> want<00:14:23.190> to<00:14:23.280> believe<00:14:23.550> that<00:14:23.690> we 00:14:24.680 --> 00:14:24.690 align:start position:0% let's do I would want to believe that we 00:14:24.690 --> 00:14:28.220 align:start position:0% let's do I would want to believe that we should<00:14:24.930> make<00:14:25.290> users<00:14:25.710> think<00:14:26.510> it's<00:14:27.510> not<00:14:27.750> exactly 00:14:28.220 --> 00:14:28.230 align:start position:0% should make users think it's not exactly 00:14:28.230 --> 00:14:32.960 align:start position:0% should make users think it's not exactly how<00:14:28.710> the<00:14:29.220> product<00:14:29.640> works<00:14:29.930> and<00:14:31.190> I<00:14:32.190> think 00:14:32.960 --> 00:14:32.970 align:start position:0% how the product works and I think 00:14:32.970 --> 00:14:36.560 align:start position:0% how the product works and I think certain<00:14:34.310> features<00:14:35.310> are<00:14:35.730> in<00:14:36.120> the<00:14:36.240> final 00:14:36.560 --> 00:14:36.570 align:start position:0% certain features are in the final 00:14:36.570 --> 00:14:38.720 align:start position:0% certain features are in the final existing<00:14:37.080> financial<00:14:37.560> system<00:14:37.950> there<00:14:38.430> for<00:14:38.700> a 00:14:38.720 --> 00:14:38.730 align:start position:0% existing financial system there for a 00:14:38.730 --> 00:14:40.910 align:start position:0% existing financial system there for a reason<00:14:39.000> so<00:14:39.570> for<00:14:39.810> example<00:14:40.140> I<00:14:40.170> can't<00:14:40.380> recovery 00:14:40.910 --> 00:14:40.920 align:start position:0% reason so for example I can't recovery 00:14:40.920 --> 00:14:43.010 align:start position:0% reason so for example I can't recovery is<00:14:41.280> there<00:14:41.550> because<00:14:41.820> you<00:14:42.480> know<00:14:42.570> we<00:14:42.720> tend<00:14:42.960> to 00:14:43.010 --> 00:14:43.020 align:start position:0% is there because you know we tend to 00:14:43.020 --> 00:14:45.140 align:start position:0% is there because you know we tend to forget<00:14:43.230> our<00:14:43.440> passwords<00:14:44.160> we<00:14:44.280> tend<00:14:44.490> to<00:14:44.550> do<00:14:44.820> stuff 00:14:45.140 --> 00:14:45.150 align:start position:0% forget our passwords we tend to do stuff 00:14:45.150 --> 00:14:50.590 align:start position:0% forget our passwords we tend to do stuff that<00:14:46.160> kind<00:14:47.160> of<00:14:47.220> work<00:14:47.460> against<00:14:47.970> us<00:14:48.060> almost<00:14:48.570> so 00:14:50.590 --> 00:14:50.600 align:start position:0% that kind of work against us almost so 00:14:50.600 --> 00:14:53.420 align:start position:0% that kind of work against us almost so you<00:14:51.600> know<00:14:51.720> thinking<00:14:52.260> about<00:14:52.380> these<00:14:52.740> things<00:14:52.800> as 00:14:53.420 --> 00:14:53.430 align:start position:0% you know thinking about these things as 00:14:53.430 --> 00:14:56.780 align:start position:0% you know thinking about these things as like<00:14:53.700> features<00:14:54.390> not<00:14:54.660> necessarily<00:14:55.380> the<00:14:55.890> sort 00:14:56.780 --> 00:14:56.790 align:start position:0% like features not necessarily the sort 00:14:56.790 --> 00:14:59.690 align:start position:0% like features not necessarily the sort of<00:14:56.850> old<00:14:57.140> system<00:14:58.140> but<00:14:58.410> rather<00:14:58.800> how<00:14:59.160> can<00:14:59.340> we<00:14:59.490> help 00:14:59.690 --> 00:14:59.700 align:start position:0% of old system but rather how can we help 00:14:59.700 --> 00:15:03.320 align:start position:0% of old system but rather how can we help users<00:15:00.380> sort<00:15:01.380> of<00:15:01.500> enter<00:15:02.280> the<00:15:02.490> crypto<00:15:02.820> community 00:15:03.320 --> 00:15:03.330 align:start position:0% users sort of enter the crypto community 00:15:03.330 --> 00:15:05.420 align:start position:0% users sort of enter the crypto community through<00:15:03.690> or<00:15:04.050> crypto<00:15:04.590> technology<00:15:04.710> through 00:15:05.420 --> 00:15:05.430 align:start position:0% through or crypto technology through 00:15:05.430 --> 00:15:07.400 align:start position:0% through or crypto technology through maybe<00:15:05.970> more<00:15:06.270> evolution<00:15:07.080> rather<00:15:07.230> than 00:15:07.400 --> 00:15:07.410 align:start position:0% maybe more evolution rather than 00:15:07.410 --> 00:15:11.600 align:start position:0% maybe more evolution rather than revolution<00:15:07.850> so<00:15:08.850> we<00:15:09.090> can<00:15:09.330> in<00:15:10.370> wallet<00:15:11.370> for 00:15:11.600 --> 00:15:11.610 align:start position:0% revolution so we can in wallet for 00:15:11.610 --> 00:15:15.410 align:start position:0% revolution so we can in wallet for example<00:15:11.970> we<00:15:12.120> have<00:15:13.070> we<00:15:14.070> allow<00:15:14.310> users<00:15:14.700> to<00:15:14.730> back 00:15:15.410 --> 00:15:15.420 align:start position:0% example we have we allow users to back 00:15:15.420 --> 00:15:19.550 align:start position:0% example we have we allow users to back their<00:15:15.690> that<00:15:16.010> their<00:15:17.010> security<00:15:17.550> their<00:15:18.560> secret 00:15:19.550 --> 00:15:19.560 align:start position:0% their that their security their secret 00:15:19.560 --> 00:15:23.620 align:start position:0% their that their security their secret peace<00:15:19.800> through<00:15:21.200> their<00:15:22.200> Google<00:15:22.620> Docs<00:15:22.860> and 00:15:23.620 --> 00:15:23.630 align:start position:0% peace through their Google Docs and 00:15:23.630 --> 00:15:25.970 align:start position:0% peace through their Google Docs and there<00:15:24.630> are<00:15:24.810> there<00:15:25.170> are<00:15:25.200> solutions<00:15:25.560> that<00:15:25.770> are 00:15:25.970 --> 00:15:25.980 align:start position:0% there are there are solutions that are 00:15:25.980 --> 00:15:27.940 align:start position:0% there are there are solutions that are more<00:15:26.010> decentralized<00:15:26.610> and<00:15:27.240> solutions 00:15:27.940 --> 00:15:27.950 align:start position:0% more decentralized and solutions 00:15:27.950 --> 00:15:30.069 align:start position:0% more decentralized and solutions that<00:15:28.190> are<00:15:28.310> more<00:15:28.459> centralized<00:15:29.060> the<00:15:29.750> most 00:15:30.069 --> 00:15:30.079 align:start position:0% that are more centralized the most 00:15:30.079 --> 00:15:32.199 align:start position:0% that are more centralized the most important<00:15:30.589> element<00:15:30.980> for<00:15:31.010> us<00:15:31.190> is<00:15:31.550> like<00:15:31.790> knowing 00:15:32.199 --> 00:15:32.209 align:start position:0% important element for us is like knowing 00:15:32.209 --> 00:15:34.690 align:start position:0% important element for us is like knowing who<00:15:32.420> our<00:15:32.450> audience<00:15:32.870> are<00:15:33.560> and<00:15:33.920> like<00:15:34.339> making 00:15:34.690 --> 00:15:34.700 align:start position:0% who our audience are and like making 00:15:34.700 --> 00:15:36.540 align:start position:0% who our audience are and like making sure<00:15:34.940> that<00:15:35.149> we're<00:15:35.389> going<00:15:35.660> to<00:15:35.750> protect<00:15:36.139> them 00:15:36.540 --> 00:15:36.550 align:start position:0% sure that we're going to protect them 00:15:36.550 --> 00:15:39.990 align:start position:0% sure that we're going to protect them and<00:15:37.550> at<00:15:38.149> the<00:15:38.240> same<00:15:38.300> time<00:15:38.720> give<00:15:39.290> them<00:15:39.589> the 00:15:39.990 --> 00:15:40.000 align:start position:0% and at the same time give them the 00:15:40.000 --> 00:15:42.910 align:start position:0% and at the same time give them the opportunity<00:15:41.000> to<00:15:41.060> do<00:15:41.510> like<00:15:42.139> to<00:15:42.260> choose<00:15:42.529> to<00:15:42.800> work 00:15:42.910 --> 00:15:42.920 align:start position:0% opportunity to do like to choose to work 00:15:42.920 --> 00:15:44.970 align:start position:0% opportunity to do like to choose to work which<00:15:43.220> direction<00:15:43.579> they<00:15:43.850> want<00:15:44.060> to<00:15:44.120> go<00:15:44.269> to<00:15:44.449> I 00:15:44.970 --> 00:15:44.980 align:start position:0% which direction they want to go to I 00:15:44.980 --> 00:15:48.069 align:start position:0% which direction they want to go to I really<00:15:45.980> like<00:15:46.160> that<00:15:46.279> idea<00:15:46.430> that<00:15:46.820> evolution<00:15:47.079> if 00:15:48.069 --> 00:15:48.079 align:start position:0% really like that idea that evolution if 00:15:48.079 --> 00:15:50.829 align:start position:0% really like that idea that evolution if we<00:15:48.199> permit<00:15:48.709> legit<00:15:49.310> I<00:15:49.760> think<00:15:50.209> these<00:15:50.300> last<00:15:50.570> year 00:15:50.829 --> 00:15:50.839 align:start position:0% we permit legit I think these last year 00:15:50.839 --> 00:15:52.030 align:start position:0% we permit legit I think these last year kind<00:15:50.959> of<00:15:51.110> ice<00:15:51.230> we<00:15:51.620> already<00:15:51.829> see<00:15:52.010> that 00:15:52.030 --> 00:15:52.040 align:start position:0% kind of ice we already see that 00:15:52.040 --> 00:15:53.920 align:start position:0% kind of ice we already see that evolution<00:15:52.850> in<00:15:52.970> terms<00:15:53.089> of<00:15:53.300> last<00:15:53.510> year<00:15:53.720> it<00:15:53.779> was 00:15:53.920 --> 00:15:53.930 align:start position:0% evolution in terms of last year it was 00:15:53.930 --> 00:15:56.100 align:start position:0% evolution in terms of last year it was like<00:15:54.079> let's<00:15:54.649> put<00:15:54.860> out<00:15:54.980> all<00:15:55.130> the<00:15:55.250> really<00:15:55.490> big 00:15:56.100 --> 00:15:56.110 align:start position:0% like let's put out all the really big 00:15:56.110 --> 00:15:58.240 align:start position:0% like let's put out all the really big problems<00:15:57.110> and<00:15:57.260> the<00:15:57.320> questions<00:15:57.740> and<00:15:57.980> we<00:15:58.070> want 00:15:58.240 --> 00:15:58.250 align:start position:0% problems and the questions and we want 00:15:58.250 --> 00:16:00.430 align:start position:0% problems and the questions and we want to<00:15:58.310> solve<00:15:58.519> her<00:15:58.790> really<00:15:59.420> really<00:15:59.690> big<00:16:00.019> important 00:16:00.430 --> 00:16:00.440 align:start position:0% to solve her really really big important 00:16:00.440 --> 00:16:03.100 align:start position:0% to solve her really really big important things<00:16:00.820> around<00:16:01.820> banks<00:16:02.269> and<00:16:02.449> the<00:16:02.510> system<00:16:02.930> the 00:16:03.100 --> 00:16:03.110 align:start position:0% things around banks and the system the 00:16:03.110 --> 00:16:05.650 align:start position:0% things around banks and the system the centralization<00:16:03.500> but<00:16:04.399> the<00:16:04.730> adoption<00:16:04.970> that<00:16:05.540> we 00:16:05.650 --> 00:16:05.660 align:start position:0% centralization but the adoption that we 00:16:05.660 --> 00:16:08.139 align:start position:0% centralization but the adoption that we see<00:16:05.930> there<00:16:06.170> and<00:16:06.440> where<00:16:06.740> that<00:16:06.980> bridge<00:16:07.310> we're 00:16:08.139 --> 00:16:08.149 align:start position:0% see there and where that bridge we're 00:16:08.149 --> 00:16:10.180 align:start position:0% see there and where that bridge we're almost<00:16:08.420> there<00:16:08.870> but<00:16:08.930> we're<00:16:09.680> trying<00:16:09.980> to<00:16:10.070> design 00:16:10.180 --> 00:16:10.190 align:start position:0% almost there but we're trying to design 00:16:10.190 --> 00:16:12.129 align:start position:0% almost there but we're trying to design for<00:16:10.459> a<00:16:10.519> user<00:16:10.730> that's<00:16:10.970> users<00:16:11.720> that<00:16:11.810> are<00:16:11.930> not 00:16:12.129 --> 00:16:12.139 align:start position:0% for a user that's users that are not 00:16:12.139 --> 00:16:13.720 align:start position:0% for a user that's users that are not quite<00:16:12.470> there<00:16:12.649> yet<00:16:12.709> they're<00:16:13.130> not<00:16:13.279> quite 00:16:13.720 --> 00:16:13.730 align:start position:0% quite there yet they're not quite 00:16:13.730 --> 00:16:16.030 align:start position:0% quite there yet they're not quite knowledgeable<00:16:13.880> I<00:16:14.829> think<00:16:15.829> that's<00:16:15.980> the 00:16:16.030 --> 00:16:16.040 align:start position:0% knowledgeable I think that's the 00:16:16.040 --> 00:16:18.370 align:start position:0% knowledgeable I think that's the difficulty<00:16:16.639> of<00:16:16.670> the<00:16:17.449> moment<00:16:17.810> we<00:16:17.930> are<00:16:18.079> in<00:16:18.230> is 00:16:18.370 --> 00:16:18.380 align:start position:0% difficulty of the moment we are in is 00:16:18.380 --> 00:16:20.680 align:start position:0% difficulty of the moment we are in is that<00:16:18.500> this<00:16:18.649> kind<00:16:19.130> of<00:16:19.250> tension<00:16:19.639> because<00:16:20.209> you 00:16:20.680 --> 00:16:20.690 align:start position:0% that this kind of tension because you 00:16:20.690 --> 00:16:23.230 align:start position:0% that this kind of tension because you want<00:16:20.899> to<00:16:20.990> build<00:16:21.139> for<00:16:21.350> the<00:16:21.500> next<00:16:21.889> wave<00:16:22.130> of<00:16:22.240> users 00:16:23.230 --> 00:16:23.240 align:start position:0% want to build for the next wave of users 00:16:23.240 --> 00:16:25.030 align:start position:0% want to build for the next wave of users coming<00:16:23.540> but<00:16:24.199> we<00:16:24.320> still<00:16:24.500> want<00:16:24.709> to<00:16:24.769> be<00:16:24.860> relevant 00:16:25.030 --> 00:16:25.040 align:start position:0% coming but we still want to be relevant 00:16:25.040 --> 00:16:27.490 align:start position:0% coming but we still want to be relevant today<00:16:25.459> and<00:16:25.910> so<00:16:26.149> what<00:16:26.750> people<00:16:26.959> understand 00:16:27.490 --> 00:16:27.500 align:start position:0% today and so what people understand 00:16:27.500 --> 00:16:28.840 align:start position:0% today and so what people understand today<00:16:27.769> is<00:16:27.949> not<00:16:28.190> what<00:16:28.370> people<00:16:28.399> would 00:16:28.840 --> 00:16:28.850 align:start position:0% today is not what people would 00:16:28.850 --> 00:16:32.319 align:start position:0% today is not what people would understand<00:16:29.529> the<00:16:30.529> future<00:16:30.709> to<00:16:31.459> give<00:16:31.670> you<00:16:31.760> a<00:16:31.820> good 00:16:32.319 --> 00:16:32.329 align:start position:0% understand the future to give you a good 00:16:32.329 --> 00:16:33.699 align:start position:0% understand the future to give you a good example<00:16:32.420> about<00:16:32.779> that<00:16:33.050> I<00:16:33.079> have<00:16:33.230> a<00:16:33.290> good<00:16:33.440> friend 00:16:33.699 --> 00:16:33.709 align:start position:0% example about that I have a good friend 00:16:33.709 --> 00:16:35.199 align:start position:0% example about that I have a good friend that<00:16:33.769> I<00:16:33.920> managed<00:16:34.190> to<00:16:34.250> convince<00:16:34.490> to<00:16:34.940> use<00:16:35.060> our 00:16:35.199 --> 00:16:35.209 align:start position:0% that I managed to convince to use our 00:16:35.209 --> 00:16:36.819 align:start position:0% that I managed to convince to use our journey<00:16:35.449> it<00:16:35.570> was<00:16:35.690> really<00:16:35.959> excited<00:16:36.410> to<00:16:36.560> put<00:16:36.709> his 00:16:36.819 --> 00:16:36.829 align:start position:0% journey it was really excited to put his 00:16:36.829 --> 00:16:38.860 align:start position:0% journey it was really excited to put his money<00:16:37.010> to<00:16:37.279> come<00:16:37.459> home<00:16:37.640> and<00:16:38.300> so<00:16:38.510> he<00:16:38.600> don't<00:16:38.779> know 00:16:38.860 --> 00:16:38.870 align:start position:0% money to come home and so he don't know 00:16:38.870 --> 00:16:40.449 align:start position:0% money to come home and so he don't know the<00:16:38.899> audience<00:16:39.290> and<00:16:39.769> he<00:16:39.949> used<00:16:40.130> actually 00:16:40.449 --> 00:16:40.459 align:start position:0% the audience and he used actually 00:16:40.459 --> 00:16:42.340 align:start position:0% the audience and he used actually because<00:16:40.760> we<00:16:41.089> didn't<00:16:41.360> have<00:16:41.390> but<00:16:41.750> if<00:16:41.899> you<00:16:42.019> had<00:16:42.110> to 00:16:42.340 --> 00:16:42.350 align:start position:0% because we didn't have but if you had to 00:16:42.350 --> 00:16:44.380 align:start position:0% because we didn't have but if you had to cryptogram<00:16:43.160> at<00:16:43.279> that<00:16:43.430> point<00:16:43.670> you<00:16:43.820> use<00:16:43.850> conveys 00:16:44.380 --> 00:16:44.390 align:start position:0% cryptogram at that point you use conveys 00:16:44.390 --> 00:16:46.449 align:start position:0% cryptogram at that point you use conveys to<00:16:44.660> buy<00:16:44.779> some<00:16:45.019> dye<00:16:45.199> then<00:16:45.890> he<00:16:45.980> wants<00:16:46.190> to<00:16:46.279> send 00:16:46.449 --> 00:16:46.459 align:start position:0% to buy some dye then he wants to send 00:16:46.459 --> 00:16:49.090 align:start position:0% to buy some dye then he wants to send this<00:16:46.579> guy<00:16:46.760> to<00:16:46.790> Archer<00:16:47.269> and<00:16:48.019> then<00:16:48.260> is<00:16:48.500> his 00:16:49.090 --> 00:16:49.100 align:start position:0% this guy to Archer and then is his 00:16:49.100 --> 00:16:50.949 align:start position:0% this guy to Archer and then is his colleague<00:16:49.550> names<00:16:49.760> like<00:16:50.000> dude<00:16:50.420> I<00:16:50.570> cannot<00:16:50.750> say 00:16:50.949 --> 00:16:50.959 align:start position:0% colleague names like dude I cannot say 00:16:50.959 --> 00:16:53.110 align:start position:0% colleague names like dude I cannot say my<00:16:51.410> dad<00:16:51.620> to<00:16:51.800> Arjun<00:16:52.160> and<00:16:52.279> I<00:16:52.339> said<00:16:52.550> yes<00:16:52.760> look<00:16:53.000> at 00:16:53.110 --> 00:16:53.120 align:start position:0% my dad to Arjun and I said yes look at 00:16:53.120 --> 00:16:55.000 align:start position:0% my dad to Arjun and I said yes look at that<00:16:53.300> screen<00:16:53.510> it<00:16:53.690> says<00:16:53.720> we<00:16:53.990> can<00:16:54.140> send<00:16:54.380> here<00:16:54.500> c20 00:16:55.000 --> 00:16:55.010 align:start position:0% that screen it says we can send here c20 00:16:55.010 --> 00:16:57.550 align:start position:0% that screen it says we can send here c20 it's<00:16:55.459> like<00:16:55.640> what's<00:16:56.000> annuity<00:16:56.390> 20<00:16:56.690> so<00:16:57.199> actually 00:16:57.550 --> 00:16:57.560 align:start position:0% it's like what's annuity 20 so actually 00:16:57.560 --> 00:16:59.530 align:start position:0% it's like what's annuity 20 so actually on<00:16:57.680> country<00:16:58.250> is<00:16:58.339> it<00:16:58.459> controller<00:16:58.820> this<00:16:59.029> guy<00:16:59.240> to 00:16:59.530 --> 00:16:59.540 align:start position:0% on country is it controller this guy to 00:16:59.540 --> 00:17:01.720 align:start position:0% on country is it controller this guy to eater<00:16:59.779> so<00:17:00.230> he<00:17:00.320> could<00:17:00.470> say<00:17:00.649> eater<00:17:00.949> and<00:17:01.579> then 00:17:01.720 --> 00:17:01.730 align:start position:0% eater so he could say eater and then 00:17:01.730 --> 00:17:04.270 align:start position:0% eater so he could say eater and then arjun<00:17:02.240> converted<00:17:02.690> eater<00:17:02.990> back<00:17:03.320> to<00:17:03.470> die<00:17:03.649> by<00:17:04.220> the 00:17:04.270 --> 00:17:04.280 align:start position:0% arjun converted eater back to die by the 00:17:04.280 --> 00:17:06.100 align:start position:0% arjun converted eater back to die by the time<00:17:04.400> you<00:17:04.699> had<00:17:04.790> done<00:17:04.970> that<00:17:05.000> it<00:17:05.299> was<00:17:05.480> like<00:17:05.660> six 00:17:06.100 --> 00:17:06.110 align:start position:0% time you had done that it was like six 00:17:06.110 --> 00:17:07.539 align:start position:0% time you had done that it was like six or<00:17:06.260> seven<00:17:06.530> percent<00:17:06.679> it<00:17:06.980> was<00:17:07.100> like<00:17:07.280> your 00:17:07.539 --> 00:17:07.549 align:start position:0% or seven percent it was like your 00:17:07.549 --> 00:17:09.730 align:start position:0% or seven percent it was like your product<00:17:07.790> makes<00:17:08.089> no<00:17:08.179> sense<00:17:08.480> and<00:17:09.049> i<00:17:09.169> think<00:17:09.410> we're 00:17:09.730 --> 00:17:09.740 align:start position:0% product makes no sense and i think we're 00:17:09.740 --> 00:17:11.949 align:start position:0% product makes no sense and i think we're saying<00:17:10.010> about<00:17:10.130> under<00:17:10.699> stinger<00:17:11.030> users<00:17:11.630> i<00:17:11.720> think 00:17:11.949 --> 00:17:11.959 align:start position:0% saying about under stinger users i think 00:17:11.959 --> 00:17:14.169 align:start position:0% saying about under stinger users i think there's<00:17:12.110> also<00:17:12.260> a<00:17:12.439> lot<00:17:12.470> of<00:17:12.640> feedback<00:17:13.640> and<00:17:14.000> we 00:17:14.169 --> 00:17:14.179 align:start position:0% there's also a lot of feedback and we 00:17:14.179 --> 00:17:16.270 align:start position:0% there's also a lot of feedback and we need<00:17:14.299> to<00:17:14.419> be<00:17:14.540> able<00:17:14.809> to<00:17:14.959> listen<00:17:15.140> to<00:17:15.350> feedback<00:17:15.919> so 00:17:16.270 --> 00:17:16.280 align:start position:0% need to be able to listen to feedback so 00:17:16.280 --> 00:17:17.949 align:start position:0% need to be able to listen to feedback so for<00:17:16.459> example<00:17:16.790> for<00:17:16.939> us<00:17:17.030> customer<00:17:17.510> support<00:17:17.809> is 00:17:17.949 --> 00:17:17.959 align:start position:0% for example for us customer support is 00:17:17.959 --> 00:17:20.079 align:start position:0% for example for us customer support is very<00:17:18.110> important<00:17:18.589> because<00:17:18.709> we<00:17:19.610> do<00:17:19.730> you<00:17:19.939> the 00:17:20.079 --> 00:17:20.089 align:start position:0% very important because we do you the 00:17:20.089 --> 00:17:21.730 align:start position:0% very important because we do you the research<00:17:20.449> ramiro<00:17:20.870> users<00:17:21.290> but<00:17:21.439> actually 00:17:21.730 --> 00:17:21.740 align:start position:0% research ramiro users but actually 00:17:21.740 --> 00:17:23.409 align:start position:0% research ramiro users but actually listening<00:17:22.130> to<00:17:22.189> the<00:17:22.309> feedback<00:17:22.549> of<00:17:22.790> the<00:17:22.939> users 00:17:23.409 --> 00:17:23.419 align:start position:0% listening to the feedback of the users 00:17:23.419 --> 00:17:25.480 align:start position:0% listening to the feedback of the users is<00:17:23.600> all<00:17:23.959> you<00:17:24.049> know<00:17:24.169> the<00:17:24.350> most<00:17:24.530> because<00:17:25.250> we<00:17:25.339> make 00:17:25.480 --> 00:17:25.490 align:start position:0% is all you know the most because we make 00:17:25.490 --> 00:17:26.230 align:start position:0% is all you know the most because we make a<00:17:25.520> lot<00:17:25.640> of<00:17:25.790> ass 00:17:26.230 --> 00:17:26.240 align:start position:0% a lot of ass 00:17:26.240 --> 00:17:28.000 align:start position:0% a lot of ass when<00:17:26.539> people<00:17:26.779> understand<00:17:27.350> what<00:17:27.559> people<00:17:27.860> know 00:17:28.000 --> 00:17:28.010 align:start position:0% when people understand what people know 00:17:28.010 --> 00:17:30.070 align:start position:0% when people understand what people know that<00:17:28.610> example<00:17:28.970> prose<00:17:29.360> was<00:17:29.539> like<00:17:29.720> of<00:17:30.020> course 00:17:30.070 --> 00:17:30.080 align:start position:0% that example prose was like of course 00:17:30.080 --> 00:17:32.409 align:start position:0% that example prose was like of course nobody<00:17:30.890> knows<00:17:31.070> what's<00:17:31.250> in<00:17:31.370> here<00:17:31.429> see<00:17:31.610> tiny<00:17:31.820> so 00:17:32.409 --> 00:17:32.419 align:start position:0% nobody knows what's in here see tiny so 00:17:32.419 --> 00:17:33.820 align:start position:0% nobody knows what's in here see tiny so you<00:17:32.480> know<00:17:32.600> we<00:17:32.720> need<00:17:32.840> to<00:17:32.870> make<00:17:33.020> that<00:17:33.230> explicit<00:17:33.500> I 00:17:33.820 --> 00:17:33.830 align:start position:0% you know we need to make that explicit I 00:17:33.830 --> 00:17:35.950 align:start position:0% you know we need to make that explicit I think<00:17:34.010> it's<00:17:34.130> a<00:17:34.220> it's<00:17:34.730> a<00:17:34.970> silly<00:17:35.270> example<00:17:35.330> that 00:17:35.950 --> 00:17:35.960 align:start position:0% think it's a it's a silly example that 00:17:35.960 --> 00:17:37.659 align:start position:0% think it's a it's a silly example that thing<00:17:36.110> it<00:17:36.200> shows<00:17:36.380> that<00:17:36.620> as<00:17:36.830> you<00:17:36.950> answer<00:17:37.580> your 00:17:37.659 --> 00:17:37.669 align:start position:0% thing it shows that as you answer your 00:17:37.669 --> 00:17:39.130 align:start position:0% thing it shows that as you answer your first<00:17:37.820> question<00:17:37.909> we<00:17:38.330> are<00:17:38.450> getting<00:17:38.690> there<00:17:38.929> but 00:17:39.130 --> 00:17:39.140 align:start position:0% first question we are getting there but 00:17:39.140 --> 00:17:40.510 align:start position:0% first question we are getting there but we<00:17:39.260> are<00:17:39.380> cleaning<00:17:39.590> up<00:17:39.860> there<00:17:40.070> yes<00:17:40.279> for<00:17:40.460> the 00:17:40.510 --> 00:17:40.520 align:start position:0% we are cleaning up there yes for the 00:17:40.520 --> 00:17:43.299 align:start position:0% we are cleaning up there yes for the next<00:17:40.549> way<00:17:40.990> what<00:17:41.990> about<00:17:42.230> her<00:17:42.500> you<00:17:42.980> guys<00:17:43.159> are 00:17:43.299 --> 00:17:43.309 align:start position:0% next way what about her you guys are 00:17:43.309 --> 00:17:46.330 align:start position:0% next way what about her you guys are working<00:17:43.429> on<00:17:43.669> a<00:17:43.970> nevis<00:17:44.480> of<00:17:44.830> launched<00:17:45.830> after<00:17:45.980> as 00:17:46.330 --> 00:17:46.340 align:start position:0% working on a nevis of launched after as 00:17:46.340 --> 00:17:50.019 align:start position:0% working on a nevis of launched after as well<00:17:46.750> and<00:17:48.100> trading<00:17:49.100> the<00:17:49.220> seamless<00:17:49.580> experience 00:17:50.019 --> 00:17:50.029 align:start position:0% well and trading the seamless experience 00:17:50.029 --> 00:17:51.549 align:start position:0% well and trading the seamless experience for<00:17:50.120> the<00:17:50.360> types<00:17:50.570> of<00:17:50.720> users<00:17:50.960> you<00:17:51.110> have<00:17:51.140> which 00:17:51.549 --> 00:17:51.559 align:start position:0% for the types of users you have which 00:17:51.559 --> 00:17:53.710 align:start position:0% for the types of users you have which are<00:17:51.679> gamers<00:17:52.130> and<00:17:52.490> they're<00:17:52.730> they're<00:17:53.090> expecting 00:17:53.710 --> 00:17:53.720 align:start position:0% are gamers and they're they're expecting 00:17:53.720 --> 00:17:56.560 align:start position:0% are gamers and they're they're expecting service<00:17:54.110> or<00:17:54.320> in<00:17:54.440> type<00:17:54.679> of<00:17:54.919> flow<00:17:55.539> when<00:17:56.539> you 00:17:56.560 --> 00:17:56.570 align:start position:0% service or in type of flow when you 00:17:56.570 --> 00:17:59.340 align:start position:0% service or in type of flow when you launch<00:17:56.899> script<00:17:57.200> affinities<00:17:57.590> at<00:17:57.799> F<00:17:58.010> Waterloo 00:17:59.340 --> 00:17:59.350 align:start position:0% launch script affinities at F Waterloo 00:17:59.350 --> 00:18:03.639 align:start position:0% launch script affinities at F Waterloo we<00:18:00.350> recently<00:18:00.760> had<00:18:02.020> we<00:18:03.020> did<00:18:03.380> a<00:18:03.409> lot<00:18:03.620> of 00:18:03.639 --> 00:18:03.649 align:start position:0% we recently had we did a lot of 00:18:03.649 --> 00:18:07.210 align:start position:0% we recently had we did a lot of onboarding<00:18:04.340> form<00:18:05.149> enemas<00:18:05.830> people<00:18:06.830> came<00:18:07.039> up<00:18:07.070> to 00:18:07.210 --> 00:18:07.220 align:start position:0% onboarding form enemas people came up to 00:18:07.220 --> 00:18:09.039 align:start position:0% onboarding form enemas people came up to us<00:18:07.399> and<00:18:07.880> was<00:18:08.090> like<00:18:08.149> what<00:18:08.480> is<00:18:08.570> this<00:18:08.600> can<00:18:08.990> i 00:18:09.039 --> 00:18:09.049 align:start position:0% us and was like what is this can i 00:18:09.049 --> 00:18:12.909 align:start position:0% us and was like what is this can i download<00:18:09.230> this<00:18:09.529> what<00:18:10.309> is<00:18:10.429> gas<00:18:10.990> and<00:18:11.990> we<00:18:12.470> sat 00:18:12.909 --> 00:18:12.919 align:start position:0% download this what is gas and we sat 00:18:12.919 --> 00:18:14.950 align:start position:0% download this what is gas and we sat down<00:18:12.950> with<00:18:13.309> tons<00:18:13.669> of<00:18:13.850> people<00:18:14.029> helping<00:18:14.720> them 00:18:14.950 --> 00:18:14.960 align:start position:0% down with tons of people helping them 00:18:14.960 --> 00:18:18.250 align:start position:0% down with tons of people helping them set<00:18:15.350> it<00:18:15.470> all<00:18:15.620> up<00:18:15.649> and<00:18:16.270> a<00:18:17.270> script<00:18:17.630> achilles<00:18:17.960> grew 00:18:18.250 --> 00:18:18.260 align:start position:0% set it all up and a script achilles grew 00:18:18.260 --> 00:18:22.120 align:start position:0% set it all up and a script achilles grew really<00:18:18.559> big<00:18:18.649> we<00:18:19.220> I<00:18:19.640> think<00:18:20.059> at<00:18:20.149> one<00:18:20.179> point<00:18:21.130> drove 00:18:22.120 --> 00:18:22.130 align:start position:0% really big we I think at one point drove 00:18:22.130 --> 00:18:26.070 align:start position:0% really big we I think at one point drove nearly<00:18:22.490> 200,000<00:18:23.450> downloads<00:18:24.080> to<00:18:24.710> mandamus<00:18:25.640> and 00:18:26.070 --> 00:18:26.080 align:start position:0% nearly 200,000 downloads to mandamus and 00:18:26.080 --> 00:18:28.720 align:start position:0% nearly 200,000 downloads to mandamus and a<00:18:27.080> lot<00:18:27.350> of<00:18:27.380> these<00:18:27.559> people<00:18:27.830> would<00:18:28.130> come<00:18:28.370> to<00:18:28.580> this 00:18:28.720 --> 00:18:28.730 align:start position:0% a lot of these people would come to this 00:18:28.730 --> 00:18:31.630 align:start position:0% a lot of these people would come to this court<00:18:29.059> and<00:18:29.960> we<00:18:30.470> are<00:18:30.830> disparate<00:18:31.190> basically 00:18:31.630 --> 00:18:31.640 align:start position:0% court and we are disparate basically 00:18:31.640 --> 00:18:34.600 align:start position:0% court and we are disparate basically between<00:18:31.880> madame<00:18:32.299> a<00:18:32.419> support<00:18:32.870> for<00:18:33.830> a<00:18:33.860> lot<00:18:34.429> of 00:18:34.600 --> 00:18:34.610 align:start position:0% between madame a support for a lot of 00:18:34.610 --> 00:18:37.299 align:start position:0% between madame a support for a lot of these<00:18:34.730> players<00:18:35.480> who<00:18:35.840> wanted<00:18:36.140> to<00:18:36.200> buy<00:18:37.070> some 00:18:37.299 --> 00:18:37.309 align:start position:0% these players who wanted to buy some 00:18:37.309 --> 00:18:40.000 align:start position:0% these players who wanted to buy some kitties<00:18:37.549> and<00:18:37.760> breed<00:18:38.120> some<00:18:38.299> kitties<00:18:38.539> and<00:18:39.010> you 00:18:40.000 --> 00:18:40.010 align:start position:0% kitties and breed some kitties and you 00:18:40.010 --> 00:18:42.639 align:start position:0% kitties and breed some kitties and you could<00:18:40.159> imagine<00:18:40.250> the<00:18:41.020> hundreds<00:18:42.020> of<00:18:42.169> thousands 00:18:42.639 --> 00:18:42.649 align:start position:0% could imagine the hundreds of thousands 00:18:42.649 --> 00:18:45.360 align:start position:0% could imagine the hundreds of thousands of<00:18:42.710> questions<00:18:43.039> that<00:18:43.429> we<00:18:43.970> have<00:18:44.090> received<00:18:44.120> from 00:18:45.360 --> 00:18:45.370 align:start position:0% of questions that we have received from 00:18:45.370 --> 00:18:47.500 align:start position:0% of questions that we have received from doing<00:18:46.370> that<00:18:46.490> amount<00:18:46.730> of<00:18:46.820> support<00:18:47.120> in<00:18:47.360> our 00:18:47.500 --> 00:18:47.510 align:start position:0% doing that amount of support in our 00:18:47.510 --> 00:18:50.560 align:start position:0% doing that amount of support in our discord<00:18:48.020> and<00:18:48.230> that<00:18:49.070> helped<00:18:49.669> us<00:18:49.850> kind<00:18:50.450> of 00:18:50.560 --> 00:18:50.570 align:start position:0% discord and that helped us kind of 00:18:50.570 --> 00:18:53.769 align:start position:0% discord and that helped us kind of understand<00:18:51.289> in<00:18:52.190> a<00:18:52.309> very<00:18:52.340> full<00:18:52.820> picture<00:18:53.090> of<00:18:53.330> all 00:18:53.769 --> 00:18:53.779 align:start position:0% understand in a very full picture of all 00:18:53.779 --> 00:18:56.649 align:start position:0% understand in a very full picture of all the<00:18:53.960> issues<00:18:54.289> that<00:18:54.860> has<00:18:55.640> arrived<00:18:55.970> with<00:18:56.270> private 00:18:56.649 --> 00:18:56.659 align:start position:0% the issues that has arrived with private 00:18:56.659 --> 00:19:00.159 align:start position:0% the issues that has arrived with private keys<00:18:57.100> and<00:18:58.100> with<00:18:58.399> like<00:18:58.700> the<00:18:59.539> continual 00:19:00.159 --> 00:19:00.169 align:start position:0% keys and with like the continual 00:19:00.169 --> 00:19:02.740 align:start position:0% keys and with like the continual controls<00:19:00.620> of<00:19:00.799> gas<00:19:01.039> and<00:19:01.549> looking<00:19:01.850> at<00:19:02.000> the<00:19:02.570> gas 00:19:02.740 --> 00:19:02.750 align:start position:0% controls of gas and looking at the gas 00:19:02.750 --> 00:19:05.769 align:start position:0% controls of gas and looking at the gas station<00:19:03.440> and<00:19:03.799> making<00:19:04.340> the<00:19:04.580> right<00:19:04.779> selection 00:19:05.769 --> 00:19:05.779 align:start position:0% station and making the right selection 00:19:05.779 --> 00:19:08.470 align:start position:0% station and making the right selection and<00:19:06.200> so<00:19:07.010> dapper<00:19:07.340> wallet<00:19:07.880> we've<00:19:08.029> been<00:19:08.210> working 00:19:08.470 --> 00:19:08.480 align:start position:0% and so dapper wallet we've been working 00:19:08.480 --> 00:19:10.800 align:start position:0% and so dapper wallet we've been working on<00:19:08.630> it<00:19:08.779> for<00:19:09.020> about<00:19:09.049> nearly<00:19:09.799> nine<00:19:10.250> months 00:19:10.800 --> 00:19:10.810 align:start position:0% on it for about nearly nine months 00:19:10.810 --> 00:19:14.430 align:start position:0% on it for about nearly nine months at<00:19:11.200> the<00:19:11.350> smart<00:19:11.560> contract<00:19:11.800> wallet<00:19:12.540> and<00:19:13.540> it's 00:19:14.430 --> 00:19:14.440 align:start position:0% at the smart contract wallet and it's 00:19:14.440 --> 00:19:16.110 align:start position:0% at the smart contract wallet and it's built<00:19:14.650> from<00:19:14.860> the<00:19:15.100> ground<00:19:15.340> up<00:19:15.550> in<00:19:15.760> terms<00:19:15.940> of 00:19:16.110 --> 00:19:16.120 align:start position:0% built from the ground up in terms of 00:19:16.120 --> 00:19:19.140 align:start position:0% built from the ground up in terms of rethinking<00:19:16.690> how<00:19:16.900> key<00:19:17.260> recovery<00:19:17.740> works<00:19:18.150> and 00:19:19.140 --> 00:19:19.150 align:start position:0% rethinking how key recovery works and 00:19:19.150 --> 00:19:21.240 align:start position:0% rethinking how key recovery works and actually<00:19:19.840> the<00:19:19.930> dapper<00:19:20.140> team<00:19:20.470> the<00:19:21.010> dapper 00:19:21.240 --> 00:19:21.250 align:start position:0% actually the dapper team the dapper 00:19:21.250 --> 00:19:23.730 align:start position:0% actually the dapper team the dapper wallet<00:19:21.640> team<00:19:21.850> is<00:19:22.000> embedded<00:19:22.480> in<00:19:22.660> the<00:19:22.990> NBA<00:19:23.350> team 00:19:23.730 --> 00:19:23.740 align:start position:0% wallet team is embedded in the NBA team 00:19:23.740 --> 00:19:26.250 align:start position:0% wallet team is embedded in the NBA team now<00:19:23.980> the<00:19:24.880> NBA<00:19:25.120> team<00:19:25.420> as<00:19:25.690> you<00:19:25.810> know<00:19:25.930> we're 00:19:26.250 --> 00:19:26.260 align:start position:0% now the NBA team as you know we're 00:19:26.260 --> 00:19:31.460 align:start position:0% now the NBA team as you know we're building<00:19:26.440> a<00:19:26.910> basketball<00:19:27.910> game<00:19:28.090> for<00:19:28.860> 2020<00:19:29.910> and 00:19:31.460 --> 00:19:31.470 align:start position:0% building a basketball game for 2020 and 00:19:31.470 --> 00:19:36.150 align:start position:0% building a basketball game for 2020 and we<00:19:32.470> have<00:19:32.800> access<00:19:33.280> to<00:19:33.630> you<00:19:34.630> know<00:19:34.710> with<00:19:35.710> access 00:19:36.150 --> 00:19:36.160 align:start position:0% we have access to you know with access 00:19:36.160 --> 00:19:38.610 align:start position:0% we have access to you know with access to<00:19:36.430> a<00:19:36.910> lot<00:19:37.150> of<00:19:37.270> fans<00:19:37.630> and<00:19:37.960> getting<00:19:38.290> a<00:19:38.350> deeper 00:19:38.610 --> 00:19:38.620 align:start position:0% to a lot of fans and getting a deeper 00:19:38.620 --> 00:19:41.420 align:start position:0% to a lot of fans and getting a deeper understanding<00:19:38.650> of<00:19:39.280> are<00:19:40.000> these<00:19:40.330> fans<00:19:40.690> of<00:19:41.020> NBA 00:19:41.420 --> 00:19:41.430 align:start position:0% understanding of are these fans of NBA 00:19:41.430 --> 00:19:44.250 align:start position:0% understanding of are these fans of NBA even<00:19:42.430> thinking<00:19:42.880> about<00:19:43.000> digital<00:19:43.600> collectibles 00:19:44.250 --> 00:19:44.260 align:start position:0% even thinking about digital collectibles 00:19:44.260 --> 00:19:47.280 align:start position:0% even thinking about digital collectibles or<00:19:44.500> true<00:19:45.130> item<00:19:45.430> ownership<00:19:45.970> and<00:19:46.240> as<00:19:47.020> with 00:19:47.280 --> 00:19:47.290 align:start position:0% or true item ownership and as with 00:19:47.290 --> 00:19:49.020 align:start position:0% or true item ownership and as with anything<00:19:47.530> that<00:19:47.740> we<00:19:47.890> do<00:19:48.070> we<00:19:48.250> always<00:19:48.580> start<00:19:48.880> off 00:19:49.020 --> 00:19:49.030 align:start position:0% anything that we do we always start off 00:19:49.030 --> 00:19:52.140 align:start position:0% anything that we do we always start off of<00:19:49.270> the<00:19:49.360> users<00:19:49.660> as<00:19:49.870> Julian<00:19:50.290> said<00:19:50.590> and<00:19:51.550> we<00:19:51.910> have 00:19:52.140 --> 00:19:52.150 align:start position:0% of the users as Julian said and we have 00:19:52.150 --> 00:19:55.020 align:start position:0% of the users as Julian said and we have thousands<00:19:52.780> of<00:19:52.870> conversations<00:19:53.140> on<00:19:53.890> a<00:19:54.400> monthly 00:19:55.020 --> 00:19:55.030 align:start position:0% thousands of conversations on a monthly 00:19:55.030 --> 00:19:57.600 align:start position:0% thousands of conversations on a monthly basis<00:19:55.570> and<00:19:55.780> that<00:19:56.350> really<00:19:56.590> helps<00:19:56.950> us<00:19:57.130> as<00:19:57.580> a 00:19:57.600 --> 00:19:57.610 align:start position:0% basis and that really helps us as a 00:19:57.610 --> 00:20:00.780 align:start position:0% basis and that really helps us as a company<00:19:58.120> get<00:19:58.720> built<00:19:59.470> this<00:19:59.680> obsession<00:20:00.130> of<00:20:00.520> like 00:20:00.780 --> 00:20:00.790 align:start position:0% company get built this obsession of like 00:20:00.790 --> 00:20:03.090 align:start position:0% company get built this obsession of like hey<00:20:01.390> this<00:20:01.720> is<00:20:01.780> not<00:20:02.080> very<00:20:02.230> good<00:20:02.530> maybe<00:20:02.860> we 00:20:03.090 --> 00:20:03.100 align:start position:0% hey this is not very good maybe we 00:20:03.100 --> 00:20:05.010 align:start position:0% hey this is not very good maybe we should<00:20:03.280> change<00:20:03.640> this<00:20:03.940> right<00:20:04.300> a<00:20:04.510> prime<00:20:04.990> example 00:20:05.010 --> 00:20:05.020 align:start position:0% should change this right a prime example 00:20:05.020 --> 00:20:08.550 align:start position:0% should change this right a prime example was<00:20:06.330> we<00:20:07.330> called<00:20:07.510> some<00:20:07.750> more<00:20:07.840> contract<00:20:08.230> wallets 00:20:08.550 --> 00:20:08.560 align:start position:0% was we called some more contract wallets 00:20:08.560 --> 00:20:10.560 align:start position:0% was we called some more contract wallets now<00:20:08.710> or<00:20:08.890> smart<00:20:09.190> wallets<00:20:09.610> it's<00:20:09.820> it's<00:20:10.090> a<00:20:10.210> simpler 00:20:10.560 --> 00:20:10.570 align:start position:0% now or smart wallets it's it's a simpler 00:20:10.570 --> 00:20:12.360 align:start position:0% now or smart wallets it's it's a simpler turn<00:20:10.780> back<00:20:11.080> I<00:20:11.500> don't<00:20:11.620> know<00:20:11.740> six<00:20:12.040> months<00:20:12.130> ago 00:20:12.360 --> 00:20:12.370 align:start position:0% turn back I don't know six months ago 00:20:12.370 --> 00:20:14.310 align:start position:0% turn back I don't know six months ago everyone's<00:20:13.060> saying<00:20:13.270> multi<00:20:13.630> signature<00:20:14.140> or 00:20:14.310 --> 00:20:14.320 align:start position:0% everyone's saying multi signature or 00:20:14.320 --> 00:20:16.650 align:start position:0% everyone's saying multi signature or multi<00:20:14.650> sick<00:20:14.890> and<00:20:15.190> when<00:20:15.850> we<00:20:15.940> did<00:20:16.090> user<00:20:16.270> research 00:20:16.650 --> 00:20:16.660 align:start position:0% multi sick and when we did user research 00:20:16.660 --> 00:20:19.850 align:start position:0% multi sick and when we did user research papers<00:20:17.020> like<00:20:17.290> what<00:20:17.530> is<00:20:17.620> multi-state 00:20:19.850 --> 00:20:19.860 align:start position:0% papers like what is multi-state 00:20:19.860 --> 00:20:22.260 align:start position:0% papers like what is multi-state multi-sig<00:20:20.860> wallet<00:20:21.280> and<00:20:21.370> what<00:20:21.520> is<00:20:21.640> a<00:20:21.700> madam<00:20:22.000> ask 00:20:22.260 --> 00:20:22.270 align:start position:0% multi-sig wallet and what is a madam ask 00:20:22.270 --> 00:20:25.080 align:start position:0% multi-sig wallet and what is a madam ask and<00:20:22.600> we<00:20:23.530> even<00:20:24.010> drilled<00:20:24.460> down<00:20:24.640> to<00:20:24.700> each 00:20:25.080 --> 00:20:25.090 align:start position:0% and we even drilled down to each 00:20:25.090 --> 00:20:27.720 align:start position:0% and we even drilled down to each individual<00:20:25.750> word<00:20:25.960> that<00:20:26.800> we<00:20:27.010> use<00:20:27.040> when<00:20:27.640> we 00:20:27.720 --> 00:20:27.730 align:start position:0% individual word that we use when we 00:20:27.730 --> 00:20:31.650 align:start position:0% individual word that we use when we invite<00:20:28.150> people<00:20:28.180> into<00:20:28.750> our<00:20:28.780> offices<00:20:29.620> and<00:20:30.660> we 00:20:31.650 --> 00:20:31.660 align:start position:0% invite people into our offices and we 00:20:31.660 --> 00:20:34.380 align:start position:0% invite people into our offices and we just<00:20:32.170> get<00:20:32.350> really<00:20:32.860> blank<00:20:33.250> faces<00:20:33.640> all<00:20:34.060> the<00:20:34.120> time 00:20:34.380 --> 00:20:34.390 align:start position:0% just get really blank faces all the time 00:20:34.390 --> 00:20:35.730 align:start position:0% just get really blank faces all the time like<00:20:34.810> oh<00:20:34.960> okay<00:20:35.290> they<00:20:35.440> don't<00:20:35.530> really 00:20:35.730 --> 00:20:35.740 align:start position:0% like oh okay they don't really 00:20:35.740 --> 00:20:38.250 align:start position:0% like oh okay they don't really understand<00:20:36.220> this<00:20:36.310> word<00:20:36.870> and<00:20:37.870> that<00:20:38.080> really 00:20:38.250 --> 00:20:38.260 align:start position:0% understand this word and that really 00:20:38.260 --> 00:20:40.800 align:start position:0% understand this word and that really helps<00:20:38.590> us<00:20:38.740> like<00:20:39.520> kind<00:20:39.730> of<00:20:39.820> sit<00:20:40.120> in<00:20:40.150> their<00:20:40.480> shoes 00:20:40.800 --> 00:20:40.810 align:start position:0% helps us like kind of sit in their shoes 00:20:40.810 --> 00:20:43.410 align:start position:0% helps us like kind of sit in their shoes and<00:20:41.200> design<00:20:42.040> something<00:20:42.370> from<00:20:43.270> their 00:20:43.410 --> 00:20:43.420 align:start position:0% and design something from their 00:20:43.420 --> 00:20:46.050 align:start position:0% and design something from their perspective<00:20:44.020> and<00:20:44.200> so<00:20:44.410> with<00:20:45.010> Doppler<00:20:45.520> one<00:20:45.910> of 00:20:46.050 --> 00:20:46.060 align:start position:0% perspective and so with Doppler one of 00:20:46.060 --> 00:20:49.430 align:start position:0% perspective and so with Doppler one of the<00:20:46.150> things<00:20:46.360> that<00:20:46.540> we<00:20:47.160> built<00:20:48.160> was<00:20:48.520> the 00:20:49.430 --> 00:20:49.440 align:start position:0% the things that we built was the 00:20:49.440 --> 00:20:52.830 align:start position:0% the things that we built was the subsidizing<00:20:50.440> gaps<00:20:50.650> for<00:20:50.950> the<00:20:51.040> users<00:20:51.310> so<00:20:51.670> for<00:20:52.390> if 00:20:52.830 --> 00:20:52.840 align:start position:0% subsidizing gaps for the users so for if 00:20:52.840 --> 00:20:54.270 align:start position:0% subsidizing gaps for the users so for if you<00:20:52.990> play<00:20:53.170> cryptic<00:20:53.470> kitties<00:20:53.710> or<00:20:53.890> any<00:20:54.040> of<00:20:54.190> the 00:20:54.270 --> 00:20:54.280 align:start position:0% you play cryptic kitties or any of the 00:20:54.280 --> 00:20:56.040 align:start position:0% you play cryptic kitties or any of the dapple<00:20:54.610> apps<00:20:54.760> games<00:20:55.090> or<00:20:55.360> the<00:20:55.630> devil<00:20:55.930> a 00:20:56.040 --> 00:20:56.050 align:start position:0% dapple apps games or the devil a 00:20:56.050 --> 00:20:59.220 align:start position:0% dapple apps games or the devil a partnership<00:20:56.530> partners<00:20:57.480> the<00:20:58.480> people<00:20:58.840> that 00:20:59.220 --> 00:20:59.230 align:start position:0% partnership partners the people that 00:20:59.230 --> 00:21:00.010 align:start position:0% partnership partners the people that your<00:20:59.410> players 00:21:00.010 --> 00:21:00.020 align:start position:0% your players 00:21:00.020 --> 00:21:02.470 align:start position:0% your players have<00:21:00.170> to<00:21:00.290> worry<00:21:00.530> about<00:21:00.890> paying<00:21:01.250> coughs<00:21:01.550> we've 00:21:02.470 --> 00:21:02.480 align:start position:0% have to worry about paying coughs we've 00:21:02.480 --> 00:21:04.180 align:start position:0% have to worry about paying coughs we've completely<00:21:03.140> eliminated<00:21:03.620> that<00:21:03.800> and<00:21:04.040> we 00:21:04.180 --> 00:21:04.190 align:start position:0% completely eliminated that and we 00:21:04.190 --> 00:21:05.860 align:start position:0% completely eliminated that and we actually<00:21:04.220> even<00:21:04.820> change<00:21:05.060> the<00:21:05.240> word<00:21:05.360> gas<00:21:05.600> to 00:21:05.860 --> 00:21:05.870 align:start position:0% actually even change the word gas to 00:21:05.870 --> 00:21:07.780 align:start position:0% actually even change the word gas to network<00:21:06.170> fee<00:21:06.410> because<00:21:06.650> through<00:21:07.370> research 00:21:07.780 --> 00:21:07.790 align:start position:0% network fee because through research 00:21:07.790 --> 00:21:09.760 align:start position:0% network fee because through research people<00:21:08.360> just<00:21:08.660> like<00:21:08.810> it<00:21:08.990> very<00:21:09.230> confused<00:21:09.680> about 00:21:09.760 --> 00:21:09.770 align:start position:0% people just like it very confused about 00:21:09.770 --> 00:21:11.680 align:start position:0% people just like it very confused about like<00:21:10.220> why<00:21:10.370> am<00:21:10.460> I<00:21:10.550> putting<00:21:10.760> gas<00:21:10.970> in<00:21:11.000> my<00:21:11.420> wallet 00:21:11.680 --> 00:21:11.690 align:start position:0% like why am I putting gas in my wallet 00:21:11.690 --> 00:21:15.520 align:start position:0% like why am I putting gas in my wallet it<00:21:12.680> makes<00:21:12.920> no<00:21:13.100> sense<00:21:13.160> so<00:21:14.030> yeah<00:21:14.930> that's<00:21:15.260> kind<00:21:15.500> of 00:21:15.520 --> 00:21:15.530 align:start position:0% it makes no sense so yeah that's kind of 00:21:15.530 --> 00:21:17.170 align:start position:0% it makes no sense so yeah that's kind of all<00:21:15.680> the<00:21:15.800> reference<00:21:16.160> points<00:21:16.520> that<00:21:16.640> we<00:21:16.790> have<00:21:16.970> as 00:21:17.170 --> 00:21:17.180 align:start position:0% all the reference points that we have as 00:21:17.180 --> 00:21:19.360 align:start position:0% all the reference points that we have as a<00:21:17.210> company<00:21:17.480> and<00:21:17.870> so<00:21:18.410> how<00:21:18.590> we<00:21:18.650> start<00:21:19.100> the 00:21:19.360 --> 00:21:19.370 align:start position:0% a company and so how we start the 00:21:19.370 --> 00:21:21.250 align:start position:0% a company and so how we start the process<00:21:19.820> of<00:21:19.970> designing<00:21:20.510> something<00:21:20.900> that 00:21:21.250 --> 00:21:21.260 align:start position:0% process of designing something that 00:21:21.260 --> 00:21:27.100 align:start position:0% process of designing something that people<00:21:22.040> could<00:21:22.220> actually<00:21:22.250> use<00:21:25.630> the<00:21:26.630> one<00:21:26.840> thing 00:21:27.100 --> 00:21:27.110 align:start position:0% people could actually use the one thing 00:21:27.110 --> 00:21:28.840 align:start position:0% people could actually use the one thing that<00:21:27.260> I<00:21:27.290> want<00:21:27.560> to<00:21:27.620> say<00:21:27.770> is<00:21:28.010> that<00:21:28.190> design<00:21:28.550> is<00:21:28.700> not 00:21:28.840 --> 00:21:28.850 align:start position:0% that I want to say is that design is not 00:21:28.850 --> 00:21:32.530 align:start position:0% that I want to say is that design is not about<00:21:29.030> design<00:21:29.390> it's<00:21:30.320> a<00:21:30.880> building<00:21:31.880> product 00:21:32.530 --> 00:21:32.540 align:start position:0% about design it's a building product 00:21:32.540 --> 00:21:35.440 align:start position:0% about design it's a building product it's<00:21:33.080> sort<00:21:33.470> of<00:21:33.560> like<00:21:33.650> this<00:21:33.920> this<00:21:34.310> whole<00:21:34.640> whole 00:21:35.440 --> 00:21:35.450 align:start position:0% it's sort of like this this whole whole 00:21:35.450 --> 00:21:38.320 align:start position:0% it's sort of like this this whole whole that<00:21:36.040> contains<00:21:37.040> of<00:21:37.280> like<00:21:37.430> three<00:21:37.820> parts 00:21:38.320 --> 00:21:38.330 align:start position:0% that contains of like three parts 00:21:38.330 --> 00:21:41.410 align:start position:0% that contains of like three parts business<00:21:39.050> technology<00:21:39.980> and<00:21:40.280> design<00:21:40.520> and<00:21:40.970> when 00:21:41.410 --> 00:21:41.420 align:start position:0% business technology and design and when 00:21:41.420 --> 00:21:43.420 align:start position:0% business technology and design and when you<00:21:41.510> take<00:21:41.690> away<00:21:41.870> one<00:21:42.260> of<00:21:42.290> it<00:21:42.560> your<00:21:43.100> product 00:21:43.420 --> 00:21:43.430 align:start position:0% you take away one of it your product 00:21:43.430 --> 00:21:47.140 align:start position:0% you take away one of it your product will<00:21:43.550> not<00:21:43.700> be<00:21:44.350> you're<00:21:45.350> basically<00:21:45.970> going<00:21:46.970> in 00:21:47.140 --> 00:21:47.150 align:start position:0% will not be you're basically going in 00:21:47.150 --> 00:21:48.610 align:start position:0% will not be you're basically going in the<00:21:47.270> wrong<00:21:47.390> direction<00:21:47.450> your<00:21:48.020> problem<00:21:48.410> there's 00:21:48.610 --> 00:21:48.620 align:start position:0% the wrong direction your problem there's 00:21:48.620 --> 00:21:50.020 align:start position:0% the wrong direction your problem there's a<00:21:48.710> higher<00:21:48.950> chance<00:21:49.100> that<00:21:49.520> you're<00:21:49.670> going<00:21:49.880> in<00:21:49.970> the 00:21:50.020 --> 00:21:50.030 align:start position:0% a higher chance that you're going in the 00:21:50.030 --> 00:21:52.210 align:start position:0% a higher chance that you're going in the wrong<00:21:50.150> direction<00:21:50.210> and<00:21:50.900> so<00:21:51.410> what<00:21:51.590> I<00:21:51.620> really 00:21:52.210 --> 00:21:52.220 align:start position:0% wrong direction and so what I really 00:21:52.220 --> 00:21:55.000 align:start position:0% wrong direction and so what I really like<00:21:52.580> about<00:21:52.880> what<00:21:53.450> we<00:21:53.690> do<00:21:54.050> at<00:21:54.260> coin<00:21:54.500> race<00:21:54.740> is 00:21:55.000 --> 00:21:55.010 align:start position:0% like about what we do at coin race is 00:21:55.010 --> 00:21:59.770 align:start position:0% like about what we do at coin race is that<00:21:55.280> the<00:21:56.210> these<00:21:56.720> three<00:21:57.140> functions<00:21:58.780> gather 00:21:59.770 --> 00:21:59.780 align:start position:0% that the these three functions gather 00:21:59.780 --> 00:22:02.530 align:start position:0% that the these three functions gather together<00:22:00.740> very<00:22:01.370> early<00:22:01.640> on<00:22:01.670> in<00:22:01.970> the<00:22:02.060> before 00:22:02.530 --> 00:22:02.540 align:start position:0% together very early on in the before 00:22:02.540 --> 00:22:04.720 align:start position:0% together very early on in the before every<00:22:02.930> future<00:22:03.380> every<00:22:03.830> product<00:22:04.160> that<00:22:04.250> we<00:22:04.340> start 00:22:04.720 --> 00:22:04.730 align:start position:0% every future every product that we start 00:22:04.730 --> 00:22:08.170 align:start position:0% every future every product that we start and<00:22:05.060> we<00:22:05.600> actually<00:22:05.810> go<00:22:06.230> through<00:22:06.530> the<00:22:07.340> market 00:22:08.170 --> 00:22:08.180 align:start position:0% and we actually go through the market 00:22:08.180 --> 00:22:11.350 align:start position:0% and we actually go through the market fit<00:22:08.420> the<00:22:08.600> technology<00:22:09.230> and<00:22:09.590> what<00:22:10.490> do<00:22:10.730> our<00:22:10.790> users 00:22:11.350 --> 00:22:11.360 align:start position:0% fit the technology and what do our users 00:22:11.360 --> 00:22:14.800 align:start position:0% fit the technology and what do our users want<00:22:11.830> sort<00:22:12.830> of<00:22:12.950> trying<00:22:13.250> to<00:22:13.340> balance<00:22:14.120> the<00:22:14.660> new 00:22:14.800 --> 00:22:14.810 align:start position:0% want sort of trying to balance the new 00:22:14.810 --> 00:22:18.940 align:start position:0% want sort of trying to balance the new products<00:22:15.790> having<00:22:16.790> that<00:22:17.060> in<00:22:17.240> mind<00:22:17.450> and<00:22:17.950> again 00:22:18.940 --> 00:22:18.950 align:start position:0% products having that in mind and again 00:22:18.950 --> 00:22:21.610 align:start position:0% products having that in mind and again design<00:22:19.340> is<00:22:19.460> not<00:22:19.670> necessarily<00:22:20.480> about<00:22:21.020> you<00:22:21.500> know 00:22:21.610 --> 00:22:21.620 align:start position:0% design is not necessarily about you know 00:22:21.620 --> 00:22:23.950 align:start position:0% design is not necessarily about you know pixels<00:22:22.190> that<00:22:22.280> you<00:22:22.400> do<00:22:22.640> it's<00:22:23.000> it's<00:22:23.600> the<00:22:23.780> user 00:22:23.950 --> 00:22:23.960 align:start position:0% pixels that you do it's it's the user 00:22:23.960 --> 00:22:29.860 align:start position:0% pixels that you do it's it's the user experience<00:22:24.410> that<00:22:24.890> your<00:22:25.100> users<00:22:25.960> well<00:22:26.960> I<00:22:28.870> want 00:22:29.860 --> 00:22:29.870 align:start position:0% experience that your users well I want 00:22:29.870 --> 00:22:32.200 align:start position:0% experience that your users well I want to<00:22:29.930> say<00:22:30.050> experience<00:22:30.530> but<00:22:30.740> yeah<00:22:31.190> but<00:22:31.490> we'll<00:22:32.030> go 00:22:32.200 --> 00:22:32.210 align:start position:0% to say experience but yeah but we'll go 00:22:32.210 --> 00:22:33.850 align:start position:0% to say experience but yeah but we'll go through<00:22:32.240> when<00:22:32.960> interacting<00:22:33.290> with<00:22:33.710> your 00:22:33.850 --> 00:22:33.860 align:start position:0% through when interacting with your 00:22:33.860 --> 00:22:36.220 align:start position:0% through when interacting with your product 00:22:36.220 --> 00:22:36.230 align:start position:0% product 00:22:36.230 --> 00:22:37.720 align:start position:0% product I<00:22:36.260> think<00:22:36.440> we'll<00:22:36.620> see<00:22:36.799> a<00:22:36.830> lot<00:22:37.100> of<00:22:37.340> that<00:22:37.490> but<00:22:37.669> I 00:22:37.720 --> 00:22:37.730 align:start position:0% I think we'll see a lot of that but I 00:22:37.730 --> 00:22:39.190 align:start position:0% I think we'll see a lot of that but I think<00:22:37.910> going<00:22:38.090> through<00:22:38.240> the<00:22:38.480> judging<00:22:38.870> as<00:22:38.990> well 00:22:39.190 --> 00:22:39.200 align:start position:0% think going through the judging as well 00:22:39.200 --> 00:22:40.600 align:start position:0% think going through the judging as well it's<00:22:39.440> like<00:22:39.620> there's<00:22:39.860> so<00:22:40.100> many<00:22:40.280> amazing 00:22:40.600 --> 00:22:40.610 align:start position:0% it's like there's so many amazing 00:22:40.610 --> 00:22:43.930 align:start position:0% it's like there's so many amazing beautiful<00:22:41.120> products<00:22:41.870> and<00:22:42.860> the<00:22:43.460> judges<00:22:43.790> are 00:22:43.930 --> 00:22:43.940 align:start position:0% beautiful products and the judges are 00:22:43.940 --> 00:22:46.120 align:start position:0% beautiful products and the judges are really<00:22:44.240> good<00:22:44.540> about<00:22:44.780> what<00:22:45.410> is<00:22:45.530> actually 00:22:46.120 --> 00:22:46.130 align:start position:0% really good about what is actually 00:22:46.130 --> 00:22:48.460 align:start position:0% really good about what is actually useful<00:22:46.340> what<00:22:46.700> is<00:22:46.850> the<00:22:47.179> problem<00:22:47.720> is<00:22:48.200> there<00:22:48.440> a 00:22:48.460 --> 00:22:48.470 align:start position:0% useful what is the problem is there a 00:22:48.470 --> 00:22:49.380 align:start position:0% useful what is the problem is there a problem 00:22:49.380 --> 00:22:49.390 align:start position:0% problem 00:22:49.390 --> 00:22:52.570 align:start position:0% problem the<00:22:50.390> product<00:22:50.870> is<00:22:50.990> solving<00:22:51.470> and<00:22:51.740> if<00:22:52.250> so<00:22:52.400> are 00:22:52.570 --> 00:22:52.580 align:start position:0% the product is solving and if so are 00:22:52.580 --> 00:22:54.789 align:start position:0% the product is solving and if so are they<00:22:52.730> clearly<00:22:53.030> figuring<00:22:53.960> out<00:22:54.110> the<00:22:54.410> depths<00:22:54.740> of 00:22:54.789 --> 00:22:54.799 align:start position:0% they clearly figuring out the depths of 00:22:54.799 --> 00:22:55.480 align:start position:0% they clearly figuring out the depths of that<00:22:55.010> problem 00:22:55.480 --> 00:22:55.490 align:start position:0% that problem 00:22:55.490 --> 00:22:57.789 align:start position:0% that problem I<00:22:55.580> think<00:22:55.760> Arjun<00:22:56.090> for<00:22:56.210> you<00:22:56.270> guys<00:22:56.679> started<00:22:57.679> with 00:22:57.789 --> 00:22:57.799 align:start position:0% I think Arjun for you guys started with 00:22:57.799 --> 00:23:00.789 align:start position:0% I think Arjun for you guys started with that<00:22:57.919> problem<00:22:58.460> right<00:22:58.640> and<00:22:59.500> you<00:23:00.500> want<00:23:00.559> to<00:23:00.679> touch 00:23:00.789 --> 00:23:00.799 align:start position:0% that problem right and you want to touch 00:23:00.799 --> 00:23:03.880 align:start position:0% that problem right and you want to touch upon<00:23:00.919> that<00:23:01.630> whatever<00:23:02.630> you<00:23:02.780> did<00:23:03.530> you<00:23:03.620> want<00:23:03.770> to 00:23:03.880 --> 00:23:03.890 align:start position:0% upon that whatever you did you want to 00:23:03.890 --> 00:23:10.750 align:start position:0% upon that whatever you did you want to say<00:23:07.929> we<00:23:08.929> kind<00:23:09.770> of<00:23:09.890> be<00:23:10.130> starting<00:23:10.610> with<00:23:10.700> a 00:23:10.750 --> 00:23:10.760 align:start position:0% say we kind of be starting with a 00:23:10.760 --> 00:23:13.150 align:start position:0% say we kind of be starting with a problem<00:23:11.270> part<00:23:12.080> of<00:23:12.140> it<00:23:12.320> you<00:23:12.740> guys<00:23:12.860> kind<00:23:13.040> of 00:23:13.150 --> 00:23:13.160 align:start position:0% problem part of it you guys kind of 00:23:13.160 --> 00:23:14.470 align:start position:0% problem part of it you guys kind of formulate<00:23:13.580> that<00:23:13.700> you<00:23:13.820> touched<00:23:14.059> on<00:23:14.240> it<00:23:14.299> earlier 00:23:14.470 --> 00:23:14.480 align:start position:0% formulate that you touched on it earlier 00:23:14.480 --> 00:23:18.669 align:start position:0% formulate that you touched on it earlier or<00:23:15.040> you're<00:23:16.040> from<00:23:16.130> the<00:23:16.280> top<00:23:16.490> for<00:23:17.450> you<00:23:17.540> guys<00:23:17.750> how 00:23:18.669 --> 00:23:18.679 align:start position:0% or you're from the top for you guys how 00:23:18.679 --> 00:23:19.720 align:start position:0% or you're from the top for you guys how are<00:23:18.710> you 00:23:19.720 --> 00:23:19.730 align:start position:0% are you 00:23:19.730 --> 00:23:22.210 align:start position:0% are you does<00:23:20.270> that<00:23:20.360> problem<00:23:20.900> also<00:23:21.200> evolve<00:23:21.620> as<00:23:21.890> people 00:23:22.210 --> 00:23:22.220 align:start position:0% does that problem also evolve as people 00:23:22.220 --> 00:23:23.740 align:start position:0% does that problem also evolve as people are<00:23:22.309> getting<00:23:22.610> more<00:23:22.730> knowledgeable<00:23:23.360> about<00:23:23.450> the 00:23:23.740 --> 00:23:23.750 align:start position:0% are getting more knowledgeable about the 00:23:23.750 --> 00:23:25.870 align:start position:0% are getting more knowledgeable about the space<00:23:24.020> or<00:23:24.410> do<00:23:24.830> you<00:23:24.950> see<00:23:25.160> that<00:23:25.340> as<00:23:25.520> kind<00:23:25.669> of<00:23:25.760> the 00:23:25.870 --> 00:23:25.880 align:start position:0% space or do you see that as kind of the 00:23:25.880 --> 00:23:30.580 align:start position:0% space or do you see that as kind of the core<00:23:25.910> problem<00:23:26.510> I<00:23:26.780> think<00:23:29.200> what<00:23:30.200> we<00:23:30.320> think<00:23:30.530> is 00:23:30.580 --> 00:23:30.590 align:start position:0% core problem I think what we think is 00:23:30.590 --> 00:23:32.530 align:start position:0% core problem I think what we think is that<00:23:30.620> you<00:23:30.860> need<00:23:30.980> to<00:23:31.100> be<00:23:31.250> a<00:23:31.280> product<00:23:31.970> for<00:23:32.240> users 00:23:32.530 --> 00:23:32.540 align:start position:0% that you need to be a product for users 00:23:32.540 --> 00:23:35.350 align:start position:0% that you need to be a product for users and<00:23:33.169> it<00:23:33.320> needs<00:23:33.470> to<00:23:33.620> solve<00:23:33.860> a<00:23:34.429> problem<00:23:34.940> for<00:23:35.270> the 00:23:35.350 --> 00:23:35.360 align:start position:0% and it needs to solve a problem for the 00:23:35.360 --> 00:23:37.630 align:start position:0% and it needs to solve a problem for the users<00:23:35.690> so<00:23:35.900> I<00:23:35.960> think<00:23:36.049> also<00:23:36.799> in<00:23:36.890> a<00:23:37.130> in<00:23:37.340> the<00:23:37.429> space 00:23:37.630 --> 00:23:37.640 align:start position:0% users so I think also in a in the space 00:23:37.640 --> 00:23:39.250 align:start position:0% users so I think also in a in the space around<00:23:37.850> often<00:23:38.270> excited<00:23:38.900> about<00:23:39.080> the 00:23:39.250 --> 00:23:39.260 align:start position:0% around often excited about the 00:23:39.260 --> 00:23:41.860 align:start position:0% around often excited about the technology<00:23:39.410> but<00:23:40.070> I<00:23:40.160> think<00:23:40.610> a<00:23:40.880> lot<00:23:41.330> of<00:23:41.390> people 00:23:41.860 --> 00:23:41.870 align:start position:0% technology but I think a lot of people 00:23:41.870 --> 00:23:43.690 align:start position:0% technology but I think a lot of people outside<00:23:42.320> of<00:23:42.380> bubble<00:23:42.770> do<00:23:42.919> not<00:23:43.070> care<00:23:43.309> too<00:23:43.669> much 00:23:43.690 --> 00:23:43.700 align:start position:0% outside of bubble do not care too much 00:23:43.700 --> 00:23:45.490 align:start position:0% outside of bubble do not care too much about<00:23:43.880> the<00:23:44.179> centralization<00:23:44.600> they<00:23:45.080> will<00:23:45.320> not 00:23:45.490 --> 00:23:45.500 align:start position:0% about the centralization they will not 00:23:45.500 --> 00:23:47.140 align:start position:0% about the centralization they will not care<00:23:45.710> about<00:23:45.799> this<00:23:46.100> these<00:23:46.370> principles<00:23:46.940> so<00:23:47.059> we 00:23:47.140 --> 00:23:47.150 align:start position:0% care about this these principles so we 00:23:47.150 --> 00:23:49.600 align:start position:0% care about this these principles so we need<00:23:47.270> to<00:23:47.360> be<00:23:47.480> able<00:23:47.660> to<00:23:47.809> find<00:23:48.260> a<00:23:48.559> problem<00:23:49.340> that 00:23:49.600 --> 00:23:49.610 align:start position:0% need to be able to find a problem that 00:23:49.610 --> 00:23:51.340 align:start position:0% need to be able to find a problem that we<00:23:49.760> solved<00:23:50.090> for<00:23:50.120> users<00:23:50.540> I<00:23:50.630> think<00:23:50.840> people<00:23:51.140> will 00:23:51.340 --> 00:23:51.350 align:start position:0% we solved for users I think people will 00:23:51.350 --> 00:23:53.020 align:start position:0% we solved for users I think people will come<00:23:51.559> to<00:23:51.770> the<00:23:51.860> blockchain<00:23:52.100> if<00:23:52.490> it<00:23:52.640> solves<00:23:52.940> a 00:23:53.020 --> 00:23:53.030 align:start position:0% come to the blockchain if it solves a 00:23:53.030 --> 00:23:55.060 align:start position:0% come to the blockchain if it solves a problem<00:23:53.210> that<00:23:54.049> cannot<00:23:54.470> be<00:23:54.530> solved<00:23:54.919> by 00:23:55.060 --> 00:23:55.070 align:start position:0% problem that cannot be solved by 00:23:55.070 --> 00:23:56.830 align:start position:0% problem that cannot be solved by technology<00:23:55.970> and<00:23:56.090> I<00:23:56.120> think<00:23:56.150> it<00:23:56.390> needs<00:23:56.419> to<00:23:56.600> solve 00:23:56.830 --> 00:23:56.840 align:start position:0% technology and I think it needs to solve 00:23:56.840 --> 00:23:59.049 align:start position:0% technology and I think it needs to solve it<00:23:57.020> by<00:23:57.200> 10x<00:23:57.650> factor<00:23:58.040> at<00:23:58.160> least<00:23:58.400> for<00:23:58.610> people<00:23:58.910> to 00:23:59.049 --> 00:23:59.059 align:start position:0% it by 10x factor at least for people to 00:23:59.059 --> 00:24:01.390 align:start position:0% it by 10x factor at least for people to actually<00:23:59.179> actually<00:24:00.020> work<00:24:00.350> that<00:24:00.500> switch<00:24:00.770> so 00:24:01.390 --> 00:24:01.400 align:start position:0% actually actually work that switch so 00:24:01.400 --> 00:24:03.460 align:start position:0% actually actually work that switch so clearly<00:24:01.700> for<00:24:01.940> the<00:24:02.030> moment<00:24:02.390> being<00:24:03.020> a<00:24:03.169> wallet 00:24:03.460 --> 00:24:03.470 align:start position:0% clearly for the moment being a wallet 00:24:03.470 --> 00:24:05.470 align:start position:0% clearly for the moment being a wallet you<00:24:03.679> are<00:24:03.710> solving<00:24:04.040> a<00:24:04.340> problem<00:24:04.610> for<00:24:05.330> the 00:24:05.470 --> 00:24:05.480 align:start position:0% you are solving a problem for the 00:24:05.480 --> 00:24:07.740 align:start position:0% you are solving a problem for the current<00:24:05.870> ecosystem<00:24:06.530> because<00:24:06.860> most<00:24:07.130> people 00:24:07.740 --> 00:24:07.750 align:start position:0% current ecosystem because most people 00:24:07.750 --> 00:24:10.330 align:start position:0% current ecosystem because most people don't<00:24:08.750> know<00:24:08.929> that<00:24:08.960> but<00:24:09.620> what<00:24:09.830> we<00:24:09.950> believe<00:24:09.980> is 00:24:10.330 --> 00:24:10.340 align:start position:0% don't know that but what we believe is 00:24:10.340 --> 00:24:11.799 align:start position:0% don't know that but what we believe is that<00:24:10.370> the<00:24:10.760> blockchain<00:24:10.970> with<00:24:11.299> some<00:24:11.510> people 00:24:11.799 --> 00:24:11.809 align:start position:0% that the blockchain with some people 00:24:11.809 --> 00:24:14.260 align:start position:0% that the blockchain with some people will<00:24:12.320> start<00:24:12.530> problem<00:24:12.830> for<00:24:13.100> all<00:24:13.730> people<00:24:14.090> I 00:24:14.260 --> 00:24:14.270 align:start position:0% will start problem for all people I 00:24:14.270 --> 00:24:16.060 align:start position:0% will start problem for all people I think<00:24:14.840> that's<00:24:14.990> the<00:24:15.110> common<00:24:15.410> vision<00:24:15.530> that<00:24:15.860> we 00:24:16.060 --> 00:24:16.070 align:start position:0% think that's the common vision that we 00:24:16.070 --> 00:24:18.190 align:start position:0% think that's the common vision that we are<00:24:16.190> we<00:24:16.820> are<00:24:16.910> all<00:24:17.059> sharing<00:24:17.270> here<00:24:17.570> so<00:24:17.840> we<00:24:17.960> are<00:24:18.080> we 00:24:18.190 --> 00:24:18.200 align:start position:0% are we are all sharing here so we are we 00:24:18.200 --> 00:24:20.289 align:start position:0% are we are all sharing here so we are we trying<00:24:18.500> to<00:24:18.740> kind<00:24:19.549> of<00:24:19.610> anticipate<00:24:19.850> this 00:24:20.289 --> 00:24:20.299 align:start position:0% trying to kind of anticipate this 00:24:20.299 --> 00:24:22.360 align:start position:0% trying to kind of anticipate this problem<00:24:20.660> and<00:24:20.870> for<00:24:21.470> us<00:24:21.620> it's<00:24:21.770> about<00:24:21.860> laying<00:24:22.190> the 00:24:22.360 --> 00:24:22.370 align:start position:0% problem and for us it's about laying the 00:24:22.370 --> 00:24:24.159 align:start position:0% problem and for us it's about laying the foundation<00:24:23.030> I<00:24:23.210> think<00:24:23.510> if<00:24:23.809> you<00:24:23.929> make<00:24:24.049> that 00:24:24.159 --> 00:24:24.169 align:start position:0% foundation I think if you make that 00:24:24.169 --> 00:24:25.750 align:start position:0% foundation I think if you make that analogy<00:24:24.530> between<00:24:24.860> the<00:24:25.130> blockchain<00:24:25.370> in<00:24:25.669> the 00:24:25.750 --> 00:24:25.760 align:start position:0% analogy between the blockchain in the 00:24:25.760 --> 00:24:27.430 align:start position:0% analogy between the blockchain in the internet<00:24:26.150> example<00:24:26.720> I<00:24:26.780> believe<00:24:27.260> on<00:24:27.410> the 00:24:27.430 --> 00:24:27.440 align:start position:0% internet example I believe on the 00:24:27.440 --> 00:24:28.990 align:start position:0% internet example I believe on the internet<00:24:27.860> people<00:24:28.220> are<00:24:28.309> to<00:24:28.429> write<00:24:28.610> common 00:24:28.990 --> 00:24:29.000 align:start position:0% internet people are to write common 00:24:29.000 --> 00:24:30.400 align:start position:0% internet people are to write common light<00:24:29.150> and<00:24:29.450> us<00:24:29.570> understand<00:24:29.990> this<00:24:30.140> would<00:24:30.320> be 00:24:30.400 --> 00:24:30.410 align:start position:0% light and us understand this would be 00:24:30.410 --> 00:24:32.680 align:start position:0% light and us understand this would be IKEA<00:24:30.770> and<00:24:31.100> then<00:24:31.580> suddenly<00:24:31.790> people 00:24:32.680 --> 00:24:32.690 align:start position:0% IKEA and then suddenly people 00:24:32.690 --> 00:24:34.299 align:start position:0% IKEA and then suddenly people with<00:24:32.899> the<00:24:32.989> idea<00:24:33.200> of<00:24:33.259> a<00:24:33.349> browser<00:24:33.590> and<00:24:34.009> then<00:24:34.159> you 00:24:34.299 --> 00:24:34.309 align:start position:0% with the idea of a browser and then you 00:24:34.309 --> 00:24:35.830 align:start position:0% with the idea of a browser and then you have<00:24:34.429> a<00:24:34.460> nice<00:24:34.639> interface<00:24:34.999> and<00:24:35.479> you<00:24:35.539> click<00:24:35.720> on 00:24:35.830 --> 00:24:35.840 align:start position:0% have a nice interface and you click on 00:24:35.840 --> 00:24:38.489 align:start position:0% have a nice interface and you click on that<00:24:36.019> and<00:24:36.200> then<00:24:36.470> it<00:24:36.499> becomes<00:24:37.220> much<00:24:37.549> more 00:24:38.489 --> 00:24:38.499 align:start position:0% that and then it becomes much more 00:24:38.499 --> 00:24:42.099 align:start position:0% that and then it becomes much more usable<00:24:39.499> by<00:24:39.739> my<00:24:40.070> own<00:24:40.309> people<00:24:40.549> and<00:24:41.330> I<00:24:41.450> think<00:24:41.509> for 00:24:42.099 --> 00:24:42.109 align:start position:0% usable by my own people and I think for 00:24:42.109 --> 00:24:44.799 align:start position:0% usable by my own people and I think for the<00:24:42.229> Internet<00:24:42.590> the<00:24:42.889> user<00:24:43.129> is<00:24:43.399> not<00:24:43.609> the<00:24:44.179> browser 00:24:44.799 --> 00:24:44.809 align:start position:0% the Internet the user is not the browser 00:24:44.809 --> 00:24:47.560 align:start position:0% the Internet the user is not the browser is<00:24:45.019> not<00:24:45.200> what<00:24:45.889> make<00:24:46.279> the<00:24:46.460> internet<00:24:46.849> go<00:24:46.999> wrong<00:24:47.299> I 00:24:47.560 --> 00:24:47.570 align:start position:0% is not what make the internet go wrong I 00:24:47.570 --> 00:24:49.419 align:start position:0% is not what make the internet go wrong I think<00:24:47.779> it<00:24:47.899> came<00:24:48.080> afterwards<00:24:48.590> games<00:24:49.249> by<00:24:49.399> the 00:24:49.419 --> 00:24:49.429 align:start position:0% think it came afterwards games by the 00:24:49.429 --> 00:24:51.070 align:start position:0% think it came afterwards games by the fact<00:24:49.729> that<00:24:49.820> there<00:24:49.999> was<00:24:50.090> no<00:24:50.239> native<00:24:50.570> payment<00:24:51.019> in 00:24:51.070 --> 00:24:51.080 align:start position:0% fact that there was no native payment in 00:24:51.080 --> 00:24:52.570 align:start position:0% fact that there was no native payment in the<00:24:51.169> browser<00:24:51.379> and<00:24:51.710> so<00:24:51.799> people<00:24:51.979> had<00:24:52.220> to<00:24:52.249> go<00:24:52.519> to 00:24:52.570 --> 00:24:52.580 align:start position:0% the browser and so people had to go to 00:24:52.580 --> 00:24:55.749 align:start position:0% the browser and so people had to go to to<00:24:53.299> marketing<00:24:53.809> and<00:24:53.989> and<00:24:54.499> ads<00:24:54.799> and<00:24:55.129> that's<00:24:55.519> what 00:24:55.749 --> 00:24:55.759 align:start position:0% to marketing and and ads and that's what 00:24:55.759 --> 00:24:57.940 align:start position:0% to marketing and and ads and that's what kind<00:24:55.970> of<00:24:56.029> corrupted<00:24:56.539> the<00:24:57.229> internet<00:24:57.590> so<00:24:57.919> I 00:24:57.940 --> 00:24:57.950 align:start position:0% kind of corrupted the internet so I 00:24:57.950 --> 00:25:00.009 align:start position:0% kind of corrupted the internet so I think<00:24:58.220> it's<00:24:58.340> it's<00:24:58.909> also<00:24:59.149> shows<00:24:59.539> that<00:24:59.779> by 00:25:00.009 --> 00:25:00.019 align:start position:0% think it's it's also shows that by 00:25:00.019 --> 00:25:02.019 align:start position:0% think it's it's also shows that by making<00:25:00.229> the<00:25:00.499> right<00:25:00.649> technological<00:25:01.519> choices 00:25:02.019 --> 00:25:02.029 align:start position:0% making the right technological choices 00:25:02.029 --> 00:25:04.419 align:start position:0% making the right technological choices now<00:25:02.539> we<00:25:03.080> are<00:25:03.259> preventing<00:25:03.739> a<00:25:04.099> thing<00:25:04.309> or 00:25:04.419 --> 00:25:04.429 align:start position:0% now we are preventing a thing or 00:25:04.429 --> 00:25:05.710 align:start position:0% now we are preventing a thing or technology<00:25:04.999> to<00:25:05.029> go<00:25:05.269> in<00:25:05.389> the<00:25:05.509> wrong<00:25:05.659> direction 00:25:05.710 --> 00:25:05.720 align:start position:0% technology to go in the wrong direction 00:25:05.720 --> 00:25:07.810 align:start position:0% technology to go in the wrong direction in<00:25:06.200> the<00:25:06.320> future<00:25:06.349> I<00:25:06.889> think<00:25:07.489> with<00:25:07.669> the<00:25:07.789> internet 00:25:07.810 --> 00:25:07.820 align:start position:0% in the future I think with the internet 00:25:07.820 --> 00:25:09.580 align:start position:0% in the future I think with the internet we<00:25:08.210> made<00:25:08.359> some<00:25:08.539> mistake<00:25:08.899> and<00:25:09.139> personally 00:25:09.580 --> 00:25:09.590 align:start position:0% we made some mistake and personally 00:25:09.590 --> 00:25:11.349 align:start position:0% we made some mistake and personally athlete<00:25:09.919> because<00:25:10.099> it's<00:25:10.639> because<00:25:10.879> of<00:25:10.999> payment 00:25:11.349 --> 00:25:11.359 align:start position:0% athlete because it's because of payment 00:25:11.359 --> 00:25:13.330 align:start position:0% athlete because it's because of payment the<00:25:11.479> lack<00:25:11.599> of<00:25:11.629> native<00:25:12.049> family<00:25:12.499> in<00:25:13.099> the 00:25:13.330 --> 00:25:13.340 align:start position:0% the lack of native family in the 00:25:13.340 --> 00:25:15.669 align:start position:0% the lack of native family in the internet<00:25:13.849> stack<00:25:14.119> and<00:25:14.359> I<00:25:14.419> think<00:25:14.629> it<00:25:15.169> is<00:25:15.349> kind<00:25:15.590> of 00:25:15.669 --> 00:25:15.679 align:start position:0% internet stack and I think it is kind of 00:25:15.679 --> 00:25:17.919 align:start position:0% internet stack and I think it is kind of a<00:25:15.799> responsibility<00:25:16.609> now<00:25:16.940> to<00:25:16.999> make<00:25:17.570> sure<00:25:17.599> that 00:25:17.919 --> 00:25:17.929 align:start position:0% a responsibility now to make sure that 00:25:17.929 --> 00:25:19.210 align:start position:0% a responsibility now to make sure that will<00:25:18.019> be<00:25:18.049> the<00:25:18.229> technology<00:25:18.470> that<00:25:18.830> doesn't 00:25:19.210 --> 00:25:19.220 align:start position:0% will be the technology that doesn't 00:25:19.220 --> 00:25:23.219 align:start position:0% will be the technology that doesn't reproduce 00:25:23.219 --> 00:25:23.229 align:start position:0% 00:25:23.229 --> 00:25:25.619 align:start position:0% thank<00:25:24.229> you<00:25:24.320> guys<00:25:24.470> for<00:25:24.649> sharing<00:25:24.799> your<00:25:25.070> insight 00:25:25.619 --> 00:25:25.629 align:start position:0% thank you guys for sharing your insight 00:25:25.629 --> 00:25:28.509 align:start position:0% thank you guys for sharing your insight in<00:25:26.629> now<00:25:27.139> we're<00:25:27.529> gonna<00:25:27.619> move<00:25:28.009> on<00:25:28.279> to<00:25:28.309> the 00:25:28.509 --> 00:25:28.519 align:start position:0% in now we're gonna move on to the 00:25:28.519 --> 00:25:30.279 align:start position:0% in now we're gonna move on to the ceremony<00:25:28.970> where<00:25:29.330> we're<00:25:29.479> gonna<00:25:29.570> be<00:25:29.809> ordinal 00:25:30.279 --> 00:25:30.289 align:start position:0% ceremony where we're gonna be ordinal 00:25:30.289 --> 00:25:34.599 align:start position:0% ceremony where we're gonna be ordinal winners<00:25:31.239> so<00:25:32.239> first<00:25:32.809> this<00:25:33.379> year<00:25:33.649> we've<00:25:33.859> got<00:25:34.099> the 00:25:34.599 --> 00:25:34.609 align:start position:0% winners so first this year we've got the 00:25:34.609 --> 00:25:37.930 align:start position:0% winners so first this year we've got the most<00:25:34.820> adorable<00:25:35.419> crypto<00:25:36.379> kayu<00:25:36.830> crypto<00:25:37.609> kitties 00:25:37.930 --> 00:25:37.940 align:start position:0% most adorable crypto kayu crypto kitties 00:25:37.940 --> 00:25:40.779 align:start position:0% most adorable crypto kayu crypto kitties and<00:25:38.330> their<00:25:39.019> physical<00:25:39.379> trophies<00:25:40.129> this<00:25:40.489> time 00:25:40.779 --> 00:25:40.789 align:start position:0% and their physical trophies this time 00:25:40.789 --> 00:25:44.529 align:start position:0% and their physical trophies this time and<00:25:41.509> they're<00:25:41.929> actually<00:25:42.309> with<00:25:43.309> it<00:25:43.519> NFT<00:25:44.239> and 00:25:44.529 --> 00:25:44.539 align:start position:0% and they're actually with it NFT and 00:25:44.539 --> 00:25:48.530 align:start position:0% and they're actually with it NFT and they<00:25:45.019> have<00:25:45.229> special<00:25:45.529> powers<00:25:45.950> which<00:25:46.190> is<00:25:46.399> us<00:25:47.409> in 00:25:48.530 --> 00:25:48.540 align:start position:0% they have special powers which is us in 00:25:48.540 --> 00:25:51.110 align:start position:0% they have special powers which is us in their<00:25:49.110> genes<00:25:49.380> so<00:25:50.220> thank<00:25:50.520> you<00:25:50.640> for<00:25:50.820> coming<00:25:51.000> to 00:25:51.110 --> 00:25:51.120 align:start position:0% their genes so thank you for coming to 00:25:51.120 --> 00:25:53.330 align:start position:0% their genes so thank you for coming to Kyle<00:25:51.330> for<00:25:51.630> participating<00:25:52.470> and<00:25:52.920> working<00:25:53.220> with 00:25:53.330 --> 00:25:53.340 align:start position:0% Kyle for participating and working with 00:25:53.340 --> 00:25:54.950 align:start position:0% Kyle for participating and working with us<00:25:53.490> on<00:25:53.670> this<00:25:53.850> we're<00:25:54.090> excited<00:25:54.390> you<00:25:54.630> guys<00:25:54.780> will 00:25:54.950 --> 00:25:54.960 align:start position:0% us on this we're excited you guys will 00:25:54.960 --> 00:25:56.470 align:start position:0% us on this we're excited you guys will see<00:25:55.080> the<00:25:55.170> trophies<00:25:55.500> living<00:25:55.770> with<00:25:55.890> you<00:25:56.040> and 00:25:56.470 --> 00:25:56.480 align:start position:0% see the trophies living with you and 00:25:56.480 --> 00:26:00.650 align:start position:0% see the trophies living with you and with<00:25:57.480> that<00:25:57.860> many<00:25:58.860> is<00:25:59.010> gonna<00:25:59.250> oh<00:25:59.520> sorry<00:26:00.360> with 00:26:00.650 --> 00:26:00.660 align:start position:0% with that many is gonna oh sorry with 00:26:00.660 --> 00:26:06.110 align:start position:0% with that many is gonna oh sorry with Jillian<00:26:01.730> first<00:26:02.730> thank<00:26:03.360> you<00:26:04.700> I'm<00:26:05.700> very<00:26:05.730> happy 00:26:06.110 --> 00:26:06.120 align:start position:0% Jillian first thank you I'm very happy 00:26:06.120 --> 00:26:08.930 align:start position:0% Jillian first thank you I'm very happy to<00:26:06.540> announce<00:26:06.570> that<00:26:07.010> the<00:26:08.010> first<00:26:08.280> winner<00:26:08.550> is<00:26:08.640> one 00:26:08.930 --> 00:26:08.940 align:start position:0% to announce that the first winner is one 00:26:08.940 --> 00:26:11.630 align:start position:0% to announce that the first winner is one instant<00:26:09.390> I<00:26:09.600> think<00:26:10.230> ramp<00:26:10.500> is<00:26:10.710> a<00:26:10.740> company<00:26:11.610> that 00:26:11.630 --> 00:26:11.640 align:start position:0% instant I think ramp is a company that 00:26:11.640 --> 00:26:14.180 align:start position:0% instant I think ramp is a company that sounds<00:26:12.030> a<00:26:12.090> very<00:26:12.230> complicated<00:26:13.230> problem<00:26:13.740> which 00:26:14.180 --> 00:26:14.190 align:start position:0% sounds a very complicated problem which 00:26:14.190 --> 00:26:16.930 align:start position:0% sounds a very complicated problem which is<00:26:14.400> going<00:26:14.850> from<00:26:15.000> Fiat<00:26:15.390> to<00:26:15.630> crypto<00:26:15.990> and 00:26:16.930 --> 00:26:16.940 align:start position:0% is going from Fiat to crypto and 00:26:16.940 --> 00:26:18.680 align:start position:0% is going from Fiat to crypto and unfortunately<00:26:17.940> I<00:26:18.000> wasn't<00:26:18.150> part<00:26:18.450> of<00:26:18.570> the 00:26:18.680 --> 00:26:18.690 align:start position:0% unfortunately I wasn't part of the 00:26:18.690 --> 00:26:20.240 align:start position:0% unfortunately I wasn't part of the discussion<00:26:19.200> when<00:26:19.230> I<00:26:19.590> received<00:26:19.920> the<00:26:20.040> feedback 00:26:20.240 --> 00:26:20.250 align:start position:0% discussion when I received the feedback 00:26:20.250 --> 00:26:22.580 align:start position:0% discussion when I received the feedback but<00:26:20.760> either<00:26:21.210> you<00:26:21.900> know<00:26:22.020> as<00:26:22.260> knowing<00:26:22.560> the 00:26:22.580 --> 00:26:22.590 align:start position:0% but either you know as knowing the 00:26:22.590 --> 00:26:23.990 align:start position:0% but either you know as knowing the product<00:26:23.070> I<00:26:23.190> think<00:26:23.400> what<00:26:23.520> they<00:26:23.670> do<00:26:23.730> extremely 00:26:23.990 --> 00:26:24.000 align:start position:0% product I think what they do extremely 00:26:24.000 --> 00:26:26.660 align:start position:0% product I think what they do extremely wide<00:26:24.450> what<00:26:25.320> right<00:26:25.620> and<00:26:25.830> it's<00:26:26.010> a<00:26:26.100> value<00:26:26.370> that<00:26:26.490> we 00:26:26.660 --> 00:26:26.670 align:start position:0% wide what right and it's a value that we 00:26:26.670 --> 00:26:28.940 align:start position:0% wide what right and it's a value that we share<00:26:26.940> is<00:26:27.420> that<00:26:27.660> the<00:26:27.780> abstract<00:26:28.050> the 00:26:28.940 --> 00:26:28.950 align:start position:0% share is that the abstract the 00:26:28.950 --> 00:26:30.710 align:start position:0% share is that the abstract the complexity<00:26:29.550> of<00:26:29.580> a<00:26:29.760> very<00:26:30.000> difficult<00:26:30.270> problem 00:26:30.710 --> 00:26:30.720 align:start position:0% complexity of a very difficult problem 00:26:30.720 --> 00:26:32.660 align:start position:0% complexity of a very difficult problem without<00:26:31.440> compromising<00:26:32.100> of<00:26:32.220> some<00:26:32.430> core 00:26:32.660 --> 00:26:32.670 align:start position:0% without compromising of some core 00:26:32.670 --> 00:26:34.460 align:start position:0% without compromising of some core principle<00:26:33.180> so<00:26:33.600> they<00:26:33.720> managed<00:26:33.960> to<00:26:33.990> maintain 00:26:34.460 --> 00:26:34.470 align:start position:0% principle so they managed to maintain 00:26:34.470 --> 00:26:36.560 align:start position:0% principle so they managed to maintain the<00:26:34.650> centralization<00:26:35.070> in<00:26:35.910> to<00:26:36.150> the<00:26:36.240> way<00:26:36.390> the 00:26:36.560 --> 00:26:36.570 align:start position:0% the centralization in to the way the 00:26:36.570 --> 00:26:39.800 align:start position:0% the centralization in to the way the recycled<00:26:37.020> yet<00:26:37.440> the<00:26:38.370> crypto<00:26:38.760> which<00:26:39.300> is<00:26:39.480> which 00:26:39.800 --> 00:26:39.810 align:start position:0% recycled yet the crypto which is which 00:26:39.810 --> 00:26:48.170 align:start position:0% recycled yet the crypto which is which is<00:26:39.840> quite<00:26:40.110> impressive<00:26:45.800> hi<00:26:46.800> thanks<00:26:47.580> really 00:26:48.170 --> 00:26:48.180 align:start position:0% is quite impressive hi thanks really 00:26:48.180 --> 00:26:55.580 align:start position:0% is quite impressive hi thanks really excited<00:26:48.660> to<00:26:48.780> be<00:26:48.900> here<00:26:53.420> so<00:26:54.420> that's<00:26:54.960> wrong<00:26:55.260> we 00:26:55.580 --> 00:26:55.590 align:start position:0% excited to be here so that's wrong we 00:26:55.590 --> 00:26:59.240 align:start position:0% excited to be here so that's wrong we try<00:26:55.830> to<00:26:55.910> solve<00:26:56.910> crypto<00:26:57.330> onboarding<00:26:57.840> and<00:26:57.990> or<00:26:58.860> at 00:26:59.240 --> 00:26:59.250 align:start position:0% try to solve crypto onboarding and or at 00:26:59.250 --> 00:27:01.250 align:start position:0% try to solve crypto onboarding and or at least<00:26:59.490> a<00:26:59.730> very<00:26:59.940> important<00:27:00.330> part<00:27:00.540> of<00:27:00.630> it 00:27:01.250 --> 00:27:01.260 align:start position:0% least a very important part of it 00:27:01.260 --> 00:27:03.620 align:start position:0% least a very important part of it Crypton<00:27:01.920> boarding<00:27:02.280> consists<00:27:02.760> of<00:27:02.880> first<00:27:03.360> we 00:27:03.620 --> 00:27:03.630 align:start position:0% Crypton boarding consists of first we 00:27:03.630 --> 00:27:06.110 align:start position:0% Crypton boarding consists of first we think<00:27:03.870> that<00:27:04.200> it<00:27:04.560> has<00:27:04.590> two<00:27:05.040> very<00:27:05.310> important 00:27:06.110 --> 00:27:06.120 align:start position:0% think that it has two very important 00:27:06.120 --> 00:27:08.240 align:start position:0% think that it has two very important parts<00:27:06.360> first<00:27:06.870> is<00:27:07.200> getting<00:27:07.590> your<00:27:07.710> crypto<00:27:08.040> and 00:27:08.240 --> 00:27:08.250 align:start position:0% parts first is getting your crypto and 00:27:08.250 --> 00:27:10.520 align:start position:0% parts first is getting your crypto and second<00:27:08.700> managing<00:27:09.060> your<00:27:09.180> keys<00:27:09.420> there<00:27:10.290> are<00:27:10.380> many 00:27:10.520 --> 00:27:10.530 align:start position:0% second managing your keys there are many 00:27:10.530 --> 00:27:12.830 align:start position:0% second managing your keys there are many companies<00:27:10.920> that<00:27:11.060> manage<00:27:12.060> your<00:27:12.330> keys<00:27:12.510> very 00:27:12.830 --> 00:27:12.840 align:start position:0% companies that manage your keys very 00:27:12.840 --> 00:27:15.380 align:start position:0% companies that manage your keys very well<00:27:13.050> and<00:27:13.290> we<00:27:13.440> are<00:27:13.560> pretty<00:27:13.980> close<00:27:14.370> to<00:27:14.910> getting 00:27:15.380 --> 00:27:15.390 align:start position:0% well and we are pretty close to getting 00:27:15.390 --> 00:27:17.000 align:start position:0% well and we are pretty close to getting this<00:27:15.480> problem<00:27:15.840> solved 00:27:17.000 --> 00:27:17.010 align:start position:0% this problem solved 00:27:17.010 --> 00:27:19.160 align:start position:0% this problem solved but<00:27:17.340> krypton<00:27:17.970> boarding<00:27:18.330> with<00:27:18.480> like<00:27:18.780> actually 00:27:19.160 --> 00:27:19.170 align:start position:0% but krypton boarding with like actually 00:27:19.170 --> 00:27:21.530 align:start position:0% but krypton boarding with like actually purchasing<00:27:19.590> crypto<00:27:19.980> is<00:27:20.190> so<00:27:20.610> complicated<00:27:21.000> so 00:27:21.530 --> 00:27:21.540 align:start position:0% purchasing crypto is so complicated so 00:27:21.540 --> 00:27:24.080 align:start position:0% purchasing crypto is so complicated so first<00:27:22.230> it's<00:27:22.440> complex<00:27:22.770> think<00:27:23.250> about<00:27:23.490> going<00:27:23.970> to 00:27:24.080 --> 00:27:24.090 align:start position:0% first it's complex think about going to 00:27:24.090 --> 00:27:25.840 align:start position:0% first it's complex think about going to a<00:27:24.120> dab<00:27:24.390> that<00:27:24.600> you<00:27:24.690> love<00:27:24.900> and<00:27:25.110> just<00:27:25.170> want<00:27:25.530> to<00:27:25.650> use 00:27:25.840 --> 00:27:25.850 align:start position:0% a dab that you love and just want to use 00:27:25.850 --> 00:27:29.660 align:start position:0% a dab that you love and just want to use but<00:27:26.850> actually<00:27:27.210> having<00:27:27.540> to<00:27:27.690> go<00:27:27.840> to<00:27:27.900> a<00:27:28.500> entire<00:27:29.430> an 00:27:29.660 --> 00:27:29.670 align:start position:0% but actually having to go to a entire an 00:27:29.670 --> 00:27:31.700 align:start position:0% but actually having to go to a entire an entirely<00:27:30.060> different<00:27:30.210> interface<00:27:31.020> in<00:27:31.290> order<00:27:31.440> to 00:27:31.700 --> 00:27:31.710 align:start position:0% entirely different interface in order to 00:27:31.710 --> 00:27:33.890 align:start position:0% entirely different interface in order to purchase<00:27:31.950> your<00:27:32.220> crypto<00:27:32.570> think<00:27:33.570> about<00:27:33.750> the 00:27:33.890 --> 00:27:33.900 align:start position:0% purchase your crypto think about the 00:27:33.900 --> 00:27:35.900 align:start position:0% purchase your crypto think about the chair<00:27:34.230> and<00:27:34.440> with<00:27:34.620> users<00:27:34.980> if<00:27:35.280> you<00:27:35.340> are<00:27:35.520> a<00:27:35.580> DAB 00:27:35.900 --> 00:27:35.910 align:start position:0% chair and with users if you are a DAB 00:27:35.910 --> 00:27:38.240 align:start position:0% chair and with users if you are a DAB that<00:27:36.120> is<00:27:36.210> actually<00:27:36.780> targeting<00:27:37.290> a<00:27:37.530> mass<00:27:38.040> user 00:27:38.240 --> 00:27:38.250 align:start position:0% that is actually targeting a mass user 00:27:38.250 --> 00:27:40.640 align:start position:0% that is actually targeting a mass user and<00:27:38.550> trying<00:27:38.940> to<00:27:39.150> get<00:27:39.360> crypto<00:27:40.170> to<00:27:40.500> mass 00:27:40.640 --> 00:27:40.650 align:start position:0% and trying to get crypto to mass 00:27:40.650 --> 00:27:41.769 align:start position:0% and trying to get crypto to mass adoption<00:27:40.920> and 00:27:41.769 --> 00:27:41.779 align:start position:0% adoption and 00:27:41.779 --> 00:27:45.729 align:start position:0% adoption and then<00:27:41.960> getting<00:27:42.469> to<00:27:42.799> send<00:27:43.580> them<00:27:43.820> or<00:27:44.739> relating 00:27:45.729 --> 00:27:45.739 align:start position:0% then getting to send them or relating 00:27:45.739 --> 00:27:47.889 align:start position:0% then getting to send them or relating them<00:27:45.919> to<00:27:45.950> some<00:27:46.279> third-party<00:27:46.609> websites<00:27:47.330> in 00:27:47.889 --> 00:27:47.899 align:start position:0% them to some third-party websites in 00:27:47.899 --> 00:27:50.139 align:start position:0% them to some third-party websites in order<00:27:48.169> to<00:27:48.349> purchase<00:27:48.710> your<00:27:48.979> crypto<00:27:49.340> and<00:27:49.609> then 00:27:50.139 --> 00:27:50.149 align:start position:0% order to purchase your crypto and then 00:27:50.149 --> 00:27:52.450 align:start position:0% order to purchase your crypto and then imagine<00:27:50.479> how<00:27:50.929> much<00:27:51.590> how<00:27:51.830> many<00:27:51.889> of<00:27:52.219> your<00:27:52.429> users 00:27:52.450 --> 00:27:52.460 align:start position:0% imagine how much how many of your users 00:27:52.460 --> 00:27:54.849 align:start position:0% imagine how much how many of your users like<00:27:53.090> normal<00:27:53.719> typical<00:27:54.080> users<00:27:54.349> who<00:27:54.559> are<00:27:54.649> used 00:27:54.849 --> 00:27:54.859 align:start position:0% like normal typical users who are used 00:27:54.859 --> 00:27:57.759 align:start position:0% like normal typical users who are used to<00:27:55.149> one-click<00:27:56.149> everything<00:27:56.690> would<00:27:57.139> turn<00:27:57.169> and 00:27:57.759 --> 00:27:57.769 align:start position:0% to one-click everything would turn and 00:27:57.769 --> 00:28:00.940 align:start position:0% to one-click everything would turn and just<00:27:57.919> turn<00:27:58.129> away<00:27:59.469> second<00:28:00.469> its<00:28:00.649> intimidating 00:28:00.940 --> 00:28:00.950 align:start position:0% just turn away second its intimidating 00:28:00.950 --> 00:28:03.159 align:start position:0% just turn away second its intimidating so<00:28:01.669> why<00:28:01.969> do<00:28:02.029> you<00:28:02.149> need<00:28:02.299> my<00:28:02.450> passport<00:28:02.659> why<00:28:03.109> do 00:28:03.159 --> 00:28:03.169 align:start position:0% so why do you need my passport why do 00:28:03.169 --> 00:28:05.950 align:start position:0% so why do you need my passport why do you<00:28:03.289> need<00:28:03.440> my<00:28:03.559> ID<00:28:03.799> why<00:28:04.309> do<00:28:04.369> you<00:28:04.519> need<00:28:04.669> my<00:28:04.960> car 00:28:05.950 --> 00:28:05.960 align:start position:0% you need my ID why do you need my car 00:28:05.960 --> 00:28:10.629 align:start position:0% you need my ID why do you need my car license<00:28:06.409> car<00:28:07.309> driving<00:28:08.210> license<00:28:09.129> we<00:28:10.129> also 00:28:10.629 --> 00:28:10.639 align:start position:0% license car driving license we also 00:28:10.639 --> 00:28:12.999 align:start position:0% license car driving license we also think<00:28:11.149> that<00:28:11.299> this<00:28:12.049> turns<00:28:12.349> away<00:28:12.559> a<00:28:12.679> lot<00:28:12.889> of 00:28:12.999 --> 00:28:13.009 align:start position:0% think that this turns away a lot of 00:28:13.009 --> 00:28:15.089 align:start position:0% think that this turns away a lot of users<00:28:13.279> who<00:28:13.460> just<00:28:13.639> want<00:28:13.789> to<00:28:13.849> casually<00:28:14.450> try 00:28:15.089 --> 00:28:15.099 align:start position:0% users who just want to casually try 00:28:15.099 --> 00:28:18.549 align:start position:0% users who just want to casually try crypto<00:28:16.099> for<00:28:16.129> the<00:28:16.429> first<00:28:16.639> time<00:28:16.940> and<00:28:17.320> it<00:28:18.320> also 00:28:18.549 --> 00:28:18.559 align:start position:0% crypto for the first time and it also 00:28:18.559 --> 00:28:21.190 align:start position:0% crypto for the first time and it also creates<00:28:19.009> a<00:28:19.219> lot<00:28:19.249> of<00:28:19.460> churn<00:28:19.789> free<00:28:20.690> it's<00:28:20.989> time 00:28:21.190 --> 00:28:21.200 align:start position:0% creates a lot of churn free it's time 00:28:21.200 --> 00:28:23.979 align:start position:0% creates a lot of churn free it's time consuming<00:28:21.229> that's<00:28:22.099> self-explanatory<00:28:22.749> for<00:28:23.749> it 00:28:23.979 --> 00:28:23.989 align:start position:0% consuming that's self-explanatory for it 00:28:23.989 --> 00:28:29.139 align:start position:0% consuming that's self-explanatory for it is<00:28:24.109> scary<00:28:24.529> we<00:28:24.859> hear<00:28:25.669> about<00:28:25.789> crypto<00:28:28.149> exchanges 00:28:29.139 --> 00:28:29.149 align:start position:0% is scary we hear about crypto exchanges 00:28:29.149 --> 00:28:31.149 align:start position:0% is scary we hear about crypto exchanges collapsing<00:28:29.719> all<00:28:29.899> the<00:28:30.049> time<00:28:30.259> and<00:28:30.559> this<00:28:30.979> is<00:28:31.039> a 00:28:31.149 --> 00:28:31.159 align:start position:0% collapsing all the time and this is a 00:28:31.159 --> 00:28:32.829 align:start position:0% collapsing all the time and this is a crowd<00:28:31.489> level<00:28:31.729> if<00:28:31.789> you<00:28:31.879> can<00:28:31.909> really<00:28:32.179> solve<00:28:32.479> with 00:28:32.829 --> 00:28:32.839 align:start position:0% crowd level if you can really solve with 00:28:32.839 --> 00:28:36.129 align:start position:0% crowd level if you can really solve with smart<00:28:33.710> smart<00:28:34.429> contract<00:28:34.789> infrastructure<00:28:35.509> so 00:28:36.129 --> 00:28:36.139 align:start position:0% smart smart contract infrastructure so 00:28:36.139 --> 00:28:38.979 align:start position:0% smart smart contract infrastructure so what<00:28:36.289> we<00:28:36.409> thought<00:28:36.619> is<00:28:36.889> to<00:28:37.609> build<00:28:37.909> an<00:28:38.119> a<00:28:38.479> crypto 00:28:38.979 --> 00:28:38.989 align:start position:0% what we thought is to build an a crypto 00:28:38.989 --> 00:28:40.599 align:start position:0% what we thought is to build an a crypto all<00:28:39.109> around<00:28:39.379> built<00:28:39.710> on<00:28:39.859> smart<00:28:40.129> contracts 00:28:40.599 --> 00:28:40.609 align:start position:0% all around built on smart contracts 00:28:40.609 --> 00:28:44.070 align:start position:0% all around built on smart contracts entirely<00:28:41.089> peer-to-peer<00:28:41.479> and<00:28:42.399> custodial<00:28:43.399> mess 00:28:44.070 --> 00:28:44.080 align:start position:0% entirely peer-to-peer and custodial mess 00:28:44.080 --> 00:28:46.899 align:start position:0% entirely peer-to-peer and custodial mess but<00:28:45.080> really<00:28:45.799> if<00:28:45.950> you<00:28:46.070> build<00:28:46.309> some<00:28:46.489> cool<00:28:46.669> tech 00:28:46.899 --> 00:28:46.909 align:start position:0% but really if you build some cool tech 00:28:46.909 --> 00:28:48.430 align:start position:0% but really if you build some cool tech you<00:28:47.029> need<00:28:47.179> to<00:28:47.330> think<00:28:47.570> about<00:28:47.719> the<00:28:47.989> end<00:28:48.109> users 00:28:48.430 --> 00:28:48.440 align:start position:0% you need to think about the end users 00:28:48.440 --> 00:28:52.509 align:start position:0% you need to think about the end users you<00:28:48.830> need<00:28:48.979> to<00:28:49.789> base<00:28:50.059> your<00:28:50.589> development<00:28:51.589> or<00:28:51.830> on 00:28:52.509 --> 00:28:52.519 align:start position:0% you need to base your development or on 00:28:52.519 --> 00:28:55.599 align:start position:0% you need to base your development or on empathy<00:28:53.330> it's<00:28:53.539> not<00:28:53.719> enough<00:28:53.960> to<00:28:54.139> build<00:28:54.289> a<00:28:54.609> cool 00:28:55.599 --> 00:28:55.609 align:start position:0% empathy it's not enough to build a cool 00:28:55.609 --> 00:28:57.279 align:start position:0% empathy it's not enough to build a cool tech<00:28:55.879> you<00:28:56.119> need<00:28:56.239> to<00:28:56.389> wrap<00:28:56.599> it<00:28:56.779> with<00:28:57.019> an 00:28:57.279 --> 00:28:57.289 align:start position:0% tech you need to wrap it with an 00:28:57.289 --> 00:28:59.589 align:start position:0% tech you need to wrap it with an enjoyable<00:28:57.679> user<00:28:58.129> interface<00:28:58.700> to<00:28:58.999> create<00:28:59.179> this 00:28:59.589 --> 00:28:59.599 align:start position:0% enjoyable user interface to create this 00:28:59.599 --> 00:29:02.739 align:start position:0% enjoyable user interface to create this delightful<00:29:00.019> experience<00:29:00.769> so<00:29:01.549> first<00:29:02.210> ramp 00:29:02.739 --> 00:29:02.749 align:start position:0% delightful experience so first ramp 00:29:02.749 --> 00:29:04.629 align:start position:0% delightful experience so first ramp instant<00:29:03.229> is<00:29:03.379> a<00:29:03.679> widget<00:29:04.039> that<00:29:04.369> you<00:29:04.519> can 00:29:04.629 --> 00:29:04.639 align:start position:0% instant is a widget that you can 00:29:04.639 --> 00:29:08.709 align:start position:0% instant is a widget that you can implement<00:29:04.969> into<00:29:05.509> your<00:29:05.539> DAP<00:29:05.929> today<00:29:06.759> or<00:29:07.759> if<00:29:08.539> you 00:29:08.709 --> 00:29:08.719 align:start position:0% implement into your DAP today or if you 00:29:08.719 --> 00:29:10.989 align:start position:0% implement into your DAP today or if you run<00:29:08.869> if<00:29:09.080> you<00:29:09.200> build<00:29:09.409> a<00:29:09.499> wallet<00:29:09.889> we<00:29:10.219> are<00:29:10.399> also<00:29:10.669> we 00:29:10.989 --> 00:29:10.999 align:start position:0% run if you build a wallet we are also we 00:29:10.999 --> 00:29:12.700 align:start position:0% run if you build a wallet we are also we are<00:29:11.149> also<00:29:11.269> we<00:29:11.779> also<00:29:11.929> think<00:29:12.169> that<00:29:12.289> this<00:29:12.529> is<00:29:12.589> a 00:29:12.700 --> 00:29:12.710 align:start position:0% are also we also think that this is a 00:29:12.710 --> 00:29:15.759 align:start position:0% are also we also think that this is a great<00:29:13.249> way<00:29:13.429> to<00:29:13.460> onboard<00:29:13.879> your<00:29:14.299> new<00:29:14.479> users<00:29:14.839> into 00:29:15.759 --> 00:29:15.769 align:start position:0% great way to onboard your new users into 00:29:15.769 --> 00:29:19.539 align:start position:0% great way to onboard your new users into crypto<00:29:16.239> so<00:29:17.239> the<00:29:18.169> ramp<00:29:18.320> instant<00:29:18.679> becomes<00:29:19.099> part 00:29:19.539 --> 00:29:19.549 align:start position:0% crypto so the ramp instant becomes part 00:29:19.549 --> 00:29:22.299 align:start position:0% crypto so the ramp instant becomes part of<00:29:19.729> the<00:29:19.879> flow<00:29:20.149> of<00:29:20.389> your<00:29:20.599> adapt<00:29:20.859> second<00:29:21.859> with<00:29:22.039> it 00:29:22.299 --> 00:29:22.309 align:start position:0% of the flow of your adapt second with it 00:29:22.309 --> 00:29:24.539 align:start position:0% of the flow of your adapt second with it connects<00:29:22.669> with<00:29:22.820> your<00:29:22.940> bank<00:29:23.179> and<00:29:23.450> this<00:29:23.899> solves 00:29:24.539 --> 00:29:24.549 align:start position:0% connects with your bank and this solves 00:29:24.549 --> 00:29:27.969 align:start position:0% connects with your bank and this solves kyc<00:29:25.549> issues<00:29:25.940> most<00:29:26.570> of<00:29:26.690> our<00:29:26.869> users<00:29:27.019> can<00:29:27.529> do 00:29:27.969 --> 00:29:27.979 align:start position:0% kyc issues most of our users can do 00:29:27.979 --> 00:29:30.430 align:start position:0% kyc issues most of our users can do their<00:29:28.639> purchases<00:29:29.239> without<00:29:29.690> scanning<00:29:30.289> their 00:29:30.430 --> 00:29:30.440 align:start position:0% their purchases without scanning their 00:29:30.440 --> 00:29:34.269 align:start position:0% their purchases without scanning their license<00:29:30.919> or<00:29:31.269> passport<00:29:32.269> free<00:29:33.229> we<00:29:33.649> let<00:29:33.889> users 00:29:34.269 --> 00:29:34.279 align:start position:0% license or passport free we let users 00:29:34.279 --> 00:29:37.419 align:start position:0% license or passport free we let users keep<00:29:35.210> control<00:29:35.629> so<00:29:35.869> we<00:29:36.019> do<00:29:36.200> not<00:29:36.619> ask<00:29:36.859> them<00:29:37.099> for 00:29:37.419 --> 00:29:37.429 align:start position:0% keep control so we do not ask them for 00:29:37.429 --> 00:29:40.029 align:start position:0% keep control so we do not ask them for their<00:29:37.759> credit<00:29:38.179> card<00:29:38.419> we<00:29:38.690> do<00:29:38.899> it<00:29:39.080> via<00:29:39.469> a<00:29:39.619> banking 00:29:40.029 --> 00:29:40.039 align:start position:0% their credit card we do it via a banking 00:29:40.039 --> 00:29:43.570 align:start position:0% their credit card we do it via a banking interface<00:29:40.519> and<00:29:41.049> every<00:29:42.049> transaction<00:29:42.919> needs<00:29:43.339> to 00:29:43.570 --> 00:29:43.580 align:start position:0% interface and every transaction needs to 00:29:43.580 --> 00:29:45.609 align:start position:0% interface and every transaction needs to be<00:29:43.700> confirmed<00:29:44.089> by<00:29:44.330> the<00:29:44.389> user<00:29:44.690> inside<00:29:45.409> the 00:29:45.609 --> 00:29:45.619 align:start position:0% be confirmed by the user inside the 00:29:45.619 --> 00:29:47.049 align:start position:0% be confirmed by the user inside the banking<00:29:45.979> device<00:29:46.249> you<00:29:46.429> will<00:29:46.549> see<00:29:46.700> that<00:29:46.820> in<00:29:46.999> the 00:29:47.049 --> 00:29:47.059 align:start position:0% banking device you will see that in the 00:29:47.059 --> 00:29:50.049 align:start position:0% banking device you will see that in the moments<00:29:47.389> and<00:29:48.009> first<00:29:49.009> and<00:29:49.190> foremost<00:29:49.580> it<00:29:49.849> is 00:29:50.049 --> 00:29:50.059 align:start position:0% moments and first and foremost it is 00:29:50.059 --> 00:29:52.640 align:start position:0% moments and first and foremost it is based<00:29:50.779> on<00:29:50.869> smart<00:29:51.139> contracts 00:29:52.640 --> 00:29:52.650 align:start position:0% based on smart contracts 00:29:52.650 --> 00:29:55.280 align:start position:0% based on smart contracts and<00:29:52.850> maintains<00:29:53.850> an<00:29:54.210> escrow<00:29:54.660> for<00:29:54.930> each<00:29:55.080> and 00:29:55.280 --> 00:29:55.290 align:start position:0% and maintains an escrow for each and 00:29:55.290 --> 00:29:57.260 align:start position:0% and maintains an escrow for each and every<00:29:55.500> transaction<00:29:55.710> that<00:29:56.010> you<00:29:56.220> initiate<00:29:56.730> so 00:29:57.260 --> 00:29:57.270 align:start position:0% every transaction that you initiate so 00:29:57.270 --> 00:29:59.930 align:start position:0% every transaction that you initiate so you<00:29:57.330> do<00:29:57.570> not<00:29:57.690> need<00:29:57.900> to<00:29:58.170> fear<00:29:59.100> about<00:29:59.340> your 00:29:59.930 --> 00:29:59.940 align:start position:0% you do not need to fear about your 00:29:59.940 --> 00:30:02.780 align:start position:0% you do not need to fear about your transaction<00:30:00.780> coming<00:30:01.290> through<00:30:01.530> and<00:30:01.770> it<00:30:02.430> is<00:30:02.550> not 00:30:02.780 --> 00:30:02.790 align:start position:0% transaction coming through and it is not 00:30:02.790 --> 00:30:04.760 align:start position:0% transaction coming through and it is not as<00:30:03.030> scary<00:30:03.360> as<00:30:03.690> using<00:30:03.960> a<00:30:04.050> centralized<00:30:04.530> exchange 00:30:04.760 --> 00:30:04.770 align:start position:0% as scary as using a centralized exchange 00:30:04.770 --> 00:30:08.450 align:start position:0% as scary as using a centralized exchange so<00:30:05.960> when<00:30:06.960> it<00:30:07.050> comes<00:30:07.260> to<00:30:07.440> design<00:30:07.710> process<00:30:08.190> we 00:30:08.450 --> 00:30:08.460 align:start position:0% so when it comes to design process we 00:30:08.460 --> 00:30:10.130 align:start position:0% so when it comes to design process we thought<00:30:08.640> that<00:30:08.850> it<00:30:09.060> is<00:30:09.180> very<00:30:09.480> important<00:30:09.990> to 00:30:10.130 --> 00:30:10.140 align:start position:0% thought that it is very important to 00:30:10.140 --> 00:30:14.930 align:start position:0% thought that it is very important to actually<00:30:10.350> talk<00:30:10.800> with<00:30:11.010> users<00:30:11.370> and<00:30:12.920> to<00:30:13.920> do<00:30:14.100> an 00:30:14.930 --> 00:30:14.940 align:start position:0% actually talk with users and to do an 00:30:14.940 --> 00:30:16.970 align:start position:0% actually talk with users and to do an interrupted<00:30:15.870> process<00:30:16.260> when<00:30:16.440> you<00:30:16.530> prototype 00:30:16.970 --> 00:30:16.980 align:start position:0% interrupted process when you prototype 00:30:16.980 --> 00:30:19.100 align:start position:0% interrupted process when you prototype user<00:30:17.310> tests<00:30:17.610> and<00:30:17.820> repeat<00:30:18.090> prototype<00:30:18.720> user 00:30:19.100 --> 00:30:19.110 align:start position:0% user tests and repeat prototype user 00:30:19.110 --> 00:30:20.870 align:start position:0% user tests and repeat prototype user tests<00:30:19.380> and<00:30:19.530> repeat<00:30:19.800> and<00:30:20.010> by<00:30:20.490> the<00:30:20.550> way<00:30:20.670> there<00:30:20.850> is 00:30:20.870 --> 00:30:20.880 align:start position:0% tests and repeat and by the way there is 00:30:20.880 --> 00:30:24.500 align:start position:0% tests and repeat and by the way there is a<00:30:20.970> cool<00:30:21.390> tip<00:30:21.720> if<00:30:22.320> you<00:30:22.560> want<00:30:22.980> to<00:30:23.760> supercharge 00:30:24.500 --> 00:30:24.510 align:start position:0% a cool tip if you want to supercharge 00:30:24.510 --> 00:30:26.420 align:start position:0% a cool tip if you want to supercharge this<00:30:24.720> process<00:30:25.140> talk<00:30:25.440> with<00:30:25.620> deep<00:30:25.860> work<00:30:26.100> studio 00:30:26.420 --> 00:30:26.430 align:start position:0% this process talk with deep work studio 00:30:26.430 --> 00:30:28.700 align:start position:0% this process talk with deep work studio they<00:30:26.640> structured<00:30:27.120> our<00:30:27.390> designing<00:30:28.290> process 00:30:28.700 --> 00:30:28.710 align:start position:0% they structured our designing process 00:30:28.710 --> 00:30:31.610 align:start position:0% they structured our designing process Charlie<00:30:29.100> is<00:30:29.220> their<00:30:30.050> big<00:30:31.050> round<00:30:31.230> of<00:30:31.350> applause 00:30:31.610 --> 00:30:31.620 align:start position:0% Charlie is their big round of applause 00:30:31.620 --> 00:30:35.570 align:start position:0% Charlie is their big round of applause to<00:30:31.650> Charlie<00:30:32.130> and<00:30:33.710> yet<00:30:34.710> so<00:30:34.920> today<00:30:35.280> you<00:30:35.340> can 00:30:35.570 --> 00:30:35.580 align:start position:0% to Charlie and yet so today you can 00:30:35.580 --> 00:30:37.670 align:start position:0% to Charlie and yet so today you can enjoy<00:30:35.880> ramp<00:30:36.150> instant<00:30:36.570> on<00:30:36.750> your<00:30:36.900> phone<00:30:37.170> and<00:30:37.440> on 00:30:37.670 --> 00:30:37.680 align:start position:0% enjoy ramp instant on your phone and on 00:30:37.680 --> 00:30:40.430 align:start position:0% enjoy ramp instant on your phone and on your<00:30:37.860> desktop<00:30:38.340> it<00:30:38.730> is<00:30:38.790> a<00:30:38.910> standalone<00:30:39.510> krypton 00:30:40.430 --> 00:30:40.440 align:start position:0% your desktop it is a standalone krypton 00:30:40.440 --> 00:30:41.930 align:start position:0% your desktop it is a standalone krypton boarding<00:30:40.770> app<00:30:40.950> but<00:30:41.190> you<00:30:41.250> can<00:30:41.400> also<00:30:41.520> implement 00:30:41.930 --> 00:30:41.940 align:start position:0% boarding app but you can also implement 00:30:41.940 --> 00:30:45.290 align:start position:0% boarding app but you can also implement it<00:30:42.330> into<00:30:42.570> your<00:30:42.780> tap<00:30:43.140> or<00:30:43.350> wallet<00:30:43.940> it's<00:30:44.940> sweet 00:30:45.290 --> 00:30:45.300 align:start position:0% it into your tap or wallet it's sweet 00:30:45.300 --> 00:30:47.780 align:start position:0% it into your tap or wallet it's sweet it's<00:30:45.660> very<00:30:45.840> simple<00:30:46.380> to<00:30:46.530> use<00:30:46.560> I<00:30:46.950> hope<00:30:47.160> we<00:30:47.310> can 00:30:47.780 --> 00:30:47.790 align:start position:0% it's very simple to use I hope we can 00:30:47.790 --> 00:30:51.380 align:start position:0% it's very simple to use I hope we can get<00:30:47.910> this<00:30:48.060> video<00:30:48.240> to<00:30:48.360> work<00:30:48.540> yeah<00:30:48.810> it<00:30:48.960> works<00:30:50.390> so 00:30:51.380 --> 00:30:51.390 align:start position:0% get this video to work yeah it works so 00:30:51.390 --> 00:30:53.030 align:start position:0% get this video to work yeah it works so in<00:30:51.600> this<00:30:51.750> flow<00:30:51.990> you<00:30:52.230> connect<00:30:52.620> to<00:30:52.740> your<00:30:52.770> bank 00:30:53.030 --> 00:30:53.040 align:start position:0% in this flow you connect to your bank 00:30:53.040 --> 00:30:54.620 align:start position:0% in this flow you connect to your bank account<00:30:53.370> and<00:30:53.610> you<00:30:53.790> create<00:30:54.090> an<00:30:54.210> instant 00:30:54.620 --> 00:30:54.630 align:start position:0% account and you create an instant 00:30:54.630 --> 00:30:56.300 align:start position:0% account and you create an instant payment<00:30:54.840> this<00:30:55.440> instant<00:30:55.800> payment<00:30:55.980> gets 00:30:56.300 --> 00:30:56.310 align:start position:0% payment this instant payment gets 00:30:56.310 --> 00:30:59.810 align:start position:0% payment this instant payment gets initiated<00:30:56.640> inside<00:30:57.860> the<00:30:58.860> actual<00:30:59.190> banking<00:30:59.700> app 00:30:59.810 --> 00:30:59.820 align:start position:0% initiated inside the actual banking app 00:30:59.820 --> 00:31:02.000 align:start position:0% initiated inside the actual banking app you<00:31:00.210> authorized<00:31:00.660> inside<00:31:01.170> the<00:31:01.320> banking<00:31:01.860> app 00:31:02.000 --> 00:31:02.010 align:start position:0% you authorized inside the banking app 00:31:02.010 --> 00:31:05.120 align:start position:0% you authorized inside the banking app and<00:31:02.190> just<00:31:03.090> after<00:31:03.210> minutes<00:31:03.750> the<00:31:04.500> payment<00:31:05.010> is 00:31:05.120 --> 00:31:05.130 align:start position:0% and just after minutes the payment is 00:31:05.130 --> 00:31:07.760 align:start position:0% and just after minutes the payment is confirmed<00:31:05.340> and<00:31:05.850> you<00:31:06.540> can<00:31:06.720> expect<00:31:07.110> your<00:31:07.320> crypto 00:31:07.760 --> 00:31:07.770 align:start position:0% confirmed and you can expect your crypto 00:31:07.770 --> 00:31:12.620 align:start position:0% confirmed and you can expect your crypto to<00:31:08.520> reach<00:31:09.390> your<00:31:09.720> user<00:31:10.520> within<00:31:11.520> 3<00:31:12.300> minutes<00:31:12.480> or 00:31:12.620 --> 00:31:12.630 align:start position:0% to reach your user within 3 minutes or 00:31:12.630 --> 00:31:13.100 align:start position:0% to reach your user within 3 minutes or less 00:31:13.100 --> 00:31:13.110 align:start position:0% less 00:31:13.110 --> 00:31:16.070 align:start position:0% less so<00:31:13.710> that's<00:31:13.950> romp<00:31:14.130> instant<00:31:14.570> you<00:31:15.570> can<00:31:15.810> actually 00:31:16.070 --> 00:31:16.080 align:start position:0% so that's romp instant you can actually 00:31:16.080 --> 00:31:19.550 align:start position:0% so that's romp instant you can actually use<00:31:16.740> it<00:31:16.890> today<00:31:17.390> go<00:31:18.390> to<00:31:18.450> ramped-up<00:31:19.050> network 00:31:19.550 --> 00:31:19.560 align:start position:0% use it today go to ramped-up network 00:31:19.560 --> 00:31:21.770 align:start position:0% use it today go to ramped-up network that's<00:31:19.890> ramp<00:31:20.250> that's<00:31:20.610> network<00:31:21.060> or<00:31:21.240> scan<00:31:21.660> this 00:31:21.770 --> 00:31:21.780 align:start position:0% that's ramp that's network or scan this 00:31:21.780 --> 00:31:24.920 align:start position:0% that's ramp that's network or scan this QR<00:31:22.020> code<00:31:22.200> and<00:31:22.730> we<00:31:23.730> can<00:31:23.910> get<00:31:24.090> you<00:31:24.180> ready<00:31:24.780> to 00:31:24.920 --> 00:31:24.930 align:start position:0% QR code and we can get you ready to 00:31:24.930 --> 00:31:27.860 align:start position:0% QR code and we can get you ready to implement<00:31:25.830> it<00:31:26.220> in<00:31:26.460> just<00:31:26.700> minutes<00:31:27.000> it's<00:31:27.300> 17 00:31:27.860 --> 00:31:27.870 align:start position:0% implement it in just minutes it's 17 00:31:27.870 --> 00:31:31.070 align:start position:0% implement it in just minutes it's 17 lines<00:31:28.230> of<00:31:28.410> code<00:31:28.620> very<00:31:28.950> simple<00:31:29.340> as<00:31:29.460> decay<00:31:30.080> we 00:31:31.070 --> 00:31:31.080 align:start position:0% lines of code very simple as decay we 00:31:31.080 --> 00:31:33.200 align:start position:0% lines of code very simple as decay we handle<00:31:31.500> all<00:31:31.710> of<00:31:31.860> it<00:31:31.980> liquidity<00:31:32.490> regulatory 00:31:33.200 --> 00:31:33.210 align:start position:0% handle all of it liquidity regulatory 00:31:33.210 --> 00:31:36.050 align:start position:0% handle all of it liquidity regulatory and<00:31:33.990> parts<00:31:34.800> of<00:31:34.920> the<00:31:35.040> interface<00:31:35.610> because<00:31:35.790> we 00:31:36.050 --> 00:31:36.060 align:start position:0% and parts of the interface because we 00:31:36.060 --> 00:31:37.580 align:start position:0% and parts of the interface because we provide<00:31:36.240> a<00:31:36.360> widget<00:31:36.600> that<00:31:36.750> is<00:31:36.870> co-branded<00:31:37.440> with 00:31:37.580 --> 00:31:37.590 align:start position:0% provide a widget that is co-branded with 00:31:37.590 --> 00:31:51.299 align:start position:0% provide a widget that is co-branded with your<00:31:37.710> brand<00:31:37.950> thank<00:31:38.520> you 00:31:51.299 --> 00:31:51.309 align:start position:0% 00:31:51.309 --> 00:31:56.919 align:start position:0% and<00:31:52.899> next<00:31:53.899> we're<00:31:54.260> excited<00:31:54.649> for<00:31:55.390> all<00:31:56.390> and<00:31:56.750> to 00:31:56.919 --> 00:31:56.929 align:start position:0% and next we're excited for all and to 00:31:56.929 --> 00:31:58.350 align:start position:0% and next we're excited for all and to introduce<00:31:57.169> Reeboks 00:31:58.350 --> 00:31:58.360 align:start position:0% introduce Reeboks 00:31:58.360 --> 00:32:02.139 align:start position:0% introduce Reeboks servants<00:31:59.360> for<00:31:59.600> that<00:31:59.750> for<00:32:00.169> the<00:32:00.260> last<00:32:01.149> three 00:32:02.139 --> 00:32:02.149 align:start position:0% servants for that for the last three 00:32:02.149 --> 00:32:04.269 align:start position:0% servants for that for the last three days<00:32:02.299> we<00:32:02.600> heard<00:32:02.840> a<00:32:02.899> lot<00:32:03.049> this<00:32:03.470> comparison<00:32:03.950> of 00:32:04.269 --> 00:32:04.279 align:start position:0% days we heard a lot this comparison of 00:32:04.279 --> 00:32:08.320 align:start position:0% days we heard a lot this comparison of the<00:32:04.399> two<00:32:04.580> projects<00:32:05.210> -<00:32:05.860> Lego<00:32:06.860> blocks<00:32:07.220> and<00:32:07.549> three 00:32:08.320 --> 00:32:08.330 align:start position:0% the two projects - Lego blocks and three 00:32:08.330 --> 00:32:12.519 align:start position:0% the two projects - Lego blocks and three box<00:32:08.600> common<00:32:09.230> component<00:32:10.899> Commons<00:32:11.899> components 00:32:12.519 --> 00:32:12.529 align:start position:0% box common component Commons components 00:32:12.529 --> 00:32:16.889 align:start position:0% box common component Commons components is<00:32:12.649> exactly<00:32:13.520> that<00:32:13.760> it's<00:32:14.270> tiny<00:32:15.070> inconspicuous 00:32:16.889 --> 00:32:16.899 align:start position:0% is exactly that it's tiny inconspicuous 00:32:16.899 --> 00:32:19.570 align:start position:0% is exactly that it's tiny inconspicuous blog<00:32:17.899> that<00:32:18.380> has<00:32:18.590> a<00:32:18.620> little<00:32:18.980> bit<00:32:19.100> of<00:32:19.220> Technology 00:32:19.570 --> 00:32:19.580 align:start position:0% blog that has a little bit of Technology 00:32:19.580 --> 00:32:23.470 align:start position:0% blog that has a little bit of Technology in<00:32:19.880> UX<00:32:20.240> and<00:32:20.450> UI<00:32:20.740> it's<00:32:21.740> probably<00:32:22.730> cannot<00:32:23.059> bury 00:32:23.470 --> 00:32:23.480 align:start position:0% in UX and UI it's probably cannot bury 00:32:23.480 --> 00:32:24.940 align:start position:0% in UX and UI it's probably cannot bury the<00:32:23.720> weight<00:32:23.899> of<00:32:24.140> your<00:32:24.260> construction<00:32:24.590> by 00:32:24.940 --> 00:32:24.950 align:start position:0% the weight of your construction by 00:32:24.950 --> 00:32:27.639 align:start position:0% the weight of your construction by itself<00:32:25.340> but<00:32:25.730> we<00:32:25.909> think<00:32:26.120> that<00:32:26.270> in<00:32:26.750> the<00:32:26.929> you<00:32:27.559> will 00:32:27.639 --> 00:32:27.649 align:start position:0% itself but we think that in the you will 00:32:27.649 --> 00:32:30.610 align:start position:0% itself but we think that in the you will find<00:32:27.710> this<00:32:28.279> component<00:32:28.940> in<00:32:29.179> a<00:32:29.690> lot<00:32:29.929> of<00:32:30.140> projects 00:32:30.610 --> 00:32:30.620 align:start position:0% find this component in a lot of projects 00:32:30.620 --> 00:32:31.360 align:start position:0% find this component in a lot of projects in<00:32:30.710> the<00:32:30.860> future 00:32:31.360 --> 00:32:31.370 align:start position:0% in the future 00:32:31.370 --> 00:32:40.570 align:start position:0% in the future welcome<00:32:32.330> and<00:32:32.510> congrats<00:32:33.380> thank<00:32:33.970> you<00:32:39.580> very 00:32:40.570 --> 00:32:40.580 align:start position:0% welcome and congrats thank you very 00:32:40.580 --> 00:32:42.909 align:start position:0% welcome and congrats thank you very great<00:32:40.909> videos<00:32:41.360> run<00:32:41.779> hi<00:32:42.110> I'm<00:32:42.440> Michael<00:32:42.830> from 00:32:42.909 --> 00:32:42.919 align:start position:0% great videos run hi I'm Michael from 00:32:42.919 --> 00:32:44.680 align:start position:0% great videos run hi I'm Michael from three<00:32:43.159> bucks<00:32:43.340> at<00:32:43.970> three<00:32:44.240> bucks<00:32:44.390> it's<00:32:44.570> our 00:32:44.680 --> 00:32:44.690 align:start position:0% three bucks at three bucks it's our 00:32:44.690 --> 00:32:46.269 align:start position:0% three bucks at three bucks it's our mission<00:32:44.960> to<00:32:45.020> make<00:32:45.080> it<00:32:45.289> really<00:32:45.559> easy<00:32:45.590> to<00:32:46.100> build 00:32:46.269 --> 00:32:46.279 align:start position:0% mission to make it really easy to build 00:32:46.279 --> 00:32:50.080 align:start position:0% mission to make it really easy to build better<00:32:46.520> apps<00:32:47.860> personally<00:32:48.860> like<00:32:49.250> we've<00:32:49.640> been 00:32:50.080 --> 00:32:50.090 align:start position:0% better apps personally like we've been 00:32:50.090 --> 00:32:51.190 align:start position:0% better apps personally like we've been around<00:32:50.179> the<00:32:50.450> space<00:32:50.659> for<00:32:50.899> a<00:32:50.929> while 00:32:51.190 --> 00:32:51.200 align:start position:0% around the space for a while 00:32:51.200 --> 00:32:54.480 align:start position:0% around the space for a while and<00:32:51.700> just<00:32:52.700> got<00:32:52.850> tired<00:32:53.240> of<00:32:53.419> seeing<00:32:53.659> gaps<00:32:54.020> be 00:32:54.480 --> 00:32:54.490 align:start position:0% and just got tired of seeing gaps be 00:32:54.490 --> 00:32:57.399 align:start position:0% and just got tired of seeing gaps be limited<00:32:55.490> to<00:32:55.520> buy<00:32:55.760> sell<00:32:56.000> transfer<00:32:56.450> and<00:32:56.720> limited 00:32:57.399 --> 00:32:57.409 align:start position:0% limited to buy sell transfer and limited 00:32:57.409 --> 00:32:59.830 align:start position:0% limited to buy sell transfer and limited only<00:32:57.529> down<00:32:57.799> chain<00:32:58.070> interactions<00:32:58.640> and<00:32:58.850> so<00:32:58.909> we 00:32:59.830 --> 00:32:59.840 align:start position:0% only down chain interactions and so we 00:32:59.840 --> 00:33:00.820 align:start position:0% only down chain interactions and so we saw<00:33:00.020> that<00:33:00.049> there<00:33:00.260> was<00:33:00.350> a<00:33:00.380> huge<00:33:00.559> opportunity 00:33:00.820 --> 00:33:00.830 align:start position:0% saw that there was a huge opportunity 00:33:00.830 --> 00:33:04.930 align:start position:0% saw that there was a huge opportunity for<00:33:01.159> making<00:33:01.970> more<00:33:02.289> interactive<00:33:03.940> applications 00:33:04.930 --> 00:33:04.940 align:start position:0% for making more interactive applications 00:33:04.940 --> 00:33:07.659 align:start position:0% for making more interactive applications with<00:33:05.210> real-time<00:33:05.419> data<00:33:06.010> that<00:33:07.010> lives<00:33:07.159> off<00:33:07.399> chain 00:33:07.659 --> 00:33:07.669 align:start position:0% with real-time data that lives off chain 00:33:07.669 --> 00:33:10.060 align:start position:0% with real-time data that lives off chain on<00:33:07.970> ipfs<00:33:08.750> and<00:33:08.960> in<00:33:09.020> distributed<00:33:09.470> networks<00:33:09.770> and 00:33:10.060 --> 00:33:10.070 align:start position:0% on ipfs and in distributed networks and 00:33:10.070 --> 00:33:12.460 align:start position:0% on ipfs and in distributed networks and so<00:33:10.250> at<00:33:10.940> three<00:33:11.149> bucks<00:33:11.299> we<00:33:11.510> we<00:33:11.960> built<00:33:12.110> a<00:33:12.289> system 00:33:12.460 --> 00:33:12.470 align:start position:0% so at three bucks we we built a system 00:33:12.470 --> 00:33:14.680 align:start position:0% so at three bucks we we built a system that<00:33:12.770> enables<00:33:13.190> devs<00:33:13.669> to<00:33:14.000> make<00:33:14.149> better<00:33:14.390> use<00:33:14.659> of 00:33:14.680 --> 00:33:14.690 align:start position:0% that enables devs to make better use of 00:33:14.690 --> 00:33:17.139 align:start position:0% that enables devs to make better use of these<00:33:15.020> p2p<00:33:15.860> technologies<00:33:16.429> to<00:33:16.640> manage<00:33:16.909> the 00:33:17.139 --> 00:33:17.149 align:start position:0% these p2p technologies to manage the 00:33:17.149 --> 00:33:19.480 align:start position:0% these p2p technologies to manage the data<00:33:17.390> for<00:33:17.630> their<00:33:17.750> application<00:33:18.289> and<00:33:19.039> what<00:33:19.399> you 00:33:19.480 --> 00:33:19.490 align:start position:0% data for their application and what you 00:33:19.490 --> 00:33:21.450 align:start position:0% data for their application and what you see<00:33:19.610> here<00:33:19.850> is<00:33:19.970> a<00:33:20.179> comments<00:33:20.690> component<00:33:21.169> like 00:33:21.450 --> 00:33:21.460 align:start position:0% see here is a comments component like 00:33:21.460 --> 00:33:24.700 align:start position:0% see here is a comments component like Ola<00:33:22.460> said<00:33:22.640> it's<00:33:22.940> the<00:33:23.809> goal<00:33:23.960> here<00:33:24.200> was<00:33:24.320> to<00:33:24.380> make 00:33:24.700 --> 00:33:24.710 align:start position:0% Ola said it's the goal here was to make 00:33:24.710 --> 00:33:27.639 align:start position:0% Ola said it's the goal here was to make it<00:33:24.740> as<00:33:25.039> easy<00:33:25.309> as<00:33:25.429> possible<00:33:25.700> to<00:33:26.120> add<00:33:26.809> discuss 00:33:27.639 --> 00:33:27.649 align:start position:0% it as easy as possible to add discuss 00:33:27.649 --> 00:33:29.260 align:start position:0% it as easy as possible to add discuss like<00:33:27.890> functionality<00:33:28.490> to<00:33:28.610> your<00:33:28.669> application 00:33:29.260 --> 00:33:29.270 align:start position:0% like functionality to your application 00:33:29.270 --> 00:33:32.409 align:start position:0% like functionality to your application and<00:33:29.450> you<00:33:30.440> can<00:33:30.470> drop<00:33:30.679> this<00:33:30.860> anywhere<00:33:31.419> like 00:33:32.409 --> 00:33:32.419 align:start position:0% and you can drop this anywhere like 00:33:32.419 --> 00:33:35.500 align:start position:0% and you can drop this anywhere like basically<00:33:33.140> on<00:33:33.380> any<00:33:34.039> website<00:33:34.580> that<00:33:34.610> has<00:33:34.970> web<00:33:35.240> 3 00:33:35.500 --> 00:33:35.510 align:start position:0% basically on any website that has web 3 00:33:35.510 --> 00:33:37.269 align:start position:0% basically on any website that has web 3 and<00:33:35.750> some<00:33:36.380> of<00:33:36.470> the<00:33:36.529> cool<00:33:36.679> things<00:33:36.710> that<00:33:36.980> we<00:33:37.130> did 00:33:37.269 --> 00:33:37.279 align:start position:0% and some of the cool things that we did 00:33:37.279 --> 00:33:39.310 align:start position:0% and some of the cool things that we did with<00:33:37.399> it<00:33:37.580> we're<00:33:37.870> trying<00:33:38.870> to<00:33:38.960> think<00:33:38.990> of<00:33:39.169> how<00:33:39.260> we 00:33:39.310 --> 00:33:39.320 align:start position:0% with it we're trying to think of how we 00:33:39.320 --> 00:33:41.649 align:start position:0% with it we're trying to think of how we can<00:33:39.500> handle<00:33:39.919> authentication<00:33:40.399> and<00:33:41.029> how<00:33:41.539> do<00:33:41.600> you 00:33:41.649 --> 00:33:41.659 align:start position:0% can handle authentication and how do you 00:33:41.659 --> 00:33:43.750 align:start position:0% can handle authentication and how do you pass<00:33:41.870> the<00:33:42.049> web<00:33:42.200> 3<00:33:42.409> provider<00:33:42.740> to<00:33:43.190> the<00:33:43.220> component 00:33:43.750 --> 00:33:43.760 align:start position:0% pass the web 3 provider to the component 00:33:43.760 --> 00:33:46.419 align:start position:0% pass the web 3 provider to the component and<00:33:43.909> so<00:33:44.679> there<00:33:45.679> are<00:33:45.770> three<00:33:45.980> options<00:33:46.340> here 00:33:46.419 --> 00:33:46.429 align:start position:0% and so there are three options here 00:33:46.429 --> 00:33:48.639 align:start position:0% and so there are three options here which<00:33:46.730> I<00:33:46.850> think<00:33:47.320> we're<00:33:48.320> probably<00:33:48.409> running 00:33:48.639 --> 00:33:48.649 align:start position:0% which I think we're probably running 00:33:48.649 --> 00:33:50.889 align:start position:0% which I think we're probably running through<00:33:48.919> in<00:33:48.980> the<00:33:49.039> video<00:33:49.250> but<00:33:49.659> yeah<00:33:50.659> you<00:33:50.720> can 00:33:50.889 --> 00:33:50.899 align:start position:0% through in the video but yeah you can 00:33:50.899 --> 00:33:52.850 align:start position:0% through in the video but yeah you can log<00:33:51.080> in<00:33:51.230> directly<00:33:51.350> to<00:33:51.649> the<00:33:51.860> component<00:33:52.340> so<00:33:52.460> the 00:33:52.850 --> 00:33:52.860 align:start position:0% log in directly to the component so the 00:33:52.860 --> 00:33:54.530 align:start position:0% log in directly to the component so the application<00:33:53.309> itself<00:33:53.790> on<00:33:53.940> a<00:33:53.970> global<00:33:54.360> state 00:33:54.530 --> 00:33:54.540 align:start position:0% application itself on a global state 00:33:54.540 --> 00:33:57.520 align:start position:0% application itself on a global state doesn't<00:33:54.780> need<00:33:54.960> to<00:33:55.049> handle<00:33:55.410> the<00:33:56.040> provider<00:33:56.420> the 00:33:57.520 --> 00:33:57.530 align:start position:0% doesn't need to handle the provider the 00:33:57.530 --> 00:34:00.650 align:start position:0% doesn't need to handle the provider the component<00:33:58.530> can<00:33:58.799> accept<00:33:59.370> the<00:33:59.700> provider<00:34:00.240> from 00:34:00.650 --> 00:34:00.660 align:start position:0% component can accept the provider from 00:34:00.660 --> 00:34:03.110 align:start position:0% component can accept the provider from the<00:34:00.900> global<00:34:01.170> application<00:34:01.650> state<00:34:01.860> and<00:34:02.730> you<00:34:03.000> can 00:34:03.110 --> 00:34:03.120 align:start position:0% the global application state and you can 00:34:03.120 --> 00:34:04.640 align:start position:0% the global application state and you can do<00:34:03.240> that<00:34:03.360> in<00:34:03.510> two<00:34:03.660> ways<00:34:03.809> like<00:34:04.110> one<00:34:04.350> when<00:34:04.559> the 00:34:04.640 --> 00:34:04.650 align:start position:0% do that in two ways like one when the 00:34:04.650 --> 00:34:06.380 align:start position:0% do that in two ways like one when the unit<00:34:04.950> when<00:34:05.130> the<00:34:05.250> user<00:34:05.429> first<00:34:05.730> on<00:34:05.970> boards<00:34:06.270> to 00:34:06.380 --> 00:34:06.390 align:start position:0% unit when the user first on boards to 00:34:06.390 --> 00:34:08.810 align:start position:0% unit when the user first on boards to your<00:34:06.510> site<00:34:06.740> you<00:34:07.740> can<00:34:07.860> authenticate<00:34:08.070> them<00:34:08.490> to 00:34:08.810 --> 00:34:08.820 align:start position:0% your site you can authenticate them to 00:34:08.820 --> 00:34:10.430 align:start position:0% your site you can authenticate them to three<00:34:09.030> box<00:34:09.210> and<00:34:09.480> what<00:34:09.750> that<00:34:09.869> does<00:34:10.080> is<00:34:10.260> it 00:34:10.430 --> 00:34:10.440 align:start position:0% three box and what that does is it 00:34:10.440 --> 00:34:13.250 align:start position:0% three box and what that does is it actually<00:34:10.830> opens<00:34:11.399> up<00:34:11.550> a<00:34:11.730> local<00:34:12.300> IP<00:34:12.629> FS<00:34:13.020> and 00:34:13.250 --> 00:34:13.260 align:start position:0% actually opens up a local IP FS and 00:34:13.260 --> 00:34:15.800 align:start position:0% actually opens up a local IP FS and Orbitz<00:34:13.679> DB<00:34:13.919> node<00:34:14.129> right<00:34:14.340> in<00:34:14.460> the<00:34:14.550> browser<00:34:14.810> and 00:34:15.800 --> 00:34:15.810 align:start position:0% Orbitz DB node right in the browser and 00:34:15.810 --> 00:34:17.300 align:start position:0% Orbitz DB node right in the browser and syncs<00:34:16.230> out<00:34:16.379> and<00:34:16.619> collects<00:34:16.830> data<00:34:16.980> from<00:34:17.100> the 00:34:17.300 --> 00:34:17.310 align:start position:0% syncs out and collects data from the 00:34:17.310 --> 00:34:19.609 align:start position:0% syncs out and collects data from the rest<00:34:17.460> of<00:34:17.550> the<00:34:17.609> network<00:34:17.850> so<00:34:18.050> it's<00:34:19.050> local<00:34:19.260> first 00:34:19.609 --> 00:34:19.619 align:start position:0% rest of the network so it's local first 00:34:19.619 --> 00:34:22.460 align:start position:0% rest of the network so it's local first it<00:34:20.159> can<00:34:20.280> run<00:34:20.399> offline<00:34:20.639> and<00:34:21.230> just<00:34:22.230> makes<00:34:22.409> it 00:34:22.460 --> 00:34:22.470 align:start position:0% it can run offline and just makes it 00:34:22.470 --> 00:34:23.810 align:start position:0% it can run offline and just makes it super<00:34:22.619> simple<00:34:22.859> to<00:34:23.040> get<00:34:23.159> started<00:34:23.220> like<00:34:23.609> there's 00:34:23.810 --> 00:34:23.820 align:start position:0% super simple to get started like there's 00:34:23.820 --> 00:34:25.099 align:start position:0% super simple to get started like there's no<00:34:23.970> extensions<00:34:24.540> that<00:34:24.659> users<00:34:24.929> have<00:34:25.080> to 00:34:25.099 --> 00:34:25.109 align:start position:0% no extensions that users have to 00:34:25.109 --> 00:34:28.520 align:start position:0% no extensions that users have to download<00:34:25.379> or<00:34:25.740> plug<00:34:25.919> in<00:34:26.129> it<00:34:27.090> just<00:34:27.450> runs<00:34:27.750> and<00:34:28.020> so 00:34:28.520 --> 00:34:28.530 align:start position:0% download or plug in it just runs and so 00:34:28.530 --> 00:34:30.619 align:start position:0% download or plug in it just runs and so you<00:34:29.429> can<00:34:29.580> see<00:34:29.700> that<00:34:29.790> there's<00:34:29.940> also<00:34:30.090> profiles 00:34:30.619 --> 00:34:30.629 align:start position:0% you can see that there's also profiles 00:34:30.629 --> 00:34:33.320 align:start position:0% you can see that there's also profiles on<00:34:30.840> here<00:34:31.080> so<00:34:31.639> outside<00:34:32.639> of<00:34:32.820> the<00:34:32.940> comments 00:34:33.320 --> 00:34:33.330 align:start position:0% on here so outside of the comments 00:34:33.330 --> 00:34:35.780 align:start position:0% on here so outside of the comments component<00:34:33.780> three<00:34:34.020> box<00:34:34.200> offers<00:34:34.830> three<00:34:35.340> box<00:34:35.520> j/s 00:34:35.780 --> 00:34:35.790 align:start position:0% component three box offers three box j/s 00:34:35.790 --> 00:34:39.260 align:start position:0% component three box offers three box j/s SDK<00:34:36.300> which<00:34:37.169> makes<00:34:37.470> it<00:34:37.590> really<00:34:37.619> easy<00:34:37.830> to<00:34:38.270> it 00:34:39.260 --> 00:34:39.270 align:start position:0% SDK which makes it really easy to it 00:34:39.270 --> 00:34:40.879 align:start position:0% SDK which makes it really easy to it provides<00:34:39.600> a<00:34:39.659> developer<00:34:40.020> interface<00:34:40.379> to<00:34:40.619> add 00:34:40.879 --> 00:34:40.889 align:start position:0% provides a developer interface to add 00:34:40.889 --> 00:34:43.609 align:start position:0% provides a developer interface to add profiles<00:34:41.869> distributed<00:34:42.869> storage<00:34:43.080> and 00:34:43.609 --> 00:34:43.619 align:start position:0% profiles distributed storage and 00:34:43.619 --> 00:34:45.169 align:start position:0% profiles distributed storage and messaging<00:34:44.250> to<00:34:44.340> your<00:34:44.460> application<00:34:44.940> and<00:34:45.090> so 00:34:45.169 --> 00:34:45.179 align:start position:0% messaging to your application and so 00:34:45.179 --> 00:34:48.080 align:start position:0% messaging to your application and so this<00:34:45.810> uses<00:34:46.200> specifically<00:34:46.800> the<00:34:47.399> profiles<00:34:47.820> and 00:34:48.080 --> 00:34:48.090 align:start position:0% this uses specifically the profiles and 00:34:48.090 --> 00:34:50.780 align:start position:0% this uses specifically the profiles and the<00:34:48.210> messaging<00:34:48.629> api's<00:34:49.220> and<00:34:50.220> so<00:34:50.369> this<00:34:50.490> actually 00:34:50.780 --> 00:34:50.790 align:start position:0% the messaging api's and so this actually 00:34:50.790 --> 00:34:54.349 align:start position:0% the messaging api's and so this actually wraps<00:34:51.000> our<00:34:51.210> three<00:34:51.389> bucks<00:34:51.600> SDK<00:34:52.700> and<00:34:53.700> also 00:34:54.349 --> 00:34:54.359 align:start position:0% wraps our three bucks SDK and also 00:34:54.359 --> 00:34:56.270 align:start position:0% wraps our three bucks SDK and also what's<00:34:54.540> cool<00:34:54.750> here<00:34:54.780> are<00:34:55.200> we<00:34:55.830> use<00:34:55.950> aetherium 00:34:56.270 --> 00:34:56.280 align:start position:0% what's cool here are we use aetherium 00:34:56.280 --> 00:34:58.940 align:start position:0% what's cool here are we use aetherium keys<00:34:56.639> for<00:34:56.850> authentication<00:34:57.090> and<00:34:57.570> signing<00:34:57.950> but 00:34:58.940 --> 00:34:58.950 align:start position:0% keys for authentication and signing but 00:34:58.950 --> 00:35:01.880 align:start position:0% keys for authentication and signing but we<00:34:59.460> have<00:34:59.640> a<00:34:59.670> did<00:35:00.510> method<00:35:00.930> decentralize 00:35:01.880 --> 00:35:01.890 align:start position:0% we have a did method decentralize 00:35:01.890 --> 00:35:03.470 align:start position:0% we have a did method decentralize identify<00:35:02.340> our<00:35:02.460> method<00:35:02.730> under<00:35:02.970> the<00:35:03.060> hood<00:35:03.210> and 00:35:03.470 --> 00:35:03.480 align:start position:0% identify our method under the hood and 00:35:03.480 --> 00:35:06.849 align:start position:0% identify our method under the hood and so<00:35:04.109> in<00:35:05.010> the<00:35:05.220> future<00:35:05.430> we<00:35:05.940> can<00:35:06.090> extend<00:35:06.390> this<00:35:06.630> to 00:35:06.849 --> 00:35:06.859 align:start position:0% so in the future we can extend this to 00:35:06.859 --> 00:35:09.440 align:start position:0% so in the future we can extend this to all<00:35:07.859> the<00:35:08.160> different<00:35:08.520> aetherium<00:35:09.090> keys<00:35:09.300> that 00:35:09.440 --> 00:35:09.450 align:start position:0% all the different aetherium keys that 00:35:09.450 --> 00:35:10.609 align:start position:0% all the different aetherium keys that you<00:35:09.540> have<00:35:09.690> across<00:35:09.930> all<00:35:10.140> of<00:35:10.260> your<00:35:10.350> different 00:35:10.609 --> 00:35:10.619 align:start position:0% you have across all of your different 00:35:10.619 --> 00:35:12.050 align:start position:0% you have across all of your different wallets<00:35:10.980> while<00:35:11.430> maintaining<00:35:11.670> the<00:35:12.030> same 00:35:12.050 --> 00:35:12.060 align:start position:0% wallets while maintaining the same 00:35:12.060 --> 00:35:14.270 align:start position:0% wallets while maintaining the same profile<00:35:12.630> on<00:35:12.750> the<00:35:12.840> same<00:35:12.990> data<00:35:13.230> and<00:35:13.650> then<00:35:14.040> taking 00:35:14.270 --> 00:35:14.280 align:start position:0% profile on the same data and then taking 00:35:14.280 --> 00:35:16.130 align:start position:0% profile on the same data and then taking that<00:35:14.369> a<00:35:14.400> step<00:35:14.460> further<00:35:14.640> you<00:35:15.210> can<00:35:15.720> also<00:35:15.869> think 00:35:16.130 --> 00:35:16.140 align:start position:0% that a step further you can also think 00:35:16.140 --> 00:35:18.050 align:start position:0% that a step further you can also think about<00:35:16.350> extending<00:35:16.530> that<00:35:16.830> to<00:35:16.980> other<00:35:17.340> chains<00:35:17.760> and 00:35:18.050 --> 00:35:18.060 align:start position:0% about extending that to other chains and 00:35:18.060 --> 00:35:20.270 align:start position:0% about extending that to other chains and other<00:35:18.150> shards<00:35:18.660> and<00:35:18.869> you<00:35:19.530> know<00:35:19.619> even<00:35:19.800> web<00:35:20.070> to 00:35:20.270 --> 00:35:20.280 align:start position:0% other shards and you know even web to 00:35:20.280 --> 00:35:22.880 align:start position:0% other shards and you know even web to authentication<00:35:20.580> methods<00:35:21.180> as<00:35:21.270> well<00:35:21.650> so<00:35:22.650> the 00:35:22.880 --> 00:35:22.890 align:start position:0% authentication methods as well so the 00:35:22.890 --> 00:35:24.770 align:start position:0% authentication methods as well so the goal<00:35:23.040> is<00:35:23.190> always<00:35:23.369> to<00:35:23.460> have<00:35:23.580> data<00:35:24.270> follow<00:35:24.600> you 00:35:24.770 --> 00:35:24.780 align:start position:0% goal is always to have data follow you 00:35:24.780 --> 00:35:26.750 align:start position:0% goal is always to have data follow you around<00:35:24.900> the<00:35:25.170> web<00:35:25.320> and<00:35:25.680> not<00:35:26.070> be<00:35:26.220> trapped<00:35:26.490> in<00:35:26.640> any 00:35:26.750 --> 00:35:26.760 align:start position:0% around the web and not be trapped in any 00:35:26.760 --> 00:35:29.210 align:start position:0% around the web and not be trapped in any sort<00:35:27.000> of<00:35:27.090> centralized<00:35:27.540> silo<00:35:27.840> or<00:35:27.869> service<00:35:28.320> and 00:35:29.210 --> 00:35:29.220 align:start position:0% sort of centralized silo or service and 00:35:29.220 --> 00:35:31.130 align:start position:0% sort of centralized silo or service and three<00:35:29.609> box<00:35:29.790> actually<00:35:30.030> lets<00:35:30.450> you<00:35:30.510> do<00:35:30.690> that<00:35:30.869> in<00:35:31.050> a 00:35:31.130 --> 00:35:31.140 align:start position:0% three box actually lets you do that in a 00:35:31.140 --> 00:35:33.920 align:start position:0% three box actually lets you do that in a real<00:35:31.350> way<00:35:31.560> that's<00:35:32.100> simple<00:35:32.460> and<00:35:32.580> so<00:35:33.090> I'm 00:35:33.920 --> 00:35:33.930 align:start position:0% real way that's simple and so I'm 00:35:33.930 --> 00:35:35.750 align:start position:0% real way that's simple and so I'm excited<00:35:34.200> that<00:35:34.380> you're<00:35:35.100> excited<00:35:35.369> about<00:35:35.550> the 00:35:35.750 --> 00:35:35.760 align:start position:0% excited that you're excited about the 00:35:35.760 --> 00:35:37.359 align:start position:0% excited that you're excited about the Commons<00:35:36.060> component<00:35:36.540> we<00:35:36.660> really<00:35:36.869> hope<00:35:37.050> that 00:35:37.359 --> 00:35:37.369 align:start position:0% Commons component we really hope that 00:35:37.369 --> 00:35:41.000 align:start position:0% Commons component we really hope that this<00:35:38.369> is<00:35:38.430> a<00:35:38.820> useful<00:35:39.000> tool<00:35:39.330> and<00:35:39.740> we're<00:35:40.740> making 00:35:41.000 --> 00:35:41.010 align:start position:0% this is a useful tool and we're making 00:35:41.010 --> 00:35:42.859 align:start position:0% this is a useful tool and we're making other<00:35:41.220> plugins<00:35:41.760> so<00:35:41.970> this<00:35:42.090> isn't<00:35:42.359> the<00:35:42.450> only<00:35:42.570> one 00:35:42.859 --> 00:35:42.869 align:start position:0% other plugins so this isn't the only one 00:35:42.869 --> 00:35:45.770 align:start position:0% other plugins so this isn't the only one we<00:35:43.530> have<00:35:43.560> a<00:35:43.710> profile<00:35:44.220> hovers<00:35:44.520> plugin<00:35:45.030> which<00:35:45.630> if 00:35:45.770 --> 00:35:45.780 align:start position:0% we have a profile hovers plugin which if 00:35:45.780 --> 00:35:47.300 align:start position:0% we have a profile hovers plugin which if you<00:35:45.900> hover<00:35:46.080> over<00:35:46.500> these<00:35:46.650> profiles<00:35:47.100> here 00:35:47.300 --> 00:35:47.310 align:start position:0% you hover over these profiles here 00:35:47.310 --> 00:35:49.160 align:start position:0% you hover over these profiles here you'll<00:35:47.460> see<00:35:47.609> like<00:35:47.730> a<00:35:47.790> little<00:35:47.970> modal<00:35:48.810> that<00:35:48.960> pops 00:35:49.160 --> 00:35:49.170 align:start position:0% you'll see like a little modal that pops 00:35:49.170 --> 00:35:50.630 align:start position:0% you'll see like a little modal that pops up<00:35:49.320> kind<00:35:49.590> of<00:35:49.619> like<00:35:49.770> Twitter<00:35:50.010> that<00:35:50.220> shows<00:35:50.430> you 00:35:50.630 --> 00:35:50.640 align:start position:0% up kind of like Twitter that shows you 00:35:50.640 --> 00:35:54.050 align:start position:0% up kind of like Twitter that shows you additional<00:35:51.030> profile<00:35:51.359> metadata<00:35:52.010> and<00:35:53.010> in<00:35:53.670> a 00:35:54.050 --> 00:35:54.060 align:start position:0% additional profile metadata and in a 00:35:54.060 --> 00:35:56.359 align:start position:0% additional profile metadata and in a week<00:35:54.330> or<00:35:54.450> two<00:35:54.660> we'll<00:35:55.350> be<00:35:55.500> releasing<00:35:55.770> a<00:35:56.160> chat 00:35:56.359 --> 00:35:56.369 align:start position:0% week or two we'll be releasing a chat 00:35:56.369 --> 00:35:58.730 align:start position:0% week or two we'll be releasing a chat box<00:35:56.550> component<00:35:57.000> plug-in<00:35:57.990> and<00:35:58.200> that<00:35:58.530> really 00:35:58.730 --> 00:35:58.740 align:start position:0% box component plug-in and that really 00:35:58.740 --> 00:36:00.920 align:start position:0% box component plug-in and that really lets<00:35:58.950> you<00:35:59.040> add<00:35:59.190> like<00:35:59.400> a<00:35:59.430> global<00:35:59.790> site<00:36:00.750> wide 00:36:00.920 --> 00:36:00.930 align:start position:0% lets you add like a global site wide 00:36:00.930 --> 00:36:02.990 align:start position:0% lets you add like a global site wide chat<00:36:01.320> a<00:36:01.590> control<00:36:02.040> box<00:36:02.250> to<00:36:02.430> the<00:36:02.520> corner<00:36:02.760> of<00:36:02.850> your 00:36:02.990 --> 00:36:03.000 align:start position:0% chat a control box to the corner of your 00:36:03.000 --> 00:36:05.070 align:start position:0% chat a control box to the corner of your site<00:36:03.210> all<00:36:03.660> built<00:36:04.140> on<00:36:04.230> p2p 00:36:05.070 --> 00:36:05.080 align:start position:0% site all built on p2p 00:36:05.080 --> 00:36:08.310 align:start position:0% site all built on p2p using<00:36:05.410> our<00:36:05.470> profiles<00:36:05.920> and<00:36:06.190> api's<00:36:06.870> so<00:36:07.870> super 00:36:08.310 --> 00:36:08.320 align:start position:0% using our profiles and api's so super 00:36:08.320 --> 00:36:11.220 align:start position:0% using our profiles and api's so super excited<00:36:08.410> thank<00:36:09.280> you<00:36:09.490> and<00:36:10.450> look<00:36:10.960> forward<00:36:11.140> to 00:36:11.220 --> 00:36:11.230 align:start position:0% excited thank you and look forward to 00:36:11.230 --> 00:36:22.680 align:start position:0% excited thank you and look forward to chatting<00:36:11.470> with<00:36:11.680> all<00:36:11.800> of<00:36:11.890> you<00:36:20.520> and<00:36:21.520> next<00:36:22.450> we 00:36:22.680 --> 00:36:22.690 align:start position:0% chatting with all of you and next we 00:36:22.690 --> 00:36:25.790 align:start position:0% chatting with all of you and next we have<00:36:22.720> any<00:36:23.050> introducing<00:36:23.710> Zairian<00:36:24.160> all<00:36:24.700> right 00:36:25.790 --> 00:36:25.800 align:start position:0% have any introducing Zairian all right 00:36:25.800 --> 00:36:29.880 align:start position:0% have any introducing Zairian all right who<00:36:26.800> here<00:36:27.190> has<00:36:27.840> created<00:36:28.840> a<00:36:28.930> CDP<00:36:29.500> raise<00:36:29.740> of 00:36:29.880 --> 00:36:29.890 align:start position:0% who here has created a CDP raise of 00:36:29.890 --> 00:36:36.990 align:start position:0% who here has created a CDP raise of hands<00:36:31.050> okay<00:36:32.070> cool<00:36:33.420> defy<00:36:34.420> is<00:36:34.840> the<00:36:35.200> future<00:36:36.000> but 00:36:36.990 --> 00:36:37.000 align:start position:0% hands okay cool defy is the future but 00:36:37.000 --> 00:36:38.760 align:start position:0% hands okay cool defy is the future but it's<00:36:37.150> complicated<00:36:37.540> because<00:36:38.080> you<00:36:38.290> have<00:36:38.440> to 00:36:38.760 --> 00:36:38.770 align:start position:0% it's complicated because you have to 00:36:38.770 --> 00:36:40.860 align:start position:0% it's complicated because you have to create<00:36:38.980> go<00:36:39.520> over<00:36:39.700> here<00:36:39.910> for<00:36:40.120> a<00:36:40.180> compound<00:36:40.600> loan 00:36:40.860 --> 00:36:40.870 align:start position:0% create go over here for a compound loan 00:36:40.870 --> 00:36:43.830 align:start position:0% create go over here for a compound loan you<00:36:41.110> go<00:36:41.230> over<00:36:41.380> here<00:36:41.560> for<00:36:41.830> a<00:36:41.860> CDP<00:36:42.690> so<00:36:43.690> we're 00:36:43.830 --> 00:36:43.840 align:start position:0% you go over here for a CDP so we're 00:36:43.840 --> 00:36:46.170 align:start position:0% you go over here for a CDP so we're really<00:36:44.020> excited<00:36:44.110> to<00:36:44.650> announce<00:36:44.890> the<00:36:45.370> final 00:36:46.170 --> 00:36:46.180 align:start position:0% really excited to announce the final 00:36:46.180 --> 00:36:48.210 align:start position:0% really excited to announce the final winner<00:36:46.360> which<00:36:46.630> is<00:36:46.780> zero<00:36:47.020> on<00:36:47.230> they've<00:36:47.980> done 00:36:48.210 --> 00:36:48.220 align:start position:0% winner which is zero on they've done 00:36:48.220 --> 00:36:50.700 align:start position:0% winner which is zero on they've done great<00:36:48.520> job<00:36:48.550> in<00:36:49.090> making<00:36:49.780> it<00:36:50.080> extremely<00:36:50.500> easy 00:36:50.700 --> 00:36:50.710 align:start position:0% great job in making it extremely easy 00:36:50.710 --> 00:36:53.460 align:start position:0% great job in making it extremely easy for<00:36:51.430> you<00:36:51.550> to<00:36:51.760> create<00:36:52.270> an<00:36:52.420> account<00:36:52.690> and<00:36:53.050> go<00:36:53.440> to 00:36:53.460 --> 00:36:53.470 align:start position:0% for you to create an account and go to 00:36:53.470 --> 00:36:56.280 align:start position:0% for you to create an account and go to all<00:36:53.770> these<00:36:54.010> different<00:36:54.070> defy<00:36:54.700> services<00:36:55.290> so 00:36:56.280 --> 00:36:56.290 align:start position:0% all these different defy services so 00:36:56.290 --> 00:36:57.720 align:start position:0% all these different defy services so we're<00:36:56.440> really<00:36:56.620> excited<00:36:56.980> for<00:36:57.160> them<00:36:57.340> to<00:36:57.520> be<00:36:57.640> the 00:36:57.720 --> 00:36:57.730 align:start position:0% we're really excited for them to be the 00:36:57.730 --> 00:37:03.350 align:start position:0% we're really excited for them to be the winner<00:37:00.270> thank<00:37:01.270> you<00:37:01.390> thank<00:37:01.630> you<00:37:01.720> Vinnie 00:37:03.350 --> 00:37:03.360 align:start position:0% winner thank you thank you Vinnie 00:37:03.360 --> 00:37:06.840 align:start position:0% winner thank you thank you Vinnie hello<00:37:04.630> it's<00:37:05.050> really<00:37:05.920> an<00:37:06.100> honor<00:37:06.220> to<00:37:06.400> be<00:37:06.550> here 00:37:06.840 --> 00:37:06.850 align:start position:0% hello it's really an honor to be here 00:37:06.850 --> 00:37:10.170 align:start position:0% hello it's really an honor to be here and<00:37:07.030> we<00:37:07.510> are<00:37:07.540> super<00:37:07.870> excited<00:37:07.900> about<00:37:08.970> there<00:37:09.970> and 00:37:10.170 --> 00:37:10.180 align:start position:0% and we are super excited about there and 00:37:10.180 --> 00:37:11.970 align:start position:0% and we are super excited about there and to<00:37:10.270> present<00:37:10.540> their<00:37:10.690> into<00:37:10.900> you<00:37:11.020> I'm<00:37:11.800> your 00:37:11.970 --> 00:37:11.980 align:start position:0% to present their into you I'm your 00:37:11.980 --> 00:37:15.660 align:start position:0% to present their into you I'm your guinea<00:37:12.210> and<00:37:13.620> what<00:37:14.620> we<00:37:14.740> believe<00:37:14.860> is<00:37:15.160> aaron<00:37:15.520> is 00:37:15.660 --> 00:37:15.670 align:start position:0% guinea and what we believe is aaron is 00:37:15.670 --> 00:37:17.490 align:start position:0% guinea and what we believe is aaron is actually<00:37:16.030> that<00:37:16.150> users<00:37:16.570> should<00:37:16.600> own<00:37:17.110> and 00:37:17.490 --> 00:37:17.500 align:start position:0% actually that users should own and 00:37:17.500 --> 00:37:19.920 align:start position:0% actually that users should own and control<00:37:17.920> their<00:37:18.190> assets<00:37:18.640> and<00:37:18.820> also<00:37:19.600> we<00:37:19.690> think 00:37:19.920 --> 00:37:19.930 align:start position:0% control their assets and also we think 00:37:19.930 --> 00:37:21.900 align:start position:0% control their assets and also we think that<00:37:20.430> financial<00:37:21.430> access<00:37:21.550> should<00:37:21.850> be 00:37:21.900 --> 00:37:21.910 align:start position:0% that financial access should be 00:37:21.910 --> 00:37:25.620 align:start position:0% that financial access should be universal<00:37:22.360> so<00:37:23.340> given<00:37:24.340> that<00:37:24.370> in<00:37:24.640> mind<00:37:24.820> we<00:37:25.210> we 00:37:25.620 --> 00:37:25.630 align:start position:0% universal so given that in mind we we 00:37:25.630 --> 00:37:27.750 align:start position:0% universal so given that in mind we we have<00:37:25.750> designs<00:37:26.200> there<00:37:26.470> and<00:37:26.680> to<00:37:26.890> be<00:37:27.040> first<00:37:27.550> a 00:37:27.750 --> 00:37:27.760 align:start position:0% have designs there and to be first a 00:37:27.760 --> 00:37:32.340 align:start position:0% have designs there and to be first a noncustodial<00:37:28.800> bank<00:37:29.800> for<00:37:30.160> deep<00:37:30.520> i<00:37:30.700> and<00:37:30.940> ii<00:37:31.630> it 00:37:32.340 --> 00:37:32.350 align:start position:0% noncustodial bank for deep i and ii it 00:37:32.350 --> 00:37:36.570 align:start position:0% noncustodial bank for deep i and ii it allows<00:37:32.620> you<00:37:32.800> to<00:37:34.110> access<00:37:35.110> all<00:37:35.620> different<00:37:36.280> defy 00:37:36.570 --> 00:37:36.580 align:start position:0% allows you to access all different defy 00:37:36.580 --> 00:37:39.570 align:start position:0% allows you to access all different defy protocols<00:37:37.090> in<00:37:37.300> a<00:37:37.870> single<00:37:38.170> place<00:37:38.380> so<00:37:39.160> i'm<00:37:39.370> gonna 00:37:39.570 --> 00:37:39.580 align:start position:0% protocols in a single place so i'm gonna 00:37:39.580 --> 00:37:41.730 align:start position:0% protocols in a single place so i'm gonna show<00:37:39.640> you<00:37:39.820> the<00:37:40.000> demo<00:37:40.840> of<00:37:41.050> how<00:37:41.110> zerrin<00:37:41.530> looks 00:37:41.730 --> 00:37:41.740 align:start position:0% show you the demo of how zerrin looks 00:37:41.740 --> 00:37:43.920 align:start position:0% show you the demo of how zerrin looks just<00:37:42.100> like<00:37:42.250> a<00:37:42.310> typical<00:37:42.790> flow<00:37:43.060> that<00:37:43.540> people 00:37:43.920 --> 00:37:43.930 align:start position:0% just like a typical flow that people 00:37:43.930 --> 00:37:48.270 align:start position:0% just like a typical flow that people will<00:37:44.050> see<00:37:44.260> while<00:37:44.800> using<00:37:45.040> zarion<00:37:46.230> so<00:37:47.230> first<00:37:47.560> you 00:37:48.270 --> 00:37:48.280 align:start position:0% will see while using zarion so first you 00:37:48.280 --> 00:37:50.490 align:start position:0% will see while using zarion so first you you'll<00:37:48.580> need<00:37:48.760> to<00:37:48.880> connect<00:37:49.240> your<00:37:49.330> any<00:37:49.870> of<00:37:50.260> your 00:37:50.490 --> 00:37:50.500 align:start position:0% you'll need to connect your any of your 00:37:50.500 --> 00:37:53.160 align:start position:0% you'll need to connect your any of your wallet<00:37:50.710> we<00:37:50.830> support<00:37:51.220> all<00:37:51.520> boards<00:37:51.970> like<00:37:52.600> mobile 00:37:53.160 --> 00:37:53.170 align:start position:0% wallet we support all boards like mobile 00:37:53.170 --> 00:37:56.220 align:start position:0% wallet we support all boards like mobile wallets<00:37:53.560> and<00:37:53.740> meta<00:37:54.160> mask<00:37:54.400> and<00:37:54.730> ledger<00:37:55.230> then 00:37:56.220 --> 00:37:56.230 align:start position:0% wallets and meta mask and ledger then 00:37:56.230 --> 00:37:58.170 align:start position:0% wallets and meta mask and ledger then you<00:37:56.350> can<00:37:56.530> see<00:37:56.710> all<00:37:57.040> your<00:37:57.340> assets<00:37:57.850> on<00:37:58.030> the 00:37:58.170 --> 00:37:58.180 align:start position:0% you can see all your assets on the 00:37:58.180 --> 00:38:01.190 align:start position:0% you can see all your assets on the account<00:37:58.660> as<00:37:59.290> and<00:37:59.680> the<00:38:00.160> performance<00:38:00.670> over<00:38:00.850> time 00:38:01.190 --> 00:38:01.200 align:start position:0% account as and the performance over time 00:38:01.200 --> 00:38:04.140 align:start position:0% account as and the performance over time we<00:38:02.200> have<00:38:02.380> integration<00:38:03.130> with<00:38:03.280> free<00:38:03.430> box<00:38:03.670> so<00:38:04.090> it 00:38:04.140 --> 00:38:04.150 align:start position:0% we have integration with free box so it 00:38:04.150 --> 00:38:05.880 align:start position:0% we have integration with free box so it shows<00:38:04.390> your<00:38:04.630> free<00:38:05.110> box<00:38:05.290> profile<00:38:05.680> on<00:38:05.800> the<00:38:05.860> top 00:38:05.880 --> 00:38:05.890 align:start position:0% shows your free box profile on the top 00:38:05.890 --> 00:38:09.840 align:start position:0% shows your free box profile on the top and<00:38:07.260> yeah<00:38:08.260> so<00:38:08.500> then<00:38:08.680> you'll<00:38:09.130> be<00:38:09.340> able<00:38:09.490> to<00:38:09.700> see 00:38:09.840 --> 00:38:09.850 align:start position:0% and yeah so then you'll be able to see 00:38:09.850 --> 00:38:12.300 align:start position:0% and yeah so then you'll be able to see all<00:38:10.150> your<00:38:10.390> unit<00:38:10.810> swap<00:38:11.020> pool<00:38:11.560> tokens<00:38:11.980> as<00:38:12.100> well 00:38:12.300 --> 00:38:12.310 align:start position:0% all your unit swap pool tokens as well 00:38:12.310 --> 00:38:15.120 align:start position:0% all your unit swap pool tokens as well and<00:38:13.270> that<00:38:13.630> we<00:38:13.750> even<00:38:13.900> have<00:38:14.140> a<00:38:14.170> mobile<00:38:14.560> app<00:38:14.800> that 00:38:15.120 --> 00:38:15.130 align:start position:0% and that we even have a mobile app that 00:38:15.130 --> 00:38:17.880 align:start position:0% and that we even have a mobile app that allows<00:38:15.490> you<00:38:15.700> to<00:38:15.900> track<00:38:16.900> your<00:38:17.050> portfolio<00:38:17.620> like 00:38:17.880 --> 00:38:17.890 align:start position:0% allows you to track your portfolio like 00:38:17.890 --> 00:38:18.490 align:start position:0% allows you to track your portfolio like your<00:38:18.040> d5 00:38:18.490 --> 00:38:18.500 align:start position:0% your d5 00:38:18.500 --> 00:38:22.089 align:start position:0% your d5 failure<00:38:18.890> on<00:38:19.070> the<00:38:19.220> go<00:38:20.050> next<00:38:21.050> I'm<00:38:21.770> gonna<00:38:22.010> show 00:38:22.089 --> 00:38:22.099 align:start position:0% failure on the go next I'm gonna show 00:38:22.099 --> 00:38:25.359 align:start position:0% failure on the go next I'm gonna show you<00:38:22.340> how<00:38:22.580> you<00:38:22.640> can<00:38:22.970> easily<00:38:23.270> swap<00:38:24.040> one<00:38:25.040> either 00:38:25.359 --> 00:38:25.369 align:start position:0% you how you can easily swap one either 00:38:25.369 --> 00:38:27.250 align:start position:0% you how you can easily swap one either let's<00:38:25.730> say<00:38:25.849> I<00:38:26.090> like<00:38:26.420> to<00:38:26.540> buy<00:38:26.660> a<00:38:26.690> hundred<00:38:27.050> die 00:38:27.250 --> 00:38:27.260 align:start position:0% let's say I like to buy a hundred die 00:38:27.260 --> 00:38:29.740 align:start position:0% let's say I like to buy a hundred die it's<00:38:28.010> through<00:38:28.190> Zarin<00:38:28.550> and<00:38:28.730> you<00:38:29.180> can<00:38:29.330> that 00:38:29.740 --> 00:38:29.750 align:start position:0% it's through Zarin and you can that 00:38:29.750 --> 00:38:32.589 align:start position:0% it's through Zarin and you can that happens<00:38:30.170> through<00:38:30.410> uni<00:38:30.859> swap<00:38:31.099> and<00:38:31.369> and<00:38:32.270> it 00:38:32.589 --> 00:38:32.599 align:start position:0% happens through uni swap and and it 00:38:32.599 --> 00:38:34.630 align:start position:0% happens through uni swap and and it directly<00:38:33.290> goes<00:38:33.380> to<00:38:33.590> the<00:38:33.830> unit<00:38:34.040> swap<00:38:34.190> contract 00:38:34.630 --> 00:38:34.640 align:start position:0% directly goes to the unit swap contract 00:38:34.640 --> 00:38:36.310 align:start position:0% directly goes to the unit swap contract you<00:38:34.820> confirm<00:38:35.180> the<00:38:35.330> transaction<00:38:35.540> in<00:38:35.990> in<00:38:36.200> the 00:38:36.310 --> 00:38:36.320 align:start position:0% you confirm the transaction in in the 00:38:36.320 --> 00:38:38.530 align:start position:0% you confirm the transaction in in the world<00:38:36.500> that<00:38:36.710> you<00:38:36.800> have<00:38:36.830> connected<00:38:37.340> and<00:38:38.300> you 00:38:38.530 --> 00:38:38.540 align:start position:0% world that you have connected and you 00:38:38.540 --> 00:38:41.230 align:start position:0% world that you have connected and you can<00:38:38.720> easily<00:38:39.020> see<00:38:39.500> how<00:38:39.530> I<00:38:40.130> see<00:38:40.730> like<00:38:40.970> right<00:38:41.150> now 00:38:41.230 --> 00:38:41.240 align:start position:0% can easily see how I see like right now 00:38:41.240 --> 00:38:44.859 align:start position:0% can easily see how I see like right now it's<00:38:41.420> pending<00:38:41.840> in<00:38:42.050> the<00:38:42.260> history<00:38:42.619> tab<00:38:43.090> we<00:38:44.090> will 00:38:44.859 --> 00:38:44.869 align:start position:0% it's pending in the history tab we will 00:38:44.869 --> 00:38:46.750 align:start position:0% it's pending in the history tab we will show<00:38:45.140> you<00:38:45.200> all<00:38:45.470> the<00:38:45.500> history<00:38:45.920> in<00:38:46.369> history 00:38:46.750 --> 00:38:46.760 align:start position:0% show you all the history in history 00:38:46.760 --> 00:38:48.580 align:start position:0% show you all the history in history shoulders<00:38:47.390> transactions<00:38:47.990> in<00:38:48.140> a<00:38:48.290> really 00:38:48.580 --> 00:38:48.590 align:start position:0% shoulders transactions in a really 00:38:48.590 --> 00:38:51.339 align:start position:0% shoulders transactions in a really user-friendly<00:38:49.010> form<00:38:49.869> for<00:38:50.869> instance<00:38:50.960> like 00:38:51.339 --> 00:38:51.349 align:start position:0% user-friendly form for instance like 00:38:51.349 --> 00:38:54.099 align:start position:0% user-friendly form for instance like that's<00:38:51.680> adding<00:38:52.460> liquidity<00:38:52.940> to<00:38:53.150> uni<00:38:53.570> swap<00:38:53.810> or 00:38:54.099 --> 00:38:54.109 align:start position:0% that's adding liquidity to uni swap or 00:38:54.109 --> 00:38:56.890 align:start position:0% that's adding liquidity to uni swap or all<00:38:54.920> the<00:38:55.099> trades<00:38:55.369> and<00:38:55.550> like<00:38:55.790> oh<00:38:56.000> you<00:38:56.060> receiving 00:38:56.890 --> 00:38:56.900 align:start position:0% all the trades and like oh you receiving 00:38:56.900 --> 00:39:00.099 align:start position:0% all the trades and like oh you receiving money<00:38:57.109> from<00:38:57.200> other<00:38:57.680> people<00:38:58.099> so<00:38:58.849> once<00:38:59.420> it's 00:39:00.099 --> 00:39:00.109 align:start position:0% money from other people so once it's 00:39:00.109 --> 00:39:02.140 align:start position:0% money from other people so once it's mined<00:39:00.470> you're<00:39:01.430> gonna<00:39:01.520> get<00:39:01.790> a<00:39:01.849> push 00:39:02.140 --> 00:39:02.150 align:start position:0% mined you're gonna get a push 00:39:02.150 --> 00:39:05.050 align:start position:0% mined you're gonna get a push notification<00:39:02.240> as<00:39:02.930> well<00:39:03.140> and<00:39:04.130> so<00:39:04.910> this 00:39:05.050 --> 00:39:05.060 align:start position:0% notification as well and so this 00:39:05.060 --> 00:39:06.670 align:start position:0% notification as well and so this interface<00:39:05.510> can<00:39:05.720> act<00:39:05.869> as<00:39:06.290> a<00:39:06.320> complete 00:39:06.670 --> 00:39:06.680 align:start position:0% interface can act as a complete 00:39:06.680 --> 00:39:09.040 align:start position:0% interface can act as a complete replacement<00:39:06.950> of<00:39:07.369> your<00:39:07.660> like<00:39:08.660> letting<00:39:09.020> my 00:39:09.040 --> 00:39:09.050 align:start position:0% replacement of your like letting my 00:39:09.050 --> 00:39:11.339 align:start position:0% replacement of your like letting my either<00:39:09.440> wallet<00:39:09.859> or<00:39:10.130> other<00:39:10.490> things<00:39:10.730> like<00:39:10.790> that 00:39:11.339 --> 00:39:11.349 align:start position:0% either wallet or other things like that 00:39:11.349 --> 00:39:13.900 align:start position:0% either wallet or other things like that then<00:39:12.349> once<00:39:12.740> you<00:39:12.890> get<00:39:13.099> some<00:39:13.340> died<00:39:13.490> you<00:39:13.550> can 00:39:13.900 --> 00:39:13.910 align:start position:0% then once you get some died you can 00:39:13.910 --> 00:39:16.630 align:start position:0% then once you get some died you can instantly<00:39:14.390> go<00:39:14.869> to<00:39:14.900> compound<00:39:15.530> and<00:39:15.859> purchase 00:39:16.630 --> 00:39:16.640 align:start position:0% instantly go to compound and purchase 00:39:16.640 --> 00:39:19.000 align:start position:0% instantly go to compound and purchase and<00:39:16.880> put<00:39:17.390> money<00:39:17.930> into<00:39:18.170> compounds<00:39:18.590> to<00:39:18.770> start 00:39:19.000 --> 00:39:19.010 align:start position:0% and put money into compounds to start 00:39:19.010 --> 00:39:21.760 align:start position:0% and put money into compounds to start earning<00:39:19.220> interest<00:39:19.609> right<00:39:20.420> away<00:39:20.630> that's<00:39:21.140> again 00:39:21.760 --> 00:39:21.770 align:start position:0% earning interest right away that's again 00:39:21.770 --> 00:39:27.760 align:start position:0% earning interest right away that's again a<00:39:21.800> super<00:39:22.250> seamless<00:39:22.609> flow<00:39:25.450> yeah<00:39:26.450> so<00:39:27.260> this<00:39:27.530> has 00:39:27.760 --> 00:39:27.770 align:start position:0% a super seamless flow yeah so this has 00:39:27.770 --> 00:39:30.490 align:start position:0% a super seamless flow yeah so this has mainly<00:39:28.400> it<00:39:28.670> about<00:39:28.970> zarion<00:39:29.359> come<00:39:30.200> and<00:39:30.349> try 00:39:30.490 --> 00:39:30.500 align:start position:0% mainly it about zarion come and try 00:39:30.500 --> 00:39:32.530 align:start position:0% mainly it about zarion come and try check<00:39:30.830> it<00:39:30.950> out<00:39:31.040> with<00:39:31.160> yourself<00:39:31.580> I<00:39:31.910> hope<00:39:32.390> you 00:39:32.530 --> 00:39:32.540 align:start position:0% check it out with yourself I hope you 00:39:32.540 --> 00:39:34.900 align:start position:0% check it out with yourself I hope you love<00:39:32.750> it<00:39:32.780> and<00:39:33.099> yeah<00:39:34.099> thanks<00:39:34.400> thanks<00:39:34.790> so<00:39:34.880> much 00:39:34.900 --> 00:39:34.910 align:start position:0% love it and yeah thanks thanks so much 00:39:34.910 --> 00:39:46.000 align:start position:0% love it and yeah thanks thanks so much again<00:39:35.060> thank<00:39:35.869> you<00:39:42.070> thank<00:39:43.070> you<00:39:44.500> and<00:39:45.500> we<00:39:45.710> wanted 00:39:46.000 --> 00:39:46.010 align:start position:0% again thank you thank you and we wanted 00:39:46.010 --> 00:39:49.599 align:start position:0% again thank you thank you and we wanted to<00:39:46.099> give<00:39:46.339> one<00:39:47.089> runner<00:39:47.990> up<00:39:48.170> Eragon<00:39:48.770> they<00:39:49.310> didn't 00:39:49.599 --> 00:39:49.609 align:start position:0% to give one runner up Eragon they didn't 00:39:49.609 --> 00:39:51.849 align:start position:0% to give one runner up Eragon they didn't win<00:39:49.760> last<00:39:49.790> year<00:39:50.240> that's<00:39:50.510> right<00:39:50.630> last<00:39:51.410> year<00:39:51.650> but 00:39:51.849 --> 00:39:51.859 align:start position:0% win last year that's right last year but 00:39:51.859 --> 00:40:33.250 align:start position:0% win last year that's right last year but we<00:39:52.330> you<00:39:53.330> gotta<00:39:53.540> check<00:39:53.780> out<00:39:53.960> this<00:39:54.080> great<00:39:54.320> video 00:40:33.250 --> 00:40:33.260 align:start position:0% 00:40:33.260 --> 00:40:45.700 align:start position:0% I<00:40:43.540> want<00:40:44.540> to<00:40:44.630> say<00:40:44.780> that<00:40:44.990> all<00:40:45.140> of<00:40:45.170> the<00:40:45.440> three 00:40:45.700 --> 00:40:45.710 align:start position:0% I want to say that all of the three 00:40:45.710 --> 00:40:49.420 align:start position:0% I want to say that all of the three winners<00:40:46.190> and<00:40:46.550> the<00:40:46.640> runner-up<00:40:46.940> had<00:40:48.040> one<00:40:49.040> thing 00:40:49.420 --> 00:40:49.430 align:start position:0% winners and the runner-up had one thing 00:40:49.430 --> 00:40:52.390 align:start position:0% winners and the runner-up had one thing in<00:40:49.610> common<00:40:49.640> they<00:40:50.360> were<00:40:50.680> very<00:40:51.680> easy<00:40:51.920> to<00:40:52.190> use 00:40:52.390 --> 00:40:52.400 align:start position:0% in common they were very easy to use 00:40:52.400 --> 00:40:55.480 align:start position:0% in common they were very easy to use that<00:40:53.240> the<00:40:53.720> mental<00:40:54.080> models<00:40:54.410> were<00:40:54.590> exactly<00:40:55.130> how 00:40:55.480 --> 00:40:55.490 align:start position:0% that the mental models were exactly how 00:40:55.490 --> 00:40:58.030 align:start position:0% that the mental models were exactly how users<00:40:55.910> sort<00:40:56.120> of<00:40:56.270> expect<00:40:56.720> them<00:40:56.870> to<00:40:56.900> be<00:40:57.170> the 00:40:58.030 --> 00:40:58.040 align:start position:0% users sort of expect them to be the 00:40:58.040 --> 00:41:00.520 align:start position:0% users sort of expect them to be the coffee<00:40:58.370> especially<00:40:59.270> like<00:40:59.900> in<00:41:00.170> bigger 00:41:00.520 --> 00:41:00.530 align:start position:0% coffee especially like in bigger 00:41:00.530 --> 00:41:06.310 align:start position:0% coffee especially like in bigger projects<00:41:01.220> were<00:41:01.580> so<00:41:02.150> well<00:41:04.090> so<00:41:05.090> detailed<00:41:05.690> and<00:41:05.960> so 00:41:06.310 --> 00:41:06.320 align:start position:0% projects were so well so detailed and so 00:41:06.320 --> 00:41:09.720 align:start position:0% projects were so well so detailed and so well<00:41:06.650> thought<00:41:06.890> out<00:41:07.630> that<00:41:08.630> all<00:41:08.960> three<00:41:09.350> of<00:41:09.500> them 00:41:09.720 --> 00:41:09.730 align:start position:0% well thought out that all three of them 00:41:09.730 --> 00:41:12.220 align:start position:0% well thought out that all three of them like<00:41:10.730> all<00:41:11.030> three<00:41:11.300> of<00:41:11.390> them<00:41:11.540> made<00:41:11.690> a<00:41:11.720> really 00:41:12.220 --> 00:41:12.230 align:start position:0% like all three of them made a really 00:41:12.230 --> 00:41:15.730 align:start position:0% like all three of them made a really great<00:41:12.530> job<00:41:12.830> in<00:41:13.190> and<00:41:14.090> made<00:41:15.080> a<00:41:15.110> really<00:41:15.410> big 00:41:15.730 --> 00:41:15.740 align:start position:0% great job in and made a really big 00:41:15.740 --> 00:41:17.920 align:start position:0% great job in and made a really big problem<00:41:16.040> with<00:41:16.370> arrogant<00:41:17.060> example<00:41:17.600> they<00:41:17.780> made 00:41:17.920 --> 00:41:17.930 align:start position:0% problem with arrogant example they made 00:41:17.930 --> 00:41:19.750 align:start position:0% problem with arrogant example they made a<00:41:17.960> really<00:41:18.290> big<00:41:18.530> progress<00:41:18.800> in<00:41:19.040> where<00:41:19.610> they 00:41:19.750 --> 00:41:19.760 align:start position:0% a really big progress in where they 00:41:19.760 --> 00:41:22.900 align:start position:0% a really big progress in where they where<00:41:20.030> a<00:41:20.390> year<00:41:21.320> ago<00:41:21.590> so<00:41:21.830> yeah<00:41:22.340> I<00:41:22.400> think<00:41:22.670> that's 00:41:22.900 --> 00:41:22.910 align:start position:0% where a year ago so yeah I think that's 00:41:22.910 --> 00:41:24.970 align:start position:0% where a year ago so yeah I think that's maybe<00:41:23.180> what<00:41:23.480> the<00:41:23.600> judges<00:41:23.810> struggled<00:41:24.710> with<00:41:24.860> the 00:41:24.970 --> 00:41:24.980 align:start position:0% maybe what the judges struggled with the 00:41:24.980 --> 00:41:26.950 align:start position:0% maybe what the judges struggled with the most<00:41:25.190> was<00:41:25.490> there's<00:41:25.790> so<00:41:25.970> many<00:41:26.120> that<00:41:26.480> applied 00:41:26.950 --> 00:41:26.960 align:start position:0% most was there's so many that applied 00:41:26.960 --> 00:41:28.630 align:start position:0% most was there's so many that applied last<00:41:27.140> year<00:41:27.470> and<00:41:27.680> the<00:41:27.890> progress<00:41:28.130> of<00:41:28.460> they've 00:41:28.630 --> 00:41:28.640 align:start position:0% last year and the progress of they've 00:41:28.640 --> 00:41:30.760 align:start position:0% last year and the progress of they've made<00:41:28.880> and<00:41:29.180> so<00:41:29.750> our<00:41:29.930> god<00:41:30.080> we<00:41:30.200> definitely<00:41:30.560> wanted 00:41:30.760 --> 00:41:30.770 align:start position:0% made and so our god we definitely wanted 00:41:30.770 --> 00:41:32.800 align:start position:0% made and so our god we definitely wanted to<00:41:30.920> kind<00:41:31.130> of<00:41:31.160> showcase<00:41:31.370> some<00:41:32.030> of<00:41:32.180> the<00:41:32.360> new 00:41:32.800 --> 00:41:32.810 align:start position:0% to kind of showcase some of the new 00:41:32.810 --> 00:41:36.070 align:start position:0% to kind of showcase some of the new design<00:41:33.200> system<00:41:33.620> that<00:41:33.770> they<00:41:33.920> they've<00:41:34.490> built<00:41:35.080> so 00:41:36.070 --> 00:41:36.080 align:start position:0% design system that they they've built so 00:41:36.080 --> 00:41:38.290 align:start position:0% design system that they they've built so with<00:41:36.320> that<00:41:36.500> thank<00:41:37.220> you<00:41:37.370> everybody<00:41:37.670> thank<00:41:38.180> you 00:41:38.290 --> 00:41:38.300 align:start position:0% with that thank you everybody thank you 00:41:38.300 --> 00:41:40.270 align:start position:0% with that thank you everybody thank you to<00:41:38.450> etherion<00:41:38.840> foundation<00:41:39.470> and<00:41:39.800> thank<00:41:40.160> you 00:41:40.270 --> 00:41:40.280 align:start position:0% to etherion foundation and thank you 00:41:40.280 --> 00:41:43.110 align:start position:0% to etherion foundation and thank you guys<00:41:40.460> all<00:41:40.490> for<00:41:40.700> sitting<00:41:41.120> here<00:41:41.270> and<00:41:41.360> coming 00:41:43.110 --> 00:41:43.120 align:start position:0% guys all for sitting here and coming 00:41:43.120 --> 00:41:52.930 align:start position:0% guys all for sitting here and coming [Applause] 00:41:52.930 --> 00:41:52.940 align:start position:0% 00:41:52.940 --> 00:41:55.000 align:start position:0% you