WEBVTT Kind: captions Language: en 00:00:00.030 --> 00:00:03.050 align:start position:0% so<00:00:00.930> I'm<00:00:01.319> Alex<00:00:01.740> on<00:00:01.890> a<00:00:01.920> Sunday<00:00:02.340> and<00:00:02.490> I<00:00:02.700> want<00:00:02.939> to 00:00:03.050 --> 00:00:03.060 align:start position:0% so I'm Alex on a Sunday and I want to 00:00:03.060 --> 00:00:06.619 align:start position:0% so I'm Alex on a Sunday and I want to talk<00:00:03.240> about<00:00:03.419> the<00:00:03.810> big<00:00:04.110> UX<00:00:05.100> problems<00:00:05.609> and<00:00:06.330> I 00:00:06.619 --> 00:00:06.629 align:start position:0% talk about the big UX problems and I 00:00:06.629 --> 00:00:09.740 align:start position:0% talk about the big UX problems and I think<00:00:06.870> UX<00:00:07.859> is<00:00:08.130> it's<00:00:09.000> important<00:00:09.510> to<00:00:09.570> talk<00:00:09.690> about 00:00:09.740 --> 00:00:09.750 align:start position:0% think UX is it's important to talk about 00:00:09.750 --> 00:00:12.230 align:start position:0% think UX is it's important to talk about UX<00:00:10.290> because<00:00:10.530> the<00:00:10.740> UX<00:00:11.070> is<00:00:11.280> as<00:00:11.490> important<00:00:12.179> as 00:00:12.230 --> 00:00:12.240 align:start position:0% UX because the UX is as important as 00:00:12.240 --> 00:00:14.870 align:start position:0% UX because the UX is as important as scalability<00:00:12.620> there<00:00:13.620> is<00:00:13.710> no<00:00:13.860> point<00:00:14.250> in<00:00:14.639> having 00:00:14.870 --> 00:00:14.880 align:start position:0% scalability there is no point in having 00:00:14.880 --> 00:00:16.640 align:start position:0% scalability there is no point in having a<00:00:15.089> blockchain<00:00:15.360> that<00:00:15.750> can<00:00:15.900> handle<00:00:16.109> a<00:00:16.320> billion 00:00:16.640 --> 00:00:16.650 align:start position:0% a blockchain that can handle a billion 00:00:16.650 --> 00:00:19.250 align:start position:0% a blockchain that can handle a billion transactions<00:00:17.250> if<00:00:17.699> your<00:00:17.970> apps<00:00:18.330> can't<00:00:18.930> reach 00:00:19.250 --> 00:00:19.260 align:start position:0% transactions if your apps can't reach 00:00:19.260 --> 00:00:21.800 align:start position:0% transactions if your apps can't reach half<00:00:19.650> a<00:00:19.770> billion<00:00:19.949> users<00:00:20.189> right<00:00:20.699> so<00:00:21.330> that's<00:00:21.539> why 00:00:21.800 --> 00:00:21.810 align:start position:0% half a billion users right so that's why 00:00:21.810 --> 00:00:23.720 align:start position:0% half a billion users right so that's why it's<00:00:22.080> so<00:00:22.439> important<00:00:23.070> to<00:00:23.100> pay<00:00:23.250> attention<00:00:23.279> to 00:00:23.720 --> 00:00:23.730 align:start position:0% it's so important to pay attention to 00:00:23.730 --> 00:00:26.570 align:start position:0% it's so important to pay attention to that<00:00:23.910> now<00:00:24.900> before<00:00:25.410> it<00:00:25.800> was<00:00:25.920> an<00:00:26.039> achievement 00:00:26.570 --> 00:00:26.580 align:start position:0% that now before it was an achievement 00:00:26.580 --> 00:00:29.300 align:start position:0% that now before it was an achievement I<00:00:26.640> was<00:00:26.820> just<00:00:27.300> in<00:00:27.449> start-up<00:00:27.869> or<00:00:28.199> I<00:00:28.500> founded 00:00:29.300 --> 00:00:29.310 align:start position:0% I was just in start-up or I founded 00:00:29.310 --> 00:00:31.550 align:start position:0% I was just in start-up or I founded syrups<00:00:29.849> failed<00:00:30.179> at<00:00:30.420> most<00:00:30.660> of<00:00:30.779> them<00:00:30.929> and<00:00:31.109> we 00:00:31.550 --> 00:00:31.560 align:start position:0% syrups failed at most of them and we 00:00:31.560 --> 00:00:34.040 align:start position:0% syrups failed at most of them and we learn<00:00:31.859> a<00:00:31.890> lot<00:00:32.099> of<00:00:32.420> metrics<00:00:33.420> that<00:00:33.570> we<00:00:33.690> keep<00:00:33.870> our 00:00:34.040 --> 00:00:34.050 align:start position:0% learn a lot of metrics that we keep our 00:00:34.050 --> 00:00:36.260 align:start position:0% learn a lot of metrics that we keep our eyes<00:00:34.290> on<00:00:34.399> when<00:00:35.399> we<00:00:35.579> are<00:00:35.640> in<00:00:35.730> their<00:00:35.880> startup 00:00:36.260 --> 00:00:36.270 align:start position:0% eyes on when we are in their startup 00:00:36.270 --> 00:00:39.010 align:start position:0% eyes on when we are in their startup Ward's<00:00:36.600> things<00:00:37.170> like<00:00:37.320> the<00:00:37.800> k-factor<00:00:38.280> virality 00:00:39.010 --> 00:00:39.020 align:start position:0% Ward's things like the k-factor virality 00:00:39.020 --> 00:00:42.740 align:start position:0% Ward's things like the k-factor virality SEO<00:00:40.020> and<00:00:40.590> we<00:00:41.399> don't<00:00:41.579> talk<00:00:41.820> about<00:00:42.000> those<00:00:42.300> here 00:00:42.740 --> 00:00:42.750 align:start position:0% SEO and we don't talk about those here 00:00:42.750 --> 00:00:45.170 align:start position:0% SEO and we don't talk about those here because<00:00:43.320> it<00:00:43.440> seems<00:00:43.710> that<00:00:43.829> we<00:00:44.070> we<00:00:44.460> sort<00:00:44.730> of<00:00:44.850> work 00:00:45.170 --> 00:00:45.180 align:start position:0% because it seems that we we sort of work 00:00:45.180 --> 00:00:47.000 align:start position:0% because it seems that we we sort of work in<00:00:45.480> a<00:00:45.539> different<00:00:45.690> level<00:00:46.050> right<00:00:46.289> those<00:00:46.680> rules 00:00:47.000 --> 00:00:47.010 align:start position:0% in a different level right those rules 00:00:47.010 --> 00:00:49.250 align:start position:0% in a different level right those rules don't<00:00:47.129> apply<00:00:47.309> to<00:00:47.520> us<00:00:47.879> but<00:00:48.719> that's<00:00:48.899> not<00:00:49.079> true 00:00:49.250 --> 00:00:49.260 align:start position:0% don't apply to us but that's not true 00:00:49.260 --> 00:00:52.100 align:start position:0% don't apply to us but that's not true right<00:00:49.800> we<00:00:50.370> are<00:00:50.489> in<00:00:50.700> the<00:00:50.789> same<00:00:51.030> game<00:00:51.539> and<00:00:51.960> we 00:00:52.100 --> 00:00:52.110 align:start position:0% right we are in the same game and we 00:00:52.110 --> 00:00:53.510 align:start position:0% right we are in the same game and we need<00:00:52.320> to<00:00:52.440> pay<00:00:52.559> attention<00:00:52.590> to<00:00:53.129> things<00:00:53.309> like 00:00:53.510 --> 00:00:53.520 align:start position:0% need to pay attention to things like 00:00:53.520 --> 00:00:57.560 align:start position:0% need to pay attention to things like this<00:00:54.480> this<00:00:55.440> the<00:00:55.920> equation<00:00:56.699> that<00:00:56.879> I<00:00:56.940> used<00:00:57.300> to 00:00:57.560 --> 00:00:57.570 align:start position:0% this this the equation that I used to 00:00:57.570 --> 00:01:00.650 align:start position:0% this this the equation that I used to spend<00:00:58.079> my<00:00:58.170> my<00:00:58.770> days<00:00:59.100> looking<00:00:59.760> at<00:00:59.850> it's 00:01:00.650 --> 00:01:00.660 align:start position:0% spend my my days looking at it's 00:01:00.660 --> 00:01:03.020 align:start position:0% spend my my days looking at it's basically<00:01:01.500> it's<00:01:01.739> also<00:01:02.070> called<00:01:02.699> the<00:01:02.850> key 00:01:03.020 --> 00:01:03.030 align:start position:0% basically it's also called the key 00:01:03.030 --> 00:01:06.100 align:start position:0% basically it's also called the key factor<00:01:03.449> and<00:01:03.780> it's<00:01:04.049> like<00:01:04.199> virality<00:01:04.760> measure 00:01:06.100 --> 00:01:06.110 align:start position:0% factor and it's like virality measure 00:01:06.110 --> 00:01:09.109 align:start position:0% factor and it's like virality measure basically<00:01:07.110> what<00:01:07.500> you're<00:01:07.619> doing<00:01:07.650> is<00:01:08.220> every 00:01:09.109 --> 00:01:09.119 align:start position:0% basically what you're doing is every 00:01:09.119 --> 00:01:11.870 align:start position:0% basically what you're doing is every time<00:01:09.330> your<00:01:09.540> user<00:01:09.840> is<00:01:10.140> exposed<00:01:10.710> to<00:01:11.100> your<00:01:11.250> app<00:01:11.490> in 00:01:11.870 --> 00:01:11.880 align:start position:0% time your user is exposed to your app in 00:01:11.880 --> 00:01:14.060 align:start position:0% time your user is exposed to your app in any<00:01:12.119> way<00:01:12.299> there's<00:01:12.960> a<00:01:13.049> chance<00:01:13.470> that<00:01:13.650> they<00:01:13.890> might 00:01:14.060 --> 00:01:14.070 align:start position:0% any way there's a chance that they might 00:01:14.070 --> 00:01:16.190 align:start position:0% any way there's a chance that they might actually<00:01:14.369> pay<00:01:14.640> attention<00:01:14.780> there's<00:01:15.780> if<00:01:16.049> they 00:01:16.190 --> 00:01:16.200 align:start position:0% actually pay attention there's if they 00:01:16.200 --> 00:01:17.570 align:start position:0% actually pay attention there's if they do<00:01:16.290> there's<00:01:16.650> a<00:01:16.740> chance<00:01:17.040> that<00:01:17.250> they<00:01:17.340> might<00:01:17.549> want 00:01:17.570 --> 00:01:17.580 align:start position:0% do there's a chance that they might want 00:01:17.580 --> 00:01:19.730 align:start position:0% do there's a chance that they might want to<00:01:17.850> sign<00:01:18.060> up<00:01:18.119> there's<00:01:19.049> a<00:01:19.170> chance<00:01:19.530> that<00:01:19.650> they 00:01:19.730 --> 00:01:19.740 align:start position:0% to sign up there's a chance that they 00:01:19.740 --> 00:01:21.649 align:start position:0% to sign up there's a chance that they might<00:01:19.890> complete<00:01:20.460> this<00:01:20.610> I<00:01:20.790> design<00:01:21.270> a<00:01:21.299> process 00:01:21.649 --> 00:01:21.659 align:start position:0% might complete this I design a process 00:01:21.659 --> 00:01:23.630 align:start position:0% might complete this I design a process that<00:01:22.140> they<00:01:22.229> might<00:01:22.409> download<00:01:22.619> the<00:01:22.950> app<00:01:23.100> and 00:01:23.630 --> 00:01:23.640 align:start position:0% that they might download the app and 00:01:23.640 --> 00:01:26.620 align:start position:0% that they might download the app and that's<00:01:23.880> after<00:01:24.150> a<00:01:24.299> bunch<00:01:24.720> of<00:01:24.869> steps<00:01:25.200> they<00:01:26.009> might 00:01:26.620 --> 00:01:26.630 align:start position:0% that's after a bunch of steps they might 00:01:26.630 --> 00:01:30.200 align:start position:0% that's after a bunch of steps they might share<00:01:27.630> some<00:01:27.960> content<00:01:28.710> to<00:01:29.009> let's<00:01:29.670> say<00:01:29.850> ten<00:01:30.180> or 00:01:30.200 --> 00:01:30.210 align:start position:0% share some content to let's say ten or 00:01:30.210 --> 00:01:32.060 align:start position:0% share some content to let's say ten or turn<00:01:30.570> your<00:01:30.689> friends<00:01:31.020> so<00:01:31.590> here's<00:01:31.829> the<00:01:31.950> basic 00:01:32.060 --> 00:01:32.070 align:start position:0% turn your friends so here's the basic 00:01:32.070 --> 00:01:35.210 align:start position:0% turn your friends so here's the basic thing<00:01:32.460> multiply<00:01:33.299> all<00:01:33.570> those<00:01:33.869> factors<00:01:34.350> if<00:01:34.650> it's 00:01:35.210 --> 00:01:35.220 align:start position:0% thing multiply all those factors if it's 00:01:35.220 --> 00:01:37.789 align:start position:0% thing multiply all those factors if it's above<00:01:35.579> one<00:01:35.939> then<00:01:36.659> your<00:01:36.840> app<00:01:37.020> is<00:01:37.200> gonna<00:01:37.439> go<00:01:37.740> to 00:01:37.789 --> 00:01:37.799 align:start position:0% above one then your app is gonna go to 00:01:37.799 --> 00:01:40.760 align:start position:0% above one then your app is gonna go to exponential<00:01:38.759> growth<00:01:38.939> it's<00:01:39.630> if<00:01:39.960> it's<00:01:40.350> slightly 00:01:40.760 --> 00:01:40.770 align:start position:0% exponential growth it's if it's slightly 00:01:40.770 --> 00:01:44.359 align:start position:0% exponential growth it's if it's slightly below<00:01:41.130> one<00:01:41.460> then<00:01:42.240> your<00:01:42.899> app<00:01:43.079> is<00:01:43.259> dying<00:01:43.590> and 00:01:44.359 --> 00:01:44.369 align:start position:0% below one then your app is dying and 00:01:44.369 --> 00:01:47.090 align:start position:0% below one then your app is dying and like<00:01:44.549> pay<00:01:45.360> attention<00:01:45.780> to<00:01:45.930> that<00:01:46.110> is<00:01:46.530> the<00:01:46.920> life 00:01:47.090 --> 00:01:47.100 align:start position:0% like pay attention to that is the life 00:01:47.100 --> 00:01:49.910 align:start position:0% like pay attention to that is the life or<00:01:47.340> death<00:01:47.549> of<00:01:47.820> your<00:01:48.210> app<00:01:48.659> because<00:01:49.500> if<00:01:49.680> for 00:01:49.910 --> 00:01:49.920 align:start position:0% or death of your app because if for 00:01:49.920 --> 00:01:52.399 align:start position:0% or death of your app because if for every<00:01:50.520> user<00:01:50.909> you're<00:01:51.270> losing<00:01:51.689> more<00:01:51.840> users<00:01:52.229> and 00:01:52.399 --> 00:01:52.409 align:start position:0% every user you're losing more users and 00:01:52.409 --> 00:01:54.109 align:start position:0% every user you're losing more users and it<00:01:52.500> means<00:01:52.649> that<00:01:52.829> you<00:01:52.950> need<00:01:53.100> to<00:01:53.250> put<00:01:53.520> more<00:01:53.820> money 00:01:54.109 --> 00:01:54.119 align:start position:0% it means that you need to put more money 00:01:54.119 --> 00:01:56.569 align:start position:0% it means that you need to put more money to<00:01:54.869> attract<00:01:55.170> more<00:01:55.320> users<00:01:55.560> and<00:01:55.799> that's<00:01:56.189> that 00:01:56.569 --> 00:01:56.579 align:start position:0% to attract more users and that's that 00:01:56.579 --> 00:01:57.319 align:start position:0% to attract more users and that's that doesn't<00:01:56.790> work 00:01:57.319 --> 00:01:57.329 align:start position:0% doesn't work 00:01:57.329 --> 00:02:00.170 align:start position:0% doesn't work how<00:01:57.899> does<00:01:58.110> it<00:01:58.140> work<00:01:58.290> for<00:01:58.770> each<00:01:58.890> internet<00:01:59.280> for 00:02:00.170 --> 00:02:00.180 align:start position:0% how does it work for each internet for 00:02:00.180 --> 00:02:02.209 align:start position:0% how does it work for each internet for any<00:02:00.390> of<00:02:00.600> your<00:02:00.869> app<00:02:01.020> it<00:02:01.320> looks<00:02:01.560> terrible<00:02:02.100> it 00:02:02.209 --> 00:02:02.219 align:start position:0% any of your app it looks terrible it 00:02:02.219 --> 00:02:03.560 align:start position:0% any of your app it looks terrible it looks<00:02:02.430> something<00:02:02.610> like<00:02:02.759> this<00:02:02.969> where<00:02:03.299> you<00:02:03.390> go 00:02:03.560 --> 00:02:03.570 align:start position:0% looks something like this where you go 00:02:03.570 --> 00:02:06.200 align:start position:0% looks something like this where you go oh<00:02:03.780> a<00:02:04.469> crypto<00:02:04.860> kitty<00:02:05.070> that's<00:02:05.520> interesting<00:02:06.060> and 00:02:06.200 --> 00:02:06.210 align:start position:0% oh a crypto kitty that's interesting and 00:02:06.210 --> 00:02:08.869 align:start position:0% oh a crypto kitty that's interesting and then<00:02:06.810> the<00:02:07.020> user<00:02:07.200> has<00:02:07.530> to<00:02:07.680> go<00:02:07.860> into<00:02:08.129> a<00:02:08.340> whole 00:02:08.869 --> 00:02:08.879 align:start position:0% then the user has to go into a whole 00:02:08.879 --> 00:02:11.360 align:start position:0% then the user has to go into a whole rabbit<00:02:09.330> hole<00:02:09.720> where<00:02:10.319> they<00:02:10.440> need<00:02:10.979> to<00:02:11.009> really 00:02:11.360 --> 00:02:11.370 align:start position:0% rabbit hole where they need to really 00:02:11.370 --> 00:02:12.460 align:start position:0% rabbit hole where they need to really quickly<00:02:11.730> PDF 00:02:12.460 --> 00:02:12.470 align:start position:0% quickly PDF 00:02:12.470 --> 00:02:14.530 align:start position:0% quickly PDF and<00:02:13.250> at<00:02:13.550> some<00:02:13.760> point<00:02:13.790> they<00:02:14.090> are<00:02:14.210> taking<00:02:14.510> a 00:02:14.530 --> 00:02:14.540 align:start position:0% and at some point they are taking a 00:02:14.540 --> 00:02:16.570 align:start position:0% and at some point they are taking a selfie<00:02:15.170> with<00:02:15.350> their<00:02:15.530> passport<00:02:16.130> so<00:02:16.310> they<00:02:16.430> can 00:02:16.570 --> 00:02:16.580 align:start position:0% selfie with their passport so they can 00:02:16.580 --> 00:02:19.270 align:start position:0% selfie with their passport so they can get<00:02:16.850> a<00:02:17.360> coinbase<00:02:17.990> account<00:02:18.620> so<00:02:18.920> that<00:02:19.070> it<00:02:19.160> can 00:02:19.270 --> 00:02:19.280 align:start position:0% get a coinbase account so that it can 00:02:19.280 --> 00:02:21.280 align:start position:0% get a coinbase account so that it can get<00:02:19.550> validated<00:02:20.390> in<00:02:20.630> three<00:02:20.810> months 00:02:21.280 --> 00:02:21.290 align:start position:0% get validated in three months 00:02:21.290 --> 00:02:23.860 align:start position:0% get validated in three months that's<00:02:21.740> crazy<00:02:22.010> no<00:02:22.460> normal<00:02:23.030> app<00:02:23.240> would<00:02:23.480> do<00:02:23.660> that 00:02:23.860 --> 00:02:23.870 align:start position:0% that's crazy no normal app would do that 00:02:23.870 --> 00:02:27.550 align:start position:0% that's crazy no normal app would do that to<00:02:24.080> you<00:02:24.290> and<00:02:24.590> that's<00:02:25.130> why<00:02:25.340> like<00:02:26.140> outside<00:02:27.140> of<00:02:27.290> us 00:02:27.550 --> 00:02:27.560 align:start position:0% to you and that's why like outside of us 00:02:27.560 --> 00:02:30.550 align:start position:0% to you and that's why like outside of us outside<00:02:27.950> of<00:02:28.340> us<00:02:28.550> like<00:02:28.790> the<00:02:29.270> viral<00:02:29.660> factor<00:02:29.960> it's 00:02:30.550 --> 00:02:30.560 align:start position:0% outside of us like the viral factor it's 00:02:30.560 --> 00:02:33.550 align:start position:0% outside of us like the viral factor it's zero<00:02:30.980> it's<00:02:31.310> not<00:02:31.460> like<00:02:31.640> 0.9<00:02:32.480> which<00:02:32.810> is<00:02:32.990> bad<00:02:33.260> it's 00:02:33.550 --> 00:02:33.560 align:start position:0% zero it's not like 0.9 which is bad it's 00:02:33.560 --> 00:02:37.810 align:start position:0% zero it's not like 0.9 which is bad it's zero<00:02:34.010> I<00:02:34.370> mean<00:02:35.000> we've<00:02:35.750> had<00:02:36.080> more<00:02:36.590> i<00:02:36.650> SEOs<00:02:37.370> last 00:02:37.810 --> 00:02:37.820 align:start position:0% zero I mean we've had more i SEOs last 00:02:37.820 --> 00:02:39.670 align:start position:0% zero I mean we've had more i SEOs last years<00:02:38.180> and<00:02:38.480> we<00:02:38.570> have<00:02:38.750> more<00:02:38.990> daily<00:02:39.320> active 00:02:39.670 --> 00:02:39.680 align:start position:0% years and we have more daily active 00:02:39.680 --> 00:02:43.960 align:start position:0% years and we have more daily active users<00:02:40.070> in<00:02:40.180> anywhere<00:02:41.180> and<00:02:42.520> that's<00:02:43.520> sort<00:02:43.790> of<00:02:43.910> the 00:02:43.960 --> 00:02:43.970 align:start position:0% users in anywhere and that's sort of the 00:02:43.970 --> 00:02:51.460 align:start position:0% users in anywhere and that's sort of the point<00:02:48.190> the<00:02:49.190> point<00:02:49.430> is<00:02:49.760> that<00:02:50.720> if<00:02:50.900> you<00:02:51.050> want<00:02:51.290> to 00:02:51.460 --> 00:02:51.470 align:start position:0% point the point is that if you want to 00:02:51.470 --> 00:02:54.520 align:start position:0% point the point is that if you want to pay<00:02:52.120> the<00:02:53.120> point<00:02:53.480> is<00:02:53.570> if<00:02:53.690> you<00:02:53.810> have<00:02:54.080> if<00:02:54.380> you<00:02:54.500> want 00:02:54.520 --> 00:02:54.530 align:start position:0% pay the point is if you have if you want 00:02:54.530 --> 00:02:56.740 align:start position:0% pay the point is if you have if you want to<00:02:54.710> reach<00:02:54.920> or<00:02:55.280> something<00:02:55.880> else<00:02:56.240> than<00:02:56.510> like 00:02:56.740 --> 00:02:56.750 align:start position:0% to reach or something else than like 00:02:56.750 --> 00:02:58.870 align:start position:0% to reach or something else than like Earth<00:02:56.990> the<00:02:57.380> tech<00:02:57.590> enthusiast<00:02:58.250> those<00:02:58.490> who<00:02:58.700> go 00:02:58.870 --> 00:02:58.880 align:start position:0% Earth the tech enthusiast those who go 00:02:58.880 --> 00:03:01.120 align:start position:0% Earth the tech enthusiast those who go to<00:02:58.910> tech<00:02:59.270> conferences<00:02:59.930> we<00:03:00.560> need<00:03:00.770> to<00:03:00.950> reach 00:03:01.120 --> 00:03:01.130 align:start position:0% to tech conferences we need to reach 00:03:01.130 --> 00:03:03.910 align:start position:0% to tech conferences we need to reach normal<00:03:02.060> people<00:03:02.450> I'm<00:03:02.660> not<00:03:02.990> getting<00:03:03.290> the<00:03:03.410> thing 00:03:03.910 --> 00:03:03.920 align:start position:0% normal people I'm not getting the thing 00:03:03.920 --> 00:03:06.400 align:start position:0% normal people I'm not getting the thing here<00:03:04.130> so<00:03:04.430> but<00:03:05.060> it's<00:03:05.210> going<00:03:05.360> there<00:03:05.540> right<00:03:05.780> and 00:03:06.400 --> 00:03:06.410 align:start position:0% here so but it's going there right and 00:03:06.410 --> 00:03:09.700 align:start position:0% here so but it's going there right and what<00:03:07.160> do<00:03:07.310> normal<00:03:07.460> people<00:03:07.730> want<00:03:08.300> normal<00:03:09.140> people 00:03:09.700 --> 00:03:09.710 align:start position:0% what do normal people want normal people 00:03:09.710 --> 00:03:11.680 align:start position:0% what do normal people want normal people they<00:03:10.070> don't<00:03:10.190> like<00:03:10.310> average<00:03:10.640> users<00:03:11.420> the 00:03:11.680 --> 00:03:11.690 align:start position:0% they don't like average users the 00:03:11.690 --> 00:03:13.570 align:start position:0% they don't like average users the medical<00:03:12.140> average<00:03:12.410> users<00:03:12.770> they<00:03:13.220> don't<00:03:13.430> care 00:03:13.570 --> 00:03:13.580 align:start position:0% medical average users they don't care 00:03:13.580 --> 00:03:14.500 align:start position:0% medical average users they don't care about<00:03:13.670> each<00:03:13.940> other<00:03:14.150> they<00:03:14.210> don't<00:03:14.330> care<00:03:14.450> about 00:03:14.500 --> 00:03:14.510 align:start position:0% about each other they don't care about 00:03:14.510 --> 00:03:17.260 align:start position:0% about each other they don't care about your<00:03:14.750> token<00:03:15.170> your<00:03:15.320> ICO<00:03:15.800> your<00:03:16.190> your<00:03:16.580> kaya<00:03:16.820> C 00:03:17.260 --> 00:03:17.270 align:start position:0% your token your ICO your your kaya C 00:03:17.270 --> 00:03:19.540 align:start position:0% your token your ICO your your kaya C they<00:03:17.959> just<00:03:18.200> want<00:03:18.380> a<00:03:18.440> username<00:03:18.830> they<00:03:19.190> just<00:03:19.370> want 00:03:19.540 --> 00:03:19.550 align:start position:0% they just want a username they just want 00:03:19.550 --> 00:03:21.610 align:start position:0% they just want a username they just want to<00:03:19.580> use<00:03:19.670> an<00:03:19.880> email<00:03:20.209> if<00:03:20.750> they're<00:03:21.140> gonna<00:03:21.320> buy 00:03:21.610 --> 00:03:21.620 align:start position:0% to use an email if they're gonna buy 00:03:21.620 --> 00:03:23.770 align:start position:0% to use an email if they're gonna buy something<00:03:22.040> why<00:03:22.790> can't<00:03:23.090> they<00:03:23.239> use<00:03:23.270> a<00:03:23.450> credit 00:03:23.770 --> 00:03:23.780 align:start position:0% something why can't they use a credit 00:03:23.780 --> 00:03:25.540 align:start position:0% something why can't they use a credit card<00:03:23.930> they<00:03:24.200> don't<00:03:24.410> understand<00:03:25.070> why<00:03:25.370> they 00:03:25.540 --> 00:03:25.550 align:start position:0% card they don't understand why they 00:03:25.550 --> 00:03:27.850 align:start position:0% card they don't understand why they can't<00:03:25.760> use<00:03:25.910> a<00:03:25.940> credit<00:03:26.239> card<00:03:26.420> and<00:03:26.930> here's 00:03:27.850 --> 00:03:27.860 align:start position:0% can't use a credit card and here's 00:03:27.860 --> 00:03:30.340 align:start position:0% can't use a credit card and here's another<00:03:28.070> thing<00:03:28.370> your<00:03:29.030> users<00:03:29.480> sort<00:03:30.110> of<00:03:30.260> he 00:03:30.340 --> 00:03:30.350 align:start position:0% another thing your users sort of he 00:03:30.350 --> 00:03:33.520 align:start position:0% another thing your users sort of he expects<00:03:31.280> to<00:03:31.400> be<00:03:31.640> able<00:03:31.760> to<00:03:32.120> use<00:03:32.930> multiple 00:03:33.520 --> 00:03:33.530 align:start position:0% expects to be able to use multiple 00:03:33.530 --> 00:03:35.650 align:start position:0% expects to be able to use multiple devices<00:03:33.920> in<00:03:34.280> this<00:03:34.670> with<00:03:34.940> the<00:03:35.120> same<00:03:35.300> account 00:03:35.650 --> 00:03:35.660 align:start position:0% devices in this with the same account 00:03:35.660 --> 00:03:37.449 align:start position:0% devices in this with the same account and<00:03:36.080> that's<00:03:36.440> something<00:03:36.650> like<00:03:36.800> he<00:03:37.010> takes<00:03:37.190> for 00:03:37.449 --> 00:03:37.459 align:start position:0% and that's something like he takes for 00:03:37.459 --> 00:03:40.150 align:start position:0% and that's something like he takes for granted<00:03:37.489> and<00:03:38.330> it's<00:03:38.660> super<00:03:39.230> hard<00:03:39.260> for<00:03:39.770> us<00:03:39.860> to<00:03:40.010> do 00:03:40.150 --> 00:03:40.160 align:start position:0% granted and it's super hard for us to do 00:03:40.160 --> 00:03:42.640 align:start position:0% granted and it's super hard for us to do how<00:03:40.880> do<00:03:40.940> we<00:03:41.090> solve<00:03:41.360> that<00:03:41.540> problem<00:03:41.959> first 00:03:42.640 --> 00:03:42.650 align:start position:0% how do we solve that problem first 00:03:42.650 --> 00:03:45.460 align:start position:0% how do we solve that problem first attempt<00:03:43.070> we<00:03:43.190> try<00:03:43.430> it<00:03:43.489> is<00:03:44.080> every<00:03:45.080> time<00:03:45.110> you 00:03:45.460 --> 00:03:45.470 align:start position:0% attempt we try it is every time you 00:03:45.470 --> 00:03:47.380 align:start position:0% attempt we try it is every time you download<00:03:45.590> an<00:03:45.920> your<00:03:46.040> app<00:03:46.250> you<00:03:46.790> create<00:03:47.090> a<00:03:47.150> new 00:03:47.380 --> 00:03:47.390 align:start position:0% download an your app you create a new 00:03:47.390 --> 00:03:50.320 align:start position:0% download an your app you create a new account<00:03:47.989> you<00:03:48.530> write<00:03:49.220> down<00:03:49.400> your<00:03:49.610> seed<00:03:49.970> phrase 00:03:50.320 --> 00:03:50.330 align:start position:0% account you write down your seed phrase 00:03:50.330 --> 00:03:53.350 align:start position:0% account you write down your seed phrase you<00:03:51.019> have<00:03:51.350> to<00:03:51.650> move<00:03:52.280> each<00:03:52.550> other<00:03:52.730> to<00:03:52.910> it<00:03:53.030> and<00:03:53.269> if 00:03:53.350 --> 00:03:53.360 align:start position:0% you have to move each other to it and if 00:03:53.360 --> 00:03:55.720 align:start position:0% you have to move each other to it and if you<00:03:53.450> want<00:03:53.660> to<00:03:53.810> use<00:03:54.500> the<00:03:54.680> same<00:03:54.890> account<00:03:55.190> let's 00:03:55.720 --> 00:03:55.730 align:start position:0% you want to use the same account let's 00:03:55.730 --> 00:03:58.120 align:start position:0% you want to use the same account let's say<00:03:55.940> like<00:03:56.300> in<00:03:56.540> and<00:03:57.350> then<00:03:57.470> you<00:03:57.560> install<00:03:57.920> it<00:03:58.010> in 00:03:58.120 --> 00:03:58.130 align:start position:0% say like in and then you install it in 00:03:58.130 --> 00:03:59.620 align:start position:0% say like in and then you install it in your<00:03:58.250> iPad<00:03:58.640> and<00:03:58.850> then<00:03:58.940> you<00:03:59.030> have<00:03:59.150> to<00:03:59.269> do<00:03:59.540> the 00:03:59.620 --> 00:03:59.630 align:start position:0% your iPad and then you have to do the 00:03:59.630 --> 00:04:01.509 align:start position:0% your iPad and then you have to do the same<00:03:59.810> process<00:04:00.050> and<00:04:00.380> pay<00:04:00.650> to<00:04:01.280> make<00:04:01.430> the 00:04:01.509 --> 00:04:01.519 align:start position:0% same process and pay to make the 00:04:01.519 --> 00:04:03.160 align:start position:0% same process and pay to make the transaction<00:04:01.880> so<00:04:02.239> you<00:04:02.330> can<00:04:02.450> use<00:04:02.660> both<00:04:02.690> your 00:04:03.160 --> 00:04:03.170 align:start position:0% transaction so you can use both your 00:04:03.170 --> 00:04:06.070 align:start position:0% transaction so you can use both your iPad<00:04:03.590> and<00:04:03.830> your<00:04:03.980> it's<00:04:04.489> crazy<00:04:04.730> then<00:04:05.480> we<00:04:05.870> move<00:04:06.050> to 00:04:06.070 --> 00:04:06.080 align:start position:0% iPad and your it's crazy then we move to 00:04:06.080 --> 00:04:09.160 align:start position:0% iPad and your it's crazy then we move to even<00:04:06.650> worse<00:04:07.400> solution<00:04:07.640> which<00:04:08.420> is<00:04:08.630> let's<00:04:08.930> type 00:04:09.160 --> 00:04:09.170 align:start position:0% even worse solution which is let's type 00:04:09.170 --> 00:04:11.050 align:start position:0% even worse solution which is let's type your<00:04:09.350> private<00:04:09.650> key<00:04:09.769> everywhere<00:04:10.160> oh<00:04:10.370> it's<00:04:10.820> here 00:04:11.050 --> 00:04:11.060 align:start position:0% your private key everywhere oh it's here 00:04:11.060 --> 00:04:14.229 align:start position:0% your private key everywhere oh it's here and<00:04:11.840> I<00:04:11.989> mean<00:04:12.110> there<00:04:12.500> are<00:04:12.620> bad<00:04:12.830> solutions<00:04:13.370> their 00:04:14.229 --> 00:04:14.239 align:start position:0% and I mean there are bad solutions their 00:04:14.239 --> 00:04:16.810 align:start position:0% and I mean there are bad solutions their solutions<00:04:14.870> are<00:04:14.989> so<00:04:15.410> bad<00:04:15.680> that<00:04:15.709> they<00:04:16.040> create<00:04:16.459> a 00:04:16.810 --> 00:04:16.820 align:start position:0% solutions are so bad that they create a 00:04:16.820 --> 00:04:20.650 align:start position:0% solutions are so bad that they create a scam<00:04:17.780> industry<00:04:18.560> so<00:04:18.890> big<00:04:19.250> that<00:04:19.580> Elon<00:04:20.000> Musk<00:04:20.239> goes 00:04:20.650 --> 00:04:20.660 align:start position:0% scam industry so big that Elon Musk goes 00:04:20.660 --> 00:04:23.300 align:start position:0% scam industry so big that Elon Musk goes on<00:04:20.870> Twitter<00:04:21.109> and<00:04:21.350> complains<00:04:21.739> about<00:04:21.950> it 00:04:23.300 --> 00:04:23.310 align:start position:0% on Twitter and complains about it 00:04:23.310 --> 00:04:25.250 align:start position:0% on Twitter and complains about it I'm<00:04:23.490> very<00:04:23.910> happy<00:04:24.180> that<00:04:24.360> we<00:04:24.600> were<00:04:24.660> like<00:04:24.960> sort<00:04:25.139> of 00:04:25.250 --> 00:04:25.260 align:start position:0% I'm very happy that we were like sort of 00:04:25.260 --> 00:04:27.200 align:start position:0% I'm very happy that we were like sort of getting<00:04:25.710> out<00:04:25.920> of<00:04:26.160> this<00:04:26.340> phase<00:04:26.550> where<00:04:26.850> we<00:04:26.970> asked 00:04:27.200 --> 00:04:27.210 align:start position:0% getting out of this phase where we asked 00:04:27.210 --> 00:04:28.910 align:start position:0% getting out of this phase where we asked people<00:04:27.330> to<00:04:27.690> type<00:04:27.900> their<00:04:28.110> private<00:04:28.440> key<00:04:28.590> or<00:04:28.620> tie 00:04:28.910 --> 00:04:28.920 align:start position:0% people to type their private key or tie 00:04:28.920 --> 00:04:32.000 align:start position:0% people to type their private key or tie or<00:04:29.250> the<00:04:29.820> Siege<00:04:30.180> phrase<00:04:30.450> in<00:04:30.840> order<00:04:31.139> to<00:04:31.320> log<00:04:31.830> into 00:04:32.000 --> 00:04:32.010 align:start position:0% or the Siege phrase in order to log into 00:04:32.010 --> 00:04:34.940 align:start position:0% or the Siege phrase in order to log into the<00:04:32.220> app<00:04:32.340> but<00:04:32.940> we're<00:04:33.240> going<00:04:33.630> into<00:04:34.110> I'm<00:04:34.380> seeing 00:04:34.940 --> 00:04:34.950 align:start position:0% the app but we're going into I'm seeing 00:04:34.950 --> 00:04:37.430 align:start position:0% the app but we're going into I'm seeing like<00:04:35.250> a<00:04:35.430> few<00:04:35.760> other<00:04:36.120> startups<00:04:36.810> are<00:04:37.020> trying<00:04:37.350> to 00:04:37.430 --> 00:04:37.440 align:start position:0% like a few other startups are trying to 00:04:37.440 --> 00:04:40.370 align:start position:0% like a few other startups are trying to solve<00:04:37.770> the<00:04:38.040> problem<00:04:38.490> with<00:04:39.150> a<00:04:39.380> wonderful 00:04:40.370 --> 00:04:40.380 align:start position:0% solve the problem with a wonderful 00:04:40.380 --> 00:04:43.310 align:start position:0% solve the problem with a wonderful interface<00:04:40.950> with<00:04:41.580> a<00:04:41.610> username<00:04:42.180> and<00:04:42.600> email<00:04:42.720> you 00:04:43.310 --> 00:04:43.320 align:start position:0% interface with a username and email you 00:04:43.320 --> 00:04:46.159 align:start position:0% interface with a username and email you go<00:04:43.500> to<00:04:43.560> the<00:04:44.070> server<00:04:44.400> it's<00:04:45.120> super<00:04:45.540> slick<00:04:45.930> it's 00:04:46.159 --> 00:04:46.169 align:start position:0% go to the server it's super slick it's 00:04:46.169 --> 00:04:47.300 align:start position:0% go to the server it's super slick it's beautiful 00:04:47.300 --> 00:04:47.310 align:start position:0% beautiful 00:04:47.310 --> 00:04:50.390 align:start position:0% beautiful and<00:04:47.520> I'm<00:04:48.270> better<00:04:48.750> a<00:04:48.990> few<00:04:49.500> people<00:04:49.830> like<00:04:50.130> in<00:04:50.280> the 00:04:50.390 --> 00:04:50.400 align:start position:0% and I'm better a few people like in the 00:04:50.400 --> 00:04:52.070 align:start position:0% and I'm better a few people like in the routiers<00:04:50.669> room<00:04:50.880> that<00:04:51.030> you<00:04:51.120> are<00:04:51.389> working<00:04:51.750> on 00:04:52.070 --> 00:04:52.080 align:start position:0% routiers room that you are working on 00:04:52.080 --> 00:04:54.140 align:start position:0% routiers room that you are working on that<00:04:52.200> solution<00:04:52.620> right<00:04:52.800> now<00:04:52.980> and<00:04:53.580> if<00:04:53.790> you<00:04:53.940> are 00:04:54.140 --> 00:04:54.150 align:start position:0% that solution right now and if you are 00:04:54.150 --> 00:04:59.330 align:start position:0% that solution right now and if you are please<00:04:55.080> stop<00:04:55.640> because<00:04:57.380> if<00:04:58.380> you<00:04:58.440> succeed 00:04:59.330 --> 00:04:59.340 align:start position:0% please stop because if you succeed 00:04:59.340 --> 00:05:01.850 align:start position:0% please stop because if you succeed here's<00:04:59.640> the<00:04:59.760> thing<00:04:59.970> if<00:05:00.510> you<00:05:00.810> succeed<00:05:01.380> doing 00:05:01.850 --> 00:05:01.860 align:start position:0% here's the thing if you succeed doing 00:05:01.860 --> 00:05:05.120 align:start position:0% here's the thing if you succeed doing that<00:05:02.150> we<00:05:03.150> all<00:05:03.419> fail<00:05:03.900> because<00:05:04.590> I'm<00:05:04.950> not 00:05:05.120 --> 00:05:05.130 align:start position:0% that we all fail because I'm not 00:05:05.130 --> 00:05:07.040 align:start position:0% that we all fail because I'm not building<00:05:05.640> we<00:05:06.180> are<00:05:06.210> talking<00:05:06.750> about<00:05:06.870> the 00:05:07.040 --> 00:05:07.050 align:start position:0% building we are talking about the 00:05:07.050 --> 00:05:09.260 align:start position:0% building we are talking about the centralization<00:05:07.410> for<00:05:08.310> you<00:05:08.490> to<00:05:08.700> build<00:05:08.910> the<00:05:09.090> next 00:05:09.260 --> 00:05:09.270 align:start position:0% centralization for you to build the next 00:05:09.270 --> 00:05:11.540 align:start position:0% centralization for you to build the next Facebook<00:05:09.480> Connect<00:05:10.320> because<00:05:10.860> that's<00:05:11.160> what<00:05:11.460> I'm 00:05:11.540 --> 00:05:11.550 align:start position:0% Facebook Connect because that's what I'm 00:05:11.550 --> 00:05:13.670 align:start position:0% Facebook Connect because that's what I'm describing<00:05:11.850> is<00:05:12.210> just<00:05:12.419> Facebook<00:05:13.140> Connect<00:05:13.470> for 00:05:13.670 --> 00:05:13.680 align:start position:0% describing is just Facebook Connect for 00:05:13.680 --> 00:05:15.680 align:start position:0% describing is just Facebook Connect for each<00:05:13.770> even<00:05:14.130> where<00:05:14.490> you<00:05:14.580> keep<00:05:14.850> all<00:05:15.150> the<00:05:15.360> private 00:05:15.680 --> 00:05:15.690 align:start position:0% each even where you keep all the private 00:05:15.690 --> 00:05:18.440 align:start position:0% each even where you keep all the private data<00:05:15.810> with<00:05:16.080> them<00:05:16.290> and<00:05:16.530> like<00:05:17.130> we<00:05:17.880> cannot<00:05:18.090> accept 00:05:18.440 --> 00:05:18.450 align:start position:0% data with them and like we cannot accept 00:05:18.450 --> 00:05:20.750 align:start position:0% data with them and like we cannot accept that<00:05:18.600> like<00:05:19.020> we<00:05:19.320> we<00:05:19.710> don't<00:05:19.950> want<00:05:20.190> that<00:05:20.520> to<00:05:20.729> be 00:05:20.750 --> 00:05:20.760 align:start position:0% that like we we don't want that to be 00:05:20.760 --> 00:05:22.520 align:start position:0% that like we we don't want that to be the<00:05:20.940> future<00:05:21.270> and<00:05:21.750> I<00:05:21.840> think<00:05:22.050> we<00:05:22.139> can<00:05:22.290> do<00:05:22.380> better 00:05:22.520 --> 00:05:22.530 align:start position:0% the future and I think we can do better 00:05:22.530 --> 00:05:25.129 align:start position:0% the future and I think we can do better and<00:05:22.860> how<00:05:23.250> I<00:05:23.280> think<00:05:23.639> we<00:05:23.729> can<00:05:23.880> do<00:05:23.970> better<00:05:24.090> is<00:05:24.479> this 00:05:25.129 --> 00:05:25.139 align:start position:0% and how I think we can do better is this 00:05:25.139 --> 00:05:27.170 align:start position:0% and how I think we can do better is this thing<00:05:25.410> I'm<00:05:25.530> calling<00:05:25.889> universal<00:05:26.370> games<00:05:26.639> it's 00:05:27.170 --> 00:05:27.180 align:start position:0% thing I'm calling universal games it's 00:05:27.180 --> 00:05:29.270 align:start position:0% thing I'm calling universal games it's not<00:05:27.390> a<00:05:27.419> single<00:05:27.810> service<00:05:28.290> is<00:05:28.500> not<00:05:28.650> a<00:05:28.710> single 00:05:29.270 --> 00:05:29.280 align:start position:0% not a single service is not a single 00:05:29.280 --> 00:05:32.240 align:start position:0% not a single service is not a single website<00:05:29.729> is<00:05:30.000> a<00:05:30.060> an<00:05:30.660> architecture<00:05:31.620> that<00:05:31.860> I<00:05:31.890> hope 00:05:32.240 --> 00:05:32.250 align:start position:0% website is a an architecture that I hope 00:05:32.250 --> 00:05:34.969 align:start position:0% website is a an architecture that I hope a<00:05:32.520> lot<00:05:32.729> of<00:05:32.880> that<00:05:33.360> any<00:05:33.570> app<00:05:33.810> can<00:05:33.840> can<00:05:34.680> introduce 00:05:34.969 --> 00:05:34.979 align:start position:0% a lot of that any app can can introduce 00:05:34.979 --> 00:05:39.170 align:start position:0% a lot of that any app can can introduce and<00:05:35.460> hear<00:05:36.180> how<00:05:36.360> it<00:05:36.450> looks<00:05:37.160> this<00:05:38.160> is<00:05:38.220> all<00:05:38.850> like 00:05:39.170 --> 00:05:39.180 align:start position:0% and hear how it looks this is all like 00:05:39.180 --> 00:05:41.300 align:start position:0% and hear how it looks this is all like life<00:05:39.419> code<00:05:39.750> running<00:05:40.110> I'm<00:05:40.289> just<00:05:40.500> I'm<00:05:41.070> just 00:05:41.300 --> 00:05:41.310 align:start position:0% life code running I'm just I'm just 00:05:41.310 --> 00:05:42.920 align:start position:0% life code running I'm just I'm just recording<00:05:41.610> it<00:05:41.850> just<00:05:42.060> because<00:05:42.330> it's<00:05:42.539> easier 00:05:42.920 --> 00:05:42.930 align:start position:0% recording it just because it's easier 00:05:42.930 --> 00:05:46.400 align:start position:0% recording it just because it's easier but<00:05:43.470> the<00:05:43.590> idea<00:05:43.860> is<00:05:44.130> that<00:05:44.419> it's<00:05:45.419> just<00:05:45.810> like<00:05:46.200> a 00:05:46.400 --> 00:05:46.410 align:start position:0% but the idea is that it's just like a 00:05:46.410 --> 00:05:48.560 align:start position:0% but the idea is that it's just like a website<00:05:46.770> where<00:05:47.610> you<00:05:47.729> click<00:05:48.030> and<00:05:48.270> you<00:05:48.360> type 00:05:48.560 --> 00:05:48.570 align:start position:0% website where you click and you type 00:05:48.570 --> 00:05:50.420 align:start position:0% website where you click and you type your<00:05:48.780> name<00:05:48.900> that's<00:05:49.320> all<00:05:49.500> I<00:05:49.590> need<00:05:49.740> to<00:05:49.830> do<00:05:49.950> and<00:05:50.220> I 00:05:50.420 --> 00:05:50.430 align:start position:0% your name that's all I need to do and I 00:05:50.430 --> 00:05:52.400 align:start position:0% your name that's all I need to do and I even<00:05:50.729> like<00:05:50.910> show<00:05:51.210> you<00:05:51.270> multiple<00:05:51.630> user<00:05:52.140> names 00:05:52.400 --> 00:05:52.410 align:start position:0% even like show you multiple user names 00:05:52.410 --> 00:05:53.810 align:start position:0% even like show you multiple user names that<00:05:52.560> you<00:05:52.650> can<00:05:52.800> pick<00:05:53.010> sort<00:05:53.310> of<00:05:53.430> like<00:05:53.550> you<00:05:53.669> can 00:05:53.810 --> 00:05:53.820 align:start position:0% that you can pick sort of like you can 00:05:53.820 --> 00:05:56.090 align:start position:0% that you can pick sort of like you can pick<00:05:54.000> bootable<00:05:54.330> emails<00:05:54.750> and<00:05:55.530> when<00:05:55.740> you<00:05:55.830> do 00:05:56.090 --> 00:05:56.100 align:start position:0% pick bootable emails and when you do 00:05:56.100 --> 00:05:58.550 align:start position:0% pick bootable emails and when you do you're<00:05:56.760> logged<00:05:57.060> in<00:05:57.240> and<00:05:57.570> here's<00:05:58.080> a<00:05:58.169> nice<00:05:58.289> thing 00:05:58.550 --> 00:05:58.560 align:start position:0% you're logged in and here's a nice thing 00:05:58.560 --> 00:06:00.560 align:start position:0% you're logged in and here's a nice thing when<00:05:58.890> you<00:05:59.070> are<00:05:59.160> logged<00:05:59.340> in<00:05:59.550> I'm<00:05:59.789> giving<00:06:00.419> you 00:06:00.560 --> 00:06:00.570 align:start position:0% when you are logged in I'm giving you 00:06:00.570 --> 00:06:02.630 align:start position:0% when you are logged in I'm giving you stuff<00:06:00.930> I<00:06:01.110> create<00:06:01.440> some<00:06:01.650> tokens<00:06:02.070> I'm<00:06:02.220> giving 00:06:02.630 --> 00:06:02.640 align:start position:0% stuff I create some tokens I'm giving 00:06:02.640 --> 00:06:04.719 align:start position:0% stuff I create some tokens I'm giving you<00:06:02.729> tokens<00:06:03.210> the<00:06:03.810> idea<00:06:04.080> being<00:06:04.320> it's 00:06:04.719 --> 00:06:04.729 align:start position:0% you tokens the idea being it's 00:06:04.729 --> 00:06:06.890 align:start position:0% you tokens the idea being it's gamification<00:06:05.729> another<00:06:06.090> word<00:06:06.360> we<00:06:06.539> don't<00:06:06.570> use<00:06:06.870> a 00:06:06.890 --> 00:06:06.900 align:start position:0% gamification another word we don't use a 00:06:06.900 --> 00:06:09.290 align:start position:0% gamification another word we don't use a lot<00:06:07.020> the<00:06:07.710> idea<00:06:07.979> being<00:06:08.280> that<00:06:08.370> every<00:06:08.940> time<00:06:09.150> you 00:06:09.290 --> 00:06:09.300 align:start position:0% lot the idea being that every time you 00:06:09.300 --> 00:06:11.300 align:start position:0% lot the idea being that every time you do<00:06:09.450> something<00:06:10.020> a<00:06:10.140> few<00:06:10.500> actions<00:06:10.950> will<00:06:11.070> cost 00:06:11.300 --> 00:06:11.310 align:start position:0% do something a few actions will cost 00:06:11.310 --> 00:06:13.880 align:start position:0% do something a few actions will cost tokens<00:06:11.880> other<00:06:12.180> actions<00:06:12.840> will<00:06:12.990> get<00:06:13.229> you<00:06:13.410> tokens 00:06:13.880 --> 00:06:13.890 align:start position:0% tokens other actions will get you tokens 00:06:13.890 --> 00:06:16.219 align:start position:0% tokens other actions will get you tokens so<00:06:14.460> you're<00:06:14.789> incentivizing<00:06:15.150> the<00:06:15.630> user<00:06:15.780> to<00:06:16.080> do 00:06:16.219 --> 00:06:16.229 align:start position:0% so you're incentivizing the user to do 00:06:16.229 --> 00:06:17.810 align:start position:0% so you're incentivizing the user to do the<00:06:16.350> right<00:06:16.560> things<00:06:16.890> one<00:06:17.340> of<00:06:17.370> those<00:06:17.580> right 00:06:17.810 --> 00:06:17.820 align:start position:0% the right things one of those right 00:06:17.820 --> 00:06:20.120 align:start position:0% the right things one of those right things<00:06:18.120> is<00:06:18.390> when<00:06:19.140> you<00:06:19.229> create<00:06:19.470> a<00:06:19.500> new<00:06:19.560> username 00:06:20.120 --> 00:06:20.130 align:start position:0% things is when you create a new username 00:06:20.130 --> 00:06:23.150 align:start position:0% things is when you create a new username you<00:06:20.760> get<00:06:20.970> a<00:06:21.000> bunch<00:06:21.240> of<00:06:21.330> tokens<00:06:21.570> and<00:06:22.039> here<00:06:23.039> is 00:06:23.150 --> 00:06:23.160 align:start position:0% you get a bunch of tokens and here is 00:06:23.160 --> 00:06:25.340 align:start position:0% you get a bunch of tokens and here is the<00:06:23.340> app<00:06:23.460> right<00:06:23.669> the<00:06:23.850> app<00:06:24.000> you<00:06:24.570> can<00:06:25.050> see<00:06:25.229> the 00:06:25.340 --> 00:06:25.350 align:start position:0% the app right the app you can see the 00:06:25.350 --> 00:06:28.360 align:start position:0% the app right the app you can see the the<00:06:25.919> the<00:06:26.220> tokens<00:06:26.550> called<00:06:26.729> click<00:06:27.060> and<00:06:27.360> I'm<00:06:28.020> just 00:06:28.360 --> 00:06:28.370 align:start position:0% the the tokens called click and I'm just 00:06:28.370 --> 00:06:31.040 align:start position:0% the the tokens called click and I'm just it's<00:06:29.370> just<00:06:29.640> a<00:06:29.760> single<00:06:30.240> there's<00:06:30.510> a<00:06:30.630> header<00:06:30.840> and 00:06:31.040 --> 00:06:31.050 align:start position:0% it's just a single there's a header and 00:06:31.050 --> 00:06:32.730 align:start position:0% it's just a single there's a header and there's<00:06:31.229> a<00:06:31.320> single 00:06:32.730 --> 00:06:32.740 align:start position:0% there's a single 00:06:32.740 --> 00:06:35.100 align:start position:0% there's a single button<00:06:33.370> and<00:06:33.639> that<00:06:33.789> button<00:06:33.819> is<00:06:34.360> tied<00:06:34.599> with<00:06:34.900> more 00:06:35.100 --> 00:06:35.110 align:start position:0% button and that button is tied with more 00:06:35.110 --> 00:06:37.110 align:start position:0% button and that button is tied with more contract<00:06:35.590> when<00:06:36.039> you<00:06:36.160> click<00:06:36.400> that<00:06:36.430> button<00:06:36.729> it 00:06:37.110 --> 00:06:37.120 align:start position:0% contract when you click that button it 00:06:37.120 --> 00:06:39.809 align:start position:0% contract when you click that button it costs<00:06:37.840> you<00:06:37.960> 1<00:06:38.380> token<00:06:38.650> exactly<00:06:39.160> 1<00:06:39.310> token<00:06:39.699> if 00:06:39.809 --> 00:06:39.819 align:start position:0% costs you 1 token exactly 1 token if 00:06:39.819 --> 00:06:41.760 align:start position:0% costs you 1 token exactly 1 token if forget<00:06:40.150> gas<00:06:40.360> free<00:06:40.599> is<00:06:40.720> an<00:06:40.870> etc<00:06:41.259> just<00:06:41.410> cost<00:06:41.650> you 00:06:41.760 --> 00:06:41.770 align:start position:0% forget gas free is an etc just cost you 00:06:41.770 --> 00:06:44.400 align:start position:0% forget gas free is an etc just cost you 1<00:06:41.889> token<00:06:42.250> and<00:06:42.370> when<00:06:42.910> you<00:06:43.000> click<00:06:43.240> it<00:06:43.349> you<00:06:44.349> can 00:06:44.400 --> 00:06:44.410 align:start position:0% 1 token and when you click it you can 00:06:44.410 --> 00:06:47.279 align:start position:0% 1 token and when you click it you can see<00:06:44.590> that<00:06:45.099> your<00:06:45.880> name<00:06:46.060> is<00:06:46.419> down<00:06:46.810> there<00:06:47.050> on<00:06:47.259> a 00:06:47.279 --> 00:06:47.289 align:start position:0% see that your name is down there on a 00:06:47.289 --> 00:06:48.960 align:start position:0% see that your name is down there on a list<00:06:47.590> that<00:06:47.710> people<00:06:47.949> who<00:06:48.250> press<00:06:48.520> the<00:06:48.669> bottom 00:06:48.960 --> 00:06:48.970 align:start position:0% list that people who press the bottom 00:06:48.970 --> 00:06:50.550 align:start position:0% list that people who press the bottom the<00:06:49.419> app<00:06:49.509> tells<00:06:49.750> nothing<00:06:49.870> right<00:06:50.229> you<00:06:50.349> just 00:06:50.550 --> 00:06:50.560 align:start position:0% the app tells nothing right you just 00:06:50.560 --> 00:06:52.080 align:start position:0% the app tells nothing right you just click<00:06:50.830> it<00:06:50.979> and<00:06:51.009> it<00:06:51.250> says<00:06:51.490> you<00:06:51.729> click<00:06:51.970> the 00:06:52.080 --> 00:06:52.090 align:start position:0% click it and it says you click the 00:06:52.090 --> 00:06:54.210 align:start position:0% click it and it says you click the button<00:06:52.389> but<00:06:53.050> the<00:06:53.110> interesting<00:06:53.530> thing<00:06:53.800> is<00:06:54.160> that 00:06:54.210 --> 00:06:54.220 align:start position:0% button but the interesting thing is that 00:06:54.220 --> 00:06:56.850 align:start position:0% button but the interesting thing is that you<00:06:55.090> just<00:06:55.380> interacted<00:06:56.380> with<00:06:56.470> a<00:06:56.560> smart 00:06:56.850 --> 00:06:56.860 align:start position:0% you just interacted with a smart 00:06:56.860 --> 00:06:58.950 align:start position:0% you just interacted with a smart contract<00:06:57.130> the<00:06:57.460> first<00:06:57.669> time<00:06:57.970> on<00:06:58.270> a<00:06:58.630> normal 00:06:58.950 --> 00:06:58.960 align:start position:0% contract the first time on a normal 00:06:58.960 --> 00:07:00.420 align:start position:0% contract the first time on a normal browser<00:06:59.319> without<00:06:59.740> having<00:07:00.160> to<00:07:00.250> download 00:07:00.420 --> 00:07:00.430 align:start position:0% browser without having to download 00:07:00.430 --> 00:07:03.480 align:start position:0% browser without having to download anything<00:07:00.880> to<00:07:01.180> sign<00:07:01.389> up<00:07:01.569> anything<00:07:02.139> and<00:07:02.319> for<00:07:03.280> the 00:07:03.480 --> 00:07:03.490 align:start position:0% anything to sign up anything and for the 00:07:03.490 --> 00:07:06.360 align:start position:0% anything to sign up anything and for the smart<00:07:03.699> contract<00:07:03.910> itself<00:07:04.479> it<00:07:05.139> sounds<00:07:05.919> like<00:07:06.069> you 00:07:06.360 --> 00:07:06.370 align:start position:0% smart contract itself it sounds like you 00:07:06.370 --> 00:07:10.070 align:start position:0% smart contract itself it sounds like you are<00:07:06.669> you<00:07:07.569> are<00:07:07.720> just<00:07:08.139> a<00:07:08.380> normal<00:07:08.680> human<00:07:09.159> account 00:07:10.070 --> 00:07:10.080 align:start position:0% are you are just a normal human account 00:07:10.080 --> 00:07:12.600 align:start position:0% are you are just a normal human account ok<00:07:11.080> but<00:07:11.229> it<00:07:11.380> sounds<00:07:11.710> weird<00:07:11.860> Alex<00:07:12.250> there's<00:07:12.520> no 00:07:12.600 --> 00:07:12.610 align:start position:0% ok but it sounds weird Alex there's no 00:07:12.610 --> 00:07:14.159 align:start position:0% ok but it sounds weird Alex there's no password<00:07:13.030> there's<00:07:13.210> no<00:07:13.300> nothing<00:07:13.750> how<00:07:13.960> do<00:07:14.020> I 00:07:14.159 --> 00:07:14.169 align:start position:0% password there's no nothing how do I 00:07:14.169 --> 00:07:17.010 align:start position:0% password there's no nothing how do I even<00:07:14.470> like<00:07:14.740> sign<00:07:15.220> up<00:07:15.430> with<00:07:15.669> an<00:07:16.569> iPhone<00:07:16.900> let's 00:07:17.010 --> 00:07:17.020 align:start position:0% even like sign up with an iPhone let's 00:07:17.020 --> 00:07:19.350 align:start position:0% even like sign up with an iPhone let's say<00:07:17.199> here's<00:07:17.949> how<00:07:18.099> we<00:07:18.159> do<00:07:18.340> it<00:07:18.520> you<00:07:18.909> just<00:07:19.120> type 00:07:19.350 --> 00:07:19.360 align:start position:0% say here's how we do it you just type 00:07:19.360 --> 00:07:22.770 align:start position:0% say here's how we do it you just type your<00:07:19.810> name<00:07:20.610> what's<00:07:21.610> your<00:07:21.759> like<00:07:22.120> you<00:07:22.330> say<00:07:22.569> look 00:07:22.770 --> 00:07:22.780 align:start position:0% your name what's your like you say look 00:07:22.780 --> 00:07:25.080 align:start position:0% your name what's your like you say look I'm<00:07:22.960> Bob<00:07:23.199> and<00:07:23.500> the<00:07:23.590> nice<00:07:23.710> thing<00:07:24.009> is<00:07:24.039> that<00:07:24.430> once 00:07:25.080 --> 00:07:25.090 align:start position:0% I'm Bob and the nice thing is that once 00:07:25.090 --> 00:07:27.120 align:start position:0% I'm Bob and the nice thing is that once I<00:07:25.330> can<00:07:25.509> detect<00:07:25.870> that<00:07:25.990> you<00:07:26.139> are<00:07:26.259> Bob<00:07:26.470> I<00:07:26.770> can<00:07:26.919> see 00:07:27.120 --> 00:07:27.130 align:start position:0% I can detect that you are Bob I can see 00:07:27.130 --> 00:07:29.339 align:start position:0% I can detect that you are Bob I can see look<00:07:27.310> Bob<00:07:27.669> already<00:07:27.940> exists<00:07:28.389> so<00:07:29.050> instead<00:07:29.289> of 00:07:29.339 --> 00:07:29.349 align:start position:0% look Bob already exists so instead of 00:07:29.349 --> 00:07:30.809 align:start position:0% look Bob already exists so instead of creating<00:07:29.590> a<00:07:29.860> new<00:07:29.889> username<00:07:30.280> I'm<00:07:30.550> gonna 00:07:30.809 --> 00:07:30.819 align:start position:0% creating a new username I'm gonna 00:07:30.819 --> 00:07:32.939 align:start position:0% creating a new username I'm gonna connect<00:07:31.240> you<00:07:31.330> with<00:07:31.630> Bob<00:07:31.900> and<00:07:32.409> when<00:07:32.650> you<00:07:32.740> click 00:07:32.939 --> 00:07:32.949 align:start position:0% connect you with Bob and when you click 00:07:32.949 --> 00:07:33.839 align:start position:0% connect you with Bob and when you click connect<00:07:33.220> to<00:07:33.280> Bob 00:07:33.839 --> 00:07:33.849 align:start position:0% connect to Bob 00:07:33.849 --> 00:07:36.120 align:start position:0% connect to Bob I<00:07:33.880> will<00:07:34.150> receive<00:07:34.479> a<00:07:34.539> person<00:07:35.009> notification<00:07:36.009> on 00:07:36.120 --> 00:07:36.130 align:start position:0% I will receive a person notification on 00:07:36.130 --> 00:07:38.490 align:start position:0% I will receive a person notification on my<00:07:36.490> browser<00:07:36.699> and<00:07:37.060> I'm<00:07:37.750> gonna<00:07:37.990> click<00:07:38.229> there<00:07:38.469> and 00:07:38.490 --> 00:07:38.500 align:start position:0% my browser and I'm gonna click there and 00:07:38.500 --> 00:07:41.159 align:start position:0% my browser and I'm gonna click there and say<00:07:38.830> yeah<00:07:39.280> that's<00:07:39.849> me<00:07:40.090> that<00:07:40.449> the<00:07:40.690> person<00:07:41.050> that 00:07:41.159 --> 00:07:41.169 align:start position:0% say yeah that's me that the person that 00:07:41.169 --> 00:07:43.529 align:start position:0% say yeah that's me that the person that was<00:07:41.259> trying<00:07:41.469> to<00:07:41.680> connect<00:07:42.130> on<00:07:42.370> an<00:07:42.759> iPhone<00:07:43.240> on 00:07:43.529 --> 00:07:43.539 align:start position:0% was trying to connect on an iPhone on 00:07:43.539 --> 00:07:46.950 align:start position:0% was trying to connect on an iPhone on this<00:07:43.810> IP<00:07:44.139> on<00:07:44.740> at<00:07:45.280> that<00:07:45.460> time<00:07:45.539> that's<00:07:46.539> me<00:07:46.780> you 00:07:46.950 --> 00:07:46.960 align:start position:0% this IP on at that time that's me you 00:07:46.960 --> 00:07:48.959 align:start position:0% this IP on at that time that's me you can<00:07:47.110> accept<00:07:47.409> it<00:07:47.560> and<00:07:47.770> when<00:07:48.340> you<00:07:48.430> accept<00:07:48.789> it 00:07:48.959 --> 00:07:48.969 align:start position:0% can accept it and when you accept it 00:07:48.969 --> 00:07:51.330 align:start position:0% can accept it and when you accept it what<00:07:49.270> happens<00:07:49.690> is<00:07:49.870> that<00:07:49.900> you're<00:07:50.440> both<00:07:50.889> your 00:07:51.330 --> 00:07:51.340 align:start position:0% what happens is that you're both your 00:07:51.340 --> 00:07:54.959 align:start position:0% what happens is that you're both your devices<00:07:52.270> will<00:07:52.360> be<00:07:52.479> synchronized<00:07:52.719> and<00:07:53.969> you'll 00:07:54.959 --> 00:07:54.969 align:start position:0% devices will be synchronized and you'll 00:07:54.969 --> 00:07:57.749 align:start position:0% devices will be synchronized and you'll be<00:07:55.120> able<00:07:55.210> to<00:07:55.419> see<00:07:55.599> soon<00:07:55.810> that<00:07:56.169> the<00:07:56.710> like<00:07:57.190> the<00:07:57.400> on 00:07:57.749 --> 00:07:57.759 align:start position:0% be able to see soon that the like the on 00:07:57.759 --> 00:07:59.790 align:start position:0% be able to see soon that the like the on the<00:07:57.969> top<00:07:58.300> there<00:07:58.509> there's<00:07:58.840> like<00:07:59.050> your<00:07:59.320> your 00:07:59.790 --> 00:07:59.800 align:start position:0% the top there there's like your your 00:07:59.800 --> 00:08:02.969 align:start position:0% the top there there's like your your your<00:08:00.389> yeah<00:08:01.389> and<00:08:01.599> you<00:08:01.690> just<00:08:01.930> get<00:08:02.110> more<00:08:02.469> tokens 00:08:02.969 --> 00:08:02.979 align:start position:0% your yeah and you just get more tokens 00:08:02.979 --> 00:08:04.649 align:start position:0% your yeah and you just get more tokens because<00:08:03.219> you<00:08:03.310> added<00:08:03.580> a<00:08:03.669> new<00:08:03.789> device<00:08:04.090> and<00:08:04.389> you 00:08:04.649 --> 00:08:04.659 align:start position:0% because you added a new device and you 00:08:04.659 --> 00:08:06.450 align:start position:0% because you added a new device and you can<00:08:04.719> see<00:08:05.050> it's<00:08:05.289> the<00:08:05.409> same<00:08:05.440> address<00:08:05.979> the<00:08:06.250> same 00:08:06.450 --> 00:08:06.460 align:start position:0% can see it's the same address the same 00:08:06.460 --> 00:08:09.029 align:start position:0% can see it's the same address the same icon<00:08:06.940> because<00:08:07.690> from<00:08:08.289> the<00:08:08.409> point<00:08:08.560> of<00:08:08.770> view<00:08:08.949> of 00:08:09.029 --> 00:08:09.039 align:start position:0% icon because from the point of view of 00:08:09.039 --> 00:08:12.120 align:start position:0% icon because from the point of view of the<00:08:09.550> of<00:08:09.759> the<00:08:09.909> app<00:08:10.270> you<00:08:10.990> are<00:08:11.229> using<00:08:11.590> the<00:08:11.919> same<00:08:12.099> e 00:08:12.120 --> 00:08:12.130 align:start position:0% the of the app you are using the same e 00:08:12.130 --> 00:08:14.010 align:start position:0% the of the app you are using the same e to<00:08:12.250> your<00:08:12.400> account<00:08:12.669> and<00:08:13.060> whatever<00:08:13.419> you<00:08:13.569> do<00:08:13.810> in 00:08:14.010 --> 00:08:14.020 align:start position:0% to your account and whatever you do in 00:08:14.020 --> 00:08:15.749 align:start position:0% to your account and whatever you do in one<00:08:14.199> side<00:08:14.500> it<00:08:14.949> will<00:08:15.099> reflect<00:08:15.340> to<00:08:15.550> the<00:08:15.610> other 00:08:15.749 --> 00:08:15.759 align:start position:0% one side it will reflect to the other 00:08:15.759 --> 00:08:18.059 align:start position:0% one side it will reflect to the other right<00:08:16.030> so<00:08:16.060> if<00:08:16.240> I<00:08:16.330> click<00:08:16.569> on<00:08:16.780> the<00:08:16.870> phone<00:08:17.110> it<00:08:17.409> will 00:08:18.059 --> 00:08:18.069 align:start position:0% right so if I click on the phone it will 00:08:18.069 --> 00:08:19.350 align:start position:0% right so if I click on the phone it will click<00:08:18.280> on<00:08:18.310> the<00:08:18.460> desktop<00:08:18.819> if<00:08:18.969> I<00:08:19.030> click<00:08:19.210> on<00:08:19.300> a 00:08:19.350 --> 00:08:19.360 align:start position:0% click on the desktop if I click on a 00:08:19.360 --> 00:08:21.089 align:start position:0% click on the desktop if I click on a desktop<00:08:19.630> it<00:08:19.900> clicks<00:08:20.080> on<00:08:20.199> the<00:08:20.289> phone<00:08:20.469> and 00:08:21.089 --> 00:08:21.099 align:start position:0% desktop it clicks on the phone and 00:08:21.099 --> 00:08:24.570 align:start position:0% desktop it clicks on the phone and here's<00:08:22.090> another<00:08:22.210> thing<00:08:22.419> the<00:08:23.199> the<00:08:23.979> the<00:08:24.340> phone 00:08:24.570 --> 00:08:24.580 align:start position:0% here's another thing the the the phone 00:08:24.580 --> 00:08:26.909 align:start position:0% here's another thing the the the phone itself<00:08:25.000> is<00:08:25.419> not<00:08:25.569> a<00:08:25.630> master<00:08:26.050> key<00:08:26.259> I'm<00:08:26.409> not<00:08:26.560> doing 00:08:26.909 --> 00:08:26.919 align:start position:0% itself is not a master key I'm not doing 00:08:26.919 --> 00:08:29.370 align:start position:0% itself is not a master key I'm not doing this<00:08:27.219> thing<00:08:27.669> where<00:08:28.120> you<00:08:28.690> do<00:08:28.870> something<00:08:29.110> on<00:08:29.289> the 00:08:29.370 --> 00:08:29.380 align:start position:0% this thing where you do something on the 00:08:29.380 --> 00:08:31.110 align:start position:0% this thing where you do something on the desktop<00:08:29.770> and<00:08:29.949> then<00:08:30.069> you<00:08:30.130> have<00:08:30.340> to<00:08:30.490> approve<00:08:30.789> in 00:08:31.110 --> 00:08:31.120 align:start position:0% desktop and then you have to approve in 00:08:31.120 --> 00:08:33.719 align:start position:0% desktop and then you have to approve in your<00:08:31.300> master<00:08:31.840> phone<00:08:32.140> device<00:08:32.529> know<00:08:33.219> every 00:08:33.719 --> 00:08:33.729 align:start position:0% your master phone device know every 00:08:33.729 --> 00:08:36.870 align:start position:0% your master phone device know every device<00:08:34.060> you<00:08:34.680> every<00:08:35.680> device<00:08:35.950> you<00:08:36.010> add<00:08:36.399> every 00:08:36.870 --> 00:08:36.880 align:start position:0% device you every device you add every 00:08:36.880 --> 00:08:38.340 align:start position:0% device you every device you add every new<00:08:37.180> app<00:08:37.479> you 00:08:38.340 --> 00:08:38.350 align:start position:0% new app you 00:08:38.350 --> 00:08:41.160 align:start position:0% new app you can<00:08:38.710> be<00:08:38.950> an<00:08:39.220> approval<00:08:39.730> or<00:08:39.910> a<00:08:39.940> signer<00:08:40.300> for<00:08:40.660> the 00:08:41.160 --> 00:08:41.170 align:start position:0% can be an approval or a signer for the 00:08:41.170 --> 00:08:44.130 align:start position:0% can be an approval or a signer for the other<00:08:41.290> apps<00:08:41.590> and<00:08:41.980> which<00:08:42.880> already<00:08:43.140> great 00:08:44.130 --> 00:08:44.140 align:start position:0% other apps and which already great 00:08:44.140 --> 00:08:45.390 align:start position:0% other apps and which already great because<00:08:44.440> you<00:08:44.530> can<00:08:44.650> have<00:08:44.800> multiple<00:08:45.040> devices 00:08:45.390 --> 00:08:45.400 align:start position:0% because you can have multiple devices 00:08:45.400 --> 00:08:47.310 align:start position:0% because you can have multiple devices multiple<00:08:46.120> apps<00:08:46.300> everyone<00:08:46.720> using<00:08:47.050> the<00:08:47.140> same 00:08:47.310 --> 00:08:47.320 align:start position:0% multiple apps everyone using the same 00:08:47.320 --> 00:08:49.860 align:start position:0% multiple apps everyone using the same username<00:08:47.620> but<00:08:48.340> what<00:08:48.580> if<00:08:48.730> like<00:08:49.180> if<00:08:49.360> I<00:08:49.510> lose<00:08:49.690> all 00:08:49.860 --> 00:08:49.870 align:start position:0% username but what if like if I lose all 00:08:49.870 --> 00:08:51.750 align:start position:0% username but what if like if I lose all my<00:08:50.020> devices<00:08:50.170> well<00:08:50.650> if<00:08:50.920> you<00:08:51.280> lose<00:08:51.460> all<00:08:51.730> your 00:08:51.750 --> 00:08:51.760 align:start position:0% my devices well if you lose all your 00:08:51.760 --> 00:08:54.240 align:start position:0% my devices well if you lose all your devices<00:08:52.120> we<00:08:52.840> can<00:08:52.870> do<00:08:53.200> something<00:08:53.590> extra<00:08:53.980> where 00:08:54.240 --> 00:08:54.250 align:start position:0% devices we can do something extra where 00:08:54.250 --> 00:08:56.430 align:start position:0% devices we can do something extra where I<00:08:54.280> can<00:08:54.520> create<00:08:54.760> a<00:08:55.180> new<00:08:55.600> code<00:08:55.840> for<00:08:55.870> you<00:08:56.200> I'm<00:08:56.350> not 00:08:56.430 --> 00:08:56.440 align:start position:0% I can create a new code for you I'm not 00:08:56.440 --> 00:08:58.110 align:start position:0% I can create a new code for you I'm not just<00:08:56.680> gonna<00:08:56.860> go<00:08:57.070> very<00:08:57.280> quickly<00:08:57.550> the<00:08:57.760> idea<00:08:58.000> is 00:08:58.110 --> 00:08:58.120 align:start position:0% just gonna go very quickly the idea is 00:08:58.120 --> 00:09:00.180 align:start position:0% just gonna go very quickly the idea is just<00:08:58.150> you<00:08:58.840> click<00:08:59.110> it<00:08:59.260> generate<00:08:59.590> some<00:08:59.770> codes<00:08:59.980> on 00:09:00.180 --> 00:09:00.190 align:start position:0% just you click it generate some codes on 00:09:00.190 --> 00:09:01.560 align:start position:0% just you click it generate some codes on the<00:09:00.310> on<00:09:00.430> the<00:09:00.520> browser<00:09:00.760> I'm<00:09:01.060> not<00:09:01.240> actually 00:09:01.560 --> 00:09:01.570 align:start position:0% the on the browser I'm not actually 00:09:01.570 --> 00:09:02.640 align:start position:0% the on the browser I'm not actually backing<00:09:01.810> up<00:09:02.080> the<00:09:02.200> keys 00:09:02.640 --> 00:09:02.650 align:start position:0% backing up the keys 00:09:02.650 --> 00:09:05.040 align:start position:0% backing up the keys I'm<00:09:02.920> just<00:09:03.190> generating<00:09:03.760> new<00:09:04.030> codes<00:09:04.390> on<00:09:04.750> the 00:09:05.040 --> 00:09:05.050 align:start position:0% I'm just generating new codes on the 00:09:05.050 --> 00:09:07.800 align:start position:0% I'm just generating new codes on the browser<00:09:05.320> which<00:09:06.190> you<00:09:06.370> be<00:09:06.520> able<00:09:06.820> to<00:09:06.970> use<00:09:07.210> that's 00:09:07.800 --> 00:09:07.810 align:start position:0% browser which you be able to use that's 00:09:07.810 --> 00:09:10.170 align:start position:0% browser which you be able to use that's the<00:09:07.960> code<00:09:08.230> you<00:09:08.800> can<00:09:08.980> print<00:09:09.310> it<00:09:09.490> and<00:09:09.700> then<00:09:09.910> maybe 00:09:10.170 --> 00:09:10.180 align:start position:0% the code you can print it and then maybe 00:09:10.180 --> 00:09:12.300 align:start position:0% the code you can print it and then maybe you<00:09:10.390> cut<00:09:10.660> it<00:09:10.780> cut<00:09:10.960> them<00:09:11.170> out<00:09:11.320> keep<00:09:12.100> them 00:09:12.300 --> 00:09:12.310 align:start position:0% you cut it cut them out keep them 00:09:12.310 --> 00:09:14.430 align:start position:0% you cut it cut them out keep them one-year<00:09:12.730> safe<00:09:13.120> when<00:09:13.540> in<00:09:13.660> your<00:09:13.720> mom's<00:09:14.110> house 00:09:14.430 --> 00:09:14.440 align:start position:0% one-year safe when in your mom's house 00:09:14.440 --> 00:09:16.200 align:start position:0% one-year safe when in your mom's house the<00:09:14.800> other<00:09:14.920> if<00:09:15.100> your<00:09:15.220> lawyers<00:09:15.640> I<00:09:15.880> don't<00:09:16.150> know 00:09:16.200 --> 00:09:16.210 align:start position:0% the other if your lawyers I don't know 00:09:16.210 --> 00:09:18.690 align:start position:0% the other if your lawyers I don't know maybe<00:09:16.720> laminate<00:09:17.290> them<00:09:17.500> if<00:09:17.740> you<00:09:17.830> want<00:09:18.010> but<00:09:18.520> the 00:09:18.690 --> 00:09:18.700 align:start position:0% maybe laminate them if you want but the 00:09:18.700 --> 00:09:21.150 align:start position:0% maybe laminate them if you want but the idea<00:09:19.000> being<00:09:19.390> if<00:09:19.870> you<00:09:20.140> lose<00:09:20.350> all<00:09:20.620> your<00:09:20.650> devices 00:09:21.150 --> 00:09:21.160 align:start position:0% idea being if you lose all your devices 00:09:21.160 --> 00:09:24.480 align:start position:0% idea being if you lose all your devices you<00:09:21.670> can<00:09:21.880> still<00:09:22.150> have<00:09:22.300> access<00:09:22.540> to<00:09:22.870> it<00:09:23.140> via<00:09:23.920> this 00:09:24.480 --> 00:09:24.490 align:start position:0% you can still have access to it via this 00:09:24.490 --> 00:09:26.820 align:start position:0% you can still have access to it via this the<00:09:25.030> recovery<00:09:25.720> code<00:09:25.960> which<00:09:26.260> is<00:09:26.410> sort<00:09:26.650> of<00:09:26.770> very 00:09:26.820 --> 00:09:26.830 align:start position:0% the recovery code which is sort of very 00:09:26.830 --> 00:09:30.210 align:start position:0% the recovery code which is sort of very easy<00:09:27.280> and<00:09:27.700> how<00:09:28.210> do<00:09:28.270> you<00:09:28.510> sort<00:09:28.960> of<00:09:29.140> save<00:09:30.070> money 00:09:30.210 --> 00:09:30.220 align:start position:0% easy and how do you sort of save money 00:09:30.220 --> 00:09:32.340 align:start position:0% easy and how do you sort of save money when<00:09:30.640> you<00:09:30.730> click<00:09:30.970> the<00:09:31.120> backup<00:09:31.570> code<00:09:31.780> we<00:09:32.200> have 00:09:32.340 --> 00:09:32.350 align:start position:0% when you click the backup code we have 00:09:32.350 --> 00:09:33.870 align:start position:0% when you click the backup code we have like<00:09:32.500> this<00:09:32.650> three-step<00:09:33.160> security<00:09:33.700> thing 00:09:33.870 --> 00:09:33.880 align:start position:0% like this three-step security thing 00:09:33.880 --> 00:09:35.580 align:start position:0% like this three-step security thing where<00:09:34.120> every<00:09:34.780> time<00:09:34.930> you<00:09:34.990> do<00:09:35.170> something<00:09:35.530> you 00:09:35.580 --> 00:09:35.590 align:start position:0% where every time you do something you 00:09:35.590 --> 00:09:37.770 align:start position:0% where every time you do something you like<00:09:35.800> you<00:09:36.400> get<00:09:36.580> more<00:09:36.730> tokens<00:09:37.150> and<00:09:37.360> bling<00:09:37.750> you 00:09:37.770 --> 00:09:37.780 align:start position:0% like you get more tokens and bling you 00:09:37.780 --> 00:09:41.880 align:start position:0% like you get more tokens and bling you just<00:09:38.230> got<00:09:38.440> your<00:09:38.710> your<00:09:39.160> latest<00:09:40.590> thing<00:09:41.590> checked 00:09:41.880 --> 00:09:41.890 align:start position:0% just got your your latest thing checked 00:09:41.890 --> 00:09:44.370 align:start position:0% just got your your latest thing checked out<00:09:42.040> so<00:09:42.310> you're<00:09:42.490> super<00:09:42.880> safe<00:09:43.120> how<00:09:43.870> do<00:09:43.930> you<00:09:44.110> do 00:09:44.370 --> 00:09:44.380 align:start position:0% out so you're super safe how do you do 00:09:44.380 --> 00:09:47.730 align:start position:0% out so you're super safe how do you do recovery<00:09:45.160> then<00:09:45.370> just<00:09:46.360> same<00:09:46.960> thing<00:09:46.990> let's<00:09:47.650> say 00:09:47.730 --> 00:09:47.740 align:start position:0% recovery then just same thing let's say 00:09:47.740 --> 00:09:49.410 align:start position:0% recovery then just same thing let's say you<00:09:47.860> lost<00:09:48.040> all<00:09:48.310> your<00:09:48.340> tokens<00:09:48.850> go<00:09:49.180> on<00:09:49.330> the 00:09:49.410 --> 00:09:49.420 align:start position:0% you lost all your tokens go on the 00:09:49.420 --> 00:09:51.870 align:start position:0% you lost all your tokens go on the website<00:09:49.570> type<00:09:50.350> I<00:09:50.560> am<00:09:50.770> Bob<00:09:51.130> and<00:09:51.490> instead<00:09:51.820> of 00:09:51.870 --> 00:09:51.880 align:start position:0% website type I am Bob and instead of 00:09:51.880 --> 00:09:53.280 align:start position:0% website type I am Bob and instead of clicking<00:09:52.000> connect<00:09:52.450> notice<00:09:52.930> that<00:09:53.020> there<00:09:53.170> is<00:09:53.200> a 00:09:53.280 --> 00:09:53.290 align:start position:0% clicking connect notice that there is a 00:09:53.290 --> 00:09:55.200 align:start position:0% clicking connect notice that there is a recovery<00:09:53.590> button<00:09:54.070> on<00:09:54.640> the<00:09:54.820> recover<00:09:55.120> button 00:09:55.200 --> 00:09:55.210 align:start position:0% recovery button on the recover button 00:09:55.210 --> 00:09:59.130 align:start position:0% recovery button on the recover button you<00:09:55.720> just<00:09:55.750> type<00:09:56.170> one<00:09:56.470> of<00:09:56.500> those<00:09:56.740> codes<00:09:57.130> and<00:09:58.140> I'm 00:09:59.130 --> 00:09:59.140 align:start position:0% you just type one of those codes and I'm 00:09:59.140 --> 00:10:01.050 align:start position:0% you just type one of those codes and I'm actually<00:09:59.380> typing<00:09:59.710> it<00:09:59.980> instead<00:10:00.310> of<00:10:00.370> just<00:10:00.730> copy 00:10:01.050 --> 00:10:01.060 align:start position:0% actually typing it instead of just copy 00:10:01.060 --> 00:10:03.060 align:start position:0% actually typing it instead of just copy pasting<00:10:01.540> it<00:10:01.660> to<00:10:01.750> see<00:10:02.020> it<00:10:02.080> to<00:10:02.260> show<00:10:02.440> you<00:10:02.500> it's 00:10:03.060 --> 00:10:03.070 align:start position:0% pasting it to see it to show you it's 00:10:03.070 --> 00:10:04.710 align:start position:0% pasting it to see it to show you it's not<00:10:03.220> something<00:10:03.610> as<00:10:03.730> complex<00:10:04.150> that<00:10:04.390> you<00:10:04.480> need 00:10:04.710 --> 00:10:04.720 align:start position:0% not something as complex that you need 00:10:04.720 --> 00:10:07.410 align:start position:0% not something as complex that you need to<00:10:04.870> actually<00:10:05.200> have<00:10:05.620> a<00:10:05.680> QR<00:10:06.130> code<00:10:06.160> or<00:10:06.850> a<00:10:06.880> digital 00:10:07.410 --> 00:10:07.420 align:start position:0% to actually have a QR code or a digital 00:10:07.420 --> 00:10:08.730 align:start position:0% to actually have a QR code or a digital file<00:10:07.600> it's<00:10:08.050> something<00:10:08.320> that<00:10:08.410> you<00:10:08.530> can 00:10:08.730 --> 00:10:08.740 align:start position:0% file it's something that you can 00:10:08.740 --> 00:10:10.650 align:start position:0% file it's something that you can actually<00:10:08.950> write<00:10:09.310> you<00:10:09.940> might<00:10:10.150> be<00:10:10.330> able<00:10:10.570> to 00:10:10.650 --> 00:10:10.660 align:start position:0% actually write you might be able to 00:10:10.660 --> 00:10:12.060 align:start position:0% actually write you might be able to remember<00:10:10.930> it<00:10:11.080> because<00:10:11.320> it<00:10:11.560> sounds<00:10:11.890> like<00:10:11.920> a 00:10:12.060 --> 00:10:12.070 align:start position:0% remember it because it sounds like a 00:10:12.070 --> 00:10:14.730 align:start position:0% remember it because it sounds like a Star<00:10:12.400> Wars<00:10:12.430> planet<00:10:12.850> but<00:10:13.480> it's<00:10:13.600> more<00:10:13.840> it's<00:10:14.620> not 00:10:14.730 --> 00:10:14.740 align:start position:0% Star Wars planet but it's more it's not 00:10:14.740 --> 00:10:17.010 align:start position:0% Star Wars planet but it's more it's not memorable<00:10:15.490> which<00:10:15.820> is<00:10:15.940> writable<00:10:16.630> you<00:10:16.840> can 00:10:17.010 --> 00:10:17.020 align:start position:0% memorable which is writable you can 00:10:17.020 --> 00:10:18.930 align:start position:0% memorable which is writable you can write<00:10:17.260> that<00:10:17.530> down<00:10:17.830> in<00:10:18.400> a<00:10:18.520> piece<00:10:18.670> of<00:10:18.700> paper 00:10:18.930 --> 00:10:18.940 align:start position:0% write that down in a piece of paper 00:10:18.940 --> 00:10:22.440 align:start position:0% write that down in a piece of paper somewhere<00:10:19.360> and<00:10:20.160> when<00:10:21.160> you<00:10:21.280> do<00:10:21.490> you're<00:10:22.270> logged 00:10:22.440 --> 00:10:22.450 align:start position:0% somewhere and when you do you're logged 00:10:22.450 --> 00:10:25.530 align:start position:0% somewhere and when you do you're logged in<00:10:22.660> notice<00:10:23.620> something<00:10:23.950> that<00:10:24.100> I<00:10:24.250> was<00:10:25.180> able<00:10:25.510> to 00:10:25.530 --> 00:10:25.540 align:start position:0% in notice something that I was able to 00:10:25.540 --> 00:10:27.900 align:start position:0% in notice something that I was able to log<00:10:26.290> in<00:10:26.470> in<00:10:26.680> multiple<00:10:27.070> devices<00:10:27.370> I<00:10:27.670> have<00:10:27.700> a 00:10:27.900 --> 00:10:27.910 align:start position:0% log in in multiple devices I have a 00:10:27.910 --> 00:10:31.440 align:start position:0% log in in multiple devices I have a paper<00:10:28.690> wallet<00:10:29.290> I<00:10:29.580> am<00:10:30.580> showing<00:10:30.970> a<00:10:31.090> bunch<00:10:31.270> of 00:10:31.440 --> 00:10:31.450 align:start position:0% paper wallet I am showing a bunch of 00:10:31.450 --> 00:10:33.690 align:start position:0% paper wallet I am showing a bunch of stuff<00:10:31.720> here<00:10:32.320> are<00:10:32.410> the<00:10:32.500> things<00:10:32.770> I<00:10:32.980> did<00:10:33.250> not<00:10:33.430> show 00:10:33.690 --> 00:10:33.700 align:start position:0% stuff here are the things I did not show 00:10:33.700 --> 00:10:37.080 align:start position:0% stuff here are the things I did not show you<00:10:33.810> right<00:10:34.810> no<00:10:35.440> mention<00:10:35.800> of<00:10:35.860> eater<00:10:36.040> no<00:10:36.820> head 00:10:37.080 --> 00:10:37.090 align:start position:0% you right no mention of eater no head 00:10:37.090 --> 00:10:40.040 align:start position:0% you right no mention of eater no head strings<00:10:37.480> no<00:10:38.080> passwords<00:10:38.740> no<00:10:39.160> cure<00:10:39.460> codes 00:10:40.040 --> 00:10:40.050 align:start position:0% strings no passwords no cure codes 00:10:40.050 --> 00:10:42.450 align:start position:0% strings no passwords no cure codes incremental<00:10:41.050> security<00:10:41.530> it<00:10:41.860> means<00:10:42.190> that<00:10:42.370> the 00:10:42.450 --> 00:10:42.460 align:start position:0% incremental security it means that the 00:10:42.460 --> 00:10:44.760 align:start position:0% incremental security it means that the first<00:10:42.670> time<00:10:42.910> the<00:10:43.090> user<00:10:43.240> logs<00:10:43.510> into<00:10:43.720> the<00:10:44.200> app<00:10:44.320> he 00:10:44.760 --> 00:10:44.770 align:start position:0% first time the user logs into the app he 00:10:44.770 --> 00:10:46.320 align:start position:0% first time the user logs into the app he can<00:10:44.920> immediately<00:10:45.190> start<00:10:45.580> playing<00:10:46.060> with<00:10:46.300> it 00:10:46.320 --> 00:10:46.330 align:start position:0% can immediately start playing with it 00:10:46.330 --> 00:10:49.710 align:start position:0% can immediately start playing with it only<00:10:47.140> after<00:10:47.580> some<00:10:48.580> sometimes<00:10:48.910> some<00:10:49.300> value<00:10:49.570> has 00:10:49.710 --> 00:10:49.720 align:start position:0% only after some sometimes some value has 00:10:49.720 --> 00:10:51.120 align:start position:0% only after some sometimes some value has passed<00:10:49.960> I 00:10:51.120 --> 00:10:51.130 align:start position:0% passed I 00:10:51.130 --> 00:10:53.210 align:start position:0% passed I you<00:10:51.550> should<00:10:51.790> probably<00:10:52.000> download<00:10:52.720> the 00:10:53.210 --> 00:10:53.220 align:start position:0% you should probably download the 00:10:53.220 --> 00:10:56.190 align:start position:0% you should probably download the smartphone<00:10:54.220> they<00:10:54.520> may<00:10:54.850> be<00:10:54.910> after<00:10:55.450> a<00:10:55.660> few 00:10:56.190 --> 00:10:56.200 align:start position:0% smartphone they may be after a few 00:10:56.200 --> 00:10:57.630 align:start position:0% smartphone they may be after a few months<00:10:56.470> maybe<00:10:56.800> after<00:10:57.100> they<00:10:57.220> have<00:10:57.370> a<00:10:57.400> lot<00:10:57.610> of 00:10:57.630 --> 00:10:57.640 align:start position:0% months maybe after they have a lot of 00:10:57.640 --> 00:11:00.000 align:start position:0% months maybe after they have a lot of value<00:10:58.060> maybe<00:10:58.360> encourage<00:10:58.870> them<00:10:59.260> to<00:10:59.290> print<00:10:59.740> and 00:11:00.000 --> 00:11:00.010 align:start position:0% value maybe encourage them to print and 00:11:00.010 --> 00:11:03.180 align:start position:0% value maybe encourage them to print and download<00:11:00.130> the<00:11:00.520> codes<00:11:00.760> and<00:11:01.590> the<00:11:02.590> user<00:11:02.770> just 00:11:03.180 --> 00:11:03.190 align:start position:0% download the codes and the user just 00:11:03.190 --> 00:11:04.680 align:start position:0% download the codes and the user just deployed<00:11:03.580> a<00:11:03.610> mood<00:11:03.940> effect<00:11:04.270> yourself 00:11:04.680 --> 00:11:04.690 align:start position:0% deployed a mood effect yourself 00:11:04.690 --> 00:11:06.060 align:start position:0% deployed a mood effect yourself sovereign<00:11:05.050> smart<00:11:05.350> contractor<00:11:05.770> Canora 00:11:06.060 --> 00:11:06.070 align:start position:0% sovereign smart contractor Canora 00:11:06.070 --> 00:11:08.670 align:start position:0% sovereign smart contractor Canora identity<00:11:06.520> and<00:11:06.850> they<00:11:07.540> didn't<00:11:07.810> even<00:11:07.990> notice<00:11:08.440> the 00:11:08.670 --> 00:11:08.680 align:start position:0% identity and they didn't even notice the 00:11:08.680 --> 00:11:11.580 align:start position:0% identity and they didn't even notice the thing<00:11:08.920> is<00:11:09.130> we<00:11:09.910> are<00:11:09.940> tricking<00:11:10.720> users<00:11:11.170> into 00:11:11.580 --> 00:11:11.590 align:start position:0% thing is we are tricking users into 00:11:11.590 --> 00:11:14.310 align:start position:0% thing is we are tricking users into using<00:11:11.950> bodicek<00:11:12.520> mortising<00:11:13.480> is<00:11:13.600> a<00:11:13.660> complicated 00:11:14.310 --> 00:11:14.320 align:start position:0% using bodicek mortising is a complicated 00:11:14.320 --> 00:11:15.870 align:start position:0% using bodicek mortising is a complicated complex<00:11:14.560> thing<00:11:15.040> that<00:11:15.220> only<00:11:15.340> that<00:11:15.640> vans 00:11:15.870 --> 00:11:15.880 align:start position:0% complex thing that only that vans 00:11:15.880 --> 00:11:18.390 align:start position:0% complex thing that only that vans developers<00:11:16.420> do<00:11:16.630> and<00:11:16.870> instead<00:11:17.680> I'm<00:11:17.860> tricking 00:11:18.390 --> 00:11:18.400 align:start position:0% developers do and instead I'm tricking 00:11:18.400 --> 00:11:20.910 align:start position:0% developers do and instead I'm tricking them<00:11:18.640> into<00:11:18.670> using<00:11:19.360> it<00:11:19.450> without<00:11:19.570> realizing<00:11:20.020> so 00:11:20.910 --> 00:11:20.920 align:start position:0% them into using it without realizing so 00:11:20.920 --> 00:11:23.400 align:start position:0% them into using it without realizing so what's<00:11:21.220> the<00:11:21.400> magic<00:11:21.610> we<00:11:22.090> are<00:11:22.210> doing<00:11:22.510> the<00:11:23.230> first 00:11:23.400 --> 00:11:23.410 align:start position:0% what's the magic we are doing the first 00:11:23.410 --> 00:11:25.410 align:start position:0% what's the magic we are doing the first thing<00:11:23.770> is<00:11:24.040> that<00:11:24.070> every<00:11:24.580> app<00:11:24.790> has<00:11:25.060> its<00:11:25.090> own 00:11:25.410 --> 00:11:25.420 align:start position:0% thing is that every app has its own 00:11:25.420 --> 00:11:27.600 align:start position:0% thing is that every app has its own private<00:11:25.870> key<00:11:26.050> generate<00:11:26.770> the<00:11:26.890> private<00:11:27.190> key<00:11:27.370> as 00:11:27.600 --> 00:11:27.610 align:start position:0% private key generate the private key as 00:11:27.610 --> 00:11:30.030 align:start position:0% private key generate the private key as we<00:11:27.910> already<00:11:28.120> do<00:11:28.570> with<00:11:29.260> apps<00:11:29.500> the<00:11:29.680> difference 00:11:30.030 --> 00:11:30.040 align:start position:0% we already do with apps the difference 00:11:30.040 --> 00:11:32.190 align:start position:0% we already do with apps the difference here<00:11:30.340> is<00:11:30.490> that<00:11:30.850> don't<00:11:31.330> try<00:11:31.600> to<00:11:31.660> back<00:11:31.930> it<00:11:32.110> up 00:11:32.190 --> 00:11:32.200 align:start position:0% here is that don't try to back it up 00:11:32.200 --> 00:11:33.840 align:start position:0% here is that don't try to back it up don't<00:11:32.530> try<00:11:32.770> to<00:11:32.830> take<00:11:33.100> it<00:11:33.160> out<00:11:33.370> of<00:11:33.400> the<00:11:33.610> device 00:11:33.840 --> 00:11:33.850 align:start position:0% don't try to take it out of the device 00:11:33.850 --> 00:11:37.380 align:start position:0% don't try to take it out of the device don't<00:11:34.540> keep<00:11:34.930> any<00:11:35.290> money<00:11:35.860> or<00:11:36.250> anything<00:11:36.850> on<00:11:37.210> that 00:11:37.380 --> 00:11:37.390 align:start position:0% don't keep any money or anything on that 00:11:37.390 --> 00:11:40.980 align:start position:0% don't keep any money or anything on that private<00:11:37.810> key<00:11:38.200> instead<00:11:39.100> use<00:11:40.030> that<00:11:40.390> private<00:11:40.810> key 00:11:40.980 --> 00:11:40.990 align:start position:0% private key instead use that private key 00:11:40.990 --> 00:11:44.160 align:start position:0% private key instead use that private key to<00:11:41.230> write<00:11:41.710> to<00:11:42.130> sign<00:11:42.340> a<00:11:42.370> message<00:11:43.050> sterling<00:11:44.050> a 00:11:44.160 --> 00:11:44.170 align:start position:0% to write to sign a message sterling a 00:11:44.170 --> 00:11:46.170 align:start position:0% to write to sign a message sterling a smart<00:11:44.410> contract<00:11:44.650> to<00:11:44.950> do<00:11:45.100> something<00:11:45.550> we<00:11:45.940> call 00:11:46.170 --> 00:11:46.180 align:start position:0% smart contract to do something we call 00:11:46.180 --> 00:11:49.050 align:start position:0% smart contract to do something we call those<00:11:46.390> messages<00:11:47.010> mera<00:11:48.010> transactions<00:11:48.790> you 00:11:49.050 --> 00:11:49.060 align:start position:0% those messages mera transactions you 00:11:49.060 --> 00:11:50.700 align:start position:0% those messages mera transactions you probably<00:11:49.390> saw<00:11:49.660> this<00:11:49.900> word<00:11:50.110> you<00:11:50.260> probably<00:11:50.530> seem 00:11:50.700 --> 00:11:50.710 align:start position:0% probably saw this word you probably seem 00:11:50.710 --> 00:11:52.700 align:start position:0% probably saw this word you probably seem like<00:11:50.860> this<00:11:51.010> Mara<00:11:51.340> cartel<00:11:51.910> thing<00:11:52.270> going<00:11:52.570> around 00:11:52.700 --> 00:11:52.710 align:start position:0% like this Mara cartel thing going around 00:11:52.710 --> 00:11:56.550 align:start position:0% like this Mara cartel thing going around that's<00:11:53.710> it<00:11:53.980> it's<00:11:54.280> about<00:11:54.930> better<00:11:55.930> tamela 00:11:56.550 --> 00:11:56.560 align:start position:0% that's it it's about better tamela 00:11:56.560 --> 00:11:58.710 align:start position:0% that's it it's about better tamela transaction<00:11:57.070> is<00:11:57.220> a<00:11:57.250> sign<00:11:57.610> message<00:11:58.090> telling<00:11:58.420> a 00:11:58.710 --> 00:11:58.720 align:start position:0% transaction is a sign message telling a 00:11:58.720 --> 00:12:01.380 align:start position:0% transaction is a sign message telling a smart<00:11:58.990> contract<00:11:59.230> to<00:11:59.620> do<00:11:59.830> something<00:12:00.310> and<00:12:00.460> how 00:12:01.380 --> 00:12:01.390 align:start position:0% smart contract to do something and how 00:12:01.390 --> 00:12:03.270 align:start position:0% smart contract to do something and how do<00:12:01.450> you<00:12:01.780> do<00:12:02.080> something<00:12:02.380> if<00:12:02.830> you<00:12:02.950> don't<00:12:03.130> have 00:12:03.270 --> 00:12:03.280 align:start position:0% do you do something if you don't have 00:12:03.280 --> 00:12:05.760 align:start position:0% do you do something if you don't have eater<00:12:03.520> on<00:12:03.880> that<00:12:04.090> device<00:12:04.390> you<00:12:05.200> have<00:12:05.380> a<00:12:05.410> relator 00:12:05.760 --> 00:12:05.770 align:start position:0% eater on that device you have a relator 00:12:05.770 --> 00:12:08.820 align:start position:0% eater on that device you have a relator who's<00:12:06.580> every<00:12:06.850> layer<00:12:07.060> anyone<00:12:07.870> with<00:12:08.140> eater<00:12:08.470> an 00:12:08.820 --> 00:12:08.830 align:start position:0% who's every layer anyone with eater an 00:12:08.830 --> 00:12:11.010 align:start position:0% who's every layer anyone with eater an internet<00:12:09.280> connection<00:12:09.430> can<00:12:09.760> be<00:12:09.940> relator<00:12:10.420> you 00:12:11.010 --> 00:12:11.020 align:start position:0% internet connection can be relator you 00:12:11.020 --> 00:12:12.870 align:start position:0% internet connection can be relator you can<00:12:11.200> cetera<00:12:11.650> layer<00:12:11.830> for<00:12:12.100> your<00:12:12.190> app<00:12:12.400> you<00:12:12.700> can 00:12:12.870 --> 00:12:12.880 align:start position:0% can cetera layer for your app you can 00:12:12.880 --> 00:12:14.970 align:start position:0% can cetera layer for your app you can have<00:12:13.030> a<00:12:13.060> relator<00:12:13.450> for<00:12:13.870> you<00:12:14.500> can<00:12:14.680> create<00:12:14.950> a 00:12:14.970 --> 00:12:14.980 align:start position:0% have a relator for you can create a 00:12:14.980 --> 00:12:17.400 align:start position:0% have a relator for you can create a relay<00:12:15.310> or<00:12:15.520> decentralized<00:12:16.270> relay<00:12:16.750> network<00:12:17.200> on 00:12:17.400 --> 00:12:17.410 align:start position:0% relay or decentralized relay network on 00:12:17.410 --> 00:12:19.440 align:start position:0% relay or decentralized relay network on whisper<00:12:17.890> the<00:12:18.490> idea<00:12:18.760> is<00:12:18.970> that<00:12:19.090> you<00:12:19.240> layer 00:12:19.440 --> 00:12:19.450 align:start position:0% whisper the idea is that you layer 00:12:19.450 --> 00:12:22.110 align:start position:0% whisper the idea is that you layer someone<00:12:19.930> who<00:12:20.050> takes<00:12:20.380> that<00:12:20.620> message<00:12:21.160> pays<00:12:21.790> the 00:12:22.110 --> 00:12:22.120 align:start position:0% someone who takes that message pays the 00:12:22.120 --> 00:12:25.260 align:start position:0% someone who takes that message pays the gas<00:12:22.330> cost<00:12:22.750> to<00:12:23.430> publish<00:12:24.430> it<00:12:24.550> to<00:12:24.670> the<00:12:24.700> blockchain 00:12:25.260 --> 00:12:25.270 align:start position:0% gas cost to publish it to the blockchain 00:12:25.270 --> 00:12:27.750 align:start position:0% gas cost to publish it to the blockchain and<00:12:25.630> then<00:12:26.140> the<00:12:26.290> contract<00:12:26.680> does<00:12:26.830> something<00:12:27.310> but 00:12:27.750 --> 00:12:27.760 align:start position:0% and then the contract does something but 00:12:27.760 --> 00:12:30.300 align:start position:0% and then the contract does something but way<00:12:27.940> right<00:12:28.480> with<00:12:28.780> someone<00:12:29.260> pay<00:12:29.560> that<00:12:29.830> because 00:12:30.300 --> 00:12:30.310 align:start position:0% way right with someone pay that because 00:12:30.310 --> 00:12:32.640 align:start position:0% way right with someone pay that because the<00:12:30.640> smart<00:12:30.880> contract<00:12:31.150> because<00:12:32.050> it's<00:12:32.230> smart 00:12:32.640 --> 00:12:32.650 align:start position:0% the smart contract because it's smart 00:12:32.650 --> 00:12:35.790 align:start position:0% the smart contract because it's smart can<00:12:33.340> pay<00:12:33.640> back<00:12:33.940> the<00:12:34.210> three<00:12:34.690> layer<00:12:34.840> it<00:12:35.200> can<00:12:35.650> pay 00:12:35.790 --> 00:12:35.800 align:start position:0% can pay back the three layer it can pay 00:12:35.800 --> 00:12:38.130 align:start position:0% can pay back the three layer it can pay back<00:12:36.040> even<00:12:36.610> depending<00:12:37.180> on<00:12:37.300> how<00:12:37.480> much<00:12:37.630> either 00:12:38.130 --> 00:12:38.140 align:start position:0% back even depending on how much either 00:12:38.140 --> 00:12:40.710 align:start position:0% back even depending on how much either how<00:12:38.560> much<00:12:38.740> gas<00:12:39.040> they<00:12:39.250> spent<00:12:39.580> so<00:12:40.210> what<00:12:40.570> are<00:12:40.630> you 00:12:40.710 --> 00:12:40.720 align:start position:0% how much gas they spent so what are you 00:12:40.720 --> 00:12:42.600 align:start position:0% how much gas they spent so what are you basically<00:12:41.110> saying<00:12:41.410> sign<00:12:41.740> messages<00:12:42.340> saying 00:12:42.600 --> 00:12:42.610 align:start position:0% basically saying sign messages saying 00:12:42.610 --> 00:12:44.730 align:start position:0% basically saying sign messages saying look<00:12:42.760> I'm<00:12:43.150> willing<00:12:43.600> to<00:12:43.630> pay<00:12:43.930> let's<00:12:44.260> say<00:12:44.440> one 00:12:44.730 --> 00:12:44.740 align:start position:0% look I'm willing to pay let's say one 00:12:44.740 --> 00:12:47.760 align:start position:0% look I'm willing to pay let's say one died<00:12:45.010> or<00:12:45.400> 3<00:12:45.910> status<00:12:46.240> tokens<00:12:46.810> for<00:12:47.290> someone<00:12:47.650> to 00:12:47.760 --> 00:12:47.770 align:start position:0% died or 3 status tokens for someone to 00:12:47.770 --> 00:12:50.160 align:start position:0% died or 3 status tokens for someone to deploy<00:12:48.100> that<00:12:48.400> message<00:12:48.970> for<00:12:49.210> someone<00:12:49.450> and<00:12:49.870> now 00:12:50.160 --> 00:12:50.170 align:start position:0% deploy that message for someone and now 00:12:50.170 --> 00:12:52.290 align:start position:0% deploy that message for someone and now any<00:12:50.500> one<00:12:51.040> in<00:12:51.220> the<00:12:51.310> relator<00:12:51.580> network<00:12:51.970> can<00:12:52.150> look 00:12:52.290 --> 00:12:52.300 align:start position:0% any one in the relator network can look 00:12:52.300 --> 00:12:53.940 align:start position:0% any one in the relator network can look at<00:12:52.450> that<00:12:52.510> and<00:12:52.690> say<00:12:52.810> hey<00:12:52.990> I<00:12:53.020> think<00:12:53.530> I<00:12:53.740> can 00:12:53.940 --> 00:12:53.950 align:start position:0% at that and say hey I think I can 00:12:53.950 --> 00:12:56.160 align:start position:0% at that and say hey I think I can probably<00:12:54.240> deploy<00:12:55.240> that<00:12:55.450> for<00:12:55.690> less<00:12:55.840> than<00:12:56.050> that 00:12:56.160 --> 00:12:56.170 align:start position:0% probably deploy that for less than that 00:12:56.170 --> 00:12:59.340 align:start position:0% probably deploy that for less than that so<00:12:56.230> I'm<00:12:56.620> taking<00:12:56.890> that<00:12:57.220> I'm<00:12:57.430> getting<00:12:57.820> a<00:12:57.880> 20 00:12:59.340 --> 00:12:59.350 align:start position:0% so I'm taking that I'm getting a 20 00:12:59.350 --> 00:13:02.490 align:start position:0% so I'm taking that I'm getting a 20 and<00:12:59.470> if<00:13:00.340> you<00:13:00.610> need<00:13:00.850> extra<00:13:01.060> recovery<00:13:01.660> keys<00:13:01.900> make 00:13:02.490 --> 00:13:02.500 align:start position:0% and if you need extra recovery keys make 00:13:02.500 --> 00:13:05.490 align:start position:0% and if you need extra recovery keys make an<00:13:02.680> extra<00:13:03.370> backup<00:13:03.730> for<00:13:03.970> it<00:13:04.090> right<00:13:04.420> don't<00:13:04.990> don't 00:13:05.490 --> 00:13:05.500 align:start position:0% an extra backup for it right don't don't 00:13:05.500 --> 00:13:07.770 align:start position:0% an extra backup for it right don't don't do<00:13:05.740> a<00:13:05.770> backup<00:13:06.190> of<00:13:06.280> that<00:13:06.520> just<00:13:07.150> do<00:13:07.300> an<00:13:07.420> extra<00:13:07.660> one 00:13:07.770 --> 00:13:07.780 align:start position:0% do a backup of that just do an extra one 00:13:07.780 --> 00:13:09.900 align:start position:0% do a backup of that just do an extra one the<00:13:08.080> advantage<00:13:08.590> being<00:13:08.800> because<00:13:09.400> it's<00:13:09.610> a<00:13:09.760> more 00:13:09.900 --> 00:13:09.910 align:start position:0% the advantage being because it's a more 00:13:09.910 --> 00:13:12.330 align:start position:0% the advantage being because it's a more smart<00:13:10.300> contract<00:13:10.720> you<00:13:10.840> can<00:13:10.990> add<00:13:11.340> conditions 00:13:12.330 --> 00:13:12.340 align:start position:0% smart contract you can add conditions 00:13:12.340 --> 00:13:15.090 align:start position:0% smart contract you can add conditions let's<00:13:12.640> say<00:13:12.820> you<00:13:13.240> can<00:13:13.390> only<00:13:13.600> do<00:13:14.350> a<00:13:14.380> recovery<00:13:14.920> key 00:13:15.090 --> 00:13:15.100 align:start position:0% let's say you can only do a recovery key 00:13:15.100 --> 00:13:17.070 align:start position:0% let's say you can only do a recovery key after<00:13:15.490> the<00:13:15.640> contract<00:13:15.970> has<00:13:16.120> been<00:13:16.300> inactive<00:13:16.870> or 00:13:17.070 --> 00:13:17.080 align:start position:0% after the contract has been inactive or 00:13:17.080 --> 00:13:19.140 align:start position:0% after the contract has been inactive or maybe<00:13:17.320> you<00:13:17.830> need<00:13:18.040> to<00:13:18.130> have<00:13:18.310> five<00:13:18.580> four<00:13:18.850> five 00:13:19.140 --> 00:13:19.150 align:start position:0% maybe you need to have five four five 00:13:19.150 --> 00:13:20.700 align:start position:0% maybe you need to have five four five trust<00:13:19.510> such<00:13:19.660> friends<00:13:20.080> to<00:13:20.200> be<00:13:20.290> able<00:13:20.350> to<00:13:20.560> do<00:13:20.650> a 00:13:20.700 --> 00:13:20.710 align:start position:0% trust such friends to be able to do a 00:13:20.710 --> 00:13:22.920 align:start position:0% trust such friends to be able to do a recovery<00:13:20.950> you<00:13:21.640> can<00:13:21.790> be<00:13:21.970> creative<00:13:22.510> on<00:13:22.690> whatever 00:13:22.920 --> 00:13:22.930 align:start position:0% recovery you can be creative on whatever 00:13:22.930 --> 00:13:24.870 align:start position:0% recovery you can be creative on whatever you<00:13:23.230> want<00:13:23.500> to<00:13:23.650> do<00:13:23.800> because<00:13:24.370> it's<00:13:24.550> a<00:13:24.610> smart 00:13:24.870 --> 00:13:24.880 align:start position:0% you want to do because it's a smart 00:13:24.880 --> 00:13:26.370 align:start position:0% you want to do because it's a smart contract<00:13:25.120> that's<00:13:25.480> doing<00:13:25.750> the<00:13:25.840> recovery<00:13:26.260> it's 00:13:26.370 --> 00:13:26.380 align:start position:0% contract that's doing the recovery it's 00:13:26.380 --> 00:13:27.930 align:start position:0% contract that's doing the recovery it's not<00:13:26.470> about<00:13:26.710> just<00:13:26.980> recovering<00:13:27.340> a<00:13:27.460> single<00:13:27.790> key 00:13:27.930 --> 00:13:27.940 align:start position:0% not about just recovering a single key 00:13:27.940 --> 00:13:31.430 align:start position:0% not about just recovering a single key and<00:13:28.680> we<00:13:29.680> have<00:13:29.830> something<00:13:30.040> very<00:13:30.400> cool<00:13:30.610> also 00:13:31.430 --> 00:13:31.440 align:start position:0% and we have something very cool also 00:13:31.440 --> 00:13:34.080 align:start position:0% and we have something very cool also they're<00:13:32.440> called<00:13:32.770> counterfactual<00:13:33.640> contracts 00:13:34.080 --> 00:13:34.090 align:start position:0% they're called counterfactual contracts 00:13:34.090 --> 00:13:36.540 align:start position:0% they're called counterfactual contracts I<00:13:34.240> hate<00:13:34.570> the<00:13:34.750> name<00:13:34.900> but<00:13:35.470> basically<00:13:35.980> it's<00:13:36.250> a 00:13:36.540 --> 00:13:36.550 align:start position:0% I hate the name but basically it's a 00:13:36.550 --> 00:13:40.080 align:start position:0% I hate the name but basically it's a deterministic<00:13:37.240> contract<00:13:37.690> address<00:13:38.140> I<00:13:39.090> wait 00:13:40.080 --> 00:13:40.090 align:start position:0% deterministic contract address I wait 00:13:40.090 --> 00:13:43.050 align:start position:0% deterministic contract address I wait which<00:13:40.570> is<00:13:40.720> idea<00:13:41.050> that<00:13:41.290> you<00:13:41.710> already<00:13:41.830> have<00:13:42.400> the 00:13:43.050 --> 00:13:43.060 align:start position:0% which is idea that you already have the 00:13:43.060 --> 00:13:45.330 align:start position:0% which is idea that you already have the the<00:13:43.720> contract<00:13:44.080> address<00:13:44.470> before<00:13:44.710> you<00:13:44.980> deploy 00:13:45.330 --> 00:13:45.340 align:start position:0% the contract address before you deploy 00:13:45.340 --> 00:13:47.220 align:start position:0% the contract address before you deploy it<00:13:45.370> that<00:13:46.000> means<00:13:46.270> that<00:13:46.450> you<00:13:46.540> can<00:13:46.690> already<00:13:46.810> sense 00:13:47.220 --> 00:13:47.230 align:start position:0% it that means that you can already sense 00:13:47.230 --> 00:13:50.100 align:start position:0% it that means that you can already sense funds<00:13:47.710> to<00:13:48.130> it<00:13:48.220> you<00:13:48.670> can<00:13:48.850> send<00:13:49.090> tokens<00:13:49.600> or<00:13:49.810> eater 00:13:50.100 --> 00:13:50.110 align:start position:0% funds to it you can send tokens or eater 00:13:50.110 --> 00:13:52.110 align:start position:0% funds to it you can send tokens or eater to<00:13:50.470> the<00:13:50.590> contract<00:13:50.950> address<00:13:51.340> before<00:13:51.850> you 00:13:52.110 --> 00:13:52.120 align:start position:0% to the contract address before you 00:13:52.120 --> 00:13:54.420 align:start position:0% to the contract address before you deploy<00:13:52.450> it<00:13:52.480> it<00:13:53.020> means<00:13:53.260> that<00:13:53.380> you<00:13:53.500> can<00:13:53.950> pretend 00:13:54.420 --> 00:13:54.430 align:start position:0% deploy it it means that you can pretend 00:13:54.430 --> 00:13:57.000 align:start position:0% deploy it it means that you can pretend for<00:13:54.700> your<00:13:54.880> users<00:13:55.300> that<00:13:55.330> his<00:13:56.230> account<00:13:56.530> is<00:13:56.710> live 00:13:57.000 --> 00:13:57.010 align:start position:0% for your users that his account is live 00:13:57.010 --> 00:13:59.430 align:start position:0% for your users that his account is live until<00:13:57.790> they<00:13:57.910> pay<00:13:58.150> it<00:13:58.360> and<00:13:58.540> then<00:13:58.900> you<00:13:59.170> deploy 00:13:59.430 --> 00:13:59.440 align:start position:0% until they pay it and then you deploy 00:13:59.440 --> 00:14:01.440 align:start position:0% until they pay it and then you deploy the<00:13:59.620> contract<00:14:00.010> and<00:14:00.400> because<00:14:00.910> it<00:14:01.060> works<00:14:01.300> the 00:14:01.440 --> 00:14:01.450 align:start position:0% the contract and because it works the 00:14:01.450 --> 00:14:03.930 align:start position:0% the contract and because it works the mood<00:14:01.600> pool<00:14:01.840> change<00:14:02.110> you<00:14:03.010> can<00:14:03.190> deploy<00:14:03.490> it<00:14:03.700> on<00:14:03.910> a 00:14:03.930 --> 00:14:03.940 align:start position:0% mood pool change you can deploy it on a 00:14:03.940 --> 00:14:06.510 align:start position:0% mood pool change you can deploy it on a test<00:14:04.390> net<00:14:04.660> or<00:14:04.900> on<00:14:05.050> a<00:14:05.080> side<00:14:05.380> chain<00:14:05.740> and<00:14:05.920> only 00:14:06.510 --> 00:14:06.520 align:start position:0% test net or on a side chain and only 00:14:06.520 --> 00:14:08.700 align:start position:0% test net or on a side chain and only move<00:14:06.730> it<00:14:06.910> to<00:14:07.030> the<00:14:07.150> main<00:14:07.360> chain<00:14:07.780> after<00:14:08.380> the<00:14:08.530> user 00:14:08.700 --> 00:14:08.710 align:start position:0% move it to the main chain after the user 00:14:08.710 --> 00:14:11.280 align:start position:0% move it to the main chain after the user has<00:14:08.890> passed<00:14:09.880> some<00:14:10.120> sort<00:14:10.390> of<00:14:10.450> threshold<00:14:10.750> right 00:14:11.280 --> 00:14:11.290 align:start position:0% has passed some sort of threshold right 00:14:11.290 --> 00:14:13.290 align:start position:0% has passed some sort of threshold right I'm<00:14:12.190> still<00:14:12.460> looking<00:14:12.700> for<00:14:12.850> a<00:14:12.880> better<00:14:13.060> name<00:14:13.270> for 00:14:13.290 --> 00:14:13.300 align:start position:0% I'm still looking for a better name for 00:14:13.300 --> 00:14:14.540 align:start position:0% I'm still looking for a better name for that 00:14:14.540 --> 00:14:14.550 align:start position:0% that 00:14:14.550 --> 00:14:18.210 align:start position:0% that so<00:14:15.750> another<00:14:16.750> cool<00:14:17.020> thing<00:14:17.080> authorization<00:14:18.010> term 00:14:18.210 --> 00:14:18.220 align:start position:0% so another cool thing authorization term 00:14:18.220 --> 00:14:20.940 align:start position:0% so another cool thing authorization term is<00:14:18.340> perky<00:14:18.700> not<00:14:19.060> every<00:14:19.510> key<00:14:19.720> is<00:14:19.900> the<00:14:20.080> same<00:14:20.110> not 00:14:20.940 --> 00:14:20.950 align:start position:0% is perky not every key is the same not 00:14:20.950 --> 00:14:22.680 align:start position:0% is perky not every key is the same not every<00:14:21.310> key<00:14:21.520> is<00:14:21.730> as<00:14:21.880> safe<00:14:22.180> as<00:14:22.390> the<00:14:22.540> other 00:14:22.680 --> 00:14:22.690 align:start position:0% every key is as safe as the other 00:14:22.690 --> 00:14:24.870 align:start position:0% every key is as safe as the other browser<00:14:23.140> keys<00:14:23.500> are<00:14:23.680> not<00:14:23.800> as<00:14:23.950> safe<00:14:24.130> as<00:14:24.310> other 00:14:24.870 --> 00:14:24.880 align:start position:0% browser keys are not as safe as other 00:14:24.880 --> 00:14:26.730 align:start position:0% browser keys are not as safe as other keys<00:14:25.210> so<00:14:25.720> one<00:14:25.870> of<00:14:25.900> the<00:14:26.050> things<00:14:26.170> you<00:14:26.290> can<00:14:26.410> do<00:14:26.620> is 00:14:26.730 --> 00:14:26.740 align:start position:0% keys so one of the things you can do is 00:14:26.740 --> 00:14:28.740 align:start position:0% keys so one of the things you can do is that<00:14:26.830> some<00:14:27.070> keys<00:14:27.250> can<00:14:27.490> can<00:14:27.820> add<00:14:28.060> transactions 00:14:28.740 --> 00:14:28.750 align:start position:0% that some keys can can add transactions 00:14:28.750 --> 00:14:30.330 align:start position:0% that some keys can can add transactions other<00:14:28.930> kids<00:14:29.230> cannot<00:14:29.440> add<00:14:29.680> transactions 00:14:30.330 --> 00:14:30.340 align:start position:0% other kids cannot add transactions 00:14:30.340 --> 00:14:33.750 align:start position:0% other kids cannot add transactions things<00:14:30.910> like<00:14:31.060> that<00:14:31.950> it's<00:14:32.950> better<00:14:33.370> for<00:14:33.610> users 00:14:33.750 --> 00:14:33.760 align:start position:0% things like that it's better for users 00:14:33.760 --> 00:14:36.480 align:start position:0% things like that it's better for users it's<00:14:34.270> better<00:14:34.600> for<00:14:34.840> apps<00:14:35.050> because<00:14:35.560> you<00:14:35.740> every 00:14:36.480 --> 00:14:36.490 align:start position:0% it's better for apps because you every 00:14:36.490 --> 00:14:38.310 align:start position:0% it's better for apps because you every time<00:14:36.760> you<00:14:36.940> install<00:14:37.060> a<00:14:37.330> new<00:14:37.390> app<00:14:37.690> you<00:14:37.720> have<00:14:38.080> more 00:14:38.310 --> 00:14:38.320 align:start position:0% time you install a new app you have more 00:14:38.320 --> 00:14:41.100 align:start position:0% time you install a new app you have more security<00:14:38.650> and<00:14:39.300> and<00:14:40.300> you<00:14:40.900> have 00:14:41.100 --> 00:14:41.110 align:start position:0% security and and you have 00:14:41.110 --> 00:14:43.470 align:start position:0% security and and you have cross-compatible<00:14:41.710> usernames<00:14:42.460> users<00:14:43.300> don't 00:14:43.470 --> 00:14:43.480 align:start position:0% cross-compatible usernames users don't 00:14:43.480 --> 00:14:46.950 align:start position:0% cross-compatible usernames users don't need<00:14:43.570> eater<00:14:43.930> and<00:14:45.240> that<00:14:46.240> means<00:14:46.480> you<00:14:46.630> can<00:14:46.810> have 00:14:46.950 --> 00:14:46.960 align:start position:0% need eater and that means you can have 00:14:46.960 --> 00:14:49.710 align:start position:0% need eater and that means you can have more<00:14:47.320> more<00:14:48.220> open<00:14:48.670> business<00:14:49.030> models<00:14:49.420> for 00:14:49.710 --> 00:14:49.720 align:start position:0% more more open business models for 00:14:49.720 --> 00:14:51.390 align:start position:0% more more open business models for instance<00:14:50.080> you<00:14:50.440> can<00:14:50.620> have<00:14:50.860> a<00:14:50.890> subscription 00:14:51.390 --> 00:14:51.400 align:start position:0% instance you can have a subscription 00:14:51.400 --> 00:14:54.330 align:start position:0% instance you can have a subscription model<00:14:51.760> where<00:14:52.390> like<00:14:52.840> the<00:14:53.290> user<00:14:53.440> just<00:14:53.740> goes<00:14:54.040> in 00:14:54.330 --> 00:14:54.340 align:start position:0% model where like the user just goes in 00:14:54.340 --> 00:14:57.150 align:start position:0% model where like the user just goes in and<00:14:54.900> like<00:14:55.900> you<00:14:56.140> pay<00:14:56.380> his<00:14:56.560> transactions<00:14:57.070> for 00:14:57.150 --> 00:14:57.160 align:start position:0% and like you pay his transactions for 00:14:57.160 --> 00:14:59.790 align:start position:0% and like you pay his transactions for for<00:14:57.640> for<00:14:58.000> free<00:14:58.180> and<00:14:58.480> then<00:14:58.810> you<00:14:58.840> just<00:14:59.260> ask<00:14:59.500> you 00:14:59.790 --> 00:14:59.800 align:start position:0% for for free and then you just ask you 00:14:59.800 --> 00:15:01.680 align:start position:0% for for free and then you just ask you have<00:14:59.980> a<00:15:00.010> credit<00:15:00.370> card<00:15:00.400> system<00:15:01.150> where<00:15:01.330> you<00:15:01.480> just 00:15:01.680 --> 00:15:01.690 align:start position:0% have a credit card system where you just 00:15:01.690 --> 00:15:04.110 align:start position:0% have a credit card system where you just charge<00:15:02.320> them<00:15:02.470> five<00:15:02.710> five<00:15:03.070> pounds<00:15:03.430> bird<00:15:03.640> per 00:15:04.110 --> 00:15:04.120 align:start position:0% charge them five five pounds bird per 00:15:04.120 --> 00:15:07.280 align:start position:0% charge them five five pounds bird per day<00:15:04.270> so<00:15:05.050> we<00:15:05.410> have<00:15:05.560> less<00:15:05.770> than<00:15:05.890> five<00:15:06.130> minutes<00:15:06.280> I 00:15:07.280 --> 00:15:07.290 align:start position:0% day so we have less than five minutes I 00:15:07.290 --> 00:15:11.130 align:start position:0% day so we have less than five minutes I so<00:15:08.290> yeah<00:15:08.680> we<00:15:09.580> had<00:15:09.940> like<00:15:10.120> a<00:15:10.150> very<00:15:10.240> quick<00:15:10.900> thing 00:15:11.130 --> 00:15:11.140 align:start position:0% so yeah we had like a very quick thing 00:15:11.140 --> 00:15:12.790 align:start position:0% so yeah we had like a very quick thing here<00:15:11.170> but<00:15:11.500> I<00:15:11.560> think<00:15:11.890> we<00:15:12.010> are<00:15:12.100> gonna<00:15:12.250> okay 00:15:12.790 --> 00:15:12.800 align:start position:0% here but I think we are gonna okay 00:15:12.800 --> 00:15:15.759 align:start position:0% here but I think we are gonna okay can<00:15:13.100> you<00:15:13.160> do<00:15:13.249> it<00:15:13.339> in<00:15:13.369> two<00:15:13.879> minutes<00:15:13.999> okay 00:15:15.759 --> 00:15:15.769 align:start position:0% can you do it in two minutes okay 00:15:15.769 --> 00:15:18.040 align:start position:0% can you do it in two minutes okay just<00:15:16.129> two<00:15:16.220> minutes<00:15:16.279> wanted<00:15:16.939> to<00:15:17.029> show<00:15:17.239> you<00:15:17.300> how 00:15:18.040 --> 00:15:18.050 align:start position:0% just two minutes wanted to show you how 00:15:18.050 --> 00:15:21.429 align:start position:0% just two minutes wanted to show you how simple<00:15:18.110> the<00:15:18.619> API<00:15:18.920> we<00:15:19.279> build<00:15:19.489> is<00:15:20.019> so<00:15:21.019> to<00:15:21.110> start 00:15:21.429 --> 00:15:21.439 align:start position:0% simple the API we build is so to start 00:15:21.439 --> 00:15:23.410 align:start position:0% simple the API we build is so to start using<00:15:21.709> Universal<00:15:22.489> logins<00:15:22.819> all<00:15:23.059> you<00:15:23.149> need<00:15:23.300> to 00:15:23.410 --> 00:15:23.420 align:start position:0% using Universal logins all you need to 00:15:23.420 --> 00:15:25.960 align:start position:0% using Universal logins all you need to do<00:15:23.540> is<00:15:23.959> to<00:15:24.170> create<00:15:24.290> as<00:15:24.559> decay<00:15:24.829> SDK<00:15:25.579> has<00:15:25.610> just 00:15:25.960 --> 00:15:25.970 align:start position:0% do is to create as decay SDK has just 00:15:25.970 --> 00:15:27.999 align:start position:0% do is to create as decay SDK has just two<00:15:26.119> parameters<00:15:26.689> the<00:15:27.259> address<00:15:27.559> of<00:15:27.709> relayer 00:15:27.999 --> 00:15:28.009 align:start position:0% two parameters the address of relayer 00:15:28.009 --> 00:15:31.539 align:start position:0% two parameters the address of relayer and<00:15:28.339> the<00:15:28.610> others<00:15:28.910> of<00:15:29.119> the<00:15:29.230> web<00:15:30.230> pre<00:15:30.439> note<00:15:30.619> then 00:15:31.539 --> 00:15:31.549 align:start position:0% and the others of the web pre note then 00:15:31.549 --> 00:15:33.400 align:start position:0% and the others of the web pre note then it<00:15:32.059> just<00:15:32.299> one<00:15:32.480> command<00:15:32.809> to<00:15:32.899> create<00:15:33.139> an 00:15:33.400 --> 00:15:33.410 align:start position:0% it just one command to create an 00:15:33.410 --> 00:15:35.639 align:start position:0% it just one command to create an identity<00:15:33.889> you<00:15:34.009> just<00:15:34.399> specify<00:15:34.639> the<00:15:34.999> name<00:15:35.360> of 00:15:35.639 --> 00:15:35.649 align:start position:0% identity you just specify the name of 00:15:35.649 --> 00:15:38.619 align:start position:0% identity you just specify the name of the<00:15:36.649> name<00:15:36.799> of<00:15:36.949> the<00:15:37.069> identity<00:15:37.699> E&S<00:15:38.179> name<00:15:38.389> of<00:15:38.540> the 00:15:38.619 --> 00:15:38.629 align:start position:0% the name of the identity E&S name of the 00:15:38.629 --> 00:15:41.139 align:start position:0% the name of the identity E&S name of the identity<00:15:39.110> and<00:15:39.319> you<00:15:39.739> have<00:15:39.949> a<00:15:39.980> private<00:15:40.730> key<00:15:40.970> and 00:15:41.139 --> 00:15:41.149 align:start position:0% identity and you have a private key and 00:15:41.149 --> 00:15:44.229 align:start position:0% identity and you have a private key and identity<00:15:41.569> a<00:15:41.600> dress<00:15:41.959> as<00:15:42.199> a<00:15:42.259> return<00:15:43.220> and<00:15:43.429> bam<00:15:43.910> you 00:15:44.229 --> 00:15:44.239 align:start position:0% identity a dress as a return and bam you 00:15:44.239 --> 00:15:46.150 align:start position:0% identity a dress as a return and bam you can<00:15:44.420> send<00:15:44.689> your<00:15:44.809> transaction<00:15:45.350> which<00:15:45.889> looks 00:15:46.150 --> 00:15:46.160 align:start position:0% can send your transaction which looks 00:15:46.160 --> 00:15:48.100 align:start position:0% can send your transaction which looks pretty<00:15:46.399> much<00:15:47.029> the<00:15:47.209> same<00:15:47.389> as<00:15:47.600> any<00:15:47.749> tomb 00:15:48.100 --> 00:15:48.110 align:start position:0% pretty much the same as any tomb 00:15:48.110 --> 00:15:50.619 align:start position:0% pretty much the same as any tomb transaction<00:15:48.709> with<00:15:48.860> this<00:15:49.009> extra<00:15:49.579> gas<00:15:50.059> talkin 00:15:50.619 --> 00:15:50.629 align:start position:0% transaction with this extra gas talkin 00:15:50.629 --> 00:15:52.960 align:start position:0% transaction with this extra gas talkin parameters<00:15:51.559> so<00:15:51.739> we<00:15:51.829> can<00:15:52.009> say<00:15:52.189> paying 00:15:52.960 --> 00:15:52.970 align:start position:0% parameters so we can say paying 00:15:52.970 --> 00:15:54.910 align:start position:0% parameters so we can say paying something<00:15:53.179> else<00:15:53.480> then<00:15:53.720> either<00:15:54.110> and<00:15:54.470> I<00:15:54.589> think 00:15:54.910 --> 00:15:54.920 align:start position:0% something else then either and I think 00:15:54.920 --> 00:15:56.079 align:start position:0% something else then either and I think we're<00:15:55.069> running<00:15:55.220> out<00:15:55.399> of<00:15:55.459> time<00:15:55.549> thank<00:15:55.910> you<00:15:55.970> very 00:15:56.079 --> 00:15:56.089 align:start position:0% we're running out of time thank you very 00:15:56.089 --> 00:16:01.119 align:start position:0% we're running out of time thank you very much<00:15:57.309> okay<00:15:58.339> now<00:15:58.790> here's<00:15:59.329> the<00:15:59.480> thing<00:15:59.860> I'm<00:16:00.860> not<00:16:01.100> I 00:16:01.119 --> 00:16:01.129 align:start position:0% much okay now here's the thing I'm not I 00:16:01.129 --> 00:16:03.249 align:start position:0% much okay now here's the thing I'm not I don't<00:16:01.429> want<00:16:01.670> here<00:16:02.059> to<00:16:02.329> for<00:16:02.540> us<00:16:02.749> to<00:16:02.929> build<00:16:03.110> the 00:16:03.249 --> 00:16:03.259 align:start position:0% don't want here to for us to build the 00:16:03.259 --> 00:16:04.929 align:start position:0% don't want here to for us to build the best<00:16:03.439> onboarding<00:16:03.980> experience<00:16:04.069> in<00:16:04.519> the<00:16:04.579> web<00:16:04.759> I 00:16:04.929 --> 00:16:04.939 align:start position:0% best onboarding experience in the web I 00:16:04.939 --> 00:16:07.660 align:start position:0% best onboarding experience in the web I think<00:16:05.179> we<00:16:05.269> can<00:16:05.389> use<00:16:05.660> the<00:16:05.839> ATM<00:16:06.769> technology<00:16:07.309> to 00:16:07.660 --> 00:16:07.670 align:start position:0% think we can use the ATM technology to 00:16:07.670 --> 00:16:08.829 align:start position:0% think we can use the ATM technology to build<00:16:07.879> the<00:16:08.029> best<00:16:08.209> onboarding<00:16:08.779> experience 00:16:08.829 --> 00:16:08.839 align:start position:0% build the best onboarding experience 00:16:08.839 --> 00:16:11.739 align:start position:0% build the best onboarding experience anywhere<00:16:09.799> because<00:16:10.610> there's<00:16:10.970> no<00:16:11.209> passwords 00:16:11.739 --> 00:16:11.749 align:start position:0% anywhere because there's no passwords 00:16:11.749 --> 00:16:13.720 align:start position:0% anywhere because there's no passwords and<00:16:12.049> you<00:16:12.319> are<00:16:12.499> in<00:16:12.619> control<00:16:12.649> of<00:16:13.189> your<00:16:13.399> own 00:16:13.720 --> 00:16:13.730 align:start position:0% and you are in control of your own 00:16:13.730 --> 00:16:15.189 align:start position:0% and you are in control of your own identity<00:16:14.029> you're<00:16:14.449> in<00:16:14.569> control<00:16:14.839> of<00:16:14.959> your<00:16:15.110> own 00:16:15.189 --> 00:16:15.199 align:start position:0% identity you're in control of your own 00:16:15.199 --> 00:16:17.019 align:start position:0% identity you're in control of your own old<00:16:15.499> funds<00:16:15.799> which<00:16:16.220> is<00:16:16.339> something<00:16:16.579> we<00:16:16.879> don't 00:16:17.019 --> 00:16:17.029 align:start position:0% old funds which is something we don't 00:16:17.029 --> 00:16:19.389 align:start position:0% old funds which is something we don't find<00:16:17.360> in<00:16:17.600> Facebook<00:16:18.049> as<00:16:18.259> a<00:16:18.709> final<00:16:19.100> figure<00:16:19.309> with 00:16:19.389 --> 00:16:19.399 align:start position:0% find in Facebook as a final figure with 00:16:19.399 --> 00:16:20.799 align:start position:0% find in Facebook as a final figure with layer<00:16:19.610> I<00:16:19.790> would<00:16:19.910> like<00:16:20.029> to<00:16:20.149> thank<00:16:20.360> the<00:16:20.480> kitchen 00:16:20.799 --> 00:16:20.809 align:start position:0% layer I would like to thank the kitchen 00:16:20.809 --> 00:16:22.840 align:start position:0% layer I would like to thank the kitchen Community<00:16:21.199> Fund<00:16:21.379> on<00:16:21.589> eff<00:16:21.799> fries<00:16:22.160> they<00:16:22.549> they 00:16:22.840 --> 00:16:22.850 align:start position:0% Community Fund on eff fries they they 00:16:22.850 --> 00:16:26.139 align:start position:0% Community Fund on eff fries they they have<00:16:22.999> a<00:16:23.029> generous<00:16:23.809> grant<00:16:23.959> that<00:16:24.439> has<00:16:25.129> made<00:16:25.999> this 00:16:26.139 --> 00:16:26.149 align:start position:0% have a generous grant that has made this 00:16:26.149 --> 00:16:27.819 align:start position:0% have a generous grant that has made this work<00:16:26.540> possible<00:16:26.569> and<00:16:27.170> of<00:16:27.230> course<00:16:27.290> the<00:16:27.619> TuneIn 00:16:27.819 --> 00:16:27.829 align:start position:0% work possible and of course the TuneIn 00:16:27.829 --> 00:16:29.379 align:start position:0% work possible and of course the TuneIn Foundation<00:16:28.220> has<00:16:28.339> been<00:16:28.490> supporting<00:16:29.029> all<00:16:29.240> the 00:16:29.379 --> 00:16:29.389 align:start position:0% Foundation has been supporting all the 00:16:29.389 --> 00:16:34.430 align:start position:0% Foundation has been supporting all the crazy<00:16:29.600> stuff<00:16:29.899> I<00:16:30.049> do<00:16:30.110> thank<00:16:30.799> you<00:16:33.100> thank<00:16:34.100> you 00:16:34.430 --> 00:16:34.440 align:start position:0% crazy stuff I do thank you thank you 00:16:34.440 --> 00:16:42.920 align:start position:0% crazy stuff I do thank you thank you [Music] 00:16:42.920 --> 00:16:42.930 align:start position:0% 00:16:42.930 --> 00:16:44.990 align:start position:0% you