WEBVTT Kind: captions Language: en 00:00:09.150 --> 00:00:14.509 align:start position:0% [Music] 00:00:14.509 --> 00:00:14.519 align:start position:0% [Music] 00:00:14.519 --> 00:00:16.170 align:start position:0% [Music] very<00:00:15.519> good 00:00:16.170 --> 00:00:16.180 align:start position:0% very good 00:00:16.180 --> 00:00:19.259 align:start position:0% very good hello<00:00:16.630> I'm<00:00:16.960> kuma<00:00:17.619> vez<00:00:17.769> from<00:00:18.340> Metta<00:00:18.609> mask<00:00:18.880> and 00:00:19.259 --> 00:00:19.269 align:start position:0% hello I'm kuma vez from Metta mask and 00:00:19.269 --> 00:00:24.060 align:start position:0% hello I'm kuma vez from Metta mask and today<00:00:20.230> we<00:00:20.590> will<00:00:20.769> be<00:00:20.849> dissecting<00:00:21.849> the<00:00:22.060> Fox<00:00:23.070> its 00:00:24.060 --> 00:00:24.070 align:start position:0% today we will be dissecting the Fox its 00:00:24.070 --> 00:00:27.089 align:start position:0% today we will be dissecting the Fox its are<00:00:24.609> there<00:00:25.060> any<00:00:25.240> meta<00:00:25.900> masks<00:00:26.109> users<00:00:26.560> out<00:00:26.769> there 00:00:27.089 --> 00:00:27.099 align:start position:0% are there any meta masks users out there 00:00:27.099 --> 00:00:32.850 align:start position:0% are there any meta masks users out there does<00:00:27.820> anyone<00:00:28.029> have<00:00:28.179> it<00:00:28.380> wow<00:00:29.380> that's<00:00:30.189> amazing 00:00:32.850 --> 00:00:32.860 align:start position:0% 00:00:32.860 --> 00:00:35.190 align:start position:0% so<00:00:33.220> yeah<00:00:33.430> we'll<00:00:33.610> be<00:00:33.789> looking<00:00:34.059> at<00:00:34.360> its<00:00:34.660> parts 00:00:35.190 --> 00:00:35.200 align:start position:0% so yeah we'll be looking at its parts 00:00:35.200 --> 00:00:38.000 align:start position:0% so yeah we'll be looking at its parts and<00:00:35.440> pieces<00:00:35.739> and<00:00:36.219> figure<00:00:36.579> out<00:00:36.640> how<00:00:37.000> it<00:00:37.030> ticks 00:00:38.000 --> 00:00:38.010 align:start position:0% and pieces and figure out how it ticks 00:00:38.010 --> 00:00:40.860 align:start position:0% and pieces and figure out how it ticks to<00:00:39.010> begin<00:00:39.250> let's<00:00:40.090> take<00:00:40.300> a<00:00:40.329> look<00:00:40.480> at<00:00:40.570> the<00:00:40.660> eyes 00:00:40.860 --> 00:00:40.870 align:start position:0% to begin let's take a look at the eyes 00:00:40.870 --> 00:00:43.970 align:start position:0% to begin let's take a look at the eyes in<00:00:41.379> the<00:00:41.469> brain<00:00:41.770> what<00:00:42.250> we<00:00:42.340> see<00:00:42.550> what<00:00:42.850> we<00:00:42.910> know 00:00:43.970 --> 00:00:43.980 align:start position:0% in the brain what we see what we know 00:00:43.980 --> 00:00:46.200 align:start position:0% in the brain what we see what we know first<00:00:44.980> of<00:00:45.100> all<00:00:45.160> we<00:00:45.280> know<00:00:45.399> we<00:00:45.610> must<00:00:45.969> be<00:00:46.120> doing 00:00:46.200 --> 00:00:46.210 align:start position:0% first of all we know we must be doing 00:00:46.210 --> 00:00:48.349 align:start position:0% first of all we know we must be doing something<00:00:46.329> right<00:00:46.780> we<00:00:47.710> have<00:00:47.829> just<00:00:48.010> shy<00:00:48.190> of 00:00:48.349 --> 00:00:48.359 align:start position:0% something right we have just shy of 00:00:48.359 --> 00:00:51.450 align:start position:0% something right we have just shy of 200,000<00:00:49.359> users<00:00:49.510> and<00:00:50.020> growing<00:00:50.770> at<00:00:51.160> quite<00:00:51.430> a 00:00:51.450 --> 00:00:51.460 align:start position:0% 200,000 users and growing at quite a 00:00:51.460 --> 00:00:57.360 align:start position:0% 200,000 users and growing at quite a pace<00:00:53.579> we're<00:00:54.579> in<00:00:54.730> Chrome<00:00:55.210> Firefox<00:00:55.960> Opera<00:00:56.800> and 00:00:57.360 --> 00:00:57.370 align:start position:0% pace we're in Chrome Firefox Opera and 00:00:57.370 --> 00:01:03.180 align:start position:0% pace we're in Chrome Firefox Opera and recently<00:00:58.210> brave<00:01:00.420> not<00:01:01.420> in<00:01:01.660> Safari<00:01:02.289> they<00:01:02.769> have 00:01:03.180 --> 00:01:03.190 align:start position:0% recently brave not in Safari they have 00:01:03.190 --> 00:01:05.280 align:start position:0% recently brave not in Safari they have not<00:01:03.489> adopted<00:01:04.030> the<00:01:04.150> standards<00:01:04.629> that<00:01:04.750> we<00:01:04.960> rely 00:01:05.280 --> 00:01:05.290 align:start position:0% not adopted the standards that we rely 00:01:05.290 --> 00:01:08.310 align:start position:0% not adopted the standards that we rely on<00:01:05.350> they<00:01:05.950> like<00:01:06.220> to<00:01:06.450> think<00:01:07.450> differently<00:01:07.840> over 00:01:08.310 --> 00:01:08.320 align:start position:0% on they like to think differently over 00:01:08.320 --> 00:01:11.190 align:start position:0% on they like to think differently over there 00:01:11.190 --> 00:01:11.200 align:start position:0% 00:01:11.200 --> 00:01:13.469 align:start position:0% more<00:01:11.530> on<00:01:11.650> brave<00:01:11.920> not<00:01:12.189> just<00:01:12.430> brave<00:01:12.729> support<00:01:13.270> but 00:01:13.469 --> 00:01:13.479 align:start position:0% more on brave not just brave support but 00:01:13.479 --> 00:01:16.289 align:start position:0% more on brave not just brave support but actually<00:01:13.810> brave<00:01:14.560> integration<00:01:15.340> if<00:01:15.850> you<00:01:16.090> go<00:01:16.240> to 00:01:16.289 --> 00:01:16.299 align:start position:0% actually brave integration if you go to 00:01:16.299 --> 00:01:19.170 align:start position:0% actually brave integration if you go to a<00:01:16.390> web<00:01:16.659> 3<00:01:16.960> enabled<00:01:17.380> app<00:01:17.619> in<00:01:17.890> brave<00:01:18.250> it'll<00:01:19.000> bring 00:01:19.170 --> 00:01:19.180 align:start position:0% a web 3 enabled app in brave it'll bring 00:01:19.180 --> 00:01:21.960 align:start position:0% a web 3 enabled app in brave it'll bring up<00:01:19.360> that<00:01:19.509> bar<00:01:20.229> at<00:01:20.409> the<00:01:20.530> top<00:01:20.850> recommending<00:01:21.850> that 00:01:21.960 --> 00:01:21.970 align:start position:0% up that bar at the top recommending that 00:01:21.970 --> 00:01:24.030 align:start position:0% up that bar at the top recommending that you<00:01:22.119> install<00:01:22.570> meta<00:01:22.810> mask<00:01:23.049> in<00:01:23.350> order<00:01:23.590> to<00:01:23.890> use 00:01:24.030 --> 00:01:24.040 align:start position:0% you install meta mask in order to use 00:01:24.040 --> 00:01:26.340 align:start position:0% you install meta mask in order to use etherium<00:01:24.520> applications<00:01:25.119> for<00:01:25.930> all<00:01:26.079> brave 00:01:26.340 --> 00:01:26.350 align:start position:0% etherium applications for all brave 00:01:26.350 --> 00:01:32.540 align:start position:0% etherium applications for all brave users<00:01:26.740> this<00:01:27.250> is<00:01:27.340> fantastic 00:01:32.540 --> 00:01:32.550 align:start position:0% 00:01:32.550 --> 00:01:34.380 align:start position:0% [Applause] 00:01:34.380 --> 00:01:34.390 align:start position:0% [Applause] 00:01:34.390 --> 00:01:38.470 align:start position:0% [Applause] some<00:01:35.390> other<00:01:35.540> statistics<00:01:37.330> despite<00:01:38.330> its 00:01:38.470 --> 00:01:38.480 align:start position:0% some other statistics despite its 00:01:38.480 --> 00:01:40.990 align:start position:0% some other statistics despite its popularity<00:01:39.160> minimus<00:01:40.160> still<00:01:40.400> represents 00:01:40.990 --> 00:01:41.000 align:start position:0% popularity minimus still represents 00:01:41.000 --> 00:01:43.720 align:start position:0% popularity minimus still represents about<00:01:41.120> 5%<00:01:41.840> of<00:01:42.500> the<00:01:42.710> transactions<00:01:43.550> on<00:01:43.700> the 00:01:43.720 --> 00:01:43.730 align:start position:0% about 5% of the transactions on the 00:01:43.730 --> 00:01:46.030 align:start position:0% about 5% of the transactions on the network<00:01:44.030> by<00:01:44.480> volume<00:01:44.810> we<00:01:45.470> had<00:01:45.590> a<00:01:45.620> peak<00:01:45.860> at<00:01:46.010> about 00:01:46.030 --> 00:01:46.040 align:start position:0% network by volume we had a peak at about 00:01:46.040 --> 00:01:49.510 align:start position:0% network by volume we had a peak at about 10%<00:01:46.730> and<00:01:47.270> I<00:01:47.840> think<00:01:48.110> the<00:01:48.350> the<00:01:48.920> other<00:01:49.070> wallets 00:01:49.510 --> 00:01:49.520 align:start position:0% 10% and I think the the other wallets 00:01:49.520 --> 00:01:51.760 align:start position:0% 10% and I think the the other wallets are<00:01:49.880> about<00:01:50.210> the<00:01:50.360> same<00:01:50.570> maybe<00:01:50.810> Meuse<00:01:51.320> a<00:01:51.350> little 00:01:51.760 --> 00:01:51.770 align:start position:0% are about the same maybe Meuse a little 00:01:51.770 --> 00:01:54.910 align:start position:0% are about the same maybe Meuse a little more<00:01:51.980> but<00:01:52.940> there's<00:01:53.300> clearly<00:01:53.570> a<00:01:54.110> large<00:01:54.590> amount 00:01:54.910 --> 00:01:54.920 align:start position:0% more but there's clearly a large amount 00:01:54.920 --> 00:01:56.440 align:start position:0% more but there's clearly a large amount of<00:01:54.980> activity<00:01:55.430> on<00:01:55.520> the<00:01:55.550> blockchain<00:01:55.820> that<00:01:56.210> must 00:01:56.440 --> 00:01:56.450 align:start position:0% of activity on the blockchain that must 00:01:56.450 --> 00:02:00.010 align:start position:0% of activity on the blockchain that must be<00:01:56.540> automated<00:01:57.500> perhaps<00:01:58.070> exchanges<00:01:58.940> or<00:01:59.720> mining 00:02:00.010 --> 00:02:00.020 align:start position:0% be automated perhaps exchanges or mining 00:02:00.020 --> 00:02:02.410 align:start position:0% be automated perhaps exchanges or mining pools<00:02:00.260> I'd<00:02:01.100> love<00:02:01.310> to<00:02:01.430> hear<00:02:01.670> if<00:02:01.910> anyone's<00:02:02.240> done 00:02:02.410 --> 00:02:02.420 align:start position:0% pools I'd love to hear if anyone's done 00:02:02.420 --> 00:02:06.700 align:start position:0% pools I'd love to hear if anyone's done some<00:02:02.630> data<00:02:02.840> analysis<00:02:03.410> there<00:02:05.410> in<00:02:06.410> the<00:02:06.500> past 00:02:06.700 --> 00:02:06.710 align:start position:0% some data analysis there in the past 00:02:06.710 --> 00:02:08.889 align:start position:0% some data analysis there in the past year<00:02:06.950> there's<00:02:07.130> been<00:02:07.190> some<00:02:07.520> fantastic<00:02:08.030> gaps 00:02:08.889 --> 00:02:08.899 align:start position:0% year there's been some fantastic gaps 00:02:08.899 --> 00:02:10.389 align:start position:0% year there's been some fantastic gaps that<00:02:09.170> have<00:02:09.230> come<00:02:09.440> out<00:02:09.560> that<00:02:09.770> play<00:02:10.190> well<00:02:10.340> with 00:02:10.389 --> 00:02:10.399 align:start position:0% that have come out that play well with 00:02:10.399 --> 00:02:12.940 align:start position:0% that have come out that play well with meta<00:02:10.610> masks<00:02:10.820> the<00:02:11.690> new<00:02:11.870> state<00:02:12.500> of<00:02:12.620> the<00:02:12.710> DAPs 00:02:12.940 --> 00:02:12.950 align:start position:0% meta masks the new state of the DAPs 00:02:12.950 --> 00:02:14.740 align:start position:0% meta masks the new state of the DAPs website<00:02:13.700> is<00:02:13.880> fantastic 00:02:14.740 --> 00:02:14.750 align:start position:0% website is fantastic 00:02:14.750 --> 00:02:17.560 align:start position:0% website is fantastic and<00:02:14.840> you<00:02:15.380> can<00:02:15.530> even<00:02:15.650> search<00:02:16.190> by<00:02:16.730> meta<00:02:17.360> mask 00:02:17.560 --> 00:02:17.570 align:start position:0% and you can even search by meta mask 00:02:17.570 --> 00:02:20.170 align:start position:0% and you can even search by meta mask compliant<00:02:18.230> apps<00:02:18.410> by<00:02:19.370> just<00:02:19.670> adding<00:02:19.850> the<00:02:20.000> meta 00:02:20.170 --> 00:02:20.180 align:start position:0% compliant apps by just adding the meta 00:02:20.180 --> 00:02:23.290 align:start position:0% compliant apps by just adding the meta mask<00:02:20.390> filter<00:02:20.630> I<00:02:21.940> encourage<00:02:22.940> you<00:02:23.030> to<00:02:23.150> check 00:02:23.290 --> 00:02:23.300 align:start position:0% mask filter I encourage you to check 00:02:23.300 --> 00:02:28.270 align:start position:0% mask filter I encourage you to check that<00:02:23.360> out<00:02:25.090> to<00:02:26.090> sort<00:02:26.390> of<00:02:26.480> gauge<00:02:26.840> what<00:02:27.770> is<00:02:27.950> the 00:02:28.270 --> 00:02:28.280 align:start position:0% that out to sort of gauge what is the 00:02:28.280 --> 00:02:31.420 align:start position:0% that out to sort of gauge what is the most<00:02:28.610> popular<00:02:28.880> daps<00:02:29.390> right<00:02:29.690> now<00:02:30.100> we<00:02:31.100> have<00:02:31.250> some 00:02:31.420 --> 00:02:31.430 align:start position:0% most popular daps right now we have some 00:02:31.430 --> 00:02:33.240 align:start position:0% most popular daps right now we have some data<00:02:31.610> from<00:02:32.150> in<00:02:32.330> fura 00:02:33.240 --> 00:02:33.250 align:start position:0% data from in fura 00:02:33.250 --> 00:02:37.210 align:start position:0% data from in fura in<00:02:34.250> first<00:02:34.700> place<00:02:34.850> is<00:02:35.210> ether<00:02:35.870> Delta<00:02:36.230> and<00:02:36.500> second 00:02:37.210 --> 00:02:37.220 align:start position:0% in first place is ether Delta and second 00:02:37.220 --> 00:02:39.510 align:start position:0% in first place is ether Delta and second is<00:02:37.340> Oasis<00:02:37.880> Dex<00:02:38.150> both<00:02:38.750> token<00:02:39.170> exchanges 00:02:39.510 --> 00:02:39.520 align:start position:0% is Oasis Dex both token exchanges 00:02:39.520 --> 00:02:42.190 align:start position:0% is Oasis Dex both token exchanges obviously<00:02:40.520> tokens<00:02:40.880> have<00:02:41.030> been<00:02:41.360> very<00:02:41.660> popular 00:02:42.190 --> 00:02:42.200 align:start position:0% obviously tokens have been very popular 00:02:42.200 --> 00:02:44.680 align:start position:0% obviously tokens have been very popular so<00:02:42.410> no<00:02:42.560> surprise<00:02:42.890> there<00:02:43.130> in<00:02:43.940> third<00:02:44.209> place<00:02:44.390> is 00:02:44.680 --> 00:02:44.690 align:start position:0% so no surprise there in third place is 00:02:44.690 --> 00:02:47.890 align:start position:0% so no surprise there in third place is meta<00:02:45.380> mask<00:02:45.590> itself<00:02:45.950> we're<00:02:46.640> a<00:02:46.670> bit<00:02:47.150> noisy<00:02:47.330> and 00:02:47.890 --> 00:02:47.900 align:start position:0% meta mask itself we're a bit noisy and 00:02:47.900 --> 00:02:49.810 align:start position:0% meta mask itself we're a bit noisy and we<00:02:48.140> are<00:02:48.770> constantly<00:02:49.040> tracking<00:02:49.640> the<00:02:49.730> latest 00:02:49.810 --> 00:02:49.820 align:start position:0% we are constantly tracking the latest 00:02:49.820 --> 00:02:52.080 align:start position:0% we are constantly tracking the latest block<00:02:50.209> updating<00:02:50.720> balances<00:02:51.110> and<00:02:51.260> whatnot 00:02:52.080 --> 00:02:52.090 align:start position:0% block updating balances and whatnot 00:02:52.090 --> 00:02:56.140 align:start position:0% block updating balances and whatnot after<00:02:53.090> that<00:02:53.239> is<00:02:53.390> the<00:02:54.200> ENS<00:02:54.680> register<00:02:55.459> ENS<00:02:55.970> was<00:02:56.120> a 00:02:56.140 --> 00:02:56.150 align:start position:0% after that is the ENS register ENS was a 00:02:56.150 --> 00:02:58.960 align:start position:0% after that is the ENS register ENS was a big<00:02:56.360> hit<00:02:56.510> this<00:02:56.630> year<00:02:57.340> after<00:02:58.340> that<00:02:58.580> we<00:02:58.850> got 00:02:58.960 --> 00:02:58.970 align:start position:0% big hit this year after that we got 00:02:58.970 --> 00:03:01.000 align:start position:0% big hit this year after that we got token<00:02:59.360> factory<00:02:59.780> token<00:03:00.380> factories<00:03:00.739> a<00:03:00.769> nice 00:03:01.000 --> 00:03:01.010 align:start position:0% token factory token factories a nice 00:03:01.010 --> 00:03:03.130 align:start position:0% token factory token factories a nice little<00:03:01.220> demoed<00:03:01.580> app<00:03:01.760> you<00:03:02.300> can<00:03:02.390> create<00:03:02.570> a<00:03:02.690> token 00:03:03.130 --> 00:03:03.140 align:start position:0% little demoed app you can create a token 00:03:03.140 --> 00:03:05.710 align:start position:0% little demoed app you can create a token sending<00:03:03.860> it<00:03:03.950> around<00:03:04.010> clearly<00:03:04.610> we<00:03:04.760> have<00:03:04.940> lots 00:03:05.710 --> 00:03:05.720 align:start position:0% sending it around clearly we have lots 00:03:05.720 --> 00:03:07.960 align:start position:0% sending it around clearly we have lots of<00:03:05.870> people<00:03:06.290> experimenting<00:03:07.190> with<00:03:07.459> aetherium 00:03:07.960 --> 00:03:07.970 align:start position:0% of people experimenting with aetherium 00:03:07.970 --> 00:03:10.710 align:start position:0% of people experimenting with aetherium trying<00:03:08.540> to<00:03:08.600> get<00:03:08.720> an<00:03:08.780> idea<00:03:09.019> of<00:03:09.080> how<00:03:09.590> to<00:03:09.650> use<00:03:09.769> it 00:03:10.710 --> 00:03:10.720 align:start position:0% trying to get an idea of how to use it 00:03:10.720 --> 00:03:13.960 align:start position:0% trying to get an idea of how to use it after<00:03:11.720> that<00:03:12.110> there's<00:03:12.410> the<00:03:12.620> sigh<00:03:12.950> the<00:03:13.489> simple 00:03:13.960 --> 00:03:13.970 align:start position:0% after that there's the sigh the simple 00:03:13.970 --> 00:03:17.830 align:start position:0% after that there's the sigh the simple stable<00:03:14.300> token<00:03:14.750> experiment<00:03:15.290> and<00:03:16.420> the<00:03:17.420> wallet 00:03:17.830 --> 00:03:17.840 align:start position:0% stable token experiment and the wallet 00:03:17.840 --> 00:03:20.110 align:start position:0% stable token experiment and the wallet da<00:03:17.959> theorem<00:03:18.410> gorg<00:03:18.739> this<00:03:19.040> is<00:03:19.190> actually<00:03:19.760> the 00:03:20.110 --> 00:03:20.120 align:start position:0% da theorem gorg this is actually the 00:03:20.120 --> 00:03:22.330 align:start position:0% da theorem gorg this is actually the official<00:03:20.390> aetherium<00:03:21.140> wallet<00:03:21.500> interface<00:03:22.100> and 00:03:22.330 --> 00:03:22.340 align:start position:0% official aetherium wallet interface and 00:03:22.340 --> 00:03:24.070 align:start position:0% official aetherium wallet interface and you<00:03:22.430> can<00:03:22.459> visit<00:03:22.850> that<00:03:22.880> in<00:03:23.239> your<00:03:23.959> regular 00:03:24.070 --> 00:03:24.080 align:start position:0% you can visit that in your regular 00:03:24.080 --> 00:03:29.080 align:start position:0% you can visit that in your regular browser<00:03:24.440> with<00:03:24.860> minim<00:03:25.130> ask<00:03:25.280> and<00:03:25.880> it<00:03:25.970> works<00:03:28.090> then 00:03:29.080 --> 00:03:29.090 align:start position:0% browser with minim ask and it works then 00:03:29.090 --> 00:03:31.630 align:start position:0% browser with minim ask and it works then a<00:03:29.120> long<00:03:29.330> tail<00:03:29.600> of<00:03:29.630> various<00:03:30.410> other<00:03:31.100> projects 00:03:31.630 --> 00:03:31.640 align:start position:0% a long tail of various other projects 00:03:31.640 --> 00:03:33.570 align:start position:0% a long tail of various other projects and<00:03:31.760> experiments<00:03:32.030> out<00:03:32.300> there<00:03:32.480> and<00:03:32.660> including 00:03:33.570 --> 00:03:33.580 align:start position:0% and experiments out there and including 00:03:33.580 --> 00:03:37.120 align:start position:0% and experiments out there and including 127<00:03:34.580> 0.1<00:03:35.420> obviously<00:03:36.230> many<00:03:36.410> developers<00:03:36.920> out 00:03:37.120 --> 00:03:37.130 align:start position:0% 127 0.1 obviously many developers out 00:03:37.130 --> 00:03:40.780 align:start position:0% 127 0.1 obviously many developers out there<00:03:37.160> cranking<00:03:38.060> away<00:03:39.400> we<00:03:40.400> also<00:03:40.550> had<00:03:40.760> a 00:03:40.780 --> 00:03:40.790 align:start position:0% there cranking away we also had a 00:03:40.790 --> 00:03:44.500 align:start position:0% there cranking away we also had a successful<00:03:41.170> security<00:03:42.170> audit<00:03:42.500> this<00:03:43.190> year<00:03:43.510> they 00:03:44.500 --> 00:03:44.510 align:start position:0% successful security audit this year they 00:03:44.510 --> 00:03:45.550 align:start position:0% successful security audit this year they said<00:03:44.750> in 00:03:45.550 --> 00:03:45.560 align:start position:0% said in 00:03:45.560 --> 00:03:47.710 align:start position:0% said in some<00:03:45.770> the<00:03:46.280> meta<00:03:46.459> mask<00:03:46.670> project<00:03:47.180> should<00:03:47.660> be 00:03:47.710 --> 00:03:47.720 align:start position:0% some the meta mask project should be 00:03:47.720 --> 00:03:50.650 align:start position:0% some the meta mask project should be considered<00:03:48.319> safe<00:03:48.650> and<00:03:49.010> secure<00:03:49.610> and<00:03:50.150> that's 00:03:50.650 --> 00:03:50.660 align:start position:0% considered safe and secure and that's 00:03:50.660 --> 00:03:54.550 align:start position:0% considered safe and secure and that's great<00:03:52.239> to<00:03:53.239> keep<00:03:53.420> up<00:03:53.569> with<00:03:53.720> the<00:03:53.900> rapid<00:03:54.319> growth 00:03:54.550 --> 00:03:54.560 align:start position:0% great to keep up with the rapid growth 00:03:54.560 --> 00:03:58.660 align:start position:0% great to keep up with the rapid growth our<00:03:54.860> team<00:03:55.130> has<00:03:55.520> grown<00:03:55.760> from<00:03:56.000> four<00:03:56.780> to<00:03:56.810> ten<00:03:57.670> much 00:03:58.660 --> 00:03:58.670 align:start position:0% our team has grown from four to ten much 00:03:58.670 --> 00:04:01.630 align:start position:0% our team has grown from four to ten much thanks<00:03:58.940> to<00:03:58.970> the<00:03:59.480> design<00:03:59.959> by<00:04:00.230> Christian<00:04:00.770> he<00:04:01.250> did 00:04:01.630 --> 00:04:01.640 align:start position:0% thanks to the design by Christian he did 00:04:01.640 --> 00:04:05.080 align:start position:0% thanks to the design by Christian he did the<00:04:01.760> original<00:04:02.269> logo<00:04:03.610> Thomas<00:04:04.610> has<00:04:04.760> helped<00:04:05.000> us 00:04:05.080 --> 00:04:05.090 align:start position:0% the original logo Thomas has helped us 00:04:05.090 --> 00:04:07.570 align:start position:0% the original logo Thomas has helped us out<00:04:05.209> with<00:04:05.269> testing<00:04:05.750> and<00:04:05.870> James<00:04:06.709> has<00:04:07.069> really 00:04:07.570 --> 00:04:07.580 align:start position:0% out with testing and James has really 00:04:07.580 --> 00:04:10.030 align:start position:0% out with testing and James has really saved<00:04:07.849> us<00:04:08.030> doing<00:04:08.360> support<00:04:08.830> answering<00:04:09.830> user 00:04:10.030 --> 00:04:10.040 align:start position:0% saved us doing support answering user 00:04:10.040 --> 00:04:12.370 align:start position:0% saved us doing support answering user questions<00:04:10.340> if<00:04:11.060> you<00:04:11.150> send<00:04:11.390> us<00:04:11.450> an<00:04:11.599> email<00:04:11.750> he's 00:04:12.370 --> 00:04:12.380 align:start position:0% questions if you send us an email he's 00:04:12.380 --> 00:04:13.240 align:start position:0% questions if you send us an email he's who<00:04:12.500> you're<00:04:12.650> talking<00:04:12.890> to 00:04:13.240 --> 00:04:13.250 align:start position:0% who you're talking to 00:04:13.250 --> 00:04:16.270 align:start position:0% who you're talking to also<00:04:14.060> the<00:04:14.330> the<00:04:14.630> Kaioken<00:04:15.019> team<00:04:15.260> has<00:04:15.890> helped<00:04:16.220> us 00:04:16.270 --> 00:04:16.280 align:start position:0% also the the Kaioken team has helped us 00:04:16.280 --> 00:04:20.229 align:start position:0% also the the Kaioken team has helped us out<00:04:16.430> very<00:04:16.730> much<00:04:16.790> with<00:04:17.600> a<00:04:17.840> new<00:04:18.970> look<00:04:19.970> and<00:04:20.180> feel 00:04:20.229 --> 00:04:20.239 align:start position:0% out very much with a new look and feel 00:04:20.239 --> 00:04:23.830 align:start position:0% out very much with a new look and feel and<00:04:20.750> I<00:04:21.500> have<00:04:21.709> to<00:04:21.859> thank<00:04:22.010> consensus<00:04:22.790> for<00:04:23.360> for 00:04:23.830 --> 00:04:23.840 align:start position:0% and I have to thank consensus for for 00:04:23.840 --> 00:04:28.540 align:start position:0% and I have to thank consensus for for making<00:04:24.080> this<00:04:24.200> possible<00:04:26.650> so<00:04:27.650> yes<00:04:27.830> let's<00:04:28.310> take<00:04:28.490> a 00:04:28.540 --> 00:04:28.550 align:start position:0% making this possible so yes let's take a 00:04:28.550 --> 00:04:31.810 align:start position:0% making this possible so yes let's take a look<00:04:28.729> at<00:04:28.850> the<00:04:29.000> fur<00:04:29.720> and<00:04:30.169> skin<00:04:30.229> the<00:04:30.950> look<00:04:31.639> and 00:04:31.810 --> 00:04:31.820 align:start position:0% look at the fur and skin the look and 00:04:31.820 --> 00:04:35.050 align:start position:0% look at the fur and skin the look and feel<00:04:32.120> of<00:04:32.180> men<00:04:32.660> of<00:04:32.750> Oz<00:04:32.870> next<00:04:33.380> and<00:04:33.860> for<00:04:34.580> that<00:04:34.729> I 00:04:35.050 --> 00:04:35.060 align:start position:0% feel of men of Oz next and for that I 00:04:35.060 --> 00:04:38.980 align:start position:0% feel of men of Oz next and for that I bring<00:04:35.840> on<00:04:35.990> Dan<00:04:36.680> from<00:04:37.040> the<00:04:37.130> Kaioken<00:04:37.490> team<00:04:37.990> also 00:04:38.980 --> 00:04:38.990 align:start position:0% bring on Dan from the Kaioken team also 00:04:38.990 --> 00:04:47.119 align:start position:0% bring on Dan from the Kaioken team also known<00:04:39.200> as<00:04:39.260> Dino<00:04:39.680> Dan 00:04:47.119 --> 00:04:47.129 align:start position:0% 00:04:47.129 --> 00:04:55.469 align:start position:0% okay<00:04:48.780> yeah<00:04:50.729> what's<00:04:51.729> up<00:04:52.080> I'm<00:04:53.080> Dan<00:04:53.469> I<00:04:53.849> am<00:04:54.849> part<00:04:55.419> of 00:04:55.469 --> 00:04:55.479 align:start position:0% okay yeah what's up I'm Dan I am part of 00:04:55.479 --> 00:04:59.730 align:start position:0% okay yeah what's up I'm Dan I am part of the<00:04:55.689> Q<00:04:55.900> can<00:04:56.080> team<00:04:56.259> we<00:04:56.680> do<00:04:57.389> apps<00:04:58.389> and<00:04:58.870> interfaces 00:04:59.730 --> 00:04:59.740 align:start position:0% the Q can team we do apps and interfaces 00:04:59.740 --> 00:05:01.589 align:start position:0% the Q can team we do apps and interfaces for<00:05:00.039> blockchain<00:05:00.550> companies<00:05:00.879> you<00:05:01.090> can<00:05:01.240> find<00:05:01.449> us 00:05:01.589 --> 00:05:01.599 align:start position:0% for blockchain companies you can find us 00:05:01.599 --> 00:05:05.610 align:start position:0% for blockchain companies you can find us at<00:05:01.750> Keo<00:05:01.930> Kent<00:05:02.110> at<00:05:02.229> i/o<00:05:02.349> I<00:05:04.349> will<00:05:05.349> talk<00:05:05.469> about 00:05:05.610 --> 00:05:05.620 align:start position:0% at Keo Kent at i/o I will talk about 00:05:05.620 --> 00:05:08.730 align:start position:0% at Keo Kent at i/o I will talk about version<00:05:06.550> 4<00:05:06.789> of<00:05:07.030> meta<00:05:07.240> mask<00:05:07.419> the<00:05:07.750> new<00:05:07.870> UI<00:05:08.080> some 00:05:08.730 --> 00:05:08.740 align:start position:0% version 4 of meta mask the new UI some 00:05:08.740 --> 00:05:11.580 align:start position:0% version 4 of meta mask the new UI some token<00:05:08.979> management<00:05:09.370> features<00:05:09.639> and<00:05:10.349> our<00:05:11.349> anni 00:05:11.580 --> 00:05:11.590 align:start position:0% token management features and our anni 00:05:11.590 --> 00:05:13.589 align:start position:0% token management features and our anni responsive<00:05:12.039> way<00:05:12.129> out<00:05:12.280> with<00:05:12.610> multiple<00:05:13.419> form 00:05:13.589 --> 00:05:13.599 align:start position:0% responsive way out with multiple form 00:05:13.599 --> 00:05:18.629 align:start position:0% responsive way out with multiple form factors<00:05:16.620> so<00:05:17.620> that<00:05:17.740> as<00:05:17.889> you<00:05:17.979> can<00:05:18.129> see<00:05:18.280> the<00:05:18.520> new 00:05:18.629 --> 00:05:18.639 align:start position:0% factors so that as you can see the new 00:05:18.639 --> 00:05:20.969 align:start position:0% factors so that as you can see the new UI<00:05:18.819> here<00:05:19.180> is<00:05:19.330> completely<00:05:19.719> redesigned<00:05:19.979> shout 00:05:20.969 --> 00:05:20.979 align:start position:0% UI here is completely redesigned shout 00:05:20.979 --> 00:05:22.499 align:start position:0% UI here is completely redesigned shout out<00:05:21.099> again<00:05:21.340> to<00:05:21.520> Christian<00:05:21.849> for<00:05:22.210> some<00:05:22.330> great 00:05:22.499 --> 00:05:22.509 align:start position:0% out again to Christian for some great 00:05:22.509 --> 00:05:25.230 align:start position:0% out again to Christian for some great work<00:05:22.740> it<00:05:23.740> looks<00:05:23.979> a<00:05:24.250> lot<00:05:24.370> better<00:05:24.430> and<00:05:24.819> it's 00:05:25.230 --> 00:05:25.240 align:start position:0% work it looks a lot better and it's 00:05:25.240 --> 00:05:26.580 align:start position:0% work it looks a lot better and it's quite<00:05:25.419> a<00:05:25.449> bit<00:05:25.599> easier<00:05:25.689> to<00:05:25.870> use<00:05:26.110> we<00:05:26.289> hope<00:05:26.439> you 00:05:26.580 --> 00:05:26.590 align:start position:0% quite a bit easier to use we hope you 00:05:26.590 --> 00:05:27.059 align:start position:0% quite a bit easier to use we hope you like<00:05:26.770> it 00:05:27.059 --> 00:05:27.069 align:start position:0% like it 00:05:27.069 --> 00:05:29.610 align:start position:0% like it look<00:05:27.699> out<00:05:27.849> for<00:05:28.240> the<00:05:28.810> rollout<00:05:29.020> in<00:05:29.349> the<00:05:29.439> next 00:05:29.610 --> 00:05:29.620 align:start position:0% look out for the rollout in the next 00:05:29.620 --> 00:05:31.200 align:start position:0% look out for the rollout in the next couple<00:05:29.860> of<00:05:29.919> weeks<00:05:29.979> on<00:05:30.370> the<00:05:30.580> chrome<00:05:30.759> store<00:05:30.849> and 00:05:31.200 --> 00:05:31.210 align:start position:0% couple of weeks on the chrome store and 00:05:31.210 --> 00:05:42.119 align:start position:0% couple of weeks on the chrome store and several<00:05:31.689> other<00:05:31.810> browsers<00:05:40.740> next<00:05:41.740> up<00:05:41.860> is<00:05:41.979> ad 00:05:42.119 --> 00:05:42.129 align:start position:0% several other browsers next up is ad 00:05:42.129 --> 00:05:43.980 align:start position:0% several other browsers next up is ad token<00:05:42.550> which<00:05:42.909> is<00:05:43.029> a<00:05:43.060> feature<00:05:43.270> that<00:05:43.419> we've 00:05:43.980 --> 00:05:43.990 align:start position:0% token which is a feature that we've 00:05:43.990 --> 00:05:46.320 align:start position:0% token which is a feature that we've cleaned<00:05:44.529> up<00:05:44.650> a<00:05:44.740> lot<00:05:44.860> as<00:05:45.250> you<00:05:45.340> can<00:05:45.520> see<00:05:45.729> here<00:05:45.969> you 00:05:46.320 --> 00:05:46.330 align:start position:0% cleaned up a lot as you can see here you 00:05:46.330 --> 00:05:50.129 align:start position:0% cleaned up a lot as you can see here you can<00:05:46.800> do<00:05:47.800> a<00:05:47.830> string<00:05:48.129> search<00:05:48.370> for<00:05:49.000> your<00:05:49.659> token 00:05:50.129 --> 00:05:50.139 align:start position:0% can do a string search for your token 00:05:50.139 --> 00:05:52.800 align:start position:0% can do a string search for your token name<00:05:50.379> and<00:05:50.710> token<00:05:51.069> symbol<00:05:51.400> this<00:05:52.270> is<00:05:52.330> actually 00:05:52.800 --> 00:05:52.810 align:start position:0% name and token symbol this is actually 00:05:52.810 --> 00:05:54.240 align:start position:0% name and token symbol this is actually an<00:05:52.960> open<00:05:53.080> source<00:05:53.379> project<00:05:53.589> you<00:05:53.919> can<00:05:54.069> make<00:05:54.219> a 00:05:54.240 --> 00:05:54.250 align:start position:0% an open source project you can make a 00:05:54.250 --> 00:05:57.089 align:start position:0% an open source project you can make a contribution<00:05:54.669> to<00:05:54.969> called<00:05:55.599> eath<00:05:55.870> -<00:05:56.319> contract 00:05:57.089 --> 00:05:57.099 align:start position:0% contribution to called eath - contract 00:05:57.099 --> 00:05:59.519 align:start position:0% contribution to called eath - contract -<00:05:57.310> metadata<00:05:57.900> right<00:05:58.900> now<00:05:59.050> we're<00:05:59.199> searching<00:05:59.440> for 00:05:59.519 --> 00:05:59.529 align:start position:0% - metadata right now we're searching for 00:05:59.529 --> 00:06:02.040 align:start position:0% - metadata right now we're searching for maker<00:05:59.800> and<00:06:00.099> we<00:06:00.879> can<00:06:01.029> add<00:06:01.150> it<00:06:01.300> as<00:06:01.719> you<00:06:01.900> can<00:06:01.990> see 00:06:02.040 --> 00:06:02.050 align:start position:0% maker and we can add it as you can see 00:06:02.050 --> 00:06:05.070 align:start position:0% maker and we can add it as you can see here<00:06:02.430> we<00:06:03.430> can<00:06:03.460> also<00:06:03.759> add<00:06:04.270> a<00:06:04.330> custom<00:06:04.719> contract 00:06:05.070 --> 00:06:05.080 align:start position:0% here we can also add a custom contract 00:06:05.080 --> 00:06:06.360 align:start position:0% here we can also add a custom contract token<00:06:05.349> as<00:06:05.650> you're<00:06:05.800> aware<00:06:05.860> of<00:06:06.069> we're<00:06:06.279> gonna 00:06:06.360 --> 00:06:06.370 align:start position:0% token as you're aware of we're gonna 00:06:06.370 --> 00:06:08.700 align:start position:0% token as you're aware of we're gonna automatically<00:06:06.969> fetch<00:06:07.210> the<00:06:07.569> token<00:06:08.409> metadata 00:06:08.700 --> 00:06:08.710 align:start position:0% automatically fetch the token metadata 00:06:08.710 --> 00:06:14.990 align:start position:0% automatically fetch the token metadata so<00:06:09.279> this<00:06:09.400> is<00:06:09.550> the<00:06:09.669> 0x<00:06:10.060> token<00:06:11.050> contract<00:06:11.440> address 00:06:14.990 --> 00:06:15.000 align:start position:0% 00:06:15.000 --> 00:06:16.230 align:start position:0% alright 00:06:16.230 --> 00:06:16.240 align:start position:0% alright 00:06:16.240 --> 00:06:18.240 align:start position:0% alright after<00:06:16.719> you've<00:06:16.839> added<00:06:16.990> your<00:06:17.169> token<00:06:17.589> you<00:06:18.039> can 00:06:18.240 --> 00:06:18.250 align:start position:0% after you've added your token you can 00:06:18.250 --> 00:06:19.800 align:start position:0% after you've added your token you can send<00:06:18.639> your<00:06:18.729> tokens<00:06:19.060> which<00:06:19.360> is<00:06:19.479> a<00:06:19.509> new<00:06:19.659> feature 00:06:19.800 --> 00:06:19.810 align:start position:0% send your tokens which is a new feature 00:06:19.810 --> 00:06:24.059 align:start position:0% send your tokens which is a new feature so<00:06:20.710> I've<00:06:21.460> got<00:06:21.729> some<00:06:22.000> keys<00:06:22.599> here<00:06:23.050> for<00:06:23.439> our 00:06:24.059 --> 00:06:24.069 align:start position:0% so I've got some keys here for our 00:06:24.069 --> 00:06:27.749 align:start position:0% so I've got some keys here for our company<00:06:24.580> key<00:06:25.240> I<00:06:25.270> can<00:06:25.479> I<00:06:25.949> can<00:06:26.949> send<00:06:27.219> my<00:06:27.339> tokens 00:06:27.749 --> 00:06:27.759 align:start position:0% company key I can I can send my tokens 00:06:27.759 --> 00:06:30.510 align:start position:0% company key I can I can send my tokens to<00:06:27.939> to<00:06:28.120> my<00:06:28.210> friend<00:06:28.479> and<00:06:28.719> I've<00:06:28.779> got<00:06:29.020> a<00:06:29.050> new<00:06:29.710> gas 00:06:30.510 --> 00:06:30.520 align:start position:0% to to my friend and I've got a new gas 00:06:30.520 --> 00:06:36.110 align:start position:0% to to my friend and I've got a new gas tool<00:06:30.849> tip<00:06:31.029> to<00:06:31.300> customize<00:06:31.930> the<00:06:32.110> gas<00:06:32.259> price 00:06:36.110 --> 00:06:36.120 align:start position:0% 00:06:36.120 --> 00:06:38.159 align:start position:0% we're<00:06:37.120> all<00:06:37.210> about<00:06:37.419> responsive<00:06:37.810> design<00:06:37.839> of 00:06:38.159 --> 00:06:38.169 align:start position:0% we're all about responsive design of 00:06:38.169 --> 00:06:40.709 align:start position:0% we're all about responsive design of course<00:06:38.789> so<00:06:39.789> you've<00:06:39.909> got<00:06:40.029> two<00:06:40.210> form<00:06:40.689> factors 00:06:40.709 --> 00:06:40.719 align:start position:0% course so you've got two form factors 00:06:40.719 --> 00:06:43.499 align:start position:0% course so you've got two form factors here<00:06:41.229> mobile<00:06:41.650> and<00:06:41.830> desktop<00:06:42.009> on<00:06:42.639> the<00:06:43.150> left<00:06:43.300> hand 00:06:43.499 --> 00:06:43.509 align:start position:0% here mobile and desktop on the left hand 00:06:43.509 --> 00:06:48.540 align:start position:0% here mobile and desktop on the left hand side<00:06:43.689> you<00:06:43.990> have<00:06:45.150> account<00:06:46.150> and<00:06:47.370> balances<00:06:48.370> and 00:06:48.540 --> 00:06:48.550 align:start position:0% side you have account and balances and 00:06:48.550 --> 00:06:49.499 align:start position:0% side you have account and balances and on<00:06:48.729> the<00:06:48.819> right<00:06:48.939> hand<00:06:49.060> side<00:06:49.270> you<00:06:49.479> have 00:06:49.499 --> 00:06:49.509 align:start position:0% on the right hand side you have 00:06:49.509 --> 00:06:51.899 align:start position:0% on the right hand side you have transactions<00:06:50.169> and<00:06:50.439> on<00:06:51.159> the<00:06:51.279> top<00:06:51.460> right<00:06:51.490> you've 00:06:51.899 --> 00:06:51.909 align:start position:0% transactions and on the top right you've 00:06:51.909 --> 00:06:54.659 align:start position:0% transactions and on the top right you've got<00:06:52.089> your<00:06:52.120> familiar<00:06:52.979> network<00:06:53.979> drop<00:06:54.159> down<00:06:54.370> and 00:06:54.659 --> 00:06:54.669 align:start position:0% got your familiar network drop down and 00:06:54.669 --> 00:06:58.740 align:start position:0% got your familiar network drop down and account<00:06:55.449> settings<00:06:55.779> and<00:06:56.849> next<00:06:57.849> up<00:06:58.000> I'd<00:06:58.360> like<00:06:58.630> to 00:06:58.740 --> 00:06:58.750 align:start position:0% account settings and next up I'd like to 00:06:58.750 --> 00:07:00.119 align:start position:0% account settings and next up I'd like to introduce<00:06:58.959> Frankie<00:06:59.529> to 00:07:00.119 --> 00:07:00.129 align:start position:0% introduce Frankie to 00:07:00.129 --> 00:07:02.159 align:start position:0% introduce Frankie to talk<00:07:00.399> a<00:07:00.429> little<00:07:00.489> bit<00:07:00.729> about<00:07:00.759> meta<00:07:01.599> mask<00:07:01.809> in<00:07:02.080> the 00:07:02.159 --> 00:07:02.169 align:start position:0% talk a little bit about meta mask in the 00:07:02.169 --> 00:07:12.570 align:start position:0% talk a little bit about meta mask in the browser<00:07:02.409> and<00:07:02.860> what<00:07:03.219> the<00:07:03.309> future<00:07:03.550> holds<00:07:11.580> can 00:07:12.570 --> 00:07:12.580 align:start position:0% browser and what the future holds can 00:07:12.580 --> 00:07:14.219 align:start position:0% browser and what the future holds can you<00:07:12.639> guys<00:07:12.789> hear<00:07:13.029> me<00:07:13.059> Oh<00:07:13.330> perfect<00:07:13.839> I<00:07:13.959> can<00:07:14.019> hear 00:07:14.219 --> 00:07:14.229 align:start position:0% you guys hear me Oh perfect I can hear 00:07:14.229 --> 00:07:16.949 align:start position:0% you guys hear me Oh perfect I can hear myself<00:07:14.379> hi<00:07:15.279> I'm<00:07:16.029> Frankie 00:07:16.949 --> 00:07:16.959 align:start position:0% myself hi I'm Frankie 00:07:16.959 --> 00:07:20.159 align:start position:0% myself hi I'm Frankie I<00:07:16.989> am<00:07:17.559> a<00:07:17.800> court<00:07:18.129> dev<00:07:18.339> on<00:07:18.699> meta<00:07:18.999> mask<00:07:19.209> I'd<00:07:19.899> like 00:07:20.159 --> 00:07:20.169 align:start position:0% I am a court dev on meta mask I'd like 00:07:20.169 --> 00:07:23.879 align:start position:0% I am a court dev on meta mask I'd like to<00:07:20.319> thank<00:07:20.589> Dan<00:07:21.099> one<00:07:21.369> more<00:07:21.610> time<00:07:21.849> for<00:07:22.769> coming<00:07:23.769> up 00:07:23.879 --> 00:07:23.889 align:start position:0% to thank Dan one more time for coming up 00:07:23.889 --> 00:07:26.939 align:start position:0% to thank Dan one more time for coming up and<00:07:24.099> speaking<00:07:24.610> for<00:07:24.879> us<00:07:25.409> so<00:07:26.409> let's<00:07:26.739> talk<00:07:26.889> about 00:07:26.939 --> 00:07:26.949 align:start position:0% and speaking for us so let's talk about 00:07:26.949 --> 00:07:29.969 align:start position:0% and speaking for us so let's talk about building<00:07:27.429> gaps<00:07:27.849> with<00:07:28.089> meta<00:07:28.300> masks<00:07:28.979> we 00:07:29.969 --> 00:07:29.979 align:start position:0% building gaps with meta masks we 00:07:29.979 --> 00:07:32.790 align:start position:0% building gaps with meta masks we recommend<00:07:30.550> this<00:07:30.909> pattern<00:07:31.419> today<00:07:31.839> if<00:07:32.349> you<00:07:32.589> want 00:07:32.790 --> 00:07:32.800 align:start position:0% recommend this pattern today if you want 00:07:32.800 --> 00:07:35.609 align:start position:0% recommend this pattern today if you want to<00:07:32.889> build<00:07:32.979> it<00:07:33.189> up<00:07:33.339> as<00:07:33.849> you<00:07:34.599> can<00:07:34.719> see<00:07:34.779> it's<00:07:35.349> quite 00:07:35.609 --> 00:07:35.619 align:start position:0% to build it up as you can see it's quite 00:07:35.619 --> 00:07:37.709 align:start position:0% to build it up as you can see it's quite a<00:07:35.740> bit<00:07:36.249> of<00:07:36.399> code<00:07:36.639> and<00:07:36.909> personally<00:07:37.479> I<00:07:37.509> think 00:07:37.709 --> 00:07:37.719 align:start position:0% a bit of code and personally I think 00:07:37.719 --> 00:07:40.019 align:start position:0% a bit of code and personally I think it's<00:07:38.169> a<00:07:38.289> little<00:07:38.529> clunky<00:07:38.860> and<00:07:39.219> that<00:07:39.519> we<00:07:39.639> can<00:07:39.849> do 00:07:40.019 --> 00:07:40.029 align:start position:0% it's a little clunky and that we can do 00:07:40.029 --> 00:07:42.119 align:start position:0% it's a little clunky and that we can do better<00:07:40.209> I've<00:07:40.990> wandered<00:07:41.319> too<00:07:41.619> far<00:07:41.649> from<00:07:41.979> the 00:07:42.119 --> 00:07:42.129 align:start position:0% better I've wandered too far from the 00:07:42.129 --> 00:07:48.869 align:start position:0% better I've wandered too far from the laptop<00:07:43.889> I<00:07:46.469> would<00:07:47.469> like<00:07:47.649> to<00:07:47.889> announce<00:07:48.279> meta 00:07:48.869 --> 00:07:48.879 align:start position:0% laptop I would like to announce meta 00:07:48.879 --> 00:07:51.959 align:start position:0% laptop I would like to announce meta mascara<00:07:49.509> meta<00:07:50.469> mascara<00:07:50.949> is<00:07:51.159> a<00:07:51.189> module<00:07:51.759> that 00:07:51.959 --> 00:07:51.969 align:start position:0% mascara meta mascara is a module that 00:07:51.969 --> 00:07:53.939 align:start position:0% mascara meta mascara is a module that you<00:07:52.119> can<00:07:52.360> require<00:07:52.749> in<00:07:52.990> your<00:07:53.110> build<00:07:53.319> system<00:07:53.529> or 00:07:53.939 --> 00:07:53.949 align:start position:0% you can require in your build system or 00:07:53.949 --> 00:07:57.329 align:start position:0% you can require in your build system or drop<00:07:54.610> in<00:07:54.849> as<00:07:55.089> a<00:07:55.119> script<00:07:55.539> tag<00:07:55.749> like<00:07:56.619> so<00:07:56.860> and<00:07:57.129> to 00:07:57.329 --> 00:07:57.339 align:start position:0% drop in as a script tag like so and to 00:07:57.339 --> 00:08:01.169 align:start position:0% drop in as a script tag like so and to use<00:07:57.459> the<00:07:57.639> CDN<00:07:59.219> but<00:08:00.219> a<00:08:00.249> mascara<00:08:00.610> finds<00:08:01.029> the 00:08:01.169 --> 00:08:01.179 align:start position:0% use the CDN but a mascara finds the 00:08:01.179 --> 00:08:03.029 align:start position:0% use the CDN but a mascara finds the environmental<00:08:01.839> provider<00:08:02.199> and<00:08:02.619> works<00:08:02.860> with 00:08:03.029 --> 00:08:03.039 align:start position:0% environmental provider and works with 00:08:03.039 --> 00:08:06.149 align:start position:0% environmental provider and works with Miss<00:08:03.309> meta<00:08:03.849> mask<00:08:04.119> extension<00:08:04.809> and<00:08:05.019> parity<00:08:05.559> will 00:08:06.149 --> 00:08:06.159 align:start position:0% Miss meta mask extension and parity will 00:08:06.159 --> 00:08:09.239 align:start position:0% Miss meta mask extension and parity will extract<00:08:06.550> it<00:08:06.789> for<00:08:07.089> you<00:08:07.329> and<00:08:07.659> if<00:08:08.469> we<00:08:08.619> actually<00:08:08.829> go 00:08:09.239 --> 00:08:09.249 align:start position:0% extract it for you and if we actually go 00:08:09.249 --> 00:08:13.350 align:start position:0% extract it for you and if we actually go back<00:08:09.550> here<00:08:09.969> we<00:08:10.449> can<00:08:10.599> see<00:08:10.839> how<00:08:11.439> that<00:08:11.499> works<00:08:12.360> and 00:08:13.350 --> 00:08:13.360 align:start position:0% back here we can see how that works and 00:08:13.360 --> 00:08:15.119 align:start position:0% back here we can see how that works and you<00:08:13.719> just<00:08:13.869> call<00:08:14.050> create<00:08:14.349> default<00:08:14.589> provider 00:08:15.119 --> 00:08:15.129 align:start position:0% you just call create default provider 00:08:15.129 --> 00:08:20.999 align:start position:0% you just call create default provider and<00:08:15.579> it<00:08:16.149> will<00:08:16.329> get<00:08:16.509> it<00:08:16.599> for<00:08:16.809> you<00:08:19.139> if<00:08:20.139> there<00:08:20.800> is 00:08:20.999 --> 00:08:21.009 align:start position:0% and it will get it for you if there is 00:08:21.009 --> 00:08:23.850 align:start position:0% and it will get it for you if there is no<00:08:21.429> environmental<00:08:21.879> web<00:08:22.629> 3<00:08:23.079> to<00:08:23.319> extract<00:08:23.709> the 00:08:23.850 --> 00:08:23.860 align:start position:0% no environmental web 3 to extract the 00:08:23.860 --> 00:08:27.389 align:start position:0% no environmental web 3 to extract the provider<00:08:24.189> from<00:08:24.569> meta<00:08:25.569> mask<00:08:26.009> we'll<00:08:27.009> our 00:08:27.389 --> 00:08:27.399 align:start position:0% provider from meta mask we'll our 00:08:27.399 --> 00:08:29.790 align:start position:0% provider from meta mask we'll our mascara<00:08:28.119> connects<00:08:28.869> to<00:08:29.050> the<00:08:29.139> new<00:08:29.319> meta<00:08:29.589> mask 00:08:29.790 --> 00:08:29.800 align:start position:0% mascara connects to the new meta mask 00:08:29.800 --> 00:08:33.350 align:start position:0% mascara connects to the new meta mask web<00:08:30.099> app<00:08:30.279> at<00:08:30.669> wallet<00:08:31.089> dot<00:08:31.269> minimus<00:08:31.659> that<00:08:31.929> I<00:08:31.959> oh 00:08:33.350 --> 00:08:33.360 align:start position:0% web app at wallet dot minimus that I oh 00:08:33.360 --> 00:08:37.040 align:start position:0% web app at wallet dot minimus that I oh let<00:08:34.360> me<00:08:34.419> just<00:08:34.599> hold<00:08:34.959> for<00:08:35.229> a<00:08:35.259> second<00:08:35.589> there<00:08:35.709> guys 00:08:37.040 --> 00:08:37.050 align:start position:0% let me just hold for a second there guys 00:08:37.050 --> 00:08:40.649 align:start position:0% let me just hold for a second there guys that<00:08:38.050> means<00:08:38.319> your<00:08:39.009> users<00:08:39.459> don't<00:08:40.120> have<00:08:40.300> to 00:08:40.649 --> 00:08:40.659 align:start position:0% that means your users don't have to 00:08:40.659 --> 00:08:48.750 align:start position:0% that means your users don't have to download<00:08:40.870> meta<00:08:41.380> masks<00:08:41.589> anymore 00:08:48.750 --> 00:08:48.760 align:start position:0% 00:08:48.760 --> 00:08:51.730 align:start position:0% to<00:08:49.760> demo<00:08:49.940> this<00:08:50.210> I've<00:08:50.480> built<00:08:50.720> a<00:08:50.990> little<00:08:51.290> DAP 00:08:51.730 --> 00:08:51.740 align:start position:0% to demo this I've built a little DAP 00:08:51.740 --> 00:08:54.040 align:start position:0% to demo this I've built a little DAP here<00:08:52.130> that<00:08:52.370> we<00:08:52.460> can<00:08:52.640> see<00:08:53.000> how<00:08:53.570> the<00:08:53.630> flow<00:08:54.020> of 00:08:54.040 --> 00:08:54.050 align:start position:0% here that we can see how the flow of 00:08:54.050 --> 00:09:01.980 align:start position:0% here that we can see how the flow of what<00:08:54.710> it<00:08:54.830> will<00:08:54.950> look<00:08:55.160> like<00:08:55.630> using<00:08:56.630> mascara 00:09:01.980 --> 00:09:01.990 align:start position:0% 00:09:01.990 --> 00:09:04.690 align:start position:0% going<00:09:02.990> create<00:09:03.230> password<00:09:03.800> sure<00:09:04.460> we're<00:09:04.610> all 00:09:04.690 --> 00:09:04.700 align:start position:0% going create password sure we're all 00:09:04.700 --> 00:09:06.420 align:start position:0% going create password sure we're all used<00:09:04.940> to<00:09:05.060> this 00:09:06.420 --> 00:09:06.430 align:start position:0% used to this 00:09:06.430 --> 00:09:12.220 align:start position:0% used to this of<00:09:07.430> course<00:09:07.700> we've<00:09:07.850> kept<00:09:08.120> our<00:09:08.270> lovely<00:09:08.630> Fox<00:09:11.230> it's 00:09:12.220 --> 00:09:12.230 align:start position:0% of course we've kept our lovely Fox it's 00:09:12.230 --> 00:09:14.020 align:start position:0% of course we've kept our lovely Fox it's also<00:09:12.380> a<00:09:12.500> little<00:09:12.770> slow<00:09:13.040> sorry<00:09:13.400> I<00:09:13.490> didn't<00:09:13.760> speed 00:09:14.020 --> 00:09:14.030 align:start position:0% also a little slow sorry I didn't speed 00:09:14.030 --> 00:09:15.850 align:start position:0% also a little slow sorry I didn't speed it<00:09:14.150> up<00:09:14.270> for<00:09:14.300> you<00:09:14.510> guys<00:09:14.710> generate<00:09:15.710> unique 00:09:15.850 --> 00:09:15.860 align:start position:0% it up for you guys generate unique 00:09:15.860 --> 00:09:18.370 align:start position:0% it up for you guys generate unique account<00:09:16.300> ignore<00:09:17.300> the<00:09:17.420> beta<00:09:17.630> notice<00:09:18.050> as<00:09:18.260> we 00:09:18.370 --> 00:09:18.380 align:start position:0% account ignore the beta notice as we 00:09:18.380 --> 00:09:20.740 align:start position:0% account ignore the beta notice as we always<00:09:18.590> do<00:09:18.980> also<00:09:19.340> just<00:09:19.790> scroll<00:09:20.150> straight<00:09:20.510> down 00:09:20.740 --> 00:09:20.750 align:start position:0% always do also just scroll straight down 00:09:20.750 --> 00:09:26.140 align:start position:0% always do also just scroll straight down and<00:09:21.080> then<00:09:21.410> do<00:09:21.710> seed<00:09:22.070> phrase<00:09:24.760> get<00:09:25.760> a<00:09:25.790> good<00:09:26.000> look 00:09:26.140 --> 00:09:26.150 align:start position:0% and then do seed phrase get a good look 00:09:26.150 --> 00:09:31.420 align:start position:0% and then do seed phrase get a good look at<00:09:26.330> that<00:09:26.360> seed<00:09:26.690> phrase<00:09:26.960> everybody<00:09:29.680> and<00:09:30.680> just 00:09:31.420 --> 00:09:31.430 align:start position:0% at that seed phrase everybody and just 00:09:31.430 --> 00:09:33.490 align:start position:0% at that seed phrase everybody and just as<00:09:31.580> a<00:09:31.610> little<00:09:31.820> added<00:09:32.030> bonus<00:09:32.510> for<00:09:32.540> our<00:09:32.780> use<00:09:33.170> to 00:09:33.490 --> 00:09:33.500 align:start position:0% as a little added bonus for our use to 00:09:33.500 --> 00:09:35.080 align:start position:0% as a little added bonus for our use to protect<00:09:33.830> our<00:09:33.950> users<00:09:34.160> we've<00:09:34.520> added<00:09:34.700> a<00:09:34.880> little 00:09:35.080 --> 00:09:35.090 align:start position:0% protect our users we've added a little 00:09:35.090 --> 00:09:37.060 align:start position:0% protect our users we've added a little game<00:09:35.600> to<00:09:36.020> make<00:09:36.170> sure<00:09:36.350> that<00:09:36.470> you've<00:09:36.620> backed<00:09:36.860> up 00:09:37.060 --> 00:09:37.070 align:start position:0% game to make sure that you've backed up 00:09:37.070 --> 00:09:40.570 align:start position:0% game to make sure that you've backed up your<00:09:37.220> seed<00:09:37.460> phrase<00:09:37.760> correctly<00:09:39.430> don't<00:09:40.430> go 00:09:40.570 --> 00:09:40.580 align:start position:0% your seed phrase correctly don't go 00:09:40.580 --> 00:09:49.700 align:start position:0% your seed phrase correctly don't go through<00:09:40.970> and<00:09:41.570> click<00:09:42.170> things<00:09:46.690> yeah<00:09:48.280> it's<00:09:49.280> fun 00:09:49.700 --> 00:09:49.710 align:start position:0% through and click things yeah it's fun 00:09:49.710 --> 00:09:56.820 align:start position:0% through and click things yeah it's fun [Music] 00:09:56.820 --> 00:09:56.830 align:start position:0% 00:09:56.830 --> 00:09:58.930 align:start position:0% now<00:09:57.830> of<00:09:57.890> course<00:09:58.100> I'm<00:09:58.220> only<00:09:58.400> human 00:09:58.930 --> 00:09:58.940 align:start position:0% now of course I'm only human 00:09:58.940 --> 00:10:00.730 align:start position:0% now of course I'm only human thank<00:09:59.210> God<00:09:59.360> I<00:09:59.390> wrote<00:09:59.810> my<00:09:59.990> seed<00:10:00.260> phrase<00:10:00.470> as<00:10:00.650> you 00:10:00.730 --> 00:10:00.740 align:start position:0% thank God I wrote my seed phrase as you 00:10:00.740 --> 00:10:02.260 align:start position:0% thank God I wrote my seed phrase as you can<00:10:00.890> see<00:10:01.010> it's<00:10:01.160> not<00:10:01.310> gonna<00:10:01.460> let<00:10:01.700> me<00:10:01.820> confirm 00:10:02.260 --> 00:10:02.270 align:start position:0% can see it's not gonna let me confirm 00:10:02.270 --> 00:10:04.540 align:start position:0% can see it's not gonna let me confirm that<00:10:02.420> because<00:10:02.660> it's<00:10:02.810> wrong<00:10:03.130> so<00:10:04.130> we<00:10:04.250> can<00:10:04.400> all 00:10:04.540 --> 00:10:04.550 align:start position:0% that because it's wrong so we can all 00:10:04.550 --> 00:10:06.700 align:start position:0% that because it's wrong so we can all awkwardly<00:10:05.000> sit<00:10:05.390> here<00:10:05.630> now<00:10:05.810> and<00:10:06.080> watch<00:10:06.260> me<00:10:06.500> try 00:10:06.700 --> 00:10:06.710 align:start position:0% awkwardly sit here now and watch me try 00:10:06.710 --> 00:10:14.920 align:start position:0% awkwardly sit here now and watch me try to<00:10:06.800> figure<00:10:07.160> it<00:10:07.310> out<00:10:13.300> yeah<00:10:14.300> there<00:10:14.780> you<00:10:14.900> go 00:10:14.920 --> 00:10:14.930 align:start position:0% to figure it out yeah there you go 00:10:14.930 --> 00:10:16.860 align:start position:0% to figure it out yeah there you go you're<00:10:15.350> doing<00:10:15.560> a<00:10:15.620> good<00:10:15.710> job 00:10:16.860 --> 00:10:16.870 align:start position:0% you're doing a good job 00:10:16.870 --> 00:10:33.820 align:start position:0% you're doing a good job it's<00:10:17.870> okay<00:10:19.330> yeah<00:10:27.100> mm-hmm<00:10:29.590> go<00:10:30.590> on<00:10:32.710> she<00:10:33.710> gets 00:10:33.820 --> 00:10:33.830 align:start position:0% it's okay yeah mm-hmm go on she gets 00:10:33.830 --> 00:10:40.410 align:start position:0% it's okay yeah mm-hmm go on she gets nervous<00:10:34.040> on<00:10:34.430> stage<00:10:34.460> you<00:10:35.270> know 00:10:40.410 --> 00:10:40.420 align:start position:0% 00:10:40.420 --> 00:10:42.540 align:start position:0% ah<00:10:40.450> there<00:10:41.050> we<00:10:41.170> go<00:10:41.200> then<00:10:42.010> of<00:10:42.100> course<00:10:42.339> it<00:10:42.459> takes 00:10:42.540 --> 00:10:42.550 align:start position:0% ah there we go then of course it takes 00:10:42.550 --> 00:10:44.100 align:start position:0% ah there we go then of course it takes you<00:10:42.730> to<00:10:42.820> this<00:10:42.910> deposit<00:10:43.269> page<00:10:43.570> which<00:10:43.810> I'm<00:10:43.959> going 00:10:44.100 --> 00:10:44.110 align:start position:0% you to this deposit page which I'm going 00:10:44.110 --> 00:10:45.540 align:start position:0% you to this deposit page which I'm going to<00:10:44.200> skip<00:10:44.470> for<00:10:44.620> the<00:10:44.680> sake<00:10:44.860> of<00:10:44.890> the<00:10:45.010> demo<00:10:45.220> and 00:10:45.540 --> 00:10:45.550 align:start position:0% to skip for the sake of the demo and 00:10:45.550 --> 00:10:48.329 align:start position:0% to skip for the sake of the demo and takes<00:10:46.120> you<00:10:46.329> to<00:10:46.690> the<00:10:47.350> account<00:10:47.800> details<00:10:48.190> screen 00:10:48.329 --> 00:10:48.339 align:start position:0% takes you to the account details screen 00:10:48.339 --> 00:10:50.759 align:start position:0% takes you to the account details screen and<00:10:48.670> we<00:10:48.790> go<00:10:48.910> back<00:10:49.060> to<00:10:49.120> the<00:10:49.360> top<00:10:49.570> click<00:10:50.290> bonk<00:10:50.560> me 00:10:50.759 --> 00:10:50.769 align:start position:0% and we go back to the top click bonk me 00:10:50.769 --> 00:10:53.639 align:start position:0% and we go back to the top click bonk me and<00:10:50.980> if<00:10:51.579> you<00:10:51.700> can<00:10:51.880> see<00:10:52.089> here<00:10:52.300> in<00:10:52.450> a<00:10:52.540> second<00:10:52.930> the 00:10:53.639 --> 00:10:53.649 align:start position:0% and if you can see here in a second the 00:10:53.649 --> 00:10:55.800 align:start position:0% and if you can see here in a second the meta<00:10:53.860> mask<00:10:54.070> window<00:10:54.339> is<00:10:54.670> going<00:10:54.850> to<00:10:54.940> pop<00:10:55.089> up<00:10:55.300> just 00:10:55.800 --> 00:10:55.810 align:start position:0% meta mask window is going to pop up just 00:10:55.810 --> 00:11:06.210 align:start position:0% meta mask window is going to pop up just like<00:10:55.930> you<00:10:56.079> would<00:10:56.170> see<00:10:56.380> in<00:10:56.500> the<00:10:56.529> extension<00:11:05.220> so 00:11:06.210 --> 00:11:06.220 align:start position:0% like you would see in the extension so 00:11:06.220 --> 00:11:07.610 align:start position:0% like you would see in the extension so let's<00:11:06.370> talk<00:11:06.519> about<00:11:06.640> how<00:11:06.820> that<00:11:06.850> works 00:11:07.610 --> 00:11:07.620 align:start position:0% let's talk about how that works 00:11:07.620 --> 00:11:11.069 align:start position:0% let's talk about how that works meta<00:11:08.620> mask<00:11:08.860> as<00:11:09.240> you<00:11:10.240> know<00:11:10.390> it<00:11:10.510> is<00:11:10.600> an<00:11:10.720> extension 00:11:11.069 --> 00:11:11.079 align:start position:0% meta mask as you know it is an extension 00:11:11.079 --> 00:11:13.410 align:start position:0% meta mask as you know it is an extension and<00:11:11.529> provides<00:11:12.040> a<00:11:12.310> single<00:11:12.519> background<00:11:13.000> process 00:11:13.410 --> 00:11:13.420 align:start position:0% and provides a single background process 00:11:13.420 --> 00:11:15.750 align:start position:0% and provides a single background process for<00:11:13.870> different<00:11:14.410> applications<00:11:14.980> to<00:11:15.070> talk<00:11:15.370> to<00:11:15.550> so 00:11:15.750 --> 00:11:15.760 align:start position:0% for different applications to talk to so 00:11:15.760 --> 00:11:18.060 align:start position:0% for different applications to talk to so users<00:11:16.060> can<00:11:16.269> use<00:11:16.450> this<00:11:16.600> in<00:11:16.839> keys<00:11:17.079> we've<00:11:17.829> created 00:11:18.060 --> 00:11:18.070 align:start position:0% users can use this in keys we've created 00:11:18.070 --> 00:11:22.230 align:start position:0% users can use this in keys we've created a<00:11:18.279> very<00:11:18.310> similar<00:11:18.730> flow<00:11:19.209> here<00:11:19.540> by<00:11:19.779> hosting<00:11:21.240> meta 00:11:22.230 --> 00:11:22.240 align:start position:0% a very similar flow here by hosting meta 00:11:22.240 --> 00:11:25.230 align:start position:0% a very similar flow here by hosting meta mascara<00:11:22.750> will<00:11:22.990> inject<00:11:23.769> an<00:11:24.040> iframe<00:11:24.519> into<00:11:25.149> the 00:11:25.230 --> 00:11:25.240 align:start position:0% mascara will inject an iframe into the 00:11:25.240 --> 00:11:27.500 align:start position:0% mascara will inject an iframe into the web<00:11:25.390> page<00:11:25.630> that<00:11:25.690> talks<00:11:26.230> to<00:11:26.500> the<00:11:26.800> serviceworker 00:11:27.500 --> 00:11:27.510 align:start position:0% web page that talks to the serviceworker 00:11:27.510 --> 00:11:30.509 align:start position:0% web page that talks to the serviceworker underneath<00:11:28.510> wallet<00:11:28.930> meta<00:11:29.290> must<00:11:29.500> at<00:11:29.680> i/o<00:11:29.769> the 00:11:30.509 --> 00:11:30.519 align:start position:0% underneath wallet meta must at i/o the 00:11:30.519 --> 00:11:32.430 align:start position:0% underneath wallet meta must at i/o the serviceworker<00:11:30.880> contains<00:11:31.570> the<00:11:31.750> meta<00:11:31.899> Moz<00:11:32.079> core 00:11:32.430 --> 00:11:32.440 align:start position:0% serviceworker contains the meta Moz core 00:11:32.440 --> 00:11:40.139 align:start position:0% serviceworker contains the meta Moz core which<00:11:32.980> also<00:11:33.220> talks<00:11:33.579> to<00:11:33.880> the<00:11:33.970> UI<00:11:36.870> I<00:11:39.000> would<00:11:40.000> just 00:11:40.139 --> 00:11:40.149 align:start position:0% which also talks to the UI I would just 00:11:40.149 --> 00:11:41.610 align:start position:0% which also talks to the UI I would just like<00:11:40.329> to<00:11:40.360> remind<00:11:40.690> everyone<00:11:41.019> also<00:11:41.350> that 00:11:41.610 --> 00:11:41.620 align:start position:0% like to remind everyone also that 00:11:41.620 --> 00:11:43.380 align:start position:0% like to remind everyone also that mascara<00:11:41.980> is<00:11:42.100> a<00:11:42.130> developer<00:11:42.700> beta<00:11:42.880> and<00:11:43.240> if<00:11:43.300> you 00:11:43.380 --> 00:11:43.390 align:start position:0% mascara is a developer beta and if you 00:11:43.390 --> 00:11:45.720 align:start position:0% mascara is a developer beta and if you find<00:11:43.570> any<00:11:43.690> issues<00:11:44.260> please<00:11:44.800> report<00:11:45.399> them<00:11:45.579> we 00:11:45.720 --> 00:11:45.730 align:start position:0% find any issues please report them we 00:11:45.730 --> 00:11:50.370 align:start position:0% find any issues please report them we greatly<00:11:46.000> appreciate<00:11:46.240> it<00:11:48.959> now<00:11:49.959> I'd<00:11:50.110> like<00:11:50.320> to 00:11:50.370 --> 00:11:50.380 align:start position:0% greatly appreciate it now I'd like to 00:11:50.380 --> 00:11:52.439 align:start position:0% greatly appreciate it now I'd like to welcome<00:11:50.529> comethis<00:11:51.130> back<00:11:51.430> up<00:11:51.640> stage<00:11:51.880> to<00:11:52.209> talk 00:11:52.439 --> 00:11:52.449 align:start position:0% welcome comethis back up stage to talk 00:11:52.449 --> 00:12:01.620 align:start position:0% welcome comethis back up stage to talk about<00:11:52.600> the<00:11:52.810> evolution<00:11:53.380> of<00:11:53.410> meta<00:11:53.949> mask<00:12:00.630> yes 00:12:01.620 --> 00:12:01.630 align:start position:0% about the evolution of meta mask yes 00:12:01.630 --> 00:12:03.930 align:start position:0% about the evolution of meta mask yes let's<00:12:02.170> talk<00:12:02.649> about<00:12:02.769> where<00:12:03.010> this<00:12:03.190> fox<00:12:03.640> is 00:12:03.930 --> 00:12:03.940 align:start position:0% let's talk about where this fox is 00:12:03.940 --> 00:12:07.280 align:start position:0% let's talk about where this fox is headed<00:12:04.329> just<00:12:05.290> a<00:12:06.070> small<00:12:06.310> one<00:12:06.430> to<00:12:06.640> begin<00:12:06.760> with 00:12:07.280 --> 00:12:07.290 align:start position:0% headed just a small one to begin with 00:12:07.290 --> 00:12:09.990 align:start position:0% headed just a small one to begin with debug.trace<00:12:08.290> transaction<00:12:09.250> if<00:12:09.640> you<00:12:09.790> saw<00:12:09.940> the 00:12:09.990 --> 00:12:10.000 align:start position:0% debug.trace transaction if you saw the 00:12:10.000 --> 00:12:11.970 align:start position:0% debug.trace transaction if you saw the demo<00:12:10.300> for<00:12:10.660> a<00:12:10.720> remake<00:12:11.170> stutter<00:12:11.529> theorem 00:12:11.970 --> 00:12:11.980 align:start position:0% demo for a remake stutter theorem 00:12:11.980 --> 00:12:14.490 align:start position:0% demo for a remake stutter theorem earlier<00:12:12.519> it's<00:12:13.060> a<00:12:13.209> fantastic<00:12:13.959> tool<00:12:14.199> for 00:12:14.490 --> 00:12:14.500 align:start position:0% earlier it's a fantastic tool for 00:12:14.500 --> 00:12:18.090 align:start position:0% earlier it's a fantastic tool for debugging<00:12:15.420> the<00:12:16.420> transactions<00:12:17.199> behavior<00:12:17.709> in 00:12:18.090 --> 00:12:18.100 align:start position:0% debugging the transactions behavior in 00:12:18.100 --> 00:12:19.949 align:start position:0% debugging the transactions behavior in your<00:12:18.279> contract<00:12:18.670> but<00:12:19.180> previously<00:12:19.660> it's 00:12:19.949 --> 00:12:19.959 align:start position:0% your contract but previously it's 00:12:19.959 --> 00:12:21.930 align:start position:0% your contract but previously it's required<00:12:20.320> tester<00:12:20.769> BC<00:12:21.100> or<00:12:21.339> a<00:12:21.490> specially 00:12:21.930 --> 00:12:21.940 align:start position:0% required tester BC or a specially 00:12:21.940 --> 00:12:24.360 align:start position:0% required tester BC or a specially configured<00:12:22.089> death<00:12:22.630> node<00:12:22.870> in<00:12:23.110> order<00:12:23.949> to<00:12:24.100> use<00:12:24.220> it 00:12:24.360 --> 00:12:24.370 align:start position:0% configured death node in order to use it 00:12:24.370 --> 00:12:27.300 align:start position:0% configured death node in order to use it and<00:12:25.110> soon<00:12:26.110> to<00:12:26.230> be<00:12:26.260> pushed<00:12:26.589> to<00:12:26.769> production<00:12:27.070> you 00:12:27.300 --> 00:12:27.310 align:start position:0% and soon to be pushed to production you 00:12:27.310 --> 00:12:29.400 align:start position:0% and soon to be pushed to production you can<00:12:27.610> use<00:12:27.940> it<00:12:28.089> right<00:12:28.570> in<00:12:28.660> meta<00:12:28.779> mask<00:12:28.990> against 00:12:29.400 --> 00:12:29.410 align:start position:0% can use it right in meta mask against 00:12:29.410 --> 00:12:34.110 align:start position:0% can use it right in meta mask against any<00:12:29.620> network<00:12:29.920> here<00:12:30.100> pointing<00:12:30.370> at<00:12:32.399> another<00:12:33.399> RPC 00:12:34.110 --> 00:12:34.120 align:start position:0% any network here pointing at another RPC 00:12:34.120 --> 00:12:36.569 align:start position:0% any network here pointing at another RPC method<00:12:34.300> our<00:12:34.720> first<00:12:35.380> new<00:12:35.890> one<00:12:36.070> the<00:12:36.310> first<00:12:36.459> one 00:12:36.569 --> 00:12:36.579 align:start position:0% method our first new one the first one 00:12:36.579 --> 00:12:38.790 align:start position:0% method our first new one the first one that<00:12:36.910> it's<00:12:37.570> been<00:12:37.779> implemented<00:12:38.140> in<00:12:38.380> meta<00:12:38.560> mask 00:12:38.790 --> 00:12:38.800 align:start position:0% that it's been implemented in meta mask 00:12:38.800 --> 00:12:41.280 align:start position:0% that it's been implemented in meta mask and<00:12:39.100> not<00:12:39.370> yet<00:12:39.640> parity<00:12:40.120> and<00:12:40.300> guess<00:12:40.570> this<00:12:41.110> is 00:12:41.280 --> 00:12:41.290 align:start position:0% and not yet parity and guess this is 00:12:41.290 --> 00:12:44.430 align:start position:0% and not yet parity and guess this is eath<00:12:41.560> sign<00:12:42.370> typed<00:12:42.820> data<00:12:43.089> from<00:12:43.660> EEP<00:12:43.899> seven<00:12:44.290> one 00:12:44.430 --> 00:12:44.440 align:start position:0% eath sign typed data from EEP seven one 00:12:44.440 --> 00:12:46.769 align:start position:0% eath sign typed data from EEP seven one two<00:12:44.490> this<00:12:45.490> gives<00:12:45.820> us<00:12:45.970> a<00:12:46.120> human<00:12:46.420> readable 00:12:46.769 --> 00:12:46.779 align:start position:0% two this gives us a human readable 00:12:46.779 --> 00:12:50.400 align:start position:0% two this gives us a human readable structured<00:12:47.500> data<00:12:47.709> signing<00:12:48.490> format<00:12:49.170> you<00:12:50.170> can 00:12:50.400 --> 00:12:50.410 align:start position:0% structured data signing format you can 00:12:50.410 --> 00:12:54.000 align:start position:0% structured data signing format you can specify<00:12:50.829> some<00:12:51.430> parameters<00:12:52.240> and<00:12:52.480> their<00:12:52.870> value 00:12:54.000 --> 00:12:54.010 align:start position:0% specify some parameters and their value 00:12:54.010 --> 00:12:56.580 align:start position:0% specify some parameters and their value and<00:12:54.100> when<00:12:54.490> they<00:12:54.670> are<00:12:55.510> intercepted<00:12:56.110> by<00:12:56.200> a<00:12:56.230> meta 00:12:56.580 --> 00:12:56.590 align:start position:0% and when they are intercepted by a meta 00:12:56.590 --> 00:12:59.010 align:start position:0% and when they are intercepted by a meta mask<00:12:56.910> here's<00:12:57.910> a<00:12:58.000> little<00:12:58.180> mock-up<00:12:58.390> we<00:12:58.840> can 00:12:59.010 --> 00:12:59.020 align:start position:0% mask here's a little mock-up we can 00:12:59.020 --> 00:13:01.500 align:start position:0% mask here's a little mock-up we can display<00:12:59.530> that<00:13:00.490> sort<00:13:00.730> of<00:13:00.760> that<00:13:00.910> form<00:13:01.270> data 00:13:01.500 --> 00:13:01.510 align:start position:0% display that sort of that form data 00:13:01.510 --> 00:13:05.490 align:start position:0% display that sort of that form data before<00:13:02.140> you<00:13:02.410> decide<00:13:03.130> to<00:13:03.160> sign<00:13:03.520> or<00:13:04.080> deny<00:13:05.080> and 00:13:05.490 --> 00:13:05.500 align:start position:0% before you decide to sign or deny and 00:13:05.500 --> 00:13:09.380 align:start position:0% before you decide to sign or deny and this<00:13:06.370> is<00:13:06.520> very<00:13:06.700> useful<00:13:07.060> for<00:13:07.090> state<00:13:07.810> channels 00:13:09.380 --> 00:13:09.390 align:start position:0% this is very useful for state channels 00:13:09.390 --> 00:13:13.080 align:start position:0% this is very useful for state channels moving<00:13:10.390> on<00:13:10.510> to<00:13:10.780> some<00:13:10.960> internal<00:13:11.860> organs<00:13:12.280> the 00:13:13.080 --> 00:13:13.090 align:start position:0% moving on to some internal organs the 00:13:13.090 --> 00:13:16.560 align:start position:0% moving on to some internal organs the heart<00:13:13.360> really<00:13:13.690> key<00:13:14.230> management<00:13:15.060> we've<00:13:16.060> broken 00:13:16.560 --> 00:13:16.570 align:start position:0% heart really key management we've broken 00:13:16.570 --> 00:13:19.260 align:start position:0% heart really key management we've broken out<00:13:16.870> the<00:13:17.500> key<00:13:17.950> ring<00:13:18.130> controller<00:13:18.580> and<00:13:18.880> one<00:13:19.150> of 00:13:19.260 --> 00:13:19.270 align:start position:0% out the key ring controller and one of 00:13:19.270 --> 00:13:21.660 align:start position:0% out the key ring controller and one of our<00:13:19.390> key<00:13:19.750> ring<00:13:19.900> types<00:13:20.200> the<00:13:20.770> hierarchical 00:13:21.660 --> 00:13:21.670 align:start position:0% our key ring types the hierarchical 00:13:21.670 --> 00:13:24.480 align:start position:0% our key ring types the hierarchical deterministic<00:13:22.570> keyring<00:13:22.930> and<00:13:23.050> and<00:13:24.010> you<00:13:24.340> can 00:13:24.480 --> 00:13:24.490 align:start position:0% deterministic keyring and and you can 00:13:24.490 --> 00:13:26.700 align:start position:0% deterministic keyring and and you can use<00:13:24.670> these<00:13:24.880> as<00:13:25.300> modules<00:13:25.780> if<00:13:26.050> you're<00:13:26.380> building 00:13:26.700 --> 00:13:26.710 align:start position:0% use these as modules if you're building 00:13:26.710 --> 00:13:31.440 align:start position:0% use these as modules if you're building a<00:13:26.950> JavaScript<00:13:27.460> wallet<00:13:28.800> and<00:13:29.800> if<00:13:30.580> you<00:13:30.910> build 00:13:31.440 --> 00:13:31.450 align:start position:0% a JavaScript wallet and if you build 00:13:31.450 --> 00:13:33.960 align:start position:0% a JavaScript wallet and if you build other<00:13:31.720> keyring<00:13:32.320> types<00:13:32.590> that<00:13:33.130> match<00:13:33.370> that<00:13:33.400> API 00:13:33.960 --> 00:13:33.970 align:start position:0% other keyring types that match that API 00:13:33.970 --> 00:13:35.760 align:start position:0% other keyring types that match that API they<00:13:34.540> can<00:13:34.690> be<00:13:34.810> added<00:13:35.170> to<00:13:35.380> the<00:13:35.500> keyring 00:13:35.760 --> 00:13:35.770 align:start position:0% they can be added to the keyring 00:13:35.770 --> 00:13:38.940 align:start position:0% they can be added to the keyring controller<00:13:36.130> or<00:13:36.310> added<00:13:36.700> to<00:13:36.730> madam<00:13:37.300> asked<00:13:37.450> if<00:13:38.440> we 00:13:38.940 --> 00:13:38.950 align:start position:0% controller or added to madam asked if we 00:13:38.950 --> 00:13:42.240 align:start position:0% controller or added to madam asked if we build<00:13:39.400> the<00:13:39.690> requisite<00:13:40.690> UI<00:13:40.840> for<00:13:41.170> them<00:13:41.320> so<00:13:42.130> they 00:13:42.240 --> 00:13:42.250 align:start position:0% build the requisite UI for them so they 00:13:42.250 --> 00:13:45.240 align:start position:0% build the requisite UI for them so they slot<00:13:42.520> right<00:13:42.730> in<00:13:43.740> so<00:13:44.740> yes 00:13:45.240 --> 00:13:45.250 align:start position:0% slot right in so yes 00:13:45.250 --> 00:13:47.370 align:start position:0% slot right in so yes wallet<00:13:46.030> developers<00:13:46.420> please<00:13:46.870> feel<00:13:47.110> free<00:13:47.140> to 00:13:47.370 --> 00:13:47.380 align:start position:0% wallet developers please feel free to 00:13:47.380 --> 00:13:50.040 align:start position:0% wallet developers please feel free to use<00:13:47.980> these<00:13:48.280> modules<00:13:48.490> take<00:13:49.360> advantage<00:13:49.810> of<00:13:49.930> our 00:13:50.040 --> 00:13:50.050 align:start position:0% use these modules take advantage of our 00:13:50.050 --> 00:13:55.380 align:start position:0% use these modules take advantage of our security<00:13:50.620> audit<00:13:53.370> we<00:13:54.370> know<00:13:54.490> many<00:13:54.670> people<00:13:55.000> have 00:13:55.380 --> 00:13:55.390 align:start position:0% security audit we know many people have 00:13:55.390 --> 00:13:57.320 align:start position:0% security audit we know many people have been<00:13:55.480> waiting<00:13:55.600> for<00:13:55.900> Hardware<00:13:56.260> wallet<00:13:56.590> support 00:13:57.320 --> 00:13:57.330 align:start position:0% been waiting for Hardware wallet support 00:13:57.330 --> 00:13:59.700 align:start position:0% been waiting for Hardware wallet support contract<00:13:58.330> proxy<00:13:58.810> account<00:13:59.080> support<00:13:59.290> and 00:13:59.700 --> 00:13:59.710 align:start position:0% contract proxy account support and 00:13:59.710 --> 00:14:03.090 align:start position:0% contract proxy account support and coming<00:14:00.640> soon<00:14:00.850> the<00:14:01.090> account<00:14:01.660> abstraction<00:14:02.350> from 00:14:03.090 --> 00:14:03.100 align:start position:0% coming soon the account abstraction from 00:14:03.100 --> 00:14:07.410 align:start position:0% coming soon the account abstraction from the<00:14:03.250> next<00:14:03.460> fork<00:14:05.820> they<00:14:06.820> can<00:14:06.970> be<00:14:07.030> implemented 00:14:07.410 --> 00:14:07.420 align:start position:0% the next fork they can be implemented 00:14:07.420 --> 00:14:10.590 align:start position:0% the next fork they can be implemented using<00:14:07.750> those<00:14:08.170> keyring<00:14:08.800> types<00:14:09.600> another 00:14:10.590 --> 00:14:10.600 align:start position:0% using those keyring types another 00:14:10.600 --> 00:14:12.810 align:start position:0% using those keyring types another internal<00:14:11.380> organ<00:14:11.800> of<00:14:11.920> meta<00:14:12.100> mask<00:14:12.310> is<00:14:12.580> the 00:14:12.810 --> 00:14:12.820 align:start position:0% internal organ of meta mask is the 00:14:12.820 --> 00:14:14.640 align:start position:0% internal organ of meta mask is the bought<00:14:13.180> chain<00:14:13.420> data<00:14:13.630> source<00:14:13.960> the<00:14:14.200> the 00:14:14.640 --> 00:14:14.650 align:start position:0% bought chain data source the the 00:14:14.650 --> 00:14:20.190 align:start position:0% bought chain data source the the provider<00:14:17.130> we've<00:14:18.130> been<00:14:18.460> experimenting<00:14:19.180> with<00:14:19.720> a 00:14:20.190 --> 00:14:20.200 align:start position:0% provider we've been experimenting with a 00:14:20.200 --> 00:14:23.750 align:start position:0% provider we've been experimenting with a ipfs<00:14:20.920> based<00:14:21.430> zero<00:14:22.120> and<00:14:22.330> light<00:14:22.510> client<00:14:22.930> and 00:14:23.750 --> 00:14:23.760 align:start position:0% ipfs based zero and light client and 00:14:23.760 --> 00:14:26.940 align:start position:0% ipfs based zero and light client and what<00:14:24.760> would<00:14:24.880> that<00:14:24.910> look<00:14:25.060> like<00:14:25.210> it's<00:14:25.800> well<00:14:26.800> it 00:14:26.940 --> 00:14:26.950 align:start position:0% what would that look like it's well it 00:14:26.950 --> 00:14:29.580 align:start position:0% what would that look like it's well it would<00:14:27.070> fit<00:14:27.760> right<00:14:28.000> into<00:14:28.240> the<00:14:29.020> network<00:14:29.350> menu 00:14:29.580 --> 00:14:29.590 align:start position:0% would fit right into the network menu 00:14:29.590 --> 00:14:32.370 align:start position:0% would fit right into the network menu and<00:14:29.860> meta<00:14:30.010> mask<00:14:30.220> like<00:14:30.400> you're<00:14:30.550> used<00:14:30.730> to<00:14:31.380> it's 00:14:32.370 --> 00:14:32.380 align:start position:0% and meta mask like you're used to it's 00:14:32.380 --> 00:14:35.910 align:start position:0% and meta mask like you're used to it's like<00:14:32.560> hearing<00:14:33.190> via<00:14:33.370> IP<00:14:33.550> FS<00:14:33.970> and<00:14:34.780> it<00:14:35.500> works<00:14:35.680> just 00:14:35.910 --> 00:14:35.920 align:start position:0% like hearing via IP FS and it works just 00:14:35.920 --> 00:14:38.490 align:start position:0% like hearing via IP FS and it works just like<00:14:36.040> you'd<00:14:36.610> imagine<00:14:36.730> it<00:14:37.060> would<00:14:37.180> and<00:14:37.570> however 00:14:38.490 --> 00:14:38.500 align:start position:0% like you'd imagine it would and however 00:14:38.500 --> 00:14:40.920 align:start position:0% like you'd imagine it would and however since<00:14:39.250> selecting<00:14:39.910> an<00:14:40.150> item<00:14:40.270> from<00:14:40.660> a<00:14:40.720> menu 00:14:40.920 --> 00:14:40.930 align:start position:0% since selecting an item from a menu 00:14:40.930 --> 00:14:43.590 align:start position:0% since selecting an item from a menu doesn't<00:14:41.350> really<00:14:41.530> make<00:14:41.770> for<00:14:42.280> a<00:14:42.340> great<00:14:42.460> demo<00:14:42.790> we 00:14:43.590 --> 00:14:43.600 align:start position:0% doesn't really make for a great demo we 00:14:43.600 --> 00:14:46.530 align:start position:0% doesn't really make for a great demo we have<00:14:43.630> a<00:14:44.140> data<00:14:44.440> visualization<00:14:44.880> of<00:14:45.880> what's 00:14:46.530 --> 00:14:46.540 align:start position:0% have a data visualization of what's 00:14:46.540 --> 00:14:51.180 align:start position:0% have a data visualization of what's happening<00:14:46.900> behind<00:14:47.440> the<00:14:47.560> scenes<00:14:49.590> so<00:14:50.590> this<00:14:51.040> is 00:14:51.180 --> 00:14:51.190 align:start position:0% happening behind the scenes so this is 00:14:51.190 --> 00:14:55.050 align:start position:0% happening behind the scenes so this is still<00:14:51.340> very<00:14:51.520> early<00:14:51.640> stage<00:14:52.150> it's<00:14:53.020> a<00:14:53.670> naive<00:14:54.670> it's 00:14:55.050 --> 00:14:55.060 align:start position:0% still very early stage it's a naive it's 00:14:55.060 --> 00:14:57.810 align:start position:0% still very early stage it's a naive it's doing<00:14:55.900> lots<00:14:56.110> of<00:14:56.320> back-and-forth<00:14:56.740> what<00:14:57.730> you 00:14:57.810 --> 00:14:57.820 align:start position:0% doing lots of back-and-forth what you 00:14:57.820 --> 00:15:00.150 align:start position:0% doing lots of back-and-forth what you see<00:14:58.000> here<00:14:58.210> is<00:14:58.270> it's<00:14:58.480> lazily<00:14:59.050> loading<00:14:59.560> nodes 00:15:00.150 --> 00:15:00.160 align:start position:0% see here is it's lazily loading nodes 00:15:00.160 --> 00:15:03.780 align:start position:0% see here is it's lazily loading nodes from<00:15:00.490> the<00:15:00.640> state<00:15:00.910> graph<00:15:01.180> in<00:15:01.480> order<00:15:02.170> to<00:15:02.790> provide 00:15:03.780 --> 00:15:03.790 align:start position:0% from the state graph in order to provide 00:15:03.790 --> 00:15:06.510 align:start position:0% from the state graph in order to provide data<00:15:04.000> for<00:15:04.330> multiple<00:15:05.230> instances<00:15:06.010> of<00:15:06.070> the 00:15:06.510 --> 00:15:06.520 align:start position:0% data for multiple instances of the 00:15:06.520 --> 00:15:08.090 align:start position:0% data for multiple instances of the theorem<00:15:06.790> virtual<00:15:07.090> machine<00:15:07.330> running 00:15:08.090 --> 00:15:08.100 align:start position:0% theorem virtual machine running 00:15:08.100 --> 00:15:10.290 align:start position:0% theorem virtual machine running currently<00:15:09.100> it's<00:15:09.250> looking<00:15:09.490> up<00:15:09.610> some<00:15:09.850> data<00:15:10.060> on 00:15:10.290 --> 00:15:10.300 align:start position:0% currently it's looking up some data on 00:15:10.300 --> 00:15:14.010 align:start position:0% currently it's looking up some data on the<00:15:10.630> oMG<00:15:11.320> token<00:15:11.740> a<00:15:12.430> couple<00:15:13.180> accounts<00:15:13.540> bounces 00:15:14.010 --> 00:15:14.020 align:start position:0% the oMG token a couple accounts bounces 00:15:14.020 --> 00:15:21.960 align:start position:0% the oMG token a couple accounts bounces as<00:15:14.290> well<00:15:14.740> as<00:15:14.860> the<00:15:15.100> total<00:15:15.730> supply<00:15:19.500> the<00:15:20.700> blue<00:15:21.700> is 00:15:21.960 --> 00:15:21.970 align:start position:0% as well as the total supply the blue is 00:15:21.970 --> 00:15:24.900 align:start position:0% as well as the total supply the blue is the<00:15:22.330> state<00:15:22.750> graph<00:15:23.020> and<00:15:23.290> the<00:15:23.710> green<00:15:23.950> is<00:15:24.160> inside 00:15:24.900 --> 00:15:24.910 align:start position:0% the state graph and the green is inside 00:15:24.910 --> 00:15:28.200 align:start position:0% the state graph and the green is inside of<00:15:25.000> the<00:15:25.060> contract<00:15:25.480> the<00:15:25.600> contract<00:15:25.630> storage<00:15:27.210> if 00:15:28.200 --> 00:15:28.210 align:start position:0% of the contract the contract storage if 00:15:28.210 --> 00:15:29.520 align:start position:0% of the contract the contract storage if you<00:15:28.360> have<00:15:28.450> some<00:15:28.630> questions<00:15:28.930> about<00:15:29.020> that<00:15:29.260> find 00:15:29.520 --> 00:15:29.530 align:start position:0% you have some questions about that find 00:15:29.530 --> 00:15:31.020 align:start position:0% you have some questions about that find me<00:15:29.650> afterwards<00:15:30.040> I'll<00:15:30.130> be<00:15:30.220> happy<00:15:30.460> to<00:15:30.490> answer 00:15:31.020 --> 00:15:31.030 align:start position:0% me afterwards I'll be happy to answer 00:15:31.030 --> 00:15:36.410 align:start position:0% me afterwards I'll be happy to answer them<00:15:33.930> this<00:15:34.930> is<00:15:35.080> still<00:15:35.290> very<00:15:35.440> early<00:15:35.890> stage 00:15:36.410 --> 00:15:36.420 align:start position:0% them this is still very early stage 00:15:36.420 --> 00:15:39.090 align:start position:0% them this is still very early stage experimental<00:15:37.420> we've<00:15:38.230> spun<00:15:38.680> up<00:15:38.830> a<00:15:38.920> project 00:15:39.090 --> 00:15:39.100 align:start position:0% experimental we've spun up a project 00:15:39.100 --> 00:15:41.760 align:start position:0% experimental we've spun up a project called<00:15:39.430> boost<00:15:39.970> Acala<00:15:40.300> to<00:15:40.780> organize<00:15:41.410> some<00:15:41.680> of 00:15:41.760 --> 00:15:41.770 align:start position:0% called boost Acala to organize some of 00:15:41.770 --> 00:15:43.770 align:start position:0% called boost Acala to organize some of the<00:15:41.830> efforts<00:15:42.250> to<00:15:42.730> bridge<00:15:43.270> in<00:15:43.450> theory<00:15:43.600> amman 00:15:43.770 --> 00:15:43.780 align:start position:0% the efforts to bridge in theory amman 00:15:43.780 --> 00:15:46.290 align:start position:0% the efforts to bridge in theory amman ipfs<00:15:44.290> it<00:15:44.650> sounds<00:15:44.920> like<00:15:45.040> many<00:15:45.370> other<00:15:45.700> projects 00:15:46.290 --> 00:15:46.300 align:start position:0% ipfs it sounds like many other projects 00:15:46.300 --> 00:15:50.340 align:start position:0% ipfs it sounds like many other projects have<00:15:46.630> been<00:15:47.590> working<00:15:48.040> on<00:15:48.130> this<00:15:48.220> as<00:15:48.400> well<00:15:48.580> so<00:15:49.350> we 00:15:50.340 --> 00:15:50.350 align:start position:0% have been working on this as well so we 00:15:50.350 --> 00:15:55.110 align:start position:0% have been working on this as well so we look<00:15:50.530> forward<00:15:50.770> to<00:15:50.860> working<00:15:51.250> with<00:15:51.520> them<00:15:54.120> and 00:15:55.110 --> 00:15:55.120 align:start position:0% look forward to working with them and 00:15:55.120 --> 00:16:02.160 align:start position:0% look forward to working with them and yes<00:15:55.390> the<00:15:55.600> foxes<00:15:56.140> howl<00:16:00.480> many<00:16:01.480> many<00:16:01.750> people<00:16:02.020> ask 00:16:02.160 --> 00:16:02.170 align:start position:0% yes the foxes howl many many people ask 00:16:02.170 --> 00:16:05.460 align:start position:0% yes the foxes howl many many people ask how<00:16:02.830> how<00:16:03.160> can<00:16:03.220> we<00:16:03.400> collaborate<00:16:04.260> we're<00:16:05.260> very 00:16:05.460 --> 00:16:05.470 align:start position:0% how how can we collaborate we're very 00:16:05.470 --> 00:16:07.800 align:start position:0% how how can we collaborate we're very open<00:16:05.650> to<00:16:06.130> this<00:16:06.250> please<00:16:06.910> just<00:16:07.150> reach<00:16:07.300> out<00:16:07.450> in 00:16:07.800 --> 00:16:07.810 align:start position:0% open to this please just reach out in 00:16:07.810 --> 00:16:10.080 align:start position:0% open to this please just reach out in particular<00:16:08.530> if<00:16:08.980> you're<00:16:09.190> doing<00:16:09.550> a<00:16:09.640> token 00:16:10.080 --> 00:16:10.090 align:start position:0% particular if you're doing a token 00:16:10.090 --> 00:16:12.990 align:start position:0% particular if you're doing a token launch<00:16:10.570> and<00:16:10.870> you<00:16:11.160> are<00:16:12.160> recommending<00:16:12.850> meta 00:16:12.990 --> 00:16:13.000 align:start position:0% launch and you are recommending meta 00:16:13.000 --> 00:16:15.750 align:start position:0% launch and you are recommending meta masks<00:16:13.240> to<00:16:13.660> your<00:16:13.780> users<00:16:14.080> please<00:16:14.950> get<00:16:15.310> ahold<00:16:15.430> of 00:16:15.750 --> 00:16:15.760 align:start position:0% masks to your users please get ahold of 00:16:15.760 --> 00:16:18.330 align:start position:0% masks to your users please get ahold of us<00:16:15.910> we've<00:16:16.510> had<00:16:16.540> many<00:16:17.110> many<00:16:17.230> support<00:16:17.950> questions 00:16:18.330 --> 00:16:18.340 align:start position:0% us we've had many many support questions 00:16:18.340 --> 00:16:20.670 align:start position:0% us we've had many many support questions over<00:16:18.550> the<00:16:18.640> past<00:16:18.850> year<00:16:19.180> and<00:16:19.360> sometimes<00:16:20.200> don't 00:16:20.670 --> 00:16:20.680 align:start position:0% over the past year and sometimes don't 00:16:20.680 --> 00:16:22.740 align:start position:0% over the past year and sometimes don't know<00:16:20.890> where<00:16:21.460> to<00:16:21.640> direct<00:16:21.820> our<00:16:22.150> users<00:16:22.540> to 00:16:22.740 --> 00:16:22.750 align:start position:0% know where to direct our users to 00:16:22.750 --> 00:16:25.140 align:start position:0% know where to direct our users to actually<00:16:23.080> get<00:16:23.260> the<00:16:23.380> information<00:16:23.940> so<00:16:24.940> please 00:16:25.140 --> 00:16:25.150 align:start position:0% actually get the information so please 00:16:25.150 --> 00:16:27.810 align:start position:0% actually get the information so please take<00:16:25.990> care<00:16:26.140> of<00:16:26.230> your<00:16:26.350> users<00:16:26.680> and<00:16:26.920> one<00:16:27.700> way<00:16:27.790> you 00:16:27.810 --> 00:16:27.820 align:start position:0% take care of your users and one way you 00:16:27.820 --> 00:16:30.650 align:start position:0% take care of your users and one way you can<00:16:28.000> do<00:16:28.120> that<00:16:28.240> is<00:16:28.390> to<00:16:28.480> reach<00:16:28.630> out<00:16:28.750> to<00:16:28.810> us 00:16:30.650 --> 00:16:30.660 align:start position:0% can do that is to reach out to us 00:16:30.660 --> 00:16:35.850 align:start position:0% can do that is to reach out to us another<00:16:31.660> how<00:16:34.080> how<00:16:35.080> to<00:16:35.140> contribute 00:16:35.850 --> 00:16:35.860 align:start position:0% another how how to contribute 00:16:35.860 --> 00:16:38.060 align:start position:0% another how how to contribute of<00:16:35.920> course<00:16:36.220> meta<00:16:36.400> mask<00:16:36.580> is<00:16:36.730> all<00:16:36.880> open<00:16:37.240> source 00:16:38.060 --> 00:16:38.070 align:start position:0% of course meta mask is all open source 00:16:38.070 --> 00:16:40.820 align:start position:0% of course meta mask is all open source we<00:16:39.070> would<00:16:39.430> love<00:16:39.550> to<00:16:39.610> have<00:16:39.850> your<00:16:39.970> contributions 00:16:40.820 --> 00:16:40.830 align:start position:0% we would love to have your contributions 00:16:40.830 --> 00:16:43.560 align:start position:0% we would love to have your contributions we're<00:16:41.830> looking<00:16:42.130> forward<00:16:42.550> to<00:16:42.790> integrating 00:16:43.560 --> 00:16:43.570 align:start position:0% we're looking forward to integrating 00:16:43.570 --> 00:16:46.230 align:start position:0% we're looking forward to integrating with<00:16:43.690> get<00:16:44.140> coin<00:16:44.410> get<00:16:44.980> token<00:16:45.160> in<00:16:45.730> all<00:16:46.060> these 00:16:46.230 --> 00:16:46.240 align:start position:0% with get coin get token in all these 00:16:46.240 --> 00:16:48.960 align:start position:0% with get coin get token in all these incentive<00:16:46.840> schemes<00:16:47.140> that<00:16:47.470> the<00:16:47.970> that 00:16:48.960 --> 00:16:48.970 align:start position:0% incentive schemes that the that 00:16:48.970 --> 00:16:51.480 align:start position:0% incentive schemes that the that ecosystem<00:16:49.570> has<00:16:49.930> been<00:16:50.140> creating<00:16:50.590> if<00:16:50.830> you 00:16:51.480 --> 00:16:51.490 align:start position:0% ecosystem has been creating if you 00:16:51.490 --> 00:16:53.100 align:start position:0% ecosystem has been creating if you really<00:16:51.820> like<00:16:51.970> minnow<00:16:52.150> masks<00:16:52.360> we're<00:16:52.930> also 00:16:53.100 --> 00:16:53.110 align:start position:0% really like minnow masks we're also 00:16:53.110 --> 00:16:59.610 align:start position:0% really like minnow masks we're also hiring<00:16:53.440> reach<00:16:54.250> out<00:16:54.430> to<00:16:54.550> us<00:16:54.700> oh<00:16:56.640> yeah<00:16:58.440> we<00:16:59.440> also 00:16:59.610 --> 00:16:59.620 align:start position:0% hiring reach out to us oh yeah we also 00:16:59.620 --> 00:17:01.320 align:start position:0% hiring reach out to us oh yeah we also would<00:17:00.220> like<00:17:00.250> to<00:17:00.430> highlight<00:17:00.700> a<00:17:00.850> few<00:17:00.970> other 00:17:01.320 --> 00:17:01.330 align:start position:0% would like to highlight a few other 00:17:01.330 --> 00:17:04.260 align:start position:0% would like to highlight a few other things<00:17:01.600> in<00:17:01.930> the<00:17:02.230> peer-to-peer<00:17:02.590> ecosystem<00:17:03.430> as 00:17:04.260 --> 00:17:04.270 align:start position:0% things in the peer-to-peer ecosystem as 00:17:04.270 --> 00:17:06.810 align:start position:0% things in the peer-to-peer ecosystem as Joseph<00:17:04.930> Puna<00:17:05.260> said<00:17:05.410> many<00:17:05.590> times<00:17:05.820> the 00:17:06.810 --> 00:17:06.820 align:start position:0% Joseph Puna said many times the 00:17:06.820 --> 00:17:08.310 align:start position:0% Joseph Puna said many times the blockchain<00:17:07.060> should<00:17:07.450> be<00:17:07.540> sort<00:17:07.750> of<00:17:07.780> the<00:17:07.900> supreme 00:17:08.310 --> 00:17:08.320 align:start position:0% blockchain should be sort of the supreme 00:17:08.320 --> 00:17:10.470 align:start position:0% blockchain should be sort of the supreme court<00:17:08.650> we<00:17:09.130> should<00:17:09.280> only<00:17:09.430> go<00:17:09.730> there<00:17:09.970> as<00:17:10.180> often 00:17:10.470 --> 00:17:10.480 align:start position:0% court we should only go there as often 00:17:10.480 --> 00:17:12.030 align:start position:0% court we should only go there as often as<00:17:10.750> necessary 00:17:12.030 --> 00:17:12.040 align:start position:0% as necessary 00:17:12.040 --> 00:17:14.490 align:start position:0% as necessary and<00:17:12.310> there's<00:17:12.580> many<00:17:12.970> elements<00:17:13.810> of<00:17:14.110> this 00:17:14.490 --> 00:17:14.500 align:start position:0% and there's many elements of this 00:17:14.500 --> 00:17:17.100 align:start position:0% and there's many elements of this decentralized<00:17:15.100> ecosystem<00:17:15.970> that<00:17:16.540> frankly 00:17:17.100 --> 00:17:17.110 align:start position:0% decentralized ecosystem that frankly 00:17:17.110 --> 00:17:20.850 align:start position:0% decentralized ecosystem that frankly don't<00:17:17.260> need<00:17:17.470> a<00:17:17.500> blockchain<00:17:17.980> and<00:17:19.050> so<00:17:20.050> I 00:17:20.850 --> 00:17:20.860 align:start position:0% don't need a blockchain and so I 00:17:20.860 --> 00:17:23.640 align:start position:0% don't need a blockchain and so I I<00:17:20.920> think<00:17:21.370> that<00:17:21.699> we<00:17:22.420> need<00:17:22.600> to<00:17:22.750> explore<00:17:23.350> some<00:17:23.620> of 00:17:23.640 --> 00:17:23.650 align:start position:0% I think that we need to explore some of 00:17:23.650 --> 00:17:25.110 align:start position:0% I think that we need to explore some of the<00:17:23.799> some<00:17:24.490> of<00:17:24.579> the<00:17:24.640> already<00:17:24.819> existing 00:17:25.110 --> 00:17:25.120 align:start position:0% the some of the already existing 00:17:25.120 --> 00:17:26.490 align:start position:0% the some of the already existing projects<00:17:25.839> that<00:17:25.929> are<00:17:26.020> doing<00:17:26.140> a<00:17:26.290> great<00:17:26.439> job 00:17:26.490 --> 00:17:26.500 align:start position:0% projects that are doing a great job 00:17:26.500 --> 00:17:28.710 align:start position:0% projects that are doing a great job there<00:17:26.829> I'd<00:17:27.670> like<00:17:27.819> to<00:17:27.939> highlight<00:17:28.120> the<00:17:28.420> beaker 00:17:28.710 --> 00:17:28.720 align:start position:0% there I'd like to highlight the beaker 00:17:28.720 --> 00:17:30.419 align:start position:0% there I'd like to highlight the beaker browser<00:17:28.990> this<00:17:29.590> is<00:17:29.710> an<00:17:29.770> awesome<00:17:29.950> peer-to-peer 00:17:30.419 --> 00:17:30.429 align:start position:0% browser this is an awesome peer-to-peer 00:17:30.429 --> 00:17:33.930 align:start position:0% browser this is an awesome peer-to-peer browser<00:17:31.140> it's<00:17:32.140> based<00:17:32.559> on<00:17:32.740> the<00:17:33.250> DAP<00:17:33.520> network 00:17:33.930 --> 00:17:33.940 align:start position:0% browser it's based on the DAP network 00:17:33.940 --> 00:17:37.830 align:start position:0% browser it's based on the DAP network which<00:17:34.299> is<00:17:34.510> comparable<00:17:34.929> to<00:17:35.049> ipfs<00:17:36.030> it<00:17:37.030> it<00:17:37.540> lets 00:17:37.830 --> 00:17:37.840 align:start position:0% which is comparable to ipfs it it lets 00:17:37.840 --> 00:17:39.750 align:start position:0% which is comparable to ipfs it it lets you<00:17:38.080> share<00:17:38.650> and<00:17:38.830> serve<00:17:39.070> websites 00:17:39.750 --> 00:17:39.760 align:start position:0% you share and serve websites 00:17:39.760 --> 00:17:42.180 align:start position:0% you share and serve websites peer-to-peer<00:17:40.059> as<00:17:40.510> well<00:17:40.809> as<00:17:40.980> create<00:17:41.980> your<00:17:42.160> own 00:17:42.180 --> 00:17:42.190 align:start position:0% peer-to-peer as well as create your own 00:17:42.190 --> 00:17:47.130 align:start position:0% peer-to-peer as well as create your own websites<00:17:44.880> patchwork<00:17:45.880> which<00:17:46.540> is<00:17:46.780> a<00:17:46.809> one 00:17:47.130 --> 00:17:47.140 align:start position:0% websites patchwork which is a one 00:17:47.140 --> 00:17:49.110 align:start position:0% websites patchwork which is a one interface<00:17:47.530> on<00:17:47.770> the<00:17:47.950> secure<00:17:48.580> scuttlebutt 00:17:49.110 --> 00:17:49.120 align:start position:0% interface on the secure scuttlebutt 00:17:49.120 --> 00:17:51.810 align:start position:0% interface on the secure scuttlebutt network<00:17:49.510> this<00:17:50.049> is<00:17:50.260> a<00:17:50.290> very<00:17:50.980> highly<00:17:51.309> featured 00:17:51.810 --> 00:17:51.820 align:start position:0% network this is a very highly featured 00:17:51.820 --> 00:17:53.700 align:start position:0% network this is a very highly featured social<00:17:52.540> network<00:17:52.870> that's<00:17:53.230> completely 00:17:53.700 --> 00:17:53.710 align:start position:0% social network that's completely 00:17:53.710 --> 00:17:56.130 align:start position:0% social network that's completely peer-to-peer<00:17:54.040> and<00:17:54.940> doesn't<00:17:55.330> use<00:17:55.360> blockchain 00:17:56.130 --> 00:17:56.140 align:start position:0% peer-to-peer and doesn't use blockchain 00:17:56.140 --> 00:17:56.580 align:start position:0% peer-to-peer and doesn't use blockchain at<00:17:56.260> all 00:17:56.580 --> 00:17:56.590 align:start position:0% at all 00:17:56.590 --> 00:17:58.770 align:start position:0% at all this<00:17:57.160> is<00:17:57.280> fantastic<00:17:57.669> I<00:17:58.059> think<00:17:58.090> you'll<00:17:58.510> enjoy 00:17:58.770 --> 00:17:58.780 align:start position:0% this is fantastic I think you'll enjoy 00:17:58.780 --> 00:18:01.680 align:start position:0% this is fantastic I think you'll enjoy exploring<00:17:59.440> its<00:17:59.980> community<00:18:00.429> so<00:18:01.210> please<00:18:01.510> check 00:18:01.680 --> 00:18:01.690 align:start position:0% exploring its community so please check 00:18:01.690 --> 00:18:07.080 align:start position:0% exploring its community so please check it<00:18:01.750> out<00:18:01.929> oh<00:18:05.850> yes 00:18:07.080 --> 00:18:07.090 align:start position:0% it out oh yes 00:18:07.090 --> 00:18:10.350 align:start position:0% it out oh yes and<00:18:07.179> one<00:18:07.750> more<00:18:07.929> thing<00:18:08.080> that<00:18:08.640> mascara<00:18:09.640> that 00:18:10.350 --> 00:18:10.360 align:start position:0% and one more thing that mascara that 00:18:10.360 --> 00:18:13.830 align:start position:0% and one more thing that mascara that Frankie<00:18:11.110> demoed<00:18:11.730> it<00:18:12.730> works<00:18:12.970> right<00:18:13.419> now<00:18:13.450> on 00:18:13.830 --> 00:18:13.840 align:start position:0% Frankie demoed it works right now on 00:18:13.840 --> 00:18:16.010 align:start position:0% Frankie demoed it works right now on Chrome<00:18:14.380> for<00:18:14.650> Android<00:18:14.710> right<00:18:15.400> in<00:18:15.520> your<00:18:15.610> browser 00:18:16.010 --> 00:18:16.020 align:start position:0% Chrome for Android right in your browser 00:18:16.020 --> 00:18:23.540 align:start position:0% Chrome for Android right in your browser so<00:18:17.020> try<00:18:17.169> that<00:18:17.230> out<00:18:17.370> thank<00:18:18.370> you 00:18:23.540 --> 00:18:23.550 align:start position:0% 00:18:23.550 --> 00:18:31.130 align:start position:0% [Music]