WEBVTT Kind: captions Language: en 00:00:01.070 --> 00:00:12.480 align:start position:0% [Applause] 00:00:12.480 --> 00:00:12.490 align:start position:0% 00:00:12.490 --> 00:00:15.189 align:start position:0% cool<00:00:13.490> so<00:00:13.730> we're<00:00:14.389> gonna<00:00:14.539> have<00:00:14.719> kick<00:00:14.900> things<00:00:15.080> up 00:00:15.189 --> 00:00:15.199 align:start position:0% cool so we're gonna have kick things up 00:00:15.199 --> 00:00:18.339 align:start position:0% cool so we're gonna have kick things up and<00:00:15.880> thanks<00:00:16.880> everyone<00:00:17.090> for<00:00:17.180> coming 00:00:18.339 --> 00:00:18.349 align:start position:0% and thanks everyone for coming 00:00:18.349 --> 00:00:21.279 align:start position:0% and thanks everyone for coming my<00:00:18.860> name<00:00:19.039> is<00:00:19.099> Ryan<00:00:19.430> it<00:00:19.579> might<00:00:19.939> be<00:00:20.900> work<00:00:21.079> for<00:00:21.110> the 00:00:21.279 --> 00:00:21.289 align:start position:0% my name is Ryan it might be work for the 00:00:21.289 --> 00:00:23.710 align:start position:0% my name is Ryan it might be work for the wrinkled<00:00:21.560> team<00:00:21.739> at<00:00:22.099> consensus<00:00:22.730> and<00:00:23.539> we're 00:00:23.710 --> 00:00:23.720 align:start position:0% wrinkled team at consensus and we're 00:00:23.720 --> 00:00:26.109 align:start position:0% wrinkled team at consensus and we're gonna<00:00:23.810> be<00:00:23.900> talking<00:00:24.289> today<00:00:24.470> about<00:00:25.119> transaction 00:00:26.109 --> 00:00:26.119 align:start position:0% gonna be talking today about transaction 00:00:26.119 --> 00:00:28.029 align:start position:0% gonna be talking today about transaction states<00:00:26.359> specifically<00:00:27.199> the<00:00:27.470> UX<00:00:27.769> of 00:00:28.029 --> 00:00:28.039 align:start position:0% states specifically the UX of 00:00:28.039 --> 00:00:31.480 align:start position:0% states specifically the UX of transaction<00:00:28.789> States<00:00:29.710> but<00:00:30.710> how<00:00:30.919> much<00:00:31.039> time<00:00:31.279> to 00:00:31.480 --> 00:00:31.490 align:start position:0% transaction States but how much time to 00:00:31.490 --> 00:00:33.970 align:start position:0% transaction States but how much time to go<00:00:31.609> into<00:00:32.080> what<00:00:33.080> we<00:00:33.170> release<00:00:33.470> right<00:00:33.650> now<00:00:33.769> that 00:00:33.970 --> 00:00:33.980 align:start position:0% go into what we release right now that 00:00:33.980 --> 00:00:36.069 align:start position:0% go into what we release right now that if<00:00:34.070> you're<00:00:34.220> interested<00:00:34.730> it's<00:00:35.269> kinda<00:00:35.540> QR<00:00:35.809> codes 00:00:36.069 --> 00:00:36.079 align:start position:0% if you're interested it's kinda QR codes 00:00:36.079 --> 00:00:38.200 align:start position:0% if you're interested it's kinda QR codes and<00:00:36.410> that's<00:00:36.530> all<00:00:36.650> upside<00:00:36.980> or<00:00:37.339> follow<00:00:37.850> the<00:00:37.940> link 00:00:38.200 --> 00:00:38.210 align:start position:0% and that's all upside or follow the link 00:00:38.210 --> 00:00:41.079 align:start position:0% and that's all upside or follow the link I<00:00:39.010> guess<00:00:40.010> to<00:00:40.129> set<00:00:40.309> the<00:00:40.400> scene<00:00:40.640> why<00:00:40.909> we're 00:00:41.079 --> 00:00:41.089 align:start position:0% I guess to set the scene why we're 00:00:41.089 --> 00:00:43.299 align:start position:0% I guess to set the scene why we're talking<00:00:41.210> about<00:00:41.420> this<00:00:41.629> today<00:00:41.860> our<00:00:42.860> main<00:00:43.070> user 00:00:43.299 --> 00:00:43.309 align:start position:0% talking about this today our main user 00:00:43.309 --> 00:00:45.279 align:start position:0% talking about this today our main user group<00:00:43.579> are<00:00:43.879> developers<00:00:44.570> in<00:00:44.690> this<00:00:44.750> place<00:00:44.960> we 00:00:45.279 --> 00:00:45.289 align:start position:0% group are developers in this place we 00:00:45.289 --> 00:00:47.260 align:start position:0% group are developers in this place we build<00:00:45.530> components<00:00:46.100> and<00:00:46.640> write<00:00:46.789> ballots<00:00:47.149> to 00:00:47.260 --> 00:00:47.270 align:start position:0% build components and write ballots to 00:00:47.270 --> 00:00:51.099 align:start position:0% build components and write ballots to try<00:00:47.420> and<00:00:47.539> help<00:00:47.660> dr.<00:00:48.620> Belman<00:00:49.719> remembers<00:00:50.719> sort 00:00:51.099 --> 00:00:51.109 align:start position:0% try and help dr. Belman remembers sort 00:00:51.109 --> 00:00:54.369 align:start position:0% try and help dr. Belman remembers sort of<00:00:51.170> improve<00:00:51.440> UX<00:00:51.739> allowable<00:00:52.960> so<00:00:53.960> we<00:00:54.050> speak<00:00:54.260> to<00:00:54.320> a 00:00:54.369 --> 00:00:54.379 align:start position:0% of improve UX allowable so we speak to a 00:00:54.379 --> 00:00:56.080 align:start position:0% of improve UX allowable so we speak to a lot<00:00:54.500> of<00:00:54.530> developers<00:00:54.949> we<00:00:55.489> do<00:00:55.910> a<00:00:55.940> lot<00:00:56.059> of 00:00:56.080 --> 00:00:56.090 align:start position:0% lot of developers we do a lot of 00:00:56.090 --> 00:00:57.700 align:start position:0% lot of developers we do a lot of research<00:00:56.269> lot<00:00:56.660> of<00:00:56.719> interviews<00:00:57.140> and<00:00:57.379> something 00:00:57.700 --> 00:00:57.710 align:start position:0% research lot of interviews and something 00:00:57.710 --> 00:01:00.610 align:start position:0% research lot of interviews and something that<00:00:57.800> came<00:00:57.949> up<00:00:58.100> sort<00:00:58.489> of<00:00:58.519> again<00:00:58.760> and<00:00:58.910> again<00:00:59.620> as 00:01:00.610 --> 00:01:00.620 align:start position:0% that came up sort of again and again as 00:01:00.620 --> 00:01:02.799 align:start position:0% that came up sort of again and again as a<00:01:00.680> penguin<00:01:00.949> the<00:01:01.280> developers<00:01:01.699> was<00:01:02.000> transaction 00:01:02.799 --> 00:01:02.809 align:start position:0% a penguin the developers was transaction 00:01:02.809 --> 00:01:05.830 align:start position:0% a penguin the developers was transaction states<00:01:03.050> and<00:01:03.289> house<00:01:03.440> designer<00:01:03.859> exactly<00:01:04.840> so 00:01:05.830 --> 00:01:05.840 align:start position:0% states and house designer exactly so 00:01:05.840 --> 00:01:07.719 align:start position:0% states and house designer exactly so instead<00:01:06.410> of<00:01:06.470> one<00:01:06.649> thing<00:01:06.830> to<00:01:07.009> sort<00:01:07.190> of<00:01:07.280> theorize 00:01:07.719 --> 00:01:07.729 align:start position:0% instead of one thing to sort of theorize 00:01:07.729 --> 00:01:09.669 align:start position:0% instead of one thing to sort of theorize around<00:01:08.210> what<00:01:08.690> might<00:01:08.960> potentially<00:01:09.259> make<00:01:09.649> a 00:01:09.669 --> 00:01:09.679 align:start position:0% around what might potentially make a 00:01:09.679 --> 00:01:12.639 align:start position:0% around what might potentially make a good<00:01:09.979> transaction<00:01:10.490> stay<00:01:10.670> to<00:01:10.729> X<00:01:11.380> we<00:01:12.380> thought<00:01:12.560> we 00:01:12.639 --> 00:01:12.649 align:start position:0% good transaction stay to X we thought we 00:01:12.649 --> 00:01:14.889 align:start position:0% good transaction stay to X we thought we try<00:01:12.800> and<00:01:13.119> uncover<00:01:14.119> the<00:01:14.270> secret<00:01:14.720> to 00:01:14.889 --> 00:01:14.899 align:start position:0% try and uncover the secret to 00:01:14.899 --> 00:01:16.900 align:start position:0% try and uncover the secret to transaction<00:01:15.410> to<00:01:15.500> X<00:01:15.679> and<00:01:15.950> our<00:01:16.310> own<00:01:16.610> across 00:01:16.900 --> 00:01:16.910 align:start position:0% transaction to X and our own across 00:01:16.910 --> 00:01:18.880 align:start position:0% transaction to X and our own across these<00:01:17.090> getting<00:01:17.840> our<00:01:18.020> hands<00:01:18.200> dirty<00:01:18.259> and<00:01:18.679> going 00:01:18.880 --> 00:01:18.890 align:start position:0% these getting our hands dirty and going 00:01:18.890 --> 00:01:20.770 align:start position:0% these getting our hands dirty and going out<00:01:19.009> to<00:01:19.039> the<00:01:19.190> fields<00:01:19.550> do<00:01:19.729> some<00:01:19.970> research<00:01:20.539> labs 00:01:20.770 --> 00:01:20.780 align:start position:0% out to the fields do some research labs 00:01:20.780 --> 00:01:23.410 align:start position:0% out to the fields do some research labs because<00:01:20.990> on<00:01:21.580> and<00:01:22.580> it's<00:01:22.789> kind<00:01:22.819> of<00:01:23.000> reminded<00:01:23.390> me 00:01:23.410 --> 00:01:23.420 align:start position:0% because on and it's kind of reminded me 00:01:23.420 --> 00:01:25.120 align:start position:0% because on and it's kind of reminded me you<00:01:24.140> know<00:01:24.229> getting<00:01:24.500> onto<00:01:24.619> the<00:01:24.800> tail<00:01:24.950> that 00:01:25.120 --> 00:01:25.130 align:start position:0% you know getting onto the tail that 00:01:25.130 --> 00:01:26.680 align:start position:0% you know getting onto the tail that house<00:01:25.250> that<00:01:25.280> city<00:01:25.670> or<00:01:25.819> the<00:01:25.940> trouble<00:01:26.360> here<00:01:26.539> at 00:01:26.680 --> 00:01:26.690 align:start position:0% house that city or the trouble here at 00:01:26.690 --> 00:01:29.440 align:start position:0% house that city or the trouble here at one<00:01:27.369> and<00:01:28.369> there's<00:01:28.520> no<00:01:28.640> relief<00:01:28.819> for<00:01:29.270> guessing 00:01:29.440 --> 00:01:29.450 align:start position:0% one and there's no relief for guessing 00:01:29.450 --> 00:01:30.249 align:start position:0% one and there's no relief for guessing who<00:01:29.690> that<00:01:29.899> might<00:01:30.080> be 00:01:30.249 --> 00:01:30.259 align:start position:0% who that might be 00:01:30.259 --> 00:01:33.999 align:start position:0% who that might be it's<00:01:31.039> Indiana<00:01:31.429> Jones<00:01:32.500> so<00:01:33.500> beginning<00:01:33.739> if<00:01:33.890> the 00:01:33.999 --> 00:01:34.009 align:start position:0% it's Indiana Jones so beginning if the 00:01:34.009 --> 00:01:36.160 align:start position:0% it's Indiana Jones so beginning if the indexes<00:01:34.399> all<00:01:34.520> help<00:01:34.789> us<00:01:34.940> talk<00:01:35.720> through<00:01:35.929> some<00:01:35.959> of 00:01:36.160 --> 00:01:36.170 align:start position:0% indexes all help us talk through some of 00:01:36.170 --> 00:01:37.630 align:start position:0% indexes all help us talk through some of the<00:01:36.229> main<00:01:36.380> problems<00:01:36.800> around<00:01:37.039> transaction 00:01:37.630 --> 00:01:37.640 align:start position:0% the main problems around transaction 00:01:37.640 --> 00:01:40.120 align:start position:0% the main problems around transaction works<00:01:37.899> so<00:01:38.899> first<00:01:39.110> I'll<00:01:39.319> never<00:01:39.739> eat<00:01:39.890> no 00:01:40.120 --> 00:01:40.130 align:start position:0% works so first I'll never eat no 00:01:40.130 --> 00:01:43.749 align:start position:0% works so first I'll never eat no transaction<00:01:40.759> so<00:01:41.209> what<00:01:42.200> happens<00:01:42.619> if<00:01:42.950> a<00:01:43.190> user 00:01:43.749 --> 00:01:43.759 align:start position:0% transaction so what happens if a user 00:01:43.759 --> 00:01:45.430 align:start position:0% transaction so what happens if a user trusts<00:01:44.239> transact<00:01:44.720> that<00:01:44.899> doesn't<00:01:45.110> have<00:01:45.259> the 00:01:45.430 --> 00:01:45.440 align:start position:0% trusts transact that doesn't have the 00:01:45.440 --> 00:01:48.639 align:start position:0% trusts transact that doesn't have the required<00:01:45.800> funds<00:01:46.869> how<00:01:47.869> do<00:01:47.929> we<00:01:48.050> help<00:01:48.170> users<00:01:48.410> get 00:01:48.639 --> 00:01:48.649 align:start position:0% required funds how do we help users get 00:01:48.649 --> 00:01:49.810 align:start position:0% required funds how do we help users get even<00:01:48.979> how<00:01:49.130> do<00:01:49.190> we 00:01:49.810 --> 00:01:49.820 align:start position:0% even how do we 00:01:49.820 --> 00:01:53.830 align:start position:0% even how do we educate<00:01:50.180> them<00:01:50.210> on<00:01:50.840> those<00:01:51.080> needed<00:01:51.970> and<00:01:52.970> these 00:01:53.830 --> 00:01:53.840 align:start position:0% educate them on those needed and these 00:01:53.840 --> 00:01:56.050 align:start position:0% educate them on those needed and these fear<00:01:54.110> the<00:01:55.010> fact<00:01:55.220> that<00:01:55.250> you<00:01:55.370> means<00:01:55.580> ease<00:01:55.850> to 00:01:56.050 --> 00:01:56.060 align:start position:0% fear the fact that you means ease to 00:01:56.060 --> 00:01:57.910 align:start position:0% fear the fact that you means ease to make<00:01:56.210> these<00:01:56.540> can<00:01:56.930> leave<00:01:57.110> a<00:01:57.170> bitter<00:01:57.350> taste 00:01:57.910 --> 00:01:57.920 align:start position:0% make these can leave a bitter taste 00:01:57.920 --> 00:01:59.800 align:start position:0% make these can leave a bitter taste and<00:01:58.130> although<00:01:58.310> transaction<00:01:59.240> fees<00:01:59.450> might<00:01:59.690> be 00:01:59.800 --> 00:01:59.810 align:start position:0% and although transaction fees might be 00:01:59.810 --> 00:02:01.510 align:start position:0% and although transaction fees might be normal<00:01:59.960> to<00:02:00.320> all<00:02:00.440> right 00:02:01.510 --> 00:02:01.520 align:start position:0% normal to all right 00:02:01.520 --> 00:02:02.950 align:start position:0% normal to all right this<00:02:01.910> is<00:02:02.030> something<00:02:02.390> that's<00:02:02.479> well<00:02:02.720> often 00:02:02.950 --> 00:02:02.960 align:start position:0% this is something that's well often 00:02:02.960 --> 00:02:07.350 align:start position:0% this is something that's well often unexpected<00:02:03.229> and<00:02:03.979> unsettling<00:02:04.610> the<00:02:04.790> new<00:02:04.909> users 00:02:07.350 --> 00:02:07.360 align:start position:0% 00:02:07.360 --> 00:02:11.290 align:start position:0% transactions<00:02:08.360> can<00:02:08.660> drag<00:02:08.959> so<00:02:09.560> compared<00:02:10.490> to<00:02:10.700> the 00:02:11.290 --> 00:02:11.300 align:start position:0% transactions can drag so compared to the 00:02:11.300 --> 00:02:13.470 align:start position:0% transactions can drag so compared to the sort<00:02:11.510> of<00:02:11.540> web<00:02:11.720> to<00:02:11.900> experiences<00:02:12.590> we<00:02:12.740> used<00:02:12.920> to 00:02:13.470 --> 00:02:13.480 align:start position:0% sort of web to experiences we used to 00:02:13.480 --> 00:02:16.300 align:start position:0% sort of web to experiences we used to when<00:02:14.480> a<00:02:14.510> transaction<00:02:14.840> might<00:02:15.200> say<00:02:15.410> minutes 00:02:16.300 --> 00:02:16.310 align:start position:0% when a transaction might say minutes 00:02:16.310 --> 00:02:19.090 align:start position:0% when a transaction might say minutes hours<00:02:16.790> even<00:02:16.910> days<00:02:17.320> how<00:02:18.320> can<00:02:18.530> we<00:02:18.650> help 00:02:19.090 --> 00:02:19.100 align:start position:0% hours even days how can we help 00:02:19.100 --> 00:02:20.590 align:start position:0% hours even days how can we help communicate<00:02:19.700> what's<00:02:19.850> happening<00:02:20.150> to<00:02:20.270> users 00:02:20.590 --> 00:02:20.600 align:start position:0% communicate what's happening to users 00:02:20.600 --> 00:02:23.590 align:start position:0% communicate what's happening to users and<00:02:21.500> on<00:02:21.709> that<00:02:21.860> note<00:02:22.180> how<00:02:23.180> much<00:02:23.360> should<00:02:23.510> we 00:02:23.590 --> 00:02:23.600 align:start position:0% and on that note how much should we 00:02:23.600 --> 00:02:24.970 align:start position:0% and on that note how much should we actually<00:02:23.720> explain<00:02:24.200> about<00:02:24.440> what's<00:02:24.650> happening 00:02:24.970 --> 00:02:24.980 align:start position:0% actually explain about what's happening 00:02:24.980 --> 00:02:26.680 align:start position:0% actually explain about what's happening how<00:02:25.250> much<00:02:25.430> should<00:02:25.550> we<00:02:25.640> be<00:02:25.760> explaining<00:02:26.300> about 00:02:26.680 --> 00:02:26.690 align:start position:0% how much should we be explaining about 00:02:26.690 --> 00:02:29.740 align:start position:0% how much should we be explaining about why<00:02:26.840> it's<00:02:27.020> taking<00:02:27.380> that<00:02:27.920> extra<00:02:28.040> time<00:02:28.630> how<00:02:29.630> much 00:02:29.740 --> 00:02:29.750 align:start position:0% why it's taking that extra time how much 00:02:29.750 --> 00:02:31.090 align:start position:0% why it's taking that extra time how much of<00:02:29.870> the<00:02:29.959> blockchain<00:02:30.140> in<00:02:30.470> general<00:02:30.800> should<00:02:30.950> we 00:02:31.090 --> 00:02:31.100 align:start position:0% of the blockchain in general should we 00:02:31.100 --> 00:02:32.500 align:start position:0% of the blockchain in general should we be<00:02:31.220> shown<00:02:31.430> to<00:02:31.610> the<00:02:31.640> users<00:02:32.030> and<00:02:32.239> how<00:02:32.330> much 00:02:32.500 --> 00:02:32.510 align:start position:0% be shown to the users and how much 00:02:32.510 --> 00:02:37.949 align:start position:0% be shown to the users and how much should<00:02:32.660> we<00:02:32.780> leave<00:02:32.959> behind<00:02:33.170> the<00:02:33.380> sins<00:02:36.850> cherry 00:02:37.949 --> 00:02:37.959 align:start position:0% should we leave behind the sins cherry 00:02:37.959 --> 00:02:40.030 align:start position:0% should we leave behind the sins cherry on<00:02:38.959> top<00:02:38.989> of<00:02:39.140> the<00:02:39.260> cake<00:02:39.470> is<00:02:39.620> that<00:02:39.650> of<00:02:39.890> course 00:02:40.030 --> 00:02:40.040 align:start position:0% on top of the cake is that of course 00:02:40.040 --> 00:02:43.300 align:start position:0% on top of the cake is that of course they're<00:02:40.280> irreversible<00:02:40.940> so<00:02:42.100> that's<00:02:43.100> quite 00:02:43.300 --> 00:02:43.310 align:start position:0% they're irreversible so that's quite 00:02:43.310 --> 00:02:46.240 align:start position:0% they're irreversible so that's quite scary<00:02:43.459> especially<00:02:43.850> for<00:02:44.360> new<00:02:44.480> users<00:02:45.250> if 00:02:46.240 --> 00:02:46.250 align:start position:0% scary especially for new users if 00:02:46.250 --> 00:02:47.979 align:start position:0% scary especially for new users if something<00:02:46.790> goes<00:02:46.940> wrong<00:02:46.970> there's<00:02:47.570> no<00:02:47.720> chance 00:02:47.979 --> 00:02:47.989 align:start position:0% something goes wrong there's no chance 00:02:47.989 --> 00:02:50.680 align:start position:0% something goes wrong there's no chance to<00:02:48.410> you<00:02:49.340> know<00:02:49.400> call<00:02:49.670> customer<00:02:50.060> service<00:02:50.239> get 00:02:50.680 --> 00:02:50.690 align:start position:0% to you know call customer service get 00:02:50.690 --> 00:02:53.560 align:start position:0% to you know call customer service get things<00:02:50.930> change<00:02:52.060> and<00:02:53.060> we<00:02:53.180> don't<00:02:53.360> want<00:02:53.510> that 00:02:53.560 --> 00:02:53.570 align:start position:0% things change and we don't want that 00:02:53.570 --> 00:02:55.780 align:start position:0% things change and we don't want that leading<00:02:53.930> to<00:02:54.110> transaction<00:02:54.950> regret<00:02:55.250> or<00:02:55.549> even 00:02:55.780 --> 00:02:55.790 align:start position:0% leading to transaction regret or even 00:02:55.790 --> 00:02:59.140 align:start position:0% leading to transaction regret or even worse<00:02:55.970> very<00:02:56.769> regret<00:02:57.769> where<00:02:58.459> people<00:02:58.730> end<00:02:58.850> up<00:02:58.940> in 00:02:59.140 --> 00:02:59.150 align:start position:0% worse very regret where people end up in 00:02:59.150 --> 00:03:00.789 align:start position:0% worse very regret where people end up in the<00:02:59.269> ecosystem<00:02:59.959> is<00:03:00.080> forgiving<00:03:00.530> up<00:03:00.650> there 00:03:00.789 --> 00:03:00.799 align:start position:0% the ecosystem is forgiving up there 00:03:00.799 --> 00:03:03.850 align:start position:0% the ecosystem is forgiving up there together<00:03:02.200> and<00:03:03.200> it's<00:03:03.380> nice<00:03:03.560> to<00:03:03.680> have 00:03:03.850 --> 00:03:03.860 align:start position:0% together and it's nice to have 00:03:03.860 --> 00:03:05.530 align:start position:0% together and it's nice to have interesting<00:03:04.430> sub<00:03:04.610> a<00:03:04.820> demo<00:03:05.090> we<00:03:05.269> come<00:03:05.450> across 00:03:05.530 --> 00:03:05.540 align:start position:0% interesting sub a demo we come across 00:03:05.540 --> 00:03:08.050 align:start position:0% interesting sub a demo we come across quite<00:03:05.900> often<00:03:06.220> around<00:03:07.220> the<00:03:07.730> notion<00:03:08.030> of 00:03:08.050 --> 00:03:08.060 align:start position:0% quite often around the notion of 00:03:08.060 --> 00:03:10.900 align:start position:0% quite often around the notion of education<00:03:08.660> so<00:03:08.989> it's<00:03:09.590> a<00:03:09.709> labor<00:03:09.860> of<00:03:10.040> do<00:03:10.579> users 00:03:10.900 --> 00:03:10.910 align:start position:0% education so it's a labor of do users 00:03:10.910 --> 00:03:13.120 align:start position:0% education so it's a labor of do users know<00:03:11.030> what<00:03:11.180> they're<00:03:11.299> doing<00:03:11.540> and<00:03:11.750> if<00:03:12.130> they 00:03:13.120 --> 00:03:13.130 align:start position:0% know what they're doing and if they 00:03:13.130 --> 00:03:14.020 align:start position:0% know what they're doing and if they don't<00:03:13.280> what<00:03:13.400> they're<00:03:13.549> doing<00:03:13.790> are<00:03:13.940> they 00:03:14.020 --> 00:03:14.030 align:start position:0% don't what they're doing are they 00:03:14.030 --> 00:03:16.690 align:start position:0% don't what they're doing are they incentivize<00:03:14.299> sufficiently<00:03:15.140> to<00:03:15.769> go<00:03:15.920> sort<00:03:16.610> of 00:03:16.690 --> 00:03:16.700 align:start position:0% incentivize sufficiently to go sort of 00:03:16.700 --> 00:03:19.680 align:start position:0% incentivize sufficiently to go sort of educate<00:03:17.180> themselves<00:03:17.570> and<00:03:17.840> make<00:03:18.440> their<00:03:18.650> best 00:03:19.680 --> 00:03:19.690 align:start position:0% educate themselves and make their best 00:03:19.690 --> 00:03:25.030 align:start position:0% educate themselves and make their best best<00:03:20.690> effort<00:03:21.019> at<00:03:21.140> it<00:03:23.560> so<00:03:24.560> that's<00:03:24.739> one<00:03:24.860> of<00:03:24.890> the 00:03:25.030 --> 00:03:25.040 align:start position:0% best effort at it so that's one of the 00:03:25.040 --> 00:03:27.039 align:start position:0% best effort at it so that's one of the main<00:03:25.190> problems<00:03:25.640> and<00:03:26.000> completely<00:03:26.660> understand 00:03:27.039 --> 00:03:27.049 align:start position:0% main problems and completely understand 00:03:27.049 --> 00:03:30.510 align:start position:0% main problems and completely understand why<00:03:27.850> this<00:03:28.850> is<00:03:29.030> such<00:03:29.209> a<00:03:29.239> okay 00:03:30.510 --> 00:03:30.520 align:start position:0% why this is such a okay 00:03:30.520 --> 00:03:33.120 align:start position:0% why this is such a okay such<00:03:30.850> a<00:03:30.880> pain<00:03:31.090> point<00:03:31.300> I<00:03:31.840> think<00:03:32.560> it's<00:03:32.770> important 00:03:33.120 --> 00:03:33.130 align:start position:0% such a pain point I think it's important 00:03:33.130 --> 00:03:35.280 align:start position:0% such a pain point I think it's important to<00:03:33.310> also<00:03:33.550> talk<00:03:33.910> about<00:03:33.940> the<00:03:34.660> opportunities<00:03:35.260> for 00:03:35.280 --> 00:03:35.290 align:start position:0% to also talk about the opportunities for 00:03:35.290 --> 00:03:37.800 align:start position:0% to also talk about the opportunities for sort<00:03:36.280> of<00:03:36.310> spending<00:03:36.700> more<00:03:36.820> time<00:03:37.030> on<00:03:37.420> to 00:03:37.800 --> 00:03:37.810 align:start position:0% sort of spending more time on to 00:03:37.810 --> 00:03:39.810 align:start position:0% sort of spending more time on to designing<00:03:38.250> transaction<00:03:39.250> states<00:03:39.490> and 00:03:39.810 --> 00:03:39.820 align:start position:0% designing transaction states and 00:03:39.820 --> 00:03:42.120 align:start position:0% designing transaction states and hopefully<00:03:40.180> this<00:03:40.780> will<00:03:40.930> convince<00:03:41.170> any<00:03:41.860> teams 00:03:42.120 --> 00:03:42.130 align:start position:0% hopefully this will convince any teams 00:03:42.130 --> 00:03:44.040 align:start position:0% hopefully this will convince any teams are<00:03:42.310> there<00:03:42.430> to<00:03:42.640> maybe<00:03:42.760> solve<00:03:43.090> hit<00:03:43.660> this<00:03:43.810> up<00:03:43.930> as 00:03:44.040 --> 00:03:44.050 align:start position:0% are there to maybe solve hit this up as 00:03:44.050 --> 00:03:47.820 align:start position:0% are there to maybe solve hit this up as a<00:03:44.080> priority<00:03:44.490> after<00:03:45.490> they<00:03:45.580> leave<00:03:45.640> a<00:03:45.790> sucker 00:03:47.820 --> 00:03:47.830 align:start position:0% a priority after they leave a sucker 00:03:47.830 --> 00:03:55.839 align:start position:0% a priority after they leave a sucker [Music] 00:03:55.839 --> 00:03:55.849 align:start position:0% [Music] 00:03:55.849 --> 00:03:58.339 align:start position:0% [Music] so<00:03:56.849> that's<00:03:57.060> that<00:03:57.239> we<00:03:57.450> talked<00:03:57.629> about<00:03:57.959> a<00:03:58.200> little 00:03:58.339 --> 00:03:58.349 align:start position:0% so that's that we talked about a little 00:03:58.349 --> 00:04:00.649 align:start position:0% so that's that we talked about a little bit<00:03:58.500> about<00:03:58.739> some<00:03:58.950> of<00:03:58.980> the<00:03:59.190> behavioral<00:03:59.849> science 00:04:00.649 --> 00:04:00.659 align:start position:0% bit about some of the behavioral science 00:04:00.659 --> 00:04:04.820 align:start position:0% bit about some of the behavioral science sort<00:04:01.500> of<00:04:01.620> justification<00:04:02.549> examiners<00:04:03.590> so<00:04:04.590> first 00:04:04.820 --> 00:04:04.830 align:start position:0% sort of justification examiners so first 00:04:04.830 --> 00:04:07.130 align:start position:0% sort of justification examiners so first up<00:04:04.980> it's<00:04:05.159> the<00:04:05.250> halo<00:04:05.700> event<00:04:06.000> and<00:04:06.239> its<00:04:06.810> elastic 00:04:07.130 --> 00:04:07.140 align:start position:0% up it's the halo event and its elastic 00:04:07.140 --> 00:04:08.570 align:start position:0% up it's the halo event and its elastic it's<00:04:07.260> probably<00:04:07.560> complicated<00:04:08.190> to<00:04:08.250> solve<00:04:08.430> an 00:04:08.570 --> 00:04:08.580 align:start position:0% it's probably complicated to solve an 00:04:08.580 --> 00:04:10.460 align:start position:0% it's probably complicated to solve an account<00:04:08.879> for<00:04:09.000> a<00:04:09.090> service<00:04:09.450> and<00:04:09.959> that<00:04:10.080> bad<00:04:10.230> user 00:04:10.460 --> 00:04:10.470 align:start position:0% account for a service and that bad user 00:04:10.470 --> 00:04:11.930 align:start position:0% account for a service and that bad user experience<00:04:10.590> will<00:04:11.129> rub<00:04:11.280> off<00:04:11.400> on<00:04:11.610> people's 00:04:11.930 --> 00:04:11.940 align:start position:0% experience will rub off on people's 00:04:11.940 --> 00:04:14.030 align:start position:0% experience will rub off on people's expectations<00:04:12.660> for<00:04:12.900> the<00:04:12.989> rest<00:04:13.170> of<00:04:13.319> the<00:04:13.440> service 00:04:14.030 --> 00:04:14.040 align:start position:0% expectations for the rest of the service 00:04:14.040 --> 00:04:16.129 align:start position:0% expectations for the rest of the service now<00:04:14.459> this<00:04:14.610> fighters<00:04:15.209> maintenance<00:04:15.959> is<00:04:16.109> a 00:04:16.129 --> 00:04:16.139 align:start position:0% now this fighters maintenance is a 00:04:16.139 --> 00:04:18.560 align:start position:0% now this fighters maintenance is a compression<00:04:16.620> we<00:04:17.370> can<00:04:17.549> certainly<00:04:17.790> solving 00:04:18.560 --> 00:04:18.570 align:start position:0% compression we can certainly solving 00:04:18.570 --> 00:04:20.539 align:start position:0% compression we can certainly solving transactions<00:04:19.410> and<00:04:19.739> we<00:04:19.859> still<00:04:20.100> have<00:04:20.220> the<00:04:20.340> exact 00:04:20.539 --> 00:04:20.549 align:start position:0% transactions and we still have the exact 00:04:20.549 --> 00:04:24.110 align:start position:0% transactions and we still have the exact same<00:04:20.729> meaning<00:04:20.880> so<00:04:21.810> if<00:04:22.560> you<00:04:23.010> user<00:04:23.250> is<00:04:23.699> exposed 00:04:24.110 --> 00:04:24.120 align:start position:0% same meaning so if you user is exposed 00:04:24.120 --> 00:04:29.240 align:start position:0% same meaning so if you user is exposed to<00:04:25.010> it's<00:04:26.010> really<00:04:26.340> bad<00:04:26.930> you<00:04:27.930> know<00:04:28.250> concrete 00:04:29.240 --> 00:04:29.250 align:start position:0% to it's really bad you know concrete 00:04:29.250 --> 00:04:30.439 align:start position:0% to it's really bad you know concrete like<00:04:29.340> this<00:04:29.460> for<00:04:29.669> example<00:04:29.729> it<00:04:30.150> doesn't<00:04:30.360> really 00:04:30.439 --> 00:04:30.449 align:start position:0% like this for example it doesn't really 00:04:30.449 --> 00:04:32.600 align:start position:0% like this for example it doesn't really explain<00:04:30.660> what<00:04:31.410> to<00:04:31.560> do<00:04:31.740> why<00:04:32.160> he<00:04:32.220> needs<00:04:32.460> one 00:04:32.600 --> 00:04:32.610 align:start position:0% explain what to do why he needs one 00:04:32.610 --> 00:04:34.580 align:start position:0% explain what to do why he needs one little<00:04:32.789> token<00:04:33.180> to<00:04:33.210> have<00:04:33.840> this<00:04:33.990> sort<00:04:34.260> of<00:04:34.320> quite 00:04:34.580 --> 00:04:34.590 align:start position:0% little token to have this sort of quite 00:04:34.590 --> 00:04:38.750 align:start position:0% little token to have this sort of quite confusing<00:04:35.270> approval<00:04:36.270> function<00:04:36.630> woman<00:04:37.760> it's 00:04:38.750 --> 00:04:38.760 align:start position:0% confusing approval function woman it's 00:04:38.760 --> 00:04:40.610 align:start position:0% confusing approval function woman it's gonna<00:04:38.910> create<00:04:39.389> a<00:04:39.479> bad<00:04:39.660> experience<00:04:40.050> even<00:04:40.500> if 00:04:40.610 --> 00:04:40.620 align:start position:0% gonna create a bad experience even if 00:04:40.620 --> 00:04:42.800 align:start position:0% gonna create a bad experience even if you<00:04:40.830> know<00:04:41.010> your<00:04:41.550> doubt<00:04:41.729> has<00:04:41.910> been<00:04:41.940> the<00:04:42.600> coolest 00:04:42.800 --> 00:04:42.810 align:start position:0% you know your doubt has been the coolest 00:04:42.810 --> 00:04:45.020 align:start position:0% you know your doubt has been the coolest tech<00:04:43.410> house 00:04:45.020 --> 00:04:45.030 align:start position:0% tech house 00:04:45.030 --> 00:04:47.659 align:start position:0% tech house the<00:04:45.479> smoothest<00:04:45.930> connecting<00:04:46.470> connecting<00:04:47.430> the 00:04:47.659 --> 00:04:47.669 align:start position:0% the smoothest connecting connecting the 00:04:47.669 --> 00:04:50.480 align:start position:0% the smoothest connecting connecting the wallet<00:04:47.940> experience<00:04:48.360> I<00:04:49.250> think<00:04:50.250> a<00:04:50.310> great 00:04:50.480 --> 00:04:50.490 align:start position:0% wallet experience I think a great 00:04:50.490 --> 00:04:52.670 align:start position:0% wallet experience I think a great analogy<00:04:50.760> for<00:04:50.910> this<00:04:51.180> is<00:04:51.449> the<00:04:52.260> Kingdom<00:04:52.560> of<00:04:52.590> the 00:04:52.670 --> 00:04:52.680 align:start position:0% analogy for this is the Kingdom of the 00:04:52.680 --> 00:04:58.010 align:start position:0% analogy for this is the Kingdom of the Crystal<00:04:52.740> Skull<00:04:53.250> movie<00:04:54.050> which<00:04:56.510> one<00:04:57.510> that<00:04:57.720> baby 00:04:58.010 --> 00:04:58.020 align:start position:0% Crystal Skull movie which one that baby 00:04:58.020 --> 00:04:59.360 align:start position:0% Crystal Skull movie which one that baby is<00:04:58.139> tarnished<00:04:58.530> the<00:04:58.680> reputation<00:04:58.860> of<00:04:59.250> the 00:04:59.360 --> 00:04:59.370 align:start position:0% is tarnished the reputation of the 00:04:59.370 --> 00:05:04.040 align:start position:0% is tarnished the reputation of the entire<00:04:59.639> franchise<00:05:02.150> the<00:05:03.150> pecan<00:05:03.510> draw<00:05:03.720> is<00:05:03.870> very 00:05:04.040 --> 00:05:04.050 align:start position:0% entire franchise the pecan draw is very 00:05:04.050 --> 00:05:06.320 align:start position:0% entire franchise the pecan draw is very similar<00:05:04.320> so<00:05:04.470> two<00:05:04.979> copies<00:05:05.310> of<00:05:05.340> bias<00:05:05.639> impacts 00:05:06.320 --> 00:05:06.330 align:start position:0% similar so two copies of bias impacts 00:05:06.330 --> 00:05:08.450 align:start position:0% similar so two copies of bias impacts have<00:05:06.479> people<00:05:06.810> remember<00:05:07.139> past<00:05:07.380> events<00:05:07.470> so 00:05:08.450 --> 00:05:08.460 align:start position:0% have people remember past events so 00:05:08.460 --> 00:05:10.159 align:start position:0% have people remember past events so these<00:05:08.580> intense<00:05:08.940> positive<00:05:09.510> or<00:05:09.810> negative 00:05:10.159 --> 00:05:10.169 align:start position:0% these intense positive or negative 00:05:10.169 --> 00:05:12.529 align:start position:0% these intense positive or negative moments<00:05:10.620> each<00:05:11.010> of<00:05:11.220> the<00:05:11.280> peaks<00:05:11.490> and<00:05:11.760> the<00:05:12.180> final 00:05:12.529 --> 00:05:12.539 align:start position:0% moments each of the peaks and the final 00:05:12.539 --> 00:05:14.480 align:start position:0% moments each of the peaks and the final moments<00:05:13.169> of<00:05:13.200> the<00:05:13.289> experience<00:05:13.770> end 00:05:14.480 --> 00:05:14.490 align:start position:0% moments of the experience end 00:05:14.490 --> 00:05:18.620 align:start position:0% moments of the experience end and<00:05:15.449> some<00:05:15.600> calculus<00:05:17.419> transaction<00:05:18.419> was 00:05:18.620 --> 00:05:18.630 align:start position:0% and some calculus transaction was 00:05:18.630 --> 00:05:21.379 align:start position:0% and some calculus transaction was probably<00:05:19.199> award<00:05:19.500> quite<00:05:20.250> often<00:05:20.400> represents<00:05:21.240> or 00:05:21.379 --> 00:05:21.389 align:start position:0% probably award quite often represents or 00:05:21.389 --> 00:05:24.770 align:start position:0% probably award quite often represents or end<00:05:21.690> part<00:05:22.050> an<00:05:22.229> experience<00:05:22.710> with<00:05:22.889> a<00:05:22.919> done<00:05:23.780> and 00:05:24.770 --> 00:05:24.780 align:start position:0% end part an experience with a done and 00:05:24.780 --> 00:05:26.120 align:start position:0% end part an experience with a done and again<00:05:25.050> they<00:05:25.319> always<00:05:25.590> have<00:05:25.710> a<00:05:25.800> very<00:05:25.919> high 00:05:26.120 --> 00:05:26.130 align:start position:0% again they always have a very high 00:05:26.130 --> 00:05:27.800 align:start position:0% again they always have a very high likelihood<00:05:26.280> of<00:05:26.699> being<00:05:26.910> either<00:05:27.360> an<00:05:27.479> intense 00:05:27.800 --> 00:05:27.810 align:start position:0% likelihood of being either an intense 00:05:27.810 --> 00:05:29.260 align:start position:0% likelihood of being either an intense positive<00:05:28.289> or<00:05:28.500> an<00:05:28.560> intense<00:05:28.800> negative 00:05:29.260 --> 00:05:29.270 align:start position:0% positive or an intense negative 00:05:29.270 --> 00:05:32.029 align:start position:0% positive or an intense negative experience<00:05:30.270> so<00:05:31.080> again<00:05:31.349> this<00:05:31.680> could<00:05:31.889> really 00:05:32.029 --> 00:05:32.039 align:start position:0% experience so again this could really 00:05:32.039 --> 00:05:33.680 align:start position:0% experience so again this could really dissolve<00:05:32.460> again<00:05:33.030> if<00:05:33.150> you<00:05:33.210> have<00:05:33.360> the<00:05:33.509> nicest 00:05:33.680 --> 00:05:33.690 align:start position:0% dissolve again if you have the nicest 00:05:33.690 --> 00:05:36.559 align:start position:0% dissolve again if you have the nicest DAP<00:05:34.590> leading<00:05:34.919> up<00:05:35.009> to<00:05:35.039> the<00:05:35.190> transaction<00:05:35.759> then 00:05:36.559 --> 00:05:36.569 align:start position:0% DAP leading up to the transaction then 00:05:36.569 --> 00:05:38.930 align:start position:0% DAP leading up to the transaction then it<00:05:36.750> really<00:05:37.199> impacts<00:05:37.710> these<00:05:37.919> or<00:05:38.280> how<00:05:38.699> either 00:05:38.930 --> 00:05:38.940 align:start position:0% it really impacts these or how either 00:05:38.940 --> 00:05:40.610 align:start position:0% it really impacts these or how either remembers<00:05:39.599> your<00:05:39.750> that<00:05:39.990> and<00:05:40.319> they've<00:05:40.440> read 00:05:40.610 --> 00:05:40.620 align:start position:0% remembers your that and they've read 00:05:40.620 --> 00:05:41.900 align:start position:0% remembers your that and they've read that<00:05:40.800> sort<00:05:40.979> of<00:05:41.009> trust<00:05:41.310> that<00:05:41.430> you<00:05:41.610> might<00:05:41.819> have 00:05:41.900 --> 00:05:41.910 align:start position:0% that sort of trust that you might have 00:05:41.910 --> 00:05:44.990 align:start position:0% that sort of trust that you might have fostered<00:05:42.539> up<00:05:42.810> until<00:05:43.080> that<00:05:43.169> point<00:05:43.759> I'm<00:05:44.759> gonna 00:05:44.990 --> 00:05:45.000 align:start position:0% fostered up until that point I'm gonna 00:05:45.000 --> 00:05:47.570 align:start position:0% fostered up until that point I'm gonna shields<00:05:45.330> mainly<00:05:45.630> again<00:05:45.870> but<00:05:46.380> rip<00:05:47.340> steam 00:05:47.570 --> 00:05:47.580 align:start position:0% shields mainly again but rip steam 00:05:47.580 --> 00:05:50.060 align:start position:0% shields mainly again but rip steam coming<00:05:48.000> at<00:05:48.090> the<00:05:48.150> end<00:05:48.180> of<00:05:48.539> the<00:05:48.810> bottom<00:05:49.680> and 00:05:50.060 --> 00:05:50.070 align:start position:0% coming at the end of the bottom and 00:05:50.070 --> 00:05:51.740 align:start position:0% coming at the end of the bottom and moving<00:05:50.340> into<00:05:50.669> the<00:05:50.759> franchise<00:05:50.910> has<00:05:51.449> certainly 00:05:51.740 --> 00:05:51.750 align:start position:0% moving into the franchise has certainly 00:05:51.750 --> 00:05:57.529 align:start position:0% moving into the franchise has certainly tiny<00:05:52.229> stuff<00:05:52.530> for<00:05:52.650> me<00:05:54.349> okay<00:05:55.349> know<00:05:56.340> right<00:05:56.729> users 00:05:57.529 --> 00:05:57.539 align:start position:0% tiny stuff for me okay know right users 00:05:57.539 --> 00:05:59.089 align:start position:0% tiny stuff for me okay know right users eventually<00:05:57.900> even<00:05:58.110> trust<00:05:58.349> work<00:05:58.530> to<00:05:58.710> you<00:05:58.949> know 00:05:59.089 --> 00:05:59.099 align:start position:0% eventually even trust work to you know 00:05:59.099 --> 00:06:02.420 align:start position:0% eventually even trust work to you know so<00:05:59.490> a<00:05:59.759> study<00:06:00.570> conducted<00:06:00.840> by<00:06:01.169> my<00:06:01.620> Institute<00:06:02.160> in 00:06:02.420 --> 00:06:02.430 align:start position:0% so a study conducted by my Institute in 00:06:02.430 --> 00:06:04.520 align:start position:0% so a study conducted by my Institute in twenty<00:06:02.789> eighteen<00:06:03.090> thousand<00:06:03.570> they<00:06:04.199> found<00:06:04.410> that 00:06:04.520 --> 00:06:04.530 align:start position:0% twenty eighteen thousand they found that 00:06:04.530 --> 00:06:06.920 align:start position:0% twenty eighteen thousand they found that 28%<00:06:04.800> of<00:06:05.220> users<00:06:05.580> abandon<00:06:06.090> their<00:06:06.240> tasks<00:06:06.479> because 00:06:06.920 --> 00:06:06.930 align:start position:0% 28% of users abandon their tasks because 00:06:06.930 --> 00:06:09.680 align:start position:0% 28% of users abandon their tasks because of<00:06:07.050> complicated<00:06:07.710> check<00:06:07.919> out<00:06:08.099> blacks<00:06:08.630> now<00:06:09.630> the 00:06:09.680 --> 00:06:09.690 align:start position:0% of complicated check out blacks now the 00:06:09.690 --> 00:06:11.719 align:start position:0% of complicated check out blacks now the study<00:06:10.259> also<00:06:10.440> found<00:06:10.620> that<00:06:10.979> main<00:06:11.190> reasons 00:06:11.719 --> 00:06:11.729 align:start position:0% study also found that main reasons 00:06:11.729 --> 00:06:13.899 align:start position:0% study also found that main reasons Bannerman<00:06:12.300> was<00:06:12.690> over<00:06:13.319> the<00:06:13.380> use<00:06:13.500> of<00:06:13.650> jargon 00:06:13.899 --> 00:06:13.909 align:start position:0% Bannerman was over the use of jargon 00:06:13.909 --> 00:06:17.390 align:start position:0% Bannerman was over the use of jargon lacked<00:06:14.909> a<00:06:15.030> visual<00:06:15.330> design<00:06:15.630> and<00:06:16.020> I<00:06:16.740> think<00:06:16.979> at 00:06:17.390 --> 00:06:17.400 align:start position:0% lacked a visual design and I think at 00:06:17.400 --> 00:06:18.589 align:start position:0% lacked a visual design and I think at the<00:06:17.520> moment<00:06:17.550> obviously<00:06:18.180> in<00:06:18.509> these 00:06:18.589 --> 00:06:18.599 align:start position:0% the moment obviously in these 00:06:18.599 --> 00:06:20.570 align:start position:0% the moment obviously in these experiments<00:06:19.139> will<00:06:19.440> face<00:06:19.680> of<00:06:19.949> material<00:06:20.400> and 00:06:20.570 --> 00:06:20.580 align:start position:0% experiments will face of material and 00:06:20.580 --> 00:06:23.170 align:start position:0% experiments will face of material and apps<00:06:20.849> and<00:06:21.030> this<00:06:21.870> is<00:06:22.020> quite<00:06:22.139> often<00:06:22.349> the<00:06:22.530> case<00:06:22.590> in 00:06:23.170 --> 00:06:23.180 align:start position:0% apps and this is quite often the case in 00:06:23.180 --> 00:06:26.379 align:start position:0% apps and this is quite often the case in in<00:06:24.180> work<00:06:24.419> for<00:06:24.599> applications<00:06:25.229> as<00:06:25.500> well<00:06:25.650> so 00:06:26.379 --> 00:06:26.389 align:start position:0% in work for applications as well so 00:06:26.389 --> 00:06:28.490 align:start position:0% in work for applications as well so again<00:06:27.389> a<00:06:27.570> really<00:06:27.750> good<00:06:27.870> opportunity<00:06:27.990> it's 00:06:28.490 --> 00:06:28.500 align:start position:0% again a really good opportunity it's 00:06:28.500 --> 00:06:31.100 align:start position:0% again a really good opportunity it's it's<00:06:28.650> over<00:06:29.039> spend<00:06:29.969> more<00:06:30.360> time<00:06:30.419> thinking<00:06:30.599> about 00:06:31.100 --> 00:06:31.110 align:start position:0% it's over spend more time thinking about 00:06:31.110 --> 00:06:33.020 align:start position:0% it's over spend more time thinking about the<00:06:31.469> design<00:06:31.710> of<00:06:31.740> transactions<00:06:32.340> and<00:06:32.610> make<00:06:32.759> that 00:06:33.020 --> 00:06:33.030 align:start position:0% the design of transactions and make that 00:06:33.030 --> 00:06:34.670 align:start position:0% the design of transactions and make that bridge<00:06:33.419> that<00:06:33.599> abandoned<00:06:34.110> and<00:06:34.229> increase<00:06:34.530> their 00:06:34.670 --> 00:06:34.680 align:start position:0% bridge that abandoned and increase their 00:06:34.680 --> 00:06:39.920 align:start position:0% bridge that abandoned and increase their trust<00:06:34.919> into<00:06:35.190> that<00:06:37.070> okay<00:06:38.070> so<00:06:38.820> we<00:06:39.270> spoking<00:06:39.599> buses 00:06:39.920 --> 00:06:39.930 align:start position:0% trust into that okay so we spoking buses 00:06:39.930 --> 00:06:42.200 align:start position:0% trust into that okay so we spoking buses and<00:06:40.050> problems<00:06:40.440> and<00:06:40.770> talk<00:06:41.669> to<00:06:41.789> us<00:06:41.880> and<00:06:42.090> the 00:06:42.200 --> 00:06:42.210 align:start position:0% and problems and talk to us and the 00:06:42.210 --> 00:06:43.629 align:start position:0% and problems and talk to us and the opportunities 00:06:43.629 --> 00:06:43.639 align:start position:0% opportunities 00:06:43.639 --> 00:06:45.980 align:start position:0% opportunities we're<00:06:44.639> gonna<00:06:44.759> show<00:06:44.969> you<00:06:45.030> a<00:06:45.150> quick<00:06:45.419> demo<00:06:45.690> and 00:06:45.980 --> 00:06:45.990 align:start position:0% we're gonna show you a quick demo and 00:06:45.990 --> 00:06:48.290 align:start position:0% we're gonna show you a quick demo and then<00:06:46.500> this<00:06:46.680> is<00:06:47.190> all<00:06:47.400> come<00:06:47.610> out<00:06:47.699> of<00:06:47.880> this<00:06:48.150> or 00:06:48.290 --> 00:06:48.300 align:start position:0% then this is all come out of this or 00:06:48.300 --> 00:06:50.480 align:start position:0% then this is all come out of this or research<00:06:48.719> and<00:06:49.139> the<00:06:49.320> design<00:06:49.740> inspiration<00:06:49.949> I 00:06:50.480 --> 00:06:50.490 align:start position:0% research and the design inspiration I 00:06:50.490 --> 00:06:52.850 align:start position:0% research and the design inspiration I mentioned<00:06:50.849> earlier<00:06:51.120> we<00:06:51.930> spend<00:06:52.229> the<00:06:52.590> last<00:06:52.680> two 00:06:52.850 --> 00:06:52.860 align:start position:0% mentioned earlier we spend the last two 00:06:52.860 --> 00:06:56.540 align:start position:0% mentioned earlier we spend the last two months<00:06:53.039> speaking<00:06:53.639> to<00:06:54.560> some<00:06:55.560> savvy<00:06:56.039> blockchain 00:06:56.540 --> 00:06:56.550 align:start position:0% months speaking to some savvy blockchain 00:06:56.550 --> 00:06:59.300 align:start position:0% months speaking to some savvy blockchain users<00:06:56.940> not<00:06:57.570> so<00:06:57.750> savvy<00:06:58.020> try<00:06:58.889> and<00:06:58.979> understand 00:06:59.300 --> 00:06:59.310 align:start position:0% users not so savvy try and understand 00:06:59.310 --> 00:07:00.860 align:start position:0% users not so savvy try and understand what<00:06:59.550> a<00:06:59.580> bit<00:06:59.759> that<00:06:59.969> secret<00:07:00.419> sauce<00:07:00.630> to 00:07:00.860 --> 00:07:00.870 align:start position:0% what a bit that secret sauce to 00:07:00.870 --> 00:07:02.110 align:start position:0% what a bit that secret sauce to transaction<00:07:01.740> yet 00:07:02.110 --> 00:07:02.120 align:start position:0% transaction yet 00:07:02.120 --> 00:07:05.890 align:start position:0% transaction yet being<00:07:03.699> just<00:07:04.699> a<00:07:04.790> caviar<00:07:05.150> slightly<00:07:05.449> we<00:07:05.540> focus 00:07:05.890 --> 00:07:05.900 align:start position:0% being just a caviar slightly we focus 00:07:05.900 --> 00:07:09.129 align:start position:0% being just a caviar slightly we focus mainly<00:07:06.080> on<00:07:07.060> darkness<00:07:08.060> that<00:07:08.479> might<00:07:08.690> be<00:07:08.900> trying 00:07:09.129 --> 00:07:09.139 align:start position:0% mainly on darkness that might be trying 00:07:09.139 --> 00:07:11.800 align:start position:0% mainly on darkness that might be trying to<00:07:09.560> appeal<00:07:10.520> to<00:07:10.550> a<00:07:10.729> more<00:07:10.880> mainstream<00:07:11.150> audience 00:07:11.800 --> 00:07:11.810 align:start position:0% to appeal to a more mainstream audience 00:07:11.810 --> 00:07:15.360 align:start position:0% to appeal to a more mainstream audience and<00:07:11.990> try<00:07:12.050> and<00:07:12.229> reach<00:07:12.380> that's<00:07:12.650> all<00:07:13.660> outside<00:07:14.660> the 00:07:15.360 --> 00:07:15.370 align:start position:0% and try and reach that's all outside the 00:07:15.370 --> 00:07:20.590 align:start position:0% and try and reach that's all outside the brain<00:07:17.229> so<00:07:18.229> the<00:07:18.800> demo<00:07:19.130> is<00:07:19.370> for<00:07:19.510> potentially<00:07:20.510> a 00:07:20.590 --> 00:07:20.600 align:start position:0% brain so the demo is for potentially a 00:07:20.600 --> 00:07:22.570 align:start position:0% brain so the demo is for potentially a Def<00:07:20.750> Con<00:07:20.990> application<00:07:21.710> where<00:07:21.949> I<00:07:22.250> guess 00:07:22.570 --> 00:07:22.580 align:start position:0% Def Con application where I guess 00:07:22.580 --> 00:07:24.189 align:start position:0% Def Con application where I guess purchase<00:07:22.970> your<00:07:23.090> two<00:07:23.240> kids<00:07:23.389> as<00:07:23.570> NF<00:07:23.840> TS 00:07:24.189 --> 00:07:24.199 align:start position:0% purchase your two kids as NF TS 00:07:24.199 --> 00:07:28.540 align:start position:0% purchase your two kids as NF TS so<00:07:24.560> my<00:07:24.979> timer<00:07:25.280> talked<00:07:25.490> us<00:07:25.610> through<00:07:25.639> that<00:07:27.550> so 00:07:28.540 --> 00:07:28.550 align:start position:0% so my timer talked us through that so 00:07:28.550 --> 00:07:30.730 align:start position:0% so my timer talked us through that so let<00:07:28.880> grant<00:07:29.120> said<00:07:29.389> we<00:07:29.570> build<00:07:29.840> a<00:07:30.020> lot<00:07:30.199> of<00:07:30.260> demos 00:07:30.730 --> 00:07:30.740 align:start position:0% let grant said we build a lot of demos 00:07:30.740 --> 00:07:33.520 align:start position:0% let grant said we build a lot of demos for<00:07:31.190> user<00:07:31.400> testing<00:07:31.940> for<00:07:32.870> this<00:07:33.020> one<00:07:33.260> we're 00:07:33.520 --> 00:07:33.530 align:start position:0% for user testing for this one we're 00:07:33.530 --> 00:07:36.070 align:start position:0% for user testing for this one we're using<00:07:33.710> it<00:07:33.889> opens<00:07:34.220> up<00:07:34.370> wins<00:07:34.610> GRC<00:07:35.389> 7:21 00:07:36.070 --> 00:07:36.080 align:start position:0% using it opens up wins GRC 7:21 00:07:36.080 --> 00:07:38.830 align:start position:0% using it opens up wins GRC 7:21 contracts<00:07:36.830> we're<00:07:37.550> using<00:07:37.729> truffle<00:07:38.419> for<00:07:38.660> the 00:07:38.830 --> 00:07:38.840 align:start position:0% contracts we're using truffle for the 00:07:38.840 --> 00:07:42.070 align:start position:0% contracts we're using truffle for the contract<00:07:39.760> management<00:07:40.760> and<00:07:41.210> deployment<00:07:41.449> and 00:07:42.070 --> 00:07:42.080 align:start position:0% contract management and deployment and 00:07:42.080 --> 00:07:43.870 align:start position:0% contract management and deployment and then<00:07:42.260> on<00:07:42.860> the<00:07:43.010> client<00:07:43.130> side<00:07:43.370> we're<00:07:43.729> using 00:07:43.870 --> 00:07:43.880 align:start position:0% then on the client side we're using 00:07:43.880 --> 00:07:46.570 align:start position:0% then on the client side we're using drizzle<00:07:44.750> to<00:07:45.050> keep<00:07:45.470> the<00:07:45.650> blockchain<00:07:45.919> data<00:07:46.280> in 00:07:46.570 --> 00:07:46.580 align:start position:0% drizzle to keep the blockchain data in 00:07:46.580 --> 00:07:54.100 align:start position:0% drizzle to keep the blockchain data in sync<00:07:46.940> the<00:07:47.530> client<00:07:48.530> side<00:07:50.470> and<00:07:52.389> we're<00:07:53.389> using<00:07:53.630> our 00:07:54.100 --> 00:07:54.110 align:start position:0% sync the client side and we're using our 00:07:54.110 --> 00:07:56.560 align:start position:0% sync the client side and we're using our own<00:07:54.410> component<00:07:55.070> system<00:07:55.430> I<00:07:55.699> believe<00:07:55.970> I<00:07:56.060> and 00:07:56.560 --> 00:07:56.570 align:start position:0% own component system I believe I and 00:07:56.570 --> 00:07:58.600 align:start position:0% own component system I believe I and some<00:07:57.110> web<00:07:57.260> 3<00:07:57.440> components<00:07:57.919> that<00:07:57.979> we<00:07:58.130> build<00:07:58.340> just 00:07:58.600 --> 00:07:58.610 align:start position:0% some web 3 components that we build just 00:07:58.610 --> 00:08:01.629 align:start position:0% some web 3 components that we build just to<00:07:58.789> keep<00:07:58.970> things<00:07:59.500> easy<00:08:00.500> and<00:08:00.770> fast<00:08:01.039> for<00:08:01.250> us<00:08:01.280> 12 00:08:01.629 --> 00:08:01.639 align:start position:0% to keep things easy and fast for us 12 00:08:01.639 --> 00:08:03.730 align:start position:0% to keep things easy and fast for us 12 and<00:08:01.910> then<00:08:02.570> we're<00:08:02.690> extending<00:08:02.960> bristle<00:08:03.590> with 00:08:03.730 --> 00:08:03.740 align:start position:0% and then we're extending bristle with 00:08:03.740 --> 00:08:06.520 align:start position:0% and then we're extending bristle with third-party<00:08:04.070> data<00:08:04.669> that<00:08:05.090> comes<00:08:05.330> from<00:08:05.530> just 00:08:06.520 --> 00:08:06.530 align:start position:0% third-party data that comes from just 00:08:06.530 --> 00:08:09.100 align:start position:0% third-party data that comes from just regular<00:08:06.680> API<00:08:07.160> services<00:08:07.700> reason<00:08:08.180> eath<00:08:08.840> gas 00:08:09.100 --> 00:08:09.110 align:start position:0% regular API services reason eath gas 00:08:09.110 --> 00:08:12.370 align:start position:0% regular API services reason eath gas stations<00:08:09.650> API<00:08:10.130> to<00:08:10.190> get<00:08:10.669> a<00:08:10.910> gas<00:08:11.389> estimate<00:08:12.110> that 00:08:12.370 --> 00:08:12.380 align:start position:0% stations API to get a gas estimate that 00:08:12.380 --> 00:08:15.460 align:start position:0% stations API to get a gas estimate that we<00:08:12.530> can<00:08:12.710> use<00:08:12.950> to<00:08:13.310> calculate<00:08:14.090> a<00:08:14.479> transaction 00:08:15.460 --> 00:08:15.470 align:start position:0% we can use to calculate a transaction 00:08:15.470 --> 00:08:18.129 align:start position:0% we can use to calculate a transaction fee<00:08:15.680> and<00:08:16.099> an<00:08:16.430> estimated<00:08:17.120> wait<00:08:17.270> time<00:08:17.300> based<00:08:17.930> on 00:08:18.129 --> 00:08:18.139 align:start position:0% fee and an estimated wait time based on 00:08:18.139 --> 00:08:19.870 align:start position:0% fee and an estimated wait time based on just<00:08:18.410> like<00:08:18.560> what<00:08:18.710> the<00:08:18.800> average<00:08:19.010> price<00:08:19.460> of<00:08:19.639> gas 00:08:19.870 --> 00:08:19.880 align:start position:0% just like what the average price of gas 00:08:19.880 --> 00:08:23.080 align:start position:0% just like what the average price of gas is<00:08:20.120> going<00:08:20.300> to<00:08:20.360> be<00:08:20.479> right<00:08:20.630> now<00:08:21.550> so<00:08:22.550> we're<00:08:22.940> using 00:08:23.080 --> 00:08:23.090 align:start position:0% is going to be right now so we're using 00:08:23.090 --> 00:08:26.230 align:start position:0% is going to be right now so we're using those<00:08:23.330> two<00:08:23.630> kind<00:08:23.990> of<00:08:24.050> key<00:08:24.289> important<00:08:25.240> pieces 00:08:26.230 --> 00:08:26.240 align:start position:0% those two kind of key important pieces 00:08:26.240 --> 00:08:28.510 align:start position:0% those two kind of key important pieces of<00:08:26.389> information<00:08:26.479> on<00:08:27.169> the<00:08:27.349> Eiger<00:08:27.889> the 00:08:28.510 --> 00:08:28.520 align:start position:0% of information on the Eiger the 00:08:28.520 --> 00:08:31.000 align:start position:0% of information on the Eiger the transaction<00:08:29.389> fee<00:08:29.960> is<00:08:30.229> what<00:08:30.470> we're<00:08:30.590> calling<00:08:30.740> it 00:08:31.000 --> 00:08:31.010 align:start position:0% transaction fee is what we're calling it 00:08:31.010 --> 00:08:33.909 align:start position:0% transaction fee is what we're calling it instead<00:08:31.520> of<00:08:31.580> talking<00:08:31.970> about<00:08:32.120> gas<00:08:32.510> and<00:08:32.919> we're 00:08:33.909 --> 00:08:33.919 align:start position:0% instead of talking about gas and we're 00:08:33.919 --> 00:08:35.500 align:start position:0% instead of talking about gas and we're estimating<00:08:34.099> that<00:08:34.550> just<00:08:34.760> based<00:08:34.940> on<00:08:35.120> like<00:08:35.330> what 00:08:35.500 --> 00:08:35.510 align:start position:0% estimating that just based on like what 00:08:35.510 --> 00:08:38.560 align:start position:0% estimating that just based on like what method<00:08:35.900> the<00:08:36.169> contracts<00:08:36.740> calling<00:08:37.219> and<00:08:37.570> the 00:08:38.560 --> 00:08:38.570 align:start position:0% method the contracts calling and the 00:08:38.570 --> 00:08:40.760 align:start position:0% method the contracts calling and the average<00:08:38.900> price<00:08:39.169> of<00:08:39.200> gas<00:08:39.529> at<00:08:39.770> the<00:08:39.919> time 00:08:40.760 --> 00:08:40.770 align:start position:0% average price of gas at the time 00:08:40.770 --> 00:08:44.540 align:start position:0% average price of gas at the time the<00:08:40.890> same<00:08:41.250> for<00:08:41.580> the<00:08:42.919> estimated<00:08:43.919> wait<00:08:44.099> time<00:08:44.130> we 00:08:44.540 --> 00:08:44.550 align:start position:0% the same for the estimated wait time we 00:08:44.550 --> 00:08:46.510 align:start position:0% the same for the estimated wait time we can<00:08:44.730> just<00:08:44.910> kind<00:08:45.120> of<00:08:45.180> see<00:08:45.360> how<00:08:45.390> long 00:08:46.510 --> 00:08:46.520 align:start position:0% can just kind of see how long 00:08:46.520 --> 00:08:48.650 align:start position:0% can just kind of see how long transactions<00:08:47.520> are<00:08:47.640> taking<00:08:47.790> at<00:08:48.120> a<00:08:48.180> set<00:08:48.420> gas 00:08:48.650 --> 00:08:48.660 align:start position:0% transactions are taking at a set gas 00:08:48.660 --> 00:08:52.220 align:start position:0% transactions are taking at a set gas price<00:08:49.050> and<00:08:49.820> we're<00:08:50.820> just<00:08:50.970> assuming<00:08:51.510> things<00:08:51.779> and 00:08:52.220 --> 00:08:52.230 align:start position:0% price and we're just assuming things and 00:08:52.230 --> 00:08:53.990 align:start position:0% price and we're just assuming things and we're<00:08:52.950> just<00:08:53.040> kind<00:08:53.279> of<00:08:53.339> guessing 00:08:53.990 --> 00:08:54.000 align:start position:0% we're just kind of guessing 00:08:54.000 --> 00:08:55.550 align:start position:0% we're just kind of guessing for<00:08:54.180> the<00:08:54.240> most<00:08:54.390> part<00:08:54.510> obviously<00:08:54.779> users<00:08:55.350> can 00:08:55.550 --> 00:08:55.560 align:start position:0% for the most part obviously users can 00:08:55.560 --> 00:08:57.680 align:start position:0% for the most part obviously users can change<00:08:55.770> how<00:08:56.730> much<00:08:56.850> faster<00:08:57.270> paying<00:08:57.480> for 00:08:57.680 --> 00:08:57.690 align:start position:0% change how much faster paying for 00:08:57.690 --> 00:08:59.600 align:start position:0% change how much faster paying for transaction<00:08:58.350> but<00:08:58.950> just<00:08:59.250> keeping<00:08:59.490> that 00:08:59.600 --> 00:08:59.610 align:start position:0% transaction but just keeping that 00:08:59.610 --> 00:09:01.960 align:start position:0% transaction but just keeping that expectation<00:09:00.300> of<00:09:00.450> threat<00:09:00.720> is<00:09:00.930> really<00:09:01.200> helpful 00:09:01.960 --> 00:09:01.970 align:start position:0% expectation of threat is really helpful 00:09:01.970 --> 00:09:05.360 align:start position:0% expectation of threat is really helpful so<00:09:02.970> I<00:09:03.000> do<00:09:03.690> like<00:09:03.899> a<00:09:03.959> quick<00:09:04.170> diagram<00:09:04.529> also<00:09:05.100> like 00:09:05.360 --> 00:09:05.370 align:start position:0% so I do like a quick diagram also like 00:09:05.370 --> 00:09:06.769 align:start position:0% so I do like a quick diagram also like another<00:09:05.610> technique<00:09:06.029> that<00:09:06.089> we're<00:09:06.360> using<00:09:06.480> here 00:09:06.769 --> 00:09:06.779 align:start position:0% another technique that we're using here 00:09:06.779 --> 00:09:08.840 align:start position:0% another technique that we're using here which<00:09:06.990> is<00:09:07.140> like<00:09:07.320> trying<00:09:07.529> to<00:09:07.770> keep<00:09:08.220> wet<00:09:08.490> free 00:09:08.840 --> 00:09:08.850 align:start position:0% which is like trying to keep wet free 00:09:08.850 --> 00:09:10.510 align:start position:0% which is like trying to keep wet free away<00:09:09.060> from<00:09:09.300> the<00:09:09.390> user<00:09:09.600> as<00:09:09.899> long<00:09:10.110> as<00:09:10.230> possible 00:09:10.510 --> 00:09:10.520 align:start position:0% away from the user as long as possible 00:09:10.520 --> 00:09:12.650 align:start position:0% away from the user as long as possible we<00:09:11.520> don't<00:09:11.640> want<00:09:11.850> to<00:09:11.910> hit<00:09:12.029> somebody<00:09:12.360> right<00:09:12.420> off 00:09:12.650 --> 00:09:12.660 align:start position:0% we don't want to hit somebody right off 00:09:12.660 --> 00:09:14.420 align:start position:0% we don't want to hit somebody right off the<00:09:12.810> bat<00:09:12.959> with<00:09:13.170> a<00:09:13.260> connect<00:09:13.529> dialog<00:09:13.980> or<00:09:14.279> we 00:09:14.420 --> 00:09:14.430 align:start position:0% the bat with a connect dialog or we 00:09:14.430 --> 00:09:16.460 align:start position:0% the bat with a connect dialog or we don't<00:09:14.580> want<00:09:14.760> to<00:09:14.850> minimize<00:09:15.420> functionality<00:09:16.380> in 00:09:16.460 --> 00:09:16.470 align:start position:0% don't want to minimize functionality in 00:09:16.470 --> 00:09:18.050 align:start position:0% don't want to minimize functionality in the<00:09:16.529> damage<00:09:16.950> so<00:09:17.130> like<00:09:17.310> they've<00:09:17.490> done<00:09:17.520> some 00:09:18.050 --> 00:09:18.060 align:start position:0% the damage so like they've done some 00:09:18.060 --> 00:09:21.410 align:start position:0% the damage so like they've done some sort<00:09:18.360> of<00:09:18.480> proof<00:09:19.080> that<00:09:19.110> they<00:09:19.500> are<00:09:19.800> on<00:09:20.160> Jane<00:09:21.089> or 00:09:21.410 --> 00:09:21.420 align:start position:0% sort of proof that they are on Jane or 00:09:21.420 --> 00:09:24.110 align:start position:0% sort of proof that they are on Jane or they're<00:09:22.140> connected<00:09:22.589> to<00:09:22.740> watching<00:09:23.190> so<00:09:23.430> once 00:09:24.110 --> 00:09:24.120 align:start position:0% they're connected to watching so once 00:09:24.120 --> 00:09:26.090 align:start position:0% they're connected to watching so once the<00:09:24.360> user<00:09:24.570> has<00:09:24.660> expressed<00:09:25.260> an<00:09:25.560> intention 00:09:26.090 --> 00:09:26.100 align:start position:0% the user has expressed an intention 00:09:26.100 --> 00:09:27.530 align:start position:0% the user has expressed an intention that's<00:09:26.640> when<00:09:26.850> we<00:09:26.940> start<00:09:27.209> doing<00:09:27.330> our 00:09:27.530 --> 00:09:27.540 align:start position:0% that's when we start doing our 00:09:27.540 --> 00:09:29.750 align:start position:0% that's when we start doing our pre-flight<00:09:27.839> transfer<00:09:28.589> you<00:09:29.100> should<00:09:29.310> have<00:09:29.610> like 00:09:29.750 --> 00:09:29.760 align:start position:0% pre-flight transfer you should have like 00:09:29.760 --> 00:09:31.400 align:start position:0% pre-flight transfer you should have like a<00:09:29.850> modern<00:09:30.180> browser<00:09:30.330> they<00:09:30.930> have<00:09:31.110> connected 00:09:31.400 --> 00:09:31.410 align:start position:0% a modern browser they have connected 00:09:31.410 --> 00:09:34.370 align:start position:0% a modern browser they have connected wallet<00:09:32.480> but<00:09:33.480> we're<00:09:33.630> on<00:09:33.750> the<00:09:33.839> right<00:09:33.959> network 00:09:34.370 --> 00:09:34.380 align:start position:0% wallet but we're on the right network 00:09:34.380 --> 00:09:36.470 align:start position:0% wallet but we're on the right network which<00:09:34.920> were<00:09:35.100> sure<00:09:35.700> like<00:09:35.910> those<00:09:36.089> things<00:09:36.330> are 00:09:36.470 --> 00:09:36.480 align:start position:0% which were sure like those things are 00:09:36.480 --> 00:09:38.269 align:start position:0% which were sure like those things are going<00:09:36.600> to<00:09:36.660> be<00:09:36.779> can<00:09:36.930> check<00:09:37.080> their<00:09:37.230> balance<00:09:37.680> you 00:09:38.269 --> 00:09:38.279 align:start position:0% going to be can check their balance you 00:09:38.279 --> 00:09:39.980 align:start position:0% going to be can check their balance you can<00:09:38.459> run<00:09:38.640> a<00:09:38.910> simulation<00:09:39.270> on<00:09:39.690> the<00:09:39.779> call<00:09:39.959> that 00:09:39.980 --> 00:09:39.990 align:start position:0% can run a simulation on the call that 00:09:39.990 --> 00:09:41.449 align:start position:0% can run a simulation on the call that they're<00:09:40.260> doing<00:09:40.380> you<00:09:40.589> get<00:09:40.680> that<00:09:40.830> transaction 00:09:41.449 --> 00:09:41.459 align:start position:0% they're doing you get that transaction 00:09:41.459 --> 00:09:43.370 align:start position:0% they're doing you get that transaction fee<00:09:41.700> then<00:09:42.300> we<00:09:42.390> can<00:09:42.540> check<00:09:42.720> their<00:09:42.930> balance<00:09:43.290> to 00:09:43.370 --> 00:09:43.380 align:start position:0% fee then we can check their balance to 00:09:43.380 --> 00:09:44.480 align:start position:0% fee then we can check their balance to make<00:09:43.529> sure<00:09:43.709> that<00:09:43.800> they're<00:09:43.950> gonna<00:09:44.070> have<00:09:44.220> enough 00:09:44.480 --> 00:09:44.490 align:start position:0% make sure that they're gonna have enough 00:09:44.490 --> 00:09:46.100 align:start position:0% make sure that they're gonna have enough money<00:09:44.520> for<00:09:44.940> what<00:09:45.120> we're<00:09:45.270> trying<00:09:45.510> to<00:09:45.600> buy<00:09:45.720> and 00:09:46.100 --> 00:09:46.110 align:start position:0% money for what we're trying to buy and 00:09:46.110 --> 00:09:48.319 align:start position:0% money for what we're trying to buy and the<00:09:46.589> transaction<00:09:47.220> fee<00:09:47.430> and<00:09:47.730> then<00:09:47.880> we<00:09:48.029> can<00:09:48.209> give 00:09:48.319 --> 00:09:48.329 align:start position:0% the transaction fee and then we can give 00:09:48.329 --> 00:09:51.139 align:start position:0% the transaction fee and then we can give them<00:09:48.510> stuffs<00:09:49.410> right<00:09:49.620> there<00:09:49.950> so<00:09:50.520> even<00:09:50.910> wait 00:09:51.139 --> 00:09:51.149 align:start position:0% them stuffs right there so even wait 00:09:51.149 --> 00:09:52.760 align:start position:0% them stuffs right there so even wait prevent<00:09:51.839> them<00:09:51.959> from<00:09:51.990> even<00:09:52.350> starting<00:09:52.709> a 00:09:52.760 --> 00:09:52.770 align:start position:0% prevent them from even starting a 00:09:52.770 --> 00:09:54.110 align:start position:0% prevent them from even starting a transaction<00:09:53.250> that<00:09:53.310> we<00:09:53.430> know<00:09:53.579> is<00:09:53.640> not<00:09:53.730> going<00:09:54.029> to 00:09:54.110 --> 00:09:54.120 align:start position:0% transaction that we know is not going to 00:09:54.120 --> 00:09:56.510 align:start position:0% transaction that we know is not going to work<00:09:54.470> so<00:09:55.470> once<00:09:55.649> we<00:09:55.770> have<00:09:55.860> all<00:09:55.890> that<00:09:56.010> we'll<00:09:56.370> give 00:09:56.510 --> 00:09:56.520 align:start position:0% work so once we have all that we'll give 00:09:56.520 --> 00:09:59.480 align:start position:0% work so once we have all that we'll give them<00:09:56.779> not<00:09:57.779> relying<00:09:58.230> on<00:09:58.500> the<00:09:58.680> wallet<00:09:58.860> UX<00:09:59.279> is 00:09:59.480 --> 00:09:59.490 align:start position:0% them not relying on the wallet UX is 00:09:59.490 --> 00:10:00.980 align:start position:0% them not relying on the wallet UX is also<00:09:59.880> like<00:10:00.120> something<00:10:00.360> that<00:10:00.510> we're<00:10:00.779> big 00:10:00.980 --> 00:10:00.990 align:start position:0% also like something that we're big 00:10:00.990 --> 00:10:03.860 align:start position:0% also like something that we're big believers<00:10:01.380> in<00:10:01.740> so<00:10:02.160> we<00:10:02.310> want<00:10:02.490> to<00:10:02.640> show<00:10:03.329> the<00:10:03.690> user 00:10:03.860 --> 00:10:03.870 align:start position:0% believers in so we want to show the user 00:10:03.870 --> 00:10:06.680 align:start position:0% believers in so we want to show the user before<00:10:04.680> or<00:10:05.339> right<00:10:05.850> at<00:10:06.120> the<00:10:06.300> time<00:10:06.480> of<00:10:06.630> the 00:10:06.680 --> 00:10:06.690 align:start position:0% before or right at the time of the 00:10:06.690 --> 00:10:07.850 align:start position:0% before or right at the time of the transaction<00:10:07.050> like<00:10:07.350> as<00:10:07.470> much<00:10:07.680> of<00:10:07.829> that 00:10:07.850 --> 00:10:07.860 align:start position:0% transaction like as much of that 00:10:07.860 --> 00:10:09.350 align:start position:0% transaction like as much of that information<00:10:08.279> as<00:10:08.640> possible 00:10:09.350 --> 00:10:09.360 align:start position:0% information as possible 00:10:09.360 --> 00:10:12.769 align:start position:0% information as possible so<00:10:09.930> once<00:10:10.800> we've<00:10:11.040> given<00:10:11.250> all<00:10:11.490> that<00:10:11.760> data<00:10:12.209> over 00:10:12.769 --> 00:10:12.779 align:start position:0% so once we've given all that data over 00:10:12.779 --> 00:10:14.569 align:start position:0% so once we've given all that data over to<00:10:12.959> the<00:10:12.990> user<00:10:13.200> they<00:10:13.529> can<00:10:13.680> make<00:10:13.800> the<00:10:13.980> informed 00:10:14.569 --> 00:10:14.579 align:start position:0% to the user they can make the informed 00:10:14.579 --> 00:10:16.579 align:start position:0% to the user they can make the informed decision<00:10:15.000> to<00:10:15.209> be<00:10:15.360> confident<00:10:15.930> that<00:10:16.410> what 00:10:16.579 --> 00:10:16.589 align:start position:0% decision to be confident that what 00:10:16.589 --> 00:10:17.840 align:start position:0% decision to be confident that what they're<00:10:16.770> doing<00:10:17.040> is<00:10:17.160> actually<00:10:17.490> going<00:10:17.610> to<00:10:17.700> work 00:10:17.840 --> 00:10:17.850 align:start position:0% they're doing is actually going to work 00:10:17.850 --> 00:10:19.010 align:start position:0% they're doing is actually going to work and<00:10:18.060> it's<00:10:18.240> going<00:10:18.360> to<00:10:18.450> work<00:10:18.570> the<00:10:18.720> way<00:10:18.750> they 00:10:19.010 --> 00:10:19.020 align:start position:0% and it's going to work the way they 00:10:19.020 --> 00:10:20.930 align:start position:0% and it's going to work the way they expect<00:10:19.350> it<00:10:19.470> to<00:10:19.649> and<00:10:20.130> then<00:10:20.220> they<00:10:20.370> have<00:10:20.520> an<00:10:20.640> idea 00:10:20.930 --> 00:10:20.940 align:start position:0% expect it to and then they have an idea 00:10:20.940 --> 00:10:23.510 align:start position:0% expect it to and then they have an idea of<00:10:21.029> how<00:10:21.180> long<00:10:21.360> it's<00:10:21.540> going<00:10:21.660> to<00:10:21.720> take<00:10:21.950> so<00:10:22.950> we'll 00:10:23.510 --> 00:10:23.520 align:start position:0% of how long it's going to take so we'll 00:10:23.520 --> 00:10:24.639 align:start position:0% of how long it's going to take so we'll just<00:10:23.670> go<00:10:23.850> through 00:10:24.639 --> 00:10:24.649 align:start position:0% just go through 00:10:24.649 --> 00:10:27.129 align:start position:0% just go through and<00:10:24.949> it's<00:10:25.129> basically<00:10:25.389> okay<00:10:26.569> though<00:10:26.720> the<00:10:26.930> heirs 00:10:27.129 --> 00:10:27.139 align:start position:0% and it's basically okay though the heirs 00:10:27.139 --> 00:10:28.629 align:start position:0% and it's basically okay though the heirs along<00:10:27.499> the<00:10:27.619> way<00:10:27.709> if<00:10:27.829> there's<00:10:28.009> any<00:10:28.189> problems 00:10:28.629 --> 00:10:28.639 align:start position:0% along the way if there's any problems 00:10:28.639 --> 00:10:30.489 align:start position:0% along the way if there's any problems that'll<00:10:28.910> help<00:10:28.970> remedy<00:10:29.269> and<00:10:29.629> then<00:10:29.779> we<00:10:29.899> finally 00:10:30.489 --> 00:10:30.499 align:start position:0% that'll help remedy and then we finally 00:10:30.499 --> 00:10:32.590 align:start position:0% that'll help remedy and then we finally finished<00:10:31.100> it<00:10:31.309> up<00:10:31.399> with<00:10:31.639> a<00:10:31.670> summary<00:10:32.209> of<00:10:32.480> the 00:10:32.590 --> 00:10:32.600 align:start position:0% finished it up with a summary of the 00:10:32.600 --> 00:10:34.749 align:start position:0% finished it up with a summary of the transaction<00:10:32.839> details<00:10:33.559> that<00:10:34.249> tell<00:10:34.279> them 00:10:34.749 --> 00:10:34.759 align:start position:0% transaction details that tell them 00:10:34.759 --> 00:10:36.309 align:start position:0% transaction details that tell them exactly<00:10:34.910> how<00:10:35.300> much<00:10:35.389> it<00:10:35.569> costs<00:10:35.930> and<00:10:35.959> like<00:10:36.139> where 00:10:36.309 --> 00:10:36.319 align:start position:0% exactly how much it costs and like where 00:10:36.319 --> 00:10:37.569 align:start position:0% exactly how much it costs and like where they<00:10:36.410> can<00:10:36.559> get<00:10:36.649> more<00:10:36.769> information<00:10:37.069> either 00:10:37.569 --> 00:10:37.579 align:start position:0% they can get more information either 00:10:37.579 --> 00:10:39.579 align:start position:0% they can get more information either link<00:10:38.180> to<00:10:38.269> either<00:10:38.420> scan<00:10:38.779> or<00:10:39.019> open<00:10:39.290> C<00:10:39.439> or 00:10:39.579 --> 00:10:39.589 align:start position:0% link to either scan or open C or 00:10:39.589 --> 00:10:42.629 align:start position:0% link to either scan or open C or something<00:10:39.769> like<00:10:39.980> that 00:10:42.629 --> 00:10:42.639 align:start position:0% 00:10:42.639 --> 00:10:45.910 align:start position:0% Thanks<00:10:43.639> so<00:10:44.019> I'm<00:10:45.019> gonna<00:10:45.230> dive<00:10:45.499> a<00:10:45.529> little<00:10:45.769> bit 00:10:45.910 --> 00:10:45.920 align:start position:0% Thanks so I'm gonna dive a little bit 00:10:45.920 --> 00:10:47.410 align:start position:0% Thanks so I'm gonna dive a little bit deeper<00:10:46.040> in<00:10:46.429> soos<00:10:46.670> or<00:10:46.970> some<00:10:47.179> of<00:10:47.240> the<00:10:47.329> more 00:10:47.410 --> 00:10:47.420 align:start position:0% deeper in soos or some of the more 00:10:47.420 --> 00:10:49.749 align:start position:0% deeper in soos or some of the more actionable<00:10:47.839> tips<00:10:48.470> that<00:10:48.740> came<00:10:48.889> out<00:10:49.100> of<00:10:49.220> this 00:10:49.749 --> 00:10:49.759 align:start position:0% actionable tips that came out of this 00:10:49.759 --> 00:10:54.639 align:start position:0% actionable tips that came out of this research<00:10:50.119> in<00:10:50.389> this<00:10:51.730> demo<00:10:52.730> so<00:10:53.290> in<00:10:54.290> the<00:10:54.379> first 00:10:54.639 --> 00:10:54.649 align:start position:0% research in this demo so in the first 00:10:54.649 --> 00:10:58.150 align:start position:0% research in this demo so in the first lesson<00:10:55.100> that<00:10:55.490> we<00:10:55.579> saw<00:10:55.819> we<00:10:56.449> came<00:10:56.720> up<00:10:56.869> with<00:10:57.160> was 00:10:58.150 --> 00:10:58.160 align:start position:0% lesson that we saw we came up with was 00:10:58.160 --> 00:11:00.069 align:start position:0% lesson that we saw we came up with was to<00:10:58.459> not<00:10:58.610> rely<00:10:58.850> too<00:10:58.910> much<00:10:59.089> on<00:10:59.360> water<00:10:59.540> collects<00:10:59.869> a 00:11:00.069 --> 00:11:00.079 align:start position:0% to not rely too much on water collects a 00:11:00.079 --> 00:11:03.009 align:start position:0% to not rely too much on water collects a lot<00:11:00.110> of<00:11:00.290> data<00:11:00.439> out<00:11:00.769> there<00:11:01.749> sort<00:11:02.749> of<00:11:02.839> thing<00:11:02.959> oh 00:11:03.009 --> 00:11:03.019 align:start position:0% lot of data out there sort of thing oh 00:11:03.019 --> 00:11:04.299 align:start position:0% lot of data out there sort of thing oh we<00:11:03.230> know<00:11:03.350> the<00:11:03.529> wallet<00:11:03.800> can<00:11:03.949> handle<00:11:04.220> the 00:11:04.299 --> 00:11:04.309 align:start position:0% we know the wallet can handle the 00:11:04.309 --> 00:11:05.799 align:start position:0% we know the wallet can handle the transaction<00:11:04.910> we<00:11:05.059> just<00:11:05.209> need<00:11:05.329> to<00:11:05.420> get<00:11:05.569> the<00:11:05.660> user 00:11:05.799 --> 00:11:05.809 align:start position:0% transaction we just need to get the user 00:11:05.809 --> 00:11:07.960 align:start position:0% transaction we just need to get the user to<00:11:06.050> that<00:11:06.290> point<00:11:06.559> and<00:11:06.769> the<00:11:07.429> issue<00:11:07.550> here<00:11:07.850> is<00:11:07.939> that 00:11:07.960 --> 00:11:07.970 align:start position:0% to that point and the issue here is that 00:11:07.970 --> 00:11:10.119 align:start position:0% to that point and the issue here is that wallets<00:11:08.389> can't<00:11:08.929> be<00:11:09.050> specific<00:11:09.230> and<00:11:09.800> actually 00:11:10.119 --> 00:11:10.129 align:start position:0% wallets can't be specific and actually 00:11:10.129 --> 00:11:12.040 align:start position:0% wallets can't be specific and actually design<00:11:10.249> the<00:11:11.149> lots<00:11:11.329> of<00:11:11.420> different<00:11:11.720> use<00:11:11.809> cases 00:11:12.040 --> 00:11:12.050 align:start position:0% design the lots of different use cases 00:11:12.050 --> 00:11:14.889 align:start position:0% design the lots of different use cases and<00:11:13.009> I'm<00:11:13.160> within<00:11:13.490> the<00:11:13.699> damp<00:11:13.879> itself<00:11:14.329> you<00:11:14.720> can 00:11:14.889 --> 00:11:14.899 align:start position:0% and I'm within the damp itself you can 00:11:14.899 --> 00:11:16.929 align:start position:0% and I'm within the damp itself you can talk<00:11:15.139> much<00:11:15.589> more<00:11:15.619> clearly<00:11:16.009> about<00:11:16.279> these<00:11:16.639> or 00:11:16.929 --> 00:11:16.939 align:start position:0% talk much more clearly about these or 00:11:16.939 --> 00:11:18.850 align:start position:0% talk much more clearly about these or the<00:11:17.209> task<00:11:17.449> at<00:11:17.779> hand<00:11:17.809> the<00:11:18.199> users<00:11:18.499> trying<00:11:18.769> to 00:11:18.850 --> 00:11:18.860 align:start position:0% the task at hand the users trying to 00:11:18.860 --> 00:11:20.980 align:start position:0% the task at hand the users trying to achieve<00:11:19.160> we<00:11:19.910> should<00:11:20.119> help<00:11:20.300> reduce<00:11:20.420> the<00:11:20.749> sort 00:11:20.980 --> 00:11:20.990 align:start position:0% achieve we should help reduce the sort 00:11:20.990 --> 00:11:23.980 align:start position:0% achieve we should help reduce the sort of<00:11:21.050> cognitive<00:11:21.350> load<00:11:21.589> on<00:11:21.920> the<00:11:22.040> user<00:11:22.869> so<00:11:23.869> for 00:11:23.980 --> 00:11:23.990 align:start position:0% of cognitive load on the user so for 00:11:23.990 --> 00:11:25.600 align:start position:0% of cognitive load on the user so for example<00:11:24.439> we<00:11:24.679> talked<00:11:24.889> about<00:11:25.040> the<00:11:25.249> fact<00:11:25.399> that 00:11:25.600 --> 00:11:25.610 align:start position:0% example we talked about the fact that 00:11:25.610 --> 00:11:28.030 align:start position:0% example we talked about the fact that once<00:11:25.879> the<00:11:25.999> transaction<00:11:26.329> started<00:11:26.899> is<00:11:27.889> the 00:11:28.030 --> 00:11:28.040 align:start position:0% once the transaction started is the 00:11:28.040 --> 00:11:30.009 align:start position:0% once the transaction started is the process<00:11:28.429> of<00:11:28.579> participating<00:11:29.300> send<00:11:29.569> problem 00:11:30.009 --> 00:11:30.019 align:start position:0% process of participating send problem 00:11:30.019 --> 00:11:32.049 align:start position:0% process of participating send problem just<00:11:30.230> so<00:11:30.319> generic<00:11:30.860> the<00:11:31.339> transaction<00:11:31.939> is 00:11:32.049 --> 00:11:32.059 align:start position:0% just so generic the transaction is 00:11:32.059 --> 00:11:35.590 align:start position:0% just so generic the transaction is pending<00:11:32.300> law<00:11:32.689> in<00:11:33.230> progress<00:11:34.540> this<00:11:35.540> is 00:11:35.590 --> 00:11:35.600 align:start position:0% pending law in progress this is 00:11:35.600 --> 00:11:38.889 align:start position:0% pending law in progress this is specifically<00:11:36.139> important<00:11:36.649> error<00:11:37.550> messages<00:11:38.059> - 00:11:38.889 --> 00:11:38.899 align:start position:0% specifically important error messages - 00:11:38.899 --> 00:11:40.689 align:start position:0% specifically important error messages - you<00:11:39.379> might<00:11:39.529> be<00:11:39.620> familiar<00:11:39.709> with<00:11:40.040> seeing<00:11:40.309> sort 00:11:40.689 --> 00:11:40.699 align:start position:0% you might be familiar with seeing sort 00:11:40.699 --> 00:11:43.600 align:start position:0% you might be familiar with seeing sort of<00:11:41.079> you<00:11:42.079> know<00:11:42.199> just<00:11:42.319> generic<00:11:42.769> insufficient 00:11:43.600 --> 00:11:43.610 align:start position:0% of you know just generic insufficient 00:11:43.610 --> 00:11:45.700 align:start position:0% of you know just generic insufficient balance<00:11:44.300> messages<00:11:44.899> of<00:11:45.230> the 00:11:45.700 --> 00:11:45.710 align:start position:0% balance messages of the 00:11:45.710 --> 00:11:48.639 align:start position:0% balance messages of the and<00:11:46.399> this<00:11:47.360> doesn't<00:11:47.600> really<00:11:47.750> help<00:11:48.110> new<00:11:48.620> users 00:11:48.639 --> 00:11:48.649 align:start position:0% and this doesn't really help new users 00:11:48.649 --> 00:11:51.280 align:start position:0% and this doesn't really help new users or<00:11:49.339> less<00:11:49.910> confident<00:11:50.360> users<00:11:50.660> actually<00:11:51.080> help 00:11:51.280 --> 00:11:51.290 align:start position:0% or less confident users actually help 00:11:51.290 --> 00:11:52.300 align:start position:0% or less confident users actually help sorry 00:11:52.300 --> 00:11:52.310 align:start position:0% sorry 00:11:52.310 --> 00:11:54.310 align:start position:0% sorry get<00:11:53.240> back<00:11:53.360> on<00:11:53.510> track<00:11:53.630> what<00:11:53.990> they're<00:11:54.110> trying<00:11:54.290> to 00:11:54.310 --> 00:11:54.320 align:start position:0% get back on track what they're trying to 00:11:54.320 --> 00:11:57.340 align:start position:0% get back on track what they're trying to do<00:11:55.029> that<00:11:56.029> shims<00:11:56.330> a<00:11:56.450> lot<00:11:56.570> of<00:11:56.690> pre-existing 00:11:57.340 --> 00:11:57.350 align:start position:0% do that shims a lot of pre-existing 00:11:57.350 --> 00:11:58.570 align:start position:0% do that shims a lot of pre-existing knowledge<00:11:57.470> which<00:11:57.890> normal<00:11:58.160> users<00:11:58.399> are<00:11:58.490> going 00:11:58.570 --> 00:11:58.580 align:start position:0% knowledge which normal users are going 00:11:58.580 --> 00:12:00.670 align:start position:0% knowledge which normal users are going to<00:11:58.640> have<00:11:58.820> so<00:11:59.600> again<00:11:59.810> within<00:12:00.020> your<00:12:00.170> data<00:12:00.440> needs 00:12:00.670 --> 00:12:00.680 align:start position:0% to have so again within your data needs 00:12:00.680 --> 00:12:02.139 align:start position:0% to have so again within your data needs to<00:12:00.860> be<00:12:00.950> able<00:12:01.040> to<00:12:01.190> make<00:12:01.339> and<00:12:01.730> to<00:12:01.880> make<00:12:02.000> that 00:12:02.139 --> 00:12:02.149 align:start position:0% to be able to make and to make that 00:12:02.149 --> 00:12:04.210 align:start position:0% to be able to make and to make that effort<00:12:02.330> in<00:12:02.570> order<00:12:02.660> to<00:12:02.870> help<00:12:02.990> users<00:12:03.260> get<00:12:04.010> past 00:12:04.210 --> 00:12:04.220 align:start position:0% effort in order to help users get past 00:12:04.220 --> 00:12:07.510 align:start position:0% effort in order to help users get past this<00:12:04.480> popsicle<00:12:05.480> and<00:12:05.779> talk<00:12:06.560> to<00:12:06.680> end<00:12:06.860> in<00:12:07.040> context 00:12:07.510 --> 00:12:07.520 align:start position:0% this popsicle and talk to end in context 00:12:07.520 --> 00:12:09.970 align:start position:0% this popsicle and talk to end in context with<00:12:07.610> what<00:12:07.700> the<00:12:07.790> users<00:12:08.029> trying<00:12:08.240> to<00:12:08.330> do<00:12:08.420> so<00:12:08.980> you 00:12:09.970 --> 00:12:09.980 align:start position:0% with what the users trying to do so you 00:12:09.980 --> 00:12:11.380 align:start position:0% with what the users trying to do so you know<00:12:10.130> how<00:12:10.250> do<00:12:10.370> not<00:12:10.520> transaction<00:12:11.029> fees<00:12:11.209> in 00:12:11.380 --> 00:12:11.390 align:start position:0% know how do not transaction fees in 00:12:11.390 --> 00:12:15.030 align:start position:0% know how do not transaction fees in order<00:12:11.420> to<00:12:11.630> pay<00:12:11.839> particular<00:12:12.080> in<00:12:12.500> this<00:12:12.620> instance 00:12:15.030 --> 00:12:15.040 align:start position:0% order to pay particular in this instance 00:12:15.040 --> 00:12:18.610 align:start position:0% order to pay particular in this instance second<00:12:16.040> lesson<00:12:16.220> is<00:12:16.670> around<00:12:17.300> prevention<00:12:17.600> so<00:12:18.230> we 00:12:18.610 --> 00:12:18.620 align:start position:0% second lesson is around prevention so we 00:12:18.620 --> 00:12:21.460 align:start position:0% second lesson is around prevention so we spoke<00:12:18.860> previously<00:12:19.370> about<00:12:20.470> the 00:12:21.460 --> 00:12:21.470 align:start position:0% spoke previously about the 00:12:21.470 --> 00:12:22.750 align:start position:0% spoke previously about the irreversibility<00:12:22.040> of<00:12:22.339> blockchain 00:12:22.750 --> 00:12:22.760 align:start position:0% irreversibility of blockchain 00:12:22.760 --> 00:12:25.120 align:start position:0% irreversibility of blockchain transactions<00:12:23.420> to<00:12:24.020> super<00:12:24.440> important<00:12:24.860> speeds 00:12:25.120 --> 00:12:25.130 align:start position:0% transactions to super important speeds 00:12:25.130 --> 00:12:26.920 align:start position:0% transactions to super important speeds or<00:12:25.399> like<00:12:25.520> Tessa<00:12:25.760> pacing<00:12:26.180> and<00:12:26.270> designing<00:12:26.720> for 00:12:26.920 --> 00:12:26.930 align:start position:0% or like Tessa pacing and designing for 00:12:26.930 --> 00:12:29.650 align:start position:0% or like Tessa pacing and designing for these<00:12:27.140> sort<00:12:27.380> of<00:12:27.790> engines<00:12:28.790> are<00:12:29.029> errors<00:12:29.360> that 00:12:29.650 --> 00:12:29.660 align:start position:0% these sort of engines are errors that 00:12:29.660 --> 00:12:31.389 align:start position:0% these sort of engines are errors that might<00:12:29.810> occur<00:12:30.080> so<00:12:30.860> that<00:12:30.890> would<00:12:31.160> be<00:12:31.220> like 00:12:31.389 --> 00:12:31.399 align:start position:0% might occur so that would be like 00:12:31.399 --> 00:12:34.150 align:start position:0% might occur so that would be like passive<00:12:31.880> UI<00:12:32.089> such<00:12:32.510> as<00:12:32.750> the<00:12:33.080> indications<00:12:34.040> in 00:12:34.150 --> 00:12:34.160 align:start position:0% passive UI such as the indications in 00:12:34.160 --> 00:12:35.860 align:start position:0% passive UI such as the indications in the<00:12:34.250> top<00:12:34.399> right<00:12:34.610> corner<00:12:34.640> about<00:12:35.240> your<00:12:35.600> wallet 00:12:35.860 --> 00:12:35.870 align:start position:0% the top right corner about your wallet 00:12:35.870 --> 00:12:38.440 align:start position:0% the top right corner about your wallet the<00:12:35.990> users<00:12:36.290> using<00:12:36.649> their<00:12:37.399> offices<00:12:37.880> that<00:12:38.120> I<00:12:38.209> try 00:12:38.440 --> 00:12:38.450 align:start position:0% the users using their offices that I try 00:12:38.450 --> 00:12:43.780 align:start position:0% the users using their offices that I try and<00:12:38.510> transact<00:12:39.020> with<00:12:39.140> into<00:12:39.560> wallet<00:12:42.700> but<00:12:43.700> it 00:12:43.780 --> 00:12:43.790 align:start position:0% and transact with into wallet but it 00:12:43.790 --> 00:12:45.280 align:start position:0% and transact with into wallet but it also<00:12:43.910> might<00:12:44.180> be<00:12:44.240> you<00:12:44.779> know<00:12:44.899> actually 00:12:45.280 --> 00:12:45.290 align:start position:0% also might be you know actually 00:12:45.290 --> 00:12:46.780 align:start position:0% also might be you know actually intentionally<00:12:45.920> designing<00:12:46.490> the<00:12:46.610> some 00:12:46.780 --> 00:12:46.790 align:start position:0% intentionally designing the some 00:12:46.790 --> 00:12:50.949 align:start position:0% intentionally designing the some friction<00:12:47.240> into<00:12:47.540> this<00:12:47.720> process<00:12:48.200> so<00:12:48.640> kind<00:12:49.640> of<00:12:49.959> is 00:12:50.949 --> 00:12:50.959 align:start position:0% friction into this process so kind of is 00:12:50.959 --> 00:12:52.900 align:start position:0% friction into this process so kind of is weird<00:12:51.230> to<00:12:51.350> say<00:12:51.529> this<00:12:51.560> quite<00:12:52.130> often<00:12:52.279> tells<00:12:52.610> me 00:12:52.900 --> 00:12:52.910 align:start position:0% weird to say this quite often tells me 00:12:52.910 --> 00:12:55.210 align:start position:0% weird to say this quite often tells me reducing<00:12:53.779> friction<00:12:54.040> reducing<00:12:55.040> friction 00:12:55.210 --> 00:12:55.220 align:start position:0% reducing friction reducing friction 00:12:55.220 --> 00:12:57.610 align:start position:0% reducing friction reducing friction reducing<00:12:55.910> Clips<00:12:56.260> reducing<00:12:57.260> the<00:12:57.320> nature 00:12:57.610 --> 00:12:57.620 align:start position:0% reducing Clips reducing the nature 00:12:57.620 --> 00:13:00.340 align:start position:0% reducing Clips reducing the nature irreversibility<00:12:58.610> and<00:12:58.810> we<00:12:59.810> felt<00:13:00.140> it<00:13:00.290> was 00:13:00.340 --> 00:13:00.350 align:start position:0% irreversibility and we felt it was 00:13:00.350 --> 00:13:03.040 align:start position:0% irreversibility and we felt it was important<00:13:00.920> to<00:13:01.040> give<00:13:01.220> the<00:13:01.339> users<00:13:01.670> final<00:13:02.420> tunity 00:13:03.040 --> 00:13:03.050 align:start position:0% important to give the users final tunity 00:13:03.050 --> 00:13:05.470 align:start position:0% important to give the users final tunity to<00:13:03.589> double-check<00:13:03.860> everything<00:13:04.310> written<00:13:05.209> in<00:13:05.390> a 00:13:05.470 --> 00:13:05.480 align:start position:0% to double-check everything written in a 00:13:05.480 --> 00:13:07.690 align:start position:0% to double-check everything written in a language<00:13:05.600> that<00:13:05.900> they<00:13:06.320> understand<00:13:07.160> compared 00:13:07.690 --> 00:13:07.700 align:start position:0% language that they understand compared 00:13:07.700 --> 00:13:09.930 align:start position:0% language that they understand compared to<00:13:07.990> what<00:13:08.990> it<00:13:09.080> would<00:13:09.170> be<00:13:09.410> more<00:13:09.560> technically 00:13:09.930 --> 00:13:09.940 align:start position:0% to what it would be more technically 00:13:09.940 --> 00:13:14.050 align:start position:0% to what it would be more technically unless<00:13:10.940> specifically<00:13:11.450> do<00:13:12.610> we<00:13:13.610> actually<00:13:13.730> feel 00:13:14.050 --> 00:13:14.060 align:start position:0% unless specifically do we actually feel 00:13:14.060 --> 00:13:16.480 align:start position:0% unless specifically do we actually feel this<00:13:14.240> is<00:13:14.420> like<00:13:14.630> yeah<00:13:15.529> super<00:13:16.040> important<00:13:16.370> way 00:13:16.480 --> 00:13:16.490 align:start position:0% this is like yeah super important way 00:13:16.490 --> 00:13:19.000 align:start position:0% this is like yeah super important way they<00:13:17.450> user<00:13:17.690> can<00:13:17.839> check<00:13:18.020> everything's<00:13:18.529> correct 00:13:19.000 --> 00:13:19.010 align:start position:0% they user can check everything's correct 00:13:19.010 --> 00:13:24.699 align:start position:0% they user can check everything's correct I<00:13:19.400> made<00:13:19.550> to<00:13:19.610> be<00:13:19.700> 90%<00:13:20.209> confident<00:13:20.660> transacting 00:13:24.699 --> 00:13:24.709 align:start position:0% 00:13:24.709 --> 00:13:29.150 align:start position:0% thirdly<00:13:25.709> is<00:13:26.040> to<00:13:26.190> set<00:13:26.399> user<00:13:26.610> expectations<00:13:27.740> so<00:13:28.740> I 00:13:29.150 --> 00:13:29.160 align:start position:0% thirdly is to set user expectations so I 00:13:29.160 --> 00:13:31.040 align:start position:0% thirdly is to set user expectations so I guess<00:13:29.730> the<00:13:29.880> main<00:13:30.029> places<00:13:30.570> you<00:13:30.690> want<00:13:30.839> to<00:13:30.899> say 00:13:31.040 --> 00:13:31.050 align:start position:0% guess the main places you want to say 00:13:31.050 --> 00:13:33.620 align:start position:0% guess the main places you want to say expectations<00:13:31.680> here<00:13:31.860> are<00:13:32.100> around<00:13:32.370> fees<00:13:33.300> and 00:13:33.620 --> 00:13:33.630 align:start position:0% expectations here are around fees and 00:13:33.630 --> 00:13:37.040 align:start position:0% expectations here are around fees and behind<00:13:33.899> me<00:13:34.339> so<00:13:35.360> again<00:13:36.360> on<00:13:36.630> this<00:13:36.810> sort<00:13:37.019> of 00:13:37.040 --> 00:13:37.050 align:start position:0% behind me so again on this sort of 00:13:37.050 --> 00:13:40.210 align:start position:0% behind me so again on this sort of checkout<00:13:37.440> screen<00:13:38.029> we<00:13:39.029> reference<00:13:39.630> the 00:13:40.210 --> 00:13:40.220 align:start position:0% checkout screen we reference the 00:13:40.220 --> 00:13:43.610 align:start position:0% checkout screen we reference the transaction<00:13:41.220> fee<00:13:41.399> at<00:13:41.699> the<00:13:42.149> time<00:13:42.360> I<00:13:43.139> think<00:13:43.440> it's 00:13:43.610 --> 00:13:43.620 align:start position:0% transaction fee at the time I think it's 00:13:43.620 --> 00:13:45.650 align:start position:0% transaction fee at the time I think it's important<00:13:44.010> to<00:13:44.040> recognize<00:13:44.190> the<00:13:44.579> fee<00:13:44.760> or<00:13:45.209> wallet 00:13:45.650 --> 00:13:45.660 align:start position:0% important to recognize the fee or wallet 00:13:45.660 --> 00:13:48.259 align:start position:0% important to recognize the fee or wallet again<00:13:46.220> this<00:13:47.220> prevents<00:13:47.639> it<00:13:47.760> from<00:13:47.820> feeling<00:13:48.060> a 00:13:48.259 --> 00:13:48.269 align:start position:0% again this prevents it from feeling a 00:13:48.269 --> 00:13:49.850 align:start position:0% again this prevents it from feeling a bit<00:13:48.420> like<00:13:48.570> a<00:13:48.600> hidden<00:13:49.199> thing<00:13:49.440> which<00:13:49.680> I<00:13:49.740> might 00:13:49.850 --> 00:13:49.860 align:start position:0% bit like a hidden thing which I might 00:13:49.860 --> 00:13:53.269 align:start position:0% bit like a hidden thing which I might end<00:13:49.980> up<00:13:50.100> the<00:13:50.220> roaming<00:13:50.519> trust<00:13:50.820> in<00:13:51.510> that<00:13:51.870> I<00:13:52.649> think 00:13:53.269 --> 00:13:53.279 align:start position:0% end up the roaming trust in that I think 00:13:53.279 --> 00:13:55.670 align:start position:0% end up the roaming trust in that I think a<00:13:53.579> lot<00:13:53.699> of<00:13:53.880> the<00:13:53.970> users<00:13:54.120> we<00:13:54.360> spoke<00:13:54.600> to<00:13:54.870> didn't 00:13:55.670 --> 00:13:55.680 align:start position:0% a lot of the users we spoke to didn't 00:13:55.680 --> 00:13:56.840 align:start position:0% a lot of the users we spoke to didn't have<00:13:55.800> pretty<00:13:56.010> great<00:13:56.220> knowledge<00:13:56.399> of<00:13:56.610> what<00:13:56.790> the 00:13:56.840 --> 00:13:56.850 align:start position:0% have pretty great knowledge of what the 00:13:56.850 --> 00:13:58.819 align:start position:0% have pretty great knowledge of what the transaction<00:13:57.389> fee<00:13:57.570> was<00:13:57.779> so<00:13:58.410> again<00:13:58.620> it<00:13:58.740> gives 00:13:58.819 --> 00:13:58.829 align:start position:0% transaction fee was so again it gives 00:13:58.829 --> 00:14:00.620 align:start position:0% transaction fee was so again it gives you<00:13:58.980> much<00:13:59.130> unity<00:13:59.430> to<00:13:59.760> sort<00:13:59.940> of<00:13:59.970> give<00:14:00.209> that<00:14:00.420> sort 00:14:00.620 --> 00:14:00.630 align:start position:0% you much unity to sort of give that sort 00:14:00.630 --> 00:14:02.300 align:start position:0% you much unity to sort of give that sort of<00:14:00.690> explanation<00:14:01.050> the<00:14:01.709> users<00:14:02.010> that<00:14:02.040> don't 00:14:02.300 --> 00:14:02.310 align:start position:0% of explanation the users that don't 00:14:02.310 --> 00:14:04.819 align:start position:0% of explanation the users that don't understand<00:14:03.199> there<00:14:04.199> seems<00:14:04.380> to<00:14:04.410> be<00:14:04.470> quite<00:14:04.800> a 00:14:04.819 --> 00:14:04.829 align:start position:0% understand there seems to be quite a 00:14:04.829 --> 00:14:06.470 align:start position:0% understand there seems to be quite a general<00:14:05.190> misconception<00:14:05.370> that<00:14:05.880> transaction 00:14:06.470 --> 00:14:06.480 align:start position:0% general misconception that transaction 00:14:06.480 --> 00:14:08.600 align:start position:0% general misconception that transaction fee<00:14:06.630> is<00:14:06.779> going<00:14:06.810> to<00:14:07.170> pick<00:14:07.290> down<00:14:07.610> teams 00:14:08.600 --> 00:14:08.610 align:start position:0% fee is going to pick down teams 00:14:08.610 --> 00:14:10.160 align:start position:0% fee is going to pick down teams themselves<00:14:08.820> it's<00:14:09.269> a<00:14:09.329> network<00:14:09.810> obviously 00:14:10.160 --> 00:14:10.170 align:start position:0% themselves it's a network obviously 00:14:10.170 --> 00:14:12.829 align:start position:0% themselves it's a network obviously isn't<00:14:11.070> going<00:14:11.220> to<00:14:11.279> help<00:14:11.339> and<00:14:11.839> understanding 00:14:12.829 --> 00:14:12.839 align:start position:0% isn't going to help and understanding 00:14:12.839 --> 00:14:16.460 align:start position:0% isn't going to help and understanding what's<00:14:12.990> going<00:14:13.019> on<00:14:13.290> and<00:14:14.839> also<00:14:15.839> the<00:14:16.019> estimated 00:14:16.460 --> 00:14:16.470 align:start position:0% what's going on and also the estimated 00:14:16.470 --> 00:14:18.769 align:start position:0% what's going on and also the estimated wait<00:14:16.589> time<00:14:16.620> so<00:14:17.100> might<00:14:17.310> explains<00:14:17.790> how<00:14:18.060> we<00:14:18.630> sort 00:14:18.769 --> 00:14:18.779 align:start position:0% wait time so might explains how we sort 00:14:18.779 --> 00:14:20.269 align:start position:0% wait time so might explains how we sort of<00:14:18.839> done<00:14:19.019> about<00:14:19.230> providing<00:14:19.560> that<00:14:19.769> to<00:14:19.920> the<00:14:20.010> area 00:14:20.269 --> 00:14:20.279 align:start position:0% of done about providing that to the area 00:14:20.279 --> 00:14:21.500 align:start position:0% of done about providing that to the area I<00:14:20.310> think<00:14:20.610> that's<00:14:20.820> really<00:14:20.970> important<00:14:21.480> that 00:14:21.500 --> 00:14:21.510 align:start position:0% I think that's really important that 00:14:21.510 --> 00:14:24.800 align:start position:0% I think that's really important that although<00:14:22.410> users<00:14:22.649> may<00:14:22.920> not<00:14:23.160> minds<00:14:23.910> the<00:14:24.660> way 00:14:24.800 --> 00:14:24.810 align:start position:0% although users may not minds the way 00:14:24.810 --> 00:14:27.290 align:start position:0% although users may not minds the way they<00:14:25.350> don't<00:14:25.649> like<00:14:25.829> the<00:14:26.550> Americans<00:14:26.910> over<00:14:27.180> live 00:14:27.290 --> 00:14:27.300 align:start position:0% they don't like the Americans over live 00:14:27.300 --> 00:14:28.840 align:start position:0% they don't like the Americans over live I<00:14:27.480> wouldn't<00:14:27.779> know<00:14:27.870> long<00:14:28.170> it's<00:14:28.470> going<00:14:28.560> to<00:14:28.620> take 00:14:28.840 --> 00:14:28.850 align:start position:0% I wouldn't know long it's going to take 00:14:28.850 --> 00:14:31.100 align:start position:0% I wouldn't know long it's going to take so<00:14:29.850> things<00:14:30.060> very<00:14:30.240> important<00:14:30.630> to<00:14:30.720> provide<00:14:30.959> this 00:14:31.100 --> 00:14:31.110 align:start position:0% so things very important to provide this 00:14:31.110 --> 00:14:32.480 align:start position:0% so things very important to provide this information<00:14:31.290> upfront<00:14:31.740> so<00:14:32.130> they<00:14:32.220> can<00:14:32.370> better 00:14:32.480 --> 00:14:32.490 align:start position:0% information upfront so they can better 00:14:32.490 --> 00:14:33.079 align:start position:0% information upfront so they can better plan 00:14:33.079 --> 00:14:33.089 align:start position:0% plan 00:14:33.089 --> 00:14:34.670 align:start position:0% plan well<00:14:33.420> they<00:14:33.510> might<00:14:33.660> want<00:14:33.839> to<00:14:33.899> do<00:14:34.019> next<00:14:34.470> what 00:14:34.670 --> 00:14:34.680 align:start position:0% well they might want to do next what 00:14:34.680 --> 00:14:36.530 align:start position:0% well they might want to do next what about<00:14:34.769> scrubbing<00:14:35.250> off<00:14:35.790> to<00:14:36.000> completes<00:14:36.300> on<00:14:36.449> the 00:14:36.530 --> 00:14:36.540 align:start position:0% about scrubbing off to completes on the 00:14:36.540 --> 00:14:38.660 align:start position:0% about scrubbing off to completes on the tasks<00:14:37.019> of<00:14:37.230> course<00:14:37.800> and<00:14:38.040> wait<00:14:38.250> and<00:14:38.399> watch<00:14:38.490> the 00:14:38.660 --> 00:14:38.670 align:start position:0% tasks of course and wait and watch the 00:14:38.670 --> 00:14:40.730 align:start position:0% tasks of course and wait and watch the transaction<00:14:39.180> very<00:14:39.600> the<00:14:40.110> most<00:14:40.260> important 00:14:40.730 --> 00:14:40.740 align:start position:0% transaction very the most important 00:14:40.740 --> 00:14:41.900 align:start position:0% transaction very the most important thing<00:14:40.860> we<00:14:40.949> want<00:14:41.070> to<00:14:41.100> do<00:14:41.250> is<00:14:41.550> give<00:14:41.760> us<00:14:41.880> a 00:14:41.900 --> 00:14:41.910 align:start position:0% thing we want to do is give us a 00:14:41.910 --> 00:14:45.350 align:start position:0% thing we want to do is give us a ballpark<00:14:42.240> figure<00:14:42.630> at<00:14:42.870> least<00:14:42.899> so<00:14:44.300> instead<00:14:45.300> of 00:14:45.350 --> 00:14:45.360 align:start position:0% ballpark figure at least so instead of 00:14:45.360 --> 00:14:49.960 align:start position:0% ballpark figure at least so instead of just<00:14:45.570> a<00:14:46.250> static<00:14:47.250> message<00:14:47.610> or<00:14:47.880> a<00:14:47.910> spinner<00:14:48.649> as<00:14:49.649> we 00:14:49.960 --> 00:14:49.970 align:start position:0% just a static message or a spinner as we 00:14:49.970 --> 00:14:53.120 align:start position:0% just a static message or a spinner as we we<00:14:50.970> heard<00:14:51.149> the<00:14:51.329> some<00:14:51.480> users<00:14:51.750> felt<00:14:52.070> or<00:14:53.070> thought 00:14:53.120 --> 00:14:53.130 align:start position:0% we heard the some users felt or thought 00:14:53.130 --> 00:14:54.980 align:start position:0% we heard the some users felt or thought them<00:14:53.579> and<00:14:53.790> their<00:14:53.910> transaction<00:14:54.390> may<00:14:54.600> be<00:14:54.660> timed 00:14:54.980 --> 00:14:54.990 align:start position:0% them and their transaction may be timed 00:14:54.990 --> 00:14:57.769 align:start position:0% them and their transaction may be timed out<00:14:55.370> obviously<00:14:56.370> result<00:14:56.550> in<00:14:56.910> the<00:14:57.329> user<00:14:57.510> tries 00:14:57.769 --> 00:14:57.779 align:start position:0% out obviously result in the user tries 00:14:57.779 --> 00:14:59.060 align:start position:0% out obviously result in the user tries to<00:14:58.019> initiate<00:14:58.470> that 00:14:59.060 --> 00:14:59.070 align:start position:0% to initiate that 00:14:59.070 --> 00:15:02.329 align:start position:0% to initiate that which<00:14:59.910> else<00:15:00.779> about<00:15:01.050> that<00:15:01.199> state<00:15:01.470> fountain 00:15:02.329 --> 00:15:02.339 align:start position:0% which else about that state fountain 00:15:02.339 --> 00:15:06.259 align:start position:0% which else about that state fountain that<00:15:02.910> will<00:15:03.649> transactions<00:15:04.649> interest<00:15:05.060> or<00:15:06.060> their 00:15:06.259 --> 00:15:06.269 align:start position:0% that will transactions interest or their 00:15:06.269 --> 00:15:10.160 align:start position:0% that will transactions interest or their own<00:15:07.639> lesson<00:15:08.639> for<00:15:08.850> is<00:15:09.449> to<00:15:09.570> provide<00:15:09.870> just<00:15:10.110> enough 00:15:10.160 --> 00:15:10.170 align:start position:0% own lesson for is to provide just enough 00:15:10.170 --> 00:15:12.980 align:start position:0% own lesson for is to provide just enough feedback<00:15:11.329> and<00:15:12.329> I<00:15:12.389> think<00:15:12.600> that<00:15:12.720> the<00:15:12.839> message 00:15:12.980 --> 00:15:12.990 align:start position:0% feedback and I think that the message 00:15:12.990 --> 00:15:14.660 align:start position:0% feedback and I think that the message here<00:15:13.410> mainly<00:15:13.589> it's<00:15:13.889> just<00:15:13.980> because<00:15:14.430> you<00:15:14.519> can 00:15:14.660 --> 00:15:14.670 align:start position:0% here mainly it's just because you can 00:15:14.670 --> 00:15:15.920 align:start position:0% here mainly it's just because you can get<00:15:14.820> that<00:15:14.940> information<00:15:15.089> from<00:15:15.540> the<00:15:15.720> blockchain 00:15:15.920 --> 00:15:15.930 align:start position:0% get that information from the blockchain 00:15:15.930 --> 00:15:18.199 align:start position:0% get that information from the blockchain because<00:15:16.589> you<00:15:16.680> can<00:15:16.860> call<00:15:17.339> and<00:15:17.550> find<00:15:17.730> out<00:15:17.910> in<00:15:18.149> the 00:15:18.199 --> 00:15:18.209 align:start position:0% because you can call and find out in the 00:15:18.209 --> 00:15:20.360 align:start position:0% because you can call and find out in the transactions<00:15:18.779> in<00:15:19.230> the<00:15:19.440> menthol<00:15:19.829> that's<00:15:20.160> being 00:15:20.360 --> 00:15:20.370 align:start position:0% transactions in the menthol that's being 00:15:20.370 --> 00:15:22.220 align:start position:0% transactions in the menthol that's being mined<00:15:20.639> doesn't<00:15:21.600> mean<00:15:21.690> the<00:15:21.779> user<00:15:21.930> wants<00:15:22.199> to 00:15:22.220 --> 00:15:22.230 align:start position:0% mined doesn't mean the user wants to 00:15:22.230 --> 00:15:24.319 align:start position:0% mined doesn't mean the user wants to know<00:15:22.410> that<00:15:22.620> or<00:15:22.860> but<00:15:23.130> it<00:15:23.250> doesn't<00:15:23.579> mean<00:15:23.880> it 00:15:24.319 --> 00:15:24.329 align:start position:0% know that or but it doesn't mean it 00:15:24.329 --> 00:15:27.920 align:start position:0% know that or but it doesn't mean it doesn't<00:15:24.420> know<00:15:24.779> that<00:15:24.990> in<00:15:25.529> that<00:15:25.589> way<00:15:26.100> so<00:15:26.750> if<00:15:27.750> we 00:15:27.920 --> 00:15:27.930 align:start position:0% doesn't know that in that way so if we 00:15:27.930 --> 00:15:29.900 align:start position:0% doesn't know that in that way so if we like<00:15:28.110> them<00:15:28.259> this<00:15:28.410> experience<00:15:28.589> that<00:15:29.430> we<00:15:29.550> demoed 00:15:29.900 --> 00:15:29.910 align:start position:0% like them this experience that we demoed 00:15:29.910 --> 00:15:33.430 align:start position:0% like them this experience that we demoed so<00:15:30.569> you<00:15:30.630> might<00:15:31.110> if<00:15:31.410> you<00:15:31.500> touch<00:15:31.980> this<00:15:32.190> baby<00:15:32.459> on 00:15:33.430 --> 00:15:33.440 align:start position:0% so you might if you touch this baby on 00:15:33.440 --> 00:15:36.290 align:start position:0% so you might if you touch this baby on Amazon<00:15:34.440> with<00:15:34.529> something<00:15:34.889> you<00:15:35.579> plan<00:15:35.759> to<00:15:35.790> say<00:15:36.089> it 00:15:36.290 --> 00:15:36.300 align:start position:0% Amazon with something you plan to say it 00:15:36.300 --> 00:15:38.559 align:start position:0% Amazon with something you plan to say it gets<00:15:36.449> downloaded<00:15:36.630> from<00:15:37.139> the<00:15:37.380> cloud<00:15:37.589> into<00:15:38.130> your 00:15:38.559 --> 00:15:38.569 align:start position:0% gets downloaded from the cloud into your 00:15:38.569 --> 00:15:41.059 align:start position:0% gets downloaded from the cloud into your actual<00:15:39.569> device<00:15:39.959> now<00:15:40.680> you<00:15:40.769> don't<00:15:40.949> get<00:15:41.009> a 00:15:41.059 --> 00:15:41.069 align:start position:0% actual device now you don't get a 00:15:41.069 --> 00:15:43.129 align:start position:0% actual device now you don't get a play-by-play<00:15:41.459> of<00:15:42.060> exactly<00:15:42.690> where<00:15:43.019> that 00:15:43.129 --> 00:15:43.139 align:start position:0% play-by-play of exactly where that 00:15:43.139 --> 00:15:45.680 align:start position:0% play-by-play of exactly where that content<00:15:43.529> is<00:15:43.680> in<00:15:44.009> the<00:15:44.819> journey<00:15:45.089> that<00:15:45.389> it<00:15:45.480> takes 00:15:45.680 --> 00:15:45.690 align:start position:0% content is in the journey that it takes 00:15:45.690 --> 00:15:48.499 align:start position:0% content is in the journey that it takes down<00:15:45.959> to<00:15:46.110> your<00:15:46.230> price<00:15:46.850> and<00:15:47.850> that's<00:15:48.149> because 00:15:48.499 --> 00:15:48.509 align:start position:0% down to your price and that's because 00:15:48.509 --> 00:15:50.449 align:start position:0% down to your price and that's because the<00:15:48.810> user<00:15:48.990> just<00:15:49.230> wants<00:15:49.440> to<00:15:49.500> know<00:15:49.589> okay<00:15:50.160> how's 00:15:50.449 --> 00:15:50.459 align:start position:0% the user just wants to know okay how's 00:15:50.459 --> 00:15:52.999 align:start position:0% the user just wants to know okay how's that<00:15:50.490> process<00:15:51.300> started<00:15:51.779> is<00:15:52.350> it<00:15:52.560> happening<00:15:52.709> as 00:15:52.999 --> 00:15:53.009 align:start position:0% that process started is it happening as 00:15:53.009 --> 00:15:54.740 align:start position:0% that process started is it happening as expected<00:15:53.370> and<00:15:53.940> when<00:15:54.480> it's<00:15:54.600> finished 00:15:54.740 --> 00:15:54.750 align:start position:0% expected and when it's finished 00:15:54.750 --> 00:15:57.530 align:start position:0% expected and when it's finished essentially<00:15:55.790> and<00:15:56.790> we<00:15:56.910> found<00:15:57.149> that<00:15:57.300> a<00:15:57.329> lot<00:15:57.509> of 00:15:57.530 --> 00:15:57.540 align:start position:0% essentially and we found that a lot of 00:15:57.540 --> 00:15:59.689 align:start position:0% essentially and we found that a lot of users<00:15:57.750> that<00:15:58.079> we<00:15:58.230> sort<00:15:58.470> for<00:15:59.190> this<00:15:59.310> in<00:15:59.430> front<00:15:59.610> of 00:15:59.689 --> 00:15:59.699 align:start position:0% users that we sort for this in front of 00:15:59.699 --> 00:16:01.430 align:start position:0% users that we sort for this in front of you<00:16:00.000> know<00:16:00.089> didn't<00:16:00.449> support<00:16:00.750> of<00:16:00.930> transactions 00:16:01.430 --> 00:16:01.440 align:start position:0% you know didn't support of transactions 00:16:01.440 --> 00:16:03.110 align:start position:0% you know didn't support of transactions go<00:16:01.589> throw<00:16:01.829> away<00:16:02.069> so<00:16:02.130> it's<00:16:02.399> kind<00:16:02.579> of<00:16:02.670> redundant 00:16:03.110 --> 00:16:03.120 align:start position:0% go throw away so it's kind of redundant 00:16:03.120 --> 00:16:05.870 align:start position:0% go throw away so it's kind of redundant me<00:16:03.209> to<00:16:03.329> waste<00:16:03.480> time<00:16:03.920> you<00:16:04.920> know<00:16:05.010> crafting<00:16:05.699> those 00:16:05.870 --> 00:16:05.880 align:start position:0% me to waste time you know crafting those 00:16:05.880 --> 00:16:07.460 align:start position:0% me to waste time you know crafting those messages<00:16:06.240> about<00:16:06.600> when<00:16:06.839> the<00:16:06.959> transaction 00:16:07.460 --> 00:16:07.470 align:start position:0% messages about when the transaction 00:16:07.470 --> 00:16:13.430 align:start position:0% messages about when the transaction event<00:16:08.540> electro<00:16:11.000> finally<00:16:12.000> and<00:16:12.350> design<00:16:13.350> for 00:16:13.430 --> 00:16:13.440 align:start position:0% event electro finally and design for 00:16:13.440 --> 00:16:15.110 align:start position:0% event electro finally and design for next<00:16:13.740> step<00:16:13.920> so<00:16:14.130> we<00:16:14.220> talked<00:16:14.399> about<00:16:14.519> it<00:16:14.699> where<00:16:14.880> to 00:16:15.110 --> 00:16:15.120 align:start position:0% next step so we talked about it where to 00:16:15.120 --> 00:16:18.530 align:start position:0% next step so we talked about it where to about<00:16:15.660> post<00:16:16.470> purchase<00:16:16.680> experience<00:16:17.540> that's 00:16:18.530 --> 00:16:18.540 align:start position:0% about post purchase experience that's 00:16:18.540 --> 00:16:22.040 align:start position:0% about post purchase experience that's not<00:16:18.839> as<00:16:19.019> applicable<00:16:19.829> in<00:16:20.449> very<00:16:21.449> necessarily 00:16:22.040 --> 00:16:22.050 align:start position:0% not as applicable in very necessarily 00:16:22.050 --> 00:16:25.100 align:start position:0% not as applicable in very necessarily where<00:16:22.290> we<00:16:22.410> have<00:16:22.970> less 00:16:25.100 --> 00:16:25.110 align:start position:0% where we have less 00:16:25.110 --> 00:16:28.790 align:start position:0% where we have less channel<00:16:25.790> 6's<00:16:26.850> automation<00:16:27.690> emails<00:16:27.959> so<00:16:28.560> I<00:16:28.620> think 00:16:28.790 --> 00:16:28.800 align:start position:0% channel 6's automation emails so I think 00:16:28.800 --> 00:16:31.519 align:start position:0% channel 6's automation emails so I think the<00:16:29.130> transaction<00:16:29.820> the<00:16:30.600> transaction<00:16:30.810> success 00:16:31.519 --> 00:16:31.529 align:start position:0% the transaction the transaction success 00:16:31.529 --> 00:16:33.800 align:start position:0% the transaction the transaction success message<00:16:31.860> is<00:16:32.339> like<00:16:32.519> a<00:16:32.579> really<00:16:32.850> good 00:16:33.800 --> 00:16:33.810 align:start position:0% message is like a really good 00:16:33.810 --> 00:16:38.920 align:start position:0% message is like a really good opportunity<00:16:34.050> to<00:16:35.540> do<00:16:36.540> that<00:16:36.920> and<00:16:37.920> in<00:16:38.130> order<00:16:38.250> to 00:16:38.920 --> 00:16:38.930 align:start position:0% opportunity to do that and in order to 00:16:38.930 --> 00:16:41.240 align:start position:0% opportunity to do that and in order to design<00:16:39.930> successful<00:16:40.620> device<00:16:40.890> versus 00:16:41.240 --> 00:16:41.250 align:start position:0% design successful device versus 00:16:41.250 --> 00:16:42.949 align:start position:0% design successful device versus experience<00:16:41.610> you<00:16:41.820> really<00:16:41.850> need<00:16:42.120> to<00:16:42.209> know<00:16:42.240> the 00:16:42.949 --> 00:16:42.959 align:start position:0% experience you really need to know the 00:16:42.959 --> 00:16:46.100 align:start position:0% experience you really need to know the actual<00:16:43.529> end<00:16:43.680> of<00:16:43.950> the<00:16:44.250> baby<00:16:44.820> that<00:16:45.149> has<00:16:45.269> service 00:16:46.100 --> 00:16:46.110 align:start position:0% actual end of the baby that has service 00:16:46.110 --> 00:16:47.930 align:start position:0% actual end of the baby that has service our<00:16:46.260> point<00:16:46.500> our<00:16:46.560> demo<00:16:46.860> the<00:16:47.339> end<00:16:47.490> goal<00:16:47.670> wasn't 00:16:47.930 --> 00:16:47.940 align:start position:0% our point our demo the end goal wasn't 00:16:47.940 --> 00:16:49.850 align:start position:0% our point our demo the end goal wasn't to<00:16:48.120> just<00:16:48.329> complete<00:16:48.600> that<00:16:48.630> transaction<00:16:48.959> and 00:16:49.850 --> 00:16:49.860 align:start position:0% to just complete that transaction and 00:16:49.860 --> 00:16:52.009 align:start position:0% to just complete that transaction and always<00:16:50.279> to<00:16:50.399> go<00:16:50.550> to<00:16:50.610> the<00:16:50.730> conference<00:16:50.970> so<00:16:51.810> this 00:16:52.009 --> 00:16:52.019 align:start position:0% always to go to the conference so this 00:16:52.019 --> 00:16:53.540 align:start position:0% always to go to the conference so this message<00:16:52.200> is<00:16:52.470> crafted<00:16:52.980> in<00:16:53.070> a<00:16:53.160> way<00:16:53.279> that 00:16:53.540 --> 00:16:53.550 align:start position:0% message is crafted in a way that 00:16:53.550 --> 00:16:55.340 align:start position:0% message is crafted in a way that explains<00:16:54.269> these<00:16:54.540> that<00:16:54.779> what<00:16:54.899> they<00:16:54.990> need<00:16:55.110> to<00:16:55.200> do 00:16:55.340 --> 00:16:55.350 align:start position:0% explains these that what they need to do 00:16:55.350 --> 00:16:57.980 align:start position:0% explains these that what they need to do once<00:16:55.560> the<00:16:55.649> tickets<00:16:55.980> man<00:16:56.190> I<00:16:56.339> met<00:16:56.459> no<00:16:56.579> wallet 00:16:57.980 --> 00:16:57.990 align:start position:0% once the tickets man I met no wallet 00:16:57.990 --> 00:17:00.139 align:start position:0% once the tickets man I met no wallet it<00:16:58.589> also<00:16:58.740> anticipates<00:16:59.430> that<00:16:59.550> the<00:16:59.730> user<00:16:59.910> may 00:17:00.139 --> 00:17:00.149 align:start position:0% it also anticipates that the user may 00:17:00.149 --> 00:17:01.610 align:start position:0% it also anticipates that the user may have<00:17:00.180> been<00:17:00.450> blind<00:17:00.690> to<00:17:00.870> get<00:17:01.110> on<00:17:01.260> the<00:17:01.350> heart<00:17:01.529> of 00:17:01.610 --> 00:17:01.620 align:start position:0% have been blind to get on the heart of 00:17:01.620 --> 00:17:03.139 align:start position:0% have been blind to get on the heart of my<00:17:01.680> friend<00:17:01.920> and<00:17:02.010> colleague<00:17:02.100> so<00:17:02.640> again<00:17:02.910> you<00:17:03.000> get 00:17:03.139 --> 00:17:03.149 align:start position:0% my friend and colleague so again you get 00:17:03.149 --> 00:17:06.199 align:start position:0% my friend and colleague so again you get this<00:17:03.300> spring<00:17:04.079> water<00:17:04.730> at<00:17:05.730> the<00:17:05.790> bottom<00:17:05.910> here 00:17:06.199 --> 00:17:06.209 align:start position:0% this spring water at the bottom here 00:17:06.209 --> 00:17:08.809 align:start position:0% this spring water at the bottom here which<00:17:06.449> is<00:17:06.569> like<00:17:06.750> if<00:17:07.199> Joseph<00:17:07.589> in<00:17:07.709> it<00:17:07.799> so<00:17:08.010> you're 00:17:08.809 --> 00:17:08.819 align:start position:0% which is like if Joseph in it so you're 00:17:08.819 --> 00:17:10.429 align:start position:0% which is like if Joseph in it so you're anticipating<00:17:09.209> what<00:17:09.750> the<00:17:09.780> user<00:17:10.020> might<00:17:10.110> want<00:17:10.410> to 00:17:10.429 --> 00:17:10.439 align:start position:0% anticipating what the user might want to 00:17:10.439 --> 00:17:11.659 align:start position:0% anticipating what the user might want to do<00:17:10.589> next<00:17:10.620> and<00:17:10.919> helping<00:17:11.250> them<00:17:11.400> achieve<00:17:11.490> that 00:17:11.659 --> 00:17:11.669 align:start position:0% do next and helping them achieve that 00:17:11.669 --> 00:17:13.490 align:start position:0% do next and helping them achieve that problem<00:17:12.270> again<00:17:12.569> assuming<00:17:13.199> they<00:17:13.290> have<00:17:13.470> a 00:17:13.490 --> 00:17:13.500 align:start position:0% problem again assuming they have a 00:17:13.500 --> 00:17:14.780 align:start position:0% problem again assuming they have a knowledge<00:17:13.860> to<00:17:14.040> be<00:17:14.100> able<00:17:14.160> to<00:17:14.339> go<00:17:14.520> into<00:17:14.640> the 00:17:14.780 --> 00:17:14.790 align:start position:0% knowledge to be able to go into the 00:17:14.790 --> 00:17:17.270 align:start position:0% knowledge to be able to go into the wallet<00:17:14.970> semi<00:17:15.900> entity<00:17:16.319> to<00:17:16.770> a<00:17:16.799> friend<00:17:17.069> or 00:17:17.270 --> 00:17:17.280 align:start position:0% wallet semi entity to a friend or 00:17:17.280 --> 00:17:19.939 align:start position:0% wallet semi entity to a friend or colleague<00:17:17.669> I<00:17:18.439> think<00:17:19.439> this<00:17:19.530> is<00:17:19.620> a<00:17:19.650> really<00:17:19.890> good 00:17:19.939 --> 00:17:19.949 align:start position:0% colleague I think this is a really good 00:17:19.949 --> 00:17:22.100 align:start position:0% colleague I think this is a really good opportunity<00:17:20.160> to<00:17:20.579> use<00:17:20.880> more<00:17:21.390> be<00:17:21.540> persistent 00:17:22.100 --> 00:17:22.110 align:start position:0% opportunity to use more be persistent 00:17:22.110 --> 00:17:23.990 align:start position:0% opportunity to use more be persistent mobilizing<00:17:22.709> a<00:17:22.890> lot<00:17:23.130> of<00:17:23.189> taps<00:17:23.370> are<00:17:23.579> there<00:17:23.760> help 00:17:23.990 --> 00:17:24.000 align:start position:0% mobilizing a lot of taps are there help 00:17:24.000 --> 00:17:26.630 align:start position:0% mobilizing a lot of taps are there help interoperability<00:17:24.809> in<00:17:25.110> mind<00:17:25.380> so<00:17:26.309> you<00:17:26.370> can<00:17:26.549> for 00:17:26.630 --> 00:17:26.640 align:start position:0% interoperability in mind so you can for 00:17:26.640 --> 00:17:28.789 align:start position:0% interoperability in mind so you can for example<00:17:26.669> if<00:17:27.000> you<00:17:27.089> like<00:17:27.209> that<00:17:27.360> about<00:17:27.929> you<00:17:28.110> user 00:17:28.789 --> 00:17:28.799 align:start position:0% example if you like that about you user 00:17:28.799 --> 00:17:31.010 align:start position:0% example if you like that about you user to<00:17:28.980> generate<00:17:29.309> die<00:17:29.490> for<00:17:29.760> example<00:17:30.240> that's<00:17:30.870> not 00:17:31.010 --> 00:17:31.020 align:start position:0% to generate die for example that's not 00:17:31.020 --> 00:17:32.539 align:start position:0% to generate die for example that's not just<00:17:31.200> how<00:17:31.290> the<00:17:31.350> message<00:17:31.740> is<00:17:31.830> playing<00:17:32.130> is<00:17:32.250> great 00:17:32.539 --> 00:17:32.549 align:start position:0% just how the message is playing is great 00:17:32.549 --> 00:17:34.820 align:start position:0% just how the message is playing is great but<00:17:32.880> could<00:17:33.000> die<00:17:33.179> why<00:17:33.809> don't<00:17:33.990> we<00:17:34.049> say<00:17:34.230> great 00:17:34.820 --> 00:17:34.830 align:start position:0% but could die why don't we say great 00:17:34.830 --> 00:17:36.770 align:start position:0% but could die why don't we say great about<00:17:35.040> the<00:17:35.190> guy<00:17:35.340> got<00:17:35.940> an<00:17:36.150> interest<00:17:36.419> on<00:17:36.600> that 00:17:36.770 --> 00:17:36.780 align:start position:0% about the guy got an interest on that 00:17:36.780 --> 00:17:38.810 align:start position:0% about the guy got an interest on that compound<00:17:37.290> there's<00:17:37.860> a<00:17:37.890> real<00:17:38.070> option<00:17:38.340> the<00:17:38.610> seeds 00:17:38.810 --> 00:17:38.820 align:start position:0% compound there's a real option the seeds 00:17:38.820 --> 00:17:41.930 align:start position:0% compound there's a real option the seeds or<00:17:39.770> cross<00:17:40.770> pollinating<00:17:41.340> s<00:17:41.490> users<00:17:41.760> between 00:17:41.930 --> 00:17:41.940 align:start position:0% or cross pollinating s users between 00:17:41.940 --> 00:17:43.870 align:start position:0% or cross pollinating s users between adapts 00:17:43.870 --> 00:17:43.880 align:start position:0% adapts 00:17:43.880 --> 00:17:45.940 align:start position:0% adapts roll<00:17:44.059> what<00:17:44.720> can<00:17:44.870> cause<00:17:45.080> a<00:17:45.140> similar<00:17:45.679> vision 00:17:45.940 --> 00:17:45.950 align:start position:0% roll what can cause a similar vision 00:17:45.950 --> 00:17:49.659 align:start position:0% roll what can cause a similar vision there<00:17:47.020> I'm<00:17:48.020> just<00:17:48.080> gonna<00:17:48.200> hand<00:17:49.190> back<00:17:49.340> over<00:17:49.460> to 00:17:49.659 --> 00:17:49.669 align:start position:0% there I'm just gonna hand back over to 00:17:49.669 --> 00:17:53.799 align:start position:0% there I'm just gonna hand back over to mine<00:17:50.049> just<00:17:51.049> a<00:17:51.169> sinner<00:17:51.559> I<00:17:52.539> can't<00:17:53.539> believe<00:17:53.720> you 00:17:53.799 --> 00:17:53.809 align:start position:0% mine just a sinner I can't believe you 00:17:53.809 --> 00:17:59.440 align:start position:0% mine just a sinner I can't believe you saw<00:17:53.990> my<00:17:54.110> desktop<00:17:54.500> I'm<00:17:54.799> so<00:17:55.190> embarrassed<00:17:58.059> so<00:17:59.059> a 00:17:59.440 --> 00:17:59.450 align:start position:0% saw my desktop I'm so embarrassed so a 00:17:59.450 --> 00:18:02.049 align:start position:0% saw my desktop I'm so embarrassed so a lot<00:17:59.929> of<00:17:59.960> it<00:18:00.049> doesn't<00:18:00.320> sound<00:18:00.620> too<00:18:00.980> novel<00:18:01.789> might 00:18:02.049 --> 00:18:02.059 align:start position:0% lot of it doesn't sound too novel might 00:18:02.059 --> 00:18:03.880 align:start position:0% lot of it doesn't sound too novel might all<00:18:02.240> sound<00:18:02.419> quite<00:18:02.780> familiar<00:18:02.929> and<00:18:03.620> I<00:18:03.710> think 00:18:03.880 --> 00:18:03.890 align:start position:0% all sound quite familiar and I think 00:18:03.890 --> 00:18:04.930 align:start position:0% all sound quite familiar and I think that's<00:18:04.039> the<00:18:04.160> case<00:18:04.309> we<00:18:04.669> don't<00:18:04.850> necessarily 00:18:04.930 --> 00:18:04.940 align:start position:0% that's the case we don't necessarily 00:18:04.940 --> 00:18:07.750 align:start position:0% that's the case we don't necessarily need<00:18:05.330> to<00:18:05.390> be<00:18:05.510> reinventing<00:18:06.200> the<00:18:06.950> design<00:18:07.400> of<00:18:07.669> the 00:18:07.750 --> 00:18:07.760 align:start position:0% need to be reinventing the design of the 00:18:07.760 --> 00:18:09.520 align:start position:0% need to be reinventing the design of the new<00:18:07.880> x<00:18:08.030> wheel<00:18:08.240> for<00:18:08.600> web<00:18:08.720> theory<00:18:08.990> I<00:18:09.230> think<00:18:09.350> we 00:18:09.520 --> 00:18:09.530 align:start position:0% new x wheel for web theory I think we 00:18:09.530 --> 00:18:11.200 align:start position:0% new x wheel for web theory I think we might<00:18:09.679> just<00:18:09.799> need<00:18:09.890> a<00:18:10.010> bit<00:18:10.220> of<00:18:10.250> a<00:18:10.370> collective 00:18:11.200 --> 00:18:11.210 align:start position:0% might just need a bit of a collective 00:18:11.210 --> 00:18:12.669 align:start position:0% might just need a bit of a collective nudge<00:18:11.480> to<00:18:11.809> sort<00:18:12.020> remember<00:18:12.380> some<00:18:12.559> of<00:18:12.620> the 00:18:12.669 --> 00:18:12.679 align:start position:0% nudge to sort remember some of the 00:18:12.679 --> 00:18:15.990 align:start position:0% nudge to sort remember some of the lessons<00:18:12.890> we<00:18:13.220> already<00:18:13.549> familiar<00:18:13.880> with<00:18:14.000> privacy 00:18:15.990 --> 00:18:16.000 align:start position:0% lessons we already familiar with privacy 00:18:16.000 --> 00:18:20.770 align:start position:0% lessons we already familiar with privacy so<00:18:18.280> I'm<00:18:19.280> just<00:18:19.400> going<00:18:19.549> to<00:18:19.580> hop<00:18:19.789> over<00:18:19.970> to<00:18:20.270> -<00:18:20.480> talk 00:18:20.770 --> 00:18:20.780 align:start position:0% so I'm just going to hop over to - talk 00:18:20.780 --> 00:18:22.210 align:start position:0% so I'm just going to hop over to - talk a<00:18:20.840> bit<00:18:21.049> about<00:18:21.080> what's<00:18:21.799> and<00:18:22.039> more 00:18:22.210 --> 00:18:22.220 align:start position:0% a bit about what's and more 00:18:22.220 --> 00:18:23.860 align:start position:0% a bit about what's and more technological<00:18:22.880> advancements<00:18:23.450> in<00:18:23.600> space 00:18:23.860 --> 00:18:23.870 align:start position:0% technological advancements in space 00:18:23.870 --> 00:18:26.680 align:start position:0% technological advancements in space company<00:18:24.289> might<00:18:25.220> mean<00:18:25.549> for<00:18:25.690> transaction 00:18:26.680 --> 00:18:26.690 align:start position:0% company might mean for transaction 00:18:26.690 --> 00:18:30.549 align:start position:0% company might mean for transaction notice<00:18:27.640> so<00:18:28.640> we<00:18:29.210> went<00:18:29.390> through<00:18:29.559> traditional 00:18:30.549 --> 00:18:30.559 align:start position:0% notice so we went through traditional 00:18:30.559 --> 00:18:33.070 align:start position:0% notice so we went through traditional transactions<00:18:31.250> and<00:18:31.669> all<00:18:32.630> that<00:18:32.809> being<00:18:32.990> said 00:18:33.070 --> 00:18:33.080 align:start position:0% transactions and all that being said 00:18:33.080 --> 00:18:35.919 align:start position:0% transactions and all that being said like<00:18:33.500> it's<00:18:33.679> great<00:18:33.890> that<00:18:34.100> we<00:18:34.340> find<00:18:35.330> energy<00:18:35.750> into 00:18:35.919 --> 00:18:35.929 align:start position:0% like it's great that we find energy into 00:18:35.929 --> 00:18:38.020 align:start position:0% like it's great that we find energy into figuring<00:18:36.110> this<00:18:36.350> stuff<00:18:36.409> out<00:18:36.740> but<00:18:37.010> honestly<00:18:37.850> if 00:18:38.020 --> 00:18:38.030 align:start position:0% figuring this stuff out but honestly if 00:18:38.030 --> 00:18:39.820 align:start position:0% figuring this stuff out but honestly if you<00:18:38.150> can<00:18:38.330> get<00:18:38.480> away<00:18:38.600> with<00:18:38.929> not<00:18:38.960> dealing<00:18:39.710> with 00:18:39.820 --> 00:18:39.830 align:start position:0% you can get away with not dealing with 00:18:39.830 --> 00:18:42.159 align:start position:0% you can get away with not dealing with these<00:18:40.010> problems<00:18:40.309> that's<00:18:41.030> the<00:18:41.270> best<00:18:41.510> design 00:18:42.159 --> 00:18:42.169 align:start position:0% these problems that's the best design 00:18:42.169 --> 00:18:44.500 align:start position:0% these problems that's the best design solution<00:18:42.770> so<00:18:43.010> if<00:18:43.250> you<00:18:43.400> can<00:18:43.549> abstract<00:18:43.909> gas<00:18:44.179> away 00:18:44.500 --> 00:18:44.510 align:start position:0% solution so if you can abstract gas away 00:18:44.510 --> 00:18:45.990 align:start position:0% solution so if you can abstract gas away if<00:18:44.570> you<00:18:44.780> can<00:18:44.900> get<00:18:45.049> rid<00:18:45.169> of<00:18:45.200> transaction<00:18:45.770> fees 00:18:45.990 --> 00:18:46.000 align:start position:0% if you can get rid of transaction fees 00:18:46.000 --> 00:18:48.820 align:start position:0% if you can get rid of transaction fees if<00:18:47.000> you<00:18:47.210> can<00:18:47.360> make<00:18:47.480> transaction<00:18:48.049> ten<00:18:48.230> faster 00:18:48.820 --> 00:18:48.830 align:start position:0% if you can make transaction ten faster 00:18:48.830 --> 00:18:50.430 align:start position:0% if you can make transaction ten faster and<00:18:49.010> that's<00:18:49.309> within<00:18:49.909> your<00:18:50.030> capabilities 00:18:50.430 --> 00:18:50.440 align:start position:0% and that's within your capabilities 00:18:50.440 --> 00:18:51.760 align:start position:0% and that's within your capabilities absolutely<00:18:51.440> do<00:18:51.559> that 00:18:51.760 --> 00:18:51.770 align:start position:0% absolutely do that 00:18:51.770 --> 00:18:55.060 align:start position:0% absolutely do that so<00:18:52.460> meta<00:18:52.820> transactions<00:18:53.510> is<00:18:54.230> one<00:18:54.559> example 00:18:55.060 --> 00:18:55.070 align:start position:0% so meta transactions is one example 00:18:55.070 --> 00:18:57.250 align:start position:0% so meta transactions is one example where<00:18:55.429> you<00:18:55.669> can<00:18:55.880> just<00:18:56.120> pay<00:18:56.270> the<00:18:56.600> gas<00:18:56.720> on<00:18:57.020> behalf 00:18:57.250 --> 00:18:57.260 align:start position:0% where you can just pay the gas on behalf 00:18:57.260 --> 00:19:00.100 align:start position:0% where you can just pay the gas on behalf of<00:18:57.440> your<00:18:57.830> users<00:18:58.570> something<00:18:59.570> like<00:18:59.809> the<00:18:59.900> gas 00:19:00.100 --> 00:19:00.110 align:start position:0% of your users something like the gas 00:19:00.110 --> 00:19:03.310 align:start position:0% of your users something like the gas station<00:19:00.559> network<00:19:00.919> or<00:19:01.340> the<00:19:02.179> FATA<00:19:02.690> transaction 00:19:03.310 --> 00:19:03.320 align:start position:0% station network or the FATA transaction 00:19:03.320 --> 00:19:06.250 align:start position:0% station network or the FATA transaction tree<00:19:03.440> light<00:19:03.650> that<00:19:04.100> lets<00:19:04.280> you<00:19:04.630> pay<00:19:05.630> for<00:19:05.960> users 00:19:06.250 --> 00:19:06.260 align:start position:0% tree light that lets you pay for users 00:19:06.260 --> 00:19:08.470 align:start position:0% tree light that lets you pay for users gas<00:19:06.500> would<00:19:06.830> get<00:19:07.340> rid<00:19:07.490> of<00:19:07.549> one<00:19:07.820> of<00:19:07.850> the<00:19:07.970> problems 00:19:08.470 --> 00:19:08.480 align:start position:0% gas would get rid of one of the problems 00:19:08.480 --> 00:19:11.200 align:start position:0% gas would get rid of one of the problems of<00:19:08.809> friction<00:19:08.870> points<00:19:09.500> later<00:19:10.429> two<00:19:10.669> solutions 00:19:11.200 --> 00:19:11.210 align:start position:0% of friction points later two solutions 00:19:11.210 --> 00:19:14.260 align:start position:0% of friction points later two solutions was<00:19:11.659> sidechains<00:19:12.380> child<00:19:13.100> plasma<00:19:13.610> chains<00:19:13.940> like 00:19:14.260 --> 00:19:14.270 align:start position:0% was sidechains child plasma chains like 00:19:14.270 --> 00:19:16.680 align:start position:0% was sidechains child plasma chains like bloom<00:19:14.570> and<00:19:14.809> POA<00:19:15.130> third-grade<00:19:16.130> they're<00:19:16.370> fast 00:19:16.680 --> 00:19:16.690 align:start position:0% bloom and POA third-grade they're fast 00:19:16.690 --> 00:19:20.279 align:start position:0% bloom and POA third-grade they're fast they<00:19:17.690> have<00:19:17.960> really<00:19:18.710> really<00:19:18.850> basically<00:19:19.850> free 00:19:20.279 --> 00:19:20.289 align:start position:0% they have really really basically free 00:19:20.289 --> 00:19:23.560 align:start position:0% they have really really basically free transaction<00:19:21.289> fees<00:19:21.610> so<00:19:22.610> again<00:19:22.820> you're<00:19:23.270> not 00:19:23.560 --> 00:19:23.570 align:start position:0% transaction fees so again you're not 00:19:23.570 --> 00:19:25.000 align:start position:0% transaction fees so again you're not having<00:19:23.960> to<00:19:24.049> even<00:19:24.320> deal<00:19:24.470> with<00:19:24.530> the<00:19:24.770> whole 00:19:25.000 --> 00:19:25.010 align:start position:0% having to even deal with the whole 00:19:25.010 --> 00:19:29.440 align:start position:0% having to even deal with the whole transaction<00:19:25.549> issue<00:19:27.280> design<00:19:28.280> with<00:19:28.909> the 00:19:29.440 --> 00:19:29.450 align:start position:0% transaction issue design with the 00:19:29.450 --> 00:19:30.880 align:start position:0% transaction issue design with the developers<00:19:30.020> from<00:19:30.140> the<00:19:30.289> very<00:19:30.440> beginning<00:19:30.590> so 00:19:30.880 --> 00:19:30.890 align:start position:0% developers from the very beginning so 00:19:30.890 --> 00:19:32.260 align:start position:0% developers from the very beginning so when<00:19:31.220> you're<00:19:31.340> not<00:19:31.460> protecting<00:19:31.909> your<00:19:31.970> smart 00:19:32.260 --> 00:19:32.270 align:start position:0% when you're not protecting your smart 00:19:32.270 --> 00:19:34.840 align:start position:0% when you're not protecting your smart contracts<00:19:32.720> use<00:19:32.960> a<00:19:32.990> proxy<00:19:33.320> pattern<00:19:33.770> that<00:19:34.549> lets 00:19:34.840 --> 00:19:34.850 align:start position:0% contracts use a proxy pattern that lets 00:19:34.850 --> 00:19:36.610 align:start position:0% contracts use a proxy pattern that lets you<00:19:34.970> chain<00:19:35.270> will<00:19:35.480> steps<00:19:35.990> together<00:19:36.169> into<00:19:36.590> a 00:19:36.610 --> 00:19:36.620 align:start position:0% you chain will steps together into a 00:19:36.620 --> 00:19:38.820 align:start position:0% you chain will steps together into a single<00:19:36.890> transaction<00:19:37.490> for<00:19:37.850> the<00:19:37.909> end<00:19:38.059> user 00:19:38.820 --> 00:19:38.830 align:start position:0% single transaction for the end user 00:19:38.830 --> 00:19:41.320 align:start position:0% single transaction for the end user there's<00:19:39.830> future<00:19:40.280> things<00:19:40.520> coming<00:19:40.880> state 00:19:41.320 --> 00:19:41.330 align:start position:0% there's future things coming state 00:19:41.330 --> 00:19:43.659 align:start position:0% there's future things coming state channels<00:19:41.809> CK<00:19:42.230> starts<00:19:42.620> that<00:19:42.860> will<00:19:43.100> also<00:19:43.460> let 00:19:43.659 --> 00:19:43.669 align:start position:0% channels CK starts that will also let 00:19:43.669 --> 00:19:44.150 align:start position:0% channels CK starts that will also let you<00:19:43.700> do 00:19:44.150 --> 00:19:44.160 align:start position:0% you do 00:19:44.160 --> 00:19:46.940 align:start position:0% you do obtain<00:19:44.720> if<00:19:45.720> you<00:19:45.930> hang<00:19:46.140> in<00:19:46.320> if<00:19:46.470> you<00:19:46.560> have<00:19:46.770> the 00:19:46.940 --> 00:19:46.950 align:start position:0% obtain if you hang in if you have the 00:19:46.950 --> 00:19:49.160 align:start position:0% obtain if you hang in if you have the ability<00:19:47.310> and<00:19:47.550> the<00:19:47.610> time<00:19:47.880> and<00:19:48.210> then<00:19:48.450> the<00:19:48.900> skill 00:19:49.160 --> 00:19:49.170 align:start position:0% ability and the time and then the skill 00:19:49.170 --> 00:19:50.990 align:start position:0% ability and the time and then the skill to<00:19:49.530> get<00:19:49.860> rid<00:19:50.040> of<00:19:50.070> transactions<00:19:50.940> from 00:19:50.990 --> 00:19:51.000 align:start position:0% to get rid of transactions from 00:19:51.000 --> 00:19:53.300 align:start position:0% to get rid of transactions from happening<00:19:51.600> that's<00:19:52.260> that's<00:19:52.800> the<00:19:52.950> best<00:19:53.070> way<00:19:53.280> to 00:19:53.300 --> 00:19:53.310 align:start position:0% happening that's that's the best way to 00:19:53.310 --> 00:19:57.650 align:start position:0% happening that's that's the best way to deal<00:19:53.550> with<00:19:53.580> transactions<00:19:56.210> but<00:19:57.210> that<00:19:57.360> doesn't 00:19:57.650 --> 00:19:57.660 align:start position:0% deal with transactions but that doesn't 00:19:57.660 --> 00:19:59.270 align:start position:0% deal with transactions but that doesn't necessarily<00:19:57.750> mean<00:19:58.170> lower<00:19:58.530> device<00:19:58.770> bones<00:19:59.070> in 00:19:59.270 --> 00:19:59.280 align:start position:0% necessarily mean lower device bones in 00:19:59.280 --> 00:20:03.680 align:start position:0% necessarily mean lower device bones in the<00:19:59.340> museum<00:20:00.740> so<00:20:01.740> just<00:20:01.920> a<00:20:01.980> recap<00:20:02.600> something<00:20:03.600> the 00:20:03.680 --> 00:20:03.690 align:start position:0% the museum so just a recap something the 00:20:03.690 --> 00:20:05.480 align:start position:0% the museum so just a recap something the overarching<00:20:04.110> heuristics<00:20:04.800> and<00:20:05.040> the<00:20:05.100> sort<00:20:05.310> of 00:20:05.480 --> 00:20:05.490 align:start position:0% overarching heuristics and the sort of 00:20:05.490 --> 00:20:06.980 align:start position:0% overarching heuristics and the sort of foundation<00:20:06.030> behind<00:20:06.450> all<00:20:06.660> these<00:20:06.720> devices 00:20:06.980 --> 00:20:06.990 align:start position:0% foundation behind all these devices 00:20:06.990 --> 00:20:08.240 align:start position:0% foundation behind all these devices still<00:20:07.380> very<00:20:07.590> much 00:20:08.240 --> 00:20:08.250 align:start position:0% still very much 00:20:08.250 --> 00:20:10.160 align:start position:0% still very much it's<00:20:08.580> all<00:20:08.670> very<00:20:08.700> much<00:20:08.880> applies<00:20:09.210> and<00:20:09.870> I<00:20:09.960> still 00:20:10.160 --> 00:20:10.170 align:start position:0% it's all very much applies and I still 00:20:10.170 --> 00:20:12.080 align:start position:0% it's all very much applies and I still always<00:20:10.590> communicate<00:20:11.100> with<00:20:11.280> the<00:20:11.340> context<00:20:11.880> be 00:20:12.080 --> 00:20:12.090 align:start position:0% always communicate with the context be 00:20:12.090 --> 00:20:13.880 align:start position:0% always communicate with the context be specific<00:20:12.600> about<00:20:12.690> what<00:20:12.900> the<00:20:13.020> use<00:20:13.170> of<00:20:13.200> doing<00:20:13.470> the 00:20:13.880 --> 00:20:13.890 align:start position:0% specific about what the use of doing the 00:20:13.890 --> 00:20:15.820 align:start position:0% specific about what the use of doing the tasks<00:20:14.160> that<00:20:14.220> they're<00:20:14.310> trying<00:20:14.550> to<00:20:14.580> achieve 00:20:15.820 --> 00:20:15.830 align:start position:0% tasks that they're trying to achieve 00:20:15.830 --> 00:20:19.490 align:start position:0% tasks that they're trying to achieve plan<00:20:16.830> for<00:20:17.010> errors<00:20:17.810> anticipate<00:20:18.810> errors<00:20:19.110> design 00:20:19.490 --> 00:20:19.500 align:start position:0% plan for errors anticipate errors design 00:20:19.500 --> 00:20:21.650 align:start position:0% plan for errors anticipate errors design error<00:20:19.860> states<00:20:20.250> help<00:20:20.970> users<00:20:21.180> out<00:20:21.330> the<00:20:21.450> jam 00:20:21.650 --> 00:20:21.660 align:start position:0% error states help users out the jam 00:20:21.660 --> 00:20:23.030 align:start position:0% error states help users out the jam don't<00:20:21.990> just<00:20:22.140> tell<00:20:22.320> them<00:20:22.470> this<00:20:22.590> that's 00:20:23.030 --> 00:20:23.040 align:start position:0% don't just tell them this that's 00:20:23.040 --> 00:20:26.990 align:start position:0% don't just tell them this that's happening<00:20:24.410> set<00:20:25.410> the<00:20:25.530> user<00:20:25.620> expectations<00:20:26.550> so 00:20:26.990 --> 00:20:27.000 align:start position:0% happening set the user expectations so 00:20:27.000 --> 00:20:28.190 align:start position:0% happening set the user expectations so always<00:20:27.300> try<00:20:27.570> and<00:20:27.660> keep<00:20:27.780> them<00:20:27.960> in<00:20:28.080> the<00:20:28.170> loop 00:20:28.190 --> 00:20:28.200 align:start position:0% always try and keep them in the loop 00:20:28.200 --> 00:20:30.560 align:start position:0% always try and keep them in the loop make<00:20:28.830> sure<00:20:29.040> that<00:20:29.220> they're<00:20:29.400> aware<00:20:29.550> of<00:20:29.850> any<00:20:30.030> sort 00:20:30.560 --> 00:20:30.570 align:start position:0% make sure that they're aware of any sort 00:20:30.570 --> 00:20:33.140 align:start position:0% make sure that they're aware of any sort of<00:20:30.720> nasty<00:20:31.380> spot<00:20:31.830> potential<00:20:32.220> Melfi<00:20:32.640> surprises 00:20:33.140 --> 00:20:33.150 align:start position:0% of nasty spot potential Melfi surprises 00:20:33.150 --> 00:20:36.620 align:start position:0% of nasty spot potential Melfi surprises such<00:20:33.360> as<00:20:33.510> fees<00:20:33.720> or<00:20:33.960> not<00:20:34.110> wait<00:20:34.260> times<00:20:35.540> but<00:20:36.540> why 00:20:36.620 --> 00:20:36.630 align:start position:0% such as fees or not wait times but why 00:20:36.630 --> 00:20:38.570 align:start position:0% such as fees or not wait times but why just<00:20:36.690> enough<00:20:37.050> information<00:20:37.290> just<00:20:38.220> because<00:20:38.490> you 00:20:38.570 --> 00:20:38.580 align:start position:0% just enough information just because you 00:20:38.580 --> 00:20:40.160 align:start position:0% just enough information just because you can<00:20:38.820> provide<00:20:39.180> the<00:20:39.360> content<00:20:39.780> doesn't<00:20:39.990> mean 00:20:40.160 --> 00:20:40.170 align:start position:0% can provide the content doesn't mean 00:20:40.170 --> 00:20:42.080 align:start position:0% can provide the content doesn't mean that<00:20:40.260> you<00:20:40.380> should<00:20:40.650> try<00:20:41.040> and<00:20:41.130> think<00:20:41.250> about<00:20:41.580> the 00:20:42.080 --> 00:20:42.090 align:start position:0% that you should try and think about the 00:20:42.090 --> 00:20:43.970 align:start position:0% that you should try and think about the actual<00:20:42.570> information<00:20:42.870> user<00:20:43.350> needs<00:20:43.620> at<00:20:43.890> the 00:20:43.970 --> 00:20:43.980 align:start position:0% actual information user needs at the 00:20:43.980 --> 00:20:46.370 align:start position:0% actual information user needs at the time<00:20:44.190> what<00:20:44.670> is<00:20:44.760> a<00:20:44.910> progress<00:20:45.510> through<00:20:45.780> the 00:20:46.370 --> 00:20:46.380 align:start position:0% time what is a progress through the 00:20:46.380 --> 00:20:48.860 align:start position:0% time what is a progress through the general<00:20:46.770> while<00:20:46.950> you're<00:20:47.130> designing<00:20:47.870> and 00:20:48.860 --> 00:20:48.870 align:start position:0% general while you're designing and 00:20:48.870 --> 00:20:50.330 align:start position:0% general while you're designing and remember<00:20:49.200> next<00:20:49.440> steps<00:20:49.650> you<00:20:49.800> know<00:20:50.010> try<00:20:50.250> and 00:20:50.330 --> 00:20:50.340 align:start position:0% remember next steps you know try and 00:20:50.340 --> 00:20:51.920 align:start position:0% remember next steps you know try and avoid<00:20:50.520> dead<00:20:50.790> ends<00:20:50.970> we<00:20:51.240> don't<00:20:51.420> want<00:20:51.600> the<00:20:51.720> user 00:20:51.920 --> 00:20:51.930 align:start position:0% avoid dead ends we don't want the user 00:20:51.930 --> 00:20:54.920 align:start position:0% avoid dead ends we don't want the user to<00:20:52.080> be<00:20:52.860> sort<00:20:53.100> of<00:20:53.160> okay<00:20:53.550> very<00:20:53.760> well<00:20:53.850> I've<00:20:54.480> lost<00:20:54.720> I 00:20:54.920 --> 00:20:54.930 align:start position:0% to be sort of okay very well I've lost I 00:20:54.930 --> 00:20:56.630 align:start position:0% to be sort of okay very well I've lost I don't<00:20:55.110> know<00:20:55.170> what<00:20:55.260> to<00:20:55.350> do<00:20:55.410> next<00:20:55.590> so<00:20:55.860> consider 00:20:56.630 --> 00:20:56.640 align:start position:0% don't know what to do next so consider 00:20:56.640 --> 00:20:58.820 align:start position:0% don't know what to do next so consider next<00:20:56.820> steps<00:20:57.020> whenever<00:20:58.020> you're<00:20:58.170> designing<00:20:58.260> a 00:20:58.820 --> 00:20:58.830 align:start position:0% next steps whenever you're designing a 00:20:58.830 --> 00:21:01.650 align:start position:0% next steps whenever you're designing a float<00:20:59.370> is<00:20:59.580> probably 00:21:01.650 --> 00:21:01.660 align:start position:0% float is probably 00:21:01.660 --> 00:21:04.210 align:start position:0% float is probably and<00:21:02.660> that's<00:21:02.810> a<00:21:02.960> again<00:21:03.260> repair<00:21:03.710> chest<00:21:04.070> and 00:21:04.210 --> 00:21:04.220 align:start position:0% and that's a again repair chest and 00:21:04.220 --> 00:21:06.190 align:start position:0% and that's a again repair chest and plenty<00:21:04.490> more<00:21:04.520> about<00:21:04.820> Rimbaud<00:21:05.180> and<00:21:05.450> scan<00:21:06.080> the 00:21:06.190 --> 00:21:06.200 align:start position:0% plenty more about Rimbaud and scan the 00:21:06.200 --> 00:21:14.300 align:start position:0% plenty more about Rimbaud and scan the QR<00:21:06.470> codes<00:21:06.770> as<00:21:07.130> well<00:21:07.490> Twitter<00:21:09.130> thank<00:21:10.130> you 00:21:14.300 --> 00:21:14.310 align:start position:0% 00:21:14.310 --> 00:21:20.380 align:start position:0% [Applause]