WEBVTT Kind: captions Language: en 00:00:00.000 --> 00:00:04.350 align:start position:0% foreign 00:00:04.350 --> 00:00:04.360 align:start position:0% 00:00:04.360 --> 00:00:14.169 align:start position:0% [Music] 00:00:14.169 --> 00:00:14.179 align:start position:0% 00:00:14.179 --> 00:00:17.269 align:start position:0% is<00:00:15.179> redefining<00:00:16.080> the<00:00:16.560> level<00:00:16.680> of<00:00:16.980> control 00:00:17.269 --> 00:00:17.279 align:start position:0% is redefining the level of control 00:00:17.279 --> 00:00:21.470 align:start position:0% is redefining the level of control people<00:00:17.760> have<00:00:18.359> in<00:00:18.960> ways<00:00:19.380> that<00:00:19.820> was<00:00:20.820> deeply 00:00:21.470 --> 00:00:21.480 align:start position:0% people have in ways that was deeply 00:00:21.480 --> 00:00:23.990 align:start position:0% people have in ways that was deeply different<00:00:21.779> and<00:00:22.619> how<00:00:22.920> this<00:00:23.100> had<00:00:23.340> been<00:00:23.580> done 00:00:23.990 --> 00:00:24.000 align:start position:0% different and how this had been done 00:00:24.000 --> 00:00:27.830 align:start position:0% different and how this had been done before<00:00:24.300> not<00:00:25.140> only<00:00:25.320> that<00:00:25.740> well<00:00:26.460> 3<00:00:26.760> has<00:00:27.359> started 00:00:27.830 --> 00:00:27.840 align:start position:0% before not only that well 3 has started 00:00:27.840 --> 00:00:31.669 align:start position:0% before not only that well 3 has started with<00:00:28.080> literal<00:00:28.859> Financial<00:00:29.340> value<00:00:30.019> even<00:00:31.019> though 00:00:31.669 --> 00:00:31.679 align:start position:0% with literal Financial value even though 00:00:31.679 --> 00:00:35.209 align:start position:0% with literal Financial value even though this<00:00:31.980> is<00:00:32.160> an<00:00:32.480> empowering<00:00:33.480> proposition<00:00:34.020> we<00:00:34.980> see 00:00:35.209 --> 00:00:35.219 align:start position:0% this is an empowering proposition we see 00:00:35.219 --> 00:00:37.030 align:start position:0% this is an empowering proposition we see how<00:00:35.579> meaningful 00:00:37.030 --> 00:00:37.040 align:start position:0% how meaningful 00:00:37.040 --> 00:00:40.250 align:start position:0% how meaningful has<00:00:38.040> their<00:00:38.280> money<00:00:38.460> compromised<00:00:39.360> every<00:00:40.020> day 00:00:40.250 --> 00:00:40.260 align:start position:0% has their money compromised every day 00:00:40.260 --> 00:00:43.610 align:start position:0% has their money compromised every day I'm<00:00:40.860> Antonella<00:00:41.640> I<00:00:42.120> do<00:00:42.300> block<00:00:42.719> security<00:00:43.140> at 00:00:43.610 --> 00:00:43.620 align:start position:0% I'm Antonella I do block security at 00:00:43.620 --> 00:00:44.750 align:start position:0% I'm Antonella I do block security at metamask 00:00:44.750 --> 00:00:44.760 align:start position:0% metamask 00:00:44.760 --> 00:00:47.110 align:start position:0% metamask my<00:00:45.420> folks<00:00:45.899> are<00:00:46.140> there 00:00:47.110 --> 00:00:47.120 align:start position:0% my folks are there 00:00:47.120 --> 00:00:50.750 align:start position:0% my folks are there before<00:00:48.120> that<00:00:48.600> I<00:00:49.379> will<00:00:49.620> let<00:00:50.039> the<00:00:50.460> user 00:00:50.750 --> 00:00:50.760 align:start position:0% before that I will let the user 00:00:50.760 --> 00:00:53.150 align:start position:0% before that I will let the user experience<00:00:51.120> team<00:00:51.420> by<00:00:51.719> the<00:00:51.899> tour<00:00:52.079> project<00:00:52.440> for 00:00:53.150 --> 00:00:53.160 align:start position:0% experience team by the tour project for 00:00:53.160 --> 00:00:56.029 align:start position:0% experience team by the tour project for half<00:00:54.120> of<00:00:54.539> the<00:00:54.780> decade 00:00:56.029 --> 00:00:56.039 align:start position:0% half of the decade 00:00:56.039 --> 00:00:58.850 align:start position:0% half of the decade deploying<00:00:57.000> privacy<00:00:57.719> and<00:00:57.960> Hyson<00:00:58.440> technology 00:00:58.850 --> 00:00:58.860 align:start position:0% deploying privacy and Hyson technology 00:00:58.860 --> 00:01:03.590 align:start position:0% deploying privacy and Hyson technology is<00:00:59.280> not<00:00:59.579> a<00:00:59.820> crime<00:01:00.260> wallets<00:01:01.260> can<00:01:02.160> be<00:01:02.399> a<00:01:03.300> lot<00:01:03.420> of 00:01:03.590 --> 00:01:03.600 align:start position:0% is not a crime wallets can be a lot of 00:01:03.600 --> 00:01:04.430 align:start position:0% is not a crime wallets can be a lot of things 00:01:04.430 --> 00:01:04.440 align:start position:0% things 00:01:04.440 --> 00:01:07.310 align:start position:0% things we<00:01:04.860> can<00:01:05.040> Define<00:01:05.220> wallets<00:01:05.820> as<00:01:06.360> a<00:01:06.600> container<00:01:07.020> of 00:01:07.310 --> 00:01:07.320 align:start position:0% we can Define wallets as a container of 00:01:07.320 --> 00:01:09.170 align:start position:0% we can Define wallets as a container of private<00:01:07.799> keys<00:01:08.220> and<00:01:08.700> their<00:01:08.939> system 00:01:09.170 --> 00:01:09.180 align:start position:0% private keys and their system 00:01:09.180 --> 00:01:12.350 align:start position:0% private keys and their system affirmations<00:01:09.960> to<00:01:10.380> manage<00:01:10.680> them<00:01:10.860> every<00:01:11.400> time<00:01:11.700> a 00:01:12.350 --> 00:01:12.360 align:start position:0% affirmations to manage them every time a 00:01:12.360 --> 00:01:14.570 align:start position:0% affirmations to manage them every time a dove<00:01:12.720> asks<00:01:13.200> the<00:01:13.320> wallet<00:01:13.680> to<00:01:13.979> execute<00:01:14.400> a 00:01:14.570 --> 00:01:14.580 align:start position:0% dove asks the wallet to execute a 00:01:14.580 --> 00:01:17.030 align:start position:0% dove asks the wallet to execute a transaction<00:01:15.119> the<00:01:15.960> wallet<00:01:16.320> is<00:01:16.439> asking<00:01:16.860> the 00:01:17.030 --> 00:01:17.040 align:start position:0% transaction the wallet is asking the 00:01:17.040 --> 00:01:19.850 align:start position:0% transaction the wallet is asking the user<00:01:17.340> to<00:01:17.520> confirm<00:01:18.119> the<00:01:18.780> usage<00:01:19.140> of<00:01:19.380> this<00:01:19.619> case 00:01:19.850 --> 00:01:19.860 align:start position:0% user to confirm the usage of this case 00:01:19.860 --> 00:01:24.410 align:start position:0% user to confirm the usage of this case Dan<00:01:20.759> Finley<00:01:21.360> and<00:01:21.900> Eric<00:01:22.680> Marx<00:01:23.280> made<00:01:24.180> a 00:01:24.410 --> 00:01:24.420 align:start position:0% Dan Finley and Eric Marx made a 00:01:24.420 --> 00:01:25.810 align:start position:0% Dan Finley and Eric Marx made a beautiful<00:01:24.600> definition 00:01:25.810 --> 00:01:25.820 align:start position:0% beautiful definition 00:01:25.820 --> 00:01:28.310 align:start position:0% beautiful definition wallets<00:01:26.820> are<00:01:27.180> built<00:01:27.600> around<00:01:28.080> the 00:01:28.310 --> 00:01:28.320 align:start position:0% wallets are built around the 00:01:28.320 --> 00:01:31.690 align:start position:0% wallets are built around the responsibility<00:01:29.040> of<00:01:29.340> myriad<00:01:29.939> in<00:01:30.180> the<00:01:30.360> the 00:01:31.690 --> 00:01:31.700 align:start position:0% responsibility of myriad in the the 00:01:31.700 --> 00:01:34.670 align:start position:0% responsibility of myriad in the the interactions<00:01:32.700> between<00:01:33.680> untrusted 00:01:34.670 --> 00:01:34.680 align:start position:0% interactions between untrusted 00:01:34.680 --> 00:01:37.069 align:start position:0% interactions between untrusted applications<00:01:35.159> and<00:01:36.000> users<00:01:36.360> keys<00:01:36.780> on<00:01:36.900> the 00:01:37.069 --> 00:01:37.079 align:start position:0% applications and users keys on the 00:01:37.079 --> 00:01:39.410 align:start position:0% applications and users keys on the computers<00:01:37.500> getting<00:01:38.460> appropriate<00:01:39.060> consent 00:01:39.410 --> 00:01:39.420 align:start position:0% computers getting appropriate consent 00:01:39.420 --> 00:01:43.490 align:start position:0% computers getting appropriate consent from<00:01:39.659> the<00:01:39.840> user<00:01:40.200> if<00:01:40.860> we<00:01:41.180> map<00:01:42.180> a<00:01:42.840> thread<00:01:43.259> model 00:01:43.490 --> 00:01:43.500 align:start position:0% from the user if we map a thread model 00:01:43.500 --> 00:01:47.090 align:start position:0% from the user if we map a thread model of<00:01:44.040> a<00:01:44.220> non-cotiller<00:01:45.000> wallet<00:01:45.299> like<00:01:45.659> metamask 00:01:47.090 --> 00:01:47.100 align:start position:0% of a non-cotiller wallet like metamask 00:01:47.100 --> 00:01:49.429 align:start position:0% of a non-cotiller wallet like metamask we<00:01:47.520> will<00:01:47.640> discover<00:01:47.880> that<00:01:48.420> the<00:01:49.020> two<00:01:49.200> more 00:01:49.429 --> 00:01:49.439 align:start position:0% we will discover that the two more 00:01:49.439 --> 00:01:51.789 align:start position:0% we will discover that the two more important<00:01:49.799> assets<00:01:50.520> that<00:01:50.880> we<00:01:51.119> have<00:01:51.299> at<00:01:51.479> stake 00:01:51.789 --> 00:01:51.799 align:start position:0% important assets that we have at stake 00:01:51.799 --> 00:01:55.249 align:start position:0% important assets that we have at stake are<00:01:52.799> a<00:01:53.340> pair<00:01:53.520> of<00:01:53.700> keys<00:01:54.119> and<00:01:54.720> the<00:01:54.899> permissions 00:01:55.249 --> 00:01:55.259 align:start position:0% are a pair of keys and the permissions 00:01:55.259 --> 00:01:56.950 align:start position:0% are a pair of keys and the permissions to<00:01:55.619> use<00:01:55.799> this<00:01:56.040> keys 00:01:56.950 --> 00:01:56.960 align:start position:0% to use this keys 00:01:56.960 --> 00:01:59.990 align:start position:0% to use this keys this<00:01:57.960> talk<00:01:58.200> is<00:01:58.619> not<00:01:58.799> going<00:01:59.040> to<00:01:59.220> be<00:01:59.399> about<00:01:59.579> very 00:01:59.990 --> 00:02:00.000 align:start position:0% this talk is not going to be about very 00:02:00.000 --> 00:02:02.289 align:start position:0% this talk is not going to be about very Keys<00:02:00.540> it's<00:02:00.840> not<00:02:01.079> going<00:02:01.320> to<00:02:01.500> be<00:02:01.740> about 00:02:02.289 --> 00:02:02.299 align:start position:0% Keys it's not going to be about 00:02:02.299 --> 00:02:06.889 align:start position:0% Keys it's not going to be about artifacts<00:02:03.299> to<00:02:03.720> protect<00:02:04.320> this<00:02:04.740> privacy<00:02:05.159> like 00:02:06.889 --> 00:02:06.899 align:start position:0% artifacts to protect this privacy like 00:02:06.899 --> 00:02:10.370 align:start position:0% artifacts to protect this privacy like Oh<00:02:07.619> see<00:02:07.979> it's<00:02:08.220> phrases<00:02:08.899> passwords<00:02:09.899> fast 00:02:10.370 --> 00:02:10.380 align:start position:0% Oh see it's phrases passwords fast 00:02:10.380 --> 00:02:13.790 align:start position:0% Oh see it's phrases passwords fast prices<00:02:10.679> or<00:02:11.640> attacks<00:02:12.180> or<00:02:12.360> that 00:02:13.790 --> 00:02:13.800 align:start position:0% prices or attacks or that 00:02:13.800 --> 00:02:15.890 align:start position:0% prices or attacks or that today<00:02:14.400> I'm<00:02:15.180> going<00:02:15.420> to<00:02:15.599> talk<00:02:15.720> about 00:02:15.890 --> 00:02:15.900 align:start position:0% today I'm going to talk about 00:02:15.900 --> 00:02:17.150 align:start position:0% today I'm going to talk about permissions 00:02:17.150 --> 00:02:17.160 align:start position:0% permissions 00:02:17.160 --> 00:02:19.190 align:start position:0% permissions and<00:02:17.700> I<00:02:17.819> want<00:02:18.000> to<00:02:18.120> talk<00:02:18.300> about<00:02:18.480> permissions 00:02:19.190 --> 00:02:19.200 align:start position:0% and I want to talk about permissions 00:02:19.200 --> 00:02:22.970 align:start position:0% and I want to talk about permissions because<00:02:20.420> permissions<00:02:21.420> is<00:02:21.900> the<00:02:22.140> elephant<00:02:22.739> in 00:02:22.970 --> 00:02:22.980 align:start position:0% because permissions is the elephant in 00:02:22.980 --> 00:02:26.030 align:start position:0% because permissions is the elephant in the<00:02:23.160> room<00:02:23.400> usability<00:02:24.360> topic<00:02:25.020> Dev<00:02:25.379> foreign 00:02:26.030 --> 00:02:26.040 align:start position:0% the room usability topic Dev foreign 00:02:26.040 --> 00:02:29.089 align:start position:0% the room usability topic Dev foreign users<00:02:26.520> in<00:02:27.120> this<00:02:27.239> ecosystem<00:02:27.720> there<00:02:28.620> is<00:02:28.739> a<00:02:28.860> lack 00:02:29.089 --> 00:02:29.099 align:start position:0% users in this ecosystem there is a lack 00:02:29.099 --> 00:02:32.390 align:start position:0% users in this ecosystem there is a lack of<00:02:29.220> Interest<00:02:29.459> or<00:02:29.879> protocol<00:02:30.360> level<00:02:30.720> on<00:02:31.680> how 00:02:32.390 --> 00:02:32.400 align:start position:0% of Interest or protocol level on how 00:02:32.400 --> 00:02:35.210 align:start position:0% of Interest or protocol level on how protocol<00:02:32.760> decisions<00:02:33.420> affects<00:02:34.379> everyday 00:02:35.210 --> 00:02:35.220 align:start position:0% protocol decisions affects everyday 00:02:35.220 --> 00:02:38.089 align:start position:0% protocol decisions affects everyday people's<00:02:36.060> lives<00:02:36.360> and<00:02:36.840> the<00:02:37.020> responsibility<00:02:37.739> of 00:02:38.089 --> 00:02:38.099 align:start position:0% people's lives and the responsibility of 00:02:38.099 --> 00:02:40.449 align:start position:0% people's lives and the responsibility of giving<00:02:38.340> users<00:02:38.940> the<00:02:39.300> chance<00:02:39.540> to<00:02:39.959> understand 00:02:40.449 --> 00:02:40.459 align:start position:0% giving users the chance to understand 00:02:40.459 --> 00:02:43.790 align:start position:0% giving users the chance to understand what<00:02:41.459> they<00:02:41.640> are<00:02:41.760> giving<00:02:41.940> permissions<00:02:42.599> to 00:02:43.790 --> 00:02:43.800 align:start position:0% what they are giving permissions to 00:02:43.800 --> 00:02:47.869 align:start position:0% what they are giving permissions to falls<00:02:44.580> on<00:02:44.940> wallets<00:02:45.680> when<00:02:46.680> we<00:02:47.519> talk<00:02:47.700> about 00:02:47.869 --> 00:02:47.879 align:start position:0% falls on wallets when we talk about 00:02:47.879 --> 00:02:49.250 align:start position:0% falls on wallets when we talk about permissions 00:02:49.250 --> 00:02:49.260 align:start position:0% permissions 00:02:49.260 --> 00:02:52.550 align:start position:0% permissions we<00:02:49.739> talk<00:02:49.860> about<00:02:50.040> an<00:02:50.519> invoker<00:02:51.379> requesting<00:02:52.379> a 00:02:52.550 --> 00:02:52.560 align:start position:0% we talk about an invoker requesting a 00:02:52.560 --> 00:02:55.250 align:start position:0% we talk about an invoker requesting a wallet<00:02:52.920> access<00:02:53.420> to<00:02:54.420> certain<00:02:54.720> user 00:02:55.250 --> 00:02:55.260 align:start position:0% wallet access to certain user 00:02:55.260 --> 00:02:57.110 align:start position:0% wallet access to certain user information<00:02:55.519> it<00:02:56.519> can<00:02:56.700> be<00:02:56.819> different 00:02:57.110 --> 00:02:57.120 align:start position:0% information it can be different 00:02:57.120 --> 00:03:01.070 align:start position:0% information it can be different depending<00:02:58.080> on<00:02:58.319> what<00:02:58.800> the<00:02:58.980> rehab<00:02:59.459> is<00:03:00.180> prompting 00:03:01.070 --> 00:03:01.080 align:start position:0% depending on what the rehab is prompting 00:03:01.080 --> 00:03:03.949 align:start position:0% depending on what the rehab is prompting the<00:03:01.200> user<00:03:01.500> to<00:03:01.620> do<00:03:01.800> during<00:03:02.340> a<00:03:02.940> connect<00:03:03.180> flow<00:03:03.720> for 00:03:03.949 --> 00:03:03.959 align:start position:0% the user to do during a connect flow for 00:03:03.959 --> 00:03:07.430 align:start position:0% the user to do during a connect flow for example<00:03:04.260> the<00:03:05.099> rehab<00:03:05.640> is<00:03:06.599> requesting<00:03:07.200> access 00:03:07.430 --> 00:03:07.440 align:start position:0% example the rehab is requesting access 00:03:07.440 --> 00:03:11.449 align:start position:0% example the rehab is requesting access to<00:03:07.800> users<00:03:08.340> public<00:03:08.819> skills<00:03:09.480> the<00:03:09.900> address<00:03:10.280> to<00:03:11.280> be 00:03:11.449 --> 00:03:11.459 align:start position:0% to users public skills the address to be 00:03:11.459 --> 00:03:14.630 align:start position:0% to users public skills the address to be able<00:03:11.700> to<00:03:11.819> push<00:03:12.060> requests<00:03:12.720> in<00:03:13.260> this<00:03:13.440> way<00:03:13.640> and 00:03:14.630 --> 00:03:14.640 align:start position:0% able to push requests in this way and 00:03:14.640 --> 00:03:19.009 align:start position:0% able to push requests in this way and this<00:03:14.879> is<00:03:15.000> the<00:03:15.420> user-facing<00:03:16.400> interface<00:03:17.900> on<00:03:18.900> how 00:03:19.009 --> 00:03:19.019 align:start position:0% this is the user-facing interface on how 00:03:19.019 --> 00:03:21.710 align:start position:0% this is the user-facing interface on how the<00:03:19.260> request<00:03:19.620> looks<00:03:20.099> on<00:03:20.340> user's<00:03:20.819> computer<00:03:20.940> I'm 00:03:21.710 --> 00:03:21.720 align:start position:0% the request looks on user's computer I'm 00:03:21.720 --> 00:03:24.410 align:start position:0% the request looks on user's computer I'm sure<00:03:22.019> some<00:03:22.260> people<00:03:22.500> has<00:03:22.860> been<00:03:23.180> facing<00:03:24.180> these 00:03:24.410 --> 00:03:24.420 align:start position:0% sure some people has been facing these 00:03:24.420 --> 00:03:25.670 align:start position:0% sure some people has been facing these screens<00:03:24.840> before 00:03:25.670 --> 00:03:25.680 align:start position:0% screens before 00:03:25.680 --> 00:03:30.229 align:start position:0% screens before the<00:03:26.459> wallet<00:03:26.879> is<00:03:27.360> making<00:03:27.720> an<00:03:28.260> epic<00:03:28.620> effort<00:03:29.459> to 00:03:30.229 --> 00:03:30.239 align:start position:0% the wallet is making an epic effort to 00:03:30.239 --> 00:03:33.710 align:start position:0% the wallet is making an epic effort to expose<00:03:30.659> and<00:03:31.379> Trust<00:03:31.620> information<00:03:32.300> in<00:03:33.300> a<00:03:33.420> secure 00:03:33.710 --> 00:03:33.720 align:start position:0% expose and Trust information in a secure 00:03:33.720 --> 00:03:36.830 align:start position:0% expose and Trust information in a secure environment<00:03:34.200> in<00:03:34.980> a<00:03:35.099> legible<00:03:35.459> manner<00:03:36.000> so<00:03:36.659> the 00:03:36.830 --> 00:03:36.840 align:start position:0% environment in a legible manner so the 00:03:36.840 --> 00:03:39.830 align:start position:0% environment in a legible manner so the user<00:03:37.200> can<00:03:37.440> consent<00:03:37.980> to<00:03:38.459> execute<00:03:39.000> or<00:03:39.239> not<00:03:39.420> this 00:03:39.830 --> 00:03:39.840 align:start position:0% user can consent to execute or not this 00:03:39.840 --> 00:03:43.250 align:start position:0% user can consent to execute or not this transaction<00:03:40.319> we<00:03:41.159> do<00:03:41.340> things<00:03:41.700> like 00:03:43.250 --> 00:03:43.260 align:start position:0% transaction we do things like 00:03:43.260 --> 00:03:45.830 align:start position:0% transaction we do things like treating<00:03:43.860> childish<00:03:44.519> and<00:03:44.700> treat<00:03:45.000> analysis 00:03:45.830 --> 00:03:45.840 align:start position:0% treating childish and treat analysis 00:03:45.840 --> 00:03:49.369 align:start position:0% treating childish and treat analysis human<00:03:46.680> review<00:03:47.120> we<00:03:48.120> have<00:03:48.299> a<00:03:48.480> lava<00:03:48.900> mode<00:03:49.019> for 00:03:49.369 --> 00:03:49.379 align:start position:0% human review we have a lava mode for 00:03:49.379 --> 00:03:51.830 align:start position:0% human review we have a lava mode for preventing<00:03:49.920> supply<00:03:50.220> chain<00:03:50.580> attacks<00:03:51.120> you 00:03:51.830 --> 00:03:51.840 align:start position:0% preventing supply chain attacks you 00:03:51.840 --> 00:03:53.809 align:start position:0% preventing supply chain attacks you should<00:03:51.959> check<00:03:52.140> out<00:03:52.379> on<00:03:52.560> kumari's<00:03:53.400> talk<00:03:53.519> from 00:03:53.809 --> 00:03:53.819 align:start position:0% should check out on kumari's talk from 00:03:53.819 --> 00:03:56.990 align:start position:0% should check out on kumari's talk from yesterday<00:03:54.200> we<00:03:55.200> have<00:03:55.379> fishing<00:03:56.040> detect<00:03:56.700> block 00:03:56.990 --> 00:03:57.000 align:start position:0% yesterday we have fishing detect block 00:03:57.000 --> 00:04:00.649 align:start position:0% yesterday we have fishing detect block lists<00:03:57.659> to<00:03:58.560> Medical<00:03:58.739> efficient<00:03:59.280> attacks<00:03:59.879> our 00:04:00.649 --> 00:04:00.659 align:start position:0% lists to Medical efficient attacks our 00:04:00.659 --> 00:04:03.229 align:start position:0% lists to Medical efficient attacks our vanity<00:04:01.200> program<00:04:01.440> and<00:04:01.920> more<00:04:02.159> people<00:04:02.700> who<00:04:03.060> work 00:04:03.229 --> 00:04:03.239 align:start position:0% vanity program and more people who work 00:04:03.239 --> 00:04:06.229 align:start position:0% vanity program and more people who work on<00:04:03.480> security<00:04:03.739> knows<00:04:04.739> that<00:04:04.980> this<00:04:05.640> is<00:04:05.879> called 00:04:06.229 --> 00:04:06.239 align:start position:0% on security knows that this is called 00:04:06.239 --> 00:04:09.530 align:start position:0% on security knows that this is called elastic<00:04:07.140> security<00:04:07.560> or<00:04:08.040> Security<00:04:08.280> in<00:04:08.700> that<00:04:08.940> but 00:04:09.530 --> 00:04:09.540 align:start position:0% elastic security or Security in that but 00:04:09.540 --> 00:04:12.229 align:start position:0% elastic security or Security in that but this<00:04:09.840> is<00:04:10.019> not<00:04:10.260> enough<00:04:10.439> to<00:04:11.280> enable<00:04:11.519> users<00:04:12.000> to 00:04:12.229 --> 00:04:12.239 align:start position:0% this is not enough to enable users to 00:04:12.239 --> 00:04:15.789 align:start position:0% this is not enough to enable users to consent<00:04:12.659> in<00:04:12.900> transaction<00:04:13.700> and<00:04:14.700> I<00:04:15.060> will<00:04:15.239> stop 00:04:15.789 --> 00:04:15.799 align:start position:0% consent in transaction and I will stop 00:04:15.799 --> 00:04:19.909 align:start position:0% consent in transaction and I will stop and<00:04:16.799> I<00:04:17.519> imagine<00:04:18.139> that<00:04:19.139> some<00:04:19.380> people<00:04:19.560> is 00:04:19.909 --> 00:04:19.919 align:start position:0% and I imagine that some people is 00:04:19.919 --> 00:04:23.270 align:start position:0% and I imagine that some people is questioning<00:04:20.780> why<00:04:21.780> we<00:04:22.500> are<00:04:22.680> talking<00:04:22.919> about 00:04:23.270 --> 00:04:23.280 align:start position:0% questioning why we are talking about 00:04:23.280 --> 00:04:28.129 align:start position:0% questioning why we are talking about consent<00:04:24.139> in<00:04:25.139> a<00:04:25.680> usable<00:04:26.100> security<00:04:26.520> talk<00:04:27.139> and 00:04:28.129 --> 00:04:28.139 align:start position:0% consent in a usable security talk and 00:04:28.139 --> 00:04:29.390 align:start position:0% consent in a usable security talk and Friends 00:04:29.390 --> 00:04:29.400 align:start position:0% Friends 00:04:29.400 --> 00:04:32.090 align:start position:0% Friends because<00:04:30.120> they<00:04:30.600> are<00:04:30.840> not<00:04:30.960> secure<00:04:31.380> systems 00:04:32.090 --> 00:04:32.100 align:start position:0% because they are not secure systems 00:04:32.100 --> 00:04:35.510 align:start position:0% because they are not secure systems without<00:04:32.580> consent<00:04:33.180> consent<00:04:34.020> is<00:04:34.380> the<00:04:34.680> radical 00:04:35.510 --> 00:04:35.520 align:start position:0% without consent consent is the radical 00:04:35.520 --> 00:04:39.230 align:start position:0% without consent consent is the radical idea<00:04:36.060> that<00:04:36.960> one<00:04:37.259> person<00:04:37.500> must<00:04:38.400> voluntarily 00:04:39.230 --> 00:04:39.240 align:start position:0% idea that one person must voluntarily 00:04:39.240 --> 00:04:41.390 align:start position:0% idea that one person must voluntarily agree<00:04:39.540> to<00:04:39.840> the<00:04:40.020> proposal<00:04:40.440> of<00:04:40.680> the<00:04:40.860> size<00:04:41.040> to 00:04:41.390 --> 00:04:41.400 align:start position:0% agree to the proposal of the size to 00:04:41.400 --> 00:04:43.909 align:start position:0% agree to the proposal of the size to another<00:04:41.580> thinking<00:04:42.479> about<00:04:42.720> this<00:04:43.199> why<00:04:43.620> Building 00:04:43.909 --> 00:04:43.919 align:start position:0% another thinking about this why Building 00:04:43.919 --> 00:04:47.870 align:start position:0% another thinking about this why Building Technology<00:04:44.720> he<00:04:45.720> still<00:04:45.960> gives<00:04:46.259> a<00:04:46.880> feminist 00:04:47.870 --> 00:04:47.880 align:start position:0% Technology he still gives a feminist 00:04:47.880 --> 00:04:51.170 align:start position:0% Technology he still gives a feminist perspective<00:04:48.660> to<00:04:49.259> active<00:04:49.740> concern<00:04:50.280> to<00:04:50.820> apply 00:04:51.170 --> 00:04:51.180 align:start position:0% perspective to active concern to apply 00:04:51.180 --> 00:04:53.770 align:start position:0% perspective to active concern to apply it<00:04:51.360> to<00:04:51.720> their<00:04:52.080> social<00:04:52.440> information<00:04:52.860> system 00:04:53.770 --> 00:04:53.780 align:start position:0% it to their social information system 00:04:53.780 --> 00:04:56.990 align:start position:0% it to their social information system that<00:04:54.780> we<00:04:54.960> work<00:04:55.199> with<00:04:55.560> every<00:04:55.860> day<00:04:56.160> these<00:04:56.880> are 00:04:56.990 --> 00:04:57.000 align:start position:0% that we work with every day these are 00:04:57.000 --> 00:04:58.810 align:start position:0% that we work with every day these are not<00:04:57.240> my<00:04:57.720> ideas 00:04:58.810 --> 00:04:58.820 align:start position:0% not my ideas 00:04:58.820 --> 00:05:02.270 align:start position:0% not my ideas these<00:04:59.820> are<00:04:59.940> ideas<00:05:00.780> that<00:05:01.199> came<00:05:01.620> in<00:05:02.100> the 00:05:02.270 --> 00:05:02.280 align:start position:0% these are ideas that came in the 00:05:02.280 --> 00:05:06.290 align:start position:0% these are ideas that came in the backbone<00:05:02.759> from<00:05:03.600> the<00:05:03.960> feminist<00:05:04.919> principles<00:05:05.880> of 00:05:06.290 --> 00:05:06.300 align:start position:0% backbone from the feminist principles of 00:05:06.300 --> 00:05:10.070 align:start position:0% backbone from the feminist principles of the<00:05:06.479> internet<00:05:07.040> for<00:05:08.040> open<00:05:08.820> human<00:05:09.479> centered 00:05:10.070 --> 00:05:10.080 align:start position:0% the internet for open human centered 00:05:10.080 --> 00:05:13.249 align:start position:0% the internet for open human centered design<00:05:10.320> processes<00:05:11.300> basically<00:05:12.300> when<00:05:12.900> we<00:05:13.080> talk 00:05:13.249 --> 00:05:13.259 align:start position:0% design processes basically when we talk 00:05:13.259 --> 00:05:15.650 align:start position:0% design processes basically when we talk about<00:05:13.440> consensual<00:05:14.220> technology<00:05:14.820> we<00:05:15.540> talk 00:05:15.650 --> 00:05:15.660 align:start position:0% about consensual technology we talk 00:05:15.660 --> 00:05:19.189 align:start position:0% about consensual technology we talk about<00:05:15.900> having<00:05:16.440> control<00:05:16.979> over<00:05:17.759> our<00:05:18.360> digital 00:05:19.189 --> 00:05:19.199 align:start position:0% about having control over our digital 00:05:19.199 --> 00:05:22.850 align:start position:0% about having control over our digital bodies<00:05:19.740> which<00:05:20.400> of<00:05:20.699> course<00:05:20.940> include<00:05:21.900> our<00:05:22.199> data 00:05:22.850 --> 00:05:22.860 align:start position:0% bodies which of course include our data 00:05:22.860 --> 00:05:26.330 align:start position:0% bodies which of course include our data and<00:05:23.280> for<00:05:23.520> sure<00:05:23.759> our<00:05:24.120> money<00:05:24.419> so<00:05:25.199> how<00:05:26.039> a 00:05:26.330 --> 00:05:26.340 align:start position:0% and for sure our money so how a 00:05:26.340 --> 00:05:28.969 align:start position:0% and for sure our money so how a transaction<00:05:26.699> based<00:05:27.300> on<00:05:27.539> concern<00:05:28.020> should<00:05:28.320> be<00:05:28.500> a 00:05:28.969 --> 00:05:28.979 align:start position:0% transaction based on concern should be a 00:05:28.979 --> 00:05:31.249 align:start position:0% transaction based on concern should be a few<00:05:29.100> people<00:05:29.340> has<00:05:30.120> been<00:05:30.360> thinking<00:05:30.660> about<00:05:30.900> this 00:05:31.249 --> 00:05:31.259 align:start position:0% few people has been thinking about this 00:05:31.259 --> 00:05:34.010 align:start position:0% few people has been thinking about this they're<00:05:32.100> finding<00:05:32.520> a<00:05:32.759> framework<00:05:33.240> on<00:05:33.600> how<00:05:33.840> to 00:05:34.010 --> 00:05:34.020 align:start position:0% they're finding a framework on how to 00:05:34.020 --> 00:05:37.629 align:start position:0% they're finding a framework on how to approach<00:05:34.520> a<00:05:35.520> consensual<00:05:36.300> way<00:05:36.840> to<00:05:37.440> having 00:05:37.629 --> 00:05:37.639 align:start position:0% approach a consensual way to having 00:05:37.639 --> 00:05:40.310 align:start position:0% approach a consensual way to having interactions<00:05:38.639> I<00:05:39.240> really<00:05:39.419> like<00:05:39.720> the<00:05:40.139> five 00:05:40.310 --> 00:05:40.320 align:start position:0% interactions I really like the five 00:05:40.320 --> 00:05:43.310 align:start position:0% interactions I really like the five principles<00:05:40.919> defined<00:05:41.460> by<00:05:41.820> false<00:05:42.360> uh<00:05:42.720> Alien 00:05:43.310 --> 00:05:43.320 align:start position:0% principles defined by false uh Alien 00:05:43.320 --> 00:05:46.850 align:start position:0% principles defined by false uh Alien media<00:05:43.740> you<00:05:44.520> can<00:05:44.639> check<00:05:45.000> this<00:05:45.360> and<00:05:46.080> more<00:05:46.320> in<00:05:46.680> the 00:05:46.850 --> 00:05:46.860 align:start position:0% media you can check this and more in the 00:05:46.860 --> 00:05:49.270 align:start position:0% media you can check this and more in the website<00:05:47.220> it's<00:05:47.520> called<00:05:47.759> senseful<00:05:48.300> touch.io 00:05:49.270 --> 00:05:49.280 align:start position:0% website it's called senseful touch.io 00:05:49.280 --> 00:05:52.129 align:start position:0% website it's called senseful touch.io good<00:05:50.280> consent<00:05:50.759> is 00:05:52.129 --> 00:05:52.139 align:start position:0% good consent is 00:05:52.139 --> 00:05:56.029 align:start position:0% good consent is freely<00:05:52.740> given<00:05:53.160> is<00:05:53.820> revocable<00:05:54.539> it's<00:05:55.380> informed 00:05:56.029 --> 00:05:56.039 align:start position:0% freely given is revocable it's informed 00:05:56.039 --> 00:05:59.810 align:start position:0% freely given is revocable it's informed it's<00:05:56.699> enthusiastic<00:05:57.479> and<00:05:58.380> it's<00:05:58.560> specific<00:05:59.100> and 00:05:59.810 --> 00:05:59.820 align:start position:0% it's enthusiastic and it's specific and 00:05:59.820 --> 00:06:02.749 align:start position:0% it's enthusiastic and it's specific and what<00:06:00.060> we<00:06:00.240> mean<00:06:00.419> by<00:06:01.380> all<00:06:01.919> these<00:06:02.160> things<00:06:02.220> the 00:06:02.749 --> 00:06:02.759 align:start position:0% what we mean by all these things the 00:06:02.759 --> 00:06:04.730 align:start position:0% what we mean by all these things the fact<00:06:02.880> that<00:06:03.060> the<00:06:03.300> consent<00:06:03.660> is<00:06:03.900> freely<00:06:04.320> given 00:06:04.730 --> 00:06:04.740 align:start position:0% fact that the consent is freely given 00:06:04.740 --> 00:06:07.129 align:start position:0% fact that the consent is freely given puts<00:06:05.400> the<00:06:05.520> person<00:06:05.699> in<00:06:06.000> a<00:06:06.120> position<00:06:06.300> of<00:06:06.780> doing 00:06:07.129 --> 00:06:07.139 align:start position:0% puts the person in a position of doing 00:06:07.139 --> 00:06:10.310 align:start position:0% puts the person in a position of doing something<00:06:07.680> with<00:06:08.639> another<00:06:08.960> that<00:06:09.960> should<00:06:10.139> be 00:06:10.310 --> 00:06:10.320 align:start position:0% something with another that should be 00:06:10.320 --> 00:06:12.950 align:start position:0% something with another that should be made<00:06:10.440> without<00:06:10.800> pressure<00:06:11.340> with<00:06:12.180> force<00:06:12.660> or 00:06:12.950 --> 00:06:12.960 align:start position:0% made without pressure with force or 00:06:12.960 --> 00:06:14.590 align:start position:0% made without pressure with force or manipulation 00:06:14.590 --> 00:06:14.600 align:start position:0% manipulation 00:06:14.600 --> 00:06:18.590 align:start position:0% manipulation anyone<00:06:15.600> can<00:06:16.380> change<00:06:16.680> the<00:06:16.979> mind<00:06:17.340> on<00:06:18.180> what<00:06:18.360> they 00:06:18.590 --> 00:06:18.600 align:start position:0% anyone can change the mind on what they 00:06:18.600 --> 00:06:22.969 align:start position:0% anyone can change the mind on what they do<00:06:18.780> at<00:06:19.380> any<00:06:19.680> time<00:06:20.240> trust<00:06:21.240> is<00:06:21.660> not<00:06:21.900> forever<00:06:22.319> this 00:06:22.969 --> 00:06:22.979 align:start position:0% do at any time trust is not forever this 00:06:22.979 --> 00:06:25.249 align:start position:0% do at any time trust is not forever this is<00:06:23.160> why<00:06:23.400> transactions<00:06:24.300> should<00:06:24.539> be<00:06:24.660> revocable 00:06:25.249 --> 00:06:25.259 align:start position:0% is why transactions should be revocable 00:06:25.259 --> 00:06:28.010 align:start position:0% is why transactions should be revocable people<00:06:25.979> should<00:06:26.340> be<00:06:26.460> able<00:06:26.759> to<00:06:26.880> understand<00:06:27.120> what 00:06:28.010 --> 00:06:28.020 align:start position:0% people should be able to understand what 00:06:28.020 --> 00:06:30.409 align:start position:0% people should be able to understand what the<00:06:28.259> trade-offs<00:06:28.919> are<00:06:29.280> of<00:06:29.759> this<00:06:30.060> decision 00:06:30.409 --> 00:06:30.419 align:start position:0% the trade-offs are of this decision 00:06:30.419 --> 00:06:33.770 align:start position:0% the trade-offs are of this decision people<00:06:31.080> should<00:06:31.440> be<00:06:31.560> able<00:06:31.919> to<00:06:32.100> read<00:06:32.580> what<00:06:33.539> they 00:06:33.770 --> 00:06:33.780 align:start position:0% people should be able to read what they 00:06:33.780 --> 00:06:36.469 align:start position:0% people should be able to read what they are<00:06:33.900> going<00:06:34.139> to<00:06:34.580> consent<00:06:35.580> to 00:06:36.469 --> 00:06:36.479 align:start position:0% are going to consent to 00:06:36.479 --> 00:06:39.890 align:start position:0% are going to consent to people<00:06:36.960> should<00:06:37.319> be<00:06:37.500> able<00:06:37.740> to<00:06:38.120> comprehend<00:06:39.120> what 00:06:39.890 --> 00:06:39.900 align:start position:0% people should be able to comprehend what 00:06:39.900 --> 00:06:42.230 align:start position:0% people should be able to comprehend what is<00:06:40.080> going<00:06:40.319> on<00:06:40.979> consent<00:06:41.880> should<00:06:42.060> be 00:06:42.230 --> 00:06:42.240 align:start position:0% is going on consent should be 00:06:42.240 --> 00:06:45.230 align:start position:0% is going on consent should be enthusiastic<00:06:42.900> if<00:06:43.800> someone<00:06:44.039> is<00:06:44.280> not<00:06:44.520> excited 00:06:45.230 --> 00:06:45.240 align:start position:0% enthusiastic if someone is not excited 00:06:45.240 --> 00:06:47.930 align:start position:0% enthusiastic if someone is not excited or<00:06:45.720> really<00:06:45.900> into<00:06:46.259> it<00:06:46.620> that<00:06:47.160> is<00:06:47.340> not<00:06:47.460> consent 00:06:47.930 --> 00:06:47.940 align:start position:0% or really into it that is not consent 00:06:47.940 --> 00:06:50.930 align:start position:0% or really into it that is not consent consent<00:06:48.840> should<00:06:49.080> be<00:06:49.259> specific<00:06:49.680> saying<00:06:50.580> yes<00:06:50.699> to 00:06:50.930 --> 00:06:50.940 align:start position:0% consent should be specific saying yes to 00:06:50.940 --> 00:06:55.309 align:start position:0% consent should be specific saying yes to this<00:06:51.240> now<00:06:52.080> today<00:06:52.680> here<00:06:53.639> in<00:06:54.000> Bogota<00:06:54.419> in<00:06:54.900> October 00:06:55.309 --> 00:06:55.319 align:start position:0% this now today here in Bogota in October 00:06:55.319 --> 00:06:58.790 align:start position:0% this now today here in Bogota in October doesn't<00:06:56.039> mean<00:06:56.539> that<00:06:57.539> I<00:06:57.840> said<00:06:58.020> yes<00:06:58.380> to<00:06:58.620> other 00:06:58.790 --> 00:06:58.800 align:start position:0% doesn't mean that I said yes to other 00:06:58.800 --> 00:07:02.990 align:start position:0% doesn't mean that I said yes to other things<00:06:59.160> so<00:07:00.199> we<00:07:01.199> started<00:07:01.680> questioning<00:07:02.400> our 00:07:02.990 --> 00:07:03.000 align:start position:0% things so we started questioning our 00:07:03.000 --> 00:07:06.430 align:start position:0% things so we started questioning our interfaces<00:07:03.900> and<00:07:04.620> how<00:07:05.039> they<00:07:05.400> can<00:07:05.639> become 00:07:06.430 --> 00:07:06.440 align:start position:0% interfaces and how they can become 00:07:06.440 --> 00:07:10.430 align:start position:0% interfaces and how they can become interfaces<00:07:07.440> that<00:07:08.100> could<00:07:08.400> enable<00:07:08.759> people<00:07:09.440> to 00:07:10.430 --> 00:07:10.440 align:start position:0% interfaces that could enable people to 00:07:10.440 --> 00:07:13.430 align:start position:0% interfaces that could enable people to give<00:07:10.680> real<00:07:11.100> consent<00:07:11.819> the<00:07:12.600> use<00:07:12.780> of<00:07:13.020> a<00:07:13.199> security 00:07:13.430 --> 00:07:13.440 align:start position:0% give real consent the use of a security 00:07:13.440 --> 00:07:16.430 align:start position:0% give real consent the use of a security design<00:07:13.860> question<00:07:14.460> that<00:07:15.180> we<00:07:15.360> put<00:07:15.600> over<00:07:15.900> a<00:07:16.199> table 00:07:16.430 --> 00:07:16.440 align:start position:0% design question that we put over a table 00:07:16.440 --> 00:07:19.790 align:start position:0% design question that we put over a table with<00:07:17.039> our<00:07:17.280> teams<00:07:18.000> with<00:07:18.900> designers<00:07:19.500> with 00:07:19.790 --> 00:07:19.800 align:start position:0% with our teams with designers with 00:07:19.800 --> 00:07:22.129 align:start position:0% with our teams with designers with developers<00:07:20.340> with<00:07:20.639> project<00:07:20.819> managers<00:07:21.660> with 00:07:22.129 --> 00:07:22.139 align:start position:0% developers with project managers with 00:07:22.139 --> 00:07:24.170 align:start position:0% developers with project managers with people<00:07:22.319> working<00:07:22.680> on<00:07:23.039> metrics<00:07:23.639> with<00:07:23.940> people 00:07:24.170 --> 00:07:24.180 align:start position:0% people working on metrics with people 00:07:24.180 --> 00:07:28.010 align:start position:0% people working on metrics with people working<00:07:24.680> on<00:07:25.680> communication<00:07:26.460> if<00:07:27.360> we<00:07:27.479> build<00:07:27.780> a 00:07:28.010 --> 00:07:28.020 align:start position:0% working on communication if we build a 00:07:28.020 --> 00:07:31.010 align:start position:0% working on communication if we build a transaction<00:07:28.440> flow<00:07:29.060> grounded<00:07:30.060> in<00:07:30.240> concerned 00:07:31.010 --> 00:07:31.020 align:start position:0% transaction flow grounded in concerned 00:07:31.020 --> 00:07:34.129 align:start position:0% transaction flow grounded in concerned how<00:07:31.680> could<00:07:31.860> it<00:07:32.099> look<00:07:32.400> like 00:07:34.129 --> 00:07:34.139 align:start position:0% how could it look like 00:07:34.139 --> 00:07:35.029 align:start position:0% how could it look like um 00:07:35.029 --> 00:07:35.039 align:start position:0% um 00:07:35.039 --> 00:07:36.589 align:start position:0% um you<00:07:35.759> spoke 00:07:36.589 --> 00:07:36.599 align:start position:0% you spoke 00:07:36.599 --> 00:07:39.230 align:start position:0% you spoke and<00:07:37.199> we<00:07:37.380> are<00:07:37.560> listening<00:07:38.099> we<00:07:38.759> read<00:07:38.940> social 00:07:39.230 --> 00:07:39.240 align:start position:0% and we are listening we read social 00:07:39.240 --> 00:07:42.469 align:start position:0% and we are listening we read social media<00:07:39.840> we<00:07:40.319> read<00:07:40.620> the<00:07:40.860> forums<00:07:41.460> we<00:07:41.699> read 00:07:42.469 --> 00:07:42.479 align:start position:0% media we read the forums we read 00:07:42.479 --> 00:07:44.930 align:start position:0% media we read the forums we read and<00:07:43.020> we<00:07:43.259> are<00:07:43.380> working<00:07:43.620> hard<00:07:43.979> on<00:07:44.280> improving<00:07:44.759> our 00:07:44.930 --> 00:07:44.940 align:start position:0% and we are working hard on improving our 00:07:44.940 --> 00:07:46.909 align:start position:0% and we are working hard on improving our confirmation<00:07:45.599> screens 00:07:46.909 --> 00:07:46.919 align:start position:0% confirmation screens 00:07:46.919 --> 00:07:50.689 align:start position:0% confirmation screens even<00:07:47.460> when<00:07:47.940> new<00:07:48.840> transactions<00:07:49.740> methods<00:07:50.340> are 00:07:50.689 --> 00:07:50.699 align:start position:0% even when new transactions methods are 00:07:50.699 --> 00:07:53.629 align:start position:0% even when new transactions methods are being<00:07:50.940> defined<00:07:51.539> right<00:07:52.500> now<00:07:52.620> in<00:07:52.919> other<00:07:53.099> rooms 00:07:53.629 --> 00:07:53.639 align:start position:0% being defined right now in other rooms 00:07:53.639 --> 00:07:56.570 align:start position:0% being defined right now in other rooms on<00:07:54.300> protocol<00:07:54.720> level<00:07:55.139> without<00:07:55.800> considering 00:07:56.570 --> 00:07:56.580 align:start position:0% on protocol level without considering 00:07:56.580 --> 00:07:58.670 align:start position:0% on protocol level without considering how<00:07:56.880> to<00:07:57.000> expose<00:07:57.360> users<00:07:57.780> to<00:07:57.960> a<00:07:58.139> consensual 00:07:58.670 --> 00:07:58.680 align:start position:0% how to expose users to a consensual 00:07:58.680 --> 00:08:00.890 align:start position:0% how to expose users to a consensual interaction<00:07:59.280> let's<00:08:00.120> see<00:08:00.300> the<00:08:00.479> case<00:08:00.660> of 00:08:00.890 --> 00:08:00.900 align:start position:0% interaction let's see the case of 00:08:00.900 --> 00:08:09.370 align:start position:0% interaction let's see the case of approvals 00:08:09.370 --> 00:08:09.380 align:start position:0% 00:08:09.380 --> 00:08:12.409 align:start position:0% to<00:08:10.380> allow<00:08:10.680> a<00:08:10.979> smart<00:08:11.220> contracts<00:08:11.880> to 00:08:12.409 --> 00:08:12.419 align:start position:0% to allow a smart contracts to 00:08:12.419 --> 00:08:14.930 align:start position:0% to allow a smart contracts to interoperate<00:08:13.139> tokens<00:08:13.740> and<00:08:14.220> provide<00:08:14.580> a<00:08:14.759> better 00:08:14.930 --> 00:08:14.940 align:start position:0% interoperate tokens and provide a better 00:08:14.940 --> 00:08:17.629 align:start position:0% interoperate tokens and provide a better user<00:08:15.720> experience<00:08:16.199> what<00:08:16.620> interacts<00:08:17.220> with<00:08:17.520> that 00:08:17.629 --> 00:08:17.639 align:start position:0% user experience what interacts with that 00:08:17.639 --> 00:08:20.270 align:start position:0% user experience what interacts with that in<00:08:18.240> order<00:08:18.419> to<00:08:18.660> perform<00:08:18.900> operations<00:08:19.620> that 00:08:20.270 --> 00:08:20.280 align:start position:0% in order to perform operations that 00:08:20.280 --> 00:08:22.249 align:start position:0% in order to perform operations that require<00:08:20.539> interactions<00:08:21.539> with<00:08:21.900> a<00:08:22.080> man 00:08:22.249 --> 00:08:22.259 align:start position:0% require interactions with a man 00:08:22.259 --> 00:08:25.550 align:start position:0% require interactions with a man contracts<00:08:22.919> like<00:08:23.160> minting<00:08:23.879> stacking<00:08:24.660> swapping 00:08:25.550 --> 00:08:25.560 align:start position:0% contracts like minting stacking swapping 00:08:25.560 --> 00:08:29.689 align:start position:0% contracts like minting stacking swapping users<00:08:26.460> are<00:08:27.240> first<00:08:27.740> required<00:08:28.740> to<00:08:28.979> permit<00:08:29.340> the 00:08:29.689 --> 00:08:29.699 align:start position:0% users are first required to permit the 00:08:29.699 --> 00:08:31.969 align:start position:0% users are first required to permit the invokers<00:08:30.300> more<00:08:30.660> contract<00:08:31.139> to<00:08:31.319> transfer<00:08:31.800> a 00:08:31.969 --> 00:08:31.979 align:start position:0% invokers more contract to transfer a 00:08:31.979 --> 00:08:33.889 align:start position:0% invokers more contract to transfer a number<00:08:32.159> of<00:08:32.399> tokens<00:08:32.940> on<00:08:33.300> their<00:08:33.419> rehab 00:08:33.889 --> 00:08:33.899 align:start position:0% number of tokens on their rehab 00:08:33.899 --> 00:08:36.529 align:start position:0% number of tokens on their rehab sometimes<00:08:34.560> the<00:08:34.800> dive<00:08:35.099> required<00:08:35.640> improving 00:08:36.529 --> 00:08:36.539 align:start position:0% sometimes the dive required improving 00:08:36.539 --> 00:08:39.769 align:start position:0% sometimes the dive required improving this<00:08:36.919> infinite<00:08:37.919> amount<00:08:38.580> of<00:08:38.940> these<00:08:39.360> tokens 00:08:39.769 --> 00:08:39.779 align:start position:0% this infinite amount of these tokens 00:08:39.779 --> 00:08:43.510 align:start position:0% this infinite amount of these tokens even<00:08:40.260> if<00:08:40.500> the<00:08:40.740> user<00:08:41.099> trust<00:08:41.640> it<00:08:41.940> up<00:08:42.120> it<00:08:42.659> could<00:08:42.899> be 00:08:43.510 --> 00:08:43.520 align:start position:0% even if the user trust it up it could be 00:08:43.520 --> 00:08:48.530 align:start position:0% even if the user trust it up it could be problematic<00:08:44.600> this<00:08:45.600> is<00:08:45.720> our<00:08:46.279> current<00:08:47.540> tokens 00:08:48.530 --> 00:08:48.540 align:start position:0% problematic this is our current tokens 00:08:48.540 --> 00:08:50.889 align:start position:0% problematic this is our current tokens allowance<00:08:49.380> screen 00:08:50.889 --> 00:08:50.899 align:start position:0% allowance screen 00:08:50.899 --> 00:08:54.350 align:start position:0% allowance screen we<00:08:51.899> have<00:08:52.200> the<00:08:52.740> original<00:08:52.980> mind<00:08:53.640> requesting 00:08:54.350 --> 00:08:54.360 align:start position:0% we have the original mind requesting 00:08:54.360 --> 00:08:56.690 align:start position:0% we have the original mind requesting this<00:08:54.660> transaction<00:08:55.140> we<00:08:55.800> have<00:08:55.920> the<00:08:56.220> contract 00:08:56.690 --> 00:08:56.700 align:start position:0% this transaction we have the contract 00:08:56.700 --> 00:08:59.690 align:start position:0% this transaction we have the contract explicit<00:08:57.600> who<00:08:58.380> is<00:08:58.500> asking<00:08:59.220> for<00:08:59.459> this 00:08:59.690 --> 00:08:59.700 align:start position:0% explicit who is asking for this 00:08:59.700 --> 00:09:02.509 align:start position:0% explicit who is asking for this interaction<00:09:00.120> but<00:09:00.959> the<00:09:01.200> point<00:09:01.380> here<00:09:01.680> is 00:09:02.509 --> 00:09:02.519 align:start position:0% interaction but the point here is 00:09:02.519 --> 00:09:05.630 align:start position:0% interaction but the point here is we<00:09:03.180> don't<00:09:03.360> have<00:09:03.600> allowances<00:09:04.260> in<00:09:05.220> the<00:09:05.399> first 00:09:05.630 --> 00:09:05.640 align:start position:0% we don't have allowances in the first 00:09:05.640 --> 00:09:08.690 align:start position:0% we don't have allowances in the first screen<00:09:06.120> of<00:09:06.660> this<00:09:06.899> flow<00:09:07.320> and<00:09:08.160> we<00:09:08.339> have<00:09:08.519> been 00:09:08.690 --> 00:09:08.700 align:start position:0% screen of this flow and we have been 00:09:08.700 --> 00:09:11.750 align:start position:0% screen of this flow and we have been working<00:09:08.940> on<00:09:09.240> that<00:09:09.480> and<00:09:10.440> we<00:09:10.860> iterated<00:09:11.339> this 00:09:11.750 --> 00:09:11.760 align:start position:0% working on that and we iterated this 00:09:11.760 --> 00:09:16.070 align:start position:0% working on that and we iterated this this<00:09:12.540> new<00:09:13.080> UI<00:09:13.580> aims<00:09:14.580> to<00:09:14.700> empower<00:09:15.000> users<00:09:15.540> to<00:09:15.959> the 00:09:16.070 --> 00:09:16.080 align:start position:0% this new UI aims to empower users to the 00:09:16.080 --> 00:09:17.930 align:start position:0% this new UI aims to empower users to the final<00:09:16.260> allowance<00:09:16.800> that<00:09:17.160> they<00:09:17.399> want<00:09:17.580> to<00:09:17.700> give 00:09:17.930 --> 00:09:17.940 align:start position:0% final allowance that they want to give 00:09:17.940 --> 00:09:21.889 align:start position:0% final allowance that they want to give to<00:09:18.300> the<00:09:18.480> lab<00:09:18.660> we<00:09:19.620> split<00:09:20.100> the<00:09:20.220> flow<00:09:20.459> into<00:09:20.720> we<00:09:21.720> now 00:09:21.889 --> 00:09:21.899 align:start position:0% to the lab we split the flow into we now 00:09:21.899 --> 00:09:25.370 align:start position:0% to the lab we split the flow into we now have<00:09:22.260> gas<00:09:22.860> fees<00:09:23.399> in<00:09:23.700> the<00:09:23.820> second<00:09:24.000> screen<00:09:24.420> which 00:09:25.370 --> 00:09:25.380 align:start position:0% have gas fees in the second screen which 00:09:25.380 --> 00:09:28.370 align:start position:0% have gas fees in the second screen which was<00:09:25.560> something<00:09:25.860> that<00:09:26.220> people<00:09:26.459> was<00:09:26.880> looking 00:09:28.370 --> 00:09:28.380 align:start position:0% was something that people was looking 00:09:28.380 --> 00:09:32.449 align:start position:0% was something that people was looking um<00:09:28.440> too<00:09:29.160> much<00:09:29.339> on<00:09:30.060> the<00:09:30.540> first<00:09:30.720> version<00:09:31.279> and<00:09:32.279> now 00:09:32.449 --> 00:09:32.459 align:start position:0% um too much on the first version and now 00:09:32.459 --> 00:09:36.590 align:start position:0% um too much on the first version and now we<00:09:32.820> have<00:09:33.000> a<00:09:33.660> specifically<00:09:34.260> who<00:09:35.160> actors<00:09:35.940> are 00:09:36.590 --> 00:09:36.600 align:start position:0% we have a specifically who actors are 00:09:36.600 --> 00:09:38.810 align:start position:0% we have a specifically who actors are interacting<00:09:37.260> in<00:09:37.560> this<00:09:37.740> transaction<00:09:38.100> we<00:09:38.640> are 00:09:38.810 --> 00:09:38.820 align:start position:0% interacting in this transaction we are 00:09:38.820 --> 00:09:43.630 align:start position:0% interacting in this transaction we are allow<00:09:39.120> users<00:09:39.740> to<00:09:40.740> verify<00:09:41.640> contracts 00:09:43.630 --> 00:09:43.640 align:start position:0% allow users to verify contracts 00:09:43.640 --> 00:09:48.350 align:start position:0% allow users to verify contracts we<00:09:44.640> are<00:09:44.820> making<00:09:45.440> explicit<00:09:46.440> which<00:09:47.399> assets<00:09:48.000> are 00:09:48.350 --> 00:09:48.360 align:start position:0% we are making explicit which assets are 00:09:48.360 --> 00:09:51.050 align:start position:0% we are making explicit which assets are being<00:09:48.600> transferred<00:09:49.320> we<00:09:49.860> are<00:09:50.040> adding<00:09:50.519> friction 00:09:51.050 --> 00:09:51.060 align:start position:0% being transferred we are adding friction 00:09:51.060 --> 00:09:54.050 align:start position:0% being transferred we are adding friction to<00:09:51.660> warn<00:09:52.140> users<00:09:52.500> when 00:09:54.050 --> 00:09:54.060 align:start position:0% to warn users when 00:09:54.060 --> 00:09:56.630 align:start position:0% to warn users when the<00:09:54.660> site<00:09:54.839> is<00:09:55.140> requesting 00:09:56.630 --> 00:09:56.640 align:start position:0% the site is requesting 00:09:56.640 --> 00:09:59.570 align:start position:0% the site is requesting um<00:09:56.700> the<00:09:57.060> entire<00:09:57.360> collections<00:09:58.019> on<00:09:58.260> a<00:09:58.380> MSC<00:09:59.040> to<00:09:59.459> be 00:09:59.570 --> 00:09:59.580 align:start position:0% um the entire collections on a MSC to be 00:09:59.580 --> 00:10:02.810 align:start position:0% um the entire collections on a MSC to be transferred<00:10:00.720> users<00:10:01.440> can<00:10:01.680> yeah<00:10:02.160> I<00:10:02.459> say<00:10:02.580> that 00:10:02.810 --> 00:10:02.820 align:start position:0% transferred users can yeah I say that 00:10:02.820 --> 00:10:05.930 align:start position:0% transferred users can yeah I say that before<00:10:03.060> can<00:10:03.480> verify<00:10:03.959> contract<00:10:04.560> details 00:10:05.930 --> 00:10:05.940 align:start position:0% before can verify contract details 00:10:05.940 --> 00:10:11.210 align:start position:0% before can verify contract details and<00:10:06.839> more<00:10:07.440> things<00:10:08.120> echo<00:10:09.120> in<00:10:09.300> on<00:10:09.800> what<00:10:10.800> Taylor 00:10:11.210 --> 00:10:11.220 align:start position:0% and more things echo in on what Taylor 00:10:11.220 --> 00:10:14.210 align:start position:0% and more things echo in on what Taylor said<00:10:11.700> this<00:10:12.120> week<00:10:12.300> we<00:10:13.140> should<00:10:13.320> be<00:10:13.500> responsible 00:10:14.210 --> 00:10:14.220 align:start position:0% said this week we should be responsible 00:10:14.220 --> 00:10:17.090 align:start position:0% said this week we should be responsible of<00:10:15.060> what<00:10:15.300> technology<00:10:15.720> we<00:10:16.200> build 00:10:17.090 --> 00:10:17.100 align:start position:0% of what technology we build 00:10:17.100 --> 00:10:19.670 align:start position:0% of what technology we build we<00:10:17.640> should<00:10:17.880> be<00:10:18.060> there<00:10:18.300> which<00:10:18.839> will<00:10:19.080> technology 00:10:19.670 --> 00:10:19.680 align:start position:0% we should be there which will technology 00:10:19.680 --> 00:10:22.610 align:start position:0% we should be there which will technology that<00:10:20.640> we<00:10:20.880> expect<00:10:21.060> people 00:10:22.610 --> 00:10:22.620 align:start position:0% that we expect people 00:10:22.620 --> 00:10:25.850 align:start position:0% that we expect people as<00:10:23.160> developers<00:10:23.820> as<00:10:24.180> wallet<00:10:24.660> developers<00:10:25.260> we 00:10:25.850 --> 00:10:25.860 align:start position:0% as developers as wallet developers we 00:10:25.860 --> 00:10:28.610 align:start position:0% as developers as wallet developers we have<00:10:26.100> the<00:10:26.580> responsibility<00:10:27.360> of<00:10:28.200> critical 00:10:28.610 --> 00:10:28.620 align:start position:0% have the responsibility of critical 00:10:28.620 --> 00:10:31.730 align:start position:0% have the responsibility of critical thinking<00:10:29.220> about<00:10:29.519> how<00:10:30.060> to<00:10:30.240> expose<00:10:30.600> users<00:10:31.200> to 00:10:31.730 --> 00:10:31.740 align:start position:0% thinking about how to expose users to 00:10:31.740 --> 00:10:33.410 align:start position:0% thinking about how to expose users to give<00:10:31.980> consent 00:10:33.410 --> 00:10:33.420 align:start position:0% give consent 00:10:33.420 --> 00:10:37.250 align:start position:0% give consent to<00:10:34.380> a<00:10:34.560> decision<00:10:34.980> that<00:10:35.760> directly<00:10:36.180> affects<00:10:36.839> the 00:10:37.250 --> 00:10:37.260 align:start position:0% to a decision that directly affects the 00:10:37.260 --> 00:10:39.829 align:start position:0% to a decision that directly affects the digital<00:10:37.680> values 00:10:39.829 --> 00:10:39.839 align:start position:0% digital values 00:10:39.839 --> 00:10:43.269 align:start position:0% digital values and<00:10:40.440> these<00:10:40.760> allowed<00:10:41.760> us<00:10:41.940> to<00:10:42.540> explore 00:10:43.269 --> 00:10:43.279 align:start position:0% and these allowed us to explore 00:10:43.279 --> 00:10:47.329 align:start position:0% and these allowed us to explore opportunities<00:10:44.360> to<00:10:45.360> design<00:10:45.740> the<00:10:46.740> centralized 00:10:47.329 --> 00:10:47.339 align:start position:0% opportunities to design the centralized 00:10:47.339 --> 00:10:50.690 align:start position:0% opportunities to design the centralized technology<00:10:48.019> that<00:10:49.019> respects<00:10:49.620> people<00:10:49.920> but 00:10:50.690 --> 00:10:50.700 align:start position:0% technology that respects people but 00:10:50.700 --> 00:10:53.650 align:start position:0% technology that respects people but practicing<00:10:51.420> open<00:10:52.019> design<00:10:52.380> methodologies 00:10:53.650 --> 00:10:53.660 align:start position:0% practicing open design methodologies 00:10:53.660 --> 00:10:55.630 align:start position:0% practicing open design methodologies balancing<00:10:54.660> security 00:10:55.630 --> 00:10:55.640 align:start position:0% balancing security 00:10:55.640 --> 00:10:59.930 align:start position:0% balancing security and<00:10:56.640> usability<00:10:57.180> it's<00:10:57.839> complex<00:10:58.459> we<00:10:59.459> do<00:10:59.640> a<00:10:59.760> lot 00:10:59.930 --> 00:10:59.940 align:start position:0% and usability it's complex we do a lot 00:10:59.940 --> 00:11:02.269 align:start position:0% and usability it's complex we do a lot of<00:11:00.060> complex<00:11:00.660> things<00:11:01.140> here 00:11:02.269 --> 00:11:02.279 align:start position:0% of complex things here 00:11:02.279 --> 00:11:04.569 align:start position:0% of complex things here these<00:11:03.000> requires 00:11:04.569 --> 00:11:04.579 align:start position:0% these requires 00:11:04.579 --> 00:11:07.910 align:start position:0% these requires inadequate<00:11:05.579> thread<00:11:06.360> modeling<00:11:06.920> the 00:11:07.910 --> 00:11:07.920 align:start position:0% inadequate thread modeling the 00:11:07.920 --> 00:11:10.370 align:start position:0% inadequate thread modeling the possibility<00:11:08.399> of<00:11:08.760> including<00:11:09.300> people<00:11:09.600> in<00:11:10.200> your 00:11:10.370 --> 00:11:10.380 align:start position:0% possibility of including people in your 00:11:10.380 --> 00:11:11.490 align:start position:0% possibility of including people in your development<00:11:10.860> process 00:11:11.490 --> 00:11:11.500 align:start position:0% development process 00:11:11.500 --> 00:11:12.769 align:start position:0% development process [Music] 00:11:12.769 --> 00:11:12.779 align:start position:0% [Music] 00:11:12.779 --> 00:11:16.430 align:start position:0% [Music] and<00:11:13.620> trying<00:11:14.160> to<00:11:14.399> understand<00:11:14.959> people's<00:11:15.959> mental 00:11:16.430 --> 00:11:16.440 align:start position:0% and trying to understand people's mental 00:11:16.440 --> 00:11:20.150 align:start position:0% and trying to understand people's mental models<00:11:17.040> too<00:11:17.700> much<00:11:17.940> with<00:11:18.600> the<00:11:18.839> flows<00:11:19.320> that<00:11:19.920> we 00:11:20.150 --> 00:11:20.160 align:start position:0% models too much with the flows that we 00:11:20.160 --> 00:11:23.509 align:start position:0% models too much with the flows that we propose<00:11:20.579> as<00:11:21.300> a<00:11:21.540> facilitator<00:11:22.260> of<00:11:22.920> consensual 00:11:23.509 --> 00:11:23.519 align:start position:0% propose as a facilitator of consensual 00:11:23.519 --> 00:11:26.030 align:start position:0% propose as a facilitator of consensual transactions<00:11:24.360> we<00:11:24.779> are<00:11:24.899> trying<00:11:25.260> to<00:11:25.560> generate 00:11:26.030 --> 00:11:26.040 align:start position:0% transactions we are trying to generate 00:11:26.040 --> 00:11:30.470 align:start position:0% transactions we are trying to generate more<00:11:26.940> Open<00:11:27.600> Spaces<00:11:28.440> to<00:11:28.800> discuss<00:11:29.120> ESL<00:11:30.120> Security 00:11:30.470 --> 00:11:30.480 align:start position:0% more Open Spaces to discuss ESL Security 00:11:30.480 --> 00:11:34.490 align:start position:0% more Open Spaces to discuss ESL Security in<00:11:31.380> the<00:11:31.560> decentralized<00:11:32.399> circle 00:11:34.490 --> 00:11:34.500 align:start position:0% in the decentralized circle 00:11:34.500 --> 00:11:36.949 align:start position:0% in the decentralized circle if<00:11:35.100> you<00:11:35.279> are<00:11:35.459> a<00:11:35.579> product<00:11:35.820> if<00:11:36.600> you<00:11:36.779> are<00:11:36.899> a 00:11:36.949 --> 00:11:36.959 align:start position:0% if you are a product if you are a 00:11:36.959 --> 00:11:40.009 align:start position:0% if you are a product if you are a designer<00:11:37.560> if<00:11:37.980> you<00:11:38.100> resonate<00:11:38.640> with<00:11:38.880> this<00:11:39.180> you 00:11:40.009 --> 00:11:40.019 align:start position:0% designer if you resonate with this you 00:11:40.019 --> 00:11:42.170 align:start position:0% designer if you resonate with this you can<00:11:40.140> find<00:11:40.440> me<00:11:40.620> I<00:11:41.100> will<00:11:41.279> be<00:11:41.399> happy<00:11:41.640> to<00:11:42.000> talk 00:11:42.170 --> 00:11:42.180 align:start position:0% can find me I will be happy to talk 00:11:42.180 --> 00:11:44.889 align:start position:0% can find me I will be happy to talk about<00:11:42.360> this<00:11:42.980> if<00:11:43.980> you<00:11:44.160> are<00:11:44.399> a<00:11:44.519> security 00:11:44.889 --> 00:11:44.899 align:start position:0% about this if you are a security 00:11:44.899 --> 00:11:48.050 align:start position:0% about this if you are a security researcher<00:11:45.899> if<00:11:46.440> you<00:11:46.620> are<00:11:46.740> a<00:11:46.920> hacker 00:11:48.050 --> 00:11:48.060 align:start position:0% researcher if you are a hacker 00:11:48.060 --> 00:11:52.310 align:start position:0% researcher if you are a hacker if<00:11:48.839> you<00:11:48.959> want<00:11:49.140> to<00:11:49.260> punch<00:11:49.620> our<00:11:50.100> services<00:11:51.019> we<00:11:52.019> and 00:11:52.310 --> 00:11:52.320 align:start position:0% if you want to punch our services we and 00:11:52.320 --> 00:11:54.710 align:start position:0% if you want to punch our services we and get<00:11:52.560> money<00:11:52.860> we<00:11:53.579> have<00:11:53.760> a<00:11:53.940> hacker<00:11:54.300> one<00:11:54.480> program 00:11:54.710 --> 00:11:54.720 align:start position:0% get money we have a hacker one program 00:11:54.720 --> 00:11:59.269 align:start position:0% get money we have a hacker one program in<00:11:55.140> place<00:11:55.640> hackerrone.com<00:11:57.079> metamask<00:11:58.100> if<00:11:59.100> you 00:11:59.269 --> 00:11:59.279 align:start position:0% in place hackerrone.com metamask if you 00:11:59.279 --> 00:12:01.970 align:start position:0% in place hackerrone.com metamask if you are<00:11:59.399> a<00:11:59.519> developer<00:12:00.060> and<00:12:00.839> you<00:12:01.019> have<00:12:01.200> ideas<00:12:01.500> on 00:12:01.970 --> 00:12:01.980 align:start position:0% are a developer and you have ideas on 00:12:01.980 --> 00:12:04.130 align:start position:0% are a developer and you have ideas on how<00:12:02.279> to<00:12:02.459> improve<00:12:02.880> metamask<00:12:03.540> you<00:12:03.899> want<00:12:04.019> to 00:12:04.130 --> 00:12:04.140 align:start position:0% how to improve metamask you want to 00:12:04.140 --> 00:12:07.130 align:start position:0% how to improve metamask you want to extend<00:12:04.680> it<00:12:04.980> you<00:12:05.579> want<00:12:05.700> to<00:12:05.880> connect<00:12:06.180> your<00:12:06.600> API 00:12:07.130 --> 00:12:07.140 align:start position:0% extend it you want to connect your API 00:12:07.140 --> 00:12:11.449 align:start position:0% extend it you want to connect your API to<00:12:07.440> metamaski<00:12:08.540> expose<00:12:09.540> in<00:12:09.779> a<00:12:09.899> metamask<00:12:10.320> UI<00:12:10.740> you 00:12:11.449 --> 00:12:11.459 align:start position:0% to metamaski expose in a metamask UI you 00:12:11.459 --> 00:12:14.030 align:start position:0% to metamaski expose in a metamask UI you should<00:12:11.640> check<00:12:12.000> out<00:12:12.180> meta<00:12:12.720> multiply<00:12:13.140> IO<00:12:13.500> slash 00:12:14.030 --> 00:12:14.040 align:start position:0% should check out meta multiply IO slash 00:12:14.040 --> 00:12:18.350 align:start position:0% should check out meta multiply IO slash snaps<00:12:14.880> and<00:12:15.600> edit<00:12:16.140> stocks<00:12:16.620> from<00:12:16.980> yesterday<00:12:17.360> I 00:12:18.350 --> 00:12:18.360 align:start position:0% snaps and edit stocks from yesterday I 00:12:18.360 --> 00:12:20.930 align:start position:0% snaps and edit stocks from yesterday I personally<00:12:18.720> believe<00:12:19.200> that<00:12:19.800> there<00:12:20.459> is<00:12:20.640> a<00:12:20.820> long 00:12:20.930 --> 00:12:20.940 align:start position:0% personally believe that there is a long 00:12:20.940 --> 00:12:24.970 align:start position:0% personally believe that there is a long way<00:12:21.240> to<00:12:21.959> go<00:12:22.200> to<00:12:22.800> rethink<00:12:23.279> how<00:12:23.940> the<00:12:24.600> information 00:12:24.970 --> 00:12:24.980 align:start position:0% way to go to rethink how the information 00:12:24.980 --> 00:12:27.650 align:start position:0% way to go to rethink how the information systems<00:12:25.980> to<00:12:26.100> which<00:12:26.339> we<00:12:26.579> delegate<00:12:27.240> trust 00:12:27.650 --> 00:12:27.660 align:start position:0% systems to which we delegate trust 00:12:27.660 --> 00:12:30.710 align:start position:0% systems to which we delegate trust interact<00:12:28.620> with<00:12:29.100> consent 00:12:30.710 --> 00:12:30.720 align:start position:0% interact with consent 00:12:30.720 --> 00:12:33.949 align:start position:0% interact with consent this<00:12:31.380> is<00:12:31.500> an<00:12:31.680> open<00:12:31.920> call<00:12:32.279> and<00:12:32.940> I<00:12:33.120> invite<00:12:33.480> you<00:12:33.660> to 00:12:33.949 --> 00:12:33.959 align:start position:0% this is an open call and I invite you to 00:12:33.959 --> 00:12:35.750 align:start position:0% this is an open call and I invite you to think<00:12:34.079> about<00:12:34.260> that<00:12:34.560> with<00:12:34.860> me 00:12:35.750 --> 00:12:35.760 align:start position:0% think about that with me 00:12:35.760 --> 00:12:38.750 align:start position:0% think about that with me thank<00:12:36.300> you<00:12:36.420> very<00:12:36.540> much<00:12:36.720> Antonella<00:12:37.620> and<00:12:38.459> we 00:12:38.750 --> 00:12:38.760 align:start position:0% thank you very much Antonella and we 00:12:38.760 --> 00:12:41.509 align:start position:0% thank you very much Antonella and we have<00:12:39.000> several<00:12:39.839> hands<00:12:40.440> up<00:12:40.560> we<00:12:41.040> are<00:12:41.220> going<00:12:41.399> to 00:12:41.509 --> 00:12:41.519 align:start position:0% have several hands up we are going to 00:12:41.519 --> 00:12:44.750 align:start position:0% have several hands up we are going to start<00:12:41.880> here<00:12:42.240> but<00:12:42.540> we<00:12:42.839> have<00:12:43.079> to<00:12:43.620> there<00:12:44.040> oh<00:12:44.339> we 00:12:44.750 --> 00:12:44.760 align:start position:0% start here but we have to there oh we 00:12:44.760 --> 00:12:47.750 align:start position:0% start here but we have to there oh we have<00:12:44.880> a<00:12:45.000> lot<00:12:45.120> of<00:12:45.240> questions<00:12:45.480> Anthony<00:12:46.019> hi<00:12:46.860> uh 00:12:47.750 --> 00:12:47.760 align:start position:0% have a lot of questions Anthony hi uh 00:12:47.760 --> 00:12:50.210 align:start position:0% have a lot of questions Anthony hi uh super<00:12:48.000> presentation<00:12:48.540> thank<00:12:48.959> you<00:12:49.139> a<00:12:49.980> quick 00:12:50.210 --> 00:12:50.220 align:start position:0% super presentation thank you a quick 00:12:50.220 --> 00:12:53.210 align:start position:0% super presentation thank you a quick question<00:12:50.459> the<00:12:51.360> UI<00:12:51.839> that<00:12:52.139> you<00:12:52.260> presented<00:12:52.740> is 00:12:53.210 --> 00:12:53.220 align:start position:0% question the UI that you presented is 00:12:53.220 --> 00:12:54.590 align:start position:0% question the UI that you presented is there<00:12:53.459> is<00:12:53.579> a<00:12:53.700> date<00:12:53.820> when<00:12:54.060> they're<00:12:54.240> going<00:12:54.360> to<00:12:54.540> be 00:12:54.590 --> 00:12:54.600 align:start position:0% there is a date when they're going to be 00:12:54.600 --> 00:12:56.290 align:start position:0% there is a date when they're going to be released 00:12:56.290 --> 00:12:56.300 align:start position:0% released 00:12:56.300 --> 00:13:00.470 align:start position:0% released we<00:12:57.300> are<00:12:57.600> working<00:12:57.959> on<00:12:58.320> that<00:12:58.700> uh<00:12:59.700> later<00:12:59.880> Quarter 00:13:00.470 --> 00:13:00.480 align:start position:0% we are working on that uh later Quarter 00:13:00.480 --> 00:13:05.030 align:start position:0% we are working on that uh later Quarter Two<00:13:00.720> quarter<00:13:01.440> four<00:13:01.620> uh<00:13:02.579> yes<00:13:03.480> yes 00:13:05.030 --> 00:13:05.040 align:start position:0% Two quarter four uh yes yes 00:13:05.040 --> 00:13:08.090 align:start position:0% Two quarter four uh yes yes you<00:13:05.700> can<00:13:06.000> we<00:13:06.660> work<00:13:06.959> in<00:13:07.139> an<00:13:07.320> open<00:13:07.500> environment 00:13:08.090 --> 00:13:08.100 align:start position:0% you can we work in an open environment 00:13:08.100 --> 00:13:10.670 align:start position:0% you can we work in an open environment we<00:13:08.519> have<00:13:08.639> a<00:13:08.820> GitHub<00:13:09.240> repository<00:13:09.959> so<00:13:10.320> you<00:13:10.560> can 00:13:10.670 --> 00:13:10.680 align:start position:0% we have a GitHub repository so you can 00:13:10.680 --> 00:13:11.810 align:start position:0% we have a GitHub repository so you can check<00:13:10.860> stuff 00:13:11.810 --> 00:13:11.820 align:start position:0% check stuff 00:13:11.820 --> 00:13:15.170 align:start position:0% check stuff next<00:13:12.420> question<00:13:12.660> we<00:13:13.440> have<00:13:13.620> some<00:13:14.160> one<00:13:14.519> two<00:13:14.880> and 00:13:15.170 --> 00:13:15.180 align:start position:0% next question we have some one two and 00:13:15.180 --> 00:13:16.430 align:start position:0% next question we have some one two and three 00:13:16.430 --> 00:13:16.440 align:start position:0% three 00:13:16.440 --> 00:13:18.769 align:start position:0% three hello<00:13:16.860> hello 00:13:18.769 --> 00:13:18.779 align:start position:0% hello hello 00:13:18.779 --> 00:13:21.050 align:start position:0% hello hello um<00:13:18.899> thanks<00:13:19.260> for<00:13:19.380> your<00:13:19.560> talk<00:13:19.820> uh<00:13:20.820> and<00:13:20.940> you 00:13:21.050 --> 00:13:21.060 align:start position:0% um thanks for your talk uh and you 00:13:21.060 --> 00:13:23.269 align:start position:0% um thanks for your talk uh and you presentation<00:13:21.480> is<00:13:21.660> told<00:13:21.899> that<00:13:22.260> as<00:13:23.040> a<00:13:23.160> security 00:13:23.269 --> 00:13:23.279 align:start position:0% presentation is told that as a security 00:13:23.279 --> 00:13:24.949 align:start position:0% presentation is told that as a security researcher<00:13:23.880> you<00:13:24.060> have<00:13:24.240> to<00:13:24.360> do<00:13:24.540> balance 00:13:24.949 --> 00:13:24.959 align:start position:0% researcher you have to do balance 00:13:24.959 --> 00:13:27.590 align:start position:0% researcher you have to do balance between<00:13:25.200> user<00:13:25.980> experience<00:13:26.339> and<00:13:26.519> security 00:13:27.590 --> 00:13:27.600 align:start position:0% between user experience and security 00:13:27.600 --> 00:13:30.829 align:start position:0% between user experience and security how<00:13:28.139> do<00:13:28.260> you<00:13:28.440> draw<00:13:28.620> the<00:13:28.920> line<00:13:29.220> of<00:13:29.760> saying<00:13:30.300> the 00:13:30.829 --> 00:13:30.839 align:start position:0% how do you draw the line of saying the 00:13:30.839 --> 00:13:33.650 align:start position:0% how do you draw the line of saying the issue<00:13:31.139> is<00:13:31.260> supposed<00:13:31.440> to<00:13:31.680> know<00:13:31.920> the<00:13:32.160> thing<00:13:32.660> uh 00:13:33.650 --> 00:13:33.660 align:start position:0% issue is supposed to know the thing uh 00:13:33.660 --> 00:13:37.069 align:start position:0% issue is supposed to know the thing uh and<00:13:34.019> I<00:13:34.260> have<00:13:34.440> to<00:13:34.680> teach<00:13:34.980> the<00:13:35.820> the<00:13:36.120> user<00:13:36.540> that 00:13:37.069 --> 00:13:37.079 align:start position:0% and I have to teach the the user that 00:13:37.079 --> 00:13:39.350 align:start position:0% and I have to teach the the user that did<00:13:37.260> you<00:13:37.440> think<00:13:37.620> that<00:13:37.800> happened<00:13:38.160> now<00:13:38.459> good 00:13:39.350 --> 00:13:39.360 align:start position:0% did you think that happened now good 00:13:39.360 --> 00:13:40.730 align:start position:0% did you think that happened now good question 00:13:40.730 --> 00:13:40.740 align:start position:0% question 00:13:40.740 --> 00:13:43.430 align:start position:0% question um<00:13:40.980> I<00:13:41.700> don't<00:13:41.760> think<00:13:41.940> we<00:13:42.300> are<00:13:42.480> here<00:13:42.779> to<00:13:43.200> teach 00:13:43.430 --> 00:13:43.440 align:start position:0% um I don't think we are here to teach 00:13:43.440 --> 00:13:46.850 align:start position:0% um I don't think we are here to teach users<00:13:44.300> I<00:13:45.300> think<00:13:45.480> we<00:13:45.720> are<00:13:45.899> here<00:13:46.139> to<00:13:46.440> inform 00:13:46.850 --> 00:13:46.860 align:start position:0% users I think we are here to inform 00:13:46.860 --> 00:13:50.569 align:start position:0% users I think we are here to inform people<00:13:47.459> to<00:13:47.880> make<00:13:48.120> informal<00:13:48.779> decisions<00:13:49.260> on<00:13:50.160> the 00:13:50.569 --> 00:13:50.579 align:start position:0% people to make informal decisions on the 00:13:50.579 --> 00:13:52.970 align:start position:0% people to make informal decisions on the balance<00:13:50.940> between<00:13:51.240> how<00:13:51.899> much<00:13:52.019> information<00:13:52.320> we 00:13:52.970 --> 00:13:52.980 align:start position:0% balance between how much information we 00:13:52.980 --> 00:13:55.850 align:start position:0% balance between how much information we show<00:13:53.220> in<00:13:53.459> our<00:13:53.700> screen<00:13:54.019> and<00:13:55.019> how<00:13:55.680> this 00:13:55.850 --> 00:13:55.860 align:start position:0% show in our screen and how this 00:13:55.860 --> 00:13:58.670 align:start position:0% show in our screen and how this information<00:13:56.180> resonates<00:13:57.180> with<00:13:57.420> people<00:13:57.779> and 00:13:58.670 --> 00:13:58.680 align:start position:0% information resonates with people and 00:13:58.680 --> 00:14:01.490 align:start position:0% information resonates with people and also<00:13:59.040> the<00:13:59.820> time<00:14:00.060> that<00:14:00.480> happens<00:14:00.779> between<00:14:01.139> the 00:14:01.490 --> 00:14:01.500 align:start position:0% also the time that happens between the 00:14:01.500 --> 00:14:04.430 align:start position:0% also the time that happens between the people<00:14:01.680> make<00:14:02.100> a<00:14:02.339> decision<00:14:02.700> and<00:14:03.300> read<00:14:03.540> may<00:14:04.139> vary 00:14:04.430 --> 00:14:04.440 align:start position:0% people make a decision and read may vary 00:14:04.440 --> 00:14:08.329 align:start position:0% people make a decision and read may vary and<00:14:05.100> change<00:14:05.420> I<00:14:06.420> think<00:14:06.600> that<00:14:06.899> is<00:14:07.200> the<00:14:07.860> most<00:14:07.980> fun 00:14:08.329 --> 00:14:08.339 align:start position:0% and change I think that is the most fun 00:14:08.339 --> 00:14:11.170 align:start position:0% and change I think that is the most fun part<00:14:08.700> finding<00:14:09.600> this<00:14:09.779> balance 00:14:11.170 --> 00:14:11.180 align:start position:0% part finding this balance 00:14:11.180 --> 00:14:14.210 align:start position:0% part finding this balance I<00:14:12.180> think<00:14:12.420> it's<00:14:12.600> super<00:14:12.839> important<00:14:13.320> also<00:14:13.800> to 00:14:14.210 --> 00:14:14.220 align:start position:0% I think it's super important also to 00:14:14.220 --> 00:14:16.850 align:start position:0% I think it's super important also to work<00:14:14.579> with<00:14:14.820> users<00:14:15.240> if<00:14:15.720> you<00:14:15.839> have<00:14:16.019> a<00:14:16.260> product<00:14:16.440> if 00:14:16.850 --> 00:14:16.860 align:start position:0% work with users if you have a product if 00:14:16.860 --> 00:14:19.810 align:start position:0% work with users if you have a product if you<00:14:17.040> are<00:14:17.279> building<00:14:17.459> a<00:14:17.820> pro<00:14:18.000> a<00:14:18.899> product 00:14:19.810 --> 00:14:19.820 align:start position:0% you are building a pro a product 00:14:19.820 --> 00:14:22.850 align:start position:0% you are building a pro a product whatever<00:14:20.820> you<00:14:21.779> should<00:14:21.899> have<00:14:22.079> users<00:14:22.500> in<00:14:22.680> your 00:14:22.850 --> 00:14:22.860 align:start position:0% whatever you should have users in your 00:14:22.860 --> 00:14:24.889 align:start position:0% whatever you should have users in your development<00:14:23.339> process<00:14:23.760> so<00:14:24.180> you<00:14:24.360> can<00:14:24.480> expose 00:14:24.889 --> 00:14:24.899 align:start position:0% development process so you can expose 00:14:24.899 --> 00:14:28.310 align:start position:0% development process so you can expose users<00:14:25.320> to<00:14:25.620> your<00:14:25.980> product<00:14:26.579> early<00:14:27.360> and<00:14:28.079> you<00:14:28.200> can 00:14:28.310 --> 00:14:28.320 align:start position:0% users to your product early and you can 00:14:28.320 --> 00:14:30.530 align:start position:0% users to your product early and you can get<00:14:28.500> feedback<00:14:29.040> and<00:14:29.579> that<00:14:29.760> it's<00:14:30.000> so<00:14:30.300> rich 00:14:30.530 --> 00:14:30.540 align:start position:0% get feedback and that it's so rich 00:14:30.540 --> 00:14:33.590 align:start position:0% get feedback and that it's so rich because<00:14:31.440> you<00:14:31.800> have<00:14:31.980> people<00:14:32.579> using<00:14:33.180> your<00:14:33.360> pro 00:14:33.590 --> 00:14:33.600 align:start position:0% because you have people using your pro 00:14:33.600 --> 00:14:37.430 align:start position:0% because you have people using your pro before<00:14:34.260> your<00:14:34.980> life<00:14:35.339> or<00:14:35.760> whatever<00:14:35.940> so<00:14:36.600> that'll 00:14:37.430 --> 00:14:37.440 align:start position:0% before your life or whatever so that'll 00:14:37.440 --> 00:14:40.189 align:start position:0% before your life or whatever so that'll answer<00:14:37.620> your<00:14:37.980> question<00:14:38.220> a<00:14:38.579> little<00:14:38.760> bit<00:14:39.199> there 00:14:40.189 --> 00:14:40.199 align:start position:0% answer your question a little bit there 00:14:40.199 --> 00:14:43.009 align:start position:0% answer your question a little bit there is<00:14:40.380> one<00:14:41.279> two<00:14:41.639> and<00:14:41.880> three<00:14:42.120> and<00:14:42.360> four<00:14:42.540> we<00:14:42.839> have 00:14:43.009 --> 00:14:43.019 align:start position:0% is one two and three and four we have 00:14:43.019 --> 00:14:45.769 align:start position:0% is one two and three and four we have time<00:14:43.260> okay<00:14:43.500> so<00:14:43.920> and<00:14:44.279> I<00:14:44.459> see<00:14:44.760> the<00:14:44.940> fifth<00:14:45.540> here 00:14:45.769 --> 00:14:45.779 align:start position:0% time okay so and I see the fifth here 00:14:45.779 --> 00:14:49.670 align:start position:0% time okay so and I see the fifth here please<00:14:46.760> thanks<00:14:47.760> great<00:14:48.600> talk<00:14:48.779> it's<00:14:49.260> part<00:14:49.560> of 00:14:49.670 --> 00:14:49.680 align:start position:0% please thanks great talk it's part of 00:14:49.680 --> 00:14:51.769 align:start position:0% please thanks great talk it's part of the<00:14:49.800> your<00:14:50.040> definition<00:14:50.279> of<00:14:50.699> consent<00:14:51.120> uh<00:14:51.660> you 00:14:51.769 --> 00:14:51.779 align:start position:0% the your definition of consent uh you 00:14:51.779 --> 00:14:56.210 align:start position:0% the your definition of consent uh you you<00:14:52.019> discussed<00:14:52.980> uh<00:14:53.160> revocable<00:14:53.959> and<00:14:54.959> uh<00:14:55.860> you 00:14:56.210 --> 00:14:56.220 align:start position:0% you discussed uh revocable and uh you 00:14:56.220 --> 00:14:59.269 align:start position:0% you discussed uh revocable and uh you know<00:14:56.339> where<00:14:56.699> does<00:14:56.880> metamask<00:14:57.660> or<00:14:57.899> the<00:14:58.139> ux<00:14:58.500> fall 00:14:59.269 --> 00:14:59.279 align:start position:0% know where does metamask or the ux fall 00:14:59.279 --> 00:15:01.670 align:start position:0% know where does metamask or the ux fall with<00:14:59.519> revocability<00:15:00.240> and<00:15:00.660> helping<00:15:01.320> the<00:15:01.440> user 00:15:01.670 --> 00:15:01.680 align:start position:0% with revocability and helping the user 00:15:01.680 --> 00:15:03.590 align:start position:0% with revocability and helping the user know<00:15:01.860> that<00:15:02.040> they<00:15:02.160> can<00:15:02.279> revoke<00:15:02.639> or<00:15:02.880> what<00:15:03.120> what 00:15:03.590 --> 00:15:03.600 align:start position:0% know that they can revoke or what what 00:15:03.600 --> 00:15:04.870 align:start position:0% know that they can revoke or what what they've<00:15:03.839> given<00:15:03.959> consent<00:15:04.320> to<00:15:04.440> in<00:15:04.620> the<00:15:04.740> past 00:15:04.870 --> 00:15:04.880 align:start position:0% they've given consent to in the past 00:15:04.880 --> 00:15:08.150 align:start position:0% they've given consent to in the past beautiful<00:15:05.880> it's<00:15:06.540> a<00:15:06.720> protocol<00:15:06.959> issue<00:15:07.680> it's<00:15:07.980> not 00:15:08.150 --> 00:15:08.160 align:start position:0% beautiful it's a protocol issue it's not 00:15:08.160 --> 00:15:11.449 align:start position:0% beautiful it's a protocol issue it's not our<00:15:08.399> problem<00:15:09.060> now<00:15:09.680> we<00:15:10.680> should<00:15:10.920> work<00:15:11.160> together 00:15:11.449 --> 00:15:11.459 align:start position:0% our problem now we should work together 00:15:11.459 --> 00:15:14.449 align:start position:0% our problem now we should work together on<00:15:12.060> protocol<00:15:12.480> level<00:15:12.839> to<00:15:13.320> make<00:15:13.500> sure 00:15:14.449 --> 00:15:14.459 align:start position:0% on protocol level to make sure 00:15:14.459 --> 00:15:17.389 align:start position:0% on protocol level to make sure that<00:15:15.300> I<00:15:15.839> mean<00:15:15.959> to<00:15:16.380> comprehend<00:15:16.800> that<00:15:17.040> we<00:15:17.220> are 00:15:17.389 --> 00:15:17.399 align:start position:0% that I mean to comprehend that we are 00:15:17.399 --> 00:15:21.350 align:start position:0% that I mean to comprehend that we are human<00:15:17.699> and<00:15:18.360> we<00:15:18.540> can<00:15:18.660> make<00:15:18.899> mistakes<00:15:19.500> and 00:15:21.350 --> 00:15:21.360 align:start position:0% human and we can make mistakes and 00:15:21.360 --> 00:15:23.870 align:start position:0% human and we can make mistakes and I<00:15:21.899> know<00:15:22.079> that<00:15:22.260> Rick<00:15:22.500> vocability<00:15:23.100> is<00:15:23.459> like<00:15:23.699> a 00:15:23.870 --> 00:15:23.880 align:start position:0% I know that Rick vocability is like a 00:15:23.880 --> 00:15:26.530 align:start position:0% I know that Rick vocability is like a Hot<00:15:24.180> Topic<00:15:24.839> in<00:15:25.199> this<00:15:25.440> space 00:15:26.530 --> 00:15:26.540 align:start position:0% Hot Topic in this space 00:15:26.540 --> 00:15:29.449 align:start position:0% Hot Topic in this space there<00:15:27.540> are<00:15:27.720> a<00:15:27.839> lot<00:15:27.899> of<00:15:28.079> ideas<00:15:28.320> on<00:15:28.860> how<00:15:29.160> to<00:15:29.279> make 00:15:29.449 --> 00:15:29.459 align:start position:0% there are a lot of ideas on how to make 00:15:29.459 --> 00:15:33.050 align:start position:0% there are a lot of ideas on how to make transactions<00:15:30.240> revocable<00:15:30.899> you<00:15:31.740> can<00:15:31.980> do<00:15:32.699> things 00:15:33.050 --> 00:15:33.060 align:start position:0% transactions revocable you can do things 00:15:33.060 --> 00:15:36.470 align:start position:0% transactions revocable you can do things like<00:15:33.540> I<00:15:34.079> don't<00:15:34.199> know<00:15:34.699> having<00:15:35.699> a<00:15:36.000> space<00:15:36.240> of 00:15:36.470 --> 00:15:36.480 align:start position:0% like I don't know having a space of 00:15:36.480 --> 00:15:38.629 align:start position:0% like I don't know having a space of nouns<00:15:37.019> in<00:15:37.199> the<00:15:37.380> middle<00:15:37.500> and<00:15:38.100> you<00:15:38.399> have<00:15:38.519> a 00:15:38.629 --> 00:15:38.639 align:start position:0% nouns in the middle and you have a 00:15:38.639 --> 00:15:40.610 align:start position:0% nouns in the middle and you have a certain<00:15:38.760> time<00:15:39.180> that<00:15:39.480> you<00:15:39.600> can<00:15:39.720> revoke<00:15:40.260> and 00:15:40.610 --> 00:15:40.620 align:start position:0% certain time that you can revoke and 00:15:40.620 --> 00:15:42.769 align:start position:0% certain time that you can revoke and stuff<00:15:40.860> they<00:15:41.399> are<00:15:41.639> smart<00:15:41.940> people<00:15:42.240> thinking 00:15:42.769 --> 00:15:42.779 align:start position:0% stuff they are smart people thinking 00:15:42.779 --> 00:15:44.269 align:start position:0% stuff they are smart people thinking about<00:15:43.019> that 00:15:44.269 --> 00:15:44.279 align:start position:0% about that 00:15:44.279 --> 00:15:47.870 align:start position:0% about that um<00:15:44.579> but<00:15:45.180> yeah<00:15:45.420> it's<00:15:45.899> it's<00:15:46.260> an<00:15:46.500> open<00:15:46.620> question 00:15:47.870 --> 00:15:47.880 align:start position:0% um but yeah it's it's an open question 00:15:47.880 --> 00:15:52.269 align:start position:0% um but yeah it's it's an open question hi<00:15:48.720> great<00:15:49.079> and<00:15:49.980> great<00:15:50.399> work<00:15:50.579> using<00:15:51.120> is<00:15:51.360> consent 00:15:52.269 --> 00:15:52.279 align:start position:0% hi great and great work using is consent 00:15:52.279 --> 00:15:55.069 align:start position:0% hi great and great work using is consent how<00:15:53.279> do<00:15:53.399> you<00:15:53.579> think<00:15:53.760> two<00:15:54.120> is<00:15:54.360> possible<00:15:54.720> to 00:15:55.069 --> 00:15:55.079 align:start position:0% how do you think two is possible to 00:15:55.079 --> 00:15:58.009 align:start position:0% how do you think two is possible to handle<00:15:55.500> a<00:15:56.399> psychnic<00:15:57.180> message<00:15:57.420> concern 00:15:58.009 --> 00:15:58.019 align:start position:0% handle a psychnic message concern 00:15:58.019 --> 00:16:00.650 align:start position:0% handle a psychnic message concern specifically<00:15:58.800> when<00:15:59.579> we<00:15:59.880> sign<00:16:00.300> some 00:16:00.650 --> 00:16:00.660 align:start position:0% specifically when we sign some 00:16:00.660 --> 00:16:03.650 align:start position:0% specifically when we sign some structured<00:16:01.320> information<00:16:01.560> on<00:16:02.279> metamask<00:16:02.760> you 00:16:03.650 --> 00:16:03.660 align:start position:0% structured information on metamask you 00:16:03.660 --> 00:16:07.550 align:start position:0% structured information on metamask you will<00:16:03.839> see<00:16:04.339> an<00:16:05.339> adjacent<00:16:06.060> that<00:16:06.899> is<00:16:07.019> really<00:16:07.320> hard 00:16:07.550 --> 00:16:07.560 align:start position:0% will see an adjacent that is really hard 00:16:07.560 --> 00:16:10.310 align:start position:0% will see an adjacent that is really hard to<00:16:07.800> understand<00:16:08.360> and<00:16:09.360> there's<00:16:09.600> been<00:16:09.959> a<00:16:10.139> lot<00:16:10.199> of 00:16:10.310 --> 00:16:10.320 align:start position:0% to understand and there's been a lot of 00:16:10.320 --> 00:16:15.170 align:start position:0% to understand and there's been a lot of hacks<00:16:10.800> lately<00:16:11.600> based<00:16:12.600> on<00:16:12.980> on<00:16:13.980> our<00:16:14.339> erc20 00:16:15.170 --> 00:16:15.180 align:start position:0% hacks lately based on on our erc20 00:16:15.180 --> 00:16:18.230 align:start position:0% hacks lately based on on our erc20 tokens<00:16:15.779> able<00:16:16.380> to<00:16:16.500> permit<00:16:16.980> user<00:16:17.880> to<00:16:18.060> sign 00:16:18.230 --> 00:16:18.240 align:start position:0% tokens able to permit user to sign 00:16:18.240 --> 00:16:19.610 align:start position:0% tokens able to permit user to sign message<00:16:18.480> in<00:16:18.839> order<00:16:18.959> to<00:16:19.199> allow<00:16:19.500> for 00:16:19.610 --> 00:16:19.620 align:start position:0% message in order to allow for 00:16:19.620 --> 00:16:22.069 align:start position:0% message in order to allow for transactions<00:16:20.279> so<00:16:20.820> it's<00:16:21.180> very<00:16:21.360> hard<00:16:21.660> for<00:16:21.899> a 00:16:22.069 --> 00:16:22.079 align:start position:0% transactions so it's very hard for a 00:16:22.079 --> 00:16:25.610 align:start position:0% transactions so it's very hard for a user<00:16:22.380> to<00:16:22.800> know<00:16:22.980> if<00:16:23.399> you're<00:16:23.720> approving<00:16:24.720> uh 00:16:25.610 --> 00:16:25.620 align:start position:0% user to know if you're approving uh 00:16:25.620 --> 00:16:26.889 align:start position:0% user to know if you're approving uh genosis 00:16:26.889 --> 00:16:26.899 align:start position:0% genosis 00:16:26.899 --> 00:16:30.650 align:start position:0% genosis multiple<00:16:27.899> or<00:16:28.800> giving<00:16:29.220> permission<00:16:29.760> to<00:16:30.540> someone 00:16:30.650 --> 00:16:30.660 align:start position:0% multiple or giving permission to someone 00:16:30.660 --> 00:16:33.530 align:start position:0% multiple or giving permission to someone to<00:16:31.079> spend<00:16:31.440> your<00:16:31.920> tokens<00:16:32.339> on<00:16:33.000> your<00:16:33.120> big<00:16:33.360> house 00:16:33.530 --> 00:16:33.540 align:start position:0% to spend your tokens on your big house 00:16:33.540 --> 00:16:37.509 align:start position:0% to spend your tokens on your big house have<00:16:34.199> you<00:16:34.560> thinking<00:16:35.220> any<00:16:36.120> kind<00:16:36.300> of<00:16:36.480> mitigation 00:16:37.509 --> 00:16:37.519 align:start position:0% have you thinking any kind of mitigation 00:16:37.519 --> 00:16:40.509 align:start position:0% have you thinking any kind of mitigation for<00:16:38.519> this<00:16:38.639> problem<00:16:38.820> on<00:16:39.060> metamask 00:16:40.509 --> 00:16:40.519 align:start position:0% for this problem on metamask 00:16:40.519 --> 00:16:44.930 align:start position:0% for this problem on metamask there<00:16:41.519> are<00:16:41.699> a<00:16:42.240> lot<00:16:42.420> of<00:16:42.600> initiatives<00:16:43.639> they<00:16:44.639> want 00:16:44.930 --> 00:16:44.940 align:start position:0% there are a lot of initiatives they want 00:16:44.940 --> 00:16:48.610 align:start position:0% there are a lot of initiatives they want to<00:16:45.240> make<00:16:45.480> transactions<00:16:46.320> readable<00:16:47.000> they<00:16:48.000> are 00:16:48.610 --> 00:16:48.620 align:start position:0% to make transactions readable they are 00:16:48.620 --> 00:16:51.650 align:start position:0% to make transactions readable they are you<00:16:49.620> know<00:16:49.800> I<00:16:50.100> mean<00:16:50.220> I<00:16:50.519> remember<00:16:50.699> five<00:16:51.180> right 00:16:51.650 --> 00:16:51.660 align:start position:0% you know I mean I remember five right 00:16:51.660 --> 00:16:53.449 align:start position:0% you know I mean I remember five right now<00:16:51.779> but<00:16:52.320> there's<00:16:52.560> a<00:16:52.800> lot<00:16:52.860> of<00:16:52.980> people<00:16:53.160> working 00:16:53.449 --> 00:16:53.459 align:start position:0% now but there's a lot of people working 00:16:53.459 --> 00:16:57.410 align:start position:0% now but there's a lot of people working on<00:16:53.820> that<00:16:54.000> I<00:16:54.959> think<00:16:55.139> it's<00:16:55.680> the<00:16:56.519> next<00:16:56.699> step<00:16:57.000> for 00:16:57.410 --> 00:16:57.420 align:start position:0% on that I think it's the next step for 00:16:57.420 --> 00:16:59.569 align:start position:0% on that I think it's the next step for big<00:16:57.660> adoption<00:16:58.320> should<00:16:59.100> we<00:16:59.279> having 00:16:59.569 --> 00:16:59.579 align:start position:0% big adoption should we having 00:16:59.579 --> 00:17:03.530 align:start position:0% big adoption should we having transactions<00:17:00.420> in<00:17:00.660> every<00:17:00.779> double<00:17:01.079> Manner<00:17:01.620> and 00:17:03.530 --> 00:17:03.540 align:start position:0% transactions in every double Manner and 00:17:03.540 --> 00:17:06.770 align:start position:0% transactions in every double Manner and I<00:17:04.260> seek<00:17:04.620> companies<00:17:05.459> making<00:17:06.299> their<00:17:06.600> own 00:17:06.770 --> 00:17:06.780 align:start position:0% I seek companies making their own 00:17:06.780 --> 00:17:10.789 align:start position:0% I seek companies making their own versions<00:17:07.260> of<00:17:07.500> this<00:17:07.860> we<00:17:08.640> should<00:17:08.880> aim<00:17:09.360> to<00:17:09.959> have<00:17:10.199> a 00:17:10.789 --> 00:17:10.799 align:start position:0% versions of this we should aim to have a 00:17:10.799 --> 00:17:13.730 align:start position:0% versions of this we should aim to have a community<00:17:10.980> level<00:17:11.600> consensus<00:17:12.600> on<00:17:13.140> how<00:17:13.380> we<00:17:13.620> are 00:17:13.730 --> 00:17:13.740 align:start position:0% community level consensus on how we are 00:17:13.740 --> 00:17:15.710 align:start position:0% community level consensus on how we are going<00:17:13.919> to<00:17:14.100> expose<00:17:14.520> these<00:17:14.880> two<00:17:15.000> users<00:17:15.360> I<00:17:15.600> think 00:17:15.710 --> 00:17:15.720 align:start position:0% going to expose these two users I think 00:17:15.720 --> 00:17:19.010 align:start position:0% going to expose these two users I think it's<00:17:15.959> like<00:17:16.199> it's<00:17:16.980> more<00:17:17.220> powerful<00:17:17.880> if<00:17:18.660> we<00:17:18.839> were 00:17:19.010 --> 00:17:19.020 align:start position:0% it's like it's more powerful if we were 00:17:19.020 --> 00:17:22.850 align:start position:0% it's like it's more powerful if we were all<00:17:19.260> together<00:17:19.819> then<00:17:20.819> if<00:17:21.419> a<00:17:21.600> company<00:17:21.839> says<00:17:22.620> that 00:17:22.850 --> 00:17:22.860 align:start position:0% all together then if a company says that 00:17:22.860 --> 00:17:24.110 align:start position:0% all together then if a company says that they<00:17:23.100> are<00:17:23.220> doing 00:17:24.110 --> 00:17:24.120 align:start position:0% they are doing 00:17:24.120 --> 00:17:27.289 align:start position:0% they are doing clear<00:17:24.959> singing<00:17:25.679> or<00:17:25.919> something<00:17:26.160> like<00:17:26.520> that<00:17:26.699> so 00:17:27.289 --> 00:17:27.299 align:start position:0% clear singing or something like that so 00:17:27.299 --> 00:17:28.429 align:start position:0% clear singing or something like that so yeah 00:17:28.429 --> 00:17:28.439 align:start position:0% yeah 00:17:28.439 --> 00:17:31.850 align:start position:0% yeah I<00:17:29.100> think<00:17:29.220> it's<00:17:29.580> a<00:17:29.700> work<00:17:29.880> in<00:17:30.059> progress<00:17:30.480> and<00:17:31.440> I 00:17:31.850 --> 00:17:31.860 align:start position:0% I think it's a work in progress and I 00:17:31.860 --> 00:17:34.070 align:start position:0% I think it's a work in progress and I hope<00:17:32.040> you<00:17:32.340> are<00:17:32.520> willing<00:17:32.880> also<00:17:33.240> a<00:17:33.360> solution<00:17:33.720> for 00:17:34.070 --> 00:17:34.080 align:start position:0% hope you are willing also a solution for 00:17:34.080 --> 00:17:36.950 align:start position:0% hope you are willing also a solution for transactions<00:17:34.919> uh<00:17:35.580> to<00:17:35.760> be<00:17:35.940> real 00:17:36.950 --> 00:17:36.960 align:start position:0% transactions uh to be real 00:17:36.960 --> 00:17:38.570 align:start position:0% transactions uh to be real hi<00:17:37.500> uh<00:17:37.679> thank<00:17:37.980> you<00:17:38.100> so<00:17:38.160> much<00:17:38.280> for<00:17:38.460> our 00:17:38.570 --> 00:17:38.580 align:start position:0% hi uh thank you so much for our 00:17:38.580 --> 00:17:40.370 align:start position:0% hi uh thank you so much for our presentation<00:17:38.940> today<00:17:39.240> I<00:17:39.419> feel<00:17:39.720> like<00:17:39.900> I<00:17:40.080> learned 00:17:40.370 --> 00:17:40.380 align:start position:0% presentation today I feel like I learned 00:17:40.380 --> 00:17:42.409 align:start position:0% presentation today I feel like I learned a<00:17:40.559> lot<00:17:40.679> so<00:17:41.160> uh<00:17:41.400> one<00:17:41.700> question<00:17:41.880> I<00:17:42.179> just<00:17:42.299> really 00:17:42.409 --> 00:17:42.419 align:start position:0% a lot so uh one question I just really 00:17:42.419 --> 00:17:45.350 align:start position:0% a lot so uh one question I just really want<00:17:42.600> to<00:17:42.720> ask<00:17:42.840> is<00:17:43.200> uh<00:17:43.799> about<00:17:44.280> metamask<00:17:45.059> product 00:17:45.350 --> 00:17:45.360 align:start position:0% want to ask is uh about metamask product 00:17:45.360 --> 00:17:47.870 align:start position:0% want to ask is uh about metamask product design<00:17:45.720> so<00:17:46.320> I<00:17:46.500> as<00:17:46.799> far<00:17:46.980> as<00:17:47.100> I<00:17:47.220> know<00:17:47.400> initially 00:17:47.870 --> 00:17:47.880 align:start position:0% design so I as far as I know initially 00:17:47.880 --> 00:17:49.850 align:start position:0% design so I as far as I know initially melamas<00:17:48.539> didn't<00:17:48.660> want<00:17:48.960> to<00:17:49.080> launch<00:17:49.320> the<00:17:49.559> swap 00:17:49.850 --> 00:17:49.860 align:start position:0% melamas didn't want to launch the swap 00:17:49.860 --> 00:17:51.950 align:start position:0% melamas didn't want to launch the swap function<00:17:50.280> and<00:17:50.580> you<00:17:50.760> know<00:17:50.880> on<00:17:51.120> they<00:17:51.539> launched<00:17:51.840> a 00:17:51.950 --> 00:17:51.960 align:start position:0% function and you know on they launched a 00:17:51.960 --> 00:17:54.049 align:start position:0% function and you know on they launched a swap<00:17:52.260> function<00:17:52.559> I<00:17:52.799> just<00:17:52.980> wanna<00:17:53.220> I<00:17:53.760> just<00:17:53.880> feel 00:17:54.049 --> 00:17:54.059 align:start position:0% swap function I just wanna I just feel 00:17:54.059 --> 00:17:57.529 align:start position:0% swap function I just wanna I just feel like<00:17:54.240> uh<00:17:54.900> in<00:17:55.140> the<00:17:55.260> current<00:17:55.440> space<00:17:56.539> the 00:17:57.529 --> 00:17:57.539 align:start position:0% like uh in the current space the 00:17:57.539 --> 00:17:59.990 align:start position:0% like uh in the current space the switching<00:17:57.960> network<00:17:58.200> is<00:17:58.620> really<00:17:59.220> you<00:17:59.580> know<00:17:59.700> a 00:17:59.990 --> 00:18:00.000 align:start position:0% switching network is really you know a 00:18:00.000 --> 00:18:02.210 align:start position:0% switching network is really you know a significant<00:18:00.360> problems<00:18:01.020> that<00:18:01.320> in<00:18:01.799> you<00:18:02.160> know 00:18:02.210 --> 00:18:02.220 align:start position:0% significant problems that in you know 00:18:02.220 --> 00:18:05.350 align:start position:0% significant problems that in you know improving<00:18:02.760> ux<00:18:03.360> I<00:18:04.320> just<00:18:04.440> want<00:18:04.620> to 00:18:05.350 --> 00:18:05.360 align:start position:0% improving ux I just want to 00:18:05.360 --> 00:18:08.870 align:start position:0% improving ux I just want to ask<00:18:06.360> more<00:18:06.720> about<00:18:07.020> what's<00:18:07.380> the<00:18:07.620> future<00:18:07.799> plan<00:18:08.160> on 00:18:08.870 --> 00:18:08.880 align:start position:0% ask more about what's the future plan on 00:18:08.880 --> 00:18:10.909 align:start position:0% ask more about what's the future plan on Madame<00:18:09.539> mask<00:18:09.720> about<00:18:09.960> this<00:18:10.320> interoperability 00:18:10.909 --> 00:18:10.919 align:start position:0% Madame mask about this interoperability 00:18:10.919 --> 00:18:14.390 align:start position:0% Madame mask about this interoperability issue<00:18:11.700> and<00:18:12.059> uh<00:18:12.480> does<00:18:13.320> metamask<00:18:13.799> having<00:18:14.100> plan 00:18:14.390 --> 00:18:14.400 align:start position:0% issue and uh does metamask having plan 00:18:14.400 --> 00:18:17.110 align:start position:0% issue and uh does metamask having plan to<00:18:14.700> solve<00:18:15.059> this<00:18:15.419> network<00:18:15.840> switching<00:18:16.500> problem 00:18:17.110 --> 00:18:17.120 align:start position:0% to solve this network switching problem 00:18:17.120 --> 00:18:21.049 align:start position:0% to solve this network switching problem yeah<00:18:18.320> amazing<00:18:19.320> question 00:18:21.049 --> 00:18:21.059 align:start position:0% yeah amazing question 00:18:21.059 --> 00:18:23.690 align:start position:0% yeah amazing question um<00:18:21.120> I<00:18:21.600> can<00:18:21.780> open<00:18:21.960> my<00:18:22.380> computer<00:18:22.559> and<00:18:23.280> show<00:18:23.520> you 00:18:23.690 --> 00:18:23.700 align:start position:0% um I can open my computer and show you 00:18:23.700 --> 00:18:26.510 align:start position:0% um I can open my computer and show you our<00:18:24.059> designs<00:18:24.720> after<00:18:25.020> the<00:18:25.260> talk<00:18:25.500> and<00:18:26.160> we<00:18:26.340> can 00:18:26.510 --> 00:18:26.520 align:start position:0% our designs after the talk and we can 00:18:26.520 --> 00:18:29.390 align:start position:0% our designs after the talk and we can discuss<00:18:26.940> it<00:18:27.120> we<00:18:27.720> are<00:18:27.900> working<00:18:28.140> on<00:18:28.620> network 00:18:29.390 --> 00:18:29.400 align:start position:0% discuss it we are working on network 00:18:29.400 --> 00:18:32.330 align:start position:0% discuss it we are working on network abstraction<00:18:30.380> it's<00:18:31.380> super<00:18:31.679> interesting 00:18:32.330 --> 00:18:32.340 align:start position:0% abstraction it's super interesting 00:18:32.340 --> 00:18:35.810 align:start position:0% abstraction it's super interesting because<00:18:32.820> super<00:18:33.419> early<00:18:33.780> in<00:18:34.500> the<00:18:34.679> moment<00:18:35.520> right 00:18:35.810 --> 00:18:35.820 align:start position:0% because super early in the moment right 00:18:35.820 --> 00:18:40.310 align:start position:0% because super early in the moment right now<00:18:36.000> and<00:18:36.900> the<00:18:37.799> options<00:18:38.160> are<00:18:38.520> infinite<00:18:39.360> like<00:18:39.720> I 00:18:40.310 --> 00:18:40.320 align:start position:0% now and the options are infinite like I 00:18:40.320 --> 00:18:41.690 align:start position:0% now and the options are infinite like I don't<00:18:40.380> think<00:18:40.500> the<00:18:40.740> version<00:18:40.919> we<00:18:41.280> are<00:18:41.400> going<00:18:41.520> to 00:18:41.690 --> 00:18:41.700 align:start position:0% don't think the version we are going to 00:18:41.700 --> 00:18:43.730 align:start position:0% don't think the version we are going to ship<00:18:42.000> first<00:18:42.299> is<00:18:42.600> going<00:18:42.960> to<00:18:43.080> be<00:18:43.200> the<00:18:43.380> best<00:18:43.500> one 00:18:43.730 --> 00:18:43.740 align:start position:0% ship first is going to be the best one 00:18:43.740 --> 00:18:46.070 align:start position:0% ship first is going to be the best one but<00:18:44.160> I<00:18:44.400> think<00:18:44.520> it's<00:18:45.000> something<00:18:45.299> good<00:18:45.660> that<00:18:45.900> we 00:18:46.070 --> 00:18:46.080 align:start position:0% but I think it's something good that we 00:18:46.080 --> 00:18:48.049 align:start position:0% but I think it's something good that we are<00:18:46.200> going<00:18:46.320> to<00:18:46.559> iterate<00:18:47.039> and<00:18:47.400> we<00:18:47.580> are<00:18:47.760> going<00:18:47.880> to 00:18:48.049 --> 00:18:48.059 align:start position:0% are going to iterate and we are going to 00:18:48.059 --> 00:18:49.909 align:start position:0% are going to iterate and we are going to learn<00:18:48.299> also<00:18:48.660> how<00:18:48.840> people<00:18:49.020> is<00:18:49.260> using<00:18:49.679> different 00:18:49.909 --> 00:18:49.919 align:start position:0% learn also how people is using different 00:18:49.919 --> 00:18:51.350 align:start position:0% learn also how people is using different networks 00:18:51.350 --> 00:18:51.360 align:start position:0% networks 00:18:51.360 --> 00:18:53.870 align:start position:0% networks um<00:18:51.419> we<00:18:51.720> are<00:18:51.900> thinking<00:18:52.320> we<00:18:52.980> can<00:18:53.160> talk<00:18:53.340> in<00:18:53.760> our 00:18:53.870 --> 00:18:53.880 align:start position:0% um we are thinking we can talk in our 00:18:53.880 --> 00:18:55.370 align:start position:0% um we are thinking we can talk in our about<00:18:54.240> it 00:18:55.370 --> 00:18:55.380 align:start position:0% about it 00:18:55.380 --> 00:18:58.190 align:start position:0% about it but<00:18:56.039> yes<00:18:56.400> please<00:18:56.700> find<00:18:57.120> me<00:18:57.360> and<00:18:57.840> we<00:18:58.080> can 00:18:58.190 --> 00:18:58.200 align:start position:0% but yes please find me and we can 00:18:58.200 --> 00:19:00.049 align:start position:0% but yes please find me and we can discuss<00:18:58.559> like<00:18:58.980> how<00:18:59.220> the<00:18:59.400> research<00:18:59.700> knowledge 00:19:00.049 --> 00:19:00.059 align:start position:0% discuss like how the research knowledge 00:19:00.059 --> 00:19:03.350 align:start position:0% discuss like how the research knowledge hi<00:19:00.960> I<00:19:01.500> actually<00:19:01.620> have<00:19:01.980> two<00:19:02.280> questions<00:19:02.580> if 00:19:03.350 --> 00:19:03.360 align:start position:0% hi I actually have two questions if 00:19:03.360 --> 00:19:05.870 align:start position:0% hi I actually have two questions if allowed<00:19:03.780> but<00:19:03.960> one<00:19:04.200> is<00:19:04.380> a<00:19:04.559> follow-up<00:19:04.919> to<00:19:05.340> the 00:19:05.870 --> 00:19:05.880 align:start position:0% allowed but one is a follow-up to the 00:19:05.880 --> 00:19:09.110 align:start position:0% allowed but one is a follow-up to the question<00:19:06.059> before<00:19:06.360> last<00:19:06.660> about<00:19:07.200> signing 00:19:09.110 --> 00:19:09.120 align:start position:0% question before last about signing 00:19:09.120 --> 00:19:10.909 align:start position:0% question before last about signing um<00:19:09.179> and<00:19:09.840> permissions<00:19:10.320> and<00:19:10.620> how<00:19:10.740> those 00:19:10.909 --> 00:19:10.919 align:start position:0% um and permissions and how those 00:19:10.919 --> 00:19:12.710 align:start position:0% um and permissions and how those interact<00:19:11.340> and<00:19:11.880> even<00:19:12.059> where<00:19:12.360> they<00:19:12.539> are 00:19:12.710 --> 00:19:12.720 align:start position:0% interact and even where they are 00:19:12.720 --> 00:19:14.690 align:start position:0% interact and even where they are readable<00:19:13.140> if<00:19:13.559> there's<00:19:13.679> one<00:19:14.039> particular<00:19:14.400> thing 00:19:14.690 --> 00:19:14.700 align:start position:0% readable if there's one particular thing 00:19:14.700 --> 00:19:16.250 align:start position:0% readable if there's one particular thing that's<00:19:14.940> being<00:19:15.120> asked<00:19:15.360> for<00:19:15.480> over<00:19:15.720> and<00:19:15.900> over<00:19:16.140> and 00:19:16.250 --> 00:19:16.260 align:start position:0% that's being asked for over and over and 00:19:16.260 --> 00:19:18.169 align:start position:0% that's being asked for over and over and over<00:19:16.440> and<00:19:16.620> over<00:19:16.799> and<00:19:16.980> over<00:19:17.220> again<00:19:17.400> the<00:19:17.880> user 00:19:18.169 --> 00:19:18.179 align:start position:0% over and over and over again the user 00:19:18.179 --> 00:19:20.270 align:start position:0% over and over and over again the user will<00:19:18.299> get<00:19:18.720> alert<00:19:19.440> fatigue<00:19:19.860> and<00:19:19.980> just<00:19:20.160> be 00:19:20.270 --> 00:19:20.280 align:start position:0% will get alert fatigue and just be 00:19:20.280 --> 00:19:23.630 align:start position:0% will get alert fatigue and just be clicking<00:19:20.700> and<00:19:21.419> to<00:19:21.600> avoid<00:19:21.900> that<00:19:22.200> I<00:19:22.919> was<00:19:23.039> seeking 00:19:23.630 --> 00:19:23.640 align:start position:0% clicking and to avoid that I was seeking 00:19:23.640 --> 00:19:26.270 align:start position:0% clicking and to avoid that I was seeking to<00:19:24.059> have<00:19:24.600> a<00:19:24.780> permission<00:19:25.080> for<00:19:25.620> that<00:19:25.860> particular 00:19:26.270 --> 00:19:26.280 align:start position:0% to have a permission for that particular 00:19:26.280 --> 00:19:29.630 align:start position:0% to have a permission for that particular thing<00:19:26.640> that<00:19:26.820> gets<00:19:27.120> repeated<00:19:27.419> many<00:19:27.780> times<00:19:28.640> and 00:19:29.630 --> 00:19:29.640 align:start position:0% thing that gets repeated many times and 00:19:29.640 --> 00:19:31.850 align:start position:0% thing that gets repeated many times and uh<00:19:30.419> was<00:19:30.780> here<00:19:30.900> for<00:19:31.080> the<00:19:31.200> hackathon<00:19:31.620> last 00:19:31.850 --> 00:19:31.860 align:start position:0% uh was here for the hackathon last 00:19:31.860 --> 00:19:33.590 align:start position:0% uh was here for the hackathon last weekend<00:19:32.039> and<00:19:32.400> wanted<00:19:32.640> to<00:19:32.820> use<00:19:32.940> made<00:19:33.179> a<00:19:33.480> mask 00:19:33.590 --> 00:19:33.600 align:start position:0% weekend and wanted to use made a mask 00:19:33.600 --> 00:19:35.810 align:start position:0% weekend and wanted to use made a mask snaps<00:19:34.140> to<00:19:34.260> make<00:19:34.380> that<00:19:34.559> easier<00:19:34.919> and<00:19:35.460> was<00:19:35.640> told 00:19:35.810 --> 00:19:35.820 align:start position:0% snaps to make that easier and was told 00:19:35.820 --> 00:19:37.669 align:start position:0% snaps to make that easier and was told oh<00:19:36.179> no<00:19:36.360> I<00:19:36.600> actually<00:19:36.720> made<00:19:37.020> in<00:19:37.200> my<00:19:37.320> Snaps 00:19:37.669 --> 00:19:37.679 align:start position:0% oh no I actually made in my Snaps 00:19:37.679 --> 00:19:39.529 align:start position:0% oh no I actually made in my Snaps doesn't<00:19:37.980> support<00:19:38.640> working<00:19:39.120> with<00:19:39.419> the 00:19:39.529 --> 00:19:39.539 align:start position:0% doesn't support working with the 00:19:39.539 --> 00:19:41.750 align:start position:0% doesn't support working with the permission<00:19:39.840> system<00:19:40.260> to<00:19:40.679> do<00:19:40.799> that<00:19:41.039> I<00:19:41.700> was 00:19:41.750 --> 00:19:41.760 align:start position:0% permission system to do that I was 00:19:41.760 --> 00:19:44.690 align:start position:0% permission system to do that I was wondering<00:19:42.059> if<00:19:42.179> there<00:19:42.480> are<00:19:42.600> plans<00:19:43.200> to<00:19:43.700> allow 00:19:44.690 --> 00:19:44.700 align:start position:0% wondering if there are plans to allow 00:19:44.700 --> 00:19:46.610 align:start position:0% wondering if there are plans to allow snaps<00:19:45.360> to<00:19:45.539> work<00:19:45.720> with<00:19:45.900> the<00:19:46.020> permission<00:19:46.320> system 00:19:46.610 --> 00:19:46.620 align:start position:0% snaps to work with the permission system 00:19:46.620 --> 00:19:50.409 align:start position:0% snaps to work with the permission system in<00:19:46.980> the<00:19:47.100> future<00:19:47.720> uh<00:19:48.720> to<00:19:49.020> follow<00:19:49.140> up<00:19:49.320> on<00:19:49.500> that 00:19:50.409 --> 00:19:50.419 align:start position:0% in the future uh to follow up on that 00:19:50.419 --> 00:19:53.690 align:start position:0% in the future uh to follow up on that good<00:19:51.419> question<00:19:51.660> I<00:19:52.260> think<00:19:52.380> the<00:19:52.799> most<00:19:53.039> powerful 00:19:53.690 --> 00:19:53.700 align:start position:0% good question I think the most powerful 00:19:53.700 --> 00:19:57.230 align:start position:0% good question I think the most powerful thing<00:19:54.240> about<00:19:54.720> snaps<00:19:55.440> is<00:19:55.919> like<00:19:56.280> the<00:19:56.880> list<00:19:57.059> of 00:19:57.230 --> 00:19:57.240 align:start position:0% thing about snaps is like the list of 00:19:57.240 --> 00:19:59.330 align:start position:0% thing about snaps is like the list of formations<00:19:57.720> we<00:19:58.080> have<00:19:58.260> available<00:19:58.500> right<00:19:59.160> now 00:19:59.330 --> 00:19:59.340 align:start position:0% formations we have available right now 00:19:59.340 --> 00:20:01.850 align:start position:0% formations we have available right now it's<00:19:59.940> not<00:20:00.179> static<00:20:00.720> it's<00:20:01.260> something<00:20:01.440> that<00:20:01.740> is 00:20:01.850 --> 00:20:01.860 align:start position:0% it's not static it's something that is 00:20:01.860 --> 00:20:05.930 align:start position:0% it's not static it's something that is going<00:20:02.100> to<00:20:02.280> grow<00:20:02.520> in<00:20:03.419> the<00:20:03.480> future<00:20:03.660> so<00:20:04.980> I'm<00:20:05.580> not 00:20:05.930 --> 00:20:05.940 align:start position:0% going to grow in the future so I'm not 00:20:05.940 --> 00:20:10.250 align:start position:0% going to grow in the future so I'm not uh<00:20:06.840> here<00:20:07.380> to<00:20:07.559> say<00:20:07.799> when<00:20:08.280> but<00:20:09.240> that<00:20:09.900> may<00:20:10.140> be 00:20:10.250 --> 00:20:10.260 align:start position:0% uh here to say when but that may be 00:20:10.260 --> 00:20:12.350 align:start position:0% uh here to say when but that may be something<00:20:10.559> that<00:20:10.919> is<00:20:11.100> in<00:20:11.280> the<00:20:11.400> pipeline<00:20:11.820> and 00:20:12.350 --> 00:20:12.360 align:start position:0% something that is in the pipeline and 00:20:12.360 --> 00:20:13.970 align:start position:0% something that is in the pipeline and the<00:20:12.480> other<00:20:12.539> question<00:20:12.780> was<00:20:13.020> you<00:20:13.620> showed 00:20:13.970 --> 00:20:13.980 align:start position:0% the other question was you showed 00:20:13.980 --> 00:20:15.770 align:start position:0% the other question was you showed earlier<00:20:14.280> some<00:20:14.580> designs<00:20:15.059> where<00:20:15.299> you<00:20:15.600> were 00:20:15.770 --> 00:20:15.780 align:start position:0% earlier some designs where you were 00:20:15.780 --> 00:20:18.710 align:start position:0% earlier some designs where you were making<00:20:16.620> it<00:20:16.980> clear<00:20:17.340> that<00:20:17.760> like<00:20:18.000> oh<00:20:18.179> you<00:20:18.419> can<00:20:18.539> set 00:20:18.710 --> 00:20:18.720 align:start position:0% making it clear that like oh you can set 00:20:18.720 --> 00:20:22.190 align:start position:0% making it clear that like oh you can set a<00:20:18.900> limit<00:20:19.080> for<00:20:19.799> how<00:20:20.280> much<00:20:20.580> of<00:20:21.120> a<00:20:21.299> token<00:20:21.720> a 00:20:22.190 --> 00:20:22.200 align:start position:0% a limit for how much of a token a 00:20:22.200 --> 00:20:24.650 align:start position:0% a limit for how much of a token a particular<00:20:22.500> dab<00:20:22.860> can<00:20:23.039> be<00:20:23.160> authorized<00:20:23.580> for<00:20:23.760> and 00:20:24.650 --> 00:20:24.660 align:start position:0% particular dab can be authorized for and 00:20:24.660 --> 00:20:26.330 align:start position:0% particular dab can be authorized for and you<00:20:24.960> have<00:20:25.080> a<00:20:25.200> line<00:20:25.320> in<00:20:25.500> there<00:20:25.679> like<00:20:25.860> oh<00:20:25.980> you<00:20:26.220> can 00:20:26.330 --> 00:20:26.340 align:start position:0% you have a line in there like oh you can 00:20:26.340 --> 00:20:28.909 align:start position:0% you have a line in there like oh you can raise<00:20:26.520> this<00:20:26.760> limit<00:20:26.940> later<00:20:27.380> but<00:20:28.380> you<00:20:28.740> aren't 00:20:28.909 --> 00:20:28.919 align:start position:0% raise this limit later but you aren't 00:20:28.919 --> 00:20:31.130 align:start position:0% raise this limit later but you aren't telling<00:20:29.280> people<00:20:29.460> that<00:20:29.760> there's<00:20:29.940> a<00:20:30.179> cost<00:20:30.480> to<00:20:30.780> do 00:20:31.130 --> 00:20:31.140 align:start position:0% telling people that there's a cost to do 00:20:31.140 --> 00:20:32.990 align:start position:0% telling people that there's a cost to do so<00:20:31.320> it's<00:20:31.559> like<00:20:31.740> a<00:20:31.919> financial<00:20:32.039> cost<00:20:32.460> of<00:20:32.820> doing 00:20:32.990 --> 00:20:33.000 align:start position:0% so it's like a financial cost of doing 00:20:33.000 --> 00:20:36.830 align:start position:0% so it's like a financial cost of doing so<00:20:33.240> later<00:20:33.600> and<00:20:34.559> I<00:20:34.679> think<00:20:34.860> that<00:20:35.160> that<00:20:35.660> seems<00:20:36.660> to 00:20:36.830 --> 00:20:36.840 align:start position:0% so later and I think that that seems to 00:20:36.840 --> 00:20:39.830 align:start position:0% so later and I think that that seems to undermine<00:20:37.440> this<00:20:37.919> idea<00:20:38.340> of<00:20:38.700> consent<00:20:39.240> a<00:20:39.720> little 00:20:39.830 --> 00:20:39.840 align:start position:0% undermine this idea of consent a little 00:20:39.840 --> 00:20:42.590 align:start position:0% undermine this idea of consent a little bit<00:20:40.020> because<00:20:40.380> you're<00:20:41.039> not<00:20:41.419> telling<00:20:42.419> people 00:20:42.590 --> 00:20:42.600 align:start position:0% bit because you're not telling people 00:20:42.600 --> 00:20:44.750 align:start position:0% bit because you're not telling people that<00:20:43.080> there<00:20:43.320> are<00:20:43.440> going<00:20:43.620> to<00:20:43.740> be<00:20:43.860> costs<00:20:44.340> if<00:20:44.580> they 00:20:44.750 --> 00:20:44.760 align:start position:0% that there are going to be costs if they 00:20:44.760 --> 00:20:47.150 align:start position:0% that there are going to be costs if they want<00:20:45.000> to<00:20:45.299> limit<00:20:45.780> things<00:20:46.140> now<00:20:46.380> and<00:20:46.620> then<00:20:46.740> add<00:20:46.980> it 00:20:47.150 --> 00:20:47.160 align:start position:0% want to limit things now and then add it 00:20:47.160 --> 00:20:49.730 align:start position:0% want to limit things now and then add it later<00:20:47.539> do<00:20:48.539> you<00:20:48.660> have<00:20:48.780> any<00:20:48.900> thoughts<00:20:49.140> about<00:20:49.260> why 00:20:49.730 --> 00:20:49.740 align:start position:0% later do you have any thoughts about why 00:20:49.740 --> 00:20:52.250 align:start position:0% later do you have any thoughts about why that<00:20:50.039> decision<00:20:50.400> was<00:20:50.580> made<00:20:50.760> to<00:20:51.000> obscure<00:20:51.419> that<00:20:51.539> I 00:20:52.250 --> 00:20:52.260 align:start position:0% that decision was made to obscure that I 00:20:52.260 --> 00:20:53.750 align:start position:0% that decision was made to obscure that I agree 00:20:53.750 --> 00:20:53.760 align:start position:0% agree 00:20:53.760 --> 00:20:57.710 align:start position:0% agree um<00:20:53.820> we<00:20:54.960> we<00:20:55.679> are<00:20:55.860> not<00:20:56.039> exposed<00:20:56.640> in<00:20:56.760> future 00:20:57.710 --> 00:20:57.720 align:start position:0% um we we are not exposed in future 00:20:57.720 --> 00:21:00.650 align:start position:0% um we we are not exposed in future cost<00:20:58.559> of<00:20:59.100> the<00:20:59.280> transaction<00:20:59.760> and<00:21:00.419> maybe 00:21:00.650 --> 00:21:00.660 align:start position:0% cost of the transaction and maybe 00:21:00.660 --> 00:21:04.250 align:start position:0% cost of the transaction and maybe something<00:21:01.080> that<00:21:02.039> um<00:21:02.340> could<00:21:02.940> be<00:21:03.059> part<00:21:03.299> of<00:21:03.539> some 00:21:04.250 --> 00:21:04.260 align:start position:0% something that um could be part of some 00:21:04.260 --> 00:21:07.330 align:start position:0% something that um could be part of some documentation<00:21:05.039> on<00:21:05.700> user-facing 00:21:07.330 --> 00:21:07.340 align:start position:0% documentation on user-facing 00:21:07.340 --> 00:21:09.770 align:start position:0% documentation on user-facing education<00:21:08.340> material<00:21:09.000> or<00:21:09.299> something<00:21:09.480> like 00:21:09.770 --> 00:21:09.780 align:start position:0% education material or something like 00:21:09.780 --> 00:21:11.289 align:start position:0% education material or something like that 00:21:11.289 --> 00:21:11.299 align:start position:0% that 00:21:11.299 --> 00:21:14.150 align:start position:0% that estimating<00:21:12.299> how<00:21:13.020> the<00:21:13.440> thing<00:21:13.620> is<00:21:13.799> going<00:21:14.039> to 00:21:14.150 --> 00:21:14.160 align:start position:0% estimating how the thing is going to 00:21:14.160 --> 00:21:18.529 align:start position:0% estimating how the thing is going to cost<00:21:14.539> in<00:21:15.539> the<00:21:15.660> future<00:21:15.780> it's<00:21:16.500> weird<00:21:17.039> and 00:21:18.529 --> 00:21:18.539 align:start position:0% cost in the future it's weird and 00:21:18.539 --> 00:21:19.909 align:start position:0% cost in the future it's weird and but 00:21:19.909 --> 00:21:19.919 align:start position:0% but 00:21:19.919 --> 00:21:23.270 align:start position:0% but I<00:21:20.460> don't<00:21:20.580> know<00:21:21.200> maybe<00:21:22.200> something<00:21:22.620> to<00:21:22.919> explore 00:21:23.270 --> 00:21:23.280 align:start position:0% I don't know maybe something to explore 00:21:23.280 --> 00:21:25.850 align:start position:0% I don't know maybe something to explore thank<00:21:24.059> you<00:21:24.179> for<00:21:24.360> that<00:21:24.600> question<00:21:24.960> and<00:21:25.559> the<00:21:25.740> last 00:21:25.850 --> 00:21:25.860 align:start position:0% thank you for that question and the last 00:21:25.860 --> 00:21:29.510 align:start position:0% thank you for that question and the last one<00:21:26.360> hello<00:21:27.360> yeah<00:21:27.720> thanks<00:21:28.080> for<00:21:28.260> this<00:21:28.440> uh<00:21:28.799> great 00:21:29.510 --> 00:21:29.520 align:start position:0% one hello yeah thanks for this uh great 00:21:29.520 --> 00:21:32.210 align:start position:0% one hello yeah thanks for this uh great presentation<00:21:30.000> it's<00:21:30.419> really<00:21:30.600> insightful<00:21:31.220> and 00:21:32.210 --> 00:21:32.220 align:start position:0% presentation it's really insightful and 00:21:32.220 --> 00:21:34.850 align:start position:0% presentation it's really insightful and so<00:21:32.700> I<00:21:32.880> have<00:21:32.940> a<00:21:33.120> question<00:21:33.240> around<00:21:33.600> the 00:21:34.850 --> 00:21:34.860 align:start position:0% so I have a question around the 00:21:34.860 --> 00:21:37.850 align:start position:0% so I have a question around the of<00:21:35.700> the<00:21:35.940> fact<00:21:36.360> of<00:21:36.539> give<00:21:36.720> it<00:21:36.900> consent<00:21:37.260> you 00:21:37.850 --> 00:21:37.860 align:start position:0% of the fact of give it consent you 00:21:37.860 --> 00:21:39.710 align:start position:0% of the fact of give it consent you mentioned<00:21:38.220> that 00:21:39.710 --> 00:21:39.720 align:start position:0% mentioned that 00:21:39.720 --> 00:21:41.930 align:start position:0% mentioned that um<00:21:39.780> it's<00:21:40.440> quite<00:21:40.799> complex<00:21:41.159> because<00:21:41.460> it's 00:21:41.930 --> 00:21:41.940 align:start position:0% um it's quite complex because it's 00:21:41.940 --> 00:21:45.470 align:start position:0% um it's quite complex because it's either<00:21:42.780> you<00:21:43.320> give<00:21:43.559> too<00:21:43.919> much<00:21:44.100> permission<00:21:44.640> and 00:21:45.470 --> 00:21:45.480 align:start position:0% either you give too much permission and 00:21:45.480 --> 00:21:47.810 align:start position:0% either you give too much permission and you<00:21:45.659> fall<00:21:45.840> into<00:21:46.020> like<00:21:46.500> an<00:21:46.740> area<00:21:46.980> where<00:21:47.460> it's 00:21:47.810 --> 00:21:47.820 align:start position:0% you fall into like an area where it's 00:21:47.820 --> 00:21:51.590 align:start position:0% you fall into like an area where it's dangerous<00:21:48.659> as<00:21:48.900> a<00:21:49.080> user<00:21:49.380> or<00:21:49.799> you<00:21:50.100> you<00:21:50.940> give<00:21:51.299> too 00:21:51.590 --> 00:21:51.600 align:start position:0% dangerous as a user or you you give too 00:21:51.600 --> 00:21:54.710 align:start position:0% dangerous as a user or you you give too much<00:21:51.780> restriction<00:21:52.340> and<00:21:53.340> then<00:21:53.640> you<00:21:54.059> hurt<00:21:54.419> the 00:21:54.710 --> 00:21:54.720 align:start position:0% much restriction and then you hurt the 00:21:54.720 --> 00:21:57.830 align:start position:0% much restriction and then you hurt the usability<00:21:55.760> of<00:21:56.760> a<00:21:56.940> user<00:21:57.179> because<00:21:57.360> the<00:21:57.539> user 00:21:57.830 --> 00:21:57.840 align:start position:0% usability of a user because the user 00:21:57.840 --> 00:22:00.490 align:start position:0% usability of a user because the user then<00:21:57.960> cannot<00:21:58.320> do<00:21:58.500> that<00:21:59.280> much 00:22:00.490 --> 00:22:00.500 align:start position:0% then cannot do that much 00:22:00.500 --> 00:22:03.770 align:start position:0% then cannot do that much what's<00:22:01.500> your<00:22:01.620> opinion<00:22:01.980> on<00:22:02.100> that<00:22:02.400> like<00:22:02.760> how<00:22:03.659> do 00:22:03.770 --> 00:22:03.780 align:start position:0% what's your opinion on that like how do 00:22:03.780 --> 00:22:06.350 align:start position:0% what's your opinion on that like how do you<00:22:03.960> find<00:22:04.440> The<00:22:05.100> Sweet<00:22:05.280> Spot<00:22:05.520> of<00:22:05.880> a<00:22:06.059> right 00:22:06.350 --> 00:22:06.360 align:start position:0% you find The Sweet Spot of a right 00:22:06.360 --> 00:22:08.990 align:start position:0% you find The Sweet Spot of a right balance<00:22:06.900> like<00:22:07.260> this<00:22:07.440> right<00:22:07.679> area<00:22:07.919> where<00:22:08.460> it's 00:22:08.990 --> 00:22:09.000 align:start position:0% balance like this right area where it's 00:22:09.000 --> 00:22:11.750 align:start position:0% balance like this right area where it's not<00:22:09.240> too<00:22:09.840> risky<00:22:10.320> but<00:22:10.860> in<00:22:11.039> the<00:22:11.220> other<00:22:11.400> on<00:22:11.700> the 00:22:11.750 --> 00:22:11.760 align:start position:0% not too risky but in the other on the 00:22:11.760 --> 00:22:14.510 align:start position:0% not too risky but in the other on the other<00:22:11.880> side<00:22:12.059> is<00:22:12.299> not<00:22:12.600> too<00:22:13.200> unusable<00:22:13.980> the 00:22:14.510 --> 00:22:14.520 align:start position:0% other side is not too unusable the 00:22:14.520 --> 00:22:16.070 align:start position:0% other side is not too unusable the equation 00:22:16.070 --> 00:22:16.080 align:start position:0% equation 00:22:16.080 --> 00:22:19.370 align:start position:0% equation um<00:22:16.400> it's<00:22:17.400> it<00:22:17.880> has<00:22:18.120> different<00:22:18.419> parts 00:22:19.370 --> 00:22:19.380 align:start position:0% um it's it has different parts 00:22:19.380 --> 00:22:22.450 align:start position:0% um it's it has different parts first<00:22:20.220> you<00:22:20.640> should<00:22:21.120> have<00:22:21.440> an 00:22:22.450 --> 00:22:22.460 align:start position:0% first you should have an 00:22:22.460 --> 00:22:25.010 align:start position:0% first you should have an interdisciplinary<00:22:23.460> team<00:22:23.820> working<00:22:24.419> on<00:22:24.720> stuff 00:22:25.010 --> 00:22:25.020 align:start position:0% interdisciplinary team working on stuff 00:22:25.020 --> 00:22:27.710 align:start position:0% interdisciplinary team working on stuff because<00:22:25.799> it's<00:22:26.100> more<00:22:26.340> powerful<00:22:26.760> you<00:22:27.299> have<00:22:27.480> more 00:22:27.710 --> 00:22:27.720 align:start position:0% because it's more powerful you have more 00:22:27.720 --> 00:22:30.049 align:start position:0% because it's more powerful you have more views<00:22:28.200> when<00:22:28.679> people<00:22:28.980> when<00:22:29.760> building 00:22:30.049 --> 00:22:30.059 align:start position:0% views when people when building 00:22:30.059 --> 00:22:32.870 align:start position:0% views when people when building something<00:22:30.480> for<00:22:30.840> people<00:22:31.080> then 00:22:32.870 --> 00:22:32.880 align:start position:0% something for people then 00:22:32.880 --> 00:22:35.270 align:start position:0% something for people then there<00:22:33.419> is<00:22:33.659> something<00:22:33.900> very<00:22:34.320> strong<00:22:34.679> having 00:22:35.270 --> 00:22:35.280 align:start position:0% there is something very strong having 00:22:35.280 --> 00:22:38.930 align:start position:0% there is something very strong having enough<00:22:35.580> meta<00:22:36.240> mask<00:22:36.360> right<00:22:36.780> now<00:22:37.020> and<00:22:37.919> is<00:22:38.159> the 00:22:38.930 --> 00:22:38.940 align:start position:0% enough meta mask right now and is the 00:22:38.940 --> 00:22:41.149 align:start position:0% enough meta mask right now and is the fact<00:22:39.120> that<00:22:39.360> we<00:22:39.600> are<00:22:39.720> building<00:22:39.900> approach<00:22:40.620> for 00:22:41.149 --> 00:22:41.159 align:start position:0% fact that we are building approach for 00:22:41.159 --> 00:22:42.970 align:start position:0% fact that we are building approach for the<00:22:41.340> entire<00:22:41.640> world 00:22:42.970 --> 00:22:42.980 align:start position:0% the entire world 00:22:42.980 --> 00:22:46.250 align:start position:0% the entire world put<00:22:43.980> us<00:22:44.220> in<00:22:44.400> a<00:22:44.520> position<00:22:44.700> to<00:22:45.299> hire<00:22:45.539> people<00:22:45.840> from 00:22:46.250 --> 00:22:46.260 align:start position:0% put us in a position to hire people from 00:22:46.260 --> 00:22:48.409 align:start position:0% put us in a position to hire people from all<00:22:46.500> over<00:22:46.679> the<00:22:46.919> world<00:22:47.039> so<00:22:47.700> basically<00:22:48.000> we<00:22:48.240> have 00:22:48.409 --> 00:22:48.419 align:start position:0% all over the world so basically we have 00:22:48.419 --> 00:22:50.450 align:start position:0% all over the world so basically we have people<00:22:48.659> working<00:22:49.080> everywhere 00:22:50.450 --> 00:22:50.460 align:start position:0% people working everywhere 00:22:50.460 --> 00:22:53.029 align:start position:0% people working everywhere and<00:22:51.059> this<00:22:51.299> is<00:22:51.539> powerful<00:22:52.200> because<00:22:52.559> you<00:22:52.860> have 00:22:53.029 --> 00:22:53.039 align:start position:0% and this is powerful because you have 00:22:53.039 --> 00:22:54.529 align:start position:0% and this is powerful because you have people<00:22:53.220> sitting<00:22:53.700> and<00:22:53.880> tables<00:22:54.299> making 00:22:54.529 --> 00:22:54.539 align:start position:0% people sitting and tables making 00:22:54.539 --> 00:22:57.590 align:start position:0% people sitting and tables making decisions<00:22:55.080> that<00:22:55.440> have<00:22:55.740> different<00:22:56.600> biases 00:22:57.590 --> 00:22:57.600 align:start position:0% decisions that have different biases 00:22:57.600 --> 00:22:59.510 align:start position:0% decisions that have different biases mental<00:22:58.559> models 00:22:59.510 --> 00:22:59.520 align:start position:0% mental models 00:22:59.520 --> 00:23:03.110 align:start position:0% mental models this<00:23:00.059> is<00:23:00.179> one<00:23:00.419> part<00:23:00.659> the<00:23:01.620> other<00:23:01.740> part<00:23:02.039> is 00:23:03.110 --> 00:23:03.120 align:start position:0% this is one part the other part is 00:23:03.120 --> 00:23:05.930 align:start position:0% this is one part the other part is talk<00:23:03.600> with<00:23:03.840> users<00:23:04.320> I<00:23:05.159> think<00:23:05.280> talking<00:23:05.580> with 00:23:05.930 --> 00:23:05.940 align:start position:0% talk with users I think talking with 00:23:05.940 --> 00:23:07.789 align:start position:0% talk with users I think talking with users<00:23:06.419> is 00:23:07.789 --> 00:23:07.799 align:start position:0% users is 00:23:07.799 --> 00:23:10.850 align:start position:0% users is um<00:23:07.860> it's<00:23:08.520> so<00:23:08.700> insightful<00:23:09.360> you<00:23:10.260> are<00:23:10.440> going<00:23:10.679> to 00:23:10.850 --> 00:23:10.860 align:start position:0% um it's so insightful you are going to 00:23:10.860 --> 00:23:14.270 align:start position:0% um it's so insightful you are going to discover<00:23:11.120> things<00:23:12.120> that<00:23:12.480> you<00:23:12.659> even<00:23:13.140> imagine<00:23:13.440> in 00:23:14.270 --> 00:23:14.280 align:start position:0% discover things that you even imagine in 00:23:14.280 --> 00:23:16.909 align:start position:0% discover things that you even imagine in the<00:23:14.400> first<00:23:14.580> second<00:23:14.880> three<00:23:15.360> rounds<00:23:16.260> of<00:23:16.440> user 00:23:16.909 --> 00:23:16.919 align:start position:0% the first second three rounds of user 00:23:16.919 --> 00:23:19.370 align:start position:0% the first second three rounds of user testing<00:23:17.400> so 00:23:19.370 --> 00:23:19.380 align:start position:0% testing so 00:23:19.380 --> 00:23:23.750 align:start position:0% testing so the<00:23:19.919> worst<00:23:20.340> team<00:23:20.780> users<00:23:21.780> first<00:23:22.140> and 00:23:23.750 --> 00:23:23.760 align:start position:0% the worst team users first and 00:23:23.760 --> 00:23:27.409 align:start position:0% the worst team users first and try<00:23:24.419> and<00:23:24.780> iterate<00:23:25.260> I<00:23:25.980> think<00:23:26.159> the<00:23:26.760> finding<00:23:27.240> the 00:23:27.409 --> 00:23:27.419 align:start position:0% try and iterate I think the finding the 00:23:27.419 --> 00:23:30.649 align:start position:0% try and iterate I think the finding the balance<00:23:27.840> is<00:23:28.100> the<00:23:29.100> most<00:23:29.220> fun<00:23:29.520> part<00:23:30.000> of<00:23:30.360> being 00:23:30.649 --> 00:23:30.659 align:start position:0% balance is the most fun part of being 00:23:30.659 --> 00:23:33.590 align:start position:0% balance is the most fun part of being working<00:23:30.960> on<00:23:31.260> this 00:23:33.590 --> 00:23:33.600 align:start position:0% 00:23:33.600 --> 00:23:36.710 align:start position:0% thank<00:23:34.140> you<00:23:34.260> very<00:23:34.440> much<00:23:34.559> we<00:23:35.039> have<00:23:35.220> time<00:23:35.520> for<00:23:36.059> one 00:23:36.710 --> 00:23:36.720 align:start position:0% thank you very much we have time for one 00:23:36.720 --> 00:23:41.330 align:start position:0% thank you very much we have time for one last<00:23:37.080> question<00:23:37.500> in<00:23:38.100> Spanish<00:23:38.400> can<00:23:38.820> be<00:23:39.320> also<00:23:40.340> if 00:23:41.330 --> 00:23:41.340 align:start position:0% last question in Spanish can be also if 00:23:41.340 --> 00:23:45.590 align:start position:0% last question in Spanish can be also if not<00:23:42.140> in<00:23:43.140> Spanish 00:23:45.590 --> 00:23:45.600 align:start position:0% 00:23:45.600 --> 00:23:47.090 align:start position:0% if<00:23:46.200> not 00:23:47.090 --> 00:23:47.100 align:start position:0% if not 00:23:47.100 --> 00:23:52.159 align:start position:0% if not muchas<00:23:47.820> gracias<00:23:48.360> santonella<00:23:48.960> yes<00:23:49.260> I'm