WEBVTT Kind: captions Language: en 00:00:01.070 --> 00:00:12.539 align:start position:0% [Applause] 00:00:12.539 --> 00:00:12.549 align:start position:0% 00:00:12.549 --> 00:00:17.670 align:start position:0% none<00:00:13.549> of<00:00:13.580> us<00:00:14.230> are<00:00:15.230> you<00:00:15.289> guys<00:00:15.379> doing<00:00:15.709> a 00:00:17.670 --> 00:00:17.680 align:start position:0% none of us are you guys doing a 00:00:17.680 --> 00:00:19.720 align:start position:0% none of us are you guys doing a three-pound<00:00:18.680> end<00:00:18.950> of<00:00:19.039> the<00:00:19.099> day<00:00:19.250> I<00:00:19.460> hope<00:00:19.610> you 00:00:19.720 --> 00:00:19.730 align:start position:0% three-pound end of the day I hope you 00:00:19.730 --> 00:00:22.390 align:start position:0% three-pound end of the day I hope you have<00:00:19.820> some<00:00:19.939> energy<00:00:20.300> because<00:00:21.259> I<00:00:21.410> yeah<00:00:22.009> yeah 00:00:22.390 --> 00:00:22.400 align:start position:0% have some energy because I yeah yeah 00:00:22.400 --> 00:00:26.079 align:start position:0% have some energy because I yeah yeah going<00:00:23.119> faster<00:00:24.520> okay<00:00:25.520> so<00:00:25.610> I'm<00:00:25.789> gonna<00:00:25.939> share 00:00:26.079 --> 00:00:26.089 align:start position:0% going faster okay so I'm gonna share 00:00:26.089 --> 00:00:27.400 align:start position:0% going faster okay so I'm gonna share some<00:00:26.269> selves<00:00:26.539> I'm<00:00:26.689> really<00:00:26.990> excited<00:00:27.199> about 00:00:27.400 --> 00:00:27.410 align:start position:0% some selves I'm really excited about 00:00:27.410 --> 00:00:29.380 align:start position:0% some selves I'm really excited about working<00:00:28.279> on<00:00:28.369> it<00:00:28.460> for<00:00:28.609> a<00:00:28.670> while<00:00:28.820> we've<00:00:29.359> been 00:00:29.380 --> 00:00:29.390 align:start position:0% working on it for a while we've been 00:00:29.390 --> 00:00:30.700 align:start position:0% working on it for a while we've been thinking<00:00:29.720> about<00:00:29.810> a<00:00:29.900> lot<00:00:29.960> of<00:00:30.259> things<00:00:30.470> there's<00:00:30.679> a 00:00:30.700 --> 00:00:30.710 align:start position:0% thinking about a lot of things there's a 00:00:30.710 --> 00:00:33.280 align:start position:0% thinking about a lot of things there's a lot<00:00:30.740> of<00:00:31.039> challenges<00:00:31.730> in<00:00:31.759> this<00:00:31.970> ecosystem<00:00:32.330> you 00:00:33.280 --> 00:00:33.290 align:start position:0% lot of challenges in this ecosystem you 00:00:33.290 --> 00:00:34.689 align:start position:0% lot of challenges in this ecosystem you know<00:00:33.410> I<00:00:33.440> think<00:00:33.620> meta<00:00:33.949> masks<00:00:34.129> at<00:00:34.370> this<00:00:34.489> point 00:00:34.689 --> 00:00:34.699 align:start position:0% know I think meta masks at this point 00:00:34.699 --> 00:00:36.160 align:start position:0% know I think meta masks at this point we're<00:00:34.850> like<00:00:35.000> the<00:00:35.239> thing<00:00:35.480> that<00:00:35.660> you<00:00:35.750> love<00:00:35.960> to 00:00:36.160 --> 00:00:36.170 align:start position:0% we're like the thing that you love to 00:00:36.170 --> 00:00:37.810 align:start position:0% we're like the thing that you love to hate<00:00:36.350> it's<00:00:36.680> like<00:00:36.860> you<00:00:37.220> know<00:00:37.309> we<00:00:37.400> forget<00:00:37.670> the 00:00:37.810 --> 00:00:37.820 align:start position:0% hate it's like you know we forget the 00:00:37.820 --> 00:00:39.729 align:start position:0% hate it's like you know we forget the joy<00:00:38.059> of<00:00:38.089> being<00:00:38.360> hated<00:00:38.780> because<00:00:39.019> you<00:00:39.290> use<00:00:39.500> us 00:00:39.729 --> 00:00:39.739 align:start position:0% joy of being hated because you use us 00:00:39.739 --> 00:00:42.910 align:start position:0% joy of being hated because you use us too<00:00:40.070> much<00:00:40.309> you<00:00:40.610> know<00:00:40.730> so<00:00:41.629> so<00:00:42.350> we're<00:00:42.710> constantly 00:00:42.910 --> 00:00:42.920 align:start position:0% too much you know so so we're constantly 00:00:42.920 --> 00:00:44.770 align:start position:0% too much you know so so we're constantly thinking<00:00:43.399> about<00:00:43.640> like<00:00:43.789> what's<00:00:44.210> the<00:00:44.360> next<00:00:44.390> step 00:00:44.770 --> 00:00:44.780 align:start position:0% thinking about like what's the next step 00:00:44.780 --> 00:00:46.900 align:start position:0% thinking about like what's the next step how<00:00:44.960> do<00:00:45.020> we<00:00:45.079> get<00:00:45.379> how<00:00:45.860> do<00:00:45.920> we<00:00:46.100> get<00:00:46.610> you<00:00:46.730> guys 00:00:46.900 --> 00:00:46.910 align:start position:0% how do we get how do we get you guys 00:00:46.910 --> 00:00:48.790 align:start position:0% how do we get how do we get you guys we're<00:00:47.270> gonna<00:00:47.449> go<00:00:47.690> how<00:00:48.050> do<00:00:48.109> we<00:00:48.199> get<00:00:48.320> your<00:00:48.469> users 00:00:48.790 --> 00:00:48.800 align:start position:0% we're gonna go how do we get your users 00:00:48.800 --> 00:00:50.680 align:start position:0% we're gonna go how do we get your users where<00:00:49.039> they<00:00:49.070> want<00:00:49.399> to<00:00:49.489> go<00:00:49.609> how<00:00:50.090> do<00:00:50.149> we<00:00:50.239> get<00:00:50.449> out 00:00:50.680 --> 00:00:50.690 align:start position:0% where they want to go how do we get out 00:00:50.690 --> 00:00:53.410 align:start position:0% where they want to go how do we get out of<00:00:50.870> your<00:00:50.960> damn<00:00:51.170> way<00:00:51.379> how<00:00:52.309> do<00:00:52.370> we<00:00:52.520> how<00:00:53.149> do<00:00:53.210> you 00:00:53.410 --> 00:00:53.420 align:start position:0% of your damn way how do we how do you 00:00:53.420 --> 00:00:55.299 align:start position:0% of your damn way how do we how do you night<00:00:53.660> these<00:00:53.960> these<00:00:54.620> three<00:00:54.920> things<00:00:55.160> that's 00:00:55.299 --> 00:00:55.309 align:start position:0% night these these three things that's 00:00:55.309 --> 00:00:57.009 align:start position:0% night these these three things that's going<00:00:55.460> to<00:00:55.519> be<00:00:55.640> a<00:00:55.670> kind<00:00:55.850> of<00:00:55.940> theme<00:00:56.180> security 00:00:57.009 --> 00:00:57.019 align:start position:0% going to be a kind of theme security 00:00:57.019 --> 00:00:59.529 align:start position:0% going to be a kind of theme security utility<00:00:57.590> usability<00:00:58.160> and<00:00:58.370> and<00:00:58.969> to<00:00:59.300> clarify 00:00:59.529 --> 00:00:59.539 align:start position:0% utility usability and and to clarify 00:00:59.539 --> 00:01:01.689 align:start position:0% utility usability and and to clarify because<00:00:59.870> some<00:01:00.769> people<00:01:01.010> think<00:01:01.219> the<00:01:01.340> usability 00:01:01.689 --> 00:01:01.699 align:start position:0% because some people think the usability 00:01:01.699 --> 00:01:03.639 align:start position:0% because some people think the usability ability<00:01:02.420> to<00:01:02.480> the<00:01:02.600> same<00:01:02.780> I'm<00:01:02.929> gonna<00:01:03.140> say<00:01:03.289> for<00:01:03.530> my 00:01:03.639 --> 00:01:03.649 align:start position:0% ability to the same I'm gonna say for my 00:01:03.649 --> 00:01:05.620 align:start position:0% ability to the same I'm gonna say for my purposes<00:01:04.190> when<00:01:04.640> I<00:01:04.670> see<00:01:04.910> utility<00:01:05.479> I'm 00:01:05.620 --> 00:01:05.630 align:start position:0% purposes when I see utility I'm 00:01:05.630 --> 00:01:07.600 align:start position:0% purposes when I see utility I'm functionally<00:01:06.380> like<00:01:06.560> a<00:01:06.770> command-line<00:01:07.220> coder 00:01:07.600 --> 00:01:07.610 align:start position:0% functionally like a command-line coder 00:01:07.610 --> 00:01:09.790 align:start position:0% functionally like a command-line coder could<00:01:07.880> do<00:01:08.000> it<00:01:08.149> but<00:01:08.660> when<00:01:08.810> I<00:01:08.840> say<00:01:09.080> usability<00:01:09.710> I'm 00:01:09.790 --> 00:01:09.800 align:start position:0% could do it but when I say usability I'm 00:01:09.800 --> 00:01:11.410 align:start position:0% could do it but when I say usability I'm talking<00:01:10.039> about<00:01:10.100> like<00:01:10.310> accessibility<00:01:10.910> like 00:01:11.410 --> 00:01:11.420 align:start position:0% talking about like accessibility like 00:01:11.420 --> 00:01:12.370 align:start position:0% talking about like accessibility like anybody<00:01:11.899> could<00:01:12.140> do<00:01:12.229> it 00:01:12.370 --> 00:01:12.380 align:start position:0% anybody could do it 00:01:12.380 --> 00:01:14.169 align:start position:0% anybody could do it so<00:01:12.950> how<00:01:13.070> do<00:01:13.130> we<00:01:13.220> make<00:01:13.429> something<00:01:13.670> that's<00:01:13.940> so 00:01:14.169 --> 00:01:14.179 align:start position:0% so how do we make something that's so 00:01:14.179 --> 00:01:17.080 align:start position:0% so how do we make something that's so secure<00:01:14.770> anybody<00:01:15.770> could<00:01:16.009> do<00:01:16.130> it<00:01:16.280> but<00:01:16.580> that<00:01:16.729> they 00:01:17.080 --> 00:01:17.090 align:start position:0% secure anybody could do it but that they 00:01:17.090 --> 00:01:19.210 align:start position:0% secure anybody could do it but that they could<00:01:17.300> do<00:01:17.420> kind<00:01:17.660> of<00:01:17.780> anything<00:01:18.259> right<00:01:18.860> that's 00:01:19.210 --> 00:01:19.220 align:start position:0% could do kind of anything right that's 00:01:19.220 --> 00:01:21.580 align:start position:0% could do kind of anything right that's the<00:01:19.369> dream<00:01:19.580> right<00:01:19.640> and<00:01:20.090> you<00:01:20.300> know<00:01:20.509> and<00:01:20.780> we're 00:01:21.580 --> 00:01:21.590 align:start position:0% the dream right and you know and we're 00:01:21.590 --> 00:01:23.499 align:start position:0% the dream right and you know and we're gonna<00:01:21.709> make<00:01:22.250> that<00:01:22.369> possible<00:01:22.610> for<00:01:22.789> you<00:01:23.060> so 00:01:23.499 --> 00:01:23.509 align:start position:0% gonna make that possible for you so 00:01:23.509 --> 00:01:25.479 align:start position:0% gonna make that possible for you so right<00:01:23.869> now<00:01:24.020> modern<00:01:24.500> wallets<00:01:24.830> are<00:01:24.950> limited<00:01:25.340> in 00:01:25.479 --> 00:01:25.489 align:start position:0% right now modern wallets are limited in 00:01:25.489 --> 00:01:28.120 align:start position:0% right now modern wallets are limited in these<00:01:25.640> these<00:01:26.179> three<00:01:26.479> axes<00:01:26.709> the<00:01:27.709> first<00:01:27.920> one 00:01:28.120 --> 00:01:28.130 align:start position:0% these these three axes the first one 00:01:28.130 --> 00:01:30.850 align:start position:0% these these three axes the first one innovation<00:01:29.090> right<00:01:29.810> we<00:01:30.229> don't<00:01:30.410> have<00:01:30.590> new 00:01:30.850 --> 00:01:30.860 align:start position:0% innovation right we don't have new 00:01:30.860 --> 00:01:32.710 align:start position:0% innovation right we don't have new networks<00:01:31.280> fast<00:01:31.580> enough<00:01:31.940> we<00:01:32.179> don't<00:01:32.360> have<00:01:32.450> your 00:01:32.710 --> 00:01:32.720 align:start position:0% networks fast enough we don't have your 00:01:32.720 --> 00:01:34.440 align:start position:0% networks fast enough we don't have your favorite<00:01:33.020> chain<00:01:33.259> your<00:01:33.709> your<00:01:33.920> favorite 00:01:34.440 --> 00:01:34.450 align:start position:0% favorite chain your your favorite 00:01:34.450 --> 00:01:37.660 align:start position:0% favorite chain your your favorite authority<00:01:35.450> whatever<00:01:35.860> we<00:01:36.860> don't<00:01:37.009> add<00:01:37.160> new<00:01:37.340> IP 00:01:37.660 --> 00:01:37.670 align:start position:0% authority whatever we don't add new IP 00:01:37.670 --> 00:01:39.190 align:start position:0% authority whatever we don't add new IP features<00:01:38.119> there<00:01:38.300> have<00:01:38.390> been<00:01:38.479> better<00:01:38.690> token 00:01:39.190 --> 00:01:39.200 align:start position:0% features there have been better token 00:01:39.200 --> 00:01:41.199 align:start position:0% features there have been better token standards<00:01:39.649> then<00:01:39.770> you<00:01:39.860> got<00:01:40.009> years<00:01:40.250> in<00:01:40.459> 24<00:01:41.000> like 00:01:41.199 --> 00:01:41.209 align:start position:0% standards then you got years in 24 like 00:01:41.209 --> 00:01:43.130 align:start position:0% standards then you got years in 24 like five<00:01:41.810> years<00:01:42.170> longer 00:01:43.130 --> 00:01:43.140 align:start position:0% five years longer 00:01:43.140 --> 00:01:46.470 align:start position:0% five years longer so<00:01:44.140> hey<00:01:44.350> like<00:01:44.950> we<00:01:45.550> don't<00:01:45.880> we<00:01:46.000> also<00:01:46.150> for<00:01:46.390> the 00:01:46.470 --> 00:01:46.480 align:start position:0% so hey like we don't we also for the 00:01:46.480 --> 00:01:48.600 align:start position:0% so hey like we don't we also for the latest<00:01:46.720> scaling<00:01:47.170> tech<00:01:47.380> right<00:01:47.800> today<00:01:48.400> if 00:01:48.600 --> 00:01:48.610 align:start position:0% latest scaling tech right today if 00:01:48.610 --> 00:01:50.700 align:start position:0% latest scaling tech right today if you've<00:01:48.820> got<00:01:49.030> a<00:01:49.060> new<00:01:49.270> plasma<00:01:49.960> thing<00:01:50.440> or<00:01:50.590> you've 00:01:50.700 --> 00:01:50.710 align:start position:0% you've got a new plasma thing or you've 00:01:50.710 --> 00:01:52.950 align:start position:0% you've got a new plasma thing or you've gotta<00:01:50.860> use<00:01:51.070> you<00:01:51.970> know<00:01:52.090> lay<00:01:52.390> or<00:01:52.540> two<00:01:52.720> thing 00:01:52.950 --> 00:01:52.960 align:start position:0% gotta use you know lay or two thing 00:01:52.960 --> 00:01:54.300 align:start position:0% gotta use you know lay or two thing you're<00:01:53.440> basically<00:01:53.740> gonna<00:01:53.890> make<00:01:53.980> your<00:01:54.250> own 00:01:54.300 --> 00:01:54.310 align:start position:0% you're basically gonna make your own 00:01:54.310 --> 00:01:56.100 align:start position:0% you're basically gonna make your own wallet<00:01:54.700> so<00:01:55.030> it's<00:01:55.150> like<00:01:55.270> that<00:01:55.360> average<00:01:55.840> theme 00:01:56.100 --> 00:01:56.110 align:start position:0% wallet so it's like that average theme 00:01:56.110 --> 00:01:58.260 align:start position:0% wallet so it's like that average theme will<00:01:56.320> be<00:01:56.440> like<00:01:56.650> well<00:01:57.220> you<00:01:57.580> make<00:01:57.790> a<00:01:57.820> new<00:01:58.060> wallet 00:01:58.260 --> 00:01:58.270 align:start position:0% will be like well you make a new wallet 00:01:58.270 --> 00:02:01.410 align:start position:0% will be like well you make a new wallet you<00:01:58.600> make<00:01:58.840> a<00:01:58.870> new<00:01:59.080> wallet<00:01:59.970> contracts<00:02:00.970> got<00:02:01.180> you 00:02:01.410 --> 00:02:01.420 align:start position:0% you make a new wallet contracts got you 00:02:01.420 --> 00:02:04.260 align:start position:0% you make a new wallet contracts got you make<00:02:01.630> a<00:02:01.660> new<00:02:01.870> wallet<00:02:02.370> you<00:02:03.370> have<00:02:03.520> a<00:02:03.550> hosting 00:02:04.260 --> 00:02:04.270 align:start position:0% make a new wallet you have a hosting 00:02:04.270 --> 00:02:06.600 align:start position:0% make a new wallet you have a hosting service<00:02:04.660> that<00:02:04.690> are<00:02:05.050> alternative<00:02:05.950> I<00:02:06.130> make<00:02:06.580> a 00:02:06.600 --> 00:02:06.610 align:start position:0% service that are alternative I make a 00:02:06.610 --> 00:02:07.200 align:start position:0% service that are alternative I make a new<00:02:06.790> wallet 00:02:07.200 --> 00:02:07.210 align:start position:0% new wallet 00:02:07.210 --> 00:02:09.150 align:start position:0% new wallet you<00:02:07.900> got<00:02:08.020> a<00:02:08.050> new<00:02:08.200> hardware<00:02:08.530> wallet<00:02:08.890> it's<00:02:09.010> not 00:02:09.150 --> 00:02:09.160 align:start position:0% you got a new hardware wallet it's not 00:02:09.160 --> 00:02:10.620 align:start position:0% you got a new hardware wallet it's not supported<00:02:09.430> by<00:02:09.670> astronomers<00:02:10.210> you<00:02:10.300> pass<00:02:10.450> up 00:02:10.620 --> 00:02:10.630 align:start position:0% supported by astronomers you pass up 00:02:10.630 --> 00:02:11.970 align:start position:0% supported by astronomers you pass up your<00:02:10.660> probably<00:02:11.050> gonna<00:02:11.140> have<00:02:11.350> to<00:02:11.410> make<00:02:11.590> it<00:02:11.710> into 00:02:11.970 --> 00:02:11.980 align:start position:0% your probably gonna have to make it into 00:02:11.980 --> 00:02:14.280 align:start position:0% your probably gonna have to make it into your<00:02:12.010> own<00:02:12.160> wallet<00:02:12.430> now<00:02:13.240> you<00:02:13.750> you<00:02:14.020> have<00:02:14.170> any 00:02:14.280 --> 00:02:14.290 align:start position:0% your own wallet now you you have any 00:02:14.290 --> 00:02:17.010 align:start position:0% your own wallet now you you have any kind<00:02:14.380> of<00:02:14.470> cryptography<00:02:14.800> you<00:02:15.460> got<00:02:15.640> some<00:02:16.020> spirit 00:02:17.010 --> 00:02:17.020 align:start position:0% kind of cryptography you got some spirit 00:02:17.020 --> 00:02:19.850 align:start position:0% kind of cryptography you got some spirit stuff<00:02:17.260> making<00:02:18.070> you<00:02:18.220> wallet 00:02:19.850 --> 00:02:19.860 align:start position:0% stuff making you wallet 00:02:19.860 --> 00:02:22.320 align:start position:0% stuff making you wallet to<00:02:20.860> slow<00:02:21.070> deliberate<00:02:21.400> slow<00:02:21.580> request<00:02:22.030> did<00:02:22.240> we 00:02:22.320 --> 00:02:22.330 align:start position:0% to slow deliberate slow request did we 00:02:22.330 --> 00:02:24.690 align:start position:0% to slow deliberate slow request did we not<00:02:22.480> get<00:02:22.690> that<00:02:22.840> feature<00:02:23.110> in<00:02:23.320> in<00:02:23.470> time<00:02:23.650> for<00:02:24.400> cos 00:02:24.690 --> 00:02:24.700 align:start position:0% not get that feature in in time for cos 00:02:24.700 --> 00:02:26.870 align:start position:0% not get that feature in in time for cos making<00:02:25.600> a<00:02:25.660> wallet 00:02:26.870 --> 00:02:26.880 align:start position:0% making a wallet 00:02:26.880 --> 00:02:30.030 align:start position:0% making a wallet we're<00:02:27.880> gonna<00:02:28.060> not<00:02:28.330> secure<00:02:28.810> enough<00:02:28.840> okay<00:02:29.530> we're 00:02:30.030 --> 00:02:30.040 align:start position:0% we're gonna not secure enough okay we're 00:02:30.040 --> 00:02:33.660 align:start position:0% we're gonna not secure enough okay we're bringing<00:02:30.250> a<00:02:30.700> JavaScript<00:02:32.190> runtime<00:02:33.190> now<00:02:33.370> I<00:02:33.400> hope 00:02:33.660 --> 00:02:33.670 align:start position:0% bringing a JavaScript runtime now I hope 00:02:33.670 --> 00:02:36.000 align:start position:0% bringing a JavaScript runtime now I hope that<00:02:33.700> you<00:02:33.910> saw<00:02:34.090> Erin's<00:02:34.959> some<00:02:35.350> curvy<00:02:35.650> talk<00:02:35.830> on 00:02:36.000 --> 00:02:36.010 align:start position:0% that you saw Erin's some curvy talk on 00:02:36.010 --> 00:02:37.170 align:start position:0% that you saw Erin's some curvy talk on well<00:02:36.160> nobody's<00:02:36.520> been<00:02:36.760> in<00:02:36.850> a<00:02:36.910> couple<00:02:37.060> times 00:02:37.170 --> 00:02:37.180 align:start position:0% well nobody's been in a couple times 00:02:37.180 --> 00:02:38.970 align:start position:0% well nobody's been in a couple times he's<00:02:37.840> talking<00:02:38.080> about<00:02:38.140> how<00:02:38.350> we're<00:02:38.560> working<00:02:38.709> to 00:02:38.970 --> 00:02:38.980 align:start position:0% he's talking about how we're working to 00:02:38.980 --> 00:02:41.670 align:start position:0% he's talking about how we're working to isolate<00:02:39.130> our<00:02:39.520> dependencies<00:02:40.120> better<00:02:40.360> and<00:02:41.320> you 00:02:41.670 --> 00:02:41.680 align:start position:0% isolate our dependencies better and you 00:02:41.680 --> 00:02:43.620 align:start position:0% isolate our dependencies better and you should<00:02:41.830> you<00:02:42.010> should<00:02:42.040> check<00:02:42.340> that<00:02:42.490> out<00:02:42.640> you 00:02:43.620 --> 00:02:43.630 align:start position:0% should you should check that out you 00:02:43.630 --> 00:02:45.510 align:start position:0% should you should check that out you know<00:02:43.660> it's<00:02:43.840> a<00:02:43.870> little<00:02:44.020> bit<00:02:44.170> on<00:02:44.260> Twitter<00:02:44.520> but 00:02:45.510 --> 00:02:45.520 align:start position:0% know it's a little bit on Twitter but 00:02:45.520 --> 00:02:47.490 align:start position:0% know it's a little bit on Twitter but but<00:02:45.970> you<00:02:46.180> know<00:02:46.300> that's<00:02:46.600> scary<00:02:46.720> and<00:02:47.170> and<00:02:47.380> the 00:02:47.490 --> 00:02:47.500 align:start position:0% but you know that's scary and and the 00:02:47.500 --> 00:02:49.470 align:start position:0% but you know that's scary and and the average<00:02:47.830> average<00:02:48.100> well<00:02:48.489> everyone<00:02:48.910> is<00:02:49.150> so<00:02:49.300> big 00:02:49.470 --> 00:02:49.480 align:start position:0% average average well everyone is so big 00:02:49.480 --> 00:02:51.570 align:start position:0% average average well everyone is so big pile<00:02:49.690> of<00:02:49.720> dependencies<00:02:50.350> and<00:02:50.470> every<00:02:50.980> and<00:02:51.280> every 00:02:51.570 --> 00:02:51.580 align:start position:0% pile of dependencies and every and every 00:02:51.580 --> 00:02:54.150 align:start position:0% pile of dependencies and every and every new<00:02:51.880> feature<00:02:52.209> increases<00:02:53.080> the<00:02:53.470> attack<00:02:53.709> service 00:02:54.150 --> 00:02:54.160 align:start position:0% new feature increases the attack service 00:02:54.160 --> 00:02:56.220 align:start position:0% new feature increases the attack service so<00:02:54.520> you're<00:02:54.670> simultaneously<00:02:55.000> furious<00:02:55.959> at<00:02:56.110> your 00:02:56.220 --> 00:02:56.230 align:start position:0% so you're simultaneously furious at your 00:02:56.230 --> 00:02:57.390 align:start position:0% so you're simultaneously furious at your wallets<00:02:56.500> for<00:02:56.620> not<00:02:56.770> having<00:02:57.010> enough<00:02:57.160> features 00:02:57.390 --> 00:02:57.400 align:start position:0% wallets for not having enough features 00:02:57.400 --> 00:02:59.940 align:start position:0% wallets for not having enough features and<00:02:57.850> you<00:02:58.720> should<00:02:58.900> be<00:02:59.019> terrified<00:02:59.560> the<00:02:59.800> more 00:02:59.940 --> 00:02:59.950 align:start position:0% and you should be terrified the more 00:02:59.950 --> 00:03:01.680 align:start position:0% and you should be terrified the more features<00:03:00.340> of<00:03:00.459> all<00:03:00.610> it<00:03:00.730> has<00:03:00.880> because<00:03:01.269> each<00:03:01.480> one 00:03:01.680 --> 00:03:01.690 align:start position:0% features of all it has because each one 00:03:01.690 --> 00:03:03.900 align:start position:0% features of all it has because each one of<00:03:01.780> them<00:03:01.900> is<00:03:02.019> making<00:03:02.380> more<00:03:02.620> vulnerable<00:03:03.130> okay 00:03:03.900 --> 00:03:03.910 align:start position:0% of them is making more vulnerable okay 00:03:03.910 --> 00:03:05.699 align:start position:0% of them is making more vulnerable okay and<00:03:04.420> there's<00:03:04.959> a<00:03:05.080> count<00:03:05.290> management 00:03:05.699 --> 00:03:05.709 align:start position:0% and there's a count management 00:03:05.709 --> 00:03:07.020 align:start position:0% and there's a count management trade-offs<00:03:06.100> of<00:03:06.250> course<00:03:06.459> and<00:03:06.670> we<00:03:06.730> all<00:03:06.850> like 00:03:07.020 --> 00:03:07.030 align:start position:0% trade-offs of course and we all like 00:03:07.030 --> 00:03:08.430 align:start position:0% trade-offs of course and we all like have<00:03:07.209> our<00:03:07.330> favorite<00:03:07.690> ones<00:03:07.870> and<00:03:08.080> like<00:03:08.260> that 00:03:08.430 --> 00:03:08.440 align:start position:0% have our favorite ones and like that 00:03:08.440 --> 00:03:10.500 align:start position:0% have our favorite ones and like that crap<00:03:08.620> on<00:03:08.769> the<00:03:08.860> other<00:03:09.010> ones<00:03:09.310> you<00:03:09.850> know<00:03:09.940> if<00:03:10.090> you 00:03:10.500 --> 00:03:10.510 align:start position:0% crap on the other ones you know if you 00:03:10.510 --> 00:03:12.300 align:start position:0% crap on the other ones you know if you make<00:03:10.630> the<00:03:10.750> keys<00:03:10.930> record<00:03:11.410> that<00:03:11.680> if<00:03:12.040> you<00:03:12.160> make 00:03:12.300 --> 00:03:12.310 align:start position:0% make the keys record that if you make 00:03:12.310 --> 00:03:13.770 align:start position:0% make the keys record that if you make the<00:03:12.400> users<00:03:12.640> require<00:03:12.910> keys<00:03:13.209> remember<00:03:13.660> as 00:03:13.770 --> 00:03:13.780 align:start position:0% the users require keys remember as 00:03:13.780 --> 00:03:15.990 align:start position:0% the users require keys remember as passwords<00:03:14.230> they<00:03:14.380> can<00:03:14.530> just<00:03:14.709> lose<00:03:14.920> them<00:03:15.160> you 00:03:15.990 --> 00:03:16.000 align:start position:0% passwords they can just lose them you 00:03:16.000 --> 00:03:17.520 align:start position:0% passwords they can just lose them you might<00:03:16.150> have<00:03:16.330> some<00:03:16.540> new<00:03:16.720> great<00:03:16.959> contract 00:03:17.520 --> 00:03:17.530 align:start position:0% might have some new great contract 00:03:17.530 --> 00:03:19.470 align:start position:0% might have some new great contract accommodate<00:03:17.980> to<00:03:18.070> get<00:03:18.220> you<00:03:18.430> know<00:03:18.550> you<00:03:19.390> know 00:03:19.470 --> 00:03:19.480 align:start position:0% accommodate to get you know you know 00:03:19.480 --> 00:03:21.330 align:start position:0% accommodate to get you know you know maybe<00:03:19.660> you<00:03:19.840> can<00:03:19.959> get<00:03:20.170> a<00:03:20.200> bird<00:03:20.860> eating<00:03:21.010> dinner 00:03:21.330 --> 00:03:21.340 align:start position:0% maybe you can get a bird eating dinner 00:03:21.340 --> 00:03:24.460 align:start position:0% maybe you can get a bird eating dinner to<00:03:21.519> put<00:03:21.700> their<00:03:21.820> funds<00:03:22.120> in<00:03:22.239> it 00:03:24.460 --> 00:03:24.470 align:start position:0% 00:03:24.470 --> 00:03:30.400 align:start position:0% they<00:03:24.860> are<00:03:27.460> both<00:03:28.460> good<00:03:28.960> wallets<00:03:29.960> just<00:03:30.140> aren't 00:03:30.400 --> 00:03:30.410 align:start position:0% they are both good wallets just aren't 00:03:30.410 --> 00:03:37.390 align:start position:0% they are both good wallets just aren't usable<00:03:30.860> right<00:03:31.480> we<00:03:32.650> got<00:03:33.650> a<00:03:35.980> yeah<00:03:36.980> I'm<00:03:37.130> sorry<00:03:37.370> I 00:03:37.390 --> 00:03:37.400 align:start position:0% usable right we got a yeah I'm sorry I 00:03:37.400 --> 00:03:39.040 align:start position:0% usable right we got a yeah I'm sorry I don't<00:03:37.520> know<00:03:37.640> the<00:03:37.790> wording<00:03:38.120> of<00:03:38.210> that<00:03:38.270> but<00:03:38.540> yeah 00:03:39.040 --> 00:03:39.050 align:start position:0% don't know the wording of that but yeah 00:03:39.050 --> 00:03:40.210 align:start position:0% don't know the wording of that but yeah you<00:03:39.290> want<00:03:39.470> to<00:03:39.530> okay<00:03:39.620> if<00:03:39.800> you<00:03:39.950> want<00:03:40.160> to 00:03:40.210 --> 00:03:40.220 align:start position:0% you want to okay if you want to 00:03:40.220 --> 00:03:42.070 align:start position:0% you want to okay if you want to procedural<00:03:40.760> progressive<00:03:41.390> security<00:03:41.810> you<00:03:41.930> want 00:03:42.070 --> 00:03:42.080 align:start position:0% procedural progressive security you want 00:03:42.080 --> 00:03:43.180 align:start position:0% procedural progressive security you want to<00:03:42.140> be<00:03:42.230> able<00:03:42.290> to<00:03:42.440> say<00:03:42.560> look<00:03:42.800> if<00:03:42.950> you've<00:03:43.070> got 00:03:43.180 --> 00:03:43.190 align:start position:0% to be able to say look if you've got 00:03:43.190 --> 00:03:44.920 align:start position:0% to be able to say look if you've got nothing<00:03:43.340> in<00:03:43.580> your<00:03:43.700> wallet<00:03:44.000> don't<00:03:44.480> back<00:03:44.630> it<00:03:44.660> up 00:03:44.920 --> 00:03:44.930 align:start position:0% nothing in your wallet don't back it up 00:03:44.930 --> 00:03:47.740 align:start position:0% nothing in your wallet don't back it up how<00:03:45.410> easy<00:03:45.710> onboarding<00:03:46.250> all<00:03:46.460> that<00:03:46.640> a<00:03:46.880> seat 00:03:47.740 --> 00:03:47.750 align:start position:0% how easy onboarding all that a seat 00:03:47.750 --> 00:03:49.600 align:start position:0% how easy onboarding all that a seat phrases<00:03:48.230> that<00:03:48.470> are<00:03:48.530> passed<00:03:48.830> and<00:03:49.040> annoying<00:03:49.400> you 00:03:49.600 --> 00:03:49.610 align:start position:0% phrases that are passed and annoying you 00:03:49.610 --> 00:03:50.950 align:start position:0% phrases that are passed and annoying you should<00:03:49.760> have<00:03:49.880> options<00:03:50.420> right<00:03:50.660> you<00:03:50.750> should<00:03:50.930> be 00:03:50.950 --> 00:03:50.960 align:start position:0% should have options right you should be 00:03:50.960 --> 00:03:53.290 align:start position:0% should have options right you should be able<00:03:51.050> to<00:03:51.230> onboard<00:03:52.070> your<00:03:52.430> users<00:03:52.730> as<00:03:52.850> gracefully 00:03:53.290 --> 00:03:53.300 align:start position:0% able to onboard your users as gracefully 00:03:53.300 --> 00:03:55.060 align:start position:0% able to onboard your users as gracefully as<00:03:53.330> you<00:03:53.450> can<00:03:53.600> conceive<00:03:53.990> of<00:03:54.140> and<00:03:54.440> you<00:03:55.010> know 00:03:55.060 --> 00:03:55.070 align:start position:0% as you can conceive of and you know 00:03:55.070 --> 00:03:56.410 align:start position:0% as you can conceive of and you know first<00:03:55.310> trip<00:03:55.580> though<00:03:55.700> is<00:03:55.760> a<00:03:55.850> pain<00:03:56.030> but<00:03:56.270> we've 00:03:56.410 --> 00:03:56.420 align:start position:0% first trip though is a pain but we've 00:03:56.420 --> 00:03:58.000 align:start position:0% first trip though is a pain but we've got<00:03:56.600> solutions<00:03:56.840> for<00:03:57.380> that<00:03:57.560> you<00:03:57.740> know<00:03:57.860> why 00:03:58.000 --> 00:03:58.010 align:start position:0% got solutions for that you know why 00:03:58.010 --> 00:04:00.070 align:start position:0% got solutions for that you know why won't<00:03:58.280> the<00:03:58.490> wallets<00:03:58.970> merge<00:03:59.180> these<00:03:59.600> solutions 00:04:00.070 --> 00:04:00.080 align:start position:0% won't the wallets merge these solutions 00:04:00.080 --> 00:04:02.440 align:start position:0% won't the wallets merge these solutions as<00:04:00.200> fast<00:04:00.410> as<00:04:00.590> they<00:04:00.680> deserve<00:04:00.950> to<00:04:00.980> be<00:04:01.280> and<00:04:02.090> and 00:04:02.440 --> 00:04:02.450 align:start position:0% as fast as they deserve to be and and 00:04:02.450 --> 00:04:04.140 align:start position:0% as fast as they deserve to be and and confirmation<00:04:03.080> screens<00:04:03.350> of<00:04:03.470> course<00:04:03.740> are 00:04:04.140 --> 00:04:04.150 align:start position:0% confirmation screens of course are 00:04:04.150 --> 00:04:06.610 align:start position:0% confirmation screens of course are obnoxious<00:04:05.150> and<00:04:05.330> tedious<00:04:06.080> and<00:04:06.290> while<00:04:06.440> they're 00:04:06.610 --> 00:04:06.620 align:start position:0% obnoxious and tedious and while they're 00:04:06.620 --> 00:04:09.130 align:start position:0% obnoxious and tedious and while they're secure<00:04:07.130> there's<00:04:07.670> so<00:04:08.030> many<00:04:08.360> of<00:04:08.600> them<00:04:08.630> that<00:04:08.780> they 00:04:09.130 --> 00:04:09.140 align:start position:0% secure there's so many of them that they 00:04:09.140 --> 00:04:11.710 align:start position:0% secure there's so many of them that they can<00:04:09.290> lead<00:04:09.500> to<00:04:09.620> user<00:04:09.800> fatigue<00:04:10.070> and<00:04:10.580> even<00:04:11.480> if<00:04:11.600> the 00:04:11.710 --> 00:04:11.720 align:start position:0% can lead to user fatigue and even if the 00:04:11.720 --> 00:04:13.330 align:start position:0% can lead to user fatigue and even if the users<00:04:12.020> are<00:04:12.140> looking<00:04:12.680> at<00:04:12.950> them<00:04:13.070> thick<00:04:13.220> you<00:04:13.310> know 00:04:13.330 --> 00:04:13.340 align:start position:0% users are looking at them thick you know 00:04:13.340 --> 00:04:15.280 align:start position:0% users are looking at them thick you know they're<00:04:13.520> basically<00:04:13.610> unreadable<00:04:14.210> because<00:04:15.050> you 00:04:15.280 --> 00:04:15.290 align:start position:0% they're basically unreadable because you 00:04:15.290 --> 00:04:16.990 align:start position:0% they're basically unreadable because you know<00:04:15.380> you're<00:04:15.590> trying<00:04:15.830> to<00:04:15.950> confirm<00:04:16.400> something 00:04:16.990 --> 00:04:17.000 align:start position:0% know you're trying to confirm something 00:04:17.000 --> 00:04:17.949 align:start position:0% know you're trying to confirm something that<00:04:17.090> a<00:04:17.150> turing-complete 00:04:17.949 --> 00:04:17.959 align:start position:0% that a turing-complete 00:04:17.959 --> 00:04:20.710 align:start position:0% that a turing-complete computer<00:04:18.500> like<00:04:18.799> we<00:04:19.670> cannot<00:04:19.970> anticipate 00:04:20.710 --> 00:04:20.720 align:start position:0% computer like we cannot anticipate 00:04:20.720 --> 00:04:22.030 align:start position:0% computer like we cannot anticipate everything<00:04:21.230> that<00:04:21.380> you've<00:04:21.470> got<00:04:21.650> you<00:04:21.830> just 00:04:22.030 --> 00:04:22.040 align:start position:0% everything that you've got you just 00:04:22.040 --> 00:04:24.790 align:start position:0% everything that you've got you just can't<00:04:22.480> so<00:04:23.480> how<00:04:23.780> do<00:04:23.840> we<00:04:24.050> how<00:04:24.350> do<00:04:24.410> we<00:04:24.530> leverage 00:04:24.790 --> 00:04:24.800 align:start position:0% can't so how do we how do we leverage 00:04:24.800 --> 00:04:28.150 align:start position:0% can't so how do we how do we leverage this<00:04:25.160> big<00:04:26.020> decentralize<00:04:27.020> ecosystem<00:04:27.710> all<00:04:27.890> of 00:04:28.150 --> 00:04:28.160 align:start position:0% this big decentralize ecosystem all of 00:04:28.160 --> 00:04:30.250 align:start position:0% this big decentralize ecosystem all of your<00:04:28.340> creativity<00:04:29.300> in<00:04:29.600> this<00:04:29.690> room<00:04:29.960> and<00:04:30.169> make 00:04:30.250 --> 00:04:30.260 align:start position:0% your creativity in this room and make 00:04:30.260 --> 00:04:32.620 align:start position:0% your creativity in this room and make something<00:04:30.560> that<00:04:30.680> is<00:04:30.710> secure<00:04:31.220> and<00:04:31.460> usable<00:04:32.330> and 00:04:32.620 --> 00:04:32.630 align:start position:0% something that is secure and usable and 00:04:32.630 --> 00:04:34.960 align:start position:0% something that is secure and usable and scale<00:04:33.230> and<00:04:33.650> so<00:04:34.340> that<00:04:34.460> we<00:04:34.520> can<00:04:34.669> all<00:04:34.760> make<00:04:34.910> it 00:04:34.960 --> 00:04:34.970 align:start position:0% scale and so that we can all make it 00:04:34.970 --> 00:04:37.480 align:start position:0% scale and so that we can all make it together<00:04:35.240> and<00:04:35.720> so<00:04:36.020> that<00:04:36.050> we<00:04:36.260> can<00:04:36.290> you<00:04:36.770> solve 00:04:37.480 --> 00:04:37.490 align:start position:0% together and so that we can you solve 00:04:37.490 --> 00:04:41.860 align:start position:0% together and so that we can you solve this<00:04:37.960> so<00:04:38.960> how<00:04:39.140> do<00:04:39.200> we<00:04:39.350> do<00:04:39.620> it<00:04:40.390> well<00:04:41.390> I'm<00:04:41.630> gonna 00:04:41.860 --> 00:04:41.870 align:start position:0% this so how do we do it well I'm gonna 00:04:41.870 --> 00:04:43.990 align:start position:0% this so how do we do it well I'm gonna propose<00:04:42.200> the<00:04:42.470> delegation<00:04:43.280> is<00:04:43.580> a<00:04:43.640> really 00:04:43.990 --> 00:04:44.000 align:start position:0% propose the delegation is a really 00:04:44.000 --> 00:04:47.110 align:start position:0% propose the delegation is a really powerful<00:04:44.180> thing<00:04:44.660> in<00:04:45.230> the<00:04:45.260> hands<00:04:45.650> of<00:04:45.800> a<00:04:45.890> user<00:04:46.120> if 00:04:47.110 --> 00:04:47.120 align:start position:0% powerful thing in the hands of a user if 00:04:47.120 --> 00:04:50.770 align:start position:0% powerful thing in the hands of a user if you<00:04:47.330> do<00:04:47.510> delegation<00:04:48.290> right<00:04:48.560> it's<00:04:49.490> you<00:04:50.390> don't 00:04:50.770 --> 00:04:50.780 align:start position:0% you do delegation right it's you don't 00:04:50.780 --> 00:04:52.330 align:start position:0% you do delegation right it's you don't have<00:04:50.990> any<00:04:51.169> authority<00:04:51.290> by<00:04:51.740> default<00:04:52.100> you<00:04:52.190> have<00:04:52.310> a 00:04:52.330 --> 00:04:52.340 align:start position:0% have any authority by default you have a 00:04:52.340 --> 00:04:54.970 align:start position:0% have any authority by default you have a nice<00:04:52.880> peaceful<00:04:53.390> safe<00:04:54.080> place<00:04:54.410> to<00:04:54.620> start<00:04:54.800> you've 00:04:54.970 --> 00:04:54.980 align:start position:0% nice peaceful safe place to start you've 00:04:54.980 --> 00:04:56.920 align:start position:0% nice peaceful safe place to start you've got<00:04:55.010> a<00:04:55.160> wallet<00:04:55.400> it<00:04:55.760> doesn't<00:04:56.450> do<00:04:56.540> anything<00:04:56.750> it 00:04:56.920 --> 00:04:56.930 align:start position:0% got a wallet it doesn't do anything it 00:04:56.930 --> 00:04:58.390 align:start position:0% got a wallet it doesn't do anything it doesn't<00:04:57.110> risk<00:04:57.380> your<00:04:57.590> funds<00:04:57.800> it's 00:04:58.390 --> 00:04:58.400 align:start position:0% doesn't risk your funds it's 00:04:58.400 --> 00:05:03.159 align:start position:0% doesn't risk your funds it's conservative<00:04:58.990> but<00:04:59.990> you're<00:05:00.110> safe<00:05:01.300> but<00:05:02.300> with 00:05:03.159 --> 00:05:03.169 align:start position:0% conservative but you're safe but with 00:05:03.169 --> 00:05:06.760 align:start position:0% conservative but you're safe but with human<00:05:03.500> readable<00:05:03.860> messengers<00:05:04.460> you<00:05:04.640> can<00:05:05.770> have 00:05:06.760 --> 00:05:06.770 align:start position:0% human readable messengers you can have 00:05:06.770 --> 00:05:09.400 align:start position:0% human readable messengers you can have machine<00:05:07.310> enforceable<00:05:08.060> authorities<00:05:08.630> that 00:05:09.400 --> 00:05:09.410 align:start position:0% machine enforceable authorities that 00:05:09.410 --> 00:05:11.980 align:start position:0% machine enforceable authorities that themselves<00:05:09.860> can<00:05:10.460> be<00:05:10.550> delegated<00:05:10.880> allowing<00:05:11.720> for 00:05:11.980 --> 00:05:11.990 align:start position:0% themselves can be delegated allowing for 00:05:11.990 --> 00:05:15.480 align:start position:0% themselves can be delegated allowing for large<00:05:12.320> networks<00:05:13.010> of<00:05:13.400> transitive 00:05:15.480 --> 00:05:15.490 align:start position:0% large networks of transitive 00:05:15.490 --> 00:05:17.290 align:start position:0% large networks of transitive extensibility 00:05:17.290 --> 00:05:17.300 align:start position:0% extensibility 00:05:17.300 --> 00:05:20.980 align:start position:0% extensibility system<00:05:18.580> to<00:05:19.580> facilitate<00:05:20.210> this<00:05:20.389> you<00:05:20.750> might<00:05:20.870> have 00:05:20.980 --> 00:05:20.990 align:start position:0% system to facilitate this you might have 00:05:20.990 --> 00:05:22.510 align:start position:0% system to facilitate this you might have seen<00:05:21.169> in<00:05:21.259> the<00:05:21.319> last<00:05:21.349> couple<00:05:21.650> months<00:05:21.889> we<00:05:22.159> really 00:05:22.510 --> 00:05:22.520 align:start position:0% seen in the last couple months we really 00:05:22.520 --> 00:05:24.159 align:start position:0% seen in the last couple months we really said<00:05:22.759> the<00:05:22.940> IP<00:05:23.150> it's<00:05:23.419> in<00:05:23.539> the<00:05:23.629> draft<00:05:23.900> stage 00:05:24.159 --> 00:05:24.169 align:start position:0% said the IP it's in the draft stage 00:05:24.169 --> 00:05:26.649 align:start position:0% said the IP it's in the draft stage you're<00:05:24.440> welcome<00:05:24.710> to<00:05:24.830> he<00:05:25.610> could<00:05:25.819> help<00:05:26.479> improve 00:05:26.649 --> 00:05:26.659 align:start position:0% you're welcome to he could help improve 00:05:26.659 --> 00:05:27.550 align:start position:0% you're welcome to he could help improve it 00:05:27.550 --> 00:05:27.560 align:start position:0% it 00:05:27.560 --> 00:05:30.070 align:start position:0% it it's<00:05:27.860> our<00:05:28.009> wallet<00:05:28.340> permissions<00:05:28.729> API<00:05:28.930> it's<00:05:29.930> a 00:05:30.070 --> 00:05:30.080 align:start position:0% it's our wallet permissions API it's a 00:05:30.080 --> 00:05:33.070 align:start position:0% it's our wallet permissions API it's a method<00:05:30.349> by<00:05:30.620> which<00:05:30.650> we<00:05:30.879> propose<00:05:31.879> to<00:05:32.300> suggest 00:05:33.070 --> 00:05:33.080 align:start position:0% method by which we propose to suggest 00:05:33.080 --> 00:05:35.110 align:start position:0% method by which we propose to suggest users<00:05:33.409> log<00:05:33.620> into<00:05:33.919> websites<00:05:34.039> with<00:05:34.610> a<00:05:34.639> series<00:05:35.060> of 00:05:35.110 --> 00:05:35.120 align:start position:0% users log into websites with a series of 00:05:35.120 --> 00:05:36.939 align:start position:0% users log into websites with a series of machine<00:05:35.599> enforceable<00:05:36.319> permissions<00:05:36.770> that<00:05:36.889> are 00:05:36.939 --> 00:05:36.949 align:start position:0% machine enforceable permissions that are 00:05:36.949 --> 00:05:39.129 align:start position:0% machine enforceable permissions that are human<00:05:37.400> readable<00:05:37.550> -<00:05:37.970> and<00:05:38.270> so<00:05:38.960> we're 00:05:39.129 --> 00:05:39.139 align:start position:0% human readable - and so we're 00:05:39.139 --> 00:05:40.570 align:start position:0% human readable - and so we're increasingly<00:05:39.620> making<00:05:39.979> that<00:05:40.099> Masco<00:05:40.370> place 00:05:40.570 --> 00:05:40.580 align:start position:0% increasingly making that Masco place 00:05:40.580 --> 00:05:42.640 align:start position:0% increasingly making that Masco place where<00:05:40.789> it<00:05:41.150> grants<00:05:41.539> no<00:05:41.720> authority<00:05:42.169> by<00:05:42.259> default 00:05:42.640 --> 00:05:42.650 align:start position:0% where it grants no authority by default 00:05:42.650 --> 00:05:44.680 align:start position:0% where it grants no authority by default keeps<00:05:43.009> users<00:05:43.190> perfectly<00:05:43.759> safe<00:05:43.970> but<00:05:44.509> gives 00:05:44.680 --> 00:05:44.690 align:start position:0% keeps users perfectly safe but gives 00:05:44.690 --> 00:05:46.629 align:start position:0% keeps users perfectly safe but gives them<00:05:44.870> the<00:05:44.960> power<00:05:44.990> to<00:05:45.259> grant<00:05:45.710> authority<00:05:45.889> as 00:05:46.629 --> 00:05:46.639 align:start position:0% them the power to grant authority as 00:05:46.639 --> 00:05:49.240 align:start position:0% them the power to grant authority as they<00:05:46.879> see<00:05:46.940> fit<00:05:47.440> the<00:05:48.440> API<00:05:48.740> looks<00:05:48.979> something 00:05:49.240 --> 00:05:49.250 align:start position:0% they see fit the API looks something 00:05:49.250 --> 00:05:51.670 align:start position:0% they see fit the API looks something like<00:05:49.370> this<00:05:49.759> you've<00:05:50.419> got<00:05:50.569> an<00:05:50.659> RPC<00:05:50.960> method<00:05:51.289> calls 00:05:51.670 --> 00:05:51.680 align:start position:0% like this you've got an RPC method calls 00:05:51.680 --> 00:05:53.439 align:start position:0% like this you've got an RPC method calls reflect<00:05:52.159> permissions<00:05:52.610> and<00:05:52.789> the<00:05:52.969> parameters 00:05:53.439 --> 00:05:53.449 align:start position:0% reflect permissions and the parameters 00:05:53.449 --> 00:05:55.230 align:start position:0% reflect permissions and the parameters is<00:05:53.629> an<00:05:53.750> object<00:05:54.169> or<00:05:54.469> you<00:05:54.710> request<00:05:55.069> the 00:05:55.230 --> 00:05:55.240 align:start position:0% is an object or you request the 00:05:55.240 --> 00:05:57.610 align:start position:0% is an object or you request the functions<00:05:56.240> you<00:05:56.300> want<00:05:56.389> access<00:05:56.810> to<00:05:56.990> which<00:05:57.469> each 00:05:57.610 --> 00:05:57.620 align:start position:0% functions you want access to which each 00:05:57.620 --> 00:06:00.189 align:start position:0% functions you want access to which each has<00:05:57.830> a<00:05:57.860> configuration<00:05:58.280> option<00:05:58.849> those<00:05:59.599> options 00:06:00.189 --> 00:06:00.199 align:start position:0% has a configuration option those options 00:06:00.199 --> 00:06:03.279 align:start position:0% has a configuration option those options can<00:06:00.469> include<00:06:01.270> limitations<00:06:02.270> self-imposed<00:06:03.110> of 00:06:03.279 --> 00:06:03.289 align:start position:0% can include limitations self-imposed of 00:06:03.289 --> 00:06:04.629 align:start position:0% can include limitations self-imposed of maybe<00:06:03.469> get<00:06:03.680> allowance<00:06:03.860> that<00:06:04.219> you<00:06:04.340> need<00:06:04.490> the 00:06:04.629 --> 00:06:04.639 align:start position:0% maybe get allowance that you need the 00:06:04.639 --> 00:06:07.270 align:start position:0% maybe get allowance that you need the duration<00:06:05.150> there's<00:06:06.139> really<00:06:06.830> the<00:06:07.069> sky's<00:06:07.250> the 00:06:07.270 --> 00:06:07.280 align:start position:0% duration there's really the sky's the 00:06:07.280 --> 00:06:08.920 align:start position:0% duration there's really the sky's the limit<00:06:07.400> in<00:06:07.669> terms<00:06:07.699> of<00:06:07.909> the<00:06:08.030> options<00:06:08.599> that<00:06:08.810> we 00:06:08.920 --> 00:06:08.930 align:start position:0% limit in terms of the options that we 00:06:08.930 --> 00:06:10.600 align:start position:0% limit in terms of the options that we might<00:06:08.990> extend<00:06:09.440> her<00:06:09.590> and<00:06:09.740> so<00:06:09.860> this<00:06:10.009> you<00:06:10.520> know 00:06:10.600 --> 00:06:10.610 align:start position:0% might extend her and so this you know 00:06:10.610 --> 00:06:13.200 align:start position:0% might extend her and so this you know really<00:06:10.969> just<00:06:11.000> the<00:06:11.180> beginning<00:06:11.569> of<00:06:11.629> a<00:06:11.780> standard 00:06:13.200 --> 00:06:13.210 align:start position:0% really just the beginning of a standard 00:06:13.210 --> 00:06:15.700 align:start position:0% really just the beginning of a standard so<00:06:14.210> well<00:06:14.569> while<00:06:14.960> the<00:06:15.020> permissions<00:06:15.469> are<00:06:15.560> we 00:06:15.700 --> 00:06:15.710 align:start position:0% so well while the permissions are we 00:06:15.710 --> 00:06:17.649 align:start position:0% so well while the permissions are we interested<00:06:16.009> in<00:06:16.250> adding<00:06:16.819> why<00:06:17.150> why<00:06:17.419> are<00:06:17.479> we 00:06:17.649 --> 00:06:17.659 align:start position:0% interested in adding why why are we 00:06:17.659 --> 00:06:19.240 align:start position:0% interested in adding why why are we pursuing<00:06:17.840> this<00:06:18.169> what<00:06:18.560> do<00:06:18.620> we<00:06:18.710> think<00:06:18.949> we<00:06:19.099> can 00:06:19.240 --> 00:06:19.250 align:start position:0% pursuing this what do we think we can 00:06:19.250 --> 00:06:20.589 align:start position:0% pursuing this what do we think we can really<00:06:19.430> in<00:06:19.639> because<00:06:19.819> we've<00:06:19.940> been<00:06:20.030> doing<00:06:20.360> a<00:06:20.449> lot 00:06:20.589 --> 00:06:20.599 align:start position:0% really in because we've been doing a lot 00:06:20.599 --> 00:06:22.029 align:start position:0% really in because we've been doing a lot of<00:06:20.629> interviews<00:06:21.050> with<00:06:21.080> that<00:06:21.380> builders<00:06:21.680> we're 00:06:22.029 --> 00:06:22.039 align:start position:0% of interviews with that builders we're 00:06:22.039 --> 00:06:24.790 align:start position:0% of interviews with that builders we're not<00:06:22.159> just<00:06:22.370> doing<00:06:22.460> this<00:06:22.669> in<00:06:22.819> a<00:06:22.849> in<00:06:23.120> a<00:06:23.240> box<00:06:23.800> so 00:06:24.790 --> 00:06:24.800 align:start position:0% not just doing this in a in a box so 00:06:24.800 --> 00:06:26.499 align:start position:0% not just doing this in a in a box so what<00:06:25.009> are<00:06:25.099> the<00:06:25.159> most<00:06:25.310> useful<00:06:25.550> ones<00:06:25.849> well 00:06:26.499 --> 00:06:26.509 align:start position:0% what are the most useful ones well 00:06:26.509 --> 00:06:30.700 align:start position:0% what are the most useful ones well people<00:06:27.020> want<00:06:27.380> want<00:06:27.889> privacy<00:06:28.599> people<00:06:29.599> want<00:06:29.779> you 00:06:30.700 --> 00:06:30.710 align:start position:0% people want want privacy people want you 00:06:30.710 --> 00:06:32.019 align:start position:0% people want want privacy people want you know<00:06:30.740> you<00:06:30.979> don't<00:06:31.130> want<00:06:31.279> to<00:06:31.370> ask<00:06:31.550> users<00:06:32.000> to 00:06:32.019 --> 00:06:32.029 align:start position:0% know you don't want to ask users to 00:06:32.029 --> 00:06:33.370 align:start position:0% know you don't want to ask users to switch<00:06:32.270> the<00:06:32.419> network<00:06:32.690> every<00:06:32.930> time<00:06:33.110> you<00:06:33.229> log<00:06:33.349> in 00:06:33.370 --> 00:06:33.380 align:start position:0% switch the network every time you log in 00:06:33.380 --> 00:06:34.689 align:start position:0% switch the network every time you log in it<00:06:33.650> would<00:06:33.770> make<00:06:33.889> a<00:06:33.919> lot<00:06:34.039> of<00:06:34.159> sense<00:06:34.340> to<00:06:34.520> make 00:06:34.689 --> 00:06:34.699 align:start position:0% it would make a lot of sense to make 00:06:34.699 --> 00:06:37.180 align:start position:0% it would make a lot of sense to make that<00:06:34.849> part<00:06:35.090> of<00:06:35.150> the<00:06:35.270> login<00:06:35.630> flow<00:06:35.870> a<00:06:36.710> lot<00:06:37.130> of 00:06:37.180 --> 00:06:37.190 align:start position:0% that part of the login flow a lot of 00:06:37.190 --> 00:06:39.010 align:start position:0% that part of the login flow a lot of apps<00:06:37.580> use<00:06:37.759> a<00:06:37.849> signature<00:06:38.330> when<00:06:38.659> they<00:06:38.750> first 00:06:39.010 --> 00:06:39.020 align:start position:0% apps use a signature when they first 00:06:39.020 --> 00:06:41.649 align:start position:0% apps use a signature when they first start<00:06:39.319> but<00:06:39.529> also<00:06:40.279> why<00:06:40.610> not<00:06:40.819> delegated<00:06:41.330> key<00:06:41.509> to 00:06:41.649 --> 00:06:41.659 align:start position:0% start but also why not delegated key to 00:06:41.659 --> 00:06:43.779 align:start position:0% start but also why not delegated key to give<00:06:42.080> permission<00:06:42.349> to<00:06:42.770> do<00:06:43.190> signatures<00:06:43.610> on<00:06:43.729> the 00:06:43.779 --> 00:06:43.789 align:start position:0% give permission to do signatures on the 00:06:43.789 --> 00:06:46.149 align:start position:0% give permission to do signatures on the user's<00:06:44.029> that<00:06:44.180> happening<00:06:44.620> decryption<00:06:45.620> you 00:06:46.149 --> 00:06:46.159 align:start position:0% user's that happening decryption you 00:06:46.159 --> 00:06:48.070 align:start position:0% user's that happening decryption you know<00:06:46.250> the<00:06:46.400> ability<00:06:46.759> to<00:06:46.789> establish<00:06:47.599> an<00:06:47.719> intent 00:06:48.070 --> 00:06:48.080 align:start position:0% know the ability to establish an intent 00:06:48.080 --> 00:06:49.959 align:start position:0% know the ability to establish an intent encrypted<00:06:48.560> channel<00:06:48.860> within<00:06:49.009> at<00:06:49.279> that<00:06:49.430> it 00:06:49.959 --> 00:06:49.969 align:start position:0% encrypted channel within at that it 00:06:49.969 --> 00:06:51.519 align:start position:0% encrypted channel within at that it would<00:06:50.090> be<00:06:50.180> the<00:06:50.270> beginning<00:06:50.690> of<00:06:50.810> like<00:06:51.020> truly 00:06:51.519 --> 00:06:51.529 align:start position:0% would be the beginning of like truly 00:06:51.529 --> 00:06:54.279 align:start position:0% would be the beginning of like truly private<00:06:51.800> apps<00:06:52.300> we<00:06:53.300> can<00:06:53.509> have<00:06:53.900> token 00:06:54.279 --> 00:06:54.289 align:start position:0% private apps we can have token 00:06:54.289 --> 00:06:55.779 align:start position:0% private apps we can have token management<00:06:54.379> we<00:06:54.949> couldn't<00:06:55.219> decentralized 00:06:55.779 --> 00:06:55.789 align:start position:0% management we couldn't decentralized 00:06:55.789 --> 00:06:57.369 align:start position:0% management we couldn't decentralized route<00:06:56.000> and<00:06:56.150> then<00:06:56.240> each<00:06:56.419> wallet<00:06:56.659> having<00:06:57.050> a<00:06:57.169> a 00:06:57.369 --> 00:06:57.379 align:start position:0% route and then each wallet having a a 00:06:57.379 --> 00:06:59.300 align:start position:0% route and then each wallet having a a centralized<00:06:58.039> repository<00:06:58.099> where<00:06:58.849> it 00:06:59.300 --> 00:06:59.310 align:start position:0% centralized repository where it 00:06:59.310 --> 00:07:01.879 align:start position:0% centralized repository where it what<00:06:59.430> tokens<00:06:59.850> are<00:06:59.940> legitimate<00:07:00.420> you<00:07:00.960> could<00:07:01.200> opt 00:07:01.879 --> 00:07:01.889 align:start position:0% what tokens are legitimate you could opt 00:07:01.889 --> 00:07:04.100 align:start position:0% what tokens are legitimate you could opt into<00:07:02.190> whatever<00:07:02.610> kind<00:07:03.030> of<00:07:03.150> authority<00:07:03.870> for<00:07:04.050> that 00:07:04.100 --> 00:07:04.110 align:start position:0% into whatever kind of authority for that 00:07:04.110 --> 00:07:06.200 align:start position:0% into whatever kind of authority for that you<00:07:04.380> need<00:07:04.590> you<00:07:04.710> perceive<00:07:05.100> spending<00:07:05.940> limits 00:07:06.200 --> 00:07:06.210 align:start position:0% you need you perceive spending limits 00:07:06.210 --> 00:07:10.520 align:start position:0% you need you perceive spending limits obviously<00:07:06.770> and<00:07:07.770> and<00:07:08.370> what<00:07:08.550> else<00:07:09.110> what<00:07:10.110> do<00:07:10.380> we 00:07:10.520 --> 00:07:10.530 align:start position:0% obviously and and what else what do we 00:07:10.530 --> 00:07:13.310 align:start position:0% obviously and and what else what do we think<00:07:10.800> is<00:07:11.010> maybe<00:07:11.310> the<00:07:11.730> single<00:07:12.270> most<00:07:12.660> important 00:07:13.310 --> 00:07:13.320 align:start position:0% think is maybe the single most important 00:07:13.320 --> 00:07:14.659 align:start position:0% think is maybe the single most important permission<00:07:13.800> and<00:07:13.980> the<00:07:14.070> thing<00:07:14.250> that<00:07:14.280> I'm<00:07:14.520> like 00:07:14.659 --> 00:07:14.669 align:start position:0% permission and the thing that I'm like 00:07:14.669 --> 00:07:16.430 align:start position:0% permission and the thing that I'm like really<00:07:14.910> excited<00:07:15.510> to<00:07:15.630> kind<00:07:15.780> of<00:07:15.900> share<00:07:16.139> with<00:07:16.290> you 00:07:16.430 --> 00:07:16.440 align:start position:0% really excited to kind of share with you 00:07:16.440 --> 00:07:18.530 align:start position:0% really excited to kind of share with you guys<00:07:16.470> today<00:07:16.620> the<00:07:17.370> thing<00:07:17.580> we<00:07:17.700> think<00:07:17.880> close<00:07:18.180> the 00:07:18.530 --> 00:07:18.540 align:start position:0% guys today the thing we think close the 00:07:18.540 --> 00:07:20.540 align:start position:0% guys today the thing we think close the loop<00:07:18.750> the<00:07:19.350> thing<00:07:19.530> we<00:07:19.650> just<00:07:19.680> renamed<00:07:20.220> five 00:07:20.540 --> 00:07:20.550 align:start position:0% loop the thing we just renamed five 00:07:20.550 --> 00:07:22.070 align:start position:0% loop the thing we just renamed five minutes<00:07:21.030> before<00:07:21.210> this<00:07:21.450> thing<00:07:21.510> goes<00:07:21.810> we<00:07:21.930> got<00:07:22.020> a 00:07:22.070 --> 00:07:22.080 align:start position:0% minutes before this thing goes we got a 00:07:22.080 --> 00:07:24.170 align:start position:0% minutes before this thing goes we got a new<00:07:22.230> traffic<00:07:22.500> thanks<00:07:23.220> Christian 00:07:24.170 --> 00:07:24.180 align:start position:0% new traffic thanks Christian 00:07:24.180 --> 00:07:26.720 align:start position:0% new traffic thanks Christian the<00:07:24.480> permission<00:07:24.810> to<00:07:24.990> add<00:07:25.230> permissions<00:07:25.730> which 00:07:26.720 --> 00:07:26.730 align:start position:0% the permission to add permissions which 00:07:26.730 --> 00:07:32.450 align:start position:0% the permission to add permissions which we<00:07:26.940> call<00:07:27.770> the<00:07:28.770> Damascus<00:07:29.310> snaps<00:07:31.250> this<00:07:32.250> is<00:07:32.400> the 00:07:32.450 --> 00:07:32.460 align:start position:0% we call the Damascus snaps this is the 00:07:32.460 --> 00:07:33.860 align:start position:0% we call the Damascus snaps this is the most<00:07:32.820> plug-in<00:07:33.090> system<00:07:33.360> about<00:07:33.480> five<00:07:33.690> minutes 00:07:33.860 --> 00:07:33.870 align:start position:0% most plug-in system about five minutes 00:07:33.870 --> 00:07:41.950 align:start position:0% most plug-in system about five minutes to<00:07:34.020> go<00:07:34.110> it<00:07:34.260> snaps<00:07:34.530> it's<00:07:34.770> awesome<00:07:39.110> thank<00:07:40.110> you<00:07:40.490> so 00:07:41.950 --> 00:07:41.960 align:start position:0% to go it snaps it's awesome thank you so 00:07:41.960 --> 00:07:49.090 align:start position:0% to go it snaps it's awesome thank you so so<00:07:42.960> what<00:07:43.140> is<00:07:43.230> it 00:07:49.090 --> 00:07:49.100 align:start position:0% 00:07:49.100 --> 00:07:52.640 align:start position:0% what<00:07:50.100> flick<00:07:50.280> on<00:07:50.430> Zack<00:07:50.610> it's<00:07:51.540> just<00:07:51.690> written<00:07:51.930> you 00:07:52.640 --> 00:07:52.650 align:start position:0% what flick on Zack it's just written you 00:07:52.650 --> 00:07:54.469 align:start position:0% what flick on Zack it's just written you can<00:07:52.830> suggest<00:07:53.040> someone<00:07:53.370> adds<00:07:53.700> to<00:07:53.970> their<00:07:54.120> wallet 00:07:54.469 --> 00:07:54.479 align:start position:0% can suggest someone adds to their wallet 00:07:54.479 --> 00:07:56.900 align:start position:0% can suggest someone adds to their wallet it's<00:07:54.690> JavaScript<00:07:55.220> it's<00:07:56.220> a<00:07:56.310> script<00:07:56.610> that<00:07:56.669> can 00:07:56.900 --> 00:07:56.910 align:start position:0% it's JavaScript it's a script that can 00:07:56.910 --> 00:07:58.760 align:start position:0% it's JavaScript it's a script that can ask<00:07:57.210> for<00:07:57.510> permissions<00:07:57.900> in<00:07:58.020> the<00:07:58.110> same<00:07:58.320> format 00:07:58.760 --> 00:07:58.770 align:start position:0% ask for permissions in the same format 00:07:58.770 --> 00:08:01.940 align:start position:0% ask for permissions in the same format that<00:07:58.800> adopt<00:07:59.220> can<00:07:59.630> this<00:08:00.630> script<00:08:00.960> gets<00:08:01.229> no<00:08:01.590> other 00:08:01.940 --> 00:08:01.950 align:start position:0% that adopt can this script gets no other 00:08:01.950 --> 00:08:03.680 align:start position:0% that adopt can this script gets no other authorities<00:08:02.729> except<00:08:03.090> for<00:08:03.240> what<00:08:03.390> the<00:08:03.510> user 00:08:03.680 --> 00:08:03.690 align:start position:0% authorities except for what the user 00:08:03.690 --> 00:08:06.380 align:start position:0% authorities except for what the user explicitly<00:08:04.290> consents<00:08:05.160> to<00:08:05.250> and<00:08:05.790> this<00:08:06.120> is<00:08:06.210> made 00:08:06.380 --> 00:08:06.390 align:start position:0% explicitly consents to and this is made 00:08:06.390 --> 00:08:08.659 align:start position:0% explicitly consents to and this is made possible<00:08:06.660> by<00:08:07.140> the<00:08:07.200> great<00:08:07.500> work<00:08:07.710> metaphoric<00:08:08.460> on 00:08:08.659 --> 00:08:08.669 align:start position:0% possible by the great work metaphoric on 00:08:08.669 --> 00:08:10.580 align:start position:0% possible by the great work metaphoric on their<00:08:08.880> secure<00:08:09.240> ethnic<00:08:09.810> privilege<00:08:10.050> project 00:08:10.580 --> 00:08:10.590 align:start position:0% their secure ethnic privilege project 00:08:10.590 --> 00:08:12.590 align:start position:0% their secure ethnic privilege project which<00:08:10.770> allows<00:08:11.040> us<00:08:11.250> to<00:08:11.280> basically<00:08:12.000> evaluate 00:08:12.590 --> 00:08:12.600 align:start position:0% which allows us to basically evaluate 00:08:12.600 --> 00:08:15.980 align:start position:0% which allows us to basically evaluate with<00:08:13.470> very<00:08:13.770> explicit<00:08:14.220> and<00:08:14.640> dominance<00:08:15.120> now<00:08:15.479> you 00:08:15.980 --> 00:08:15.990 align:start position:0% with very explicit and dominance now you 00:08:15.990 --> 00:08:17.480 align:start position:0% with very explicit and dominance now you know<00:08:16.110> there's<00:08:16.289> obviously<00:08:16.680> caveats<00:08:17.190> you<00:08:17.370> know 00:08:17.480 --> 00:08:17.490 align:start position:0% know there's obviously caveats you know 00:08:17.490 --> 00:08:20.120 align:start position:0% know there's obviously caveats you know security<00:08:18.180> is<00:08:18.510> is<00:08:18.750> an<00:08:19.020> ongoing<00:08:19.200> process<00:08:19.680> it's 00:08:20.120 --> 00:08:20.130 align:start position:0% security is is an ongoing process it's 00:08:20.130 --> 00:08:21.620 align:start position:0% security is is an ongoing process it's never<00:08:20.310> perfect<00:08:20.610> so<00:08:21.000> we're<00:08:21.150> gonna<00:08:21.240> have<00:08:21.479> like 00:08:21.620 --> 00:08:21.630 align:start position:0% never perfect so we're gonna have like 00:08:21.630 --> 00:08:24.500 align:start position:0% never perfect so we're gonna have like strong<00:08:22.320> user<00:08:22.590> cautions<00:08:23.550> or<00:08:23.729> especially<00:08:24.060> early 00:08:24.500 --> 00:08:24.510 align:start position:0% strong user cautions or especially early 00:08:24.510 --> 00:08:26.450 align:start position:0% strong user cautions or especially early on<00:08:24.539> into<00:08:24.900> the<00:08:24.990> system<00:08:25.380> but<00:08:25.950> we<00:08:26.160> think<00:08:26.310> that 00:08:26.450 --> 00:08:26.460 align:start position:0% on into the system but we think that 00:08:26.460 --> 00:08:28.550 align:start position:0% on into the system but we think that this<00:08:26.580> is<00:08:26.789> the<00:08:27.479> the<00:08:27.780> kind<00:08:28.020> of<00:08:28.080> path<00:08:28.260> that<00:08:28.470> we 00:08:28.550 --> 00:08:28.560 align:start position:0% this is the the kind of path that we 00:08:28.560 --> 00:08:32.450 align:start position:0% this is the the kind of path that we believe<00:08:28.770> is<00:08:28.860> very<00:08:29.130> right<00:08:29.280> to<00:08:29.460> pursue<00:08:30.380> and<00:08:31.460> the 00:08:32.450 --> 00:08:32.460 align:start position:0% believe is very right to pursue and the 00:08:32.460 --> 00:08:35.690 align:start position:0% believe is very right to pursue and the plugins<00:08:33.210> can<00:08:33.479> then<00:08:33.690> provide<00:08:34.159> api's<00:08:35.159> to<00:08:35.460> every 00:08:35.690 --> 00:08:35.700 align:start position:0% plugins can then provide api's to every 00:08:35.700 --> 00:08:38.280 align:start position:0% plugins can then provide api's to every website<00:08:35.909> that<00:08:36.150> user<00:08:36.510> visits 00:08:38.280 --> 00:08:38.290 align:start position:0% website that user visits 00:08:38.290 --> 00:08:42.330 align:start position:0% website that user visits yeah<00:08:38.800> that's<00:08:39.400> what<00:08:39.640> that<00:08:39.790> was<00:08:39.910> that<00:08:40.060> Luther<00:08:40.360> so 00:08:42.330 --> 00:08:42.340 align:start position:0% yeah that's what that was that Luther so 00:08:42.340 --> 00:08:44.850 align:start position:0% yeah that's what that was that Luther so so<00:08:42.729> here's<00:08:42.970> security<00:08:43.419> IP<00:08:43.570> 2255<00:08:44.500> the<00:08:44.650> next 00:08:44.850 --> 00:08:44.860 align:start position:0% so here's security IP 2255 the next 00:08:44.860 --> 00:08:47.340 align:start position:0% so here's security IP 2255 the next generation<00:08:45.370> of<00:08:45.490> the<00:08:45.700> developer<00:08:46.330> missions<00:08:46.660> now 00:08:47.340 --> 00:08:47.350 align:start position:0% generation of the developer missions now 00:08:47.350 --> 00:08:49.260 align:start position:0% generation of the developer missions now one<00:08:48.070> of<00:08:48.100> the<00:08:48.310> wallet<00:08:48.610> permissions<00:08:49.000> you<00:08:49.090> can 00:08:49.260 --> 00:08:49.270 align:start position:0% one of the wallet permissions you can 00:08:49.270 --> 00:08:50.310 align:start position:0% one of the wallet permissions you can request<00:08:49.480> it's<00:08:49.840> this<00:08:49.990> kind<00:08:50.170> of<00:08:50.260> weird 00:08:50.310 --> 00:08:50.320 align:start position:0% request it's this kind of weird 00:08:50.320 --> 00:08:52.770 align:start position:0% request it's this kind of weird namespace<00:08:51.190> thing<00:08:51.460> where<00:08:52.060> you<00:08:52.240> say<00:08:52.450> you<00:08:52.510> want 00:08:52.770 --> 00:08:52.780 align:start position:0% namespace thing where you say you want 00:08:52.780 --> 00:08:54.840 align:start position:0% namespace thing where you say you want wallet<00:08:53.140> plugin<00:08:53.620> and<00:08:53.800> then<00:08:54.040> there's<00:08:54.430> a<00:08:54.520> domain 00:08:54.840 --> 00:08:54.850 align:start position:0% wallet plugin and then there's a domain 00:08:54.850 --> 00:08:56.880 align:start position:0% wallet plugin and then there's a domain stream<00:08:55.240> in<00:08:55.750> this<00:08:55.840> case<00:08:56.050> I<00:08:56.170> made<00:08:56.350> a<00:08:56.380> plasma 00:08:56.880 --> 00:08:56.890 align:start position:0% stream in this case I made a plasma 00:08:56.890 --> 00:08:59.040 align:start position:0% stream in this case I made a plasma dotty<00:08:57.070> let's<00:08:57.610> say<00:08:57.790> that<00:08:58.000> plasma<00:08:58.480> body<00:08:58.660> is<00:08:58.990> a 00:08:59.040 --> 00:08:59.050 align:start position:0% dotty let's say that plasma body is a 00:08:59.050 --> 00:09:02.190 align:start position:0% dotty let's say that plasma body is a pointer<00:08:59.530> to<00:08:59.560> an<00:08:59.800> IPS<00:09:00.130> ipfs<00:09:01.120> file<00:09:01.360> which<00:09:01.990> is<00:09:02.170> a 00:09:02.190 --> 00:09:02.200 align:start position:0% pointer to an IPS ipfs file which is a 00:09:02.200 --> 00:09:04.350 align:start position:0% pointer to an IPS ipfs file which is a plugin<00:09:02.620> bundle<00:09:03.070> we'll<00:09:03.580> learn<00:09:03.880> a<00:09:04.030> little<00:09:04.270> bit 00:09:04.350 --> 00:09:04.360 align:start position:0% plugin bundle we'll learn a little bit 00:09:04.360 --> 00:09:06.960 align:start position:0% plugin bundle we'll learn a little bit about<00:09:04.420> that<00:09:04.720> in<00:09:04.810> a<00:09:04.900> minute<00:09:05.100> now<00:09:06.100> when<00:09:06.670> the<00:09:06.790> user 00:09:06.960 --> 00:09:06.970 align:start position:0% about that in a minute now when the user 00:09:06.970 --> 00:09:09.210 align:start position:0% about that in a minute now when the user sees<00:09:07.540> that<00:09:07.720> they<00:09:07.960> get<00:09:08.140> a<00:09:08.170> confirmation<00:09:08.680> just 00:09:09.210 --> 00:09:09.220 align:start position:0% sees that they get a confirmation just 00:09:09.220 --> 00:09:11.040 align:start position:0% sees that they get a confirmation just like<00:09:09.820> a<00:09:09.850> normal<00:09:10.030> login<00:09:10.480> screen<00:09:10.750> but<00:09:10.870> one<00:09:11.020> of 00:09:11.040 --> 00:09:11.050 align:start position:0% like a normal login screen but one of 00:09:11.050 --> 00:09:12.930 align:start position:0% like a normal login screen but one of the<00:09:11.170> permissions<00:09:11.620> would<00:09:11.860> be<00:09:12.010> the<00:09:12.430> permissions 00:09:12.930 --> 00:09:12.940 align:start position:0% the permissions would be the permissions 00:09:12.940 --> 00:09:15.840 align:start position:0% the permissions would be the permissions you<00:09:13.290> it<00:09:14.290> connects<00:09:14.770> to<00:09:14.800> this<00:09:15.040> new<00:09:15.310> protocol 00:09:15.840 --> 00:09:15.850 align:start position:0% you it connects to this new protocol 00:09:15.850 --> 00:09:17.730 align:start position:0% you it connects to this new protocol that<00:09:16.030> you<00:09:16.360> know<00:09:16.480> the<00:09:16.570> uniform<00:09:16.990> Pataki's<00:09:17.440> wants 00:09:17.730 --> 00:09:17.740 align:start position:0% that you know the uniform Pataki's wants 00:09:17.740 --> 00:09:19.590 align:start position:0% that you know the uniform Pataki's wants to<00:09:17.830> talk<00:09:18.070> to<00:09:18.100> unit<00:09:18.850> pig<00:09:19.030> Dottie 00:09:19.590 --> 00:09:19.600 align:start position:0% to talk to unit pig Dottie 00:09:19.600 --> 00:09:22.260 align:start position:0% to talk to unit pig Dottie you<00:09:20.020> know<00:09:20.140> and<00:09:20.560> it<00:09:20.740> wants<00:09:21.100> to<00:09:21.190> and<00:09:21.970> then<00:09:22.180> he 00:09:22.260 --> 00:09:22.270 align:start position:0% you know and it wants to and then he 00:09:22.270 --> 00:09:23.280 align:start position:0% you know and it wants to and then he would<00:09:22.390> also<00:09:22.540> have<00:09:22.750> its<00:09:22.900> own<00:09:23.020> one<00:09:23.110> about 00:09:23.280 --> 00:09:23.290 align:start position:0% would also have its own one about 00:09:23.290 --> 00:09:24.720 align:start position:0% would also have its own one about permissions<00:09:23.680> who<00:09:23.770> this<00:09:23.950> is<00:09:24.100> I<00:09:24.250> kind<00:09:24.700> of 00:09:24.720 --> 00:09:24.730 align:start position:0% permissions who this is I kind of 00:09:24.730 --> 00:09:26.280 align:start position:0% permissions who this is I kind of repetitive<00:09:24.970> this<00:09:25.270> one<00:09:25.420> of<00:09:25.510> them<00:09:25.600> so<00:09:26.020> it<00:09:26.170> would 00:09:26.280 --> 00:09:26.290 align:start position:0% repetitive this one of them so it would 00:09:26.290 --> 00:09:28.440 align:start position:0% repetitive this one of them so it would maybe<00:09:26.530> want<00:09:26.920> to<00:09:27.010> show<00:09:27.190> custom<00:09:27.580> assets<00:09:27.970> pin<00:09:28.330> it 00:09:28.440 --> 00:09:28.450 align:start position:0% maybe want to show custom assets pin it 00:09:28.450 --> 00:09:30.780 align:start position:0% maybe want to show custom assets pin it to<00:09:28.540> the<00:09:28.570> network<00:09:29.190> you<00:09:30.190> know<00:09:30.310> and<00:09:30.520> whatever 00:09:30.780 --> 00:09:30.790 align:start position:0% to the network you know and whatever 00:09:30.790 --> 00:09:32.070 align:start position:0% to the network you know and whatever else<00:09:31.060> I<00:09:31.150> didn't<00:09:31.450> have<00:09:31.540> to<00:09:31.630> talk<00:09:31.780> to<00:09:31.960> their 00:09:32.070 --> 00:09:32.080 align:start position:0% else I didn't have to talk to their 00:09:32.080 --> 00:09:33.900 align:start position:0% else I didn't have to talk to their protocol<00:09:32.470> this<00:09:32.650> about<00:09:32.890> exactly<00:09:33.280> what<00:09:33.670> would 00:09:33.900 --> 00:09:33.910 align:start position:0% protocol this about exactly what would 00:09:33.910 --> 00:09:38.160 align:start position:0% protocol this about exactly what would be<00:09:34.060> their<00:09:34.470> authority<00:09:35.470> report<00:09:36.900> so<00:09:37.900> what<00:09:38.020> are<00:09:38.110> a 00:09:38.160 --> 00:09:38.170 align:start position:0% be their authority report so what are a 00:09:38.170 --> 00:09:39.840 align:start position:0% be their authority report so what are a few<00:09:38.440> possibilities<00:09:38.920> we're<00:09:39.430> thinking<00:09:39.730> about 00:09:39.840 --> 00:09:39.850 align:start position:0% few possibilities we're thinking about 00:09:39.850 --> 00:09:42.450 align:start position:0% few possibilities we're thinking about for<00:09:39.970> these<00:09:40.210> plugins<00:09:40.980> we<00:09:41.980> think<00:09:42.190> that<00:09:42.310> new 00:09:42.450 --> 00:09:42.460 align:start position:0% for these plugins we think that new 00:09:42.460 --> 00:09:44.370 align:start position:0% for these plugins we think that new asset<00:09:42.820> types<00:09:43.030> are<00:09:43.330> finally<00:09:43.750> in<00:09:43.840> the<00:09:43.930> hands<00:09:44.290> of 00:09:44.370 --> 00:09:44.380 align:start position:0% asset types are finally in the hands of 00:09:44.380 --> 00:09:46.380 align:start position:0% asset types are finally in the hands of the<00:09:44.500> developers<00:09:45.040> we<00:09:45.610> think<00:09:45.820> new<00:09:46.150> token 00:09:46.380 --> 00:09:46.390 align:start position:0% the developers we think new token 00:09:46.390 --> 00:09:48.420 align:start position:0% the developers we think new token standards<00:09:46.960> we're<00:09:47.800> really<00:09:47.920> excited<00:09:48.190> to<00:09:48.400> see 00:09:48.420 --> 00:09:48.430 align:start position:0% standards we're really excited to see 00:09:48.430 --> 00:09:52.890 align:start position:0% standards we're really excited to see subscriptions<00:09:49.410> or<00:09:50.410> we<00:09:50.800> want<00:09:51.040> to<00:09:51.100> see<00:09:51.900> new 00:09:52.890 --> 00:09:52.900 align:start position:0% subscriptions or we want to see new 00:09:52.900 --> 00:09:54.690 align:start position:0% subscriptions or we want to see new kinds<00:09:53.200> of<00:09:53.260> collectibles<00:09:53.740> more<00:09:54.280> security 00:09:54.690 --> 00:09:54.700 align:start position:0% kinds of collectibles more security 00:09:54.700 --> 00:09:57.960 align:start position:0% kinds of collectibles more security tokens<00:09:55.120> that<00:09:55.210> actually<00:09:55.570> keep<00:09:55.720> you<00:09:55.840> safer<00:09:56.970> yep 00:09:57.960 --> 00:09:57.970 align:start position:0% tokens that actually keep you safer yep 00:09:57.970 --> 00:10:00.630 align:start position:0% tokens that actually keep you safer yep credit<00:09:58.330> lines<00:09:58.510> based<00:09:59.230> 0.04<00:10:00.040> CBP's<00:10:00.400> in<00:10:00.520> there 00:10:00.630 --> 00:10:00.640 align:start position:0% credit lines based 0.04 CBP's in there 00:10:00.640 --> 00:10:03.000 align:start position:0% credit lines based 0.04 CBP's in there like<00:10:00.790> why<00:10:01.240> not<00:10:01.390> let<00:10:01.570> your<00:10:01.720> users<00:10:02.020> decide<00:10:02.350> you 00:10:03.000 --> 00:10:03.010 align:start position:0% like why not let your users decide you 00:10:03.010 --> 00:10:04.170 align:start position:0% like why not let your users decide you know<00:10:03.130> I<00:10:03.160> one<00:10:03.490> of<00:10:03.520> my<00:10:03.580> favorite<00:10:03.940> reddit 00:10:04.170 --> 00:10:04.180 align:start position:0% know I one of my favorite reddit 00:10:04.180 --> 00:10:04.940 align:start position:0% know I one of my favorite reddit comments<00:10:04.480> ever<00:10:04.600> said 00:10:04.940 --> 00:10:04.950 align:start position:0% comments ever said 00:10:04.950 --> 00:10:07.340 align:start position:0% comments ever said if<00:10:05.340> the<00:10:05.670> internet<00:10:06.000> instead<00:10:06.300> of<00:10:06.390> rvg<00:10:06.990> the 00:10:07.340 --> 00:10:07.350 align:start position:0% if the internet instead of rvg the 00:10:07.350 --> 00:10:09.320 align:start position:0% if the internet instead of rvg the damascus<00:10:07.680> your<00:10:07.890> inventory<00:10:08.430> so<00:10:08.760> how<00:10:09.210> do<00:10:09.270> we 00:10:09.320 --> 00:10:09.330 align:start position:0% damascus your inventory so how do we 00:10:09.330 --> 00:10:11.060 align:start position:0% damascus your inventory so how do we just<00:10:09.540> let<00:10:09.690> the<00:10:09.780> spear<00:10:09.960> in<00:10:10.080> the<00:10:10.110> car<00:10:10.320> just<00:10:10.530> put 00:10:11.060 --> 00:10:11.070 align:start position:0% just let the spear in the car just put 00:10:11.070 --> 00:10:14.120 align:start position:0% just let the spear in the car just put when<00:10:11.310> we<00:10:11.400> want<00:10:11.610> it<00:10:11.840> and<00:10:12.950> bring<00:10:13.950> your<00:10:14.040> own 00:10:14.120 --> 00:10:14.130 align:start position:0% when we want it and bring your own 00:10:14.130 --> 00:10:16.040 align:start position:0% when we want it and bring your own cryptography<00:10:14.730> we're<00:10:15.300> having<00:10:15.720> an 00:10:16.040 --> 00:10:16.050 align:start position:0% cryptography we're having an 00:10:16.050 --> 00:10:18.290 align:start position:0% cryptography we're having an experimental<00:10:16.650> API<00:10:16.890> that's<00:10:17.250> been<00:10:17.460> an<00:10:17.550> EIP<00:10:17.880> for 00:10:18.290 --> 00:10:18.300 align:start position:0% experimental API that's been an EIP for 00:10:18.300 --> 00:10:20.360 align:start position:0% experimental API that's been an EIP for about<00:10:18.780> six<00:10:18.990> months<00:10:19.140> now<00:10:19.380> this<00:10:19.620> get<00:10:19.920> a<00:10:19.950> few 00:10:20.360 --> 00:10:20.370 align:start position:0% about six months now this get a few 00:10:20.370 --> 00:10:22.520 align:start position:0% about six months now this get a few proposals<00:10:20.640> so<00:10:21.060> within<00:10:21.240> your<00:10:21.450> plugin<00:10:22.050> context 00:10:22.520 --> 00:10:22.530 align:start position:0% proposals so within your plugin context 00:10:22.530 --> 00:10:24.620 align:start position:0% proposals so within your plugin context you<00:10:22.650> can<00:10:22.800> get<00:10:22.980> a<00:10:23.010> private<00:10:23.460> key<00:10:23.610> that<00:10:23.880> only<00:10:24.300> your 00:10:24.620 --> 00:10:24.630 align:start position:0% you can get a private key that only your 00:10:24.630 --> 00:10:26.900 align:start position:0% you can get a private key that only your domain<00:10:24.990> has<00:10:25.170> access<00:10:25.590> to<00:10:25.620> and<00:10:26.070> that<00:10:26.430> means<00:10:26.640> we 00:10:26.900 --> 00:10:26.910 align:start position:0% domain has access to and that means we 00:10:26.910 --> 00:10:28.580 align:start position:0% domain has access to and that means we don't<00:10:27.030> you<00:10:27.360> don't<00:10:27.540> have<00:10:27.630> to<00:10:27.720> ask<00:10:27.870> us<00:10:28.170> to<00:10:28.410> merge 00:10:28.580 --> 00:10:28.590 align:start position:0% don't you don't have to ask us to merge 00:10:28.590 --> 00:10:31.400 align:start position:0% don't you don't have to ask us to merge your<00:10:29.220> encryption<00:10:29.640> or<00:10:30.060> signing<00:10:30.420> method<00:10:30.720> you 00:10:31.400 --> 00:10:31.410 align:start position:0% your encryption or signing method you 00:10:31.410 --> 00:10:33.320 align:start position:0% your encryption or signing method you get<00:10:31.650> to<00:10:31.830> decide<00:10:32.130> you<00:10:32.460> get<00:10:32.610> to<00:10:32.730> define<00:10:32.940> your<00:10:33.270> own 00:10:33.320 --> 00:10:33.330 align:start position:0% get to decide you get to define your own 00:10:33.330 --> 00:10:35.180 align:start position:0% get to decide you get to define your own cryptography<00:10:34.050> type<00:10:34.200> computer<00:10:34.680> new<00:10:34.800> elliptic 00:10:35.180 --> 00:10:35.190 align:start position:0% cryptography type computer new elliptic 00:10:35.190 --> 00:10:37.010 align:start position:0% cryptography type computer new elliptic curve<00:10:35.430> can<00:10:35.790> use<00:10:35.880> EK<00:10:36.300> start<00:10:36.660> just<00:10:36.930> start 00:10:37.010 --> 00:10:37.020 align:start position:0% curve can use EK start just start 00:10:37.020 --> 00:10:39.200 align:start position:0% curve can use EK start just start whatever<00:10:37.500> you<00:10:37.830> need<00:10:38.040> you<00:10:38.670> build<00:10:38.910> a<00:10:39.030> script 00:10:39.200 --> 00:10:39.210 align:start position:0% whatever you need you build a script 00:10:39.210 --> 00:10:41.030 align:start position:0% whatever you need you build a script that<00:10:39.330> defines<00:10:39.720> just<00:10:40.080> that<00:10:40.200> simon<00:10:40.590> type<00:10:40.770> and 00:10:41.030 --> 00:10:41.040 align:start position:0% that defines just that simon type and 00:10:41.040 --> 00:10:43.430 align:start position:0% that defines just that simon type and you<00:10:41.370> get<00:10:41.520> to<00:10:41.670> expose<00:10:42.090> an<00:10:42.330> API<00:10:42.420> to<00:10:42.750> the<00:10:42.960> websites 00:10:43.430 --> 00:10:43.440 align:start position:0% you get to expose an API to the websites 00:10:43.440 --> 00:10:45.740 align:start position:0% you get to expose an API to the websites the<00:10:43.650> user<00:10:43.830> visits<00:10:44.160> so<00:10:44.850> that<00:10:45.000> they<00:10:45.150> can<00:10:45.540> now 00:10:45.740 --> 00:10:45.750 align:start position:0% the user visits so that they can now 00:10:45.750 --> 00:10:47.810 align:start position:0% the user visits so that they can now sign<00:10:46.050> using<00:10:46.530> that<00:10:46.650> type<00:10:46.860> and<00:10:47.130> you'd<00:10:47.550> be<00:10:47.730> able 00:10:47.810 --> 00:10:47.820 align:start position:0% sign using that type and you'd be able 00:10:47.820 --> 00:10:50.540 align:start position:0% sign using that type and you'd be able to<00:10:48.000> show<00:10:48.630> up<00:10:48.960> custom<00:10:49.590> confirmations<00:10:50.190> as<00:10:50.370> well 00:10:50.540 --> 00:10:50.550 align:start position:0% to show up custom confirmations as well 00:10:50.550 --> 00:10:53.480 align:start position:0% to show up custom confirmations as well this<00:10:51.090> makes<00:10:51.330> layer<00:10:51.690> two<00:10:52.020> suddenly<00:10:53.010> feasible 00:10:53.480 --> 00:10:53.490 align:start position:0% this makes layer two suddenly feasible 00:10:53.490 --> 00:10:55.790 align:start position:0% this makes layer two suddenly feasible of<00:10:53.880> writing<00:10:54.300> the<00:10:54.390> normal<00:10:54.690> wallet 00:10:55.790 --> 00:10:55.800 align:start position:0% of writing the normal wallet 00:10:55.800 --> 00:10:57.890 align:start position:0% of writing the normal wallet we've<00:10:56.580> there's<00:10:56.850> a<00:10:56.880> lot<00:10:57.030> of<00:10:57.120> great<00:10:57.300> teams<00:10:57.630> doing 00:10:57.890 --> 00:10:57.900 align:start position:0% we've there's a lot of great teams doing 00:10:57.900 --> 00:10:59.840 align:start position:0% we've there's a lot of great teams doing security<00:10:58.410> audits<00:10:58.680> right<00:10:59.100> as<00:10:59.310> a<00:10:59.340> service<00:10:59.700> but 00:10:59.840 --> 00:10:59.850 align:start position:0% security audits right as a service but 00:10:59.850 --> 00:11:01.250 align:start position:0% security audits right as a service but where<00:11:00.000> is<00:11:00.090> the<00:11:00.180> channel<00:11:00.660> to<00:11:00.780> currently<00:11:01.110> show 00:11:01.250 --> 00:11:01.260 align:start position:0% where is the channel to currently show 00:11:01.260 --> 00:11:04.220 align:start position:0% where is the channel to currently show that<00:11:01.440> why<00:11:02.220> why<00:11:02.670> not<00:11:02.850> let<00:11:03.030> the<00:11:03.150> wallet<00:11:03.480> just 00:11:04.220 --> 00:11:04.230 align:start position:0% that why why not let the wallet just 00:11:04.230 --> 00:11:06.080 align:start position:0% that why why not let the wallet just think<00:11:04.440> well<00:11:04.650> now<00:11:04.680> our<00:11:04.860> job<00:11:05.280> is<00:11:05.460> just<00:11:05.490> to<00:11:05.760> extend 00:11:06.080 --> 00:11:06.090 align:start position:0% think well now our job is just to extend 00:11:06.090 --> 00:11:09.620 align:start position:0% think well now our job is just to extend the<00:11:06.620> API<00:11:07.620> surface<00:11:08.220> that<00:11:08.430> lets<00:11:08.700> them<00:11:08.910> be<00:11:08.970> useful 00:11:09.620 --> 00:11:09.630 align:start position:0% the API surface that lets them be useful 00:11:09.630 --> 00:11:11.510 align:start position:0% the API surface that lets them be useful so<00:11:09.870> we<00:11:10.020> say<00:11:10.170> okay<00:11:10.860> all<00:11:10.980> right<00:11:11.130> guy<00:11:11.280> is<00:11:11.400> the 00:11:11.510 --> 00:11:11.520 align:start position:0% so we say okay all right guy is the 00:11:11.520 --> 00:11:14.330 align:start position:0% so we say okay all right guy is the permission<00:11:12.000> to<00:11:12.590> warn<00:11:13.590> you<00:11:13.770> about<00:11:13.920> a<00:11:14.070> dangerous 00:11:14.330 --> 00:11:14.340 align:start position:0% permission to warn you about a dangerous 00:11:14.340 --> 00:11:16.430 align:start position:0% permission to warn you about a dangerous contract<00:11:14.970> now<00:11:15.510> you<00:11:15.570> can<00:11:15.840> ask<00:11:16.050> for<00:11:16.320> the 00:11:16.430 --> 00:11:16.440 align:start position:0% contract now you can ask for the 00:11:16.440 --> 00:11:17.840 align:start position:0% contract now you can ask for the permission<00:11:16.560> to<00:11:16.920> warn<00:11:17.160> a<00:11:17.280> user<00:11:17.490> about<00:11:17.790> a 00:11:17.840 --> 00:11:17.850 align:start position:0% permission to warn a user about a 00:11:17.850 --> 00:11:19.850 align:start position:0% permission to warn a user about a dangerous<00:11:18.090> contract<00:11:18.780> right<00:11:19.140> that's<00:11:19.350> the<00:11:19.560> yeah 00:11:19.850 --> 00:11:19.860 align:start position:0% dangerous contract right that's the yeah 00:11:19.860 --> 00:11:21.470 align:start position:0% dangerous contract right that's the yeah that's<00:11:20.070> the<00:11:20.280> the<00:11:20.640> pull<00:11:20.910> request<00:11:21.060> you're<00:11:21.390> no 00:11:21.470 --> 00:11:21.480 align:start position:0% that's the the pull request you're no 00:11:21.480 --> 00:11:22.790 align:start position:0% that's the the pull request you're no longer<00:11:21.720> saying<00:11:21.930> hey<00:11:22.110> can<00:11:22.170> you<00:11:22.320> lock<00:11:22.500> your 00:11:22.790 --> 00:11:22.800 align:start position:0% longer saying hey can you lock your 00:11:22.800 --> 00:11:24.890 align:start position:0% longer saying hey can you lock your users<00:11:23.190> into<00:11:23.460> my<00:11:23.580> service<00:11:23.850> and<00:11:24.150> pull<00:11:24.540> in<00:11:24.660> all<00:11:24.780> my 00:11:24.890 --> 00:11:24.900 align:start position:0% users into my service and pull in all my 00:11:24.900 --> 00:11:27.140 align:start position:0% users into my service and pull in all my dependencies<00:11:25.470> while<00:11:25.680> you're<00:11:25.800> at<00:11:25.860> it<00:11:25.890> no<00:11:26.550> you 00:11:27.140 --> 00:11:27.150 align:start position:0% dependencies while you're at it no you 00:11:27.150 --> 00:11:29.750 align:start position:0% dependencies while you're at it no you ask<00:11:27.330> the<00:11:27.540> user<00:11:27.750> if<00:11:28.080> you<00:11:28.260> can<00:11:28.500> just<00:11:29.010> warn<00:11:29.490> them 00:11:29.750 --> 00:11:29.760 align:start position:0% ask the user if you can just warn them 00:11:29.760 --> 00:11:32.720 align:start position:0% ask the user if you can just warn them about<00:11:30.530> addresses<00:11:31.530> they're<00:11:31.680> sending<00:11:32.040> to<00:11:32.190> you 00:11:32.720 --> 00:11:32.730 align:start position:0% about addresses they're sending to you 00:11:32.730 --> 00:11:34.040 align:start position:0% about addresses they're sending to you don't<00:11:32.880> get<00:11:33.000> to<00:11:33.150> see<00:11:33.300> anything<00:11:33.570> else 00:11:34.040 --> 00:11:34.050 align:start position:0% don't get to see anything else 00:11:34.050 --> 00:11:36.380 align:start position:0% don't get to see anything else your<00:11:34.500> decode<00:11:34.830> is<00:11:34.950> securely<00:11:35.310> isolated<00:11:36.030> we 00:11:36.380 --> 00:11:36.390 align:start position:0% your decode is securely isolated we 00:11:36.390 --> 00:11:38.300 align:start position:0% your decode is securely isolated we don't<00:11:36.570> have<00:11:36.690> to<00:11:36.810> merge<00:11:37.260> pull<00:11:37.530> request<00:11:37.590> anymore 00:11:38.300 --> 00:11:38.310 align:start position:0% don't have to merge pull request anymore 00:11:38.310 --> 00:11:40.310 align:start position:0% don't have to merge pull request anymore and<00:11:39.000> and<00:11:39.240> people<00:11:39.570> get<00:11:39.690> to<00:11:39.780> be<00:11:39.900> safer<00:11:40.200> because 00:11:40.310 --> 00:11:40.320 align:start position:0% and and people get to be safer because 00:11:40.320 --> 00:11:41.769 align:start position:0% and and people get to be safer because their<00:11:40.620> permission<00:11:40.980> was<00:11:41.130> they<00:11:41.250> getting<00:11:41.490> more 00:11:41.769 --> 00:11:41.779 align:start position:0% their permission was they getting more 00:11:41.779 --> 00:11:45.160 align:start position:0% their permission was they getting more by<00:11:41.899> a<00:11:41.930> whole<00:11:42.170> network<00:11:42.499> dilaudid<00:11:44.170> potentially 00:11:45.160 --> 00:11:45.170 align:start position:0% by a whole network dilaudid potentially 00:11:45.170 --> 00:11:47.590 align:start position:0% by a whole network dilaudid potentially you<00:11:45.230> could<00:11:45.410> charge<00:11:45.620> for<00:11:45.649> these<00:11:45.889> plugins<00:11:46.100> too 00:11:47.590 --> 00:11:47.600 align:start position:0% you could charge for these plugins too 00:11:47.600 --> 00:11:49.900 align:start position:0% you could charge for these plugins too we<00:11:48.050> are<00:11:48.259> excited<00:11:48.649> to<00:11:48.680> support<00:11:48.920> view<00:11:49.370> protocols 00:11:49.900 --> 00:11:49.910 align:start position:0% we are excited to support view protocols 00:11:49.910 --> 00:11:52.119 align:start position:0% we are excited to support view protocols we<00:11:50.569> actually<00:11:50.870> have<00:11:51.139> an<00:11:51.259> example<00:11:51.560> folder<00:11:52.009> we're 00:11:52.119 --> 00:11:52.129 align:start position:0% we actually have an example folder we're 00:11:52.129 --> 00:11:52.960 align:start position:0% we actually have an example folder we're going<00:11:52.249> to<00:11:52.310> show<00:11:52.430> you<00:11:52.519> in<00:11:52.610> a<00:11:52.670> little<00:11:52.759> bit 00:11:52.960 --> 00:11:52.970 align:start position:0% going to show you in a little bit 00:11:52.970 --> 00:11:55.090 align:start position:0% going to show you in a little bit there's<00:11:53.779> an<00:11:53.870> idea<00:11:54.079> fest<00:11:54.290> example<00:11:54.649> it<00:11:54.829> was<00:11:54.920> like 00:11:55.090 --> 00:11:55.100 align:start position:0% there's an idea fest example it was like 00:11:55.100 --> 00:11:58.360 align:start position:0% there's an idea fest example it was like 10<00:11:55.459> months<00:11:56.290> do<00:11:57.290> you'll<00:11:57.829> be<00:11:57.980> able<00:11:58.040> to<00:11:58.220> make 00:11:58.360 --> 00:11:58.370 align:start position:0% 10 months do you'll be able to make 00:11:58.370 --> 00:12:00.369 align:start position:0% 10 months do you'll be able to make custom<00:11:58.790> confirmations<00:11:59.420> the<00:11:59.809> current<00:12:00.199> beta 00:12:00.369 --> 00:12:00.379 align:start position:0% custom confirmations the current beta 00:12:00.379 --> 00:12:02.199 align:start position:0% custom confirmations the current beta build<00:12:00.680> that<00:12:00.800> we<00:12:00.889> have<00:12:01.100> just<00:12:01.430> uses<00:12:01.759> alert<00:12:02.029> and 00:12:02.199 --> 00:12:02.209 align:start position:0% build that we have just uses alert and 00:12:02.209 --> 00:12:03.879 align:start position:0% build that we have just uses alert and confirmed<00:12:02.600> but<00:12:02.959> we<00:12:03.110> are<00:12:03.259> gonna<00:12:03.350> let<00:12:03.620> it<00:12:03.769> be 00:12:03.879 --> 00:12:03.889 align:start position:0% confirmed but we are gonna let it be 00:12:03.889 --> 00:12:06.970 align:start position:0% confirmed but we are gonna let it be pretty<00:12:04.069> eventually<00:12:04.639> -<00:12:05.290> and<00:12:06.290> new<00:12:06.680> account 00:12:06.970 --> 00:12:06.980 align:start position:0% pretty eventually - and new account 00:12:06.980 --> 00:12:09.460 align:start position:0% pretty eventually - and new account types<00:12:07.329> there's<00:12:08.329> really<00:12:08.569> an<00:12:08.779> endless<00:12:09.110> number 00:12:09.460 --> 00:12:09.470 align:start position:0% types there's really an endless number 00:12:09.470 --> 00:12:10.269 align:start position:0% types there's really an endless number of<00:12:09.499> account<00:12:09.889> types 00:12:10.269 --> 00:12:10.279 align:start position:0% of account types 00:12:10.279 --> 00:12:12.249 align:start position:0% of account types I<00:12:10.430> would<00:12:10.970> figured<00:12:11.300> out<00:12:11.420> the<00:12:11.540> last<00:12:11.720> one<00:12:11.899> the 00:12:12.249 --> 00:12:12.259 align:start position:0% I would figured out the last one the 00:12:12.259 --> 00:12:15.610 align:start position:0% I would figured out the last one the account<00:12:12.559> types<00:12:12.949> to<00:12:13.129> rule<00:12:13.309> them<00:12:13.459> all<00:12:13.579> or<00:12:14.620> maybe 00:12:15.610 --> 00:12:15.620 align:start position:0% account types to rule them all or maybe 00:12:15.620 --> 00:12:17.470 align:start position:0% account types to rule them all or maybe maybe<00:12:16.189> even<00:12:16.490> account<00:12:16.759> types<00:12:16.970> deserve<00:12:17.269> to<00:12:17.389> be 00:12:17.470 --> 00:12:17.480 align:start position:0% maybe even account types deserve to be 00:12:17.480 --> 00:12:19.090 align:start position:0% maybe even account types deserve to be extensible<00:12:17.930> one<00:12:18.170> of<00:12:18.259> the<00:12:18.350> coolest<00:12:18.920> things 00:12:19.090 --> 00:12:19.100 align:start position:0% extensible one of the coolest things 00:12:19.100 --> 00:12:20.499 align:start position:0% extensible one of the coolest things about<00:12:19.279> the<00:12:19.399> gnosis<00:12:19.579> savior's<00:12:19.999> it<00:12:20.149> supports 00:12:20.499 --> 00:12:20.509 align:start position:0% about the gnosis savior's it supports 00:12:20.509 --> 00:12:23.049 align:start position:0% about the gnosis savior's it supports add-ons<00:12:20.839> itself<00:12:21.230> so<00:12:21.860> why<00:12:22.069> not<00:12:22.189> make<00:12:22.370> a<00:12:22.430> plugin 00:12:23.049 --> 00:12:23.059 align:start position:0% add-ons itself so why not make a plugin 00:12:23.059 --> 00:12:27.549 align:start position:0% add-ons itself so why not make a plugin that<00:12:23.269> accepts<00:12:23.689> plugins<00:12:24.110> perhaps<00:12:24.620> and<00:12:26.559> of 00:12:27.549 --> 00:12:27.559 align:start position:0% that accepts plugins perhaps and of 00:12:27.559 --> 00:12:28.929 align:start position:0% that accepts plugins perhaps and of course<00:12:27.920> you're<00:12:28.399> getting<00:12:28.550> fewer 00:12:28.929 --> 00:12:28.939 align:start position:0% course you're getting fewer 00:12:28.939 --> 00:12:30.759 align:start position:0% course you're getting fewer confirmations<00:12:29.629> because<00:12:29.930> when<00:12:30.139> you<00:12:30.259> delegate 00:12:30.759 --> 00:12:30.769 align:start position:0% confirmations because when you delegate 00:12:30.769 --> 00:12:33.730 align:start position:0% confirmations because when you delegate some<00:12:31.189> capabilities<00:12:31.850> to<00:12:32.180> a<00:12:32.420> script<00:12:32.899> you<00:12:33.620> can 00:12:33.730 --> 00:12:33.740 align:start position:0% some capabilities to a script you can 00:12:33.740 --> 00:12:36.610 align:start position:0% some capabilities to a script you can potentially<00:12:34.160> delegate<00:12:35.350> things<00:12:36.350> that<00:12:36.529> you 00:12:36.610 --> 00:12:36.620 align:start position:0% potentially delegate things that you 00:12:36.620 --> 00:12:37.989 align:start position:0% potentially delegate things that you would<00:12:36.740> normally<00:12:36.860> be<00:12:37.100> repetitively 00:12:37.989 --> 00:12:37.999 align:start position:0% would normally be repetitively 00:12:37.999 --> 00:12:39.790 align:start position:0% would normally be repetitively confirming<00:12:38.569> and<00:12:38.749> so<00:12:38.930> is<00:12:39.079> just<00:12:39.230> opportunities 00:12:39.790 --> 00:12:39.800 align:start position:0% confirming and so is just opportunities 00:12:39.800 --> 00:12:43.059 align:start position:0% confirming and so is just opportunities for<00:12:39.949> reducing<00:12:40.220> user<00:12:40.550> reason<00:12:41.620> okay<00:12:42.620> so<00:12:42.680> then 00:12:43.059 --> 00:12:43.069 align:start position:0% for reducing user reason okay so then 00:12:43.069 --> 00:12:44.710 align:start position:0% for reducing user reason okay so then what<00:12:43.819> do<00:12:43.910> you<00:12:43.970> want<00:12:44.029> to<00:12:44.329> see<00:12:44.480> is<00:12:44.600> there 00:12:44.710 --> 00:12:44.720 align:start position:0% what do you want to see is there 00:12:44.720 --> 00:12:46.540 align:start position:0% what do you want to see is there anything<00:12:44.899> that<00:12:45.110> I<00:12:45.290> didn't<00:12:45.769> say<00:12:46.040> there<00:12:46.279> is 00:12:46.540 --> 00:12:46.550 align:start position:0% anything that I didn't say there is 00:12:46.550 --> 00:12:48.639 align:start position:0% anything that I didn't say there is there<00:12:46.699> are<00:12:46.819> the<00:12:46.910> use<00:12:47.269> cases<00:12:47.509> in<00:12:47.809> it<00:12:47.899> is<00:12:48.259> anybody 00:12:48.639 --> 00:12:48.649 align:start position:0% there are the use cases in it is anybody 00:12:48.649 --> 00:12:51.490 align:start position:0% there are the use cases in it is anybody like<00:12:48.800> my<00:12:49.459> thing<00:12:49.730> like<00:12:50.389> finally<00:12:51.079> like<00:12:51.319> I<00:12:51.439> don't 00:12:51.490 --> 00:12:51.500 align:start position:0% like my thing like finally like I don't 00:12:51.500 --> 00:12:53.639 align:start position:0% like my thing like finally like I don't have<00:12:51.680> to<00:12:51.829> be<00:12:51.980> our<00:12:52.160> wallet<00:12:52.550> or<00:12:52.670> build<00:12:52.850> a<00:12:52.939> wallet 00:12:53.639 --> 00:12:53.649 align:start position:0% have to be our wallet or build a wallet 00:12:53.649 --> 00:12:57.519 align:start position:0% have to be our wallet or build a wallet yeah<00:12:54.680> am<00:12:55.220> i<00:12:55.339> governor<00:12:55.699> yeah<00:12:55.879> you<00:12:55.939> got<00:12:56.149> it<00:12:56.529> alone 00:12:57.519 --> 00:12:57.529 align:start position:0% yeah am i governor yeah you got it alone 00:12:57.529 --> 00:12:59.290 align:start position:0% yeah am i governor yeah you got it alone okay<00:12:57.949> okay<00:12:58.250> hit<00:12:58.550> that<00:12:58.730> time<00:12:58.910> you<00:12:59.089> don't<00:12:59.209> have 00:12:59.290 --> 00:12:59.300 align:start position:0% okay okay hit that time you don't have 00:12:59.300 --> 00:13:00.579 align:start position:0% okay okay hit that time you don't have to<00:12:59.389> shame 00:13:00.579 --> 00:13:00.589 align:start position:0% to shame 00:13:00.589 --> 00:13:05.350 align:start position:0% to shame what's<00:13:01.009> that<00:13:01.129> free<00:13:02.000> money<00:13:02.209> free<00:13:02.839> money<00:13:04.360> you 00:13:05.350 --> 00:13:05.360 align:start position:0% what's that free money free money you 00:13:05.360 --> 00:13:07.420 align:start position:0% what's that free money free money you can<00:13:05.480> make<00:13:05.600> a<00:13:05.629> free<00:13:05.839> money<00:13:06.019> plugin<00:13:06.379> is<00:13:06.500> analog 00:13:07.420 --> 00:13:07.430 align:start position:0% can make a free money plugin is analog 00:13:07.430 --> 00:13:08.340 align:start position:0% can make a free money plugin is analog in<00:13:07.639> the 00:13:08.340 --> 00:13:08.350 align:start position:0% in the 00:13:08.350 --> 00:13:11.130 align:start position:0% in the just<00:13:08.560> a<00:13:08.710> memory<00:13:09.400> after<00:13:09.670> wait<00:13:10.120> yeah<00:13:10.570> let's<00:13:11.020> do<00:13:11.110> I 00:13:11.130 --> 00:13:11.140 align:start position:0% just a memory after wait yeah let's do I 00:13:11.140 --> 00:13:12.450 align:start position:0% just a memory after wait yeah let's do I gotta<00:13:11.380> make<00:13:11.500> free<00:13:11.710> money<00:13:11.740> in<00:13:12.010> just<00:13:12.160> a<00:13:12.220> minute 00:13:12.450 --> 00:13:12.460 align:start position:0% gotta make free money in just a minute 00:13:12.460 --> 00:13:15.900 align:start position:0% gotta make free money in just a minute oh<00:13:13.620> yeah<00:13:14.620> there's<00:13:14.890> a<00:13:14.950> screenshot<00:13:15.250> we<00:13:15.580> have<00:13:15.700> we 00:13:15.900 --> 00:13:15.910 align:start position:0% oh yeah there's a screenshot we have we 00:13:15.910 --> 00:13:17.760 align:start position:0% oh yeah there's a screenshot we have we have<00:13:16.000> a<00:13:16.090> very<00:13:16.300> simple<00:13:16.630> MVP<00:13:17.170> right<00:13:17.380> now<00:13:17.500> here's 00:13:17.760 --> 00:13:17.770 align:start position:0% have a very simple MVP right now here's 00:13:17.770 --> 00:13:19.410 align:start position:0% have a very simple MVP right now here's an<00:13:17.890> example<00:13:18.130> of<00:13:18.250> a<00:13:18.340> contract<00:13:18.670> on<00:13:18.910> a<00:13:18.940> plugin<00:13:19.330> we 00:13:19.410 --> 00:13:19.420 align:start position:0% an example of a contract on a plugin we 00:13:19.420 --> 00:13:21.990 align:start position:0% an example of a contract on a plugin we put<00:13:19.840> this<00:13:19.960> up<00:13:20.110> in<00:13:20.140> an<00:13:20.290> hour<00:13:20.440> this<00:13:20.620> morning<00:13:21.000> so 00:13:21.990 --> 00:13:22.000 align:start position:0% put this up in an hour this morning so 00:13:22.000 --> 00:13:24.510 align:start position:0% put this up in an hour this morning so it's<00:13:22.510> incredibly<00:13:23.080> easy<00:13:23.290> for<00:13:23.410> us<00:13:23.740> to<00:13:23.860> add<00:13:24.070> new 00:13:24.510 --> 00:13:24.520 align:start position:0% it's incredibly easy for us to add new 00:13:24.520 --> 00:13:27.330 align:start position:0% it's incredibly easy for us to add new features<00:13:24.790> that<00:13:25.270> then<00:13:26.110> are<00:13:26.410> just<00:13:26.590> surface<00:13:27.070> area 00:13:27.330 --> 00:13:27.340 align:start position:0% features that then are just surface area 00:13:27.340 --> 00:13:31.500 align:start position:0% features that then are just surface area for<00:13:27.580> the<00:13:27.610> ecosystem<00:13:28.270> to<00:13:28.780> extend<00:13:29.110> on<00:13:30.300> this<00:13:31.300> also 00:13:31.500 --> 00:13:31.510 align:start position:0% for the ecosystem to extend on this also 00:13:31.510 --> 00:13:33.750 align:start position:0% for the ecosystem to extend on this also allows<00:13:31.840> for<00:13:31.870> kind<00:13:32.320> of<00:13:32.410> new<00:13:32.590> onboarding<00:13:33.520> those 00:13:33.750 --> 00:13:33.760 align:start position:0% allows for kind of new onboarding those 00:13:33.760 --> 00:13:35.850 align:start position:0% allows for kind of new onboarding those those<00:13:34.450> confirmations<00:13:34.810> that<00:13:35.260> we<00:13:35.470> use<00:13:35.590> to 00:13:35.850 --> 00:13:35.860 align:start position:0% those confirmations that we use to 00:13:35.860 --> 00:13:37.590 align:start position:0% those confirmations that we use to onboard<00:13:36.100> people<00:13:36.610> they<00:13:36.730> can<00:13:36.880> also<00:13:37.060> be<00:13:37.300> used<00:13:37.330> as 00:13:37.590 --> 00:13:37.600 align:start position:0% onboard people they can also be used as 00:13:37.600 --> 00:13:39.450 align:start position:0% onboard people they can also be used as onboarding<00:13:38.110> links<00:13:38.500> so<00:13:38.770> we<00:13:38.800> kind<00:13:39.130> of<00:13:39.220> have<00:13:39.340> an 00:13:39.450 --> 00:13:39.460 align:start position:0% onboarding links so we kind of have an 00:13:39.460 --> 00:13:41.190 align:start position:0% onboarding links so we kind of have an idea<00:13:39.550> that<00:13:39.850> in<00:13:40.150> the<00:13:40.240> future<00:13:40.450> if<00:13:40.840> you<00:13:40.960> want<00:13:41.140> to 00:13:41.190 --> 00:13:41.200 align:start position:0% idea that in the future if you want to 00:13:41.200 --> 00:13:42.570 align:start position:0% idea that in the future if you want to onboard<00:13:41.320> somebody<00:13:41.800> to<00:13:41.950> crypto<00:13:42.250> there<00:13:42.490> could 00:13:42.570 --> 00:13:42.580 align:start position:0% onboard somebody to crypto there could 00:13:42.580 --> 00:13:44.130 align:start position:0% onboard somebody to crypto there could be<00:13:42.610> a<00:13:42.700> single<00:13:42.940> link<00:13:43.210> and<00:13:43.510> it<00:13:44.020> could 00:13:44.130 --> 00:13:44.140 align:start position:0% be a single link and it could 00:13:44.140 --> 00:13:47.160 align:start position:0% be a single link and it could incorporate<00:13:44.410> both<00:13:44.920> the<00:13:45.720> redirection<00:13:46.720> to<00:13:46.990> get 00:13:47.160 --> 00:13:47.170 align:start position:0% incorporate both the redirection to get 00:13:47.170 --> 00:13:49.740 align:start position:0% incorporate both the redirection to get onboard<00:13:47.380> with<00:13:47.680> the<00:13:47.920> wallet<00:13:48.100> but<00:13:48.610> also<00:13:48.910> the 00:13:49.740 --> 00:13:49.750 align:start position:0% onboard with the wallet but also the 00:13:49.750 --> 00:13:51.660 align:start position:0% onboard with the wallet but also the configuration<00:13:50.500> of<00:13:50.590> the<00:13:50.740> dependencies<00:13:51.490> that 00:13:51.660 --> 00:13:51.670 align:start position:0% configuration of the dependencies that 00:13:51.670 --> 00:13:53.160 align:start position:0% configuration of the dependencies that your<00:13:51.790> application<00:13:52.330> believes<00:13:52.600> in<00:13:52.840> that<00:13:52.990> one 00:13:53.160 --> 00:13:53.170 align:start position:0% your application believes in that one 00:13:53.170 --> 00:13:55.200 align:start position:0% your application believes in that one right<00:13:53.860> so<00:13:54.130> if<00:13:54.250> your<00:13:54.400> if<00:13:54.670> your<00:13:54.700> point<00:13:55.060> of<00:13:55.150> sale 00:13:55.200 --> 00:13:55.210 align:start position:0% right so if your if your point of sale 00:13:55.210 --> 00:13:57.540 align:start position:0% right so if your if your point of sale requires<00:13:55.870> a<00:13:55.960> certain<00:13:56.320> state<00:13:56.560> channel<00:13:56.920> why<00:13:57.370> not 00:13:57.540 --> 00:13:57.550 align:start position:0% requires a certain state channel why not 00:13:57.550 --> 00:13:59.280 align:start position:0% requires a certain state channel why not just<00:13:57.700> give<00:13:57.880> a<00:13:57.910> person<00:13:58.330> a<00:13:58.390> single<00:13:58.570> link<00:13:58.900> they 00:13:59.280 --> 00:13:59.290 align:start position:0% just give a person a single link they 00:13:59.290 --> 00:14:00.930 align:start position:0% just give a person a single link they suddenly<00:13:59.500> have<00:13:59.680> a<00:13:59.710> wallet<00:13:59.950> the<00:14:00.430> only<00:14:00.640> thing<00:14:00.820> in 00:14:00.930 --> 00:14:00.940 align:start position:0% suddenly have a wallet the only thing in 00:14:00.940 --> 00:14:02.940 align:start position:0% suddenly have a wallet the only thing in there<00:14:01.030> all<00:14:01.210> that<00:14:01.360> is<00:14:01.480> your<00:14:01.750> like<00:14:01.960> your<00:14:02.560> stores 00:14:02.940 --> 00:14:02.950 align:start position:0% there all that is your like your stores 00:14:02.950 --> 00:14:05.310 align:start position:0% there all that is your like your stores you<00:14:03.370> know<00:14:03.490> they're<00:14:04.030> dense<00:14:04.210> in<00:14:04.450> the<00:14:04.660> frequent 00:14:05.310 --> 00:14:05.320 align:start position:0% you know they're dense in the frequent 00:14:05.320 --> 00:14:06.990 align:start position:0% you know they're dense in the frequent shopper<00:14:05.470> points<00:14:05.980> but<00:14:06.130> that's<00:14:06.610> the<00:14:06.700> only<00:14:06.760> thing 00:14:06.990 --> 00:14:07.000 align:start position:0% shopper points but that's the only thing 00:14:07.000 --> 00:14:08.250 align:start position:0% shopper points but that's the only thing they<00:14:07.090> care<00:14:07.270> about<00:14:07.330> so<00:14:07.840> what<00:14:08.020> are<00:14:08.110> they<00:14:08.170> getting 00:14:08.250 --> 00:14:08.260 align:start position:0% they care about so what are they getting 00:14:08.260 --> 00:14:10.260 align:start position:0% they care about so what are they getting into<00:14:08.530> pizza<00:14:08.770> for<00:14:09.010> it<00:14:09.100> but<00:14:09.520> your<00:14:09.670> product<00:14:10.120> right 00:14:10.260 --> 00:14:10.270 align:start position:0% into pizza for it but your product right 00:14:10.270 --> 00:14:11.460 align:start position:0% into pizza for it but your product right this<00:14:10.690> is<00:14:10.810> this<00:14:10.960> is<00:14:11.080> about<00:14:11.230> what<00:14:11.380> you're 00:14:11.460 --> 00:14:11.470 align:start position:0% this is this is about what you're 00:14:11.470 --> 00:14:13.530 align:start position:0% this is this is about what you're building<00:14:11.620> we're<00:14:12.310> always<00:14:12.820> just<00:14:12.970> pin<00:14:13.300> a<00:14:13.450> little 00:14:13.530 --> 00:14:13.540 align:start position:0% building we're always just pin a little 00:14:13.540 --> 00:14:17.610 align:start position:0% building we're always just pin a little on-ramp<00:14:13.900> for<00:14:13.990> you<00:14:14.790> and<00:14:15.790> the<00:14:16.360> ways<00:14:16.690> that<00:14:16.720> we<00:14:17.440> can 00:14:17.610 --> 00:14:17.620 align:start position:0% on-ramp for you and the ways that we can 00:14:17.620 --> 00:14:19.080 align:start position:0% on-ramp for you and the ways that we can make<00:14:17.710> it<00:14:17.860> extensionists<00:14:18.430> oh<00:14:18.520> yeah<00:14:18.820> you<00:14:18.880> could 00:14:19.080 --> 00:14:19.090 align:start position:0% make it extensionists oh yeah you could 00:14:19.090 --> 00:14:20.730 align:start position:0% make it extensionists oh yeah you could we<00:14:19.600> can<00:14:19.750> built<00:14:19.870> this<00:14:19.960> is<00:14:20.110> all<00:14:20.230> JavaScript<00:14:20.500> we 00:14:20.730 --> 00:14:20.740 align:start position:0% we can built this is all JavaScript we 00:14:20.740 --> 00:14:22.200 align:start position:0% we can built this is all JavaScript we could<00:14:21.010> make<00:14:21.190> us<00:14:21.340> a<00:14:21.370> single<00:14:21.610> page<00:14:21.850> thing<00:14:22.090> we 00:14:22.200 --> 00:14:22.210 align:start position:0% could make us a single page thing we 00:14:22.210 --> 00:14:23.520 align:start position:0% could make us a single page thing we could<00:14:22.360> do<00:14:22.450> a<00:14:22.480> burner<00:14:22.720> equivalent<00:14:23.170> of<00:14:23.230> this<00:14:23.320> and 00:14:23.520 --> 00:14:23.530 align:start position:0% could do a burner equivalent of this and 00:14:23.530 --> 00:14:25.470 align:start position:0% could do a burner equivalent of this and gradually<00:14:23.860> progress<00:14:24.010> it<00:14:24.340> and<00:14:24.580> I<00:14:24.850> know<00:14:25.150> there's 00:14:25.470 --> 00:14:25.480 align:start position:0% gradually progress it and I know there's 00:14:25.480 --> 00:14:26.880 align:start position:0% gradually progress it and I know there's there's<00:14:25.720> someone<00:14:26.020> calling<00:14:26.380> for<00:14:26.410> that<00:14:26.620> it's 00:14:26.880 --> 00:14:26.890 align:start position:0% there's someone calling for that it's 00:14:26.890 --> 00:14:28.200 align:start position:0% there's someone calling for that it's kind<00:14:27.130> of<00:14:27.160> a<00:14:27.220> bandwidth<00:14:27.580> hang<00:14:27.730> for<00:14:27.940> us<00:14:28.000> where 00:14:28.200 --> 00:14:28.210 align:start position:0% kind of a bandwidth hang for us where 00:14:28.210 --> 00:14:30.830 align:start position:0% kind of a bandwidth hang for us where we're<00:14:28.420> kind<00:14:28.660> of<00:14:28.720> in<00:14:29.200> the<00:14:29.380> spin-off<00:14:29.740> obviously 00:14:30.830 --> 00:14:30.840 align:start position:0% we're kind of in the spin-off obviously 00:14:30.840 --> 00:14:33.980 align:start position:0% we're kind of in the spin-off obviously so<00:14:31.840> the<00:14:32.470> way<00:14:32.560> work<00:14:32.770> the<00:14:32.890> process<00:14:33.280> is<00:14:33.550> iterative 00:14:33.980 --> 00:14:33.990 align:start position:0% so the way work the process is iterative 00:14:33.990 --> 00:14:36.660 align:start position:0% so the way work the process is iterative we<00:14:34.990> added<00:14:35.410> this<00:14:35.500> permission<00:14:35.800> system<00:14:36.310> we're 00:14:36.660 --> 00:14:36.670 align:start position:0% we added this permission system we're 00:14:36.670 --> 00:14:38.940 align:start position:0% we added this permission system we're pretty<00:14:36.820> happy<00:14:37.000> about<00:14:37.270> it<00:14:37.510> puts<00:14:37.750> a<00:14:37.990> mirror<00:14:38.350> RPC 00:14:38.940 --> 00:14:38.950 align:start position:0% pretty happy about it puts a mirror RPC 00:14:38.950 --> 00:14:41.700 align:start position:0% pretty happy about it puts a mirror RPC our<00:14:39.940> pcs<00:14:40.270> are<00:14:40.390> pretty<00:14:40.600> coarse<00:14:40.930> but<00:14:41.230> they<00:14:41.380> will 00:14:41.700 --> 00:14:41.710 align:start position:0% our pcs are pretty coarse but they will 00:14:41.710 --> 00:14:44.910 align:start position:0% our pcs are pretty coarse but they will get<00:14:41.800> us<00:14:41.950> started<00:14:42.600> the<00:14:43.600> plug-in<00:14:43.930> system<00:14:44.290> uses 00:14:44.910 --> 00:14:44.920 align:start position:0% get us started the plug-in system uses 00:14:44.920 --> 00:14:47.730 align:start position:0% get us started the plug-in system uses the<00:14:44.950> RPC<00:14:45.400> permission<00:14:45.940> system<00:14:46.150> to<00:14:46.740> allow 00:14:47.730 --> 00:14:47.740 align:start position:0% the RPC permission system to allow 00:14:47.740 --> 00:14:49.440 align:start position:0% the RPC permission system to allow scripts<00:14:48.160> that<00:14:48.370> allow<00:14:48.670> users<00:14:49.030> to<00:14:49.060> request 00:14:49.440 --> 00:14:49.450 align:start position:0% scripts that allow users to request 00:14:49.450 --> 00:14:51.000 align:start position:0% scripts that allow users to request permission<00:14:49.630> and<00:14:50.020> then<00:14:50.500> pass<00:14:50.740> those 00:14:51.000 --> 00:14:51.010 align:start position:0% permission and then pass those 00:14:51.010 --> 00:14:54.480 align:start position:0% permission and then pass those permissions<00:14:51.430> on<00:14:51.550> the<00:14:51.580> scripts<00:14:51.910> and<00:14:53.220> from<00:14:54.220> here 00:14:54.480 --> 00:14:54.490 align:start position:0% permissions on the scripts and from here 00:14:54.490 --> 00:14:56.550 align:start position:0% permissions on the scripts and from here we<00:14:55.000> basically<00:14:55.330> want<00:14:55.630> to<00:14:55.690> know<00:14:55.840> what<00:14:56.170> API 00:14:56.550 --> 00:14:56.560 align:start position:0% we basically want to know what API 00:14:56.560 --> 00:14:59.580 align:start position:0% we basically want to know what API surface<00:14:57.120> unleashes<00:14:58.120> your<00:14:58.660> projects<00:14:59.260> the<00:14:59.290> most 00:14:59.580 --> 00:14:59.590 align:start position:0% surface unleashes your projects the most 00:14:59.590 --> 00:15:02.520 align:start position:0% surface unleashes your projects the most I<00:14:59.950> gave<00:15:00.340> a<00:15:00.370> lot<00:15:00.580> of<00:15:00.610> examples<00:15:01.030> and<00:15:01.450> you<00:15:02.440> know 00:15:02.520 --> 00:15:02.530 align:start position:0% I gave a lot of examples and you know 00:15:02.530 --> 00:15:03.990 align:start position:0% I gave a lot of examples and you know some<00:15:02.770> of<00:15:02.890> those<00:15:02.950> are<00:15:03.160> accounting<00:15:03.490> for<00:15:03.640> some<00:15:03.910> of 00:15:03.990 --> 00:15:04.000 align:start position:0% some of those are accounting for some of 00:15:04.000 --> 00:15:05.380 align:start position:0% some of those are accounting for some of those<00:15:04.060> eight<00:15:04.240> guys<00:15:04.480> were<00:15:04.690> making<00:15:04.810> we're 00:15:05.380 --> 00:15:05.390 align:start position:0% those eight guys were making we're 00:15:05.390 --> 00:15:07.780 align:start position:0% those eight guys were making we're show<00:15:05.570> you<00:15:05.630> some<00:15:05.870> docs<00:15:06.080> in<00:15:06.290> a<00:15:06.320> second<00:15:06.680> yeah<00:15:07.550> one 00:15:07.780 --> 00:15:07.790 align:start position:0% show you some docs in a second yeah one 00:15:07.790 --> 00:15:08.620 align:start position:0% show you some docs in a second yeah one who's<00:15:08.030> come<00:15:08.210> to<00:15:08.300> mind 00:15:08.620 --> 00:15:08.630 align:start position:0% who's come to mind 00:15:08.630 --> 00:15:10.750 align:start position:0% who's come to mind yeah<00:15:08.870> curious<00:15:09.350> about<00:15:09.440> like<00:15:09.650> books<00:15:09.890> so<00:15:10.280> how<00:15:10.610> is 00:15:10.750 --> 00:15:10.760 align:start position:0% yeah curious about like books so how is 00:15:10.760 --> 00:15:13.060 align:start position:0% yeah curious about like books so how is it<00:15:10.790> that<00:15:10.910> we<00:15:11.120> actually<00:15:11.240> put<00:15:11.810> our<00:15:11.870> plug<00:15:12.770> in<00:15:12.920> to 00:15:13.060 --> 00:15:13.070 align:start position:0% it that we actually put our plug in to 00:15:13.070 --> 00:15:14.680 align:start position:0% it that we actually put our plug in to be<00:15:13.190> actually<00:15:13.520> able<00:15:13.880> to<00:15:14.000> modify<00:15:14.360> the<00:15:14.420> user 00:15:14.680 --> 00:15:14.690 align:start position:0% be actually able to modify the user 00:15:14.690 --> 00:15:16.060 align:start position:0% be actually able to modify the user experience<00:15:15.110> beyond<00:15:15.650> just<00:15:15.800> like<00:15:15.980> the 00:15:16.060 --> 00:15:16.070 align:start position:0% experience beyond just like the 00:15:16.070 --> 00:15:18.310 align:start position:0% experience beyond just like the confirmation<00:15:16.550> screen<00:15:16.580> error<00:15:17.060> so<00:15:17.660> so 00:15:18.310 --> 00:15:18.320 align:start position:0% confirmation screen error so so 00:15:18.320 --> 00:15:20.800 align:start position:0% confirmation screen error so so initially<00:15:19.250> just<00:15:19.490> yeah<00:15:20.030> we<00:15:20.600> should<00:15:20.720> probably 00:15:20.800 --> 00:15:20.810 align:start position:0% initially just yeah we should probably 00:15:20.810 --> 00:15:22.570 align:start position:0% initially just yeah we should probably do<00:15:21.020> it<00:15:21.110> too<00:15:21.230> in<00:15:21.350> a<00:15:21.470> little<00:15:22.100> bit<00:15:22.190> later<00:15:22.370> but 00:15:22.570 --> 00:15:22.580 align:start position:0% do it too in a little bit later but 00:15:22.580 --> 00:15:24.790 align:start position:0% do it too in a little bit later but initially<00:15:23.420> we're<00:15:23.660> looking<00:15:23.960> at<00:15:24.080> very<00:15:24.350> discreet 00:15:24.790 --> 00:15:24.800 align:start position:0% initially we're looking at very discreet 00:15:24.800 --> 00:15:26.020 align:start position:0% initially we're looking at very discreet deliberate<00:15:25.310> changes<00:15:25.730> to<00:15:25.820> the<00:15:25.910> user 00:15:26.020 --> 00:15:26.030 align:start position:0% deliberate changes to the user 00:15:26.030 --> 00:15:27.910 align:start position:0% deliberate changes to the user experience<00:15:26.720> where<00:15:26.930> we're<00:15:27.140> still<00:15:27.350> controlling 00:15:27.910 --> 00:15:27.920 align:start position:0% experience where we're still controlling 00:15:27.920 --> 00:15:29.860 align:start position:0% experience where we're still controlling it<00:15:28.040> but<00:15:28.160> we're<00:15:28.340> like<00:15:28.490> permitting<00:15:29.240> parts<00:15:29.570> of<00:15:29.720> it 00:15:29.860 --> 00:15:29.870 align:start position:0% it but we're like permitting parts of it 00:15:29.870 --> 00:15:32.110 align:start position:0% it but we're like permitting parts of it right<00:15:30.320> longer-term<00:15:30.710> as<00:15:31.130> there<00:15:31.550> are<00:15:31.730> more 00:15:32.110 --> 00:15:32.120 align:start position:0% right longer-term as there are more 00:15:32.120 --> 00:15:34.390 align:start position:0% right longer-term as there are more secure<00:15:32.510> options<00:15:32.960> available<00:15:33.110> for<00:15:33.770> extending 00:15:34.390 --> 00:15:34.400 align:start position:0% secure options available for extending 00:15:34.400 --> 00:15:36.790 align:start position:0% secure options available for extending the<00:15:34.490> user<00:15:34.670> integration<00:15:35.240> in<00:15:35.540> a<00:15:35.720> safe<00:15:35.930> way<00:15:36.170> where 00:15:36.790 --> 00:15:36.800 align:start position:0% the user integration in a safe way where 00:15:36.800 --> 00:15:38.830 align:start position:0% the user integration in a safe way where we're<00:15:37.280> open<00:15:37.610> exploring<00:15:38.120> that<00:15:38.240> but<00:15:38.510> but<00:15:38.780> I 00:15:38.830 --> 00:15:38.840 align:start position:0% we're open exploring that but but I 00:15:38.840 --> 00:15:41.080 align:start position:0% we're open exploring that but but I think<00:15:39.290> a<00:15:39.530> very<00:15:39.560> gradual<00:15:40.400> iterative<00:15:40.820> approach 00:15:41.080 --> 00:15:41.090 align:start position:0% think a very gradual iterative approach 00:15:41.090 --> 00:15:51.280 align:start position:0% think a very gradual iterative approach is<00:15:41.270> the<00:15:42.040> it's<00:15:43.040> already<00:15:46.120> you<00:15:47.120> I<00:15:49.150> I<00:15:50.150> mean<00:15:50.960> not<00:15:51.110> yet 00:15:51.280 --> 00:15:51.290 align:start position:0% is the it's already you I I mean not yet 00:15:51.290 --> 00:15:52.720 align:start position:0% is the it's already you I I mean not yet but<00:15:51.440> that's<00:15:51.560> like<00:15:51.800> the<00:15:51.890> kind<00:15:52.070> of<00:15:52.160> conversation 00:15:52.720 --> 00:15:52.730 align:start position:0% but that's like the kind of conversation 00:15:52.730 --> 00:15:54.130 align:start position:0% but that's like the kind of conversation we<00:15:52.820> can<00:15:52.940> now<00:15:53.000> have<00:15:53.240> we<00:15:53.390> can<00:15:53.540> say<00:15:53.690> would<00:15:54.080> you 00:15:54.130 --> 00:15:54.140 align:start position:0% we can now have we can say would you 00:15:54.140 --> 00:15:55.900 align:start position:0% we can now have we can say would you would<00:15:54.500> you<00:15:54.560> be<00:15:54.740> interested<00:15:54.920> in<00:15:55.250> the<00:15:55.340> the<00:15:55.580> API 00:15:55.900 --> 00:15:55.910 align:start position:0% would you be interested in the the API 00:15:55.910 --> 00:15:58.300 align:start position:0% would you be interested in the the API to<00:15:56.000> rebrand<00:15:56.990> and<00:15:57.290> take<00:15:57.950> your<00:15:58.100> commission 00:15:58.300 --> 00:15:58.310 align:start position:0% to rebrand and take your commission 00:15:58.310 --> 00:16:01.000 align:start position:0% to rebrand and take your commission really<00:15:58.970> well<00:15:59.270> you<00:15:59.360> know<00:15:59.390> like<00:15:59.660> well<00:15:59.840> we<00:16:00.440> are 00:16:01.000 --> 00:16:01.010 align:start position:0% really well you know like well we are 00:16:01.010 --> 00:16:02.590 align:start position:0% really well you know like well we are going<00:16:01.220> to<00:16:01.280> need<00:16:01.370> dinner<00:16:01.580> at<00:16:01.760> some<00:16:01.940> point<00:16:02.150> but 00:16:02.590 --> 00:16:02.600 align:start position:0% going to need dinner at some point but 00:16:02.600 --> 00:16:04.930 align:start position:0% going to need dinner at some point but but<00:16:03.200> we<00:16:03.320> can<00:16:03.440> tell<00:16:03.590> you<00:16:03.860> know<00:16:03.950> now<00:16:04.250> now<00:16:04.730> we've 00:16:04.930 --> 00:16:04.940 align:start position:0% but we can tell you know now now we've 00:16:04.940 --> 00:16:07.360 align:start position:0% but we can tell you know now now we've elevated<00:16:05.090> the<00:16:05.420> enit<00:16:06.200> conversation<00:16:06.920> from<00:16:07.160> like 00:16:07.360 --> 00:16:07.370 align:start position:0% elevated the enit conversation from like 00:16:07.370 --> 00:16:10.300 align:start position:0% elevated the enit conversation from like you<00:16:08.300> know<00:16:08.450> like<00:16:08.720> yeah<00:16:09.650> is<00:16:09.830> your<00:16:10.100> specific 00:16:10.300 --> 00:16:10.310 align:start position:0% you know like yeah is your specific 00:16:10.310 --> 00:16:12.910 align:start position:0% you know like yeah is your specific protocol<00:16:10.700> and<00:16:11.210> part<00:16:11.480> of<00:16:11.510> the<00:16:11.750> wallet<00:16:12.230> and<00:16:12.410> all 00:16:12.910 --> 00:16:12.920 align:start position:0% protocol and part of the wallet and all 00:16:12.920 --> 00:16:15.220 align:start position:0% protocol and part of the wallet and all while<00:16:13.130> it's<00:16:13.310> not<00:16:13.490> integrated<00:16:13.910> to<00:16:14.600> you<00:16:14.900> cannot 00:16:15.220 --> 00:16:15.230 align:start position:0% while it's not integrated to you cannot 00:16:15.230 --> 00:16:18.220 align:start position:0% while it's not integrated to you cannot find<00:16:15.530> your<00:16:15.790> component<00:16:16.790> and<00:16:16.940> and<00:16:17.930> you<00:16:18.080> can 00:16:18.220 --> 00:16:18.230 align:start position:0% find your component and and you can 00:16:18.230 --> 00:16:19.720 align:start position:0% find your component and and you can justify<00:16:18.440> the<00:16:18.620> surface<00:16:19.040> area<00:16:19.250> we<00:16:19.430> need<00:16:19.640> to 00:16:19.720 --> 00:16:19.730 align:start position:0% justify the surface area we need to 00:16:19.730 --> 00:16:21.400 align:start position:0% justify the surface area we need to expose<00:16:19.970> to<00:16:20.180> neighborhood<00:16:20.600> and<00:16:20.810> that<00:16:21.140> could<00:16:21.350> be 00:16:21.400 --> 00:16:21.410 align:start position:0% expose to neighborhood and that could be 00:16:21.410 --> 00:16:23.800 align:start position:0% expose to neighborhood and that could be the<00:16:21.560> politic<00:16:22.180> fun<00:16:23.180> good<00:16:23.330> question<00:16:23.630> around 00:16:23.800 --> 00:16:23.810 align:start position:0% the politic fun good question around 00:16:23.810 --> 00:16:25.190 align:start position:0% the politic fun good question around like<00:16:24.080> so<00:16:24.350> in<00:16:24.590> theory 00:16:25.190 --> 00:16:25.200 align:start position:0% like so in theory 00:16:25.200 --> 00:16:28.610 align:start position:0% like so in theory like<00:16:25.560> long<00:16:26.430> absolutely<00:16:27.300> yes<00:16:27.540> yeah<00:16:28.410> I<00:16:28.440> think 00:16:28.610 --> 00:16:28.620 align:start position:0% like long absolutely yes yeah I think 00:16:28.620 --> 00:16:30.710 align:start position:0% like long absolutely yes yeah I think like<00:16:28.950> we've<00:16:29.700> been<00:16:29.910> considering<00:16:30.240> that<00:16:30.510> you 00:16:30.710 --> 00:16:30.720 align:start position:0% like we've been considering that you 00:16:30.720 --> 00:16:33.350 align:start position:0% like we've been considering that you know<00:16:30.839> we<00:16:31.139> are<00:16:31.560> pre-revenue<00:16:32.399> us<00:16:32.730> like<00:16:33.060> pretty 00:16:33.350 --> 00:16:33.360 align:start position:0% know we are pre-revenue us like pretty 00:16:33.360 --> 00:16:35.180 align:start position:0% know we are pre-revenue us like pretty much<00:16:33.389> every<00:16:33.750> while<00:16:33.959> it<00:16:34.110> is<00:16:34.260> it's<00:16:34.680> possible 00:16:35.180 --> 00:16:35.190 align:start position:0% much every while it is it's possible 00:16:35.190 --> 00:16:36.680 align:start position:0% much every while it is it's possible that<00:16:35.279> a<00:16:35.339> curation<00:16:35.700> of<00:16:35.940> a<00:16:36.000> store<00:16:36.209> or<00:16:36.389> something 00:16:36.680 --> 00:16:36.690 align:start position:0% that a curation of a store or something 00:16:36.690 --> 00:16:39.379 align:start position:0% that a curation of a store or something like<00:16:36.899> that<00:16:37.110> could<00:16:37.320> be<00:16:37.500> an<00:16:38.100> alternate<00:16:38.610> but<00:16:39.209> this 00:16:39.379 --> 00:16:39.389 align:start position:0% like that could be an alternate but this 00:16:39.389 --> 00:16:40.879 align:start position:0% like that could be an alternate but this is<00:16:39.570> the<00:16:39.750> beginning<00:16:40.139> of<00:16:40.200> the<00:16:40.290> developer<00:16:40.740> beta 00:16:40.879 --> 00:16:40.889 align:start position:0% is the beginning of the developer beta 00:16:40.889 --> 00:16:43.009 align:start position:0% is the beginning of the developer beta it's<00:16:41.220> but<00:16:41.490> we're<00:16:41.610> not<00:16:41.760> Lagos<00:16:42.180> selling<00:16:42.899> or 00:16:43.009 --> 00:16:43.019 align:start position:0% it's but we're not Lagos selling or 00:16:43.019 --> 00:16:47.870 align:start position:0% it's but we're not Lagos selling or walling<00:16:43.560> missing<00:16:43.800> audio<00:16:45.050> so<00:16:46.050> yeah<00:16:46.730> we've<00:16:47.730> got 00:16:47.870 --> 00:16:47.880 align:start position:0% walling missing audio so yeah we've got 00:16:47.880 --> 00:16:49.160 align:start position:0% walling missing audio so yeah we've got we<00:16:48.060> have<00:16:48.180> a<00:16:48.209> lot<00:16:48.360> to<00:16:48.449> cover<00:16:48.570> and<00:16:48.779> I<00:16:48.810> do<00:16:48.870> want<00:16:49.110> to 00:16:49.160 --> 00:16:49.170 align:start position:0% we have a lot to cover and I do want to 00:16:49.170 --> 00:16:51.230 align:start position:0% we have a lot to cover and I do want to help<00:16:49.380> you<00:16:49.470> guys<00:16:49.709> build<00:16:50.370> already<00:16:50.790> get<00:16:50.910> on<00:16:51.029> time 00:16:51.230 --> 00:16:51.240 align:start position:0% help you guys build already get on time 00:16:51.240 --> 00:16:52.759 align:start position:0% help you guys build already get on time but<00:16:51.449> I'm<00:16:51.540> hoping<00:16:51.870> that<00:16:52.019> we<00:16:52.079> have<00:16:52.110> a<00:16:52.230> majority 00:16:52.759 --> 00:16:52.769 align:start position:0% but I'm hoping that we have a majority 00:16:52.769 --> 00:16:54.079 align:start position:0% but I'm hoping that we have a majority of<00:16:52.949> the<00:16:53.010> workshop<00:16:53.399> for<00:16:53.610> you<00:16:53.670> guys<00:16:53.820> to<00:16:53.940> actually 00:16:54.079 --> 00:16:54.089 align:start position:0% of the workshop for you guys to actually 00:16:54.089 --> 00:16:56.900 align:start position:0% of the workshop for you guys to actually try<00:16:54.480> it<00:16:54.540> out<00:16:54.750> and<00:16:54.990> the<00:16:55.889> period<00:16:56.430> for<00:16:56.579> questions 00:16:56.900 --> 00:16:56.910 align:start position:0% try it out and the period for questions 00:16:56.910 --> 00:16:59.210 align:start position:0% try it out and the period for questions so<00:16:57.540> I'd<00:16:58.079> like<00:16:58.199> to<00:16:58.260> thank<00:16:58.560> some<00:16:58.740> of<00:16:58.800> the<00:16:58.949> early 00:16:59.210 --> 00:16:59.220 align:start position:0% so I'd like to thank some of the early 00:16:59.220 --> 00:17:00.889 align:start position:0% so I'd like to thank some of the early teams<00:16:59.459> that<00:16:59.639> we<00:16:59.730> gave<00:16:59.880> you<00:17:00.540> we<00:17:00.660> have<00:17:00.750> some 00:17:00.889 --> 00:17:00.899 align:start position:0% teams that we gave you we have some 00:17:00.899 --> 00:17:02.449 align:start position:0% teams that we gave you we have some feedback<00:17:01.079> from<00:17:01.440> we<00:17:01.589> did<00:17:01.740> some<00:17:01.860> user<00:17:02.040> research 00:17:02.449 --> 00:17:02.459 align:start position:0% feedback from we did some user research 00:17:02.459 --> 00:17:04.789 align:start position:0% feedback from we did some user research some<00:17:02.880> teams<00:17:03.120> even<00:17:03.420> well<00:17:03.660> that<00:17:03.839> some<00:17:04.079> some 00:17:04.789 --> 00:17:04.799 align:start position:0% some teams even well that some some 00:17:04.799 --> 00:17:09.770 align:start position:0% some teams even well that some some early<00:17:05.339> prototypes<00:17:06.559> so<00:17:07.559> now<00:17:08.250> to<00:17:08.970> talk<00:17:09.480> a<00:17:09.510> little 00:17:09.770 --> 00:17:09.780 align:start position:0% early prototypes so now to talk a little 00:17:09.780 --> 00:17:11.720 align:start position:0% early prototypes so now to talk a little bit<00:17:09.990> about<00:17:10.020> what<00:17:10.470> a<00:17:10.500> HelloWorld<00:17:10.890> plugin<00:17:11.490> looks 00:17:11.720 --> 00:17:11.730 align:start position:0% bit about what a HelloWorld plugin looks 00:17:11.730 --> 00:17:12.199 align:start position:0% bit about what a HelloWorld plugin looks like 00:17:12.199 --> 00:17:12.209 align:start position:0% like 00:17:12.209 --> 00:17:18.410 align:start position:0% like like<00:17:12.449> to<00:17:12.660> welcome<00:17:13.049> to<00:17:13.230> the<00:17:13.350> stage<00:17:13.559> mr.<00:17:14.100> Mars 00:17:18.410 --> 00:17:18.420 align:start position:0% 00:17:18.420 --> 00:17:19.809 align:start position:0% [Applause] 00:17:19.809 --> 00:17:19.819 align:start position:0% [Applause] 00:17:19.819 --> 00:17:23.770 align:start position:0% [Applause] now<00:17:20.819> so<00:17:21.150> for<00:17:21.449> my<00:17:21.540> first<00:17:21.750> race<00:17:22.079> let's<00:17:22.980> make<00:17:23.220> this 00:17:23.770 --> 00:17:23.780 align:start position:0% now so for my first race let's make this 00:17:23.780 --> 00:17:26.659 align:start position:0% now so for my first race let's make this area<00:17:24.780> up<00:17:24.870> here<00:17:24.929> just<00:17:25.439> a<00:17:25.650> little<00:17:26.069> bit<00:17:26.339> more 00:17:26.659 --> 00:17:26.669 align:start position:0% area up here just a little bit more 00:17:26.669 --> 00:17:29.810 align:start position:0% area up here just a little bit more Internet<00:17:27.360> we<00:17:27.780> have<00:17:27.929> two<00:17:28.230> seats<00:17:28.559> over<00:17:28.890> here<00:17:29.070> two 00:17:29.810 --> 00:17:29.820 align:start position:0% Internet we have two seats over here two 00:17:29.820 --> 00:17:31.850 align:start position:0% Internet we have two seats over here two seats<00:17:30.120> over<00:17:30.330> here<00:17:30.450> one<00:17:31.200> seat<00:17:31.500> over<00:17:31.710> here 00:17:31.850 --> 00:17:31.860 align:start position:0% seats over here one seat over here 00:17:31.860 --> 00:17:35.390 align:start position:0% seats over here one seat over here please<00:17:32.340> move<00:17:32.730> forward<00:17:33.500> come<00:17:34.500> towards<00:17:35.309> the 00:17:35.390 --> 00:17:35.400 align:start position:0% please move forward come towards the 00:17:35.400 --> 00:17:40.950 align:start position:0% please move forward come towards the stage<00:17:35.700> as<00:17:36.230> it<00:17:37.230> were<00:17:37.380> is 00:17:40.950 --> 00:17:40.960 align:start position:0% 00:17:40.960 --> 00:17:46.890 align:start position:0% [Music] 00:17:46.890 --> 00:17:46.900 align:start position:0% 00:17:46.900 --> 00:17:48.520 align:start position:0% [Music] 00:17:48.520 --> 00:17:48.530 align:start position:0% [Music] 00:17:48.530 --> 00:17:50.690 align:start position:0% [Music] although<00:17:49.530> if<00:17:49.679> you<00:17:49.800> happen<00:17:50.130> to<00:17:50.160> have<00:17:50.280> internet 00:17:50.690 --> 00:17:50.700 align:start position:0% although if you happen to have internet 00:17:50.700 --> 00:17:53.330 align:start position:0% although if you happen to have internet and<00:17:50.910> you<00:17:51.540> scan<00:17:51.780> that<00:17:51.960> QR<00:17:52.170> code<00:17:52.559> it<00:17:52.890> will<00:17:53.130> take 00:17:53.330 --> 00:17:53.340 align:start position:0% and you scan that QR code it will take 00:17:53.340 --> 00:17:55.549 align:start position:0% and you scan that QR code it will take you<00:17:53.580> to<00:17:54.030> the<00:17:54.420> page<00:17:54.570> where<00:17:54.809> you<00:17:54.929> can<00:17:55.140> download 00:17:55.549 --> 00:17:55.559 align:start position:0% you to the page where you can download 00:17:55.559 --> 00:17:57.140 align:start position:0% you to the page where you can download things<00:17:56.040> to<00:17:56.400> actually<00:17:56.640> start<00:17:57.059> building 00:17:57.140 --> 00:17:57.150 align:start position:0% things to actually start building 00:17:57.150 --> 00:18:00.710 align:start position:0% things to actually start building something<00:17:58.910> it's<00:17:59.910> got<00:18:00.059> everything<00:18:00.300> you<00:18:00.690> could 00:18:00.710 --> 00:18:00.720 align:start position:0% something it's got everything you could 00:18:00.720 --> 00:18:06.590 align:start position:0% something it's got everything you could scan<00:18:04.130> right<00:18:05.130> yes<00:18:05.460> we're<00:18:05.910> dropping<00:18:06.059> the<00:18:06.270> videos 00:18:06.590 --> 00:18:06.600 align:start position:0% scan right yes we're dropping the videos 00:18:06.600 --> 00:18:09.500 align:start position:0% scan right yes we're dropping the videos and<00:18:06.840> also<00:18:06.990> exercise<00:18:07.470> yes<00:18:07.740> but<00:18:08.340> anyway<00:18:08.580> I<00:18:08.820> don't 00:18:09.500 --> 00:18:09.510 align:start position:0% and also exercise yes but anyway I don't 00:18:09.510 --> 00:18:11.510 align:start position:0% and also exercise yes but anyway I don't have<00:18:09.600> to<00:18:09.720> talk<00:18:09.929> to<00:18:10.080> this<00:18:10.200> mic<00:18:10.530> because<00:18:10.890> I<00:18:11.190> need 00:18:11.510 --> 00:18:11.520 align:start position:0% have to talk to this mic because I need 00:18:11.520 --> 00:18:14.000 align:start position:0% have to talk to this mic because I need both<00:18:12.360> my<00:18:12.540> hands<00:18:12.840> so<00:18:13.350> when<00:18:13.470> everyone<00:18:13.740> has 00:18:14.000 --> 00:18:14.010 align:start position:0% both my hands so when everyone has 00:18:14.010 --> 00:18:17.049 align:start position:0% both my hands so when everyone has finished<00:18:14.220> moving<00:18:14.820> up<00:18:15.059> if<00:18:15.480> they<00:18:15.720> want<00:18:15.750> to<00:18:16.050> get 00:18:17.049 --> 00:18:17.059 align:start position:0% finished moving up if they want to get 00:18:17.059 --> 00:18:24.409 align:start position:0% finished moving up if they want to get I'm<00:18:18.059> going<00:18:18.240> to<00:18:18.330> say<00:18:18.480> that<00:18:18.720> that's<00:18:19.110> good<00:18:19.320> enough 00:18:24.409 --> 00:18:24.419 align:start position:0% 00:18:24.419 --> 00:18:26.180 align:start position:0% there's<00:18:24.779> like<00:18:24.929> two<00:18:25.139> seasons<00:18:25.589> up<00:18:25.679> here<00:18:25.889> there's 00:18:26.180 --> 00:18:26.190 align:start position:0% there's like two seasons up here there's 00:18:26.190 --> 00:18:27.919 align:start position:0% there's like two seasons up here there's just<00:18:26.249> here<00:18:26.819> there's<00:18:27.119> like<00:18:27.269> two<00:18:27.509> more<00:18:27.659> seats 00:18:27.919 --> 00:18:27.929 align:start position:0% just here there's like two more seats 00:18:27.929 --> 00:18:32.110 align:start position:0% just here there's like two more seats here<00:18:28.169> if<00:18:28.739> you<00:18:29.429> want<00:18:29.579> to<00:18:29.609> come<00:18:29.789> sit 00:18:32.110 --> 00:18:32.120 align:start position:0% 00:18:32.120 --> 00:18:41.480 align:start position:0% [Music] 00:18:41.480 --> 00:18:41.490 align:start position:0% 00:18:41.490 --> 00:18:58.350 align:start position:0% [Music] 00:18:58.350 --> 00:18:58.360 align:start position:0% 00:18:58.360 --> 00:19:30.260 align:start position:0% [Music] 00:19:30.260 --> 00:19:30.270 align:start position:0% 00:19:30.270 --> 00:19:32.430 align:start position:0% but<00:19:31.270> yeah<00:19:31.390> well<00:19:31.720> everything<00:19:32.200> will<00:19:32.350> be 00:19:32.430 --> 00:19:32.440 align:start position:0% but yeah well everything will be 00:19:32.440 --> 00:19:35.159 align:start position:0% but yeah well everything will be uploaded<00:19:32.950> and<00:19:33.220> available<00:19:33.730> later<00:19:34.630> for<00:19:35.049> what 00:19:35.159 --> 00:19:35.169 align:start position:0% uploaded and available later for what 00:19:35.169 --> 00:19:40.710 align:start position:0% uploaded and available later for what you<00:19:35.320> guys<00:19:35.470> have<00:19:39.030> yeah<00:19:40.030> after<00:19:40.630> this 00:19:40.710 --> 00:19:40.720 align:start position:0% you guys have yeah after this 00:19:40.720 --> 00:19:43.090 align:start position:0% you guys have yeah after this presentation<00:19:40.960> will<00:19:41.530> even<00:19:41.830> post<00:19:42.070> it<00:19:42.220> locally 00:19:43.090 --> 00:19:43.100 align:start position:0% presentation will even post it locally 00:19:43.100 --> 00:19:51.299 align:start position:0% presentation will even post it locally anybody<00:19:43.639> can<00:19:43.970> come<00:19:44.000> in<00:19:45.970> okay<00:19:46.970> so<00:19:49.779> so<00:19:50.779> there<00:19:50.990> are 00:19:51.299 --> 00:19:51.309 align:start position:0% anybody can come in okay so so there are 00:19:51.309 --> 00:19:55.389 align:start position:0% anybody can come in okay so so there are first<00:19:52.309> of<00:19:52.490> all<00:19:52.990> we<00:19:53.990> have<00:19:54.139> really<00:19:54.529> just<00:19:54.830> now 00:19:55.389 --> 00:19:55.399 align:start position:0% first of all we have really just now 00:19:55.399 --> 00:19:57.700 align:start position:0% first of all we have really just now made<00:19:55.789> public<00:19:56.269> the<00:19:56.509> two<00:19:57.080> relevant 00:19:57.700 --> 00:19:57.710 align:start position:0% made public the two relevant 00:19:57.710 --> 00:20:00.159 align:start position:0% made public the two relevant repositories<00:19:58.549> for<00:19:58.580> this<00:19:58.880> I'm<00:19:59.630> going<00:19:59.870> to<00:19:59.990> talk 00:20:00.159 --> 00:20:00.169 align:start position:0% repositories for this I'm going to talk 00:20:00.169 --> 00:20:02.110 align:start position:0% repositories for this I'm going to talk about<00:20:00.440> like<00:20:00.620> what<00:20:00.860> a<00:20:00.889> plugin<00:20:01.429> is<00:20:01.639> under<00:20:02.000> the 00:20:02.110 --> 00:20:02.120 align:start position:0% about like what a plugin is under the 00:20:02.120 --> 00:20:03.940 align:start position:0% about like what a plugin is under the hood<00:20:02.269> for<00:20:02.299> the<00:20:02.720> depths<00:20:03.169> of<00:20:03.230> the<00:20:03.350> roofs<00:20:03.529> who<00:20:03.769> can 00:20:03.940 --> 00:20:03.950 align:start position:0% hood for the depths of the roofs who can 00:20:03.950 --> 00:20:05.440 align:start position:0% hood for the depths of the roofs who can take<00:20:04.190> this<00:20:04.370> away<00:20:04.490> and<00:20:04.759> start<00:20:04.970> building<00:20:05.179> with 00:20:05.440 --> 00:20:05.450 align:start position:0% take this away and start building with 00:20:05.450 --> 00:20:08.259 align:start position:0% take this away and start building with it<00:20:05.769> we<00:20:06.769> have<00:20:06.799> a<00:20:06.919> fork<00:20:07.370> of<00:20:07.610> the<00:20:07.880> meta<00:20:08.059> mask 00:20:08.259 --> 00:20:08.269 align:start position:0% it we have a fork of the meta mask 00:20:08.269 --> 00:20:11.499 align:start position:0% it we have a fork of the meta mask extension<00:20:08.929> that<00:20:09.470> supports<00:20:09.980> the<00:20:10.509> plugin 00:20:11.499 --> 00:20:11.509 align:start position:0% extension that supports the plugin 00:20:11.509 --> 00:20:14.259 align:start position:0% extension that supports the plugin system<00:20:11.899> it<00:20:12.139> is<00:20:12.470> at<00:20:12.860> been<00:20:13.130> amassed<00:20:13.399> London<00:20:14.179> Bay 00:20:14.259 --> 00:20:14.269 align:start position:0% system it is at been amassed London Bay 00:20:14.269 --> 00:20:17.619 align:start position:0% system it is at been amassed London Bay though<00:20:14.450> we<00:20:15.289> also<00:20:15.500> have<00:20:15.889> a<00:20:16.629> command-line 00:20:17.619 --> 00:20:17.629 align:start position:0% though we also have a command-line 00:20:17.629 --> 00:20:21.310 align:start position:0% though we also have a command-line utility<00:20:18.620> called<00:20:18.980> MN<00:20:19.370> plugin<00:20:19.820> that<00:20:20.029> you<00:20:20.750> can 00:20:21.310 --> 00:20:21.320 align:start position:0% utility called MN plugin that you can 00:20:21.320 --> 00:20:24.369 align:start position:0% utility called MN plugin that you can use<00:20:21.470> to<00:20:21.620> build<00:20:21.769> configure<00:20:22.570> watch<00:20:23.570> for<00:20:24.259> file 00:20:24.369 --> 00:20:24.379 align:start position:0% use to build configure watch for file 00:20:24.379 --> 00:20:27.100 align:start position:0% use to build configure watch for file changes<00:20:24.799> has<00:20:25.220> served<00:20:25.490> them<00:20:25.639> locally<00:20:26.210> for 00:20:27.100 --> 00:20:27.110 align:start position:0% changes has served them locally for 00:20:27.110 --> 00:20:31.509 align:start position:0% changes has served them locally for testing<00:20:27.620> for<00:20:27.860> local<00:20:28.100> development<00:20:28.190> and<00:20:30.519> we 00:20:31.509 --> 00:20:31.519 align:start position:0% testing for local development and we 00:20:31.519 --> 00:20:34.330 align:start position:0% testing for local development and we have<00:20:31.730> on<00:20:32.059> the<00:20:32.500> venom<00:20:33.500> house<00:20:33.620> plugin<00:20:34.039> beta 00:20:34.330 --> 00:20:34.340 align:start position:0% have on the venom house plugin beta 00:20:34.340 --> 00:20:37.389 align:start position:0% have on the venom house plugin beta repository<00:20:35.210> a<00:20:35.299> wiki<00:20:36.019> that<00:20:36.230> should<00:20:37.070> contain 00:20:37.389 --> 00:20:37.399 align:start position:0% repository a wiki that should contain 00:20:37.399 --> 00:20:42.149 align:start position:0% repository a wiki that should contain everything<00:20:37.850> you<00:20:37.940> need<00:20:38.149> to<00:20:38.720> get<00:20:39.710> started<00:20:39.980> and 00:20:42.149 --> 00:20:42.159 align:start position:0% everything you need to get started and 00:20:42.159 --> 00:20:45.779 align:start position:0% everything you need to get started and so<00:20:43.159> what<00:20:43.610> is<00:20:43.789> so<00:20:44.480> as<00:20:44.779> far<00:20:44.990> as<00:20:45.049> the<00:20:45.169> meta<00:20:45.379> mask 00:20:45.779 --> 00:20:45.789 align:start position:0% so what is so as far as the meta mask 00:20:45.789 --> 00:20:49.299 align:start position:0% so what is so as far as the meta mask extension<00:20:46.789> is<00:20:46.909> concerned<00:20:47.330> a<00:20:47.659> plugin<00:20:48.620> is<00:20:48.860> two 00:20:49.299 --> 00:20:49.309 align:start position:0% extension is concerned a plugin is two 00:20:49.309 --> 00:20:52.330 align:start position:0% extension is concerned a plugin is two things<00:20:49.549> one<00:20:50.269> is<00:20:50.600> a<00:20:50.860> package.json<00:20:51.860> file 00:20:52.330 --> 00:20:52.340 align:start position:0% things one is a package.json file 00:20:52.340 --> 00:20:54.700 align:start position:0% things one is a package.json file following<00:20:53.059> the<00:20:53.210> conventions<00:20:53.960> established<00:20:54.620> by 00:20:54.700 --> 00:20:54.710 align:start position:0% following the conventions established by 00:20:54.710 --> 00:20:56.590 align:start position:0% following the conventions established by NPM<00:20:55.159> which<00:20:55.429> would<00:20:55.549> be<00:20:55.669> super<00:20:56.029> familiar<00:20:56.450> to 00:20:56.590 --> 00:20:56.600 align:start position:0% NPM which would be super familiar to 00:20:56.600 --> 00:21:02.049 align:start position:0% NPM which would be super familiar to most<00:20:56.690> of<00:20:56.899> you<00:20:57.039> and<00:20:58.480> second<00:20:59.480> is<00:20:59.750> a<00:21:00.789> source<00:21:01.789> file 00:21:02.049 --> 00:21:02.059 align:start position:0% most of you and second is a source file 00:21:02.059 --> 00:21:09.190 align:start position:0% most of you and second is a source file bundle<00:21:02.570> and<00:21:05.919> we<00:21:06.919> made<00:21:07.399> the<00:21:07.580> tool<00:21:07.759> mm<00:21:08.720> plugin<00:21:09.080> as 00:21:09.190 --> 00:21:09.200 align:start position:0% bundle and we made the tool mm plugin as 00:21:09.200 --> 00:21:11.560 align:start position:0% bundle and we made the tool mm plugin as I<00:21:09.289> said<00:21:09.500> to<00:21:09.710> help<00:21:10.490> you<00:21:10.700> get<00:21:10.970> started<00:21:11.120> with<00:21:11.419> that 00:21:11.560 --> 00:21:11.570 align:start position:0% I said to help you get started with that 00:21:11.570 --> 00:21:15.389 align:start position:0% I said to help you get started with that and<00:21:12.200> on<00:21:12.799> the<00:21:12.919> wiki<00:21:13.220> we<00:21:14.090> also<00:21:14.360> talked<00:21:14.750> about<00:21:14.779> the 00:21:15.389 --> 00:21:15.399 align:start position:0% and on the wiki we also talked about the 00:21:15.399 --> 00:21:18.639 align:start position:0% and on the wiki we also talked about the plug-in<00:21:16.399> API<00:21:16.580> which<00:21:17.059> is<00:21:17.179> the<00:21:17.299> API<00:21:17.659> that<00:21:18.080> the 00:21:18.639 --> 00:21:18.649 align:start position:0% plug-in API which is the API that the 00:21:18.649 --> 00:21:21.430 align:start position:0% plug-in API which is the API that the extension<00:21:19.549> exposes<00:21:20.179> to<00:21:20.450> the<00:21:20.600> plug-in<00:21:20.870> context 00:21:21.430 --> 00:21:21.440 align:start position:0% extension exposes to the plug-in context 00:21:21.440 --> 00:21:26.379 align:start position:0% extension exposes to the plug-in context as<00:21:22.009> Dan<00:21:22.309> mentioned<00:21:23.769> we<00:21:24.769> take<00:21:25.279> the<00:21:25.730> plugin 00:21:26.379 --> 00:21:26.389 align:start position:0% as Dan mentioned we take the plugin 00:21:26.389 --> 00:21:28.379 align:start position:0% as Dan mentioned we take the plugin bundle<00:21:26.720> we<00:21:26.929> load<00:21:27.139> it<00:21:27.289> into<00:21:27.409> the<00:21:27.529> extension<00:21:28.100> and 00:21:28.379 --> 00:21:28.389 align:start position:0% bundle we load it into the extension and 00:21:28.389 --> 00:21:31.830 align:start position:0% bundle we load it into the extension and execute<00:21:29.389> it<00:21:29.539> inside<00:21:30.110> of<00:21:30.379> a<00:21:30.500> cess<00:21:31.190> container 00:21:31.830 --> 00:21:31.840 align:start position:0% execute it inside of a cess container 00:21:31.840 --> 00:21:37.700 align:start position:0% execute it inside of a cess container that<00:21:32.840> container<00:21:33.399> doesn't<00:21:34.399> get<00:21:34.610> any 00:21:37.700 --> 00:21:37.710 align:start position:0% 00:21:37.710 --> 00:21:39.860 align:start position:0% any<00:21:37.920> sort<00:21:38.160> of<00:21:38.190> Global's<00:21:38.610> by<00:21:38.790> default<00:21:39.270> so<00:21:39.540> we 00:21:39.860 --> 00:21:39.870 align:start position:0% any sort of Global's by default so we 00:21:39.870 --> 00:21:43.100 align:start position:0% any sort of Global's by default so we inject<00:21:40.500> some<00:21:40.800> stuff<00:21:41.070> into<00:21:41.460> it<00:21:41.490> by<00:21:41.730> default<00:21:42.110> at 00:21:43.100 --> 00:21:43.110 align:start position:0% inject some stuff into it by default at 00:21:43.110 --> 00:21:46.220 align:start position:0% inject some stuff into it by default at the<00:21:43.230> moment<00:21:43.590> such<00:21:43.770> as<00:21:43.950> the<00:21:44.340> fetch<00:21:44.520> API<00:21:45.230> XML 00:21:46.220 --> 00:21:46.230 align:start position:0% the moment such as the fetch API XML 00:21:46.230 --> 00:21:50.590 align:start position:0% the moment such as the fetch API XML HTTP<00:21:47.160> request<00:21:47.520> and<00:21:47.790> so<00:21:48.510> on<00:21:48.690> we<00:21:49.680> are<00:21:49.860> also 00:21:50.590 --> 00:21:50.600 align:start position:0% HTTP request and so on we are also 00:21:50.600 --> 00:21:53.480 align:start position:0% HTTP request and so on we are also injecting<00:21:51.600> this<00:21:51.720> global<00:21:52.230> wallet<00:21:53.040> object 00:21:53.480 --> 00:21:53.490 align:start position:0% injecting this global wallet object 00:21:53.490 --> 00:21:56.570 align:start position:0% injecting this global wallet object which<00:21:54.030> represents<00:21:55.070> which<00:21:56.070> basically 00:21:56.570 --> 00:21:56.580 align:start position:0% which represents which basically 00:21:56.580 --> 00:21:58.520 align:start position:0% which represents which basically contains<00:21:56.880> most<00:21:57.300> of<00:21:57.510> the<00:21:57.570> methods<00:21:57.750> that<00:21:58.050> Madame 00:21:58.520 --> 00:21:58.530 align:start position:0% contains most of the methods that Madame 00:21:58.530 --> 00:22:01.610 align:start position:0% contains most of the methods that Madame s<00:21:58.650> uses<00:21:59.070> internally<00:21:59.760> to<00:22:00.660> construct<00:22:01.170> our<00:22:01.320> user 00:22:01.610 --> 00:22:01.620 align:start position:0% s uses internally to construct our user 00:22:01.620 --> 00:22:05.810 align:start position:0% s uses internally to construct our user interface<00:22:02.180> and<00:22:03.180> we<00:22:04.040> yeah<00:22:05.040> it's<00:22:05.310> basically<00:22:05.640> and 00:22:05.810 --> 00:22:05.820 align:start position:0% interface and we yeah it's basically and 00:22:05.820 --> 00:22:07.730 align:start position:0% interface and we yeah it's basically and and<00:22:06.090> also<00:22:06.390> a<00:22:06.570> bunch<00:22:06.780> of<00:22:06.900> provider<00:22:07.290> methods<00:22:07.680> so 00:22:07.730 --> 00:22:07.740 align:start position:0% and also a bunch of provider methods so 00:22:07.740 --> 00:22:09.350 align:start position:0% and also a bunch of provider methods so you<00:22:07.770> can<00:22:07.980> think<00:22:08.160> of<00:22:08.280> it<00:22:08.400> as<00:22:08.520> a<00:22:08.550> superset<00:22:09.120> of<00:22:09.270> the 00:22:09.350 --> 00:22:09.360 align:start position:0% you can think of it as a superset of the 00:22:09.360 --> 00:22:12.590 align:start position:0% you can think of it as a superset of the etherium<00:22:09.810> provider<00:22:10.340> and<00:22:11.340> we're<00:22:11.850> we're<00:22:12.540> still 00:22:12.590 --> 00:22:12.600 align:start position:0% etherium provider and we're we're still 00:22:12.600 --> 00:22:14.240 align:start position:0% etherium provider and we're we're still changing<00:22:13.200> stuff<00:22:13.410> and<00:22:13.680> we're<00:22:13.800> thinking<00:22:13.980> about 00:22:14.240 --> 00:22:14.250 align:start position:0% changing stuff and we're thinking about 00:22:14.250 --> 00:22:15.830 align:start position:0% changing stuff and we're thinking about like<00:22:14.610> we're<00:22:15.000> definitely<00:22:15.180> going<00:22:15.570> to<00:22:15.630> add 00:22:15.830 --> 00:22:15.840 align:start position:0% like we're definitely going to add 00:22:15.840 --> 00:22:18.680 align:start position:0% like we're definitely going to add methods<00:22:16.350> we<00:22:16.710> may<00:22:16.830> also<00:22:17.010> remove<00:22:17.610> some<00:22:17.640> edits<00:22:18.210> in 00:22:18.680 --> 00:22:18.690 align:start position:0% methods we may also remove some edits in 00:22:18.690 --> 00:22:21.650 align:start position:0% methods we may also remove some edits in flux<00:22:18.960> but<00:22:19.170> Brett<00:22:19.590> at<00:22:19.830> the<00:22:20.010> moment<00:22:20.400> a<00:22:20.660> plugin 00:22:21.650 --> 00:22:21.660 align:start position:0% flux but Brett at the moment a plugin 00:22:21.660 --> 00:22:23.780 align:start position:0% flux but Brett at the moment a plugin can<00:22:21.840> request<00:22:22.170> basically<00:22:22.740> any<00:22:22.980> method<00:22:23.490> that<00:22:23.520> we 00:22:23.780 --> 00:22:23.790 align:start position:0% can request basically any method that we 00:22:23.790 --> 00:22:25.970 align:start position:0% can request basically any method that we use<00:22:24.000> internally<00:22:24.450> except<00:22:25.260> for<00:22:25.470> some<00:22:25.590> super 00:22:25.970 --> 00:22:25.980 align:start position:0% use internally except for some super 00:22:25.980 --> 00:22:27.710 align:start position:0% use internally except for some super critical<00:22:26.550> key<00:22:26.790> management<00:22:27.120> stuff<00:22:27.510> that 00:22:27.710 --> 00:22:27.720 align:start position:0% critical key management stuff that 00:22:27.720 --> 00:22:29.870 align:start position:0% critical key management stuff that nobody<00:22:27.960> should<00:22:28.260> ever<00:22:28.320> be<00:22:28.560> able<00:22:28.770> to<00:22:28.890> request<00:22:29.220> a 00:22:29.870 --> 00:22:29.880 align:start position:0% nobody should ever be able to request a 00:22:29.880 --> 00:22:31.670 align:start position:0% nobody should ever be able to request a blanked<00:22:30.660> and<00:22:30.750> request<00:22:31.080> that<00:22:31.140> as<00:22:31.350> a<00:22:31.380> permission 00:22:31.670 --> 00:22:31.680 align:start position:0% blanked and request that as a permission 00:22:31.680 --> 00:22:35.120 align:start position:0% blanked and request that as a permission to<00:22:31.920> use<00:22:32.270> for<00:22:33.270> whatever<00:22:33.510> it<00:22:33.870> is<00:22:33.990> it's<00:22:34.680> trying<00:22:35.010> to 00:22:35.120 --> 00:22:35.130 align:start position:0% to use for whatever it is it's trying to 00:22:35.130 --> 00:22:40.160 align:start position:0% to use for whatever it is it's trying to do<00:22:36.080> and<00:22:38.120> for<00:22:39.120> my<00:22:39.240> next<00:22:39.450> trick<00:22:39.690> I'm<00:22:39.900> going<00:22:40.110> to 00:22:40.160 --> 00:22:40.170 align:start position:0% do and for my next trick I'm going to 00:22:40.170 --> 00:22:41.630 align:start position:0% do and for my next trick I'm going to show<00:22:40.230> you<00:22:40.410> how<00:22:40.890> to<00:22:40.920> get<00:22:41.190> started<00:22:41.400> with 00:22:41.630 --> 00:22:41.640 align:start position:0% show you how to get started with 00:22:41.640 --> 00:22:45.080 align:start position:0% show you how to get started with developing<00:22:41.990> meta<00:22:42.990> best<00:22:43.200> plugins<00:22:43.620> or<00:22:43.820> snaps<00:22:44.820> as 00:22:45.080 --> 00:22:45.090 align:start position:0% developing meta best plugins or snaps as 00:22:45.090 --> 00:22:50.390 align:start position:0% developing meta best plugins or snaps as that<00:22:45.270> leibrandt's<00:22:45.810> takes<00:22:47.000> and<00:22:48.470> so<00:22:49.470> for<00:22:50.250> me<00:22:50.340> the 00:22:50.390 --> 00:22:50.400 align:start position:0% that leibrandt's takes and so for me the 00:22:50.400 --> 00:22:52.460 align:start position:0% that leibrandt's takes and so for me the tool<00:22:50.700> m-f<00:22:51.090> plugin<00:22:51.420> so<00:22:51.660> all<00:22:51.810> i've<00:22:51.930> done<00:22:51.960> here<00:22:52.410> is 00:22:52.460 --> 00:22:52.470 align:start position:0% tool m-f plugin so all i've done here is 00:22:52.470 --> 00:22:55.010 align:start position:0% tool m-f plugin so all i've done here is i've<00:22:52.680> created<00:22:53.040> a<00:22:53.610> folder<00:22:53.940> for<00:22:54.240> my<00:22:54.360> project<00:22:54.810> I'm 00:22:55.010 --> 00:22:55.020 align:start position:0% i've created a folder for my project I'm 00:22:55.020 --> 00:22:57.410 align:start position:0% i've created a folder for my project I'm calling<00:22:55.320> it<00:22:55.440> full<00:22:55.560> of<00:22:55.590> world<00:22:56.030> and<00:22:57.030> we're<00:22:57.390> just 00:22:57.410 --> 00:22:57.420 align:start position:0% calling it full of world and we're just 00:22:57.420 --> 00:23:00.970 align:start position:0% calling it full of world and we're just going<00:22:57.630> to<00:22:57.690> call<00:22:57.810> me<00:22:57.960> mmm<00:22:58.140> plug-in<00:22:58.530> in<00:22:58.770> it<00:22:59.270> and 00:23:00.970 --> 00:23:00.980 align:start position:0% going to call me mmm plug-in in it and 00:23:00.980 --> 00:23:02.930 align:start position:0% going to call me mmm plug-in in it and so<00:23:01.980> the<00:23:02.130> first<00:23:02.310> thing<00:23:02.460> it's<00:23:02.580> going<00:23:02.610> to<00:23:02.730> do<00:23:02.820> is 00:23:02.930 --> 00:23:02.940 align:start position:0% so the first thing it's going to do is 00:23:02.940 --> 00:23:04.100 align:start position:0% so the first thing it's going to do is it's<00:23:03.090> just<00:23:03.120> going<00:23:03.270> to<00:23:03.420> walk<00:23:03.540> you<00:23:03.690> through<00:23:03.930> the 00:23:04.100 --> 00:23:04.110 align:start position:0% it's just going to walk you through the 00:23:04.110 --> 00:23:07.400 align:start position:0% it's just going to walk you through the usual<00:23:04.530> and<00:23:04.740> hit<00:23:05.630> workflow<00:23:06.630> to<00:23:06.960> create<00:23:07.290> the 00:23:07.400 --> 00:23:07.410 align:start position:0% usual and hit workflow to create the 00:23:07.410 --> 00:23:10.490 align:start position:0% usual and hit workflow to create the basic<00:23:07.590> package<00:23:07.950> not<00:23:08.220> JSON<00:23:08.690> so<00:23:09.690> we're<00:23:09.810> just<00:23:09.840> for 00:23:10.490 --> 00:23:10.500 align:start position:0% basic package not JSON so we're just for 00:23:10.500 --> 00:23:17.870 align:start position:0% basic package not JSON so we're just for this<00:23:11.090> hello 00:23:17.870 --> 00:23:17.880 align:start position:0% 00:23:17.880 --> 00:23:24.180 align:start position:0% all<00:23:18.880> of<00:23:19.090> us<00:23:22.110> great<00:23:23.110> and<00:23:23.410> so<00:23:23.710> we're<00:23:23.920> gonna<00:23:23.980> draw 00:23:24.180 --> 00:23:24.190 align:start position:0% all of us great and so we're gonna draw 00:23:24.190 --> 00:23:28.500 align:start position:0% all of us great and so we're gonna draw hands<00:23:24.400> to<00:23:24.520> accept<00:23:24.910> that<00:23:26.130> and<00:23:27.130> now<00:23:27.400> once<00:23:28.330> it's 00:23:28.500 --> 00:23:28.510 align:start position:0% hands to accept that and now once it's 00:23:28.510 --> 00:23:29.880 align:start position:0% hands to accept that and now once it's gone<00:23:28.630> through<00:23:28.840> the<00:23:28.960> regular<00:23:29.050> and<00:23:29.440> imminent 00:23:29.880 --> 00:23:29.890 align:start position:0% gone through the regular and imminent 00:23:29.890 --> 00:23:32.390 align:start position:0% gone through the regular and imminent then<00:23:30.070> we<00:23:30.280> add<00:23:30.460> some<00:23:30.490> more<00:23:30.970> stuff<00:23:31.290> that 00:23:32.390 --> 00:23:32.400 align:start position:0% then we add some more stuff that 00:23:32.400 --> 00:23:34.740 align:start position:0% then we add some more stuff that metamath<00:23:33.400> uses<00:23:33.730> to<00:23:33.880> identify<00:23:34.330> that<00:23:34.480> it<00:23:34.600> is<00:23:34.720> a 00:23:34.740 --> 00:23:34.750 align:start position:0% metamath uses to identify that it is a 00:23:34.750 --> 00:23:36.960 align:start position:0% metamath uses to identify that it is a plugin<00:23:35.050> and<00:23:35.320> how<00:23:35.410> to<00:23:35.470> load<00:23:35.650> it<00:23:35.680> and<00:23:35.980> so<00:23:36.130> on<00:23:36.250> and 00:23:36.960 --> 00:23:36.970 align:start position:0% plugin and how to load it and so on and 00:23:36.970 --> 00:23:39.240 align:start position:0% plugin and how to load it and so on and so<00:23:37.330> we're<00:23:38.170> just<00:23:38.200> going<00:23:38.440> to<00:23:38.470> use<00:23:38.560> the<00:23:38.800> defaults 00:23:39.240 --> 00:23:39.250 align:start position:0% so we're just going to use the defaults 00:23:39.250 --> 00:23:40.680 align:start position:0% so we're just going to use the defaults here<00:23:39.310> but<00:23:39.580> I'll<00:23:39.700> just<00:23:39.730> show<00:23:39.970> you<00:23:40.120> what<00:23:40.510> it 00:23:40.680 --> 00:23:40.690 align:start position:0% here but I'll just show you what it 00:23:40.690 --> 00:23:43.740 align:start position:0% here but I'll just show you what it looks<00:23:40.960> like<00:23:41.140> so<00:23:41.920> we<00:23:42.640> defined<00:23:42.970> a<00:23:43.060> local<00:23:43.360> server 00:23:43.740 --> 00:23:43.750 align:start position:0% looks like so we defined a local server 00:23:43.750 --> 00:23:45.510 align:start position:0% looks like so we defined a local server port<00:23:44.020> like<00:23:44.440> where<00:23:44.620> we'll<00:23:44.800> host<00:23:44.950> it<00:23:45.160> locally 00:23:45.510 --> 00:23:45.520 align:start position:0% port like where we'll host it locally 00:23:45.520 --> 00:23:49.440 align:start position:0% port like where we'll host it locally for<00:23:46.240> development<00:23:46.690> an<00:23:47.680> output<00:23:48.040> directory<00:23:48.520> and 00:23:49.440 --> 00:23:49.450 align:start position:0% for development an output directory and 00:23:49.450 --> 00:23:52.890 align:start position:0% for development an output directory and the<00:23:50.050> initial<00:23:50.500> permissions<00:23:50.950> that<00:23:51.820> the<00:23:52.240> plugin 00:23:52.890 --> 00:23:52.900 align:start position:0% the initial permissions that the plugin 00:23:52.900 --> 00:23:55.490 align:start position:0% the initial permissions that the plugin is<00:23:53.110> going<00:23:53.320> to<00:23:53.500> request<00:23:53.770> the<00:23:53.920> puppy<00:23:54.250> football 00:23:55.490 --> 00:23:55.500 align:start position:0% is going to request the puppy football 00:23:55.500 --> 00:23:58.650 align:start position:0% is going to request the puppy football and<00:23:56.500> Bruce<00:23:57.100> me<00:23:57.220> run<00:23:57.400> intercept<00:23:57.760> app<00:23:57.940> and<00:23:58.240> then 00:23:58.650 --> 00:23:58.660 align:start position:0% and Bruce me run intercept app and then 00:23:58.660 --> 00:24:01.020 align:start position:0% and Bruce me run intercept app and then it<00:23:58.930> did<00:23:59.110> a<00:23:59.140> bunch<00:23:59.320> of<00:23:59.440> stuff<00:23:59.820> but<00:24:00.820> all<00:24:00.910> it 00:24:01.020 --> 00:24:01.030 align:start position:0% it did a bunch of stuff but all it 00:24:01.030 --> 00:24:03.210 align:start position:0% it did a bunch of stuff but all it really<00:24:01.180> did<00:24:01.450> was<00:24:01.510> that<00:24:01.900> just<00:24:02.050> grow<00:24:02.320> the<00:24:02.920> files 00:24:03.210 --> 00:24:03.220 align:start position:0% really did was that just grow the files 00:24:03.220 --> 00:24:07.020 align:start position:0% really did was that just grow the files that<00:24:03.490> we'll<00:24:03.790> need<00:24:03.970> to<00:24:04.330> work<00:24:05.260> and<00:24:05.770> the<00:24:06.730> inside 00:24:07.020 --> 00:24:07.030 align:start position:0% that we'll need to work and the inside 00:24:07.030 --> 00:24:09.960 align:start position:0% that we'll need to work and the inside this<00:24:07.120> folder<00:24:07.570> we<00:24:07.890> have<00:24:08.890> the<00:24:09.130> bundle<00:24:09.430> itself<00:24:09.760> so 00:24:09.960 --> 00:24:09.970 align:start position:0% this folder we have the bundle itself so 00:24:09.970 --> 00:24:13.800 align:start position:0% this folder we have the bundle itself so it<00:24:10.240> just<00:24:10.420> wrote<00:24:10.780> these<00:24:10.990> files<00:24:11.610> with<00:24:12.610> like<00:24:12.850> the 00:24:13.800 --> 00:24:13.810 align:start position:0% it just wrote these files with like the 00:24:13.810 --> 00:24:15.810 align:start position:0% it just wrote these files with like the most<00:24:14.050> sort<00:24:14.440> of<00:24:14.530> minimal<00:24:14.950> hello<00:24:15.190> world<00:24:15.400> plugin 00:24:15.810 --> 00:24:15.820 align:start position:0% most sort of minimal hello world plugin 00:24:15.820 --> 00:24:17.700 align:start position:0% most sort of minimal hello world plugin and<00:24:16.150> you<00:24:16.360> might<00:24:16.540> want<00:24:16.780> this<00:24:17.020> a<00:24:17.050> framework<00:24:17.410> for 00:24:17.700 --> 00:24:17.710 align:start position:0% and you might want this a framework for 00:24:17.710 --> 00:24:20.490 align:start position:0% and you might want this a framework for you<00:24:17.800> to<00:24:17.860> get<00:24:17.980> started<00:24:18.310> with<00:24:18.460> and<00:24:19.420> also<00:24:19.570> build 00:24:20.490 --> 00:24:20.500 align:start position:0% you to get started with and also build 00:24:20.500 --> 00:24:23.610 align:start position:0% you to get started with and also build it<00:24:20.710> and<00:24:21.360> we<00:24:22.360> can<00:24:22.480> start<00:24:22.690> by<00:24:22.810> taking<00:24:22.990> a<00:24:23.200> look<00:24:23.350> at 00:24:23.610 --> 00:24:23.620 align:start position:0% it and we can start by taking a look at 00:24:23.620 --> 00:24:28.530 align:start position:0% it and we can start by taking a look at the<00:24:24.430> package<00:24:24.850> JSON<00:24:25.210> and<00:24:26.940> you'll<00:24:27.940> see<00:24:28.210> that<00:24:28.390> it 00:24:28.530 --> 00:24:28.540 align:start position:0% the package JSON and you'll see that it 00:24:28.540 --> 00:24:31.010 align:start position:0% the package JSON and you'll see that it looks<00:24:28.570> just<00:24:29.530> like<00:24:29.680> a<00:24:29.800> regular<00:24:30.070> package<00:24:30.430> JSON 00:24:31.010 --> 00:24:31.020 align:start position:0% looks just like a regular package JSON 00:24:31.020 --> 00:24:35.010 align:start position:0% looks just like a regular package JSON except<00:24:32.020> for<00:24:32.380> this<00:24:32.740> wave<00:24:33.340> 3<00:24:33.610> wallet<00:24:34.020> property 00:24:35.010 --> 00:24:35.020 align:start position:0% except for this wave 3 wallet property 00:24:35.020 --> 00:24:38.610 align:start position:0% except for this wave 3 wallet property here<00:24:35.260> it<00:24:36.010> contains<00:24:36.550> a<00:24:37.120> bundle<00:24:37.960> property<00:24:38.410> which 00:24:38.610 --> 00:24:38.620 align:start position:0% here it contains a bundle property which 00:24:38.620 --> 00:24:43.050 align:start position:0% here it contains a bundle property which tells<00:24:38.650> madam<00:24:39.610> s<00:24:39.730> where<00:24:40.000> the<00:24:40.180> bottle<00:24:40.510> is<00:24:41.880> so<00:24:42.880> you 00:24:43.050 --> 00:24:43.060 align:start position:0% tells madam s where the bottle is so you 00:24:43.060 --> 00:24:45.450 align:start position:0% tells madam s where the bottle is so you have<00:24:43.210> the<00:24:43.420> local<00:24:43.900> which<00:24:44.710> just<00:24:45.010> says<00:24:45.190> like 00:24:45.450 --> 00:24:45.460 align:start position:0% have the local which just says like 00:24:45.460 --> 00:24:47.040 align:start position:0% have the local which just says like where<00:24:45.730> is<00:24:45.940> the<00:24:46.120> bundle<00:24:46.300> relative<00:24:46.840> to<00:24:46.960> the 00:24:47.040 --> 00:24:47.050 align:start position:0% where is the bundle relative to the 00:24:47.050 --> 00:24:49.500 align:start position:0% where is the bundle relative to the project<00:24:47.410> root<00:24:47.530> and<00:24:47.800> then<00:24:47.920> the<00:24:47.950> URL<00:24:48.360> which<00:24:49.360> is 00:24:49.500 --> 00:24:49.510 align:start position:0% project root and then the URL which is 00:24:49.510 --> 00:24:52.770 align:start position:0% project root and then the URL which is where<00:24:49.690> it<00:24:49.780> will<00:24:49.930> be<00:24:50.050> hosted<00:24:50.520> and<00:24:51.520> if<00:24:52.300> this<00:24:52.570> were 00:24:52.770 --> 00:24:52.780 align:start position:0% where it will be hosted and if this were 00:24:52.780 --> 00:24:53.840 align:start position:0% where it will be hosted and if this were there<00:24:53.140> for<00:24:53.350> production 00:24:53.840 --> 00:24:53.850 align:start position:0% there for production 00:24:53.850 --> 00:24:56.690 align:start position:0% there for production and<00:24:53.940> that<00:24:54.630> would<00:24:54.780> be<00:24:54.900> like<00:24:55.080> the<00:24:55.230> URL<00:24:55.669> where<00:24:56.669> you 00:24:56.690 --> 00:24:56.700 align:start position:0% and that would be like the URL where you 00:24:56.700 --> 00:24:59.840 align:start position:0% and that would be like the URL where you are<00:24:57.059> hosting<00:24:57.450> the<00:24:57.570> plugin<00:24:57.900> bubble<00:24:58.200> online<00:24:58.850> and 00:24:59.840 --> 00:24:59.850 align:start position:0% are hosting the plugin bubble online and 00:24:59.850 --> 00:25:03.560 align:start position:0% are hosting the plugin bubble online and we<00:25:00.720> hope<00:25:00.900> to<00:25:01.049> support<00:25:01.350> DNS<00:25:01.950> and<00:25:02.299> and<00:25:03.299> other 00:25:03.560 --> 00:25:03.570 align:start position:0% we hope to support DNS and and other 00:25:03.570 --> 00:25:06.400 align:start position:0% we hope to support DNS and and other things<00:25:03.870> with<00:25:04.410> that<00:25:04.559> but<00:25:04.740> for<00:25:04.770> now<00:25:05.010> it's<00:25:05.280> just 00:25:06.400 --> 00:25:06.410 align:start position:0% things with that but for now it's just 00:25:06.410 --> 00:25:10.159 align:start position:0% things with that but for now it's just HTTP<00:25:08.000> and<00:25:09.000> the<00:25:09.150> initial<00:25:09.450> conditions<00:25:09.870> that's 00:25:10.159 --> 00:25:10.169 align:start position:0% HTTP and the initial conditions that's 00:25:10.169 --> 00:25:12.289 align:start position:0% HTTP and the initial conditions that's just<00:25:10.440> as<00:25:10.710> I<00:25:10.860> said<00:25:11.100> those<00:25:11.520> permissions<00:25:12.059> that<00:25:12.179> it 00:25:12.289 --> 00:25:12.299 align:start position:0% just as I said those permissions that it 00:25:12.299 --> 00:25:16.029 align:start position:0% just as I said those permissions that it will<00:25:12.419> request<00:25:12.720> when<00:25:12.960> it's<00:25:13.080> installed<00:25:13.880> and<00:25:14.880> so 00:25:16.029 --> 00:25:16.039 align:start position:0% will request when it's installed and so 00:25:16.039 --> 00:25:19.460 align:start position:0% will request when it's installed and so now<00:25:17.039> I'm<00:25:17.160> going<00:25:17.250> to<00:25:17.520> call<00:25:18.059> watch<00:25:18.570> so<00:25:19.140> we<00:25:19.260> can 00:25:19.460 --> 00:25:19.470 align:start position:0% now I'm going to call watch so we can 00:25:19.470 --> 00:25:29.410 align:start position:0% now I'm going to call watch so we can rebuild<00:25:20.100> on<00:25:20.340> change<00:25:20.669> and<00:25:22.400> serve<00:25:25.370> okay<00:25:27.530> here 00:25:29.410 --> 00:25:29.420 align:start position:0% rebuild on change and serve okay here 00:25:29.420 --> 00:25:31.409 align:start position:0% rebuild on change and serve okay here [Music] 00:25:31.409 --> 00:25:31.419 align:start position:0% [Music] 00:25:31.419 --> 00:25:36.449 align:start position:0% [Music] fresh<00:25:32.049> ah<00:25:33.089> it's<00:25:34.089> the<00:25:34.329> front<00:25:34.570> end<00:25:34.919> half-hour<00:25:35.919> on 00:25:36.449 --> 00:25:36.459 align:start position:0% fresh ah it's the front end half-hour on 00:25:36.459 --> 00:25:39.539 align:start position:0% fresh ah it's the front end half-hour on our<00:25:36.909> planet<00:25:37.209> and<00:25:37.749> inside<00:25:38.320> the<00:25:38.619> and<00:25:38.889> inside<00:25:39.279> the 00:25:39.539 --> 00:25:39.549 align:start position:0% our planet and inside the and inside the 00:25:39.549 --> 00:25:41.669 align:start position:0% our planet and inside the and inside the project<00:25:40.299> directory<00:25:40.690> it's<00:25:40.809> just<00:25:41.079> it<00:25:41.289> builds<00:25:41.589> an 00:25:41.669 --> 00:25:41.679 align:start position:0% project directory it's just it builds an 00:25:41.679 --> 00:25:43.949 align:start position:0% project directory it's just it builds an index.html<00:25:42.190> file<00:25:42.969> just<00:25:43.179> so<00:25:43.329> you<00:25:43.450> have<00:25:43.659> a<00:25:43.690> user 00:25:43.949 --> 00:25:43.959 align:start position:0% index.html file just so you have a user 00:25:43.959 --> 00:25:46.049 align:start position:0% index.html file just so you have a user interface<00:25:44.499> as<00:25:44.859> you<00:25:45.249> can<00:25:45.399> work<00:25:45.579> with<00:25:45.789> them<00:25:45.909> get 00:25:46.049 --> 00:25:46.059 align:start position:0% interface as you can work with them get 00:25:46.059 --> 00:25:47.489 align:start position:0% interface as you can work with them get a<00:25:46.089> feel<00:25:46.329> for<00:25:46.539> like<00:25:46.809> what<00:25:47.019> it<00:25:47.200> will<00:25:47.379> actually 00:25:47.489 --> 00:25:47.499 align:start position:0% a feel for like what it will actually 00:25:47.499 --> 00:25:50.999 align:start position:0% a feel for like what it will actually look<00:25:47.889> like<00:25:47.919> in<00:25:48.219> practice<00:25:49.289> and<00:25:50.289> so<00:25:50.320> in<00:25:50.859> my 00:25:50.999 --> 00:25:51.009 align:start position:0% look like in practice and so in my 00:25:51.009 --> 00:25:54.180 align:start position:0% look like in practice and so in my extension<00:25:51.729> here<00:25:52.089> I<00:25:52.269> have<00:25:52.989> the<00:25:53.289> plugin<00:25:53.919> version 00:25:54.180 --> 00:25:54.190 align:start position:0% extension here I have the plugin version 00:25:54.190 --> 00:25:56.039 align:start position:0% extension here I have the plugin version of<00:25:54.309> meta<00:25:54.489> mask<00:25:54.700> loaded<00:25:55.089> it's<00:25:55.749> going<00:25:55.899> to<00:25:55.959> make 00:25:56.039 --> 00:25:56.049 align:start position:0% of meta mask loaded it's going to make 00:25:56.049 --> 00:25:59.579 align:start position:0% of meta mask loaded it's going to make sure<00:25:56.109> that<00:25:56.379> my<00:25:56.559> state<00:25:56.950> is<00:25:57.249> clear<00:25:58.349> usually<00:25:59.349> you 00:25:59.579 --> 00:25:59.589 align:start position:0% sure that my state is clear usually you 00:25:59.589 --> 00:26:01.259 align:start position:0% sure that my state is clear usually you should<00:25:59.619> not<00:26:00.009> have<00:26:00.159> to<00:26:00.279> do<00:26:00.399> that<00:26:00.549> but<00:26:00.789> we<00:26:00.909> expose 00:26:01.259 --> 00:26:01.269 align:start position:0% should not have to do that but we expose 00:26:01.269 --> 00:26:03.659 align:start position:0% should not have to do that but we expose we<00:26:01.599> have<00:26:01.690> those<00:26:01.899> buttons<00:26:02.259> just<00:26:02.589> in<00:26:03.429> case<00:26:03.639> for 00:26:03.659 --> 00:26:03.669 align:start position:0% we have those buttons just in case for 00:26:03.669 --> 00:26:05.909 align:start position:0% we have those buttons just in case for development<00:26:04.149> purposes<00:26:04.329> and<00:26:04.899> then<00:26:05.799> I'm<00:26:05.889> just 00:26:05.909 --> 00:26:05.919 align:start position:0% development purposes and then I'm just 00:26:05.919 --> 00:26:08.609 align:start position:0% development purposes and then I'm just going<00:26:06.159> to<00:26:06.190> go<00:26:06.279> ahead<00:26:06.369> and<00:26:06.549> then<00:26:06.639> connect<00:26:07.619> and 00:26:08.609 --> 00:26:08.619 align:start position:0% going to go ahead and then connect and 00:26:08.619 --> 00:26:11.759 align:start position:0% going to go ahead and then connect and that<00:26:08.649> will<00:26:08.919> initiate<00:26:09.929> this<00:26:10.929> request<00:26:11.289> and<00:26:11.559> this 00:26:11.759 --> 00:26:11.769 align:start position:0% that will initiate this request and this 00:26:11.769 --> 00:26:14.279 align:start position:0% that will initiate this request and this is<00:26:12.009> this<00:26:12.369> request<00:26:12.789> here<00:26:13.059> is<00:26:13.299> the<00:26:13.450> dab<00:26:13.690> saying 00:26:14.279 --> 00:26:14.289 align:start position:0% is this request here is the dab saying 00:26:14.289 --> 00:26:16.560 align:start position:0% is this request here is the dab saying hey<00:26:14.589> meta<00:26:14.829> mask<00:26:15.070> can<00:26:15.669> I<00:26:15.759> talk<00:26:15.999> to<00:26:16.179> this<00:26:16.269> plugin 00:26:16.560 --> 00:26:16.570 align:start position:0% hey meta mask can I talk to this plugin 00:26:16.570 --> 00:26:18.959 align:start position:0% hey meta mask can I talk to this plugin and<00:26:16.959> also<00:26:17.559> install<00:26:17.950> it<00:26:18.159> if<00:26:18.339> it's<00:26:18.489> not<00:26:18.639> already 00:26:18.959 --> 00:26:18.969 align:start position:0% and also install it if it's not already 00:26:18.969 --> 00:26:21.749 align:start position:0% and also install it if it's not already installed<00:26:19.209> so<00:26:20.049> this<00:26:20.499> is<00:26:20.649> the<00:26:20.919> DAP<00:26:21.129> asking 00:26:21.749 --> 00:26:21.759 align:start position:0% installed so this is the DAP asking 00:26:21.759 --> 00:26:24.299 align:start position:0% installed so this is the DAP asking permission<00:26:21.940> to<00:26:22.359> use<00:26:22.749> the<00:26:22.959> plugin<00:26:23.169> and<00:26:23.829> we're 00:26:24.299 --> 00:26:24.309 align:start position:0% permission to use the plugin and we're 00:26:24.309 --> 00:26:27.569 align:start position:0% permission to use the plugin and we're going<00:26:24.459> to<00:26:24.519> go<00:26:24.609> ahead<00:26:24.669> and<00:26:24.879> say<00:26:24.999> yes<00:26:26.279> and<00:26:27.279> now 00:26:27.569 --> 00:26:27.579 align:start position:0% going to go ahead and say yes and now 00:26:27.579 --> 00:26:30.119 align:start position:0% going to go ahead and say yes and now this<00:26:28.179> request<00:26:28.570> so<00:26:28.929> we're<00:26:29.499> still<00:26:29.649> working<00:26:30.039> on 00:26:30.119 --> 00:26:30.129 align:start position:0% this request so we're still working on 00:26:30.129 --> 00:26:32.810 align:start position:0% this request so we're still working on exactly<00:26:30.609> what<00:26:30.789> this<00:26:30.940> is<00:26:30.999> going<00:26:31.509> to<00:26:31.739> look<00:26:32.739> like 00:26:32.810 --> 00:26:32.820 align:start position:0% exactly what this is going to look like 00:26:32.820 --> 00:26:36.119 align:start position:0% exactly what this is going to look like but<00:26:33.820> this<00:26:34.089> request<00:26:34.479> is<00:26:34.779> the<00:26:34.899> plugin<00:26:35.169> which<00:26:35.679> we 00:26:36.119 --> 00:26:36.129 align:start position:0% but this request is the plugin which we 00:26:36.129 --> 00:26:39.449 align:start position:0% but this request is the plugin which we had<00:26:36.219> just<00:26:36.249> now<00:26:36.700> installed<00:26:37.179> saying<00:26:37.989> hey<00:26:38.459> can 00:26:39.449 --> 00:26:39.459 align:start position:0% had just now installed saying hey can 00:26:39.459 --> 00:26:41.759 align:start position:0% had just now installed saying hey can hide<00:26:39.729> the<00:26:39.999> plugin<00:26:40.479> get<00:26:41.169> the<00:26:41.289> permission<00:26:41.679> to 00:26:41.759 --> 00:26:41.769 align:start position:0% hide the plugin get the permission to 00:26:41.769 --> 00:26:44.190 align:start position:0% hide the plugin get the permission to show<00:26:41.950> alerts<00:26:42.429> on<00:26:42.759> the<00:26:42.909> user's<00:26:43.239> page<00:26:43.419> and<00:26:44.019> as 00:26:44.190 --> 00:26:44.200 align:start position:0% show alerts on the user's page and as 00:26:44.200 --> 00:26:46.319 align:start position:0% show alerts on the user's page and as Dan<00:26:44.649> mentioned<00:26:44.759> currently<00:26:45.759> we're<00:26:45.940> just<00:26:46.119> using 00:26:46.319 --> 00:26:46.329 align:start position:0% Dan mentioned currently we're just using 00:26:46.329 --> 00:26:48.389 align:start position:0% Dan mentioned currently we're just using that<00:26:46.539> at<00:26:46.659> browser<00:26:46.929> defaults<00:26:47.619> for<00:26:47.769> alert<00:26:48.129> and 00:26:48.389 --> 00:26:48.399 align:start position:0% that at browser defaults for alert and 00:26:48.399 --> 00:26:51.149 align:start position:0% that at browser defaults for alert and confirmed<00:26:48.849> but<00:26:49.089> we're<00:26:49.389> gonna<00:26:49.679> and<00:26:50.679> eventually 00:26:51.149 --> 00:26:51.159 align:start position:0% confirmed but we're gonna and eventually 00:26:51.159 --> 00:26:53.909 align:start position:0% confirmed but we're gonna and eventually we<00:26:51.700> want<00:26:51.849> to<00:26:52.059> allow<00:26:52.329> plug-in<00:26:53.320> developers<00:26:53.739> to 00:26:53.909 --> 00:26:53.919 align:start position:0% we want to allow plug-in developers to 00:26:53.919 --> 00:26:55.560 align:start position:0% we want to allow plug-in developers to build<00:26:54.249> their<00:26:54.519> own<00:26:54.549> sort<00:26:55.119> of<00:26:55.179> custom 00:26:55.560 --> 00:26:55.570 align:start position:0% build their own sort of custom 00:26:55.570 --> 00:26:57.449 align:start position:0% build their own sort of custom confirmation<00:26:56.229> screens<00:26:56.529> so<00:26:57.070> say<00:26:57.219> that<00:26:57.399> you 00:26:57.449 --> 00:26:57.459 align:start position:0% confirmation screens so say that you 00:26:57.459 --> 00:26:59.249 align:start position:0% confirmation screens so say that you have<00:26:57.579> some<00:26:57.820> interaction<00:26:58.269> you<00:26:58.989> go<00:26:59.109> to<00:26:59.169> the 00:26:59.249 --> 00:26:59.259 align:start position:0% have some interaction you go to the 00:26:59.259 --> 00:27:01.589 align:start position:0% have some interaction you go to the plug-in<00:26:59.619> for<00:26:59.859> your<00:26:59.919> death<00:27:00.249> the<00:27:01.089> death<00:27:01.269> calls 00:27:01.589 --> 00:27:01.599 align:start position:0% plug-in for your death the death calls 00:27:01.599 --> 00:27:03.089 align:start position:0% plug-in for your death the death calls the<00:27:01.779> method<00:27:02.079> of<00:27:02.139> the<00:27:02.259> plug-in<00:27:02.619> and<00:27:02.859> you<00:27:02.889> want 00:27:03.089 --> 00:27:03.099 align:start position:0% the method of the plug-in and you want 00:27:03.099 --> 00:27:04.739 align:start position:0% the method of the plug-in and you want to<00:27:03.159> display<00:27:03.369> a<00:27:03.519> custom<00:27:03.729> confirmation<00:27:04.629> screen 00:27:04.739 --> 00:27:04.749 align:start position:0% to display a custom confirmation screen 00:27:04.749 --> 00:27:07.669 align:start position:0% to display a custom confirmation screen and<00:27:05.409> that's<00:27:05.669> initiated<00:27:06.669> from<00:27:06.759> inside<00:27:07.209> venom<00:27:07.539> s 00:27:07.669 --> 00:27:07.679 align:start position:0% and that's initiated from inside venom s 00:27:07.679 --> 00:27:09.659 align:start position:0% and that's initiated from inside venom s you'll<00:27:08.679> be<00:27:08.799> able<00:27:08.889> to<00:27:09.070> do<00:27:09.159> that<00:27:09.369> eventually 00:27:09.659 --> 00:27:09.669 align:start position:0% you'll be able to do that eventually 00:27:09.669 --> 00:27:12.419 align:start position:0% you'll be able to do that eventually that's<00:27:10.419> the<00:27:10.509> plan<00:27:10.719> but<00:27:11.079> we'll<00:27:11.919> submit<00:27:12.129> that 00:27:12.419 --> 00:27:12.429 align:start position:0% that's the plan but we'll submit that 00:27:12.429 --> 00:27:15.389 align:start position:0% that's the plan but we'll submit that and<00:27:12.869> this<00:27:13.869> plugin<00:27:14.139> being<00:27:14.619> very<00:27:14.829> simple<00:27:15.190> it<00:27:15.369> has 00:27:15.389 --> 00:27:15.399 align:start position:0% and this plugin being very simple it has 00:27:15.399 --> 00:27:17.129 align:start position:0% and this plugin being very simple it has on<00:27:15.669> hello<00:27:15.879> method<00:27:16.089> so<00:27:16.570> we're<00:27:16.690> going<00:27:16.779> to<00:27:16.869> send 00:27:17.129 --> 00:27:17.139 align:start position:0% on hello method so we're going to send 00:27:17.139 --> 00:27:19.979 align:start position:0% on hello method so we're going to send the<00:27:17.229> hello<00:27:17.440> method<00:27:17.799> and<00:27:18.329> that<00:27:19.329> super<00:27:19.809> tiny 00:27:19.979 --> 00:27:19.989 align:start position:0% the hello method and that super tiny 00:27:19.989 --> 00:27:24.080 align:start position:0% the hello method and that super tiny text<00:27:20.409> says<00:27:20.589> hello<00:27:21.399> localhost 00:27:24.080 --> 00:27:24.090 align:start position:0% 00:27:24.090 --> 00:27:27.080 align:start position:0% and<00:27:24.180> and<00:27:25.170> the<00:27:25.710> big<00:27:25.860> deal<00:27:26.130> we<00:27:26.580> didn't<00:27:26.850> come<00:27:26.970> from 00:27:27.080 --> 00:27:27.090 align:start position:0% and and the big deal we didn't come from 00:27:27.090 --> 00:27:29.960 align:start position:0% and and the big deal we didn't come from the<00:27:27.270> page<00:27:27.590> it<00:27:28.590> came<00:27:28.800> from<00:27:28.920> venomous<00:27:29.250> yes<00:27:29.580> it 00:27:29.960 --> 00:27:29.970 align:start position:0% the page it came from venomous yes it 00:27:29.970 --> 00:27:31.870 align:start position:0% the page it came from venomous yes it came<00:27:30.150> from<00:27:30.270> it<00:27:30.360> so<00:27:30.510> it<00:27:30.660> because<00:27:30.960> it<00:27:31.080> uses<00:27:31.290> the 00:27:31.870 --> 00:27:31.880 align:start position:0% came from it so it because it uses the 00:27:31.880 --> 00:27:34.430 align:start position:0% came from it so it because it uses the alert<00:27:32.880> method<00:27:33.360> that<00:27:33.570> we've<00:27:33.750> defined<00:27:33.960> inside 00:27:34.430 --> 00:27:34.440 align:start position:0% alert method that we've defined inside 00:27:34.440 --> 00:27:36.680 align:start position:0% alert method that we've defined inside meta<00:27:34.890> mask<00:27:35.130> which<00:27:35.790> is<00:27:35.910> the<00:27:36.060> permission<00:27:36.450> and<00:27:36.600> a 00:27:36.680 --> 00:27:36.690 align:start position:0% meta mask which is the permission and a 00:27:36.690 --> 00:27:39.110 align:start position:0% meta mask which is the permission and a sport<00:27:37.080> when<00:27:37.170> it<00:27:37.290> was<00:27:37.440> installed<00:27:37.910> and<00:27:38.910> that's 00:27:39.110 --> 00:27:39.120 align:start position:0% sport when it was installed and that's 00:27:39.120 --> 00:27:42.770 align:start position:0% sport when it was installed and that's where<00:27:39.330> the<00:27:39.390> notification<00:27:40.050> came<00:27:40.980> from<00:27:41.600> and<00:27:42.600> so 00:27:42.770 --> 00:27:42.780 align:start position:0% where the notification came from and so 00:27:42.780 --> 00:27:44.870 align:start position:0% where the notification came from and so the<00:27:42.960> big<00:27:43.140> deal<00:27:43.350> is<00:27:43.710> so<00:27:43.950> the<00:27:44.130> big<00:27:44.250> deal<00:27:44.490> here<00:27:44.760> is 00:27:44.870 --> 00:27:44.880 align:start position:0% the big deal is so the big deal here is 00:27:44.880 --> 00:27:47.780 align:start position:0% the big deal is so the big deal here is that<00:27:45.060> now<00:27:45.270> we've<00:27:45.630> effectively<00:27:46.550> extended<00:27:47.550> the 00:27:47.780 --> 00:27:47.790 align:start position:0% that now we've effectively extended the 00:27:47.790 --> 00:27:50.630 align:start position:0% that now we've effectively extended the venom<00:27:48.480> s<00:27:48.600> in<00:27:48.840> crazy<00:27:49.080> provider<00:27:49.590> with<00:27:50.190> an<00:27:50.280> RPC 00:27:50.630 --> 00:27:50.640 align:start position:0% venom s in crazy provider with an RPC 00:27:50.640 --> 00:27:53.480 align:start position:0% venom s in crazy provider with an RPC method<00:27:51.290> that<00:27:52.290> belongs<00:27:52.620> to<00:27:52.710> a<00:27:52.800> plug-in<00:27:53.220> that's 00:27:53.480 --> 00:27:53.490 align:start position:0% method that belongs to a plug-in that's 00:27:53.490 --> 00:27:54.230 align:start position:0% method that belongs to a plug-in that's running 00:27:54.230 --> 00:27:54.240 align:start position:0% running 00:27:54.240 --> 00:27:56.720 align:start position:0% running trustless<00:27:54.780> lis<00:27:55.020> inside<00:27:55.830> masked<00:27:56.100> men<00:27:56.460> amassed 00:27:56.720 --> 00:27:56.730 align:start position:0% trustless lis inside masked men amassed 00:27:56.730 --> 00:28:01.100 align:start position:0% trustless lis inside masked men amassed in<00:27:56.970> SS<00:27:57.420> container<00:27:57.780> and<00:27:59.120> so<00:28:00.120> if<00:28:00.270> we<00:28:00.450> look<00:28:00.690> under 00:28:01.100 --> 00:28:01.110 align:start position:0% in SS container and so if we look under 00:28:01.110 --> 00:28:03.710 align:start position:0% in SS container and so if we look under the<00:28:01.230> hood<00:28:01.380> here<00:28:01.860> of<00:28:02.250> what's<00:28:02.490> going<00:28:02.700> on<00:28:02.940> you<00:28:03.690> can 00:28:03.710 --> 00:28:03.720 align:start position:0% the hood here of what's going on you can 00:28:03.720 --> 00:28:10.340 align:start position:0% the hood here of what's going on you can start<00:28:04.110> with 00:28:10.340 --> 00:28:10.350 align:start position:0% 00:28:10.350 --> 00:28:13.490 align:start position:0% start<00:28:11.010> with<00:28:11.310> the<00:28:11.580> index.html 00:28:13.490 --> 00:28:13.500 align:start position:0% start with the index.html 00:28:13.500 --> 00:28:15.650 align:start position:0% start with the index.html so<00:28:14.340> this<00:28:14.460> is<00:28:14.640> the<00:28:14.850> web<00:28:15.150> page<00:28:15.180> we<00:28:15.540> were<00:28:15.630> just 00:28:15.650 --> 00:28:15.660 align:start position:0% so this is the web page we were just 00:28:15.660 --> 00:28:18.560 align:start position:0% so this is the web page we were just looking<00:28:15.930> for<00:28:16.290> our<00:28:16.320> front<00:28:16.800> end<00:28:16.980> as<00:28:17.190> it<00:28:17.340> works<00:28:17.570> as 00:28:18.560 --> 00:28:18.570 align:start position:0% looking for our front end as it works as 00:28:18.570 --> 00:28:20.390 align:start position:0% looking for our front end as it works as a<00:28:18.630> buttons<00:28:19.110> and<00:28:19.320> stuff<00:28:19.500> and<00:28:19.770> the<00:28:19.890> first<00:28:20.160> thing 00:28:20.390 --> 00:28:20.400 align:start position:0% a buttons and stuff and the first thing 00:28:20.400 --> 00:28:23.860 align:start position:0% a buttons and stuff and the first thing I<00:28:20.790> want<00:28:21.450> to<00:28:21.870> bring<00:28:22.380> your<00:28:22.560> attention<00:28:22.680> to<00:28:23.010> is 00:28:23.860 --> 00:28:23.870 align:start position:0% I want to bring your attention to is 00:28:23.870 --> 00:28:26.300 align:start position:0% I want to bring your attention to is this<00:28:24.870> connected<00:28:25.350> to<00:28:25.500> the<00:28:25.650> function<00:28:26.010> of<00:28:26.070> gear 00:28:26.300 --> 00:28:26.310 align:start position:0% this connected to the function of gear 00:28:26.310 --> 00:28:32.210 align:start position:0% this connected to the function of gear so<00:28:26.580> this<00:28:27.420> follows<00:28:27.720> the<00:28:28.230> EIP<00:28:29.030> 22:55<00:28:31.130> api<00:28:32.130> that 00:28:32.210 --> 00:28:32.220 align:start position:0% so this follows the EIP 22:55 api that 00:28:32.220 --> 00:28:35.650 align:start position:0% so this follows the EIP 22:55 api that damn<00:28:32.700> showed<00:28:33.450> earlier<00:28:33.780> in<00:28:33.900> his<00:28:34.080> slides<00:28:34.320> and<00:28:34.650> so 00:28:35.650 --> 00:28:35.660 align:start position:0% damn showed earlier in his slides and so 00:28:35.660 --> 00:28:38.870 align:start position:0% damn showed earlier in his slides and so this<00:28:36.660> is<00:28:36.810> again<00:28:37.080> the<00:28:37.320> dab<00:28:38.100> asking<00:28:38.670> for 00:28:38.870 --> 00:28:38.880 align:start position:0% this is again the dab asking for 00:28:38.880 --> 00:28:41.690 align:start position:0% this is again the dab asking for permissions<00:28:39.510> to<00:28:39.810> talk<00:28:40.200> to<00:28:40.350> the<00:28:40.440> plugin<00:28:40.800> and<00:28:40.980> so 00:28:41.690 --> 00:28:41.700 align:start position:0% permissions to talk to the plugin and so 00:28:41.700 --> 00:28:43.520 align:start position:0% permissions to talk to the plugin and so the<00:28:42.000> method<00:28:42.300> is<00:28:42.420> wallet<00:28:42.750> request<00:28:42.930> permissions 00:28:43.520 --> 00:28:43.530 align:start position:0% the method is wallet request permissions 00:28:43.530 --> 00:28:48.680 align:start position:0% the method is wallet request permissions and<00:28:44.390> the<00:28:45.920> permission<00:28:46.920> is<00:28:47.370> is<00:28:47.790> plug<00:28:48.090> in<00:28:48.210> origin 00:28:48.680 --> 00:28:48.690 align:start position:0% and the permission is is plug in origin 00:28:48.690 --> 00:28:57.170 align:start position:0% and the permission is is plug in origin strings<00:28:49.080> that<00:28:50.010> we<00:28:50.220> construct<00:28:53.060> and<00:28:56.180> so 00:28:57.170 --> 00:28:57.180 align:start position:0% strings that we construct and so 00:28:57.180 --> 00:28:59.000 align:start position:0% strings that we construct and so basically<00:28:57.840> and<00:28:58.080> basically<00:28:58.350> what<00:28:58.530> that<00:28:58.680> is<00:28:58.860> it 00:28:59.000 --> 00:28:59.010 align:start position:0% basically and basically what that is it 00:28:59.010 --> 00:29:02.540 align:start position:0% basically and basically what that is it just<00:28:59.220> that<00:28:59.430> takes<00:28:59.850> this<00:29:01.190> permission<00:29:02.190> and 00:29:02.540 --> 00:29:02.550 align:start position:0% just that takes this permission and 00:29:02.550 --> 00:29:06.050 align:start position:0% just that takes this permission and namespace<00:29:03.210> prefix<00:29:03.810> and<00:29:04.140> then<00:29:04.950> the<00:29:05.160> plugins 00:29:06.050 --> 00:29:06.060 align:start position:0% namespace prefix and then the plugins 00:29:06.060 --> 00:29:08.810 align:start position:0% namespace prefix and then the plugins origin<00:29:07.050> string<00:29:07.560> and<00:29:07.800> just<00:29:07.830> tacks<00:29:08.220> it<00:29:08.370> on<00:29:08.520> and 00:29:08.810 --> 00:29:08.820 align:start position:0% origin string and just tacks it on and 00:29:08.820 --> 00:29:11.120 align:start position:0% origin string and just tacks it on and just<00:29:08.850> add<00:29:09.540> towards<00:29:09.810> them<00:29:09.990> together<00:29:10.140> and<00:29:10.620> that 00:29:11.120 --> 00:29:11.130 align:start position:0% just add towards them together and that 00:29:11.130 --> 00:29:13.340 align:start position:0% just add towards them together and that becomes<00:29:11.490> a<00:29:11.610> permission<00:29:11.940> identifying<00:29:12.630> the 00:29:13.340 --> 00:29:13.350 align:start position:0% becomes a permission identifying the 00:29:13.350 --> 00:29:18.020 align:start position:0% becomes a permission identifying the and<00:29:13.950> then<00:29:15.200> we<00:29:16.200> have<00:29:16.440> the<00:29:17.280> send<00:29:17.580> handler 00:29:18.020 --> 00:29:18.030 align:start position:0% and then we have the send handler 00:29:18.030 --> 00:29:20.510 align:start position:0% and then we have the send handler here<00:29:18.480> which<00:29:19.260> again<00:29:19.410> just<00:29:19.740> uses<00:29:20.040> the<00:29:20.160> infeed 00:29:20.510 --> 00:29:20.520 align:start position:0% here which again just uses the infeed 00:29:20.520 --> 00:29:22.720 align:start position:0% here which again just uses the infeed provider<00:29:20.880> to<00:29:21.240> send<00:29:21.750> a<00:29:21.810> message<00:29:22.110> to<00:29:22.140> meta<00:29:22.410> mask 00:29:22.720 --> 00:29:22.730 align:start position:0% provider to send a message to meta mask 00:29:22.730 --> 00:29:26.960 align:start position:0% provider to send a message to meta mask but<00:29:23.730> now<00:29:23.910> the<00:29:24.510> method<00:29:24.960> we<00:29:25.740> use<00:29:25.920> plugin<00:29:26.610> origin 00:29:26.960 --> 00:29:26.970 align:start position:0% but now the method we use plugin origin 00:29:26.970 --> 00:29:28.850 align:start position:0% but now the method we use plugin origin as<00:29:27.120> the<00:29:27.300> method<00:29:27.690> which<00:29:28.200> tells<00:29:28.440> better<00:29:28.650> best 00:29:28.850 --> 00:29:28.860 align:start position:0% as the method which tells better best 00:29:28.860 --> 00:29:33.050 align:start position:0% as the method which tells better best hey<00:29:29.130> I<00:29:29.600> want<00:29:30.600> to<00:29:30.950> talk<00:29:31.950> to<00:29:32.160> the<00:29:32.340> plug-in<00:29:32.580> that's 00:29:33.050 --> 00:29:33.060 align:start position:0% hey I want to talk to the plug-in that's 00:29:33.060 --> 00:29:35.810 align:start position:0% hey I want to talk to the plug-in that's identified<00:29:33.510> by<00:29:33.810> this<00:29:33.870> string<00:29:34.290> and<00:29:34.820> inside 00:29:35.810 --> 00:29:35.820 align:start position:0% identified by this string and inside 00:29:35.820 --> 00:29:38.540 align:start position:0% identified by this string and inside here<00:29:36.180> we<00:29:36.360> send<00:29:36.600> an<00:29:36.720> object<00:29:37.230> that<00:29:38.160> can<00:29:38.340> take 00:29:38.540 --> 00:29:38.550 align:start position:0% here we send an object that can take 00:29:38.550 --> 00:29:40.490 align:start position:0% here we send an object that can take whatever<00:29:38.820> shape<00:29:39.270> the<00:29:39.540> plug-in<00:29:39.990> developer 00:29:40.490 --> 00:29:40.500 align:start position:0% whatever shape the plug-in developer 00:29:40.500 --> 00:29:43.400 align:start position:0% whatever shape the plug-in developer wants<00:29:40.830> it<00:29:40.950> to<00:29:41.040> take<00:29:41.510> but<00:29:42.510> we<00:29:42.720> just<00:29:42.930> used<00:29:43.170> like 00:29:43.400 --> 00:29:43.410 align:start position:0% wants it to take but we just used like 00:29:43.410 --> 00:29:47.000 align:start position:0% wants it to take but we just used like the<00:29:43.830> same<00:29:44.070> RPC<00:29:44.790> request<00:29:45.230> object<00:29:46.230> format<00:29:46.560> and 00:29:47.000 --> 00:29:47.010 align:start position:0% the same RPC request object format and 00:29:47.010 --> 00:29:50.720 align:start position:0% the same RPC request object format and there's<00:29:47.520> one<00:29:47.730> and<00:29:48.720> the<00:29:48.840> method<00:29:49.140> is<00:29:49.290> low<00:29:49.530> and<00:29:50.460> if 00:29:50.720 --> 00:29:50.730 align:start position:0% there's one and the method is low and if 00:29:50.730 --> 00:29:55.430 align:start position:0% there's one and the method is low and if we<00:29:50.910> look<00:29:51.120> at<00:29:51.330> the<00:29:51.570> plugin<00:29:51.930> source<00:29:52.170> code 00:29:55.430 --> 00:29:55.440 align:start position:0% 00:29:55.440 --> 00:29:58.940 align:start position:0% and<00:29:55.620> his<00:29:56.100> ten<00:29:56.400> lines<00:29:56.750> and<00:29:57.750> we<00:29:57.900> see<00:29:58.110> that<00:29:58.740> it 00:29:58.940 --> 00:29:58.950 align:start position:0% and his ten lines and we see that it 00:29:58.950 --> 00:30:00.710 align:start position:0% and his ten lines and we see that it defined<00:29:59.340> the<00:29:59.460> single<00:29:59.880> method<00:30:00.210> called<00:30:00.420> below 00:30:00.710 --> 00:30:00.720 align:start position:0% defined the single method called below 00:30:00.720 --> 00:30:05.180 align:start position:0% defined the single method called below and<00:30:01.200> it<00:30:01.830> sends<00:30:02.100> back<00:30:02.190> below<00:30:02.730> whatever<00:30:04.190> origin 00:30:05.180 --> 00:30:05.190 align:start position:0% and it sends back below whatever origin 00:30:05.190 --> 00:30:07.400 align:start position:0% and it sends back below whatever origin and<00:30:05.520> it<00:30:05.910> came<00:30:06.120> from<00:30:06.360> and<00:30:06.630> the<00:30:06.720> origin<00:30:07.140> here 00:30:07.400 --> 00:30:07.410 align:start position:0% and it came from and the origin here 00:30:07.410 --> 00:30:09.020 align:start position:0% and it came from and the origin here that's<00:30:07.650> the<00:30:07.800> origin<00:30:08.100> of<00:30:08.160> the<00:30:08.310> DAF<00:30:08.520> that<00:30:08.790> sent 00:30:09.020 --> 00:30:09.030 align:start position:0% that's the origin of the DAF that sent 00:30:09.030 --> 00:30:11.810 align:start position:0% that's the origin of the DAF that sent the<00:30:09.120> request<00:30:09.770> and<00:30:10.770> so<00:30:11.040> to<00:30:11.100> just<00:30:11.250> go<00:30:11.550> over<00:30:11.700> what 00:30:11.810 --> 00:30:11.820 align:start position:0% the request and so to just go over what 00:30:11.820 --> 00:30:14.780 align:start position:0% the request and so to just go over what we<00:30:12.120> have<00:30:12.240> going<00:30:12.510> on<00:30:12.660> here<00:30:12.980> we<00:30:13.980> have<00:30:14.100> this<00:30:14.280> as<00:30:14.550> I 00:30:14.780 --> 00:30:14.790 align:start position:0% we have going on here we have this as I 00:30:14.790 --> 00:30:17.000 align:start position:0% we have going on here we have this as I mentioned<00:30:15.150> the<00:30:15.210> global<00:30:15.660> wallet<00:30:16.590> up<00:30:16.770> that 00:30:17.000 --> 00:30:17.010 align:start position:0% mentioned the global wallet up that 00:30:17.010 --> 00:30:19.250 align:start position:0% mentioned the global wallet up that wallet<00:30:17.400> object<00:30:17.820> which<00:30:18.090> is<00:30:18.270> the<00:30:18.420> API<00:30:18.780> that<00:30:19.020> meta 00:30:19.250 --> 00:30:19.260 align:start position:0% wallet object which is the API that meta 00:30:19.260 --> 00:30:22.430 align:start position:0% wallet object which is the API that meta mask<00:30:19.500> exposes<00:30:20.070> to<00:30:20.100> the<00:30:20.250> plugin<00:30:20.640> and<00:30:21.440> this 00:30:22.430 --> 00:30:22.440 align:start position:0% mask exposes to the plugin and this 00:30:22.440 --> 00:30:27.350 align:start position:0% mask exposes to the plugin and this register<00:30:23.070> RPC<00:30:23.550> message<00:30:23.700> handler<00:30:24.270> is<00:30:24.840> what<00:30:26.360> if 00:30:27.350 --> 00:30:27.360 align:start position:0% register RPC message handler is what if 00:30:27.360 --> 00:30:29.270 align:start position:0% register RPC message handler is what if what<00:30:27.540> you<00:30:27.720> use<00:30:27.990> as<00:30:28.260> a<00:30:28.290> plugin<00:30:28.680> developer<00:30:29.130> to 00:30:29.270 --> 00:30:29.280 align:start position:0% what you use as a plugin developer to 00:30:29.280 --> 00:30:31.340 align:start position:0% what you use as a plugin developer to extend<00:30:29.670> the<00:30:29.790> meta<00:30:29.940> mask<00:30:30.180> in<00:30:30.390> to<00:30:30.780> effectively 00:30:31.340 --> 00:30:31.350 align:start position:0% extend the meta mask in to effectively 00:30:31.350 --> 00:30:34.640 align:start position:0% extend the meta mask in to effectively extend<00:30:31.830> the<00:30:32.340> Menem<00:30:32.640> s<00:30:32.790> in-page<00:30:33.380> provider<00:30:34.380> API 00:30:34.640 --> 00:30:34.650 align:start position:0% extend the Menem s in-page provider API 00:30:34.650 --> 00:30:37.100 align:start position:0% extend the Menem s in-page provider API and<00:30:35.250> so<00:30:35.760> that<00:30:35.880> takes<00:30:36.030> an<00:30:36.240> origin<00:30:36.600> string<00:30:36.870> which 00:30:37.100 --> 00:30:37.110 align:start position:0% and so that takes an origin string which 00:30:37.110 --> 00:30:40.130 align:start position:0% and so that takes an origin string which is<00:30:37.140> the<00:30:37.470> string<00:30:37.770> of<00:30:37.980> the<00:30:38.600> requesting<00:30:39.600> context 00:30:40.130 --> 00:30:40.140 align:start position:0% is the string of the requesting context 00:30:40.140 --> 00:30:40.880 align:start position:0% is the string of the requesting context like<00:30:40.350> the<00:30:40.500> daps 00:30:40.880 --> 00:30:40.890 align:start position:0% like the daps 00:30:40.890 --> 00:30:44.060 align:start position:0% like the daps origin<00:30:41.340> and<00:30:41.580> then<00:30:42.120> a<00:30:42.420> request<00:30:43.200> object<00:30:43.410> that 00:30:44.060 --> 00:30:44.070 align:start position:0% origin and then a request object that 00:30:44.070 --> 00:30:45.650 align:start position:0% origin and then a request object that can<00:30:44.250> be<00:30:44.310> whatever<00:30:44.610> shape<00:30:44.970> you<00:30:45.180> want<00:30:45.240> it 00:30:45.650 --> 00:30:45.660 align:start position:0% can be whatever shape you want it 00:30:45.660 --> 00:30:46.910 align:start position:0% can be whatever shape you want it doesn't<00:30:45.930> even<00:30:46.020> have<00:30:46.200> to<00:30:46.260> be<00:30:46.350> an<00:30:46.500> opportunity 00:30:46.910 --> 00:30:46.920 align:start position:0% doesn't even have to be an opportunity 00:30:46.920 --> 00:30:48.380 align:start position:0% doesn't even have to be an opportunity to<00:30:47.040> be<00:30:47.130> a<00:30:47.160> script<00:30:47.460> it<00:30:47.580> could<00:30:47.700> be<00:30:47.820> whatever<00:30:47.970> but 00:30:48.380 --> 00:30:48.390 align:start position:0% to be a script it could be whatever but 00:30:48.390 --> 00:30:52.580 align:start position:0% to be a script it could be whatever but and<00:30:50.150> by<00:30:51.150> convention<00:30:51.660> of<00:30:51.750> Markus<00:30:52.050> it<00:30:52.170> goes<00:30:52.410> on 00:30:52.580 --> 00:30:52.590 align:start position:0% and by convention of Markus it goes on 00:30:52.590 --> 00:30:57.110 align:start position:0% and by convention of Markus it goes on and<00:30:53.240> it<00:30:54.240> just<00:30:54.270> says<00:30:55.220> hello<00:30:56.220> origins<00:30:56.760> string<00:30:56.970> is 00:30:57.110 --> 00:30:57.120 align:start position:0% and it just says hello origins string is 00:30:57.120 --> 00:30:59.060 align:start position:0% and it just says hello origins string is what<00:30:57.270> it<00:30:57.390> returns<00:30:57.510> and<00:30:57.900> if<00:30:57.990> it<00:30:58.110> doesn't<00:30:58.560> get<00:30:59.010> a 00:30:59.060 --> 00:30:59.070 align:start position:0% what it returns and if it doesn't get a 00:30:59.070 --> 00:31:01.940 align:start position:0% what it returns and if it doesn't get a method<00:30:59.540> that<00:31:00.540> it<00:31:00.780> recognized<00:31:01.320> it<00:31:01.560> it 00:31:01.940 --> 00:31:01.950 align:start position:0% method that it recognized it it 00:31:01.950 --> 00:31:04.550 align:start position:0% method that it recognized it it recognizes<00:31:02.430> it<00:31:02.790> throws<00:31:03.060> an<00:31:03.210> error<00:31:03.360> and<00:31:03.720> so<00:31:04.350> we 00:31:04.550 --> 00:31:04.560 align:start position:0% recognizes it throws an error and so we 00:31:04.560 --> 00:31:07.790 align:start position:0% recognizes it throws an error and so we can<00:31:04.740> very<00:31:04.980> simply<00:31:05.220> alter<00:31:05.880> this<00:31:06.030> and<00:31:06.800> since 00:31:07.790 --> 00:31:07.800 align:start position:0% can very simply alter this and since 00:31:07.800 --> 00:31:12.990 align:start position:0% can very simply alter this and since we're<00:31:08.070> at<00:31:08.520> DEFCON<00:31:08.700> 5 00:31:12.990 --> 00:31:13.000 align:start position:0% 00:31:13.000 --> 00:31:17.430 align:start position:0% and<00:31:13.960> we'll<00:31:14.110> write<00:31:14.320> the<00:31:14.620> bill<00:31:15.630> and<00:31:16.630> we'll<00:31:17.260> go 00:31:17.430 --> 00:31:17.440 align:start position:0% and we'll write the bill and we'll go 00:31:17.440 --> 00:31:21.120 align:start position:0% and we'll write the bill and we'll go back<00:31:17.710> the<00:31:18.520> image<00:31:19.169> and<00:31:20.169> now<00:31:20.350> because<00:31:20.620> I<00:31:20.740> rebuilt 00:31:21.120 --> 00:31:21.130 align:start position:0% back the image and now because I rebuilt 00:31:21.130 --> 00:31:22.529 align:start position:0% back the image and now because I rebuilt the<00:31:21.250> plug-in<00:31:21.640> we're<00:31:22.059> going<00:31:22.210> to<00:31:22.270> we're<00:31:22.510> just 00:31:22.529 --> 00:31:22.539 align:start position:0% the plug-in we're going to we're just 00:31:22.539 --> 00:31:24.810 align:start position:0% the plug-in we're going to we're just going<00:31:22.809> to<00:31:22.870> do<00:31:23.320> the<00:31:23.530> Kinect<00:31:23.919> flow<00:31:24.130> again<00:31:24.429> and 00:31:24.810 --> 00:31:24.820 align:start position:0% going to do the Kinect flow again and 00:31:24.820 --> 00:31:29.669 align:start position:0% going to do the Kinect flow again and reinstall<00:31:25.419> it<00:31:25.450> and<00:31:27.480> now<00:31:28.480> if<00:31:28.630> we<00:31:28.720> send<00:31:28.990> below<00:31:29.200> we 00:31:29.669 --> 00:31:29.679 align:start position:0% reinstall it and now if we send below we 00:31:29.679 --> 00:31:39.260 align:start position:0% reinstall it and now if we send below we get<00:31:29.890> from<00:31:30.730> each<00:31:30.850> you<00:31:30.970> want<00:31:31.120> localhost<00:31:32.100> instead 00:31:39.260 --> 00:31:39.270 align:start position:0% 00:31:39.270 --> 00:31:43.289 align:start position:0% thanks<00:31:40.270> if<00:31:40.960> you<00:31:41.049> like<00:31:41.409> that<00:31:41.880> just<00:31:42.880> we<00:31:43.059> didn't 00:31:43.289 --> 00:31:43.299 align:start position:0% thanks if you like that just we didn't 00:31:43.299 --> 00:31:47.940 align:start position:0% thanks if you like that just we didn't see<00:31:44.250> what<00:31:45.250> these<00:31:45.400> examples<00:31:45.970> do<00:31:46.559> and<00:31:47.559> before<00:31:47.740> I 00:31:47.940 --> 00:31:47.950 align:start position:0% see what these examples do and before I 00:31:47.950 --> 00:31:49.740 align:start position:0% see what these examples do and before I do<00:31:48.010> that<00:31:48.130> was<00:31:48.520> there<00:31:48.669> a<00:31:48.700> question<00:31:48.850> in<00:31:49.179> the<00:31:49.299> back 00:31:49.740 --> 00:31:49.750 align:start position:0% do that was there a question in the back 00:31:49.750 --> 00:31:51.810 align:start position:0% do that was there a question in the back what<00:31:49.929> happens<00:31:50.289> when<00:31:50.470> the<00:31:50.650> remote<00:31:50.950> bundle<00:31:51.580> gets 00:31:51.810 --> 00:31:51.820 align:start position:0% what happens when the remote bundle gets 00:31:51.820 --> 00:31:55.380 align:start position:0% what happens when the remote bundle gets changed<00:31:52.179> if<00:31:52.450> you<00:31:52.539> not<00:31:52.690> the<00:31:52.870> in<00:31:53.080> app<00:31:53.370> and<00:31:54.370> so<00:31:54.730> we 00:31:55.380 --> 00:31:55.390 align:start position:0% changed if you not the in app and so we 00:31:55.390 --> 00:31:59.130 align:start position:0% changed if you not the in app and so we will<00:31:55.659> have<00:31:56.429> some<00:31:57.429> well-defined<00:31:58.240> way<00:31:58.780> of 00:31:59.130 --> 00:31:59.140 align:start position:0% will have some well-defined way of 00:31:59.140 --> 00:32:02.190 align:start position:0% will have some well-defined way of handling<00:31:59.650> updates<00:32:00.309> to<00:32:00.490> plugins<00:32:00.909> we<00:32:01.780> have<00:32:01.900> yet 00:32:02.190 --> 00:32:02.200 align:start position:0% handling updates to plugins we have yet 00:32:02.200 --> 00:32:05.130 align:start position:0% handling updates to plugins we have yet to<00:32:03.000> define<00:32:04.000> what<00:32:04.270> that's<00:32:04.419> going<00:32:04.659> to<00:32:04.750> look<00:32:04.929> like 00:32:05.130 --> 00:32:05.140 align:start position:0% to define what that's going to look like 00:32:05.140 --> 00:32:08.250 align:start position:0% to define what that's going to look like at<00:32:05.950> the<00:32:06.070> moment<00:32:06.190> since<00:32:06.580> it's<00:32:06.820> been<00:32:07.240> we<00:32:08.049> haven't 00:32:08.250 --> 00:32:08.260 align:start position:0% at the moment since it's been we haven't 00:32:08.260 --> 00:32:09.810 align:start position:0% at the moment since it's been we haven't defined<00:32:08.650> it<00:32:08.799> yet<00:32:08.860> since<00:32:09.220> nothing<00:32:09.429> is<00:32:09.640> in 00:32:09.810 --> 00:32:09.820 align:start position:0% defined it yet since nothing is in 00:32:09.820 --> 00:32:11.970 align:start position:0% defined it yet since nothing is in production<00:32:10.299> yet<00:32:10.450> but<00:32:11.260> there<00:32:11.409> will<00:32:11.559> be<00:32:11.620> a<00:32:11.770> way 00:32:11.970 --> 00:32:11.980 align:start position:0% production yet but there will be a way 00:32:11.980 --> 00:32:14.399 align:start position:0% production yet but there will be a way for<00:32:12.280> plug-ins<00:32:12.580> to<00:32:12.820> essentially<00:32:13.450> issue 00:32:14.399 --> 00:32:14.409 align:start position:0% for plug-ins to essentially issue 00:32:14.409 --> 00:32:16.409 align:start position:0% for plug-ins to essentially issue updates<00:32:15.010> to<00:32:15.159> themselves<00:32:15.730> like<00:32:15.909> let<00:32:16.150> users 00:32:16.409 --> 00:32:16.419 align:start position:0% updates to themselves like let users 00:32:16.419 --> 00:32:18.480 align:start position:0% updates to themselves like let users know<00:32:16.570> that<00:32:16.960> they're<00:32:17.080> updated<00:32:17.620> and<00:32:18.100> will<00:32:18.309> also 00:32:18.480 --> 00:32:18.490 align:start position:0% know that they're updated and will also 00:32:18.490 --> 00:32:21.750 align:start position:0% know that they're updated and will also provide<00:32:18.669> a<00:32:19.000> way<00:32:19.240> for<00:32:19.679> my<00:32:20.679> say<00:32:21.130> that<00:32:21.309> you<00:32:21.460> change 00:32:21.750 --> 00:32:21.760 align:start position:0% provide a way for my say that you change 00:32:21.760 --> 00:32:23.700 align:start position:0% provide a way for my say that you change say<00:32:22.330> that<00:32:22.510> because<00:32:22.809> the<00:32:22.929> plugins<00:32:23.260> can<00:32:23.380> persist 00:32:23.700 --> 00:32:23.710 align:start position:0% say that because the plugins can persist 00:32:23.710 --> 00:32:26.370 align:start position:0% say that because the plugins can persist their<00:32:23.950> state<00:32:24.250> also<00:32:24.549> and<00:32:25.090> will<00:32:25.659> also<00:32:25.990> expose<00:32:26.320> a 00:32:26.370 --> 00:32:26.380 align:start position:0% their state also and will also expose a 00:32:26.380 --> 00:32:28.890 align:start position:0% their state also and will also expose a way<00:32:26.620> for<00:32:27.039> updating<00:32:27.610> without<00:32:27.880> like<00:32:28.150> erasing<00:32:28.510> in 00:32:28.890 --> 00:32:28.900 align:start position:0% way for updating without like erasing in 00:32:28.900 --> 00:32:31.200 align:start position:0% way for updating without like erasing in its<00:32:29.049> state<00:32:29.530> its<00:32:30.039> local<00:32:30.429> state<00:32:30.669> inside<00:32:31.030> the 00:32:31.200 --> 00:32:31.210 align:start position:0% its state its local state inside the 00:32:31.210 --> 00:32:34.740 align:start position:0% its state its local state inside the users<00:32:31.539> attention<00:32:32.070> yeah<00:32:33.070> but<00:32:34.059> for<00:32:34.210> now<00:32:34.360> there 00:32:34.740 --> 00:32:34.750 align:start position:0% users attention yeah but for now there 00:32:34.750 --> 00:32:37.320 align:start position:0% users attention yeah but for now there is<00:32:35.039> every<00:32:36.039> time<00:32:36.220> you<00:32:36.520> update<00:32:36.700> you<00:32:37.150> just 00:32:37.320 --> 00:32:37.330 align:start position:0% is every time you update you just 00:32:37.330 --> 00:32:40.409 align:start position:0% is every time you update you just reinstall<00:32:37.840> it<00:32:37.870> and<00:32:38.049> it<00:32:38.260> wipes<00:32:38.500> everything<00:32:39.390> yes 00:32:40.409 --> 00:32:40.419 align:start position:0% reinstall it and it wipes everything yes 00:32:40.419 --> 00:32:43.470 align:start position:0% reinstall it and it wipes everything yes venomoth<00:32:41.110> and<00:32:41.440> local<00:32:41.770> to<00:32:41.980> or<00:32:42.280> your<00:32:42.429> justice<00:32:42.789> so 00:32:43.470 --> 00:32:43.480 align:start position:0% venomoth and local to or your justice so 00:32:43.480 --> 00:32:45.330 align:start position:0% venomoth and local to or your justice so how<00:32:43.720> this<00:32:43.900> is<00:32:43.960> going<00:32:44.230> to<00:32:44.350> work<00:32:44.380> with<00:32:44.679> mobile<00:32:45.130> is 00:32:45.330 --> 00:32:45.340 align:start position:0% how this is going to work with mobile is 00:32:45.340 --> 00:32:47.490 align:start position:0% how this is going to work with mobile is we<00:32:45.580> absolutely<00:32:46.000> want<00:32:46.539> it<00:32:46.840> to<00:32:47.110> work<00:32:47.230> with 00:32:47.490 --> 00:32:47.500 align:start position:0% we absolutely want it to work with 00:32:47.500 --> 00:32:49.690 align:start position:0% we absolutely want it to work with mobile<00:32:48.000> and 00:32:49.690 --> 00:32:49.700 align:start position:0% mobile and 00:32:49.700 --> 00:32:57.360 align:start position:0% mobile and but<00:32:49.820> how<00:32:49.940> we're<00:32:50.120> going<00:32:50.270> to<00:32:50.390> accomplish<00:32:51.110> that 00:32:57.360 --> 00:32:57.370 align:start position:0% 00:32:57.370 --> 00:33:03.550 align:start position:0% this<00:32:58.370> time<00:32:58.580> yeah<00:32:59.450> yeah<00:33:01.420> no<00:33:02.420> but<00:33:02.630> you're<00:33:03.440> right 00:33:03.550 --> 00:33:03.560 align:start position:0% this time yeah yeah no but you're right 00:33:03.560 --> 00:33:12.600 align:start position:0% this time yeah yeah no but you're right to<00:33:03.740> ask<00:33:03.830> if<00:33:04.310> you<00:33:04.400> want<00:33:04.550> to<00:33:04.640> go 00:33:12.600 --> 00:33:12.610 align:start position:0% 00:33:12.610 --> 00:33:25.340 align:start position:0% [Music] 00:33:25.340 --> 00:33:25.350 align:start position:0% 00:33:25.350 --> 00:33:27.600 align:start position:0% you<00:33:26.350> mean<00:33:26.500> content<00:33:27.040> the<00:33:27.130> plug-in<00:33:27.490> itself 00:33:27.600 --> 00:33:27.610 align:start position:0% you mean content the plug-in itself 00:33:27.610 --> 00:33:30.200 align:start position:0% you mean content the plug-in itself being<00:33:28.120> cooler 00:33:30.200 --> 00:33:30.210 align:start position:0% being cooler 00:33:30.210 --> 00:33:35.450 align:start position:0% being cooler and<00:33:31.210> probably<00:33:31.950> because<00:33:32.950> the<00:33:33.070> thing<00:33:33.760> is<00:33:33.910> like 00:33:35.450 --> 00:33:35.460 align:start position:0% and probably because the thing is like 00:33:35.460 --> 00:33:41.070 align:start position:0% and probably because the thing is like you<00:33:36.460> try<00:33:37.090> and<00:33:37.390> tell<00:33:37.600> us<00:33:37.780> what<00:33:38.110> errors<00:33:40.080> because 00:33:41.070 --> 00:33:41.080 align:start position:0% you try and tell us what errors because 00:33:41.080 --> 00:33:43.170 align:start position:0% you try and tell us what errors because yeah<00:33:41.980> we'll<00:33:42.190> talk<00:33:42.340> about<00:33:42.400> that<00:33:42.670> in<00:33:42.730> a<00:33:42.850> second 00:33:43.170 --> 00:33:43.180 align:start position:0% yeah we'll talk about that in a second 00:33:43.180 --> 00:33:44.430 align:start position:0% yeah we'll talk about that in a second because<00:33:43.240> like<00:33:43.510> what<00:33:43.660> the<00:33:43.780> build<00:33:43.960> script<00:33:44.200> does 00:33:44.430 --> 00:33:44.440 align:start position:0% because like what the build script does 00:33:44.440 --> 00:33:48.170 align:start position:0% because like what the build script does it<00:33:44.740> will<00:33:45.010> pull<00:33:45.220> in<00:33:45.400> all<00:33:45.610> of<00:33:45.760> your<00:33:46.230> dependencies 00:33:48.170 --> 00:33:48.180 align:start position:0% it will pull in all of your dependencies 00:33:48.180 --> 00:33:50.700 align:start position:0% it will pull in all of your dependencies when<00:33:49.180> you<00:33:49.300> build<00:33:49.540> and<00:33:49.840> then<00:33:50.200> we<00:33:50.320> run<00:33:50.530> them 00:33:50.700 --> 00:33:50.710 align:start position:0% when you build and then we run them 00:33:50.710 --> 00:33:53.550 align:start position:0% when you build and then we run them through<00:33:50.740> browserify<00:33:51.610> currently<00:33:52.300> and<00:33:53.230> so 00:33:53.550 --> 00:33:53.560 align:start position:0% through browserify currently and so 00:33:53.560 --> 00:33:55.860 align:start position:0% through browserify currently and so there<00:33:54.340> are<00:33:54.550> sometimes<00:33:54.970> issues<00:33:55.330> that<00:33:55.690> arise 00:33:55.860 --> 00:33:55.870 align:start position:0% there are sometimes issues that arise 00:33:55.870 --> 00:33:57.750 align:start position:0% there are sometimes issues that arise when<00:33:56.380> your<00:33:56.560> dependencies<00:33:57.250> are<00:33:57.370> being<00:33:57.580> too 00:33:57.750 --> 00:33:57.760 align:start position:0% when your dependencies are being too 00:33:57.760 --> 00:34:01.260 align:start position:0% when your dependencies are being too clever<00:33:58.090> with<00:33:58.540> JavaScript<00:33:59.080> bubbles<00:33:59.850> or<00:34:00.850> when 00:34:01.260 --> 00:34:01.270 align:start position:0% clever with JavaScript bubbles or when 00:34:01.270 --> 00:34:02.880 align:start position:0% clever with JavaScript bubbles or when they<00:34:01.390> do<00:34:01.570> dumb<00:34:01.870> stuff<00:34:01.900> that<00:34:02.380> they<00:34:02.470> should<00:34:02.650> in 00:34:02.880 --> 00:34:02.890 align:start position:0% they do dumb stuff that they should in 00:34:02.890 --> 00:34:14.149 align:start position:0% they do dumb stuff that they should in it<00:34:03.010> throws<00:34:03.280> errors 00:34:14.149 --> 00:34:14.159 align:start position:0% 00:34:14.159 --> 00:34:17.909 align:start position:0% yeah<00:34:15.480> it's<00:34:16.480> not<00:34:16.599> a<00:34:16.629> desktop<00:34:17.230> application<00:34:17.379> it's 00:34:17.909 --> 00:34:17.919 align:start position:0% yeah it's not a desktop application it's 00:34:17.919 --> 00:34:24.809 align:start position:0% yeah it's not a desktop application it's a<00:34:18.069> browser<00:34:18.310> extension<00:34:18.879> yeah<00:34:23.220> eventually<00:34:24.220> be 00:34:24.809 --> 00:34:24.819 align:start position:0% a browser extension yeah eventually be 00:34:24.819 --> 00:34:26.220 align:start position:0% a browser extension yeah eventually be something<00:34:25.210> we<00:34:25.419> would<00:34:25.629> have<00:34:25.869> to<00:34:25.990> go<00:34:26.109> to<00:34:26.139> a 00:34:26.220 --> 00:34:26.230 align:start position:0% something we would have to go to a 00:34:26.230 --> 00:34:28.200 align:start position:0% something we would have to go to a native<00:34:26.560> layer<00:34:26.740> and<00:34:27.010> it's<00:34:27.369> beyond<00:34:27.639> this<00:34:27.760> it's 00:34:28.200 --> 00:34:28.210 align:start position:0% native layer and it's beyond this it's 00:34:28.210 --> 00:34:32.190 align:start position:0% native layer and it's beyond this it's not<00:34:28.329> the<00:34:28.450> future<00:34:28.720> we're<00:34:28.869> using<00:34:31.079> what<00:34:32.079> any 00:34:32.190 --> 00:34:32.200 align:start position:0% not the future we're using what any 00:34:32.200 --> 00:34:35.250 align:start position:0% not the future we're using what any event<00:34:32.819> thank<00:34:33.819> you<00:34:33.879> for<00:34:34.000> your<00:34:34.089> question<00:34:34.510> and 00:34:35.250 --> 00:34:35.260 align:start position:0% event thank you for your question and 00:34:35.260 --> 00:34:37.349 align:start position:0% event thank you for your question and fear<00:34:36.220> for<00:34:36.369> the<00:34:36.460> examples<00:34:36.940> there<00:34:37.119> are<00:34:37.149> a<00:34:37.210> couple 00:34:37.349 --> 00:34:37.359 align:start position:0% fear for the examples there are a couple 00:34:37.359 --> 00:34:39.240 align:start position:0% fear for the examples there are a couple we<00:34:38.200> have<00:34:38.319> a<00:34:38.349> number<00:34:38.649> of<00:34:38.740> them<00:34:38.919> we're 00:34:39.240 --> 00:34:39.250 align:start position:0% we have a number of them we're 00:34:39.250 --> 00:34:41.909 align:start position:0% we have a number of them we're constantly<00:34:39.730> adding<00:34:40.179> to<00:34:40.210> them<00:34:40.470> hello<00:34:41.470> plugin 00:34:41.909 --> 00:34:41.919 align:start position:0% constantly adding to them hello plugin 00:34:41.919 --> 00:34:44.790 align:start position:0% constantly adding to them hello plugin here<00:34:42.159> is<00:34:42.429> the<00:34:42.819> one<00:34:42.970> you<00:34:43.119> get<00:34:43.389> when<00:34:43.450> you<00:34:43.899> run<00:34:44.139> em 00:34:44.790 --> 00:34:44.800 align:start position:0% here is the one you get when you run em 00:34:44.800 --> 00:34:47.700 align:start position:0% here is the one you get when you run em and<00:34:45.010> plug<00:34:45.159> it<00:34:45.310> in<00:34:45.399> it<00:34:45.929> and<00:34:46.929> the<00:34:47.050> first<00:34:47.260> one<00:34:47.500> I 00:34:47.700 --> 00:34:47.710 align:start position:0% and plug it in it and the first one I 00:34:47.710 --> 00:34:50.760 align:start position:0% and plug it in it and the first one I want<00:34:48.099> to<00:34:48.129> show<00:34:48.280> you<00:34:48.339> is<00:34:48.899> this<00:34:49.899> recipient 00:34:50.760 --> 00:34:50.770 align:start position:0% want to show you is this recipient 00:34:50.770 --> 00:34:54.980 align:start position:0% want to show you is this recipient address<00:34:51.240> officer<00:34:52.240> which<00:34:53.109> is<00:34:53.290> just<00:34:53.710> basically 00:34:54.980 --> 00:34:54.990 align:start position:0% address officer which is just basically 00:34:54.990 --> 00:34:58.410 align:start position:0% address officer which is just basically we've<00:34:55.990> added<00:34:56.230> and<00:34:57.210> internally<00:34:58.210> the<00:34:58.359> I 00:34:58.410 --> 00:34:58.420 align:start position:0% we've added and internally the I 00:34:58.420 --> 00:35:00.809 align:start position:0% we've added and internally the I amendment<00:34:58.869> that<00:34:59.050> allows<00:34:59.470> you<00:35:00.430> the<00:35:00.609> plugin 00:35:00.809 --> 00:35:00.819 align:start position:0% amendment that allows you the plugin 00:35:00.819 --> 00:35:04.800 align:start position:0% amendment that allows you the plugin developer<00:35:01.420> to<00:35:02.099> tell<00:35:03.099> madam<00:35:04.030> asked<00:35:04.210> what<00:35:04.630> is 00:35:04.800 --> 00:35:04.810 align:start position:0% developer to tell madam asked what is 00:35:04.810 --> 00:35:08.040 align:start position:0% developer to tell madam asked what is unsafe<00:35:05.680> for<00:35:05.859> a<00:35:05.920> safe<00:35:06.190> address<00:35:06.670> and<00:35:06.970> so<00:35:07.810> if<00:35:07.900> we 00:35:08.040 --> 00:35:08.050 align:start position:0% unsafe for a safe address and so if we 00:35:08.050 --> 00:35:10.980 align:start position:0% unsafe for a safe address and so if we look<00:35:08.230> at<00:35:08.349> the<00:35:08.640> package.json<00:35:09.640> here<00:35:10.240> the 00:35:10.980 --> 00:35:10.990 align:start position:0% look at the package.json here the 00:35:10.990 --> 00:35:14.400 align:start position:0% look at the package.json here the initial<00:35:11.440> permissions<00:35:11.920> requested<00:35:12.700> is<00:35:13.410> new 00:35:14.400 --> 00:35:14.410 align:start position:0% initial permissions requested is new 00:35:14.410 --> 00:35:16.170 align:start position:0% initial permissions requested is new unapproved<00:35:14.920> transaction<00:35:15.520> so<00:35:15.880> that's<00:35:16.060> an 00:35:16.170 --> 00:35:16.180 align:start position:0% unapproved transaction so that's an 00:35:16.180 --> 00:35:18.780 align:start position:0% unapproved transaction so that's an event<00:35:16.740> inside<00:35:17.740> the<00:35:17.829> metamath<00:35:18.220> that's<00:35:18.520> fired 00:35:18.780 --> 00:35:18.790 align:start position:0% event inside the metamath that's fired 00:35:18.790 --> 00:35:22.200 align:start position:0% event inside the metamath that's fired when<00:35:19.240> a<00:35:19.540> new<00:35:20.520> transaction<00:35:21.520> is<00:35:21.609> created<00:35:22.060> that 00:35:22.200 --> 00:35:22.210 align:start position:0% when a new transaction is created that 00:35:22.210 --> 00:35:24.720 align:start position:0% when a new transaction is created that the<00:35:22.240> user<00:35:22.480> has<00:35:22.720> to<00:35:22.960> approve<00:35:23.260> and<00:35:23.710> then<00:35:24.310> this 00:35:24.720 --> 00:35:24.730 align:start position:0% the user has to approve and then this 00:35:24.730 --> 00:35:27.000 align:start position:0% the user has to approve and then this new<00:35:25.119> address<00:35:25.569> audit<00:35:25.990> is<00:35:26.140> a<00:35:26.200> way<00:35:26.500> for<00:35:26.859> the 00:35:27.000 --> 00:35:27.010 align:start position:0% new address audit is a way for the 00:35:27.010 --> 00:35:32.490 align:start position:0% new address audit is a way for the plug-in<00:35:27.520> to<00:35:27.990> modify<00:35:29.250> that<00:35:30.250> screen<00:35:30.640> and<00:35:31.569> so 00:35:32.490 --> 00:35:32.500 align:start position:0% plug-in to modify that screen and so 00:35:32.500 --> 00:35:36.540 align:start position:0% plug-in to modify that screen and so here<00:35:32.740> we've<00:35:33.190> created<00:35:34.200> this<00:35:35.200> mock<00:35:35.589> audit<00:35:36.069> guide 00:35:36.540 --> 00:35:36.550 align:start position:0% here we've created this mock audit guide 00:35:36.550 --> 00:35:42.000 align:start position:0% here we've created this mock audit guide which<00:35:37.300> it<00:35:38.020> looks<00:35:38.290> at<00:35:38.589> whether<00:35:38.890> the<00:35:39.510> final<00:35:41.010> hex 00:35:42.000 --> 00:35:42.010 align:start position:0% which it looks at whether the final hex 00:35:42.010 --> 00:35:44.760 align:start position:0% which it looks at whether the final hex character<00:35:42.579> of<00:35:42.910> the<00:35:43.260> recipient<00:35:44.260> mattress<00:35:44.589> is<00:35:44.740> a 00:35:44.760 --> 00:35:44.770 align:start position:0% character of the recipient mattress is a 00:35:44.770 --> 00:35:47.099 align:start position:0% character of the recipient mattress is a letter<00:35:45.010> and<00:35:45.280> then<00:35:45.640> from<00:35:45.910> there<00:35:46.089> determines<00:35:46.990> if 00:35:47.099 --> 00:35:47.109 align:start position:0% letter and then from there determines if 00:35:47.109 --> 00:35:48.970 align:start position:0% letter and then from there determines if it's<00:35:47.290> safe 00:35:48.970 --> 00:35:48.980 align:start position:0% it's safe 00:35:48.980 --> 00:35:52.510 align:start position:0% it's safe and<00:35:49.250> here<00:35:50.210> what<00:35:50.840> then<00:35:51.080> so<00:35:51.349> what<00:35:52.160> this<00:35:52.280> plugin 00:35:52.510 --> 00:35:52.520 align:start position:0% and here what then so what this plugin 00:35:52.520 --> 00:35:54.820 align:start position:0% and here what then so what this plugin looks<00:35:52.790> like<00:35:52.970> is<00:35:53.180> we<00:35:53.540> say<00:35:53.840> we<00:35:54.290> create<00:35:54.800> a 00:35:54.820 --> 00:35:54.830 align:start position:0% looks like is we say we create a 00:35:54.830 --> 00:35:57.180 align:start position:0% looks like is we say we create a listener<00:35:55.310> for<00:35:55.640> new<00:35:55.849> unapproved<00:35:56.330> transaction 00:35:57.180 --> 00:35:57.190 align:start position:0% listener for new unapproved transaction 00:35:57.190 --> 00:36:02.140 align:start position:0% listener for new unapproved transaction and<00:35:58.190> whenever<00:35:59.180> a<00:35:59.270> transaction<00:35:59.950> appears<00:36:01.150> it's 00:36:02.140 --> 00:36:02.150 align:start position:0% and whenever a transaction appears it's 00:36:02.150 --> 00:36:05.170 align:start position:0% and whenever a transaction appears it's we<00:36:02.960> call<00:36:03.140> this<00:36:03.320> an<00:36:03.530> address<00:36:04.070> audit<00:36:04.490> method<00:36:04.910> and 00:36:05.170 --> 00:36:05.180 align:start position:0% we call this an address audit method and 00:36:05.180 --> 00:36:08.740 align:start position:0% we call this an address audit method and it<00:36:05.720> will<00:36:05.930> indicate<00:36:06.650> in<00:36:07.190> the<00:36:07.430> same<00:36:07.760> screen<00:36:08.060> if 00:36:08.740 --> 00:36:08.750 align:start position:0% it will indicate in the same screen if 00:36:08.750 --> 00:36:11.320 align:start position:0% it will indicate in the same screen if this<00:36:09.590> particular<00:36:10.280> plug-in<00:36:10.609> to<00:36:10.910> thinks<00:36:11.180> that 00:36:11.320 --> 00:36:11.330 align:start position:0% this particular plug-in to thinks that 00:36:11.330 --> 00:36:15.010 align:start position:0% this particular plug-in to thinks that the<00:36:11.420> recipient<00:36:11.960> is<00:36:12.200> safe<00:36:12.830> or<00:36:13.099> unsafe<00:36:13.130> or<00:36:14.020> where 00:36:15.010 --> 00:36:15.020 align:start position:0% the recipient is safe or unsafe or where 00:36:15.020 --> 00:36:18.490 align:start position:0% the recipient is safe or unsafe or where perhaps<00:36:15.400> unknown<00:36:16.400> if<00:36:16.640> the<00:36:17.230> plugin<00:36:18.230> doesn't 00:36:18.490 --> 00:36:18.500 align:start position:0% perhaps unknown if the plugin doesn't 00:36:18.500 --> 00:36:22.960 align:start position:0% perhaps unknown if the plugin doesn't have<00:36:18.590> an<00:36:18.710> opinion<00:36:19.210> so<00:36:20.210> now<00:36:20.540> we<00:36:20.950> now<00:36:21.950> we<00:36:21.980> can<00:36:22.609> add 00:36:22.960 --> 00:36:22.970 align:start position:0% have an opinion so now we now we can add 00:36:22.970 --> 00:36:25.420 align:start position:0% have an opinion so now we now we can add all<00:36:23.270> sorts<00:36:23.300> of<00:36:23.750> smart<00:36:24.500> like<00:36:24.920> contract 00:36:25.420 --> 00:36:25.430 align:start position:0% all sorts of smart like contract 00:36:25.430 --> 00:36:27.910 align:start position:0% all sorts of smart like contract security<00:36:25.910> recipients<00:36:26.750> security<00:36:27.200> and<00:36:27.470> plugins 00:36:27.910 --> 00:36:27.920 align:start position:0% security recipients security and plugins 00:36:27.920 --> 00:36:32.250 align:start position:0% security recipients security and plugins with<00:36:28.609> this<00:36:28.760> API<00:36:29.470> the<00:36:30.470> second<00:36:30.740> example<00:36:31.010> is 00:36:32.250 --> 00:36:32.260 align:start position:0% with this API the second example is 00:36:32.260 --> 00:36:35.290 align:start position:0% with this API the second example is custom<00:36:33.260> tokens<00:36:33.680> or<00:36:33.859> free<00:36:34.130> money<00:36:34.369> this<00:36:35.030> is<00:36:35.210> a 00:36:35.290 --> 00:36:35.300 align:start position:0% custom tokens or free money this is a 00:36:35.300 --> 00:36:38.410 align:start position:0% custom tokens or free money this is a lot<00:36:35.510> yeah<00:36:35.960> whoever<00:36:36.410> has<00:36:36.680> that<00:36:36.710> question<00:36:37.420> pay 00:36:38.410 --> 00:36:38.420 align:start position:0% lot yeah whoever has that question pay 00:36:38.420 --> 00:36:42.010 align:start position:0% lot yeah whoever has that question pay attention<00:36:39.369> so<00:36:40.369> here<00:36:40.550> are<00:36:40.970> our<00:36:41.510> only 00:36:42.010 --> 00:36:42.020 align:start position:0% attention so here are our only 00:36:42.020 --> 00:36:43.780 align:start position:0% attention so here are our only permission<00:36:42.290> is<00:36:42.500> this<00:36:42.650> wallet<00:36:42.890> manage<00:36:43.340> assets 00:36:43.780 --> 00:36:43.790 align:start position:0% permission is this wallet manage assets 00:36:43.790 --> 00:36:49.480 align:start position:0% permission is this wallet manage assets method<00:36:44.750> and<00:36:45.460> if<00:36:46.460> we<00:36:46.640> look<00:36:46.790> at<00:36:46.910> this<00:36:47.030> source<00:36:48.490> we 00:36:49.480 --> 00:36:49.490 align:start position:0% method and if we look at this source we 00:36:49.490 --> 00:36:52.240 align:start position:0% method and if we look at this source we define<00:36:49.849> our<00:36:50.090> own<00:36:50.300> free<00:36:50.840> money<00:36:51.080> token<00:36:51.920> here 00:36:52.240 --> 00:36:52.250 align:start position:0% define our own free money token here 00:36:52.250 --> 00:36:54.700 align:start position:0% define our own free money token here that<00:36:52.490> we<00:36:52.609> call<00:36:52.730> asset<00:36:53.210> and<00:36:53.450> that<00:36:54.230> this<00:36:54.470> one 00:36:54.700 --> 00:36:54.710 align:start position:0% that we call asset and that this one 00:36:54.710 --> 00:36:58.450 align:start position:0% that we call asset and that this one lives<00:36:55.010> in<00:36:55.250> memory<00:36:55.730> so<00:36:56.060> it<00:36:57.020> won't<00:36:57.290> be<00:36:57.470> very<00:36:57.710> it 00:36:58.450 --> 00:36:58.460 align:start position:0% lives in memory so it won't be very it 00:36:58.460 --> 00:37:01.150 align:start position:0% lives in memory so it won't be very it won't<00:36:58.640> make<00:36:59.119> you<00:36:59.240> rich<00:36:59.270> for<00:36:59.630> very<00:36:59.810> long<00:37:00.010> but<00:37:01.010> we 00:37:01.150 --> 00:37:01.160 align:start position:0% won't make you rich for very long but we 00:37:01.160 --> 00:37:01.660 align:start position:0% won't make you rich for very long but we can<00:37:01.280> a<00:37:01.339> man 00:37:01.660 --> 00:37:01.670 align:start position:0% can a man 00:37:01.670 --> 00:37:03.819 align:start position:0% can a man and<00:37:01.760> that<00:37:02.029> you<00:37:02.329> know<00:37:02.450> it's<00:37:02.900> some<00:37:03.170> ERC 00:37:03.819 --> 00:37:03.829 align:start position:0% and that you know it's some ERC 00:37:03.829 --> 00:37:06.359 align:start position:0% and that you know it's some ERC interface<00:37:04.819> that's<00:37:05.299> uncommon<00:37:05.779> to<00:37:05.930> meta<00:37:06.079> mask 00:37:06.359 --> 00:37:06.369 align:start position:0% interface that's uncommon to meta mask 00:37:06.369 --> 00:37:08.710 align:start position:0% interface that's uncommon to meta mask but<00:37:07.369> that<00:37:07.549> you<00:37:07.789> the<00:37:07.880> plugin<00:37:08.119> developer<00:37:08.569> know 00:37:08.710 --> 00:37:08.720 align:start position:0% but that you the plugin developer know 00:37:08.720 --> 00:37:11.890 align:start position:0% but that you the plugin developer know about<00:37:08.990> and<00:37:09.319> so<00:37:09.920> we<00:37:10.760> just<00:37:10.910> find<00:37:11.119> this<00:37:11.660> object 00:37:11.890 --> 00:37:11.900 align:start position:0% about and so we just find this object 00:37:11.900 --> 00:37:14.529 align:start position:0% about and so we just find this object that<00:37:12.470> tells<00:37:13.220> men<00:37:13.460> amassed<00:37:13.730> some<00:37:13.910> basic<00:37:14.299> stuff 00:37:14.529 --> 00:37:14.539 align:start position:0% that tells men amassed some basic stuff 00:37:14.539 --> 00:37:17.500 align:start position:0% that tells men amassed some basic stuff like<00:37:14.779> presumably<00:37:15.470> if<00:37:15.890> it's<00:37:16.039> acid<00:37:16.490> it<00:37:17.150> has<00:37:17.299> some 00:37:17.500 --> 00:37:17.510 align:start position:0% like presumably if it's acid it has some 00:37:17.510 --> 00:37:20.140 align:start position:0% like presumably if it's acid it has some sort<00:37:17.660> of<00:37:17.779> symbol<00:37:17.990> imbalance<00:37:19.150> identifier 00:37:20.140 --> 00:37:20.150 align:start position:0% sort of symbol imbalance identifier 00:37:20.150 --> 00:37:24.099 align:start position:0% sort of symbol imbalance identifier maybe<00:37:20.630> an<00:37:20.750> image<00:37:21.099> maybe<00:37:22.099> some<00:37:22.339> decimals<00:37:23.109> and 00:37:24.099 --> 00:37:24.109 align:start position:0% maybe an image maybe some decimals and 00:37:24.109 --> 00:37:29.230 align:start position:0% maybe an image maybe some decimals and then<00:37:25.299> we<00:37:26.299> have<00:37:26.539> a<00:37:27.369> RPC<00:37:28.369> message<00:37:28.549> handler<00:37:29.000> so 00:37:29.230 --> 00:37:29.240 align:start position:0% then we have a RPC message handler so 00:37:29.240 --> 00:37:32.740 align:start position:0% then we have a RPC message handler so from<00:37:29.420> the<00:37:29.539> in<00:37:29.660> page<00:37:30.130> the<00:37:31.130> user<00:37:31.519> can<00:37:31.910> never<00:37:32.359> get 00:37:32.740 --> 00:37:32.750 align:start position:0% from the in page the user can never get 00:37:32.750 --> 00:37:35.500 align:start position:0% from the in page the user can never get the<00:37:32.930> balance<00:37:33.440> of<00:37:33.680> this<00:37:33.890> custom<00:37:34.250> token<00:37:34.609> it<00:37:35.359> can 00:37:35.500 --> 00:37:35.510 align:start position:0% the balance of this custom token it can 00:37:35.510 --> 00:37:38.319 align:start position:0% the balance of this custom token it can bend<00:37:35.720> more<00:37:36.019> of<00:37:36.109> them<00:37:36.430> it<00:37:37.430> convert<00:37:37.819> them<00:37:38.089> and 00:37:38.319 --> 00:37:38.329 align:start position:0% bend more of them it convert them and 00:37:38.329 --> 00:37:42.279 align:start position:0% bend more of them it convert them and then<00:37:39.109> here<00:37:39.440> in<00:37:39.589> this<00:37:39.710> update<00:37:40.010> UI<00:37:41.019> function<00:37:42.019> it 00:37:42.279 --> 00:37:42.289 align:start position:0% then here in this update UI function it 00:37:42.289 --> 00:37:44.920 align:start position:0% then here in this update UI function it basically<00:37:43.069> keeps<00:37:43.760> track<00:37:44.119> of<00:37:44.150> like<00:37:44.480> what<00:37:44.720> is 00:37:44.920 --> 00:37:44.930 align:start position:0% basically keeps track of like what is 00:37:44.930 --> 00:37:48.460 align:start position:0% basically keeps track of like what is the<00:37:45.170> status<00:37:45.559> of<00:37:45.710> my<00:37:46.240> of<00:37:47.240> this<00:37:47.569> asset<00:37:47.990> so 00:37:48.460 --> 00:37:48.470 align:start position:0% the status of my of this asset so 00:37:48.470 --> 00:37:49.809 align:start position:0% the status of my of this asset so imagine<00:37:48.950> like<00:37:48.980> if<00:37:49.220> it's<00:37:49.369> actually<00:37:49.700> I'm 00:37:49.809 --> 00:37:49.819 align:start position:0% imagine like if it's actually I'm 00:37:49.819 --> 00:37:51.819 align:start position:0% imagine like if it's actually I'm chained<00:37:50.059> you<00:37:50.329> could<00:37:50.480> query<00:37:50.750> the<00:37:51.619> chain 00:37:51.819 --> 00:37:51.829 align:start position:0% chained you could query the chain 00:37:51.829 --> 00:37:53.529 align:start position:0% chained you could query the chain somehow<00:37:52.190> you<00:37:52.490> can<00:37:52.609> actually<00:37:52.760> send<00:37:53.150> a<00:37:53.269> request 00:37:53.529 --> 00:37:53.539 align:start position:0% somehow you can actually send a request 00:37:53.539 --> 00:37:56.680 align:start position:0% somehow you can actually send a request to<00:37:53.720> meta<00:37:53.990> mask<00:37:54.230> to<00:37:54.829> like<00:37:55.010> read<00:37:55.390> read<00:37:56.390> from<00:37:56.539> the 00:37:56.680 --> 00:37:56.690 align:start position:0% to meta mask to like read read from the 00:37:56.690 --> 00:37:58.299 align:start position:0% to meta mask to like read read from the blockchain<00:37:56.869> and<00:37:57.289> see<00:37:57.529> what<00:37:57.769> your<00:37:57.890> asset<00:37:58.190> is 00:37:58.299 --> 00:37:58.309 align:start position:0% blockchain and see what your asset is 00:37:58.309 --> 00:38:01.720 align:start position:0% blockchain and see what your asset is doing<00:37:58.670> and<00:37:58.910> then<00:37:59.450> you<00:37:59.839> can<00:37:59.990> update<00:38:00.470> it<00:38:00.730> using 00:38:01.720 --> 00:38:01.730 align:start position:0% doing and then you can update it using 00:38:01.730 --> 00:38:04.299 align:start position:0% doing and then you can update it using this<00:38:01.819> wallet<00:38:02.089> that<00:38:02.359> segment<00:38:02.869> so<00:38:03.470> here<00:38:03.710> is<00:38:04.010> that 00:38:04.299 --> 00:38:04.309 align:start position:0% this wallet that segment so here is that 00:38:04.309 --> 00:38:06.039 align:start position:0% this wallet that segment so here is that this<00:38:04.490> is<00:38:04.670> actually<00:38:04.819> the<00:38:05.150> plugin<00:38:05.539> sending<00:38:05.960> an 00:38:06.039 --> 00:38:06.049 align:start position:0% this is actually the plugin sending an 00:38:06.049 --> 00:38:09.640 align:start position:0% this is actually the plugin sending an RPC<00:38:06.410> request<00:38:06.940> from<00:38:07.940> inside<00:38:08.450> meta<00:38:08.750> mask<00:38:09.019> to 00:38:09.640 --> 00:38:09.650 align:start position:0% RPC request from inside meta mask to 00:38:09.650 --> 00:38:12.400 align:start position:0% RPC request from inside meta mask to mathematical<00:38:10.400> in<00:38:11.299> order<00:38:11.599> that<00:38:11.630> it<00:38:12.230> should 00:38:12.400 --> 00:38:12.410 align:start position:0% mathematical in order that it should 00:38:12.410 --> 00:38:16.329 align:start position:0% mathematical in order that it should update<00:38:12.529> the<00:38:13.029> the<00:38:14.029> assets<00:38:14.420> and<00:38:15.170> that's<00:38:15.769> and<00:38:16.160> so 00:38:16.329 --> 00:38:16.339 align:start position:0% update the the assets and that's and so 00:38:16.339 --> 00:38:17.769 align:start position:0% update the the assets and that's and so and<00:38:16.579> that<00:38:16.730> has<00:38:16.910> it<00:38:17.059> will<00:38:17.180> be<00:38:17.359> displayed<00:38:17.750> like 00:38:17.769 --> 00:38:17.779 align:start position:0% and that has it will be displayed like 00:38:17.779 --> 00:38:18.700 align:start position:0% and that has it will be displayed like in<00:38:18.140> the<00:38:18.289> Tony 00:38:18.700 --> 00:38:18.710 align:start position:0% in the Tony 00:38:18.710 --> 00:38:22.360 align:start position:0% in the Tony or<00:38:19.190> in<00:38:19.310> the<00:38:19.400> asset<00:38:19.760> listening<00:38:20.180> cycle<00:38:21.370> and 00:38:22.360 --> 00:38:22.370 align:start position:0% or in the asset listening cycle and 00:38:22.370 --> 00:38:25.000 align:start position:0% or in the asset listening cycle and finally<00:38:22.910> one<00:38:23.750> cool<00:38:23.990> thing<00:38:24.020> you<00:38:24.260> can<00:38:24.410> also<00:38:24.740> do 00:38:25.000 --> 00:38:25.010 align:start position:0% finally one cool thing you can also do 00:38:25.010 --> 00:38:27.220 align:start position:0% finally one cool thing you can also do is<00:38:25.310> add<00:38:25.700> new<00:38:26.060> forms<00:38:26.360> of<00:38:26.420> cryptography<00:38:26.780> to 00:38:27.220 --> 00:38:27.230 align:start position:0% is add new forms of cryptography to 00:38:27.230 --> 00:38:29.350 align:start position:0% is add new forms of cryptography to metamath<00:38:27.680> which<00:38:27.920> previously<00:38:28.280> was<00:38:28.730> hard<00:38:29.090> but 00:38:29.350 --> 00:38:29.360 align:start position:0% metamath which previously was hard but 00:38:29.360 --> 00:38:32.140 align:start position:0% metamath which previously was hard but now<00:38:29.420> is<00:38:29.810> very<00:38:30.050> easy<00:38:30.380> as<00:38:30.740> you<00:38:30.770> will<00:38:31.040> see<00:38:31.220> that 00:38:32.140 --> 00:38:32.150 align:start position:0% now is very easy as you will see that 00:38:32.150 --> 00:38:34.480 align:start position:0% now is very easy as you will see that this<00:38:32.390> plug-in<00:38:32.660> has<00:38:33.170> confirmed<00:38:33.980> as<00:38:34.430> a 00:38:34.480 --> 00:38:34.490 align:start position:0% this plug-in has confirmed as a 00:38:34.490 --> 00:38:39.400 align:start position:0% this plug-in has confirmed as a permission<00:38:35.060> just<00:38:35.450> for<00:38:36.250> like<00:38:37.250> the<00:38:38.030> UX<00:38:38.930> purposes 00:38:39.400 --> 00:38:39.410 align:start position:0% permission just for like the UX purposes 00:38:39.410 --> 00:38:42.310 align:start position:0% permission just for like the UX purposes for<00:38:40.190> the<00:38:40.310> demo<00:38:40.580> but<00:38:41.480> if<00:38:41.630> we<00:38:41.750> look<00:38:41.900> at<00:38:41.990> the<00:38:42.050> index 00:38:42.310 --> 00:38:42.320 align:start position:0% for the demo but if we look at the index 00:38:42.320 --> 00:38:46.270 align:start position:0% for the demo but if we look at the index here<00:38:42.700> we<00:38:43.700> important<00:38:44.210> this<00:38:44.330> pls<00:38:45.290> 12<00:38:45.620> 3<00:38:45.890> 1 00:38:46.270 --> 00:38:46.280 align:start position:0% here we important this pls 12 3 1 00:38:46.280 --> 00:38:51.880 align:start position:0% here we important this pls 12 3 1 library<00:38:46.810> and<00:38:48.790> we<00:38:49.790> use<00:38:50.030> the<00:38:50.480> wallet<00:38:51.230> on<00:38:51.410> get<00:38:51.650> app 00:38:51.880 --> 00:38:51.890 align:start position:0% library and we use the wallet on get app 00:38:51.890 --> 00:38:54.640 align:start position:0% library and we use the wallet on get app key<00:38:52.130> that<00:38:52.760> Dan<00:38:52.970> mentioned<00:38:53.290> so<00:38:54.290> I<00:38:54.350> have<00:38:54.440> a<00:38:54.500> case 00:38:54.640 --> 00:38:54.650 align:start position:0% key that Dan mentioned so I have a case 00:38:54.650 --> 00:38:55.690 align:start position:0% key that Dan mentioned so I have a case of<00:38:54.770> something<00:38:54.950> we've<00:38:55.190> been<00:38:55.370> researching 00:38:55.690 --> 00:38:55.700 align:start position:0% of something we've been researching 00:38:55.700 --> 00:38:58.390 align:start position:0% of something we've been researching internally<00:38:56.390> for<00:38:56.570> some<00:38:56.750> time<00:38:56.990> and<00:38:57.400> we 00:38:58.390 --> 00:38:58.400 align:start position:0% internally for some time and we 00:38:58.400 --> 00:39:01.690 align:start position:0% internally for some time and we essentially<00:38:58.760> we<00:38:59.030> get<00:38:59.270> a<00:38:59.540> a<00:39:00.280> private<00:39:01.280> key<00:39:01.550> we 00:39:01.690 --> 00:39:01.700 align:start position:0% essentially we get a a private key we 00:39:01.700 --> 00:39:04.300 align:start position:0% essentially we get a a private key we treat<00:39:01.940> the<00:39:02.060> map<00:39:02.390> key<00:39:02.600> as<00:39:02.690> the<00:39:02.840> private<00:39:03.200> key<00:39:03.350> we 00:39:04.300 --> 00:39:04.310 align:start position:0% treat the map key as the private key we 00:39:04.310 --> 00:39:07.180 align:start position:0% treat the map key as the private key we call<00:39:04.610> the<00:39:04.910> get<00:39:05.810> public<00:39:06.200> key<00:39:06.380> method<00:39:06.920> of<00:39:07.040> this 00:39:07.180 --> 00:39:07.190 align:start position:0% call the get public key method of this 00:39:07.190 --> 00:39:10.210 align:start position:0% call the get public key method of this MPLS<00:39:07.880> library<00:39:08.360> and<00:39:08.630> now<00:39:09.200> suddenly<00:39:09.710> we<00:39:10.070> can 00:39:10.210 --> 00:39:10.220 align:start position:0% MPLS library and now suddenly we can 00:39:10.220 --> 00:39:12.730 align:start position:0% MPLS library and now suddenly we can sign<00:39:10.490> an<00:39:10.670> arbitrary<00:39:11.180> data<00:39:11.390> and<00:39:11.720> do<00:39:12.020> all<00:39:12.440> the 00:39:12.730 --> 00:39:12.740 align:start position:0% sign an arbitrary data and do all the 00:39:12.740 --> 00:39:15.250 align:start position:0% sign an arbitrary data and do all the usual<00:39:12.770> key<00:39:13.580> pair<00:39:13.790> stuff<00:39:14.060> with<00:39:14.690> this<00:39:14.870> app<00:39:15.050> key 00:39:15.250 --> 00:39:15.260 align:start position:0% usual key pair stuff with this app key 00:39:15.260 --> 00:39:18.460 align:start position:0% usual key pair stuff with this app key and<00:39:15.500> this<00:39:15.650> new<00:39:15.860> an<00:39:16.100> odd<00:39:17.080> public<00:39:18.080> key<00:39:18.200> that<00:39:18.230> we 00:39:18.460 --> 00:39:18.470 align:start position:0% and this new an odd public key that we 00:39:18.470 --> 00:39:21.400 align:start position:0% and this new an odd public key that we created<00:39:19.180> and<00:39:20.180> if<00:39:20.690> you<00:39:20.840> think<00:39:21.050> that's<00:39:21.260> cool 00:39:21.400 --> 00:39:21.410 align:start position:0% created and if you think that's cool 00:39:21.410 --> 00:39:24.370 align:start position:0% created and if you think that's cool that<00:39:21.890> we<00:39:22.490> have<00:39:22.760> Tom<00:39:23.060> from<00:39:23.570> start<00:39:23.900> with<00:39:24.110> here 00:39:24.370 --> 00:39:24.380 align:start position:0% that we have Tom from start with here 00:39:24.380 --> 00:39:27.820 align:start position:0% that we have Tom from start with here who<00:39:24.770> is<00:39:25.730> actually<00:39:26.330> doing<00:39:26.600> something<00:39:26.830> useful 00:39:27.820 --> 00:39:27.830 align:start position:0% who is actually doing something useful 00:39:27.830 --> 00:39:48.640 align:start position:0% who is actually doing something useful with<00:39:27.980> this<00:39:28.130> exact<00:39:28.910> eSports<00:39:29.450> hope<00:39:30.350> yes 00:39:48.640 --> 00:39:48.650 align:start position:0% 00:39:48.650 --> 00:40:00.890 align:start position:0% yeah 00:40:00.890 --> 00:40:00.900 align:start position:0% 00:40:00.900 --> 00:40:04.980 align:start position:0% okay<00:40:01.920> so<00:40:02.920> just<00:40:03.670> a<00:40:03.789> quick<00:40:03.970> intro<00:40:04.359> my<00:40:04.720> name<00:40:04.869> is 00:40:04.980 --> 00:40:04.990 align:start position:0% okay so just a quick intro my name is 00:40:04.990 --> 00:40:07.589 align:start position:0% okay so just a quick intro my name is Donna<00:40:05.260> and<00:40:05.470> I'm<00:40:05.770> a<00:40:05.940> protocol<00:40:06.940> research<00:40:07.390> and 00:40:07.589 --> 00:40:07.599 align:start position:0% Donna and I'm a protocol research and 00:40:07.599 --> 00:40:12.089 align:start position:0% Donna and I'm a protocol research and product<00:40:08.410> manager<00:40:08.799> in<00:40:08.920> start<00:40:09.220> with<00:40:10.950> we<00:40:11.950> our 00:40:12.089 --> 00:40:12.099 align:start position:0% product manager in start with we our 00:40:12.099 --> 00:40:16.520 align:start position:0% product manager in start with we our company<00:40:13.059> based<00:40:13.270> in<00:40:13.390> Israel<00:40:13.780> and<00:40:14.079> were 00:40:16.520 --> 00:40:16.530 align:start position:0% 00:40:16.530 --> 00:40:19.440 align:start position:0% development<00:40:17.530> for<00:40:17.799> the<00:40:17.859> position<00:40:18.339> of<00:40:18.490> zero 00:40:19.440 --> 00:40:19.450 align:start position:0% development for the position of zero 00:40:19.450 --> 00:40:21.180 align:start position:0% development for the position of zero knowledge<00:40:19.630> groups<00:40:20.020> basically<00:40:20.380> starts<00:40:20.920> a 00:40:21.180 --> 00:40:21.190 align:start position:0% knowledge groups basically starts a 00:40:21.190 --> 00:40:23.910 align:start position:0% knowledge groups basically starts a first<00:40:21.880> product<00:40:22.210> which<00:40:22.720> Oran<00:40:23.500> which<00:40:23.650> is<00:40:23.770> also 00:40:23.910 --> 00:40:23.920 align:start position:0% first product which Oran which is also 00:40:23.920 --> 00:40:26.460 align:start position:0% first product which Oran which is also here<00:40:24.190> announced<00:40:24.670> today<00:40:25.510> on<00:40:25.750> the<00:40:25.839> main<00:40:26.020> stages 00:40:26.460 --> 00:40:26.470 align:start position:0% here announced today on the main stages 00:40:26.470 --> 00:40:28.170 align:start position:0% here announced today on the main stages are<00:40:26.680> there<00:40:27.280> in<00:40:27.460> tools<00:40:27.730> can<00:40:28.000> a<00:40:28.030> business 00:40:28.170 --> 00:40:28.180 align:start position:0% are there in tools can a business 00:40:28.180 --> 00:40:31.890 align:start position:0% are there in tools can a business solution<00:40:29.130> enabled<00:40:30.130> self<00:40:30.789> custody<00:40:31.329> training 00:40:31.890 --> 00:40:31.900 align:start position:0% solution enabled self custody training 00:40:31.900 --> 00:40:34.140 align:start position:0% solution enabled self custody training which<00:40:32.710> hopefully<00:40:32.950> will<00:40:33.400> be<00:40:33.579> live<00:40:33.910> and 00:40:34.140 --> 00:40:34.150 align:start position:0% which hopefully will be live and 00:40:34.150 --> 00:40:36.359 align:start position:0% which hopefully will be live and maintenance<00:40:34.500> married<00:40:35.500> together<00:40:36.130> with<00:40:36.339> a 00:40:36.359 --> 00:40:36.369 align:start position:0% maintenance married together with a 00:40:36.369 --> 00:40:38.789 align:start position:0% maintenance married together with a partner<00:40:36.609> say<00:40:37.089> the<00:40:37.299> first<00:40:37.480> fight<00:40:37.780> which<00:40:38.440> was<00:40:38.470> a 00:40:38.789 --> 00:40:38.799 align:start position:0% partner say the first fight which was a 00:40:38.799 --> 00:40:42.870 align:start position:0% partner say the first fight which was a Phoenix<00:40:39.130> a<00:40:39.420> months<00:40:40.420> ago<00:40:40.630> and<00:40:41.470> then<00:40:42.130> what<00:40:42.760> we're 00:40:42.870 --> 00:40:42.880 align:start position:0% Phoenix a months ago and then what we're 00:40:42.880 --> 00:40:45.380 align:start position:0% Phoenix a months ago and then what we're going<00:40:43.000> to<00:40:43.059> show<00:40:43.270> you<00:40:43.299> today<00:40:43.809> is<00:40:44.109> basically<00:40:44.770> a 00:40:45.380 --> 00:40:45.390 align:start position:0% going to show you today is basically a 00:40:45.390 --> 00:40:52.529 align:start position:0% going to show you today is basically a nice<00:40:50.640> basically<00:40:51.640> it's<00:40:51.730> a<00:40:51.789> very<00:40:52.359> nice 00:40:52.529 --> 00:40:52.539 align:start position:0% nice basically it's a very nice 00:40:52.539 --> 00:40:54.900 align:start position:0% nice basically it's a very nice variation<00:40:53.109> and<00:40:53.260> fearless<00:40:53.619> signer<00:40:54.309> which 00:40:54.900 --> 00:40:54.910 align:start position:0% variation and fearless signer which 00:40:54.910 --> 00:40:58.109 align:start position:0% variation and fearless signer which allows<00:40:55.210> us<00:40:55.480> to<00:40:56.460> give<00:40:57.460> the<00:40:57.640> users<00:40:57.940> the<00:40:57.970> ability 00:40:58.109 --> 00:40:58.119 align:start position:0% allows us to give the users the ability 00:40:58.119 --> 00:41:00.979 align:start position:0% allows us to give the users the ability to<00:40:58.480> sign 00:41:00.979 --> 00:41:00.989 align:start position:0% 00:41:00.989 --> 00:41:04.109 align:start position:0% elliptic<00:41:01.989> curve<00:41:02.680> parameters<00:41:03.249> I<00:41:03.459> will<00:41:03.819> give<00:41:03.999> a 00:41:04.109 --> 00:41:04.119 align:start position:0% elliptic curve parameters I will give a 00:41:04.119 --> 00:41:05.400 align:start position:0% elliptic curve parameters I will give a big<00:41:04.569> insert<00:41:04.989> to<00:41:05.109> it 00:41:05.400 --> 00:41:05.410 align:start position:0% big insert to it 00:41:05.410 --> 00:41:10.709 align:start position:0% big insert to it so<00:41:08.609> gentlemen<00:41:09.609> troops<00:41:10.089> in<00:41:10.239> order<00:41:10.329> to<00:41:10.599> have 00:41:10.709 --> 00:41:10.719 align:start position:0% so gentlemen troops in order to have 00:41:10.719 --> 00:41:14.969 align:start position:0% so gentlemen troops in order to have efficient<00:41:12.059> proving<00:41:13.059> you<00:41:13.569> have<00:41:13.749> to<00:41:13.959> tweak<00:41:14.949> a 00:41:14.969 --> 00:41:14.979 align:start position:0% efficient proving you have to tweak a 00:41:14.979 --> 00:41:17.099 align:start position:0% efficient proving you have to tweak a bit<00:41:15.219> the<00:41:15.430> curve<00:41:15.880> parameters<00:41:16.449> of<00:41:16.630> the<00:41:16.809> normal 00:41:17.099 --> 00:41:17.109 align:start position:0% bit the curve parameters of the normal 00:41:17.109 --> 00:41:20.489 align:start position:0% bit the curve parameters of the normal is<00:41:17.469> missing<00:41:17.949> we<00:41:18.369> do<00:41:18.519> sign<00:41:18.729> over<00:41:19.059> the<00:41:19.499> secretary 00:41:20.489 --> 00:41:20.499 align:start position:0% is missing we do sign over the secretary 00:41:20.499 --> 00:41:23.279 align:start position:0% is missing we do sign over the secretary 256<00:41:21.430> which<00:41:21.549> is<00:41:21.729> the<00:41:21.880> normal<00:41:22.390> curve<00:41:22.630> in<00:41:22.869> eternal 00:41:23.279 --> 00:41:23.289 align:start position:0% 256 which is the normal curve in eternal 00:41:23.289 --> 00:41:26.339 align:start position:0% 256 which is the normal curve in eternal v-twin<00:41:24.069> it<00:41:24.190> comes<00:41:24.579> very<00:41:24.910> inefficient<00:41:25.479> so<00:41:26.259> you 00:41:26.339 --> 00:41:26.349 align:start position:0% v-twin it comes very inefficient so you 00:41:26.349 --> 00:41:29.219 align:start position:0% v-twin it comes very inefficient so you have<00:41:26.529> to<00:41:26.739> pick<00:41:27.430> specific<00:41:27.670> parameters<00:41:28.390> in 00:41:29.219 --> 00:41:29.229 align:start position:0% have to pick specific parameters in 00:41:29.229 --> 00:41:31.079 align:start position:0% have to pick specific parameters in order<00:41:29.440> to<00:41:29.529> have<00:41:29.680> an<00:41:29.769> efficient<00:41:30.130> option<00:41:30.579> but 00:41:31.079 --> 00:41:31.089 align:start position:0% order to have an efficient option but 00:41:31.089 --> 00:41:34.739 align:start position:0% order to have an efficient option but then<00:41:31.239> it<00:41:32.049> gets<00:41:32.199> very<00:41:32.440> hard<00:41:32.680> to<00:41:32.920> use<00:41:33.749> mandamus 00:41:34.739 --> 00:41:34.749 align:start position:0% then it gets very hard to use mandamus 00:41:34.749 --> 00:41:38.219 align:start position:0% then it gets very hard to use mandamus for<00:41:34.959> example<00:41:35.349> so<00:41:36.309> what<00:41:36.489> this<00:41:36.609> plug-in<00:41:37.229> system 00:41:38.219 --> 00:41:38.229 align:start position:0% for example so what this plug-in system 00:41:38.229 --> 00:41:40.769 align:start position:0% for example so what this plug-in system or<00:41:38.739> snap<00:41:39.009> system<00:41:39.400> let<00:41:39.849> us<00:41:39.969> do<00:41:40.119> is<00:41:40.269> very<00:41:40.539> easily 00:41:40.769 --> 00:41:40.779 align:start position:0% or snap system let us do is very easily 00:41:40.779 --> 00:41:42.539 align:start position:0% or snap system let us do is very easily create<00:41:41.109> a<00:41:41.319> plugin<00:41:41.739> which<00:41:42.069> I'll<00:41:42.219> show<00:41:42.339> you<00:41:42.369> in<00:41:42.430> a 00:41:42.539 --> 00:41:42.549 align:start position:0% create a plugin which I'll show you in a 00:41:42.549 --> 00:41:46.079 align:start position:0% create a plugin which I'll show you in a second<00:41:42.910> that<00:41:43.229> allows<00:41:44.229> users<00:41:44.680> to<00:41:44.709> use<00:41:45.089> meta 00:41:46.079 --> 00:41:46.089 align:start position:0% second that allows users to use meta 00:41:46.089 --> 00:41:48.779 align:start position:0% second that allows users to use meta musk<00:41:46.359> with<00:41:47.109> a<00:41:47.259> derived<00:41:47.739> pregnant<00:41:48.430> keen<00:41:48.609> to 00:41:48.779 --> 00:41:48.789 align:start position:0% musk with a derived pregnant keen to 00:41:48.789 --> 00:41:52.890 align:start position:0% musk with a derived pregnant keen to sign<00:41:48.969> over<00:41:49.469> artistically<00:41:50.469> to<00:41:50.650> turn<00:41:50.859> right<00:41:51.900> so 00:41:52.890 --> 00:41:52.900 align:start position:0% sign over artistically to turn right so 00:41:52.900 --> 00:41:57.509 align:start position:0% sign over artistically to turn right so I'm<00:41:53.019> trying<00:41:53.319> to<00:41:53.349> show<00:41:56.039> please<00:41:57.039> tell<00:41:57.249> me<00:41:57.400> if<00:41:57.459> you 00:41:57.509 --> 00:41:57.519 align:start position:0% I'm trying to show please tell me if you 00:41:57.519 --> 00:42:01.019 align:start position:0% I'm trying to show please tell me if you don't<00:41:57.670> hear<00:41:57.969> hear<00:41:58.180> or<00:41:58.239> don't<00:41:58.390> see<00:41:58.660> anything<00:42:00.029> so 00:42:01.019 --> 00:42:01.029 align:start position:0% don't hear hear or don't see anything so 00:42:01.029 --> 00:42:04.640 align:start position:0% don't hear hear or don't see anything so I<00:42:01.329> just<00:42:01.979> start<00:42:02.979> first<00:42:03.400> to<00:42:03.579> the<00:42:03.670> black 00:42:04.640 --> 00:42:04.650 align:start position:0% I just start first to the black 00:42:04.650 --> 00:42:07.810 align:start position:0% I just start first to the black then<00:42:05.220> I<00:42:05.250> can<00:42:05.520> go<00:42:05.670> a<00:42:05.700> little<00:42:05.910> bit<00:42:06.120> I'm<00:42:06.240> going<00:42:06.630> to 00:42:07.810 --> 00:42:07.820 align:start position:0% then I can go a little bit I'm going to 00:42:07.820 --> 00:42:13.339 align:start position:0% then I can go a little bit I'm going to sit<00:42:10.610> in<00:42:11.610> the 00:42:13.339 --> 00:42:13.349 align:start position:0% sit in the 00:42:13.349 --> 00:42:28.279 align:start position:0% sit in the -<00:42:13.920> thanks<00:42:14.309> big<00:42:14.459> enough<00:42:16.369> okay<00:42:26.119> so<00:42:27.170> just<00:42:28.170> to 00:42:28.279 --> 00:42:28.289 align:start position:0% - thanks big enough okay so just to 00:42:28.289 --> 00:42:29.599 align:start position:0% - thanks big enough okay so just to remind<00:42:28.559> what<00:42:28.920> we're<00:42:29.069> doing<00:42:29.279> so<00:42:29.309> we're 00:42:29.599 --> 00:42:29.609 align:start position:0% remind what we're doing so we're 00:42:29.609 --> 00:42:35.839 align:start position:0% remind what we're doing so we're building<00:42:31.969> so<00:42:34.130> we<00:42:35.130> are<00:42:35.279> here<00:42:35.549> in<00:42:35.670> the 00:42:35.839 --> 00:42:35.849 align:start position:0% building so we are here in the 00:42:35.849 --> 00:42:39.430 align:start position:0% building so we are here in the department<00:42:36.719> directory<00:42:37.140> everything<00:42:37.920> we<00:42:38.009> just 00:42:39.430 --> 00:42:39.440 align:start position:0% department directory everything we just 00:42:39.440 --> 00:42:43.430 align:start position:0% department directory everything we just filled<00:42:40.440> it<00:42:41.390> and<00:42:42.390> then<00:42:42.539> we<00:42:42.690> can<00:42:42.869> certainly<00:42:43.079> be 00:42:43.430 --> 00:42:43.440 align:start position:0% filled it and then we can certainly be 00:42:43.440 --> 00:42:50.240 align:start position:0% filled it and then we can certainly be pleased 00:42:50.240 --> 00:42:50.250 align:start position:0% 00:42:50.250 --> 00:42:52.259 align:start position:0% [Music] 00:42:52.259 --> 00:42:52.269 align:start position:0% [Music] 00:42:52.269 --> 00:42:57.149 align:start position:0% [Music] okay<00:42:52.899> great<00:42:53.369> now<00:42:54.369> we<00:42:54.429> have<00:42:54.609> it<00:42:54.759> here<00:42:56.039> so<00:42:57.039> this 00:42:57.149 --> 00:42:57.159 align:start position:0% okay great now we have it here so this 00:42:57.159 --> 00:43:01.139 align:start position:0% okay great now we have it here so this is<00:42:57.279> like<00:42:57.479> some<00:42:58.479> kind<00:42:58.809> of<00:42:59.819> nice 00:43:01.139 --> 00:43:01.149 align:start position:0% is like some kind of nice 00:43:01.149 --> 00:43:04.799 align:start position:0% is like some kind of nice you<00:43:01.479> either<00:43:01.659> basically<00:43:03.089> this<00:43:04.089> will<00:43:04.299> be<00:43:04.479> in<00:43:04.599> the 00:43:04.799 --> 00:43:04.809 align:start position:0% you either basically this will be in the 00:43:04.809 --> 00:43:07.679 align:start position:0% you either basically this will be in the client<00:43:05.769> of<00:43:05.919> the<00:43:06.129> exchange<00:43:06.909> right<00:43:07.119> what<00:43:07.599> we 00:43:07.679 --> 00:43:07.689 align:start position:0% client of the exchange right what we 00:43:07.689 --> 00:43:09.149 align:start position:0% client of the exchange right what we want<00:43:07.869> to<00:43:08.019> look<00:43:08.139> like<00:43:08.319> that<00:43:08.499> it<00:43:08.649> would<00:43:08.799> be<00:43:08.949> just 00:43:09.149 --> 00:43:09.159 align:start position:0% want to look like that it would be just 00:43:09.159 --> 00:43:11.039 align:start position:0% want to look like that it would be just a<00:43:09.399> simple<00:43:09.879> client<00:43:10.299> of<00:43:10.389> the<00:43:10.449> exchange<00:43:10.749> will 00:43:11.039 --> 00:43:11.049 align:start position:0% a simple client of the exchange will 00:43:11.049 --> 00:43:14.489 align:start position:0% a simple client of the exchange will enable<00:43:11.289> us<00:43:11.529> to<00:43:11.969> connect<00:43:12.969> mathematical<00:43:13.689> Simon 00:43:14.489 --> 00:43:14.499 align:start position:0% enable us to connect mathematical Simon 00:43:14.499 --> 00:43:16.699 align:start position:0% enable us to connect mathematical Simon orders<00:43:15.309> which<00:43:15.549> you<00:43:15.639> want<00:43:15.849> to<00:43:15.909> submit<00:43:16.179> to<00:43:16.449> the 00:43:16.699 --> 00:43:16.709 align:start position:0% orders which you want to submit to the 00:43:16.709 --> 00:43:22.699 align:start position:0% orders which you want to submit to the exchange<00:43:18.269> so<00:43:20.759> same<00:43:21.759> way<00:43:21.939> that<00:43:22.089> we<00:43:22.329> did<00:43:22.449> the 00:43:22.699 --> 00:43:22.709 align:start position:0% exchange so same way that we did the 00:43:22.709 --> 00:43:25.859 align:start position:0% exchange so same way that we did the portal<00:43:23.709> connecting<00:43:23.919> to<00:43:24.279> the<00:43:24.689> installing<00:43:25.689> the 00:43:25.859 --> 00:43:25.869 align:start position:0% portal connecting to the installing the 00:43:25.869 --> 00:43:28.429 align:start position:0% portal connecting to the installing the plugin<00:43:26.079> and<00:43:26.319> then<00:43:26.409> allowing<00:43:26.949> it<00:43:27.189> to 00:43:28.429 --> 00:43:28.439 align:start position:0% plugin and then allowing it to 00:43:28.439 --> 00:43:31.609 align:start position:0% plugin and then allowing it to conditions<00:43:29.439> with<00:43:29.589> where<00:43:29.739> as<00:43:29.859> head<00:43:30.069> for<00:43:30.279> I 00:43:31.609 --> 00:43:31.619 align:start position:0% conditions with where as head for I 00:43:31.619 --> 00:43:38.549 align:start position:0% conditions with where as head for I don't<00:43:32.619> know<00:43:32.859> like<00:43:33.339> it<00:43:34.949> is<00:43:36.479> and<00:43:37.479> once<00:43:37.719> we<00:43:37.929> have 00:43:38.549 --> 00:43:38.559 align:start position:0% don't know like it is and once we have 00:43:38.559 --> 00:43:42.980 align:start position:0% don't know like it is and once we have it<00:43:38.709> we<00:43:38.859> can<00:43:39.039> just<00:43:39.069> get<00:43:39.759> the<00:43:39.969> public<00:43:40.299> team<00:43:41.819> just 00:43:42.980 --> 00:43:42.990 align:start position:0% it we can just get the public team just 00:43:42.990 --> 00:43:44.749 align:start position:0% it we can just get the public team just [Music] 00:43:44.749 --> 00:43:44.759 align:start position:0% [Music] 00:43:44.759 --> 00:43:47.519 align:start position:0% [Music] make<00:43:45.759> sure<00:43:45.909> you<00:43:46.029> understand<00:43:46.449> this<00:43:46.569> is<00:43:46.689> the 00:43:47.519 --> 00:43:47.529 align:start position:0% make sure you understand this is the 00:43:47.529 --> 00:43:50.849 align:start position:0% make sure you understand this is the hockey<00:43:48.339> key<00:43:48.759> based<00:43:49.719> on<00:43:49.899> our<00:43:50.079> ellipse<00:43:50.469> here 00:43:50.849 --> 00:43:50.859 align:start position:0% hockey key based on our ellipse here 00:43:50.859 --> 00:43:54.240 align:start position:0% hockey key based on our ellipse here which<00:43:51.399> was<00:43:51.669> derived<00:43:51.969> from<00:43:52.209> the<00:43:52.359> same<00:43:52.689> metal 00:43:54.240 --> 00:43:54.250 align:start position:0% which was derived from the same metal 00:43:54.250 --> 00:43:59.430 align:start position:0% which was derived from the same metal we're<00:43:54.640> not<00:43:54.910> saying<00:43:55.210> that<00:43:55.390> if<00:43:55.690> they<00:43:55.930> get<00:43:58.440> their 00:43:59.430 --> 00:43:59.440 align:start position:0% we're not saying that if they get their 00:43:59.440 --> 00:44:02.160 align:start position:0% we're not saying that if they get their public<00:43:59.800> you<00:43:59.980> can<00:44:00.190> sign<00:44:00.460> any<00:44:01.420> message<00:44:01.780> we<00:44:01.900> want 00:44:02.160 --> 00:44:02.170 align:start position:0% public you can sign any message we want 00:44:02.170 --> 00:44:04.560 align:start position:0% public you can sign any message we want specifically<00:44:03.130> in<00:44:03.220> order<00:44:03.520> innocently<00:44:03.970> says<00:44:04.300> I 00:44:04.560 --> 00:44:04.570 align:start position:0% specifically in order innocently says I 00:44:04.570 --> 00:44:10.530 align:start position:0% specifically in order innocently says I want<00:44:05.440> to<00:44:05.530> buy<00:44:07.740> maybe<00:44:08.740> we<00:44:08.980> don't<00:44:09.400> sell<00:44:09.820> eat<00:44:10.090> to 00:44:10.530 --> 00:44:10.540 align:start position:0% want to buy maybe we don't sell eat to 00:44:10.540 --> 00:44:18.000 align:start position:0% want to buy maybe we don't sell eat to be<00:44:10.690> indifferent<00:44:11.080> right<00:44:15.810> so<00:44:16.810> I<00:44:17.230> want<00:44:17.650> to<00:44:17.710> still 00:44:18.000 --> 00:44:18.010 align:start position:0% be indifferent right so I want to still 00:44:18.010 --> 00:44:20.550 align:start position:0% be indifferent right so I want to still die<00:44:18.280> in<00:44:18.550> the<00:44:19.060> recipients<00:44:20.050> and<00:44:20.200> this<00:44:20.290> is<00:44:20.410> the 00:44:20.550 --> 00:44:20.560 align:start position:0% die in the recipients and this is the 00:44:20.560 --> 00:44:22.290 align:start position:0% die in the recipients and this is the accounts<00:44:21.220> that<00:44:21.250> they<00:44:21.430> have<00:44:21.580> often<00:44:21.760> I<00:44:22.000> won't 00:44:22.290 --> 00:44:22.300 align:start position:0% accounts that they have often I won't 00:44:22.300 --> 00:44:24.960 align:start position:0% accounts that they have often I won't get<00:44:22.480> into<00:44:22.660> it<00:44:22.810> this<00:44:23.770> is<00:44:23.830> like<00:44:24.130> Dorian<00:44:24.730> deeds 00:44:24.960 --> 00:44:24.970 align:start position:0% get into it this is like Dorian deeds 00:44:24.970 --> 00:44:27.000 align:start position:0% get into it this is like Dorian deeds and<00:44:25.300> then<00:44:25.480> we'll<00:44:25.599> get<00:44:25.690> a<00:44:25.750> problem<00:44:26.140> you<00:44:26.619> can<00:44:26.770> see 00:44:27.000 --> 00:44:27.010 align:start position:0% and then we'll get a problem you can see 00:44:27.010 --> 00:44:28.260 align:start position:0% and then we'll get a problem you can see it<00:44:27.099> but<00:44:27.220> it<00:44:27.369> says<00:44:27.550> do<00:44:27.700> you<00:44:27.790> really<00:44:28.000> want<00:44:28.180> to 00:44:28.260 --> 00:44:28.270 align:start position:0% it but it says do you really want to 00:44:28.270 --> 00:44:30.540 align:start position:0% it but it says do you really want to sign<00:44:28.450> this<00:44:28.660> message<00:44:29.080> and<00:44:29.260> parameters<00:44:30.070> K<00:44:30.400> we 00:44:30.540 --> 00:44:30.550 align:start position:0% sign this message and parameters K we 00:44:30.550 --> 00:44:35.150 align:start position:0% sign this message and parameters K we have<00:44:31.080> wants<00:44:32.080> us<00:44:32.970> basically<00:44:33.970> receive<00:44:34.540> this 00:44:35.150 --> 00:44:35.160 align:start position:0% have wants us basically receive this 00:44:35.160 --> 00:44:46.240 align:start position:0% have wants us basically receive this okay<00:44:40.650> yeah<00:44:42.060> yeah<00:44:43.060> where's<00:44:43.750> this<00:44:44.050> pls<00:44:44.560> key<00:44:44.770> back 00:44:46.240 --> 00:44:46.250 align:start position:0% okay yeah yeah where's this pls key back 00:44:46.250 --> 00:44:48.490 align:start position:0% okay yeah yeah where's this pls key back does<00:44:46.880> not<00:44:47.030> realize<00:44:47.359> it's<00:44:47.510> a<00:44:47.599> simple<00:44:48.050> ECDSA 00:44:48.490 --> 00:44:48.500 align:start position:0% does not realize it's a simple ECDSA 00:44:48.500 --> 00:44:49.270 align:start position:0% does not realize it's a simple ECDSA sorry 00:44:49.270 --> 00:44:49.280 align:start position:0% sorry 00:44:49.280 --> 00:44:51.160 align:start position:0% sorry where<00:44:49.520> are<00:44:49.640> where's<00:44:49.820> the<00:44:50.000> key<00:44:50.180> backed<00:44:50.390> up<00:44:50.540> as<00:44:51.109> a 00:44:51.160 --> 00:44:51.170 align:start position:0% where are where's the key backed up as a 00:44:51.170 --> 00:44:53.250 align:start position:0% where are where's the key backed up as a plugin<00:44:51.680> developer<00:44:52.160> are<00:44:52.280> you<00:44:52.460> responsible<00:44:52.849> for 00:44:53.250 --> 00:44:53.260 align:start position:0% plugin developer are you responsible for 00:44:53.260 --> 00:44:55.630 align:start position:0% plugin developer are you responsible for you<00:44:54.260> know<00:44:54.380> the<00:44:54.530> keys<00:44:54.770> inside<00:44:55.130> the<00:44:55.190> minimize 00:44:55.630 --> 00:44:55.640 align:start position:0% you know the keys inside the minimize 00:44:55.640 --> 00:45:02.440 align:start position:0% you know the keys inside the minimize and<00:44:55.970> they<00:44:56.030> also<00:44:56.210> quote<00:44:56.540> but<00:44:57.410> yes<00:45:01.270> okay<00:45:02.270> great 00:45:02.440 --> 00:45:02.450 align:start position:0% and they also quote but yes okay great 00:45:02.450 --> 00:45:05.680 align:start position:0% and they also quote but yes okay great so<00:45:03.490> first<00:45:04.490> of<00:45:04.640> all<00:45:04.760> we<00:45:04.880> can<00:45:05.000> look<00:45:05.030> at<00:45:05.270> the 00:45:05.680 --> 00:45:05.690 align:start position:0% so first of all we can look at the 00:45:05.690 --> 00:45:08.490 align:start position:0% so first of all we can look at the [Music] 00:45:08.490 --> 00:45:08.500 align:start position:0% [Music] 00:45:08.500 --> 00:45:11.410 align:start position:0% [Music] justin<00:45:09.500> what<00:45:09.650> we<00:45:09.770> have<00:45:09.890> here<00:45:10.070> so<00:45:10.280> again<00:45:11.060> we've 00:45:11.410 --> 00:45:11.420 align:start position:0% justin what we have here so again we've 00:45:11.420 --> 00:45:14.140 align:start position:0% justin what we have here so again we've ever<00:45:11.570> only<00:45:11.930> two<00:45:12.170> to<00:45:12.980> close<00:45:13.250> why<00:45:13.849> don't<00:45:14.000> you<00:45:14.060> get 00:45:14.140 --> 00:45:14.150 align:start position:0% ever only two to close why don't you get 00:45:14.150 --> 00:45:16.660 align:start position:0% ever only two to close why don't you get a<00:45:14.180> comment<00:45:14.660> just<00:45:15.050> even<00:45:15.410> the<00:45:15.500> public<00:45:15.770> key<00:45:15.920> one 00:45:16.660 --> 00:45:16.670 align:start position:0% a comment just even the public key one 00:45:16.670 --> 00:45:18.400 align:start position:0% a comment just even the public key one at<00:45:16.790> the<00:45:16.910> same<00:45:17.060> message<00:45:17.270> in<00:45:17.599> the<00:45:18.020> nice<00:45:18.170> thing 00:45:18.400 --> 00:45:18.410 align:start position:0% at the same message in the nice thing 00:45:18.410 --> 00:45:21.070 align:start position:0% at the same message in the nice thing about<00:45:18.500> the<00:45:19.400> way<00:45:19.609> meta<00:45:19.849> must<00:45:20.030> did<00:45:20.330> it<00:45:20.450> and<00:45:20.930> they 00:45:21.070 --> 00:45:21.080 align:start position:0% about the way meta must did it and they 00:45:21.080 --> 00:45:28.089 align:start position:0% about the way meta must did it and they don't<00:45:21.260> be<00:45:23.950> I<00:45:24.950> can<00:45:25.790> show<00:45:25.970> you<00:45:26.030> India<00:45:26.450> so<00:45:27.170> we 00:45:28.089 --> 00:45:28.099 align:start position:0% don't be I can show you India so we 00:45:28.099 --> 00:45:31.930 align:start position:0% don't be I can show you India so we previously<00:45:28.880> had<00:45:29.950> our<00:45:30.950> own<00:45:31.190> module<00:45:31.609> for 00:45:31.930 --> 00:45:31.940 align:start position:0% previously had our own module for 00:45:31.940 --> 00:45:34.349 align:start position:0% previously had our own module for signing<00:45:32.330> over<00:45:32.510> a<00:45:32.690> literature<00:45:33.109> using<00:45:33.619> only<00:45:33.830> the 00:45:34.349 --> 00:45:34.359 align:start position:0% signing over a literature using only the 00:45:34.359 --> 00:45:37.810 align:start position:0% signing over a literature using only the Olympic<00:45:35.359> module<00:45:35.750> meta<00:45:36.680> must've<00:45:37.010> music<00:45:37.340> and 00:45:37.810 --> 00:45:37.820 align:start position:0% Olympic module meta must've music and 00:45:37.820 --> 00:45:40.750 align:start position:0% Olympic module meta must've music and once<00:45:38.060> we<00:45:38.210> had<00:45:38.390> it<00:45:38.570> you<00:45:38.780> only<00:45:39.470> needed<00:45:39.710> to<00:45:40.010> import 00:45:40.750 --> 00:45:40.760 align:start position:0% once we had it you only needed to import 00:45:40.760 --> 00:45:43.720 align:start position:0% once we had it you only needed to import it<00:45:40.940> here<00:45:41.180> and<00:45:41.480> it<00:45:42.200> all<00:45:43.040> gets<00:45:43.250> bundled<00:45:43.490> together 00:45:43.720 --> 00:45:43.730 align:start position:0% it here and it all gets bundled together 00:45:43.730 --> 00:45:45.660 align:start position:0% it here and it all gets bundled together in<00:45:44.000> the<00:45:44.210> bundle<00:45:44.540> JavaScript<00:45:45.230> and<00:45:45.349> then 00:45:45.660 --> 00:45:45.670 align:start position:0% in the bundle JavaScript and then 00:45:45.670 --> 00:45:49.470 align:start position:0% in the bundle JavaScript and then whatever<00:45:46.670> you<00:45:46.940> have<00:45:47.800> already<00:45:48.800> you<00:45:48.980> can<00:45:49.160> just 00:45:49.470 --> 00:45:49.480 align:start position:0% whatever you have already you can just 00:45:49.480 --> 00:45:51.579 align:start position:0% whatever you have already you can just incorporated<00:45:50.480> into<00:45:50.720> the<00:45:50.900> plug-in<00:45:51.109> you<00:45:51.320> don't 00:45:51.579 --> 00:45:51.589 align:start position:0% incorporated into the plug-in you don't 00:45:51.589 --> 00:45:53.560 align:start position:0% incorporated into the plug-in you don't need<00:45:51.710> to<00:45:51.830> do<00:45:51.920> anything<00:45:52.190> you<00:45:52.460> and<00:45:53.060> so<00:45:53.210> once<00:45:53.420> we 00:45:53.560 --> 00:45:53.570 align:start position:0% need to do anything you and so once we 00:45:53.570 --> 00:45:54.880 align:start position:0% need to do anything you and so once we have<00:45:53.690> our<00:45:53.930> signatures 00:45:54.880 --> 00:45:54.890 align:start position:0% have our signatures 00:45:54.890 --> 00:45:56.710 align:start position:0% have our signatures what<00:45:55.550> we<00:45:55.670> need<00:45:55.820> to<00:45:55.849> do<00:45:56.030> is<00:45:56.119> get<00:45:56.300> the<00:45:56.420> public 00:45:56.710 --> 00:45:56.720 align:start position:0% what we need to do is get the public 00:45:56.720 --> 00:46:01.030 align:start position:0% what we need to do is get the public email<00:45:56.869> to<00:45:57.109> it<00:45:57.320> in<00:45:57.440> a<00:45:57.500> second<00:45:59.470> and<00:46:00.470> you<00:46:00.589> just<00:46:00.830> get 00:46:01.030 --> 00:46:01.040 align:start position:0% email to it in a second and you just get 00:46:01.040 --> 00:46:06.730 align:start position:0% email to it in a second and you just get it<00:46:01.570> from<00:46:02.570> our<00:46:03.640> crypto<00:46:04.640> library<00:46:05.290> and<00:46:06.290> same<00:46:06.560> with 00:46:06.730 --> 00:46:06.740 align:start position:0% it from our crypto library and same with 00:46:06.740 --> 00:46:09.480 align:start position:0% it from our crypto library and same with the<00:46:06.830> same<00:46:07.040> mice<00:46:07.970> you<00:46:08.150> want<00:46:08.630> to<00:46:08.720> send<00:46:08.960> a<00:46:09.050> message 00:46:09.480 --> 00:46:09.490 align:start position:0% the same mice you want to send a message 00:46:09.490 --> 00:46:15.880 align:start position:0% the same mice you want to send a message you<00:46:10.490> just<00:46:12.070> mind<00:46:13.070> that<00:46:13.990> you<00:46:14.990> just<00:46:15.230> get<00:46:15.470> the<00:46:15.740> or 00:46:15.880 --> 00:46:15.890 align:start position:0% you just mind that you just get the or 00:46:15.890 --> 00:46:17.950 align:start position:0% you just mind that you just get the or the<00:46:16.339> message<00:46:16.670> you<00:46:16.760> want<00:46:16.790> to<00:46:17.030> sign<00:46:17.270> and<00:46:17.810> you 00:46:17.950 --> 00:46:17.960 align:start position:0% the message you want to sign and you 00:46:17.960 --> 00:46:22.000 align:start position:0% the message you want to sign and you pull<00:46:18.170> it<00:46:18.200> out<00:46:18.349> of<00:46:18.500> one<00:46:18.820> module<00:46:20.560> okay<00:46:21.560> great 00:46:22.000 --> 00:46:22.010 align:start position:0% pull it out of one module okay great 00:46:22.010 --> 00:46:29.790 align:start position:0% pull it out of one module okay great anything<00:46:22.940> else<00:46:23.089> do<00:46:23.210> you<00:46:23.359> see<00:46:26.020> okay<00:46:27.020> maybe<00:46:27.380> just 00:46:29.790 --> 00:46:29.800 align:start position:0% 00:46:29.800 --> 00:46:34.240 align:start position:0% he's<00:46:30.800> n<00:46:30.890> equip<00:46:31.130> is<00:46:31.280> there<00:46:31.430> any<00:46:31.520> questions<00:46:33.250> yeah 00:46:34.240 --> 00:46:34.250 align:start position:0% he's n equip is there any questions yeah 00:46:34.250 --> 00:46:40.240 align:start position:0% he's n equip is there any questions yeah you're<00:46:35.089> like<00:46:35.950> like<00:46:36.950> start 00:46:40.240 --> 00:46:40.250 align:start position:0% 00:46:40.250 --> 00:46:44.540 align:start position:0% so<00:46:41.090> that<00:46:41.270> like<00:46:41.390> adapt<00:46:41.690> those 00:46:44.540 --> 00:46:44.550 align:start position:0% 00:46:44.550 --> 00:46:46.680 align:start position:0% so<00:46:45.550> this<00:46:45.700> has<00:46:45.880> nothing<00:46:46.210> to<00:46:46.240> do<00:46:46.480> with<00:46:46.510> the 00:46:46.680 --> 00:46:46.690 align:start position:0% so this has nothing to do with the 00:46:46.690 --> 00:46:49.770 align:start position:0% so this has nothing to do with the proofs<00:46:46.960> just<00:46:47.760> we<00:46:48.760> want<00:46:48.970> to<00:46:49.030> allow<00:46:49.300> the<00:46:49.360> user<00:46:49.480> to 00:46:49.770 --> 00:46:49.780 align:start position:0% proofs just we want to allow the user to 00:46:49.780 --> 00:46:53.640 align:start position:0% proofs just we want to allow the user to sign<00:46:50.230> with<00:46:50.980> a<00:46:51.010> slightly<00:46:51.610> different<00:46:52.650> signature 00:46:53.640 --> 00:46:53.650 align:start position:0% sign with a slightly different signature 00:46:53.650 --> 00:46:56.720 align:start position:0% sign with a slightly different signature scheme<00:46:53.920> right<00:46:54.790> so<00:46:55.030> this<00:46:55.570> is<00:46:55.630> our<00:46:55.900> way<00:46:56.170> to 00:46:56.720 --> 00:46:56.730 align:start position:0% scheme right so this is our way to 00:46:56.730 --> 00:47:01.500 align:start position:0% scheme right so this is our way to whatever<00:46:59.100> like<00:47:00.100> changing<00:47:00.760> the<00:47:00.910> character<00:47:01.390> to 00:47:01.500 --> 00:47:01.510 align:start position:0% whatever like changing the character to 00:47:01.510 --> 00:47:04.440 align:start position:0% whatever like changing the character to these<00:47:01.660> sign<00:47:01.930> over<00:47:02.230> yeah<00:47:02.650> but<00:47:03.550> in<00:47:04.210> a<00:47:04.300> very 00:47:04.440 --> 00:47:04.450 align:start position:0% these sign over yeah but in a very 00:47:04.450 --> 00:47:06.360 align:start position:0% these sign over yeah but in a very simple<00:47:04.840> way<00:47:04.900> so<00:47:05.290> he<00:47:05.710> took<00:47:05.860> us<00:47:06.010> to<00:47:06.130> the<00:47:06.220> other 00:47:06.360 --> 00:47:06.370 align:start position:0% simple way so he took us to the other 00:47:06.370 --> 00:47:09.510 align:start position:0% simple way so he took us to the other only<00:47:06.490> a<00:47:06.580> couple<00:47:06.760> of<00:47:06.910> hours<00:47:07.060> to<00:47:07.360> do<00:47:07.480> is<00:47:08.520> maybe 00:47:09.510 --> 00:47:09.520 align:start position:0% only a couple of hours to do is maybe 00:47:09.520 --> 00:47:38.040 align:start position:0% only a couple of hours to do is maybe just<00:47:10.050> the<00:47:11.050> design<00:47:11.410> of<00:47:11.590> the<00:47:12.060> Heartland<00:47:37.050> like 00:47:38.040 --> 00:47:38.050 align:start position:0% just the design of the Heartland like 00:47:38.050 --> 00:47:42.320 align:start position:0% just the design of the Heartland like the<00:47:38.230> library<00:47:39.720> again<00:47:40.720> turning 00:47:42.320 --> 00:47:42.330 align:start position:0% the library again turning 00:47:42.330 --> 00:47:45.090 align:start position:0% the library again turning so<00:47:43.330> you're<00:47:43.540> asking<00:47:43.600> about<00:47:44.020> whether<00:47:44.380> we<00:47:44.590> expose 00:47:45.090 --> 00:47:45.100 align:start position:0% so you're asking about whether we expose 00:47:45.100 --> 00:47:47.310 align:start position:0% so you're asking about whether we expose any<00:47:45.280> native<00:47:45.610> noted<00:47:45.970> modules<00:47:46.420> right<00:47:46.840> under 00:47:47.310 --> 00:47:47.320 align:start position:0% any native noted modules right under 00:47:47.320 --> 00:47:50.910 align:start position:0% any native noted modules right under there<00:47:47.590> no<00:47:47.800> he's<00:47:49.050> only<00:47:50.050> giving<00:47:50.470> any<00:47:50.620> know<00:47:50.890> the 00:47:50.910 --> 00:47:50.920 align:start position:0% there no he's only giving any know the 00:47:50.920 --> 00:47:54.120 align:start position:0% there no he's only giving any know the native<00:47:51.430> modules<00:47:51.910> right<00:47:52.950> because<00:47:53.950> we<00:47:54.100> don't 00:47:54.120 --> 00:47:54.130 align:start position:0% native modules right because we don't 00:47:54.130 --> 00:47:57.540 align:start position:0% native modules right because we don't inject<00:47:54.550> any<00:47:54.730> authority<00:47:55.660> from<00:47:56.400> environment<00:47:57.400> at 00:47:57.540 --> 00:47:57.550 align:start position:0% inject any authority from environment at 00:47:57.550 --> 00:47:59.790 align:start position:0% inject any authority from environment at browserify<00:47:57.940> I<00:47:58.060> guess<00:47:58.270> does<00:47:58.480> provide<00:47:58.900> some<00:47:58.960> but 00:47:59.790 --> 00:47:59.800 align:start position:0% browserify I guess does provide some but 00:47:59.800 --> 00:48:01.800 align:start position:0% browserify I guess does provide some but children<00:48:00.130> I<00:48:00.610> work<00:48:00.760> here<00:48:01.000> because<00:48:01.480> they're 00:48:01.800 --> 00:48:01.810 align:start position:0% children I work here because they're 00:48:01.810 --> 00:48:04.830 align:start position:0% children I work here because they're only<00:48:01.960> getting<00:48:02.200> booked<00:48:02.530> run<00:48:02.860> and<00:48:03.600> they're<00:48:04.600> only 00:48:04.830 --> 00:48:04.840 align:start position:0% only getting booked run and they're only 00:48:04.840 --> 00:48:06.300 align:start position:0% only getting booked run and they're only getting<00:48:05.020> bloated<00:48:05.230> at<00:48:05.470> runtime<00:48:05.650> so<00:48:06.010> there's<00:48:06.160> no 00:48:06.300 --> 00:48:06.310 align:start position:0% getting bloated at runtime so there's no 00:48:06.310 --> 00:48:09.000 align:start position:0% getting bloated at runtime so there's no there's<00:48:06.340> no<00:48:06.730> address<00:48:07.090> today<00:48:07.780> even<00:48:08.050> access<00:48:08.380> at 00:48:09.000 --> 00:48:09.010 align:start position:0% there's no address today even access at 00:48:09.010 --> 00:48:11.780 align:start position:0% there's no address today even access at okay<00:48:09.310> time<00:48:09.580> for<00:48:09.790> my<00:48:10.000> Creek<00:48:10.420> goes<00:48:10.630> exactly 00:48:11.780 --> 00:48:11.790 align:start position:0% okay time for my Creek goes exactly 00:48:11.790 --> 00:48:14.190 align:start position:0% okay time for my Creek goes exactly right<00:48:12.790> so<00:48:13.030> some<00:48:13.270> reservoir<00:48:13.690> in<00:48:13.780> certs<00:48:14.050> a 00:48:14.190 --> 00:48:14.200 align:start position:0% right so some reservoir in certs a 00:48:14.200 --> 00:48:16.740 align:start position:0% right so some reservoir in certs a crypto<00:48:14.620> library<00:48:15.190> and<00:48:15.520> so<00:48:15.700> it<00:48:15.970> would<00:48:16.210> I<00:48:16.480> guess 00:48:16.740 --> 00:48:16.750 align:start position:0% crypto library and so it would I guess 00:48:16.750 --> 00:48:23.280 align:start position:0% crypto library and so it would I guess get<00:48:17.110> a<00:48:17.140> year<00:48:21.630> right<00:48:22.630> great<00:48:22.840> so<00:48:23.050> the<00:48:23.200> way 00:48:23.280 --> 00:48:23.290 align:start position:0% get a year right great so the way 00:48:23.290 --> 00:48:24.990 align:start position:0% get a year right great so the way browserify<00:48:23.620> works<00:48:23.920> if<00:48:24.040> you<00:48:24.190> require<00:48:24.640> crypto 00:48:24.990 --> 00:48:25.000 align:start position:0% browserify works if you require crypto 00:48:25.000 --> 00:48:27.510 align:start position:0% browserify works if you require crypto it's<00:48:25.150> going<00:48:25.330> to<00:48:25.390> provided<00:48:26.320> and<00:48:26.680> and<00:48:27.040> yeah<00:48:27.190> at 00:48:27.510 --> 00:48:27.520 align:start position:0% it's going to provided and and yeah at 00:48:27.520 --> 00:48:29.070 align:start position:0% it's going to provided and and yeah at the<00:48:27.610> moment<00:48:27.760> I<00:48:28.060> don't<00:48:28.120> know<00:48:28.240> Eric<00:48:28.840> native 00:48:29.070 --> 00:48:29.080 align:start position:0% the moment I don't know Eric native 00:48:29.080 --> 00:48:31.710 align:start position:0% the moment I don't know Eric native purposes<00:48:29.500> there<00:48:29.680> our<00:48:30.430> goal<00:48:30.940> is<00:48:31.210> to<00:48:31.450> provide 00:48:31.710 --> 00:48:31.720 align:start position:0% purposes there our goal is to provide 00:48:31.720 --> 00:48:34.020 align:start position:0% purposes there our goal is to provide zero<00:48:32.110> and<00:48:32.350> the<00:48:32.440> authority<00:48:32.920> or<00:48:33.400> right<00:48:33.640> now<00:48:33.790> for 00:48:34.020 --> 00:48:34.030 align:start position:0% zero and the authority or right now for 00:48:34.030 --> 00:48:35.670 align:start position:0% zero and the authority or right now for convenience<00:48:34.180> we<00:48:34.540> do<00:48:34.780> have<00:48:34.930> some<00:48:35.170> API<00:48:35.500> is<00:48:35.560> that 00:48:35.670 --> 00:48:35.680 align:start position:0% convenience we do have some API is that 00:48:35.680 --> 00:48:37.500 align:start position:0% convenience we do have some API is that we're<00:48:35.980> just<00:48:36.010> kind<00:48:36.370> of<00:48:36.400> leaving<00:48:36.610> in<00:48:36.910> for<00:48:37.450> the 00:48:37.500 --> 00:48:37.510 align:start position:0% we're just kind of leaving in for the 00:48:37.510 --> 00:48:40.140 align:start position:0% we're just kind of leaving in for the sake<00:48:37.690> of<00:48:37.720> convenience<00:48:37.960> because<00:48:39.030> mocking<00:48:40.030> the 00:48:40.140 --> 00:48:40.150 align:start position:0% sake of convenience because mocking the 00:48:40.150 --> 00:48:41.940 align:start position:0% sake of convenience because mocking the entire<00:48:40.390> fetch<00:48:40.750> library<00:48:41.230> behind<00:48:41.410> a<00:48:41.680> permission 00:48:41.940 --> 00:48:41.950 align:start position:0% entire fetch library behind a permission 00:48:41.950 --> 00:48:43.770 align:start position:0% entire fetch library behind a permission system<00:48:42.250> is<00:48:42.700> a<00:48:42.760> little<00:48:42.940> bit<00:48:43.150> tedious<00:48:43.330> but<00:48:43.510> it's 00:48:43.770 --> 00:48:43.780 align:start position:0% system is a little bit tedious but it's 00:48:43.780 --> 00:48:46.740 align:start position:0% system is a little bit tedious but it's very<00:48:43.900> complicated<00:48:44.320> API<00:48:44.860> but<00:48:45.490> but<00:48:46.390> yeah<00:48:46.540> that's 00:48:46.740 --> 00:48:46.750 align:start position:0% very complicated API but but yeah that's 00:48:46.750 --> 00:48:49.070 align:start position:0% very complicated API but but yeah that's that's<00:48:47.080> where<00:48:47.470> we're<00:48:47.620> headed<00:48:47.830> towards<00:48:48.070> bear 00:48:49.070 --> 00:48:49.080 align:start position:0% that's where we're headed towards bear 00:48:49.080 --> 00:48:52.300 align:start position:0% that's where we're headed towards bear anything<00:48:50.080> Gillis 00:48:52.300 --> 00:48:52.310 align:start position:0% anything Gillis 00:48:52.310 --> 00:49:07.720 align:start position:0% anything Gillis okay<00:48:52.880> thank<00:48:53.090> you<00:49:05.230> yes<00:49:06.230> this<00:49:06.830> is<00:49:07.010> awesome<00:49:07.220> I 00:49:07.720 --> 00:49:07.730 align:start position:0% okay thank you yes this is awesome I 00:49:07.730 --> 00:49:10.090 align:start position:0% okay thank you yes this is awesome I have<00:49:08.000> a<00:49:08.030> lot<00:49:08.300> of<00:49:08.330> plugin<00:49:08.750> ideas<00:49:09.260> that<00:49:09.650> I<00:49:09.830> would 00:49:10.090 --> 00:49:10.100 align:start position:0% have a lot of plugin ideas that I would 00:49:10.100 --> 00:49:15.490 align:start position:0% have a lot of plugin ideas that I would want<00:49:10.310> to<00:49:10.370> build<00:49:10.580> like<00:49:10.820> today<00:49:14.290> today<00:49:15.290> with 00:49:15.490 --> 00:49:15.500 align:start position:0% want to build like today today with 00:49:15.500 --> 00:49:19.450 align:start position:0% want to build like today today with County<00:49:16.490> Schools<00:49:16.760> yeah<00:49:17.470> so<00:49:18.470> you<00:49:19.100> know<00:49:19.160> right 00:49:19.450 --> 00:49:19.460 align:start position:0% County Schools yeah so you know right 00:49:19.460 --> 00:49:21.010 align:start position:0% County Schools yeah so you know right now<00:49:19.640> with<00:49:19.850> the<00:49:20.030> remix<00:49:20.420> plug-in<00:49:20.810> system 00:49:21.010 --> 00:49:21.020 align:start position:0% now with the remix plug-in system 00:49:21.020 --> 00:49:23.920 align:start position:0% now with the remix plug-in system there's<00:49:21.530> no<00:49:21.590> forum<00:49:22.280> or<00:49:22.460> community<00:49:22.940> to<00:49:23.210> to 00:49:23.920 --> 00:49:23.930 align:start position:0% there's no forum or community to to 00:49:23.930 --> 00:49:26.910 align:start position:0% there's no forum or community to to coordinate<00:49:24.470> the<00:49:24.590> creation<00:49:25.040> of<00:49:25.100> the<00:49:25.220> plug-in 00:49:26.910 --> 00:49:26.920 align:start position:0% coordinate the creation of the plug-in 00:49:26.920 --> 00:49:30.280 align:start position:0% coordinate the creation of the plug-in that's<00:49:27.920> that's<00:49:28.370> fine<00:49:28.670> but<00:49:28.970> I<00:49:29.480> would<00:49:29.960> like<00:49:30.110> to 00:49:30.280 --> 00:49:30.290 align:start position:0% that's that's fine but I would like to 00:49:30.290 --> 00:49:32.620 align:start position:0% that's that's fine but I would like to see<00:49:30.500> the<00:49:30.710> best<00:49:31.040> and<00:49:31.430> the<00:49:31.520> most<00:49:31.550> needed<00:49:32.090> plugins 00:49:32.620 --> 00:49:32.630 align:start position:0% see the best and the most needed plugins 00:49:32.630 --> 00:49:37.710 align:start position:0% see the best and the most needed plugins put<00:49:33.020> forward<00:49:35.140> and<00:49:36.140> so<00:49:36.410> if<00:49:36.800> the<00:49:36.980> answer<00:49:37.100> is 00:49:37.710 --> 00:49:37.720 align:start position:0% put forward and so if the answer is 00:49:37.720 --> 00:49:42.910 align:start position:0% put forward and so if the answer is community<00:49:40.300> to<00:49:41.300> create<00:49:41.480> this<00:49:41.780> with<00:49:42.590> your<00:49:42.770> input 00:49:42.910 --> 00:49:42.920 align:start position:0% community to create this with your input 00:49:42.920 --> 00:49:45.220 align:start position:0% community to create this with your input because<00:49:43.550> I<00:49:43.760> want<00:49:44.150> to<00:49:44.180> see<00:49:44.360> it's<00:49:44.690> like<00:49:44.840> several 00:49:45.220 --> 00:49:45.230 align:start position:0% because I want to see it's like several 00:49:45.230 --> 00:49:48.340 align:start position:0% because I want to see it's like several plugins<00:49:46.180> absolutely<00:49:47.180> awesome<00:49:47.630> just<00:49:48.260> to 00:49:48.340 --> 00:49:48.350 align:start position:0% plugins absolutely awesome just to 00:49:48.350 --> 00:49:50.110 align:start position:0% plugins absolutely awesome just to recant<00:49:49.070> that<00:49:49.160> for<00:49:49.430> anyone<00:49:49.670> who<00:49:49.790> didn't<00:49:50.030> hear 00:49:50.110 --> 00:49:50.120 align:start position:0% recant that for anyone who didn't hear 00:49:50.120 --> 00:49:50.980 align:start position:0% recant that for anyone who didn't hear because<00:49:50.360> I<00:49:50.510> thought<00:49:50.660> it<00:49:50.750> was<00:49:50.840> really 00:49:50.980 --> 00:49:50.990 align:start position:0% because I thought it was really 00:49:50.990 --> 00:49:54.040 align:start position:0% because I thought it was really wonderful<00:49:52.270> it<00:49:53.270> was<00:49:53.330> a<00:49:53.390> positive<00:49:53.630> community 00:49:54.040 --> 00:49:54.050 align:start position:0% wonderful it was a positive community 00:49:54.050 --> 00:49:55.570 align:start position:0% wonderful it was a positive community action<00:49:54.410> in<00:49:54.500> organizing<00:49:55.070> yeah<00:49:55.250> first<00:49:55.430> people 00:49:55.570 --> 00:49:55.580 align:start position:0% action in organizing yeah first people 00:49:55.580 --> 00:49:58.450 align:start position:0% action in organizing yeah first people in<00:49:55.700> the<00:49:55.730> video<00:49:56.290> yeah<00:49:57.290> that<00:49:57.530> that<00:49:57.890> let's<00:49:58.190> let's 00:49:58.450 --> 00:49:58.460 align:start position:0% in the video yeah that that let's let's 00:49:58.460 --> 00:49:59.860 align:start position:0% in the video yeah that that let's let's get<00:49:58.610> a<00:49:58.670> forum<00:49:59.060> but<00:49:59.210> let's<00:49:59.330> get<00:49:59.450> a<00:49:59.480> community 00:49:59.860 --> 00:49:59.870 align:start position:0% get a forum but let's get a community 00:49:59.870 --> 00:50:01.180 align:start position:0% get a forum but let's get a community going<00:50:00.050> when<00:50:00.260> we<00:50:00.380> list<00:50:00.590> the<00:50:00.770> plugins<00:50:01.100> that 00:50:01.180 --> 00:50:01.190 align:start position:0% going when we list the plugins that 00:50:01.190 --> 00:50:03.340 align:start position:0% going when we list the plugins that would<00:50:01.280> be<00:50:01.370> most<00:50:01.550> beneficial<00:50:01.870> right<00:50:02.870> now<00:50:03.050> we've 00:50:03.340 --> 00:50:03.350 align:start position:0% would be most beneficial right now we've 00:50:03.350 --> 00:50:05.230 align:start position:0% would be most beneficial right now we've got<00:50:03.560> we've<00:50:03.890> got<00:50:04.040> the<00:50:04.220> kind<00:50:04.970> of<00:50:05.030> plug-in 00:50:05.230 --> 00:50:05.240 align:start position:0% got we've got the kind of plug-in 00:50:05.240 --> 00:50:07.780 align:start position:0% got we've got the kind of plug-in repository<00:50:05.540> we<00:50:06.470> also<00:50:06.620> have<00:50:06.770> started<00:50:07.100> a<00:50:07.220> key 00:50:07.780 --> 00:50:07.790 align:start position:0% repository we also have started a key 00:50:07.790 --> 00:50:10.360 align:start position:0% repository we also have started a key base<00:50:08.080> team<00:50:09.080> channel<00:50:09.590> called<00:50:09.890> meta<00:50:10.070> master 00:50:10.360 --> 00:50:10.370 align:start position:0% base team channel called meta master 00:50:10.370 --> 00:50:13.690 align:start position:0% base team channel called meta master plugin<00:50:10.760> I<00:50:11.600> think<00:50:11.870> with<00:50:11.960> an<00:50:12.050> S<00:50:12.230> which<00:50:13.040> one<00:50:13.670> of 00:50:13.690 --> 00:50:13.700 align:start position:0% plugin I think with an S which one of 00:50:13.700 --> 00:50:15.190 align:start position:0% plugin I think with an S which one of them<00:50:13.850> is<00:50:13.910> a<00:50:13.970> fish<00:50:14.150> are<00:50:14.300> probably<00:50:14.750> good<00:50:15.020> by<00:50:15.140> the 00:50:15.190 --> 00:50:15.200 align:start position:0% them is a fish are probably good by the 00:50:15.200 --> 00:50:17.150 align:start position:0% them is a fish are probably good by the time<00:50:15.290> I<00:50:15.440> roll 00:50:17.150 --> 00:50:17.160 align:start position:0% time I roll 00:50:17.160 --> 00:50:20.420 align:start position:0% time I roll we'll<00:50:17.880> get<00:50:18.020> I<00:50:19.020> think<00:50:19.560> it's<00:50:19.770> on<00:50:19.890> the<00:50:19.920> weekend<00:50:20.280> if 00:50:20.420 --> 00:50:20.430 align:start position:0% we'll get I think it's on the weekend if 00:50:20.430 --> 00:50:21.980 align:start position:0% we'll get I think it's on the weekend if you're<00:50:20.580> on<00:50:20.760> that<00:50:20.910> on<00:50:21.030> the<00:50:21.150> repo<00:50:21.420> but<00:50:21.660> but<00:50:21.900> yeah 00:50:21.980 --> 00:50:21.990 align:start position:0% you're on that on the repo but but yeah 00:50:21.990 --> 00:50:23.510 align:start position:0% you're on that on the repo but but yeah I<00:50:22.020> agree<00:50:22.500> we<00:50:22.650> should<00:50:22.680> we<00:50:22.950> should<00:50:23.100> get<00:50:23.160> those<00:50:23.370> we 00:50:23.510 --> 00:50:23.520 align:start position:0% I agree we should we should get those we 00:50:23.520 --> 00:50:24.800 align:start position:0% I agree we should we should get those we should<00:50:23.580> get<00:50:23.760> bounties<00:50:24.090> on<00:50:24.240> them<00:50:24.390> because 00:50:24.800 --> 00:50:24.810 align:start position:0% should get bounties on them because 00:50:24.810 --> 00:50:27.110 align:start position:0% should get bounties on them because things<00:50:25.200> like<00:50:25.320> like<00:50:25.890> a<00:50:25.920> stark<00:50:26.220> signer<00:50:26.490> that's<00:50:27.000> a 00:50:27.110 --> 00:50:27.120 align:start position:0% things like like a stark signer that's a 00:50:27.120 --> 00:50:29.090 align:start position:0% things like like a stark signer that's a thing<00:50:27.300> where<00:50:27.510> one<00:50:27.870> person<00:50:28.200> makes<00:50:28.380> it<00:50:28.590> every 00:50:29.090 --> 00:50:29.100 align:start position:0% thing where one person makes it every 00:50:29.100 --> 00:50:31.280 align:start position:0% thing where one person makes it every dub<00:50:29.400> can<00:50:29.640> use<00:50:29.760> it<00:50:29.940> right<00:50:30.360> and<00:50:30.900> bet<00:50:31.110> those 00:50:31.280 --> 00:50:31.290 align:start position:0% dub can use it right and bet those 00:50:31.290 --> 00:50:34.600 align:start position:0% dub can use it right and bet those accounts<00:50:31.620> are<00:50:31.680> portable<00:50:32.070> between<00:50:32.280> adapts<00:50:32.700> I 00:50:34.600 --> 00:50:34.610 align:start position:0% accounts are portable between adapts I 00:50:34.610 --> 00:50:38.480 align:start position:0% accounts are portable between adapts I requested<00:50:35.610> without<00:50:36.290> reminding<00:50:37.290> example<00:50:38.040> that 00:50:38.480 --> 00:50:38.490 align:start position:0% requested without reminding example that 00:50:38.490 --> 00:50:40.460 align:start position:0% requested without reminding example that Eric<00:50:38.790> showed<00:50:39.060> where<00:50:39.390> you<00:50:39.540> are<00:50:39.690> listing<00:50:39.930> that 00:50:40.460 --> 00:50:40.470 align:start position:0% Eric showed where you are listing that 00:50:40.470 --> 00:50:43.220 align:start position:0% Eric showed where you are listing that sort<00:50:40.770> of<00:50:40.860> criteria<00:50:41.090> that<00:50:42.090> typically<00:50:42.480> users 00:50:43.220 --> 00:50:43.230 align:start position:0% sort of criteria that typically users 00:50:43.230 --> 00:50:45.170 align:start position:0% sort of criteria that typically users now<00:50:43.440> do<00:50:43.500> made<00:50:43.830> me<00:50:44.010> relate<00:50:44.280> to<00:50:44.460> add<00:50:44.580> joking 00:50:45.170 --> 00:50:45.180 align:start position:0% now do made me relate to add joking 00:50:45.180 --> 00:50:45.770 align:start position:0% now do made me relate to add joking right 00:50:45.770 --> 00:50:45.780 align:start position:0% right 00:50:45.780 --> 00:50:47.240 align:start position:0% right so<00:50:45.930> does<00:50:46.140> that<00:50:46.290> actually<00:50:46.470> could<00:50:46.890> that<00:50:47.040> like 00:50:47.240 --> 00:50:47.250 align:start position:0% so does that actually could that like 00:50:47.250 --> 00:50:49.700 align:start position:0% so does that actually could that like replace<00:50:48.030> that<00:50:48.390> process<00:50:49.080> so<00:50:49.680> that 00:50:49.700 --> 00:50:49.710 align:start position:0% replace that process so that 00:50:49.710 --> 00:50:52.820 align:start position:0% replace that process so that theoretically<00:50:50.700> a<00:50:51.380> developer<00:50:52.380> let's<00:50:52.710> say 00:50:52.820 --> 00:50:52.830 align:start position:0% theoretically a developer let's say 00:50:52.830 --> 00:50:54.260 align:start position:0% theoretically a developer let's say you're<00:50:53.010> doing<00:50:53.070> some<00:50:53.340> benefits<00:50:53.790> actions<00:50:54.180> do 00:50:54.260 --> 00:50:54.270 align:start position:0% you're doing some benefits actions do 00:50:54.270 --> 00:50:56.090 align:start position:0% you're doing some benefits actions do you<00:50:54.360> want<00:50:54.510> to<00:50:54.570> use<00:50:54.660> your<00:50:54.720> token<00:50:55.170> and<00:50:55.440> that<00:50:55.980> you 00:50:56.090 --> 00:50:56.100 align:start position:0% you want to use your token and that you 00:50:56.100 --> 00:50:58.310 align:start position:0% you want to use your token and that you can<00:50:56.280> kind<00:50:56.610> of<00:50:56.640> add<00:50:56.910> that<00:50:57.170> tokens<00:50:58.170> and 00:50:58.310 --> 00:50:58.320 align:start position:0% can kind of add that tokens and 00:50:58.320 --> 00:51:00.140 align:start position:0% can kind of add that tokens and understand<00:50:58.950> that<00:50:59.100> Kerina<00:50:59.250> the<00:50:59.610> question<00:50:59.970> is 00:51:00.140 --> 00:51:00.150 align:start position:0% understand that Kerina the question is 00:51:00.150 --> 00:51:02.960 align:start position:0% understand that Kerina the question is whether<00:51:00.660> the<00:51:01.050> the<00:51:01.440> API<00:51:02.130> were<00:51:02.340> exposing<00:51:02.670> for 00:51:02.960 --> 00:51:02.970 align:start position:0% whether the the API were exposing for 00:51:02.970 --> 00:51:04.850 align:start position:0% whether the the API were exposing for managing<00:51:03.330> assets<00:51:03.510> could<00:51:03.930> replace<00:51:04.260> the<00:51:04.530> manual 00:51:04.850 --> 00:51:04.860 align:start position:0% managing assets could replace the manual 00:51:04.860 --> 00:51:06.740 align:start position:0% managing assets could replace the manual process<00:51:04.980> of<00:51:05.370> users<00:51:05.640> adding<00:51:05.940> tokens<00:51:06.330> that's 00:51:06.740 --> 00:51:06.750 align:start position:0% process of users adding tokens that's 00:51:06.750 --> 00:51:08.990 align:start position:0% process of users adding tokens that's totally<00:51:07.200> the<00:51:07.320> point<00:51:07.580> being<00:51:08.580> the<00:51:08.700> stuff<00:51:08.880> on 00:51:08.990 --> 00:51:09.000 align:start position:0% totally the point being the stuff on 00:51:09.000 --> 00:51:11.420 align:start position:0% totally the point being the stuff on here<00:51:09.120> actually<00:51:09.480> have<00:51:09.600> it<00:51:09.720> both<00:51:09.840> the<00:51:10.050> IP<00:51:10.430> 747 00:51:11.420 --> 00:51:11.430 align:start position:0% here actually have it both the IP 747 00:51:11.430 --> 00:51:13.070 align:start position:0% here actually have it both the IP 747 has<00:51:11.760> the<00:51:11.910> kind<00:51:12.090> of<00:51:12.120> real<00:51:12.300> popular<00:51:12.750> of<00:51:12.870> y'all 00:51:13.070 --> 00:51:13.080 align:start position:0% has the kind of real popular of y'all 00:51:13.080 --> 00:51:16.130 align:start position:0% has the kind of real popular of y'all but<00:51:13.590> it<00:51:14.190> already<00:51:14.820> does<00:51:15.150> that<00:51:15.330> it<00:51:15.420> suggests<00:51:15.780> the 00:51:16.130 --> 00:51:16.140 align:start position:0% but it already does that it suggests the 00:51:16.140 --> 00:51:18.290 align:start position:0% but it already does that it suggests the API<00:51:16.590> at<00:51:17.100> a<00:51:17.160> time<00:51:17.370> of<00:51:17.520> tokens<00:51:17.850> so<00:51:17.970> you<00:51:18.060> can<00:51:18.210> do 00:51:18.290 --> 00:51:18.300 align:start position:0% API at a time of tokens so you can do 00:51:18.300 --> 00:51:19.730 align:start position:0% API at a time of tokens so you can do that<00:51:18.450> today<00:51:18.630> but<00:51:19.140> this<00:51:19.290> is<00:51:19.350> the<00:51:19.470> way<00:51:19.560> that<00:51:19.680> a 00:51:19.730 --> 00:51:19.740 align:start position:0% that today but this is the way that a 00:51:19.740 --> 00:51:20.990 align:start position:0% that today but this is the way that a whole<00:51:19.950> are<00:51:20.160> going<00:51:20.280> to<00:51:20.370> do<00:51:20.520> it<00:51:20.610> so<00:51:20.700> if<00:51:20.820> you've 00:51:20.990 --> 00:51:21.000 align:start position:0% whole are going to do it so if you've 00:51:21.000 --> 00:51:22.580 align:start position:0% whole are going to do it so if you've got<00:51:21.210> like<00:51:21.480> not<00:51:21.690> just<00:51:21.900> one<00:51:22.020> plugin<00:51:22.350> but<00:51:22.470> you've 00:51:22.580 --> 00:51:22.590 align:start position:0% got like not just one plugin but you've 00:51:22.590 --> 00:51:25.940 align:start position:0% got like not just one plugin but you've got<00:51:22.800> your<00:51:23.430> a<00:51:23.820> directory<00:51:24.420> or<00:51:25.050> something<00:51:25.410> and 00:51:25.940 --> 00:51:25.950 align:start position:0% got your a directory or something and 00:51:25.950 --> 00:51:27.530 align:start position:0% got your a directory or something and also<00:51:26.460> most<00:51:26.700> of<00:51:26.850> those<00:51:26.940> that<00:51:27.090> you<00:51:27.150> guys<00:51:27.270> like 00:51:27.530 --> 00:51:27.540 align:start position:0% also most of those that you guys like 00:51:27.540 --> 00:51:29.750 align:start position:0% also most of those that you guys like that<00:51:27.750> that's<00:51:28.410> that<00:51:28.650> is<00:51:28.920> a<00:51:28.950> rough<00:51:29.250> that<00:51:29.460> is<00:51:29.520> like 00:51:29.750 --> 00:51:29.760 align:start position:0% that that's that is a rough that is like 00:51:29.760 --> 00:51:31.910 align:start position:0% that that's that is a rough that is like a<00:51:29.910> proposal<00:51:30.420> right<00:51:30.690> basically<00:51:31.230> all<00:51:31.440> these<00:51:31.590> api 00:51:31.910 --> 00:51:31.920 align:start position:0% a proposal right basically all these api 00:51:31.920 --> 00:51:34.490 align:start position:0% a proposal right basically all these api sorry<00:51:32.220> IP<00:51:32.610> giraffe<00:51:33.390> giraffe<00:51:33.690> stages<00:51:34.350> like 00:51:34.490 --> 00:51:34.500 align:start position:0% sorry IP giraffe giraffe stages like 00:51:34.500 --> 00:51:36.200 align:start position:0% sorry IP giraffe giraffe stages like we're<00:51:35.100> traveling<00:51:35.280> it's<00:51:35.520> you<00:51:35.640> as<00:51:35.760> early<00:51:36.030> as<00:51:36.090> we 00:51:36.200 --> 00:51:36.210 align:start position:0% we're traveling it's you as early as we 00:51:36.210 --> 00:51:38.330 align:start position:0% we're traveling it's you as early as we can<00:51:36.420> so<00:51:36.630> we<00:51:36.660> can<00:51:36.900> get<00:51:37.020> feedback<00:51:37.230> and<00:51:37.650> not<00:51:37.770> feel 00:51:38.330 --> 00:51:38.340 align:start position:0% can so we can get feedback and not feel 00:51:38.340 --> 00:51:40.130 align:start position:0% can so we can get feedback and not feel hurt<00:51:38.610> if<00:51:38.760> we<00:51:38.820> change<00:51:39.150> the<00:51:39.300> quality<00:51:39.660> customers 00:51:40.130 --> 00:51:40.140 align:start position:0% hurt if we change the quality customers 00:51:40.140 --> 00:51:46.660 align:start position:0% hurt if we change the quality customers okay<00:51:43.190> that's<00:51:44.190> a<00:51:44.280> plugin<00:51:44.670> you<00:51:44.970> get<00:51:45.090> access<00:51:45.270> to 00:51:46.660 --> 00:51:46.670 align:start position:0% okay that's a plugin you get access to 00:51:46.670 --> 00:51:49.930 align:start position:0% okay that's a plugin you get access to upon<00:51:47.269> it<00:51:47.680> no<00:51:48.680> as<00:51:48.950> a<00:51:48.980> plugin<00:51:49.369> you<00:51:49.460> do<00:51:49.579> not<00:51:49.730> get 00:51:49.930 --> 00:51:49.940 align:start position:0% upon it no as a plugin you do not get 00:51:49.940 --> 00:51:51.880 align:start position:0% upon it no as a plugin you do not get access<00:51:50.269> to<00:51:50.299> the<00:51:50.480> mind<00:51:50.750> what<00:51:51.079> you<00:51:51.260> get<00:51:51.470> is<00:51:51.680> you 00:51:51.880 --> 00:51:51.890 align:start position:0% access to the mind what you get is you 00:51:51.890 --> 00:51:54.400 align:start position:0% access to the mind what you get is you get<00:51:52.069> the<00:51:52.760> top<00:51:53.059> key<00:51:53.299> that<00:51:53.480> proposal<00:51:54.200> that<00:51:54.289> we're 00:51:54.400 --> 00:51:54.410 align:start position:0% get the top key that proposal that we're 00:51:54.410 --> 00:51:57.099 align:start position:0% get the top key that proposal that we're using<00:51:54.559> right<00:51:54.799> the<00:51:55.640> idea<00:51:55.940> that<00:51:56.089> came<00:51:56.539> to<00:51:56.779> it<00:51:57.079> was 00:51:57.099 --> 00:51:57.109 align:start position:0% using right the idea that came to it was 00:51:57.109 --> 00:51:59.440 align:start position:0% using right the idea that came to it was from<00:51:57.410> RM<00:51:57.710> to<00:51:57.859> go<00:51:57.980> from<00:51:58.220> 0<00:51:58.430> X<00:51:58.579> protocol<00:51:59.000> it<00:51:59.329> was<00:51:59.420> a 00:51:59.440 --> 00:51:59.450 align:start position:0% from RM to go from 0 X protocol it was a 00:51:59.450 --> 00:52:01.150 align:start position:0% from RM to go from 0 X protocol it was a very<00:51:59.720> simple<00:52:00.140> and<00:52:00.230> elegant<00:52:00.260> solution<00:52:00.799> I 00:52:01.150 --> 00:52:01.160 align:start position:0% very simple and elegant solution I 00:52:01.160 --> 00:52:03.390 align:start position:0% very simple and elegant solution I thought<00:52:01.369> we<00:52:01.609> take<00:52:01.789> the<00:52:02.089> your<00:52:02.690> current<00:52:02.990> account 00:52:03.390 --> 00:52:03.400 align:start position:0% thought we take the your current account 00:52:03.400 --> 00:52:06.819 align:start position:0% thought we take the your current account for<00:52:04.400> for<00:52:04.970> each<00:52:05.089> account<00:52:05.450> we<00:52:05.900> take<00:52:06.109> its<00:52:06.440> private 00:52:06.819 --> 00:52:06.829 align:start position:0% for for each account we take its private 00:52:06.829 --> 00:52:08.890 align:start position:0% for for each account we take its private key<00:52:07.010> combined<00:52:07.609> it<00:52:07.730> with<00:52:07.760> through<00:52:08.029> the<00:52:08.539> plugins 00:52:08.890 --> 00:52:08.900 align:start position:0% key combined it with through the plugins 00:52:08.900 --> 00:52:10.569 align:start position:0% key combined it with through the plugins domain<00:52:09.349> so<00:52:09.859> it's<00:52:10.010> the<00:52:10.099> most<00:52:10.250> secure 00:52:10.569 --> 00:52:10.579 align:start position:0% domain so it's the most secure 00:52:10.579 --> 00:52:12.130 align:start position:0% domain so it's the most secure identifier<00:52:11.180> we<00:52:11.329> have<00:52:11.480> of<00:52:11.660> it<00:52:11.779> hopefully<00:52:12.049> in 00:52:12.130 --> 00:52:12.140 align:start position:0% identifier we have of it hopefully in 00:52:12.140 --> 00:52:13.660 align:start position:0% identifier we have of it hopefully in the<00:52:12.170> NS<00:52:12.470> name<00:52:12.680> or<00:52:12.799> something<00:52:13.069> can<00:52:13.400> we<00:52:13.490> hash 00:52:13.660 --> 00:52:13.670 align:start position:0% the NS name or something can we hash 00:52:13.670 --> 00:52:15.759 align:start position:0% the NS name or something can we hash those<00:52:13.940> together<00:52:14.180> so<00:52:14.660> generate<00:52:15.140> a<00:52:15.200> new<00:52:15.349> private 00:52:15.759 --> 00:52:15.769 align:start position:0% those together so generate a new private 00:52:15.769 --> 00:52:17.710 align:start position:0% those together so generate a new private key<00:52:15.920> that<00:52:15.950> is<00:52:16.190> exposed<00:52:16.579> to<00:52:16.789> that<00:52:16.910> plugin<00:52:17.359> so 00:52:17.710 --> 00:52:17.720 align:start position:0% key that is exposed to that plugin so 00:52:17.720 --> 00:52:19.299 align:start position:0% key that is exposed to that plugin so your<00:52:17.869> plugin<00:52:18.230> has<00:52:18.349> a<00:52:18.410> private<00:52:18.859> key<00:52:18.980> that<00:52:19.010> is 00:52:19.299 --> 00:52:19.309 align:start position:0% your plugin has a private key that is 00:52:19.309 --> 00:52:21.490 align:start position:0% your plugin has a private key that is deterministic<00:52:20.299> we<00:52:20.569> generated<00:52:21.049> from<00:52:21.289> the 00:52:21.490 --> 00:52:21.500 align:start position:0% deterministic we generated from the 00:52:21.500 --> 00:52:23.440 align:start position:0% deterministic we generated from the user's<00:52:21.829> seed<00:52:22.069> in<00:52:22.309> a<00:52:22.579> way<00:52:22.700> that<00:52:22.880> only<00:52:23.059> your 00:52:23.440 --> 00:52:23.450 align:start position:0% user's seed in a way that only your 00:52:23.450 --> 00:52:27.009 align:start position:0% user's seed in a way that only your plugin<00:52:23.900> has<00:52:23.990> access<00:52:24.440> to<00:52:24.470> and<00:52:24.799> that's<00:52:25.460> why<00:52:26.019> you 00:52:27.009 --> 00:52:27.019 align:start position:0% plugin has access to and that's why you 00:52:27.019 --> 00:52:28.630 align:start position:0% plugin has access to and that's why you know<00:52:27.140> the<00:52:27.319> get<00:52:27.529> out<00:52:27.619> keys<00:52:27.859> proposal<00:52:28.279> had<00:52:28.400> some 00:52:28.630 --> 00:52:28.640 align:start position:0% know the get out keys proposal had some 00:52:28.640 --> 00:52:30.609 align:start position:0% know the get out keys proposal had some kind<00:52:28.910> of<00:52:28.940> a<00:52:29.119> critique<00:52:29.630> when<00:52:29.869> we<00:52:30.019> first<00:52:30.230> posted 00:52:30.609 --> 00:52:30.619 align:start position:0% kind of a critique when we first posted 00:52:30.619 --> 00:52:32.200 align:start position:0% kind of a critique when we first posted it<00:52:30.710> because<00:52:31.039> all<00:52:31.309> these<00:52:31.640> keys<00:52:32.000> aren't 00:52:32.200 --> 00:52:32.210 align:start position:0% it because all these keys aren't 00:52:32.210 --> 00:52:34.150 align:start position:0% it because all these keys aren't portable<00:52:32.690> between<00:52:32.839> sites<00:52:33.289> we'll<00:52:33.799> invite<00:52:34.010> the 00:52:34.150 --> 00:52:34.160 align:start position:0% portable between sites we'll invite the 00:52:34.160 --> 00:52:36.730 align:start position:0% portable between sites we'll invite the PI<00:52:34.279> to<00:52:34.339> plugins<00:52:34.819> they<00:52:35.269> absolutely<00:52:35.480> are<00:52:35.809> so<00:52:36.529> now 00:52:36.730 --> 00:52:36.740 align:start position:0% PI to plugins they absolutely are so now 00:52:36.740 --> 00:52:38.380 align:start position:0% PI to plugins they absolutely are so now a<00:52:36.769> single<00:52:37.279> plug-in<00:52:37.609> can<00:52:37.819> represent<00:52:38.000> a<00:52:38.210> single 00:52:38.380 --> 00:52:38.390 align:start position:0% a single plug-in can represent a single 00:52:38.390 --> 00:52:40.359 align:start position:0% a single plug-in can represent a single sign<00:52:38.660> of<00:52:38.690> strategy<00:52:39.230> and<00:52:39.410> every<00:52:39.829> account<00:52:40.190> can 00:52:40.359 --> 00:52:40.369 align:start position:0% sign of strategy and every account can 00:52:40.369 --> 00:52:42.009 align:start position:0% sign of strategy and every account can have<00:52:40.430> any<00:52:40.730> number<00:52:40.970> of<00:52:41.180> key<00:52:41.420> types<00:52:41.660> associated 00:52:42.009 --> 00:52:42.019 align:start position:0% have any number of key types associated 00:52:42.019 --> 00:52:47.680 align:start position:0% have any number of key types associated with<00:52:43.089> yeah<00:52:44.589> what<00:52:45.589> that<00:52:45.619> question<00:52:46.599> it's<00:52:47.599> a 00:52:47.680 --> 00:52:47.690 align:start position:0% with yeah what that question it's a 00:52:47.690 --> 00:52:50.500 align:start position:0% with yeah what that question it's a plugin<00:52:47.900> ideas<00:52:48.319> is<00:52:49.039> going<00:52:49.250> to<00:52:49.309> be<00:52:49.369> pasted<00:52:50.329> based 00:52:50.500 --> 00:52:50.510 align:start position:0% plugin ideas is going to be pasted based 00:52:50.510 --> 00:52:55.070 align:start position:0% plugin ideas is going to be pasted based off<00:52:50.690> of<00:52:50.720> these<00:52:51.079> critical<00:52:51.710> plugin 00:52:55.070 --> 00:52:55.080 align:start position:0% 00:52:55.080 --> 00:52:59.900 align:start position:0% twelve<00:52:55.950> crazy<00:52:56.370> I<00:52:57.890> started<00:52:58.890> yet 00:52:59.900 --> 00:52:59.910 align:start position:0% twelve crazy I started yet 00:52:59.910 --> 00:53:03.930 align:start position:0% twelve crazy I started yet [Music] 00:53:03.930 --> 00:53:03.940 align:start position:0% 00:53:03.940 --> 00:53:07.000 align:start position:0% so<00:53:04.940> it's<00:53:05.090> not<00:53:05.300> so<00:53:05.600> it's<00:53:05.690> so<00:53:06.260> the<00:53:06.350> key<00:53:06.560> is<00:53:06.860> not 00:53:07.000 --> 00:53:07.010 align:start position:0% so it's not so it's so the key is not 00:53:07.010 --> 00:53:09.160 align:start position:0% so it's not so it's so the key is not based<00:53:07.370> on<00:53:07.550> the<00:53:07.670> source<00:53:07.910> Cobra<00:53:08.540> deployment 00:53:09.160 --> 00:53:09.170 align:start position:0% based on the source Cobra deployment 00:53:09.170 --> 00:53:12.010 align:start position:0% based on the source Cobra deployment okay<00:53:09.500> right<00:53:10.400> now<00:53:10.700> it's<00:53:11.120> based<00:53:11.330> on<00:53:11.480> the<00:53:11.630> origin 00:53:12.010 --> 00:53:12.020 align:start position:0% okay right now it's based on the origin 00:53:12.020 --> 00:53:15.160 align:start position:0% okay right now it's based on the origin stream<00:53:12.320> which<00:53:12.890> still<00:53:13.660> introduces<00:53:14.660> a<00:53:14.690> problem 00:53:15.160 --> 00:53:15.170 align:start position:0% stream which still introduces a problem 00:53:15.170 --> 00:53:18.400 align:start position:0% stream which still introduces a problem if<00:53:15.380> you<00:53:15.970> hosted<00:53:16.970> somewhere<00:53:17.180> else<00:53:17.420> which<00:53:18.380> is 00:53:18.400 --> 00:53:18.410 align:start position:0% if you hosted somewhere else which is 00:53:18.410 --> 00:53:21.520 align:start position:0% if you hosted somewhere else which is why<00:53:18.680> we<00:53:18.920> would<00:53:19.160> like<00:53:19.430> to<00:53:20.300> support<00:53:20.930> the<00:53:21.170> MS<00:53:21.500> and 00:53:21.520 --> 00:53:21.530 align:start position:0% why we would like to support the MS and 00:53:21.530 --> 00:53:23.410 align:start position:0% why we would like to support the MS and that<00:53:21.950> hopefully<00:53:22.370> it<00:53:22.580> could<00:53:22.790> just<00:53:22.940> be<00:53:23.120> hosted 00:53:23.410 --> 00:53:23.420 align:start position:0% that hopefully it could just be hosted 00:53:23.420 --> 00:53:24.640 align:start position:0% that hopefully it could just be hosted at<00:53:23.480> the<00:53:23.510> same<00:53:23.720> place<00:53:23.930> and<00:53:24.110> you<00:53:24.200> at<00:53:24.320> this<00:53:24.380> point 00:53:24.640 --> 00:53:24.650 align:start position:0% at the same place and you at this point 00:53:24.650 --> 00:53:26.160 align:start position:0% at the same place and you at this point it<00:53:24.860> elsewhere 00:53:26.160 --> 00:53:26.170 align:start position:0% it elsewhere 00:53:26.170 --> 00:53:28.720 align:start position:0% it elsewhere yeah<00:53:27.170> and<00:53:27.530> that<00:53:27.680> lets<00:53:27.860> us<00:53:27.980> like<00:53:28.220> these<00:53:28.490> plugins 00:53:28.720 --> 00:53:28.730 align:start position:0% yeah and that lets us like these plugins 00:53:28.730 --> 00:53:30.310 align:start position:0% yeah and that lets us like these plugins can<00:53:28.970> be<00:53:29.030> updated<00:53:29.480> right<00:53:29.600> now<00:53:29.840> or<00:53:30.110> something 00:53:30.310 --> 00:53:30.320 align:start position:0% can be updated right now or something 00:53:30.320 --> 00:53:31.930 align:start position:0% can be updated right now or something like<00:53:30.560> you<00:53:30.710> could<00:53:30.860> imagine<00:53:31.040> a<00:53:31.340> very<00:53:31.610> very 00:53:31.930 --> 00:53:31.940 align:start position:0% like you could imagine a very very 00:53:31.940 --> 00:53:33.670 align:start position:0% like you could imagine a very very secure<00:53:32.300> resilient<00:53:32.690> process<00:53:33.380> for<00:53:33.530> updating 00:53:33.670 --> 00:53:33.680 align:start position:0% secure resilient process for updating 00:53:33.680 --> 00:53:35.320 align:start position:0% secure resilient process for updating them<00:53:34.040> which<00:53:34.250> is<00:53:34.370> something<00:53:34.400> we're<00:53:34.850> envy<00:53:35.180> is<00:53:35.300> a 00:53:35.320 --> 00:53:35.330 align:start position:0% them which is something we're envy is a 00:53:35.330 --> 00:53:37.720 align:start position:0% them which is something we're envy is a because<00:53:35.780> the<00:53:36.100> Chrome<00:53:37.100> extension<00:53:37.130> store 00:53:37.720 --> 00:53:37.730 align:start position:0% because the Chrome extension store 00:53:37.730 --> 00:53:39.190 align:start position:0% because the Chrome extension store doesn't<00:53:38.090> give<00:53:38.210> us<00:53:38.330> that<00:53:38.540> and<00:53:38.750> they<00:53:38.990> give<00:53:39.110> us 00:53:39.190 --> 00:53:39.200 align:start position:0% doesn't give us that and they give us 00:53:39.200 --> 00:53:40.690 align:start position:0% doesn't give us that and they give us very<00:53:39.440> force<00:53:39.740> permissions<00:53:40.280> that<00:53:40.370> we<00:53:40.430> have<00:53:40.550> to 00:53:40.690 --> 00:53:40.700 align:start position:0% very force permissions that we have to 00:53:40.700 --> 00:53:43.150 align:start position:0% very force permissions that we have to request<00:53:41.140> yeah<00:53:42.140> you'll<00:53:42.560> never<00:53:42.770> have<00:53:42.890> to<00:53:43.040> ask 00:53:43.150 --> 00:53:43.160 align:start position:0% request yeah you'll never have to ask 00:53:43.160 --> 00:53:44.830 align:start position:0% request yeah you'll never have to ask for<00:53:43.490> the<00:53:43.610> ability<00:53:43.940> to<00:53:43.970> rewrite<00:53:44.360> everything<00:53:44.630> on 00:53:44.830 --> 00:53:44.840 align:start position:0% for the ability to rewrite everything on 00:53:44.840 --> 00:53:49.930 align:start position:0% for the ability to rewrite everything on the<00:53:44.900> site<00:53:45.110> it's<00:53:45.500> exposing<00:53:45.800> a<00:53:48.280> baby<00:53:49.370> bring<00:53:49.760> the 00:53:49.930 --> 00:53:49.940 align:start position:0% the site it's exposing a baby bring the 00:53:49.940 --> 00:53:55.440 align:start position:0% the site it's exposing a baby bring the nursing<00:53:51.700> support<00:53:52.700> into<00:53:53.390> the<00:53:53.480> plug-in<00:53:53.720> that 00:53:55.440 --> 00:53:55.450 align:start position:0% nursing support into the plug-in that 00:53:55.450 --> 00:53:57.329 align:start position:0% nursing support into the plug-in that you<00:53:56.170> know<00:53:56.319> you<00:53:56.529> know<00:53:56.619> there's<00:53:56.859> there's<00:53:57.250> a 00:53:57.329 --> 00:53:57.339 align:start position:0% you know you know there's there's a 00:53:57.339 --> 00:53:59.970 align:start position:0% you know you know there's there's a definitely<00:53:58.119> a<00:53:58.210> thing<00:53:58.750> that<00:53:58.960> we<00:53:59.049> toy<00:53:59.289> with<00:53:59.500> and 00:53:59.970 --> 00:53:59.980 align:start position:0% definitely a thing that we toy with and 00:53:59.980 --> 00:54:01.230 align:start position:0% definitely a thing that we toy with and now<00:54:00.130> that<00:54:00.339> we've<00:54:00.460> been<00:54:00.579> playing<00:54:00.789> with<00:54:00.970> this<00:54:01.059> is 00:54:01.230 --> 00:54:01.240 align:start position:0% now that we've been playing with this is 00:54:01.240 --> 00:54:02.819 align:start position:0% now that we've been playing with this is goodbye<00:54:01.900> that<00:54:02.170> we<00:54:02.319> can<00:54:02.529> move<00:54:02.650> our 00:54:02.819 --> 00:54:02.829 align:start position:0% goodbye that we can move our 00:54:02.829 --> 00:54:04.589 align:start position:0% goodbye that we can move our architecture<00:54:03.430> into<00:54:03.670> the<00:54:03.760> plug-in<00:54:04.089> system<00:54:04.269> and 00:54:04.589 --> 00:54:04.599 align:start position:0% architecture into the plug-in system and 00:54:04.599 --> 00:54:06.450 align:start position:0% architecture into the plug-in system and and<00:54:05.019> we<00:54:05.200> get<00:54:05.380> this<00:54:05.589> great<00:54:05.890> kind<00:54:06.190> of<00:54:06.250> code 00:54:06.450 --> 00:54:06.460 align:start position:0% and we get this great kind of code 00:54:06.460 --> 00:54:08.700 align:start position:0% and we get this great kind of code isolation<00:54:07.089> for<00:54:07.299> free<00:54:07.510> it's<00:54:08.410> funny<00:54:08.589> because 00:54:08.700 --> 00:54:08.710 align:start position:0% isolation for free it's funny because 00:54:08.710 --> 00:54:10.440 align:start position:0% isolation for free it's funny because it's<00:54:08.920> kind<00:54:09.099> of<00:54:09.130> a<00:54:09.220> great<00:54:09.460> counterpart<00:54:10.150> to<00:54:10.359> the 00:54:10.440 --> 00:54:10.450 align:start position:0% it's kind of a great counterpart to the 00:54:10.450 --> 00:54:11.670 align:start position:0% it's kind of a great counterpart to the work<00:54:10.569> that<00:54:10.750> Aaron<00:54:11.019> is<00:54:11.109> doing<00:54:11.319> with<00:54:11.440> lava 00:54:11.670 --> 00:54:11.680 align:start position:0% work that Aaron is doing with lava 00:54:11.680 --> 00:54:13.500 align:start position:0% work that Aaron is doing with lava though<00:54:11.890> where<00:54:12.130> we<00:54:12.250> are<00:54:12.339> procedurally<00:54:13.029> sandbox 00:54:13.500 --> 00:54:13.510 align:start position:0% though where we are procedurally sandbox 00:54:13.510 --> 00:54:15.299 align:start position:0% though where we are procedurally sandbox and<00:54:13.720> all<00:54:13.900> of<00:54:14.079> our<00:54:14.170> dependencies<00:54:14.799> using<00:54:15.220> the 00:54:15.299 --> 00:54:15.309 align:start position:0% and all of our dependencies using the 00:54:15.309 --> 00:54:17.490 align:start position:0% and all of our dependencies using the exact<00:54:15.579> same<00:54:15.609> order<00:54:16.539> secured<00:54:16.990> at<00:54:17.109> the<00:54:17.140> script 00:54:17.490 --> 00:54:17.500 align:start position:0% exact same order secured at the script 00:54:17.500 --> 00:54:20.670 align:start position:0% exact same order secured at the script assistant<00:54:18.309> so<00:54:18.900> so<00:54:19.900> yeah<00:54:20.109> I<00:54:20.140> think<00:54:20.380> I<00:54:20.650> think 00:54:20.670 --> 00:54:20.680 align:start position:0% assistant so so yeah I think I think 00:54:20.680 --> 00:54:22.650 align:start position:0% assistant so so yeah I think I think it's<00:54:21.160> a<00:54:21.279> really<00:54:21.549> cool<00:54:21.760> opportunity<00:54:22.059> for 00:54:22.650 --> 00:54:22.660 align:start position:0% it's a really cool opportunity for 00:54:22.660 --> 00:54:24.779 align:start position:0% it's a really cool opportunity for modularity<00:54:23.049> really<00:54:23.680> tight<00:54:23.920> security<00:54:24.279> between 00:54:24.779 --> 00:54:24.789 align:start position:0% modularity really tight security between 00:54:24.789 --> 00:54:27.589 align:start position:0% modularity really tight security between our<00:54:24.940> own<00:54:25.119> infrastructure<00:54:25.660> but<00:54:26.529> yet<00:54:26.710> just 00:54:27.589 --> 00:54:27.599 align:start position:0% our own infrastructure but yet just 00:54:27.599 --> 00:54:30.450 align:start position:0% our own infrastructure but yet just connect<00:54:28.599> with<00:54:29.529> that<00:54:29.559> yet<00:54:29.799> for<00:54:29.980> example<00:54:30.039> yeah 00:54:30.450 --> 00:54:30.460 align:start position:0% connect with that yet for example yeah 00:54:30.460 --> 00:54:33.839 align:start position:0% connect with that yet for example yeah yeah<00:54:30.750> for<00:54:31.750> example<00:54:32.170> yeah<00:54:32.529> not<00:54:33.309> just<00:54:33.490> tokens 00:54:33.839 --> 00:54:33.849 align:start position:0% yeah for example yeah not just tokens 00:54:33.849 --> 00:54:38.779 align:start position:0% yeah for example yeah not just tokens but<00:54:34.089> like<00:54:34.529> almost<00:54:35.529> everything<00:54:35.890> that<00:54:36.069> we<00:54:36.160> do 00:54:38.779 --> 00:54:38.789 align:start position:0% 00:54:38.789 --> 00:54:40.259 align:start position:0% yeah 00:54:40.259 --> 00:54:40.269 align:start position:0% yeah 00:54:40.269 --> 00:54:42.690 align:start position:0% yeah so<00:54:40.599> the<00:54:41.170> user<00:54:41.380> prompt<00:54:41.890> was<00:54:42.039> just<00:54:42.309> an<00:54:42.430> alert 00:54:42.690 --> 00:54:42.700 align:start position:0% so the user prompt was just an alert 00:54:42.700 --> 00:54:44.279 align:start position:0% so the user prompt was just an alert like<00:54:43.029> an<00:54:43.180> old-school<00:54:43.450> browser<00:54:43.869> like<00:54:44.140> yeah 00:54:44.279 --> 00:54:44.289 align:start position:0% like an old-school browser like yeah 00:54:44.289 --> 00:54:47.819 align:start position:0% like an old-school browser like yeah these<00:54:44.410> are<00:54:44.559> going<00:54:44.769> to<00:54:44.829> be<00:54:44.950> yeah<00:54:45.789> yeah<00:54:45.819> so<00:54:46.829> just 00:54:47.819 --> 00:54:47.829 align:start position:0% these are going to be yeah yeah so just 00:54:47.829 --> 00:54:49.470 align:start position:0% these are going to be yeah yeah so just to<00:54:47.920> reiterate<00:54:48.099> just<00:54:48.549> concerned<00:54:49.210> that<00:54:49.329> we're 00:54:49.470 --> 00:54:49.480 align:start position:0% to reiterate just concerned that we're 00:54:49.480 --> 00:54:51.180 align:start position:0% to reiterate just concerned that we're just<00:54:49.599> exposing<00:54:50.019> the<00:54:50.079> browser<00:54:50.289> alert<00:54:50.619> no 00:54:51.180 --> 00:54:51.190 align:start position:0% just exposing the browser alert no 00:54:51.190 --> 00:54:54.059 align:start position:0% just exposing the browser alert no that's<00:54:51.460> just<00:54:51.579> MVP<00:54:52.500> we<00:54:53.500> have<00:54:53.799> an<00:54:53.890> opportunity 00:54:54.059 --> 00:54:54.069 align:start position:0% that's just MVP we have an opportunity 00:54:54.069 --> 00:54:55.559 align:start position:0% that's just MVP we have an opportunity to<00:54:54.400> let<00:54:54.579> you<00:54:54.700> render<00:54:55.000> whatever<00:54:55.180> rich 00:54:55.559 --> 00:54:55.569 align:start position:0% to let you render whatever rich 00:54:55.569 --> 00:54:57.359 align:start position:0% to let you render whatever rich notification<00:54:56.230> you<00:54:56.289> want<00:54:56.650> which<00:54:56.799> seems<00:54:57.220> like<00:54:57.339> a 00:54:57.359 --> 00:54:57.369 align:start position:0% notification you want which seems like a 00:54:57.369 --> 00:54:58.799 align:start position:0% notification you want which seems like a pretty<00:54:57.609> big<00:54:57.849> opportunity<00:54:58.480> there<00:54:58.599> have<00:54:58.690> been<00:54:58.750> a 00:54:58.799 --> 00:54:58.809 align:start position:0% pretty big opportunity there have been a 00:54:58.809 --> 00:55:00.210 align:start position:0% pretty big opportunity there have been a number<00:54:58.869> of<00:54:59.230> different<00:54:59.559> proposals<00:54:59.740> from 00:55:00.210 --> 00:55:00.220 align:start position:0% number of different proposals from 00:55:00.220 --> 00:55:01.950 align:start position:0% number of different proposals from different<00:55:00.490> wallets<00:55:00.819> how<00:55:01.390> to<00:55:01.450> let<00:55:01.720> daffs 00:55:01.950 --> 00:55:01.960 align:start position:0% different wallets how to let daffs 00:55:01.960 --> 00:55:05.490 align:start position:0% different wallets how to let daffs propose<00:55:02.519> custom<00:55:03.630> notifications<00:55:04.630> and<00:55:04.809> a<00:55:05.259> lot 00:55:05.490 --> 00:55:05.500 align:start position:0% propose custom notifications and a lot 00:55:05.500 --> 00:55:07.799 align:start position:0% propose custom notifications and a lot of<00:55:05.529> the<00:55:05.740> basically<00:55:06.099> the<00:55:06.549> problem<00:55:06.940> with<00:55:07.420> all<00:55:07.690> of 00:55:07.799 --> 00:55:07.809 align:start position:0% of the basically the problem with all of 00:55:07.809 --> 00:55:09.180 align:start position:0% of the basically the problem with all of them<00:55:07.960> to<00:55:08.200> me<00:55:08.349> the<00:55:08.529> thing<00:55:08.680> that<00:55:08.710> has<00:55:08.920> given<00:55:08.950> the 00:55:09.180 --> 00:55:09.190 align:start position:0% them to me the thing that has given the 00:55:09.190 --> 00:55:10.650 align:start position:0% them to me the thing that has given the apprehension<00:55:09.460> about<00:55:09.880> every<00:55:10.210> propose<00:55:10.539> that 00:55:10.650 --> 00:55:10.660 align:start position:0% apprehension about every propose that 00:55:10.660 --> 00:55:12.420 align:start position:0% apprehension about every propose that I've<00:55:10.809> seen<00:55:11.019> is<00:55:11.259> they<00:55:11.500> all<00:55:11.650> end<00:55:11.920> up<00:55:12.039> pointing<00:55:12.220> up 00:55:12.420 --> 00:55:12.430 align:start position:0% I've seen is they all end up pointing up 00:55:12.430 --> 00:55:14.279 align:start position:0% I've seen is they all end up pointing up some<00:55:12.609> central<00:55:12.910> repository<00:55:13.150> and<00:55:13.990> they're<00:55:14.140> just 00:55:14.279 --> 00:55:14.289 align:start position:0% some central repository and they're just 00:55:14.289 --> 00:55:15.299 align:start position:0% some central repository and they're just like<00:55:14.440> they're<00:55:14.859> like<00:55:15.009> they're<00:55:15.279> like 00:55:15.299 --> 00:55:15.309 align:start position:0% like they're like they're like 00:55:15.309 --> 00:55:17.279 align:start position:0% like they're like they're like decentralize<00:55:15.849> magic<00:55:16.210> like<00:55:16.480> yeah<00:55:16.839> once<00:55:17.109> it's<00:55:17.230> a 00:55:17.279 --> 00:55:17.289 align:start position:0% decentralize magic like yeah once it's a 00:55:17.289 --> 00:55:18.660 align:start position:0% decentralize magic like yeah once it's a TCR<00:55:17.680> it's<00:55:17.829> not<00:55:17.950> a<00:55:17.980> problem<00:55:18.190> or<00:55:18.400> something 00:55:18.660 --> 00:55:18.670 align:start position:0% TCR it's not a problem or something 00:55:18.670 --> 00:55:20.880 align:start position:0% TCR it's not a problem or something here<00:55:19.329> we're<00:55:19.599> saying<00:55:19.900> no<00:55:20.200> very<00:55:20.380> explicitly 00:55:20.880 --> 00:55:20.890 align:start position:0% here we're saying no very explicitly 00:55:20.890 --> 00:55:22.529 align:start position:0% here we're saying no very explicitly there<00:55:21.460> is<00:55:21.700> there's<00:55:22.029> gonna<00:55:22.119> be<00:55:22.269> a<00:55:22.329> mechanism 00:55:22.529 --> 00:55:22.539 align:start position:0% there is there's gonna be a mechanism 00:55:22.539 --> 00:55:25.930 align:start position:0% there is there's gonna be a mechanism for<00:55:22.869> each<00:55:23.319> plug-in<00:55:23.799> to<00:55:24.099> moderate<00:55:25.000> and<00:55:25.180> manage 00:55:25.930 --> 00:55:25.940 align:start position:0% for each plug-in to moderate and manage 00:55:25.940 --> 00:55:27.700 align:start position:0% for each plug-in to moderate and manage you<00:55:26.480> could<00:55:26.630> have<00:55:26.750> a<00:55:26.780> different<00:55:27.020> governance 00:55:27.700 --> 00:55:27.710 align:start position:0% you could have a different governance 00:55:27.710 --> 00:55:29.650 align:start position:0% you could have a different governance protocol<00:55:28.130> for<00:55:28.280> each<00:55:28.480> confirmations<00:55:29.480> for<00:55:29.540> you 00:55:29.650 --> 00:55:29.660 align:start position:0% protocol for each confirmations for you 00:55:29.660 --> 00:55:31.120 align:start position:0% protocol for each confirmations for you together<00:55:29.900> different<00:55:30.560> confirmation<00:55:31.010> screen 00:55:31.120 --> 00:55:31.130 align:start position:0% together different confirmation screen 00:55:31.130 --> 00:55:34.000 align:start position:0% together different confirmation screen for<00:55:31.339> each<00:55:31.400> contract<00:55:32.170> those<00:55:33.170> are<00:55:33.319> that<00:55:33.680> is<00:55:33.859> the 00:55:34.000 --> 00:55:34.010 align:start position:0% for each contract those are that is the 00:55:34.010 --> 00:55:35.020 align:start position:0% for each contract those are that is the kind<00:55:34.160> of<00:55:34.220> conversation<00:55:34.369> that<00:55:34.790> we<00:55:34.880> can<00:55:34.910> have 00:55:35.020 --> 00:55:35.030 align:start position:0% kind of conversation that we can have 00:55:35.030 --> 00:55:37.480 align:start position:0% kind of conversation that we can have methyls<00:55:35.569> we<00:55:35.660> can<00:55:35.839> say<00:55:36.020> what<00:55:36.560> is<00:55:36.710> the<00:55:36.950> amount<00:55:37.310> of 00:55:37.480 --> 00:55:37.490 align:start position:0% methyls we can say what is the amount of 00:55:37.490 --> 00:55:38.859 align:start position:0% methyls we can say what is the amount of granularity<00:55:37.940> we<00:55:38.270> walk<00:55:38.480> with<00:55:38.660> these 00:55:38.859 --> 00:55:38.869 align:start position:0% granularity we walk with these 00:55:38.869 --> 00:55:41.079 align:start position:0% granularity we walk with these conformation<00:55:39.410> which<00:55:39.500> means<00:55:39.680> what<00:55:40.670> would<00:55:40.790> most 00:55:41.079 --> 00:55:41.089 align:start position:0% conformation which means what would most 00:55:41.089 --> 00:55:45.270 align:start position:0% conformation which means what would most empowered<00:55:41.599> that's<00:55:41.990> to<00:55:42.380> feel<00:55:43.130> coherent<00:55:43.760> -<00:55:43.970> oh 00:55:45.270 --> 00:55:45.280 align:start position:0% empowered that's to feel coherent - oh 00:55:45.280 --> 00:55:47.980 align:start position:0% empowered that's to feel coherent - oh yeah<00:55:46.280> yeah<00:55:46.579> I<00:55:46.609> wanted<00:55:47.089> to<00:55:47.150> just<00:55:47.329> how<00:55:47.450> to<00:55:47.510> wrap 00:55:47.980 --> 00:55:47.990 align:start position:0% yeah yeah I wanted to just how to wrap 00:55:47.990 --> 00:55:50.260 align:start position:0% yeah yeah I wanted to just how to wrap this<00:55:48.140> up<00:55:48.290> because<00:55:48.440> uh<00:55:48.560> because<00:55:49.490> this<00:55:49.849> is<00:55:50.000> this 00:55:50.260 --> 00:55:50.270 align:start position:0% this up because uh because this is this 00:55:50.270 --> 00:55:52.750 align:start position:0% this up because uh because this is this is<00:55:50.329> a<00:55:50.750> we're<00:55:51.230> coming<00:55:51.530> up<00:55:51.619> on<00:55:51.829> one<00:55:52.130> of<00:55:52.160> our<00:55:52.520> two 00:55:52.750 --> 00:55:52.760 align:start position:0% is a we're coming up on one of our two 00:55:52.760 --> 00:55:55.359 align:start position:0% is a we're coming up on one of our two hours<00:55:53.060> and<00:55:53.329> art<00:55:53.690> our<00:55:53.960> dream<00:55:54.349> was<00:55:54.650> that<00:55:54.710> we 00:55:55.359 --> 00:55:55.369 align:start position:0% hours and art our dream was that we 00:55:55.369 --> 00:55:56.589 align:start position:0% hours and art our dream was that we could<00:55:55.520> actually<00:55:55.670> get<00:55:55.970> some<00:55:56.150> of<00:55:56.240> you<00:55:56.300> like<00:55:56.450> cuz 00:55:56.589 --> 00:55:56.599 align:start position:0% could actually get some of you like cuz 00:55:56.599 --> 00:55:58.990 align:start position:0% could actually get some of you like cuz I<00:55:56.690> bet<00:55:57.020> a<00:55:57.290> number<00:55:57.680> of<00:55:57.770> you<00:55:57.890> here<00:55:58.099> have<00:55:58.520> like<00:55:58.849> a 00:55:58.990 --> 00:55:59.000 align:start position:0% I bet a number of you here have like a 00:55:59.000 --> 00:56:00.700 align:start position:0% I bet a number of you here have like a library<00:55:59.420> like<00:55:59.480> star<00:55:59.990> per<00:56:00.170> head<00:56:00.349> where<00:56:00.589> it's 00:56:00.700 --> 00:56:00.710 align:start position:0% library like star per head where it's 00:56:00.710 --> 00:56:01.990 align:start position:0% library like star per head where it's like<00:56:00.829> this<00:56:01.280> thing<00:56:01.490> you<00:56:01.609> might<00:56:01.700> be<00:56:01.760> able<00:56:01.880> to 00:56:01.990 --> 00:56:02.000 align:start position:0% like this thing you might be able to 00:56:02.000 --> 00:56:04.420 align:start position:0% like this thing you might be able to just<00:56:02.180> drop<00:56:02.420> in<00:56:02.740> so<00:56:03.740> I'm<00:56:03.859> gonna<00:56:03.980> just<00:56:04.190> give<00:56:04.369> you 00:56:04.420 --> 00:56:04.430 align:start position:0% just drop in so I'm gonna just give you 00:56:04.430 --> 00:56:06.430 align:start position:0% just drop in so I'm gonna just give you a<00:56:04.490> few<00:56:04.730> caveats<00:56:05.030> like<00:56:05.510> current<00:56:06.020> issues<00:56:06.290> that 00:56:06.430 --> 00:56:06.440 align:start position:0% a few caveats like current issues that 00:56:06.440 --> 00:56:07.960 align:start position:0% a few caveats like current issues that you<00:56:06.589> might<00:56:06.740> want<00:56:06.950> to<00:56:07.010> know<00:56:07.160> when<00:56:07.700> you're<00:56:07.819> using 00:56:07.960 --> 00:56:07.970 align:start position:0% you might want to know when you're using 00:56:07.970 --> 00:56:11.230 align:start position:0% you might want to know when you're using the<00:56:08.119> system<00:56:08.480> oh<00:56:09.410> yeah<00:56:09.920> so<00:56:10.460> so<00:56:10.910> you're<00:56:11.089> gonna 00:56:11.230 --> 00:56:11.240 align:start position:0% the system oh yeah so so you're gonna 00:56:11.240 --> 00:56:12.849 align:start position:0% the system oh yeah so so you're gonna you're<00:56:11.690> you<00:56:11.900> might<00:56:12.050> learn<00:56:12.230> through<00:56:12.589> the<00:56:12.680> build 00:56:12.849 --> 00:56:12.859 align:start position:0% you're you might learn through the build 00:56:12.859 --> 00:56:14.260 align:start position:0% you're you might learn through the build system<00:56:13.040> you<00:56:13.310> might<00:56:13.430> get<00:56:13.579> some<00:56:13.849> errors<00:56:14.240> that 00:56:14.260 --> 00:56:14.270 align:start position:0% system you might get some errors that 00:56:14.270 --> 00:56:16.390 align:start position:0% system you might get some errors that are<00:56:14.599> strange<00:56:14.960> or<00:56:15.200> new<00:56:15.380> to<00:56:15.530> use<00:56:15.650> these<00:56:16.250> are 00:56:16.390 --> 00:56:16.400 align:start position:0% are strange or new to use these are 00:56:16.400 --> 00:56:18.160 align:start position:0% are strange or new to use these are usually<00:56:16.579> things<00:56:16.970> about<00:56:17.270> your<00:56:17.540> dependencies 00:56:18.160 --> 00:56:18.170 align:start position:0% usually things about your dependencies 00:56:18.170 --> 00:56:20.470 align:start position:0% usually things about your dependencies tried<00:56:18.470> to<00:56:18.589> mutate<00:56:19.099> the<00:56:19.430> prototype<00:56:19.910> of<00:56:19.940> string 00:56:20.470 --> 00:56:20.480 align:start position:0% tried to mutate the prototype of string 00:56:20.480 --> 00:56:22.059 align:start position:0% tried to mutate the prototype of string or<00:56:20.510> tried<00:56:20.930> to<00:56:21.050> change<00:56:21.290> function<00:56:21.589> or<00:56:21.890> try<00:56:22.040> to 00:56:22.059 --> 00:56:22.069 align:start position:0% or tried to change function or try to 00:56:22.069 --> 00:56:24.790 align:start position:0% or tried to change function or try to mess<00:56:22.460> with<00:56:22.609> what<00:56:22.960> promised<00:56:23.960> it<00:56:24.140> and<00:56:24.319> and 00:56:24.790 --> 00:56:24.800 align:start position:0% mess with what promised it and and 00:56:24.800 --> 00:56:26.770 align:start position:0% mess with what promised it and and that's<00:56:24.980> that's<00:56:25.220> what<00:56:25.400> Eric<00:56:25.790> Emily<00:56:26.180> said<00:56:26.390> to 00:56:26.770 --> 00:56:26.780 align:start position:0% that's that's what Eric Emily said to 00:56:26.780 --> 00:56:28.960 align:start position:0% that's that's what Eric Emily said to club<00:56:27.050> okay<00:56:27.530> if<00:56:28.010> your<00:56:28.160> dependencies<00:56:28.640> are<00:56:28.760> doing 00:56:28.960 --> 00:56:28.970 align:start position:0% club okay if your dependencies are doing 00:56:28.970 --> 00:56:30.579 align:start position:0% club okay if your dependencies are doing things<00:56:29.180> that<00:56:29.240> are<00:56:29.329> downright<00:56:29.660> dangerous<00:56:30.079> and 00:56:30.579 --> 00:56:30.589 align:start position:0% things that are downright dangerous and 00:56:30.589 --> 00:56:31.780 align:start position:0% things that are downright dangerous and they're<00:56:30.680> basically<00:56:30.920> resemble<00:56:31.520> the<00:56:31.640> same 00:56:31.780 --> 00:56:31.790 align:start position:0% they're basically resemble the same 00:56:31.790 --> 00:56:33.700 align:start position:0% they're basically resemble the same thing<00:56:31.970> an<00:56:32.060> attacker<00:56:32.390> would<00:56:32.569> do<00:56:32.720> it's<00:56:33.560> gonna 00:56:33.700 --> 00:56:33.710 align:start position:0% thing an attacker would do it's gonna 00:56:33.710 --> 00:56:35.170 align:start position:0% thing an attacker would do it's gonna fail<00:56:34.010> it's<00:56:34.280> gonna<00:56:34.400> fail<00:56:34.640> on<00:56:34.790> the<00:56:34.849> build<00:56:35.030> system 00:56:35.170 --> 00:56:35.180 align:start position:0% fail it's gonna fail on the build system 00:56:35.180 --> 00:56:36.819 align:start position:0% fail it's gonna fail on the build system it's<00:56:35.690> gonna<00:56:35.810> fail<00:56:36.020> when<00:56:36.200> you<00:56:36.260> try<00:56:36.440> to<00:56:36.500> load<00:56:36.680> it 00:56:36.819 --> 00:56:36.829 align:start position:0% it's gonna fail when you try to load it 00:56:36.829 --> 00:56:38.770 align:start position:0% it's gonna fail when you try to load it into<00:56:36.950> met<00:56:37.130> amount<00:56:37.339> so<00:56:37.880> it's<00:56:38.270> an<00:56:38.359> opportunity 00:56:38.770 --> 00:56:38.780 align:start position:0% into met amount so it's an opportunity 00:56:38.780 --> 00:56:40.780 align:start position:0% into met amount so it's an opportunity of<00:56:38.930> you<00:56:39.140> get<00:56:39.530> off<00:56:39.710> of<00:56:39.740> insecure<00:56:40.280> dependencies 00:56:40.780 --> 00:56:40.790 align:start position:0% of you get off of insecure dependencies 00:56:40.790 --> 00:56:42.760 align:start position:0% of you get off of insecure dependencies and<00:56:41.000> to<00:56:41.510> push<00:56:41.720> security<00:56:42.200> updates<00:56:42.470> to<00:56:42.740> your 00:56:42.760 --> 00:56:42.770 align:start position:0% and to push security updates to your 00:56:42.770 --> 00:56:44.980 align:start position:0% and to push security updates to your dependencies<00:56:43.430> which<00:56:44.270> is<00:56:44.420> a<00:56:44.450> cool<00:56:44.660> side 00:56:44.980 --> 00:56:44.990 align:start position:0% dependencies which is a cool side 00:56:44.990 --> 00:56:46.690 align:start position:0% dependencies which is a cool side benefit<00:56:45.410> of<00:56:45.440> this<00:56:45.589> if<00:56:45.800> you<00:56:45.920> use<00:56:46.220> our<00:56:46.369> plugins 00:56:46.690 --> 00:56:46.700 align:start position:0% benefit of this if you use our plugins 00:56:46.700 --> 00:56:48.460 align:start position:0% benefit of this if you use our plugins isn't<00:56:47.000> here<00:56:47.150> making<00:56:47.569> your<00:56:47.690> dependencies<00:56:48.290> more 00:56:48.460 --> 00:56:48.470 align:start position:0% isn't here making your dependencies more 00:56:48.470 --> 00:56:52.630 align:start position:0% isn't here making your dependencies more secure<00:56:48.829> sweet<00:56:49.700> right<00:56:50.770> we're<00:56:51.770> also<00:56:52.339> gonna<00:56:52.550> add 00:56:52.630 --> 00:56:52.640 align:start position:0% secure sweet right we're also gonna add 00:56:52.640 --> 00:56:54.640 align:start position:0% secure sweet right we're also gonna add big<00:56:53.089> fat<00:56:53.300> security<00:56:53.720> warnings<00:56:54.020> okay<00:56:54.260> none<00:56:54.530> of 00:56:54.640 --> 00:56:54.650 align:start position:0% big fat security warnings okay none of 00:56:54.650 --> 00:56:55.780 align:start position:0% big fat security warnings okay none of these<00:56:54.740> things<00:56:54.950> are<00:56:55.130> perfect<00:56:55.520> we're<00:56:55.670> not 00:56:55.780 --> 00:56:55.790 align:start position:0% these things are perfect we're not 00:56:55.790 --> 00:56:58.150 align:start position:0% these things are perfect we're not claiming<00:56:56.089> that<00:56:56.450> test<00:56:56.750> is<00:56:56.990> perfect<00:56:57.650> it's<00:56:58.010> not<00:56:58.069> a 00:56:58.150 --> 00:56:58.160 align:start position:0% claiming that test is perfect it's not a 00:56:58.160 --> 00:57:00.400 align:start position:0% claiming that test is perfect it's not a panacea<00:56:58.490> but<00:56:58.880> we<00:56:59.030> should<00:56:59.630> aspire<00:56:59.780> for<00:56:59.960> it<00:57:00.290> to 00:57:00.400 --> 00:57:00.410 align:start position:0% panacea but we should aspire for it to 00:57:00.410 --> 00:57:01.690 align:start position:0% panacea but we should aspire for it to be<00:57:00.530> and<00:57:00.740> this<00:57:00.950> is<00:57:01.099> the<00:57:01.220> kind<00:57:01.400> of<00:57:01.460> thing<00:57:01.670> that 00:57:01.690 --> 00:57:01.700 align:start position:0% be and this is the kind of thing that 00:57:01.700 --> 00:57:02.859 align:start position:0% be and this is the kind of thing that the<00:57:01.970> community<00:57:02.359> should<00:57:02.420> rally<00:57:02.690> around 00:57:02.859 --> 00:57:02.869 align:start position:0% the community should rally around 00:57:02.869 --> 00:57:04.359 align:start position:0% the community should rally around helping<00:57:03.560> fund<00:57:03.710> this<00:57:03.859> is<00:57:04.010> this<00:57:04.130> is<00:57:04.220> something 00:57:04.359 --> 00:57:04.369 align:start position:0% helping fund this is this is something 00:57:04.369 --> 00:57:06.370 align:start position:0% helping fund this is this is something worthy<00:57:04.700> of<00:57:04.940> animal<00:57:05.420> walked<00:57:05.569> out<00:57:05.810> of<00:57:06.050> the 00:57:06.370 --> 00:57:06.380 align:start position:0% worthy of animal walked out of the 00:57:06.380 --> 00:57:08.200 align:start position:0% worthy of animal walked out of the community<00:57:06.560> should<00:57:07.010> get<00:57:07.160> around<00:57:07.400> formally 00:57:08.200 --> 00:57:08.210 align:start position:0% community should get around formally 00:57:08.210 --> 00:57:10.510 align:start position:0% community should get around formally verifying<00:57:08.750> tools<00:57:09.140> likes<00:57:09.589> tests<00:57:09.920> that<00:57:10.040> let<00:57:10.369> us 00:57:10.510 --> 00:57:10.520 align:start position:0% verifying tools likes tests that let us 00:57:10.520 --> 00:57:12.430 align:start position:0% verifying tools likes tests that let us all<00:57:10.790> benefit<00:57:11.329> from<00:57:11.480> great<00:57:11.900> the<00:57:12.109> increased 00:57:12.430 --> 00:57:12.440 align:start position:0% all benefit from great the increased 00:57:12.440 --> 00:57:14.680 align:start position:0% all benefit from great the increased security<00:57:12.800> okay<00:57:13.490> this<00:57:13.640> is<00:57:13.730> a<00:57:13.790> huge<00:57:14.240> huge 00:57:14.680 --> 00:57:14.690 align:start position:0% security okay this is a huge huge 00:57:14.690 --> 00:57:17.500 align:start position:0% security okay this is a huge huge community<00:57:15.170> resource<00:57:16.030> and<00:57:17.030> we're<00:57:17.240> gonna<00:57:17.329> give 00:57:17.500 --> 00:57:17.510 align:start position:0% community resource and we're gonna give 00:57:17.510 --> 00:57:18.540 align:start position:0% community resource and we're gonna give a<00:57:17.540> lots<00:57:17.720> of<00:57:17.810> you<00:57:17.900> guys<00:57:18.020> love<00:57:18.230> this 00:57:18.540 --> 00:57:18.550 align:start position:0% a lots of you guys love this 00:57:18.550 --> 00:57:20.310 align:start position:0% a lots of you guys love this in<00:57:18.640> a<00:57:18.700> very<00:57:18.910> rough<00:57:19.150> but<00:57:19.540> you<00:57:19.780> know<00:57:19.900> it's<00:57:20.140> sorry 00:57:20.310 --> 00:57:20.320 align:start position:0% in a very rough but you know it's sorry 00:57:20.320 --> 00:57:22.110 align:start position:0% in a very rough but you know it's sorry for<00:57:20.530> the<00:57:20.620> alerts<00:57:20.860> and<00:57:21.070> all<00:57:21.250> that<00:57:21.460> we<00:57:21.880> really 00:57:22.110 --> 00:57:22.120 align:start position:0% for the alerts and all that we really 00:57:22.120 --> 00:57:23.550 align:start position:0% for the alerts and all that we really just<00:57:22.150> wanted<00:57:22.600> to<00:57:22.660> get<00:57:22.810> it<00:57:22.930> into<00:57:23.080> your<00:57:23.200> hands<00:57:23.410> as 00:57:23.550 --> 00:57:23.560 align:start position:0% just wanted to get it into your hands as 00:57:23.560 --> 00:57:26.460 align:start position:0% just wanted to get it into your hands as soon<00:57:23.590> as<00:57:23.800> possible<00:57:24.720> we're<00:57:25.720> also<00:57:25.900> going<00:57:26.140> to<00:57:26.200> try 00:57:26.460 --> 00:57:26.470 align:start position:0% soon as possible we're also going to try 00:57:26.470 --> 00:57:28.500 align:start position:0% soon as possible we're also going to try to<00:57:26.560> incorporate<00:57:26.920> much<00:57:27.520> better<00:57:27.850> signals<00:57:28.300> about 00:57:28.500 --> 00:57:28.510 align:start position:0% to incorporate much better signals about 00:57:28.510 --> 00:57:30.450 align:start position:0% to incorporate much better signals about whatsoever<00:57:28.930> putable<00:57:29.440> plugin<00:57:29.890> we<00:57:30.160> know<00:57:30.310> that 00:57:30.450 --> 00:57:30.460 align:start position:0% whatsoever putable plugin we know that 00:57:30.460 --> 00:57:31.950 align:start position:0% whatsoever putable plugin we know that one<00:57:30.610> of<00:57:30.640> the<00:57:30.730> reasons<00:57:31.090> our<00:57:31.240> users<00:57:31.630> don't<00:57:31.780> get 00:57:31.950 --> 00:57:31.960 align:start position:0% one of the reasons our users don't get 00:57:31.960 --> 00:57:33.360 align:start position:0% one of the reasons our users don't get fish<00:57:32.200> the<00:57:32.350> very<00:57:32.500> often<00:57:32.800> is<00:57:32.890> that<00:57:33.040> the<00:57:33.160> chrome 00:57:33.360 --> 00:57:33.370 align:start position:0% fish the very often is that the chrome 00:57:33.370 --> 00:57:35.850 align:start position:0% fish the very often is that the chrome store<00:57:33.610> has<00:57:33.820> reviews<00:57:34.270> and<00:57:34.510> user<00:57:34.750> accounts<00:57:35.020> we 00:57:35.850 --> 00:57:35.860 align:start position:0% store has reviews and user accounts we 00:57:35.860 --> 00:57:37.230 align:start position:0% store has reviews and user accounts we would<00:57:36.010> like<00:57:36.190> to<00:57:36.400> extend<00:57:36.550> the<00:57:36.820> similar 00:57:37.230 --> 00:57:37.240 align:start position:0% would like to extend the similar 00:57:37.240 --> 00:57:38.910 align:start position:0% would like to extend the similar opportunities<00:57:37.900> but<00:57:38.140> perhaps<00:57:38.620> in<00:57:38.740> a<00:57:38.800> more 00:57:38.910 --> 00:57:38.920 align:start position:0% opportunities but perhaps in a more 00:57:38.920 --> 00:57:41.850 align:start position:0% opportunities but perhaps in a more decentralized<00:57:39.250> manner<00:57:40.710> obviously<00:57:41.710> we're 00:57:41.850 --> 00:57:41.860 align:start position:0% decentralized manner obviously we're 00:57:41.860 --> 00:57:43.680 align:start position:0% decentralized manner obviously we're gonna<00:57:41.950> put<00:57:42.340> up<00:57:42.430> a<00:57:42.460> bug<00:57:42.850> bounties<00:57:43.270> and<00:57:43.480> we're 00:57:43.680 --> 00:57:43.690 align:start position:0% gonna put up a bug bounties and we're 00:57:43.690 --> 00:57:45.810 align:start position:0% gonna put up a bug bounties and we're gonna<00:57:43.780> have<00:57:43.990> security<00:57:44.530> audits<00:57:44.980> and<00:57:45.130> all<00:57:45.520> sorts 00:57:45.810 --> 00:57:45.820 align:start position:0% gonna have security audits and all sorts 00:57:45.820 --> 00:57:47.820 align:start position:0% gonna have security audits and all sorts of<00:57:45.880> stuff<00:57:46.090> you<00:57:46.660> can't<00:57:46.900> audit<00:57:47.200> this<00:57:47.440> enough 00:57:47.820 --> 00:57:47.830 align:start position:0% of stuff you can't audit this enough 00:57:47.830 --> 00:57:49.530 align:start position:0% of stuff you can't audit this enough this<00:57:48.100> is<00:57:48.280> about<00:57:48.730> the<00:57:48.880> scariest<00:57:49.240> thing<00:57:49.450> you 00:57:49.530 --> 00:57:49.540 align:start position:0% this is about the scariest thing you 00:57:49.540 --> 00:57:51.330 align:start position:0% this is about the scariest thing you could<00:57:49.690> do<00:57:49.840> but<00:57:50.320> if<00:57:50.410> we<00:57:50.440> do<00:57:50.710> it<00:57:50.830> right<00:57:51.040> it<00:57:51.310> just 00:57:51.330 --> 00:57:51.340 align:start position:0% could do but if we do it right it just 00:57:51.340 --> 00:57:55.560 align:start position:0% could do but if we do it right it just could<00:57:52.060> be<00:57:52.330> the<00:57:52.480> coolest<00:57:53.160> and<00:57:54.160> and<00:57:55.000> then<00:57:55.450> of 00:57:55.560 --> 00:57:55.570 align:start position:0% could be the coolest and and then of 00:57:55.570 --> 00:57:56.340 align:start position:0% could be the coolest and and then of course<00:57:55.750> we're<00:57:55.870> going<00:57:55.990> to<00:57:56.050> improve<00:57:56.230> the 00:57:56.340 --> 00:57:56.350 align:start position:0% course we're going to improve the 00:57:56.350 --> 00:57:58.260 align:start position:0% course we're going to improve the performance<00:57:56.560> you've<00:57:57.400> probably<00:57:57.670> noticed<00:57:57.880> that 00:57:58.260 --> 00:57:58.270 align:start position:0% performance you've probably noticed that 00:57:58.270 --> 00:57:59.550 align:start position:0% performance you've probably noticed that you<00:57:58.480> know<00:57:58.570> the<00:57:58.660> popups<00:57:59.020> are<00:57:59.110> already<00:57:59.380> slowing 00:57:59.550 --> 00:57:59.560 align:start position:0% you know the popups are already slowing 00:57:59.560 --> 00:58:01.350 align:start position:0% you know the popups are already slowing madam<00:57:59.890> s<00:58:00.010> this<00:58:00.220> did<00:58:00.670> make<00:58:00.850> it<00:58:00.880> a<00:58:01.030> little<00:58:01.180> bit 00:58:01.350 --> 00:58:01.360 align:start position:0% madam s this did make it a little bit 00:58:01.360 --> 00:58:02.940 align:start position:0% madam s this did make it a little bit worse<00:58:01.510> we're<00:58:02.020> gonna<00:58:02.110> be<00:58:02.290> tooling<00:58:02.710> and<00:58:02.860> we're 00:58:02.940 --> 00:58:02.950 align:start position:0% worse we're gonna be tooling and we're 00:58:02.950 --> 00:58:04.350 align:start position:0% worse we're gonna be tooling and we're gonna<00:58:03.040> be<00:58:03.220> improving<00:58:03.670> and<00:58:03.820> tweaking<00:58:04.150> and<00:58:04.270> all 00:58:04.350 --> 00:58:04.360 align:start position:0% gonna be improving and tweaking and all 00:58:04.360 --> 00:58:06.300 align:start position:0% gonna be improving and tweaking and all that<00:58:04.480> kind<00:58:04.630> of<00:58:04.660> stuff<00:58:04.870> and<00:58:05.800> then<00:58:06.070> of<00:58:06.250> course 00:58:06.300 --> 00:58:06.310 align:start position:0% that kind of stuff and then of course 00:58:06.310 --> 00:58:08.130 align:start position:0% that kind of stuff and then of course we're<00:58:06.640> gonna<00:58:06.700> allow<00:58:07.030> a<00:58:07.060> plugins<00:58:07.630> to<00:58:07.750> specify 00:58:08.130 --> 00:58:08.140 align:start position:0% we're gonna allow a plugins to specify 00:58:08.140 --> 00:58:10.080 align:start position:0% we're gonna allow a plugins to specify settings<00:58:08.470> pages<00:58:08.860> because<00:58:09.340> we<00:58:09.880> don't<00:58:10.030> know 00:58:10.080 --> 00:58:10.090 align:start position:0% settings pages because we don't know 00:58:10.090 --> 00:58:12.240 align:start position:0% settings pages because we don't know what<00:58:10.210> you<00:58:10.270> need<00:58:10.420> but<00:58:10.930> you<00:58:11.050> do<00:58:11.170> you<00:58:12.040> can 00:58:12.240 --> 00:58:12.250 align:start position:0% what you need but you do you can 00:58:12.250 --> 00:58:13.620 align:start position:0% what you need but you do you can basically<00:58:12.700> already<00:58:12.880> hack<00:58:13.210> it<00:58:13.360> together 00:58:13.620 --> 00:58:13.630 align:start position:0% basically already hack it together 00:58:13.630 --> 00:58:15.240 align:start position:0% basically already hack it together because<00:58:13.900> your<00:58:14.170> plugin<00:58:14.560> gets<00:58:14.740> the<00:58:14.860> work<00:58:15.040> the 00:58:15.240 --> 00:58:15.250 align:start position:0% because your plugin gets the work the 00:58:15.250 --> 00:58:16.740 align:start position:0% because your plugin gets the work the requesting<00:58:15.700> origin<00:58:16.060> string<00:58:16.300> so<00:58:16.450> you<00:58:16.600> can 00:58:16.740 --> 00:58:16.750 align:start position:0% requesting origin string so you can 00:58:16.750 --> 00:58:18.570 align:start position:0% requesting origin string so you can basically<00:58:16.870> just<00:58:17.110> say<00:58:17.440> my<00:58:17.620> domain<00:58:18.010> is<00:58:18.040> my<00:58:18.340> set<00:58:18.550> a 00:58:18.570 --> 00:58:18.580 align:start position:0% basically just say my domain is my set a 00:58:18.580 --> 00:58:20.460 align:start position:0% basically just say my domain is my set a string<00:58:18.940> and<00:58:19.090> give<00:58:19.240> it<00:58:19.360> special<00:58:19.540> methods<00:58:20.050> it's 00:58:20.460 --> 00:58:20.470 align:start position:0% string and give it special methods it's 00:58:20.470 --> 00:58:21.870 align:start position:0% string and give it special methods it's just<00:58:20.590> kind<00:58:20.800> of<00:58:20.890> a<00:58:20.950> cool<00:58:21.070> side<00:58:21.280> benefit<00:58:21.730> of 00:58:21.870 --> 00:58:21.880 align:start position:0% just kind of a cool side benefit of 00:58:21.880 --> 00:58:23.310 align:start position:0% just kind of a cool side benefit of getting<00:58:22.000> to<00:58:22.210> define<00:58:22.510> your<00:58:22.690> own<00:58:22.780> permissions 00:58:23.310 --> 00:58:23.320 align:start position:0% getting to define your own permissions 00:58:23.320 --> 00:58:27.150 align:start position:0% getting to define your own permissions and<00:58:24.160> yeah<00:58:25.120> a<00:58:25.150> plug-in<00:58:25.840> update<00:58:26.320> visible<00:58:26.890> will 00:58:27.150 --> 00:58:27.160 align:start position:0% and yeah a plug-in update visible will 00:58:27.160 --> 00:58:28.560 align:start position:0% and yeah a plug-in update visible will be<00:58:27.250> coming<00:58:27.580> that's<00:58:27.700> wave<00:58:27.970> something 00:58:28.560 --> 00:58:28.570 align:start position:0% be coming that's wave something 00:58:28.570 --> 00:58:30.240 align:start position:0% be coming that's wave something definitely<00:58:29.260> required<00:58:29.740> before<00:58:30.040> production 00:58:30.240 --> 00:58:30.250 align:start position:0% definitely required before production 00:58:30.250 --> 00:58:33.240 align:start position:0% definitely required before production and<00:58:31.530> before<00:58:32.530> production<00:58:32.770> we're<00:58:33.040> gonna<00:58:33.160> be 00:58:33.240 --> 00:58:33.250 align:start position:0% and before production we're gonna be 00:58:33.250 --> 00:58:35.100 align:start position:0% and before production we're gonna be walking<00:58:33.580> down<00:58:33.670> all<00:58:33.970> global<00:58:34.240> event<00:58:34.720> Authority 00:58:35.100 --> 00:58:35.110 align:start position:0% walking down all global event Authority 00:58:35.110 --> 00:58:36.510 align:start position:0% walking down all global event Authority plugins<00:58:35.470> we<00:58:35.560> have<00:58:35.680> nothing<00:58:35.920> that<00:58:36.100> they<00:58:36.310> didn't 00:58:36.510 --> 00:58:36.520 align:start position:0% plugins we have nothing that they didn't 00:58:36.520 --> 00:58:39.660 align:start position:0% plugins we have nothing that they didn't explicitly<00:58:36.820> ask<00:58:37.570> for<00:58:37.930> from<00:58:38.110> users<00:58:38.670> we're 00:58:39.660 --> 00:58:39.670 align:start position:0% explicitly ask for from users we're 00:58:39.670 --> 00:58:40.950 align:start position:0% explicitly ask for from users we're trying<00:58:39.850> to<00:58:39.910> make<00:58:40.000> the<00:58:40.090> most<00:58:40.270> safe<00:58:40.480> environment 00:58:40.950 --> 00:58:40.960 align:start position:0% trying to make the most safe environment 00:58:40.960 --> 00:58:43.290 align:start position:0% trying to make the most safe environment we<00:58:41.020> can<00:58:41.140> ever<00:58:41.550> and<00:58:42.550> then<00:58:42.790> we<00:58:42.940> gotta<00:58:43.120> just 00:58:43.290 --> 00:58:43.300 align:start position:0% we can ever and then we gotta just 00:58:43.300 --> 00:58:44.430 align:start position:0% we can ever and then we gotta just refine<00:58:43.600> those<00:58:43.750> API 00:58:44.430 --> 00:58:44.440 align:start position:0% refine those API 00:58:44.440 --> 00:58:45.990 align:start position:0% refine those API beyond<00:58:44.710> all<00:58:44.830> that<00:58:44.980> is<00:58:45.250> just<00:58:45.310> about<00:58:45.730> getting 00:58:45.990 --> 00:58:46.000 align:start position:0% beyond all that is just about getting 00:58:46.000 --> 00:58:48.120 align:start position:0% beyond all that is just about getting you<00:58:46.240> guys<00:58:46.300> to<00:58:46.750> communicate<00:58:47.410> rally<00:58:47.770> around<00:58:47.950> the 00:58:48.120 --> 00:58:48.130 align:start position:0% you guys to communicate rally around the 00:58:48.130 --> 00:58:49.590 align:start position:0% you guys to communicate rally around the plugins<00:58:48.460> that<00:58:48.580> are<00:58:48.640> most<00:58:48.910> effective<00:58:49.360> and<00:58:49.540> the 00:58:49.590 --> 00:58:49.600 align:start position:0% plugins that are most effective and the 00:58:49.600 --> 00:58:51.780 align:start position:0% plugins that are most effective and the api's<00:58:50.320> that<00:58:50.530> enable<00:58:50.950> those<00:58:51.100> most<00:58:51.370> effective 00:58:51.780 --> 00:58:51.790 align:start position:0% api's that enable those most effective 00:58:51.790 --> 00:58:53.850 align:start position:0% api's that enable those most effective plugins<00:58:52.180> and<00:58:52.360> those<00:58:53.170> can<00:58:53.350> be<00:58:53.380> the<00:58:53.470> things<00:58:53.740> that 00:58:53.850 --> 00:58:53.860 align:start position:0% plugins and those can be the things that 00:58:53.860 --> 00:58:55.410 align:start position:0% plugins and those can be the things that we've<00:58:53.980> really<00:58:54.010> kind<00:58:54.340> of<00:58:54.430> focus<00:58:54.850> on<00:58:55.000> it's<00:58:55.270> like 00:58:55.410 --> 00:58:55.420 align:start position:0% we've really kind of focus on it's like 00:58:55.420 --> 00:58:59.310 align:start position:0% we've really kind of focus on it's like a<00:58:55.480> community<00:58:55.870> instead<00:58:56.440> it's<00:58:56.650> a<00:58:58.200> group<00:58:59.200> of 00:58:59.310 --> 00:58:59.320 align:start position:0% a community instead it's a group of 00:58:59.320 --> 00:59:03.450 align:start position:0% a community instead it's a group of people<00:59:00.150> so<00:59:01.150> that<00:59:01.600> that<00:59:02.260> is<00:59:02.500> all<00:59:02.740> we<00:59:03.130> have<00:59:03.310> to 00:59:03.450 --> 00:59:03.460 align:start position:0% people so that that is all we have to 00:59:03.460 --> 00:59:06.150 align:start position:0% people so that that is all we have to say<00:59:03.670> to<00:59:04.210> get<00:59:04.780> you<00:59:04.990> kind<00:59:05.380> of<00:59:05.470> started<00:59:05.860> we<00:59:06.010> hope 00:59:06.150 --> 00:59:06.160 align:start position:0% say to get you kind of started we hope 00:59:06.160 --> 00:59:19.260 align:start position:0% say to get you kind of started we hope this<00:59:06.280> is<00:59:06.430> a<00:59:06.460> big<00:59:06.730> push<00:59:06.970> on<00:59:07.270> this<00:59:18.060> you<00:59:19.060> can 00:59:19.260 --> 00:59:19.270 align:start position:0% this is a big push on this you can 00:59:19.270 --> 00:59:21.150 align:start position:0% this is a big push on this you can connect<00:59:19.600> to<00:59:19.810> the<00:59:19.870> Wi-Fi<00:59:20.080> metamath<00:59:20.740> right<00:59:21.040> now 00:59:21.150 --> 00:59:21.160 align:start position:0% connect to the Wi-Fi metamath right now 00:59:21.160 --> 00:59:22.650 align:start position:0% connect to the Wi-Fi metamath right now and<00:59:21.400> point<00:59:21.610> your<00:59:21.700> browser<00:59:21.850> to<00:59:22.060> meta<00:59:22.270> mascot 00:59:22.650 --> 00:59:22.660 align:start position:0% and point your browser to meta mascot 00:59:22.660 --> 00:59:24.600 align:start position:0% and point your browser to meta mascot local<00:59:23.020> and<00:59:23.260> you've<00:59:23.380> got<00:59:23.530> all<00:59:23.680> the<00:59:23.800> docs<00:59:24.040> and<00:59:24.340> a 00:59:24.600 --> 00:59:24.610 align:start position:0% local and you've got all the docs and a 00:59:24.610 --> 00:59:26.460 align:start position:0% local and you've got all the docs and a little<00:59:25.060> meta<00:59:25.270> mastered<00:59:25.690> supports<00:59:26.020> plugins 00:59:26.460 --> 00:59:26.470 align:start position:0% little meta mastered supports plugins 00:59:26.470 --> 00:59:28.800 align:start position:0% little meta mastered supports plugins and<00:59:26.710> the<00:59:27.250> MN<00:59:27.550> plug-in<00:59:27.940> bullets<00:59:28.180> hope<00:59:28.360> you're 00:59:28.800 --> 00:59:28.810 align:start position:0% and the MN plug-in bullets hope you're 00:59:28.810 --> 00:59:30.060 align:start position:0% and the MN plug-in bullets hope you're like<00:59:28.990> really<00:59:29.200> paranoid<00:59:29.620> about<00:59:29.740> how<00:59:29.980> this 00:59:30.060 --> 00:59:30.070 align:start position:0% like really paranoid about how this 00:59:30.070 --> 00:59:33.060 align:start position:0% like really paranoid about how this would<00:59:30.220> happen<00:59:30.490> and<00:59:31.590> yeah<00:59:32.590> other<00:59:32.830> that's 00:59:33.060 --> 00:59:33.070 align:start position:0% would happen and yeah other that's 00:59:33.070 --> 00:59:34.470 align:start position:0% would happen and yeah other that's canvas<00:59:33.580> if<00:59:33.700> you<00:59:33.790> do<00:59:33.940> have<00:59:34.060> the<00:59:34.150> Internet 00:59:34.470 --> 00:59:34.480 align:start position:0% canvas if you do have the Internet 00:59:34.480 --> 00:59:36.270 align:start position:0% canvas if you do have the Internet you'll<00:59:34.720> go<00:59:34.840> to<00:59:34.900> the<00:59:35.020> github<00:59:35.200> wiki<00:59:35.500> three<00:59:36.010> posts 00:59:36.270 --> 00:59:36.280 align:start position:0% you'll go to the github wiki three posts 00:59:36.280 --> 00:59:38.040 align:start position:0% you'll go to the github wiki three posts open<00:59:36.610> now<00:59:36.730> it's<00:59:36.970> got<00:59:37.210> a<00:59:37.240> video<00:59:37.540> that's<00:59:37.870> very 00:59:38.040 --> 00:59:38.050 align:start position:0% open now it's got a video that's very 00:59:38.050 --> 00:59:39.510 align:start position:0% open now it's got a video that's very similar<00:59:38.320> than<00:59:38.560> the<00:59:38.620> presentation<00:59:39.220> we<00:59:39.310> just 00:59:39.510 --> 00:59:39.520 align:start position:0% similar than the presentation we just 00:59:39.520 --> 00:59:41.130 align:start position:0% similar than the presentation we just made<00:59:39.700> for<00:59:39.850> the<00:59:40.060> people<00:59:40.360> outside<00:59:40.480> of<00:59:40.720> this<00:59:40.930> room 00:59:41.130 --> 00:59:41.140 align:start position:0% made for the people outside of this room 00:59:41.140 --> 00:59:44.790 align:start position:0% made for the people outside of this room can<00:59:41.350> be<00:59:41.560> learning<00:59:42.100> this<00:59:42.220> right<00:59:42.520> now<00:59:42.670> and<00:59:43.800> yeah 00:59:44.790 --> 00:59:44.800 align:start position:0% can be learning this right now and yeah 00:59:44.800 --> 00:59:46.470 align:start position:0% can be learning this right now and yeah so<00:59:45.070> what's<00:59:45.310> the<00:59:45.640> rest<00:59:45.730> of<00:59:45.850> the<00:59:45.940> time<00:59:46.090> yeah<00:59:46.330> that 00:59:46.470 --> 00:59:46.480 align:start position:0% so what's the rest of the time yeah that 00:59:46.480 --> 00:59:48.300 align:start position:0% so what's the rest of the time yeah that was<00:59:46.570> exactly<00:59:46.900> one<00:59:47.080> hour<00:59:47.230> maybe<00:59:47.800> maybe<00:59:48.220> like 00:59:48.300 --> 00:59:48.310 align:start position:0% was exactly one hour maybe maybe like 00:59:48.310 --> 00:59:50.250 align:start position:0% was exactly one hour maybe maybe like five<00:59:48.880> minutes<00:59:49.300> or<00:59:49.600> something<00:59:49.720> like<00:59:49.870> maybe 00:59:50.250 --> 00:59:50.260 align:start position:0% five minutes or something like maybe 00:59:50.260 --> 00:59:52.110 align:start position:0% five minutes or something like maybe just<00:59:50.530> like<00:59:50.650> a<00:59:50.830> few<00:59:51.040> questions<00:59:51.250> and<00:59:51.610> then<00:59:51.700> you 00:59:52.110 --> 00:59:52.120 align:start position:0% just like a few questions and then you 00:59:52.120 --> 00:59:54.150 align:start position:0% just like a few questions and then you want<00:59:52.270> us<00:59:52.330> to<00:59:52.450> start<00:59:52.660> going<00:59:52.960> in<00:59:53.050> with<00:59:53.590> our<00:59:53.710> whole 00:59:54.150 --> 00:59:54.160 align:start position:0% want us to start going in with our whole 00:59:54.160 --> 00:59:57.150 align:start position:0% want us to start going in with our whole team<00:59:54.370> full<00:59:54.820> of<00:59:55.020> mathematical<00:59:56.020> misery<00:59:56.320> I<00:59:56.650> was 00:59:57.150 --> 00:59:57.160 align:start position:0% team full of mathematical misery I was 00:59:57.160 --> 00:59:58.680 align:start position:0% team full of mathematical misery I was ready<00:59:57.340> to<00:59:57.460> answer<00:59:57.670> your<00:59:57.790> questions<00:59:58.240> actually 00:59:58.680 --> 00:59:58.690 align:start position:0% ready to answer your questions actually 00:59:58.690 --> 01:00:00.600 align:start position:0% ready to answer your questions actually over<00:59:59.080> or<00:59:59.500> you<00:59:59.650> said<00:59:59.830> you<00:59:59.980> guys<01:00:00.040> researcher<01:00:00.490> who 01:00:00.600 --> 01:00:00.610 align:start position:0% over or you said you guys researcher who 01:00:00.610 --> 01:00:02.520 align:start position:0% over or you said you guys researcher who maybe<01:00:00.850> like<01:00:01.060> to<01:00:01.180> say<01:00:01.300> a<01:00:01.330> couple<01:00:01.810> words<01:00:01.930> before 01:00:02.520 --> 01:00:02.530 align:start position:0% maybe like to say a couple words before 01:00:02.530 --> 01:00:09.400 align:start position:0% maybe like to say a couple words before you<01:00:02.590> get<01:00:02.710> started 01:00:09.400 --> 01:00:09.410 align:start position:0% 01:00:09.410 --> 01:00:12.620 align:start position:0% so<01:00:10.410> as<01:00:10.740> such<01:00:11.250> back<01:00:11.670> there<01:00:11.880> said<01:00:12.210> that<01:00:12.240> they 01:00:12.620 --> 01:00:12.630 align:start position:0% so as such back there said that they 01:00:12.630 --> 01:00:14.600 align:start position:0% so as such back there said that they have<01:00:12.840> that<01:00:13.110> ideas<01:00:13.560> and<01:00:13.800> what<01:00:13.920> I<01:00:14.130> can<01:00:14.280> say<01:00:14.430> on<01:00:14.580> a 01:00:14.600 --> 01:00:14.610 align:start position:0% have that ideas and what I can say on a 01:00:14.610 --> 01:00:16.760 align:start position:0% have that ideas and what I can say on a bit<01:00:14.820> you<01:00:15.240> wanna<01:00:15.420> listen<01:00:15.660> to<01:00:15.930> me<01:00:16.080> on<01:00:16.380> what 01:00:16.760 --> 01:00:16.770 align:start position:0% bit you wanna listen to me on what 01:00:16.770 --> 01:00:19.810 align:start position:0% bit you wanna listen to me on what against<01:00:17.190> you<01:00:17.460> and<01:00:17.640> one<01:00:17.760> of<01:00:17.790> it<01:00:18.030> and<01:00:18.270> why 01:00:19.810 --> 01:00:19.820 align:start position:0% against you and one of it and why 01:00:19.820 --> 01:00:24.290 align:start position:0% against you and one of it and why obviously<01:00:21.200> probably<01:00:22.200> talk<01:00:22.380> to<01:00:22.560> us<01:00:23.030> you<01:00:24.030> want 01:00:24.290 --> 01:00:24.300 align:start position:0% obviously probably talk to us you want 01:00:24.300 --> 01:00:26.060 align:start position:0% obviously probably talk to us you want to<01:00:24.420> hear<01:00:24.630> you<01:00:24.900> so<01:00:25.140> that<01:00:25.290> you<01:00:25.410> can<01:00:25.530> find<01:00:25.860> out 01:00:26.060 --> 01:00:26.070 align:start position:0% to hear you so that you can find out 01:00:26.070 --> 01:00:28.940 align:start position:0% to hear you so that you can find out what<01:00:26.370> the<01:00:26.580> most<01:00:26.760> effective<01:00:27.120> is<01:00:27.660> disregard<01:00:28.200> and 01:00:28.940 --> 01:00:28.950 align:start position:0% what the most effective is disregard and 01:00:28.950 --> 01:00:30.500 align:start position:0% what the most effective is disregard and what<01:00:29.160> we<01:00:29.370> should<01:00:29.550> be<01:00:29.580> building<01:00:29.790> close<01:00:30.210> to 01:00:30.500 --> 01:00:30.510 align:start position:0% what we should be building close to 01:00:30.510 --> 01:00:34.670 align:start position:0% what we should be building close to death<01:00:31.730> if<01:00:32.730> you<01:00:32.790> don't<01:00:33.240> have<01:00:33.750> an<01:00:33.870> idea<01:00:34.140> of<01:00:34.410> what 01:00:34.670 --> 01:00:34.680 align:start position:0% death if you don't have an idea of what 01:00:34.680 --> 01:00:37.040 align:start position:0% death if you don't have an idea of what in<01:00:35.250> my<01:00:35.370> credibility<01:00:36.060> but<01:00:36.630> you<01:00:36.810> can 01:00:37.040 --> 01:00:37.050 align:start position:0% in my credibility but you can 01:00:37.050 --> 01:00:38.930 align:start position:0% in my credibility but you can think<01:00:37.380> of<01:00:37.590> what<01:00:37.950> is<01:00:38.130> he<01:00:38.280> missing<01:00:38.610> in<01:00:38.790> the 01:00:38.930 --> 01:00:38.940 align:start position:0% think of what is he missing in the 01:00:38.940 --> 01:00:48.020 align:start position:0% think of what is he missing in the wallet<01:00:39.800> experience<01:00:40.800> for<01:00:40.980> users<01:00:46.610> we<01:00:47.610> also<01:00:47.760> want 01:00:48.020 --> 01:00:48.030 align:start position:0% wallet experience for users we also want 01:00:48.030 --> 01:00:50.570 align:start position:0% wallet experience for users we also want to<01:00:48.060> hear<01:00:48.540> from<01:00:48.720> you<01:00:48.930> on<01:00:49.200> what<01:00:49.470> is<01:00:49.650> a<01:00:50.040> what<01:00:50.430> in 01:00:50.570 --> 01:00:50.580 align:start position:0% to hear from you on what is a what in 01:00:50.580 --> 01:00:53.390 align:start position:0% to hear from you on what is a what in your<01:00:50.700> DNA<01:00:51.210> is<01:00:51.330> missing<01:00:51.660> from<01:00:51.780> from<01:00:52.320> the<01:00:53.130> wallet 01:00:53.390 --> 01:00:53.400 align:start position:0% your DNA is missing from from the wallet 01:00:53.400 --> 01:00:55.730 align:start position:0% your DNA is missing from from the wallet so<01:00:53.430> that<01:00:53.820> we<01:00:53.940> can<01:00:54.120> think<01:00:54.270> of<01:00:54.740> potential 01:00:55.730 --> 01:00:55.740 align:start position:0% so that we can think of potential 01:00:55.740 --> 01:00:59.480 align:start position:0% so that we can think of potential solution<01:00:56.160> for<01:00:56.310> ID<01:00:56.430> and<01:00:56.640> as<01:00:57.180> a<01:00:57.210> travel<01:00:57.720> card<01:00:58.490> and 01:00:59.480 --> 01:00:59.490 align:start position:0% solution for ID and as a travel card and 01:00:59.490 --> 01:01:01.040 align:start position:0% solution for ID and as a travel card and the<01:00:59.640> third<01:00:59.820> thing<01:01:00.030> is<01:01:00.090> if<01:01:00.420> you<01:01:00.570> can<01:01:00.690> think<01:01:00.930> of 01:01:01.040 --> 01:01:01.050 align:start position:0% the third thing is if you can think of 01:01:01.050 --> 01:01:03.010 align:start position:0% the third thing is if you can think of planet<01:01:01.410> is<01:01:01.560> an<01:01:01.770> application<01:01:02.280> that<01:01:02.610> you<01:01:02.850> might 01:01:03.010 --> 01:01:03.020 align:start position:0% planet is an application that you might 01:01:03.020 --> 01:01:06.230 align:start position:0% planet is an application that you might see<01:01:04.250> foresee<01:01:05.250> coming<01:01:05.280> with<01:01:05.790> the<01:01:05.880> system 01:01:06.230 --> 01:01:06.240 align:start position:0% see foresee coming with the system 01:01:06.240 --> 01:01:25.200 align:start position:0% see foresee coming with the system because<01:01:06.960> muttered<01:01:07.410> here<01:01:07.680> a<01:01:10.550> lot<01:01:11.550> but 01:01:25.200 --> 01:01:25.210 align:start position:0% 01:01:25.210 --> 01:01:26.930 align:start position:0% [Applause] 01:01:26.930 --> 01:01:26.940 align:start position:0% [Applause] 01:01:26.940 --> 01:01:29.359 align:start position:0% [Applause] what's<01:01:27.599> that<01:01:27.930> just<01:01:28.440> subscription 01:01:29.359 --> 01:01:29.369 align:start position:0% what's that just subscription 01:01:29.369 --> 01:01:31.670 align:start position:0% what's that just subscription subscriptions<01:01:30.319> subscriptions<01:01:31.319> like<01:01:31.500> to 01:01:31.670 --> 01:01:31.680 align:start position:0% subscriptions subscriptions like to 01:01:31.680 --> 01:01:34.279 align:start position:0% subscriptions subscriptions like to events<01:01:32.039> or<01:01:32.250> subscriptions<01:01:32.760> like<01:01:33.170> around<01:01:34.170> I 01:01:34.279 --> 01:01:34.289 align:start position:0% events or subscriptions like around I 01:01:34.289 --> 01:01:36.019 align:start position:0% events or subscriptions like around I made<01:01:34.500> it<01:01:34.619> payments<01:01:35.130> right<01:01:35.460> there<01:01:35.670> right<01:01:35.789> yeah 01:01:36.019 --> 01:01:36.029 align:start position:0% made it payments right there right yeah 01:01:36.029 --> 01:01:37.880 align:start position:0% made it payments right there right yeah yeah<01:01:36.299> but<01:01:36.599> you<01:01:37.020> should<01:01:37.200> group<01:01:37.380> up<01:01:37.529> with<01:01:37.559> this 01:01:37.880 --> 01:01:37.890 align:start position:0% yeah but you should group up with this 01:01:37.890 --> 01:01:38.990 align:start position:0% yeah but you should group up with this plugin<01:01:38.220> team<01:01:38.369> over<01:01:38.549> here<01:01:38.579> that<01:01:38.819> we're<01:01:38.910> gonna 01:01:38.990 --> 01:01:39.000 align:start position:0% plugin team over here that we're gonna 01:01:39.000 --> 01:01:40.160 align:start position:0% plugin team over here that we're gonna have<01:01:39.089> a<01:01:39.150> little<01:01:39.390> half<01:01:39.510> the<01:01:39.630> time<01:01:39.779> for<01:01:39.900> the<01:01:39.990> next 01:01:40.160 --> 01:01:40.170 align:start position:0% have a little half the time for the next 01:01:40.170 --> 01:01:40.670 align:start position:0% have a little half the time for the next hour 01:01:40.670 --> 01:01:40.680 align:start position:0% hour 01:01:40.680 --> 01:01:42.440 align:start position:0% hour groundhogs<01:01:41.279> does<01:01:41.490> subscriptions<01:01:42.059> that<01:01:42.150> I<01:01:42.299> bet 01:01:42.440 --> 01:01:42.450 align:start position:0% groundhogs does subscriptions that I bet 01:01:42.450 --> 01:01:44.120 align:start position:0% groundhogs does subscriptions that I bet you<01:01:42.539> they<01:01:42.660> can<01:01:42.809> drop<01:01:42.990> one<01:01:43.170> in<01:01:43.289> the<01:01:43.799> custom 01:01:44.120 --> 01:01:44.130 align:start position:0% you they can drop one in the custom 01:01:44.130 --> 01:01:45.440 align:start position:0% you they can drop one in the custom asset<01:01:44.250> thing<01:01:44.640> you<01:01:44.819> can<01:01:44.970> just<01:01:45.000> hack<01:01:45.270> around 01:01:45.440 --> 01:01:45.450 align:start position:0% asset thing you can just hack around 01:01:45.450 --> 01:01:47.029 align:start position:0% asset thing you can just hack around right<01:01:45.720> now<01:01:45.750> when<01:01:46.049> you<01:01:46.140> click<01:01:46.410> on<01:01:46.529> it<01:01:46.710> you<01:01:46.890> guys 01:01:47.029 --> 01:01:47.039 align:start position:0% right now when you click on it you guys 01:01:47.039 --> 01:01:48.890 align:start position:0% right now when you click on it you guys are<01:01:47.069> soaking<01:01:47.460> a<01:01:47.549> page<01:01:47.730> so<01:01:48.299> hopefully<01:01:48.720> that's 01:01:48.890 --> 01:01:48.900 align:start position:0% are soaking a page so hopefully that's 01:01:48.900 --> 01:01:50.510 align:start position:0% are soaking a page so hopefully that's announced<01:01:49.170> it<01:01:49.319> just<01:01:49.470> kind<01:01:49.650> of<01:01:49.680> like<01:01:49.859> children 01:01:50.510 --> 01:01:50.520 align:start position:0% announced it just kind of like children 01:01:50.520 --> 01:01:53.539 align:start position:0% announced it just kind of like children canto<01:01:50.940> yeah<01:01:52.279> cool 01:01:53.539 --> 01:01:53.549 align:start position:0% canto yeah cool 01:01:53.549 --> 01:01:55.940 align:start position:0% canto yeah cool yeah<01:01:54.089> baby<01:01:54.569> wanna<01:01:54.750> shout<01:01:55.020> out<01:01:55.170> plugins<01:01:55.829> that 01:01:55.940 --> 01:01:55.950 align:start position:0% yeah baby wanna shout out plugins that 01:01:55.950 --> 01:01:57.890 align:start position:0% yeah baby wanna shout out plugins that you're<01:01:56.039> hoping<01:01:56.220> to<01:01:56.400> maybe<01:01:56.760> whip<01:01:57.569> up<01:01:57.720> in<01:01:57.839> this 01:01:57.890 --> 01:01:57.900 align:start position:0% you're hoping to maybe whip up in this 01:01:57.900 --> 01:01:59.329 align:start position:0% you're hoping to maybe whip up in this next<01:01:58.079> hour<01:01:58.260> and<01:01:58.589> you<01:01:58.680> can<01:01:58.829> help<01:01:59.039> connect 01:01:59.329 --> 01:01:59.339 align:start position:0% next hour and you can help connect 01:01:59.339 --> 01:02:00.859 align:start position:0% next hour and you can help connect people<01:01:59.460> that<01:02:00.059> seems<01:02:00.240> like<01:02:00.359> a<01:02:00.390> good<01:02:00.539> use<01:02:00.660> of<01:02:00.750> my 01:02:00.859 --> 01:02:00.869 align:start position:0% people that seems like a good use of my 01:02:00.869 --> 01:02:01.099 align:start position:0% people that seems like a good use of my time 01:02:01.099 --> 01:02:01.109 align:start position:0% time 01:02:01.109 --> 01:02:50.850 align:start position:0% time yeah<01:02:01.880> any<01:02:02.880> any<01:02:03.150> other<01:02:03.210> plugins<01:02:03.690> that<01:02:03.839> people 01:02:50.850 --> 01:02:50.860 align:start position:0% 01:02:50.860 --> 01:03:29.130 align:start position:0% so<01:02:58.660> University 01:03:29.130 --> 01:03:29.140 align:start position:0% 01:03:29.140 --> 01:03:36.170 align:start position:0% [Applause] 01:03:36.170 --> 01:03:36.180 align:start position:0% 01:03:36.180 --> 01:03:38.240 align:start position:0% you