WEBVTT Kind: captions Language: en 00:00:17.890 --> 00:00:21.130 align:start position:0% hey<00:00:18.890> how's<00:00:19.100> how's<00:00:19.730> everybody<00:00:20.090> doing<00:00:20.300> I'm 00:00:21.130 --> 00:00:21.140 align:start position:0% hey how's how's everybody doing I'm 00:00:21.140 --> 00:00:22.980 align:start position:0% hey how's how's everybody doing I'm Aaron<00:00:21.530> Davis<00:00:21.800> I<00:00:22.010> also<00:00:22.190> go<00:00:22.369> by<00:00:22.400> Kumho<00:00:22.700> vez 00:00:22.980 --> 00:00:22.990 align:start position:0% Aaron Davis I also go by Kumho vez 00:00:22.990 --> 00:00:25.510 align:start position:0% Aaron Davis I also go by Kumho vez whichever<00:00:23.990> you<00:00:24.110> prefer<00:00:24.260> and<00:00:25.070> today<00:00:25.400> we're 00:00:25.510 --> 00:00:25.520 align:start position:0% whichever you prefer and today we're 00:00:25.520 --> 00:00:27.640 align:start position:0% whichever you prefer and today we're gonna<00:00:25.580> be<00:00:25.700> talking<00:00:26.029> about<00:00:26.300> meta<00:00:26.960> masking<00:00:27.410> and 00:00:27.640 --> 00:00:27.650 align:start position:0% gonna be talking about meta masking and 00:00:27.650 --> 00:00:32.080 align:start position:0% gonna be talking about meta masking and how<00:00:27.980> we<00:00:28.040> get<00:00:28.730> aetherium<00:00:29.000> into<00:00:29.270> the<00:00:29.360> browser<00:00:31.090> so 00:00:32.080 --> 00:00:32.090 align:start position:0% how we get aetherium into the browser so 00:00:32.090 --> 00:00:34.810 align:start position:0% how we get aetherium into the browser so our<00:00:32.660> core<00:00:33.020> our<00:00:33.440> core<00:00:33.770> goal<00:00:33.950> is<00:00:34.310> ease<00:00:34.670> of 00:00:34.810 --> 00:00:34.820 align:start position:0% our core our core goal is ease of 00:00:34.820 --> 00:00:37.360 align:start position:0% our core our core goal is ease of adoption<00:00:35.030> and<00:00:35.570> one<00:00:36.320> way<00:00:36.470> we<00:00:36.740> we<00:00:37.130> sort<00:00:37.310> of 00:00:37.360 --> 00:00:37.370 align:start position:0% adoption and one way we we sort of 00:00:37.370 --> 00:00:39.880 align:start position:0% adoption and one way we we sort of measure<00:00:37.550> that<00:00:37.640> is<00:00:38.090> time<00:00:38.810> from<00:00:39.050> first<00:00:39.440> account 00:00:39.880 --> 00:00:39.890 align:start position:0% measure that is time from first account 00:00:39.890 --> 00:00:43.710 align:start position:0% measure that is time from first account to<00:00:40.610> first<00:00:40.970> ether<00:00:41.329> to<00:00:41.480> first<00:00:41.750> transaction<00:00:42.140> and 00:00:43.710 --> 00:00:43.720 align:start position:0% to first ether to first transaction and 00:00:43.720 --> 00:00:46.930 align:start position:0% to first ether to first transaction and I'm<00:00:44.720> going<00:00:44.899> to<00:00:44.930> bring<00:00:45.200> Frankie<00:00:45.980> and<00:00:46.310> Kevin<00:00:46.820> on 00:00:46.930 --> 00:00:46.940 align:start position:0% I'm going to bring Frankie and Kevin on 00:00:46.940 --> 00:00:50.530 align:start position:0% I'm going to bring Frankie and Kevin on to<00:00:47.540> talk<00:00:48.080> about<00:00:48.200> that<00:00:48.470> yeah<00:00:49.070> hello<00:00:49.940> dear<00:00:50.240> devs 00:00:50.530 --> 00:00:50.540 align:start position:0% to talk about that yeah hello dear devs 00:00:50.540 --> 00:00:56.350 align:start position:0% to talk about that yeah hello dear devs let<00:00:50.750> us<00:00:50.870> make<00:00:51.050> you<00:00:51.170> roar<00:00:51.530> about<00:00:52.130> medam<00:00:55.060> made<00:00:56.060> by 00:00:56.350 --> 00:00:56.360 align:start position:0% let us make you roar about medam made by 00:00:56.360 --> 00:01:02.790 align:start position:0% let us make you roar about medam made by us<00:00:56.600> for<00:00:57.110> I'm<00:00:57.470> sorry<00:00:58.270> okay<00:00:59.270> this<00:00:59.450> is<00:00:59.540> not<00:00:59.660> good 00:01:02.790 --> 00:01:02.800 align:start position:0% 00:01:02.800 --> 00:01:03.910 align:start position:0% okay 00:01:03.910 --> 00:01:03.920 align:start position:0% okay 00:01:03.920 --> 00:01:06.100 align:start position:0% okay oh<00:01:03.950> yeah<00:01:04.129> okay<00:01:04.339> sorry<00:01:04.549> a<00:01:05.509> browser<00:01:05.990> extension 00:01:06.100 --> 00:01:06.110 align:start position:0% oh yeah okay sorry a browser extension 00:01:06.110 --> 00:01:08.320 align:start position:0% oh yeah okay sorry a browser extension for<00:01:06.710> Chrome<00:01:06.890> and<00:01:07.009> more<00:01:07.280> but<00:01:08.000> there's<00:01:08.180> even 00:01:08.320 --> 00:01:08.330 align:start position:0% for Chrome and more but there's even 00:01:08.330 --> 00:01:10.420 align:start position:0% for Chrome and more but there's even more<00:01:08.479> browsers<00:01:08.930> and<00:01:09.290> mobile<00:01:09.380> coming<00:01:10.100> up<00:01:10.250> in 00:01:10.420 --> 00:01:10.430 align:start position:0% more browsers and mobile coming up in 00:01:10.430 --> 00:01:13.179 align:start position:0% more browsers and mobile coming up in store<00:01:10.759> meta<00:01:11.390> mass<00:01:11.570> index<00:01:12.020> pages<00:01:12.650> what<00:01:12.920> green 00:01:13.179 --> 00:01:13.189 align:start position:0% store meta mass index pages what green 00:01:13.189 --> 00:01:15.399 align:start position:0% store meta mass index pages what green your<00:01:13.369> page<00:01:13.579> is<00:01:13.729> real<00:01:13.970> lazy<00:01:14.240> webbed<00:01:15.170> apps 00:01:15.399 --> 00:01:15.409 align:start position:0% your page is real lazy webbed apps 00:01:15.409 --> 00:01:17.200 align:start position:0% your page is real lazy webbed apps running<00:01:15.710> in<00:01:15.829> a<00:01:15.920> normal<00:01:16.159> browser<00:01:16.340> that's<00:01:16.790> crazy 00:01:17.200 --> 00:01:17.210 align:start position:0% running in a normal browser that's crazy 00:01:17.210 --> 00:01:19.420 align:start position:0% running in a normal browser that's crazy there's<00:01:17.900> no<00:01:17.990> need<00:01:18.350> for<00:01:18.380> a<00:01:18.619> local<00:01:18.830> full<00:01:19.190> node 00:01:19.420 --> 00:01:19.430 align:start position:0% there's no need for a local full node 00:01:19.430 --> 00:01:21.250 align:start position:0% there's no need for a local full node first-time<00:01:20.240> user<00:01:20.450> you've<00:01:20.690> hit<00:01:20.870> the<00:01:20.900> mother 00:01:21.250 --> 00:01:21.260 align:start position:0% first-time user you've hit the mother 00:01:21.260 --> 00:01:24.850 align:start position:0% first-time user you've hit the mother lode<00:01:21.560> we<00:01:22.130> protect<00:01:22.520> you<00:01:22.580> with<00:01:22.900> contravenes<00:01:23.900> so 00:01:24.850 --> 00:01:24.860 align:start position:0% lode we protect you with contravenes so 00:01:24.860 --> 00:01:26.380 align:start position:0% lode we protect you with contravenes so that<00:01:25.010> you<00:01:25.159> don't<00:01:25.370> lose<00:01:25.640> your<00:01:25.670> ether<00:01:26.180> like 00:01:26.380 --> 00:01:26.390 align:start position:0% that you don't lose your ether like 00:01:26.390 --> 00:01:28.570 align:start position:0% that you don't lose your ether like spilling<00:01:26.690> the<00:01:26.930> beans<00:01:27.110> on<00:01:27.440> top<00:01:27.950> of<00:01:28.159> that<00:01:28.250> here 00:01:28.570 --> 00:01:28.580 align:start position:0% spilling the beans on top of that here 00:01:28.580 --> 00:01:30.280 align:start position:0% spilling the beans on top of that here have<00:01:28.850> some<00:01:29.150> wallets<00:01:29.540> to<00:01:29.900> hold<00:01:30.080> all<00:01:30.260> that 00:01:30.280 --> 00:01:30.290 align:start position:0% have some wallets to hold all that 00:01:30.290 --> 00:01:32.469 align:start position:0% have some wallets to hold all that either<00:01:30.560> so<00:01:30.860> that<00:01:30.890> you<00:01:31.190> can<00:01:31.370> haul<00:01:31.610> it<00:01:31.820> we<00:01:32.270> love 00:01:32.469 --> 00:01:32.479 align:start position:0% either so that you can haul it we love 00:01:32.479 --> 00:01:34.450 align:start position:0% either so that you can haul it we love the<00:01:32.659> apps<00:01:32.780> ether<00:01:33.229> needs<00:01:33.470> them<00:01:33.590> in<00:01:33.710> stacks<00:01:34.010> give 00:01:34.450 --> 00:01:34.460 align:start position:0% the apps ether needs them in stacks give 00:01:34.460 --> 00:01:36.969 align:start position:0% the apps ether needs them in stacks give us<00:01:34.610> more<00:01:34.909> of<00:01:35.090> them<00:01:35.240> like<00:01:35.270> flapjack<00:01:36.170> I<00:01:36.440> don't 00:01:36.969 --> 00:01:36.979 align:start position:0% us more of them like flapjack I don't 00:01:36.979 --> 00:01:38.530 align:start position:0% us more of them like flapjack I don't have<00:01:37.159> anything<00:01:37.430> else<00:01:37.760> to<00:01:38.060> say 00:01:38.530 --> 00:01:38.540 align:start position:0% have anything else to say 00:01:38.540 --> 00:01:45.399 align:start position:0% have anything else to say so<00:01:38.930> here's<00:01:39.290> Frankie<00:01:39.800> yay 00:01:45.399 --> 00:01:45.409 align:start position:0% 00:01:45.409 --> 00:01:49.419 align:start position:0% um<00:01:46.280> thanks<00:01:47.030> Kevin<00:01:47.299> hi<00:01:47.899> guys<00:01:48.229> I'm<00:01:48.619> Frankie<00:01:49.189> and 00:01:49.419 --> 00:01:49.429 align:start position:0% um thanks Kevin hi guys I'm Frankie and 00:01:49.429 --> 00:01:51.849 align:start position:0% um thanks Kevin hi guys I'm Frankie and I'm<00:01:49.490> going<00:01:49.700> to<00:01:49.850> talk<00:01:50.090> about<00:01:50.359> meta<00:01:50.929> mass<00:01:51.140> from 00:01:51.849 --> 00:01:51.859 align:start position:0% I'm going to talk about meta mass from 00:01:51.859 --> 00:01:54.069 align:start position:0% I'm going to talk about meta mass from the<00:01:51.920> user<00:01:52.189> experience<00:01:52.310> from<00:01:53.119> first 00:01:54.069 --> 00:01:54.079 align:start position:0% the user experience from first 00:01:54.079 --> 00:01:56.169 align:start position:0% the user experience from first installation<00:01:54.500> to<00:01:55.100> dap<00:01:55.340> use<00:01:55.700> to<00:01:55.939> first 00:01:56.169 --> 00:01:56.179 align:start position:0% installation to dap use to first 00:01:56.179 --> 00:02:02.289 align:start position:0% installation to dap use to first transaction<00:01:57.340> louder<00:01:58.340> even<00:01:59.299> louder<00:02:00.100> god<00:02:01.299> okay 00:02:02.289 --> 00:02:02.299 align:start position:0% transaction louder even louder god okay 00:02:02.299 --> 00:02:05.649 align:start position:0% transaction louder even louder god okay we<00:02:02.929> are<00:02:03.289> live<00:02:03.649> on<00:02:03.979> the<00:02:04.189> chrome<00:02:04.429> store<00:02:04.609> so<00:02:05.270> user 00:02:05.649 --> 00:02:05.659 align:start position:0% we are live on the chrome store so user 00:02:05.659 --> 00:02:08.619 align:start position:0% we are live on the chrome store so user goes<00:02:06.049> and<00:02:06.079> downloads<00:02:06.890> meta<00:02:07.189> musk<00:02:07.429> and<00:02:07.880> we 00:02:08.619 --> 00:02:08.629 align:start position:0% goes and downloads meta musk and we 00:02:08.629 --> 00:02:12.330 align:start position:0% goes and downloads meta musk and we create<00:02:08.929> a<00:02:08.959> vault<00:02:09.229> it<00:02:09.560> is<00:02:09.890> a<00:02:10.330> deterministic 00:02:12.330 --> 00:02:12.340 align:start position:0% create a vault it is a deterministic 00:02:12.340 --> 00:02:14.979 align:start position:0% create a vault it is a deterministic keyring<00:02:13.340> I<00:02:13.610> had<00:02:14.120> to<00:02:14.269> remember<00:02:14.510> this<00:02:14.780> this 00:02:14.979 --> 00:02:14.989 align:start position:0% keyring I had to remember this this 00:02:14.989 --> 00:02:18.940 align:start position:0% keyring I had to remember this this morning<00:02:16.540> after<00:02:17.540> copying<00:02:18.110> the<00:02:18.230> twelve<00:02:18.470> words<00:02:18.739> C 00:02:18.940 --> 00:02:18.950 align:start position:0% morning after copying the twelve words C 00:02:18.950 --> 00:02:22.089 align:start position:0% morning after copying the twelve words C phrase<00:02:19.250> to<00:02:19.459> a<00:02:19.489> safe<00:02:19.790> spots<00:02:20.209> we<00:02:21.140> now<00:02:21.319> head<00:02:21.860> over 00:02:22.089 --> 00:02:22.099 align:start position:0% phrase to a safe spots we now head over 00:02:22.099 --> 00:02:24.819 align:start position:0% phrase to a safe spots we now head over to<00:02:22.220> token<00:02:22.549> factory<00:02:22.970> which<00:02:23.360> is<00:02:23.660> a<00:02:23.720> DAP<00:02:24.410> that 00:02:24.819 --> 00:02:24.829 align:start position:0% to token factory which is a DAP that 00:02:24.829 --> 00:02:28.780 align:start position:0% to token factory which is a DAP that generates<00:02:25.310> your<00:02:25.640> own<00:02:25.849> tokens<00:02:27.340> we<00:02:28.340> go<00:02:28.489> through 00:02:28.780 --> 00:02:28.790 align:start position:0% generates your own tokens we go through 00:02:28.790 --> 00:02:32.259 align:start position:0% generates your own tokens we go through we<00:02:29.030> fill<00:02:29.269> it<00:02:29.390> out<00:02:30.129> we<00:02:31.129> hit<00:02:31.340> create<00:02:31.549> token<00:02:32.060> and 00:02:32.259 --> 00:02:32.269 align:start position:0% we fill it out we hit create token and 00:02:32.269 --> 00:02:34.660 align:start position:0% we fill it out we hit create token and our<00:02:32.840> beautiful<00:02:33.440> meta<00:02:33.860> mouse<00:02:34.040> confirmation 00:02:34.660 --> 00:02:34.670 align:start position:0% our beautiful meta mouse confirmation 00:02:34.670 --> 00:02:37.210 align:start position:0% our beautiful meta mouse confirmation screen<00:02:35.030> will<00:02:35.390> pop<00:02:35.599> up<00:02:35.660> and<00:02:36.170> you<00:02:36.230> can<00:02:37.069> either 00:02:37.210 --> 00:02:37.220 align:start position:0% screen will pop up and you can either 00:02:37.220 --> 00:02:39.699 align:start position:0% screen will pop up and you can either accept<00:02:37.519> or<00:02:37.970> reject<00:02:38.150> it<00:02:38.480> now<00:02:38.750> in<00:02:39.140> the<00:02:39.290> case<00:02:39.500> that 00:02:39.699 --> 00:02:39.709 align:start position:0% accept or reject it now in the case that 00:02:39.709 --> 00:02:42.250 align:start position:0% accept or reject it now in the case that you<00:02:39.980> don't<00:02:40.280> have<00:02:40.519> enough<00:02:40.760> either<00:02:41.000> a<00:02:41.480> by<00:02:41.900> ether 00:02:42.250 --> 00:02:42.260 align:start position:0% you don't have enough either a by ether 00:02:42.260 --> 00:02:44.140 align:start position:0% you don't have enough either a by ether button<00:02:42.620> will<00:02:42.769> pop<00:02:42.799> up<00:02:43.040> and<00:02:43.400> you<00:02:43.489> have<00:02:43.819> two 00:02:44.140 --> 00:02:44.150 align:start position:0% button will pop up and you have two 00:02:44.150 --> 00:02:45.970 align:start position:0% button will pop up and you have two options<00:02:44.690> if<00:02:44.930> you're<00:02:45.319> in<00:02:45.410> the<00:02:45.500> u.s.<00:02:45.769> you<00:02:45.799> have 00:02:45.970 --> 00:02:45.980 align:start position:0% options if you're in the u.s. you have 00:02:45.980 --> 00:02:49.059 align:start position:0% options if you're in the u.s. you have coin<00:02:46.340> boosts<00:02:46.549> or<00:02:46.760> you<00:02:46.910> have<00:02:47.030> shape-shift<00:02:48.069> very 00:02:49.059 --> 00:02:49.069 align:start position:0% coin boosts or you have shape-shift very 00:02:49.069 --> 00:02:52.599 align:start position:0% coin boosts or you have shape-shift very simple<00:02:49.549> just<00:02:49.790> enter<00:02:50.209> your<00:02:50.239> email<00:02:50.599> in<00:02:51.609> confirm 00:02:52.599 --> 00:02:52.609 align:start position:0% simple just enter your email in confirm 00:02:52.609 --> 00:02:54.879 align:start position:0% simple just enter your email in confirm your<00:02:52.760> email<00:02:53.200> enter<00:02:54.200> your<00:02:54.319> phone<00:02:54.500> number 00:02:54.879 --> 00:02:54.889 align:start position:0% your email enter your phone number 00:02:54.889 --> 00:02:57.430 align:start position:0% your email enter your phone number confirm<00:02:55.430> phone<00:02:55.670> number<00:02:56.000> and<00:02:56.209> then<00:02:56.810> enter<00:02:57.290> your 00:02:57.430 --> 00:02:57.440 align:start position:0% confirm phone number and then enter your 00:02:57.440 --> 00:02:59.050 align:start position:0% confirm phone number and then enter your credit<00:02:57.620> card<00:02:57.799> trans<00:02:58.190> or<00:02:58.489> credit<00:02:58.849> card 00:02:59.050 --> 00:02:59.060 align:start position:0% credit card trans or credit card 00:02:59.060 --> 00:03:01.990 align:start position:0% credit card trans or credit card information<00:02:59.480> this<00:03:00.319> has<00:03:00.380> a<00:03:00.680> five<00:03:01.130> dollar<00:03:01.519> a<00:03:01.639> day 00:03:01.990 --> 00:03:02.000 align:start position:0% information this has a five dollar a day 00:03:02.000 --> 00:03:05.589 align:start position:0% information this has a five dollar a day limit<00:03:03.160> very<00:03:04.160> and<00:03:04.669> goes<00:03:05.000> straight<00:03:05.180> to<00:03:05.359> your 00:03:05.589 --> 00:03:05.599 align:start position:0% limit very and goes straight to your 00:03:05.599 --> 00:03:10.509 align:start position:0% limit very and goes straight to your account<00:03:07.569> unfortunately<00:03:09.130> when<00:03:10.130> you<00:03:10.220> get<00:03:10.370> there 00:03:10.509 --> 00:03:10.519 align:start position:0% account unfortunately when you get there 00:03:10.519 --> 00:03:11.830 align:start position:0% account unfortunately when you get there you<00:03:10.609> can<00:03:10.639> accept<00:03:11.090> and<00:03:11.209> reject<00:03:11.329> once<00:03:11.720> you've 00:03:11.830 --> 00:03:11.840 align:start position:0% you can accept and reject once you've 00:03:11.840 --> 00:03:13.059 align:start position:0% you can accept and reject once you've gotten<00:03:11.989> your<00:03:12.079> either<00:03:12.349> will<00:03:12.650> hold<00:03:12.919> the 00:03:13.059 --> 00:03:13.069 align:start position:0% gotten your either will hold the 00:03:13.069 --> 00:03:15.220 align:start position:0% gotten your either will hold the transaction<00:03:13.730> and<00:03:13.970> voila<00:03:14.269> you've<00:03:15.019> created 00:03:15.220 --> 00:03:15.230 align:start position:0% transaction and voila you've created 00:03:15.230 --> 00:03:18.250 align:start position:0% transaction and voila you've created your<00:03:15.500> token<00:03:16.120> unfortunately<00:03:17.120> though<00:03:17.329> if<00:03:17.810> you 00:03:18.250 --> 00:03:18.260 align:start position:0% your token unfortunately though if you 00:03:18.260 --> 00:03:20.860 align:start position:0% your token unfortunately though if you are<00:03:18.609> not<00:03:19.609> in<00:03:19.819> the<00:03:19.970> u.s.<00:03:20.239> you<00:03:20.480> don't<00:03:20.660> have 00:03:20.860 --> 00:03:20.870 align:start position:0% are not in the u.s. you don't have 00:03:20.870 --> 00:03:22.000 align:start position:0% are not in the u.s. you don't have access<00:03:21.380> to<00:03:21.530> coinbase 00:03:22.000 --> 00:03:22.010 align:start position:0% access to coinbase 00:03:22.010 --> 00:03:24.610 align:start position:0% access to coinbase so<00:03:22.310> if<00:03:22.430> you<00:03:22.579> guys<00:03:22.730> know<00:03:23.090> any<00:03:23.450> products<00:03:24.260> or<00:03:24.440> are 00:03:24.610 --> 00:03:24.620 align:start position:0% so if you guys know any products or are 00:03:24.620 --> 00:03:27.460 align:start position:0% so if you guys know any products or are working<00:03:24.950> on<00:03:25.069> something<00:03:25.430> that<00:03:25.609> offers<00:03:26.019> fiat<00:03:27.019> to 00:03:27.460 --> 00:03:27.470 align:start position:0% working on something that offers fiat to 00:03:27.470 --> 00:03:29.620 align:start position:0% working on something that offers fiat to ease<00:03:27.739> that<00:03:28.340> would<00:03:28.489> be<00:03:28.579> amazing<00:03:28.849> please<00:03:29.329> come 00:03:29.620 --> 00:03:29.630 align:start position:0% ease that would be amazing please come 00:03:29.630 --> 00:03:31.210 align:start position:0% ease that would be amazing please come talk<00:03:29.810> to<00:03:30.109> us<00:03:30.230> we<00:03:30.380> would<00:03:30.500> love<00:03:30.709> to<00:03:30.889> hear<00:03:31.010> from 00:03:31.210 --> 00:03:31.220 align:start position:0% talk to us we would love to hear from 00:03:31.220 --> 00:03:34.650 align:start position:0% talk to us we would love to hear from you<00:03:31.750> our<00:03:32.750> status<00:03:33.349> right<00:03:33.500> now<00:03:33.560> is<00:03:33.829> public<00:03:34.010> beta 00:03:34.650 --> 00:03:34.660 align:start position:0% you our status right now is public beta 00:03:34.660 --> 00:03:39.009 align:start position:0% you our status right now is public beta we<00:03:35.660> have<00:03:35.900> we<00:03:36.590> have<00:03:37.190> done<00:03:37.220> 44<00:03:38.180> releases<00:03:38.750> since 00:03:39.009 --> 00:03:39.019 align:start position:0% we have we have done 44 releases since 00:03:39.019 --> 00:03:41.349 align:start position:0% we have we have done 44 releases since March<00:03:39.470> we<00:03:39.709> have<00:03:39.950> weekly<00:03:40.250> updates<00:03:40.970> we<00:03:41.239> have 00:03:41.349 --> 00:03:41.359 align:start position:0% March we have weekly updates we have 00:03:41.359 --> 00:03:44.740 align:start position:0% March we have weekly updates we have over<00:03:41.540> 2000<00:03:42.290> users<00:03:42.680> and<00:03:42.950> 14<00:03:43.700> million<00:03:43.940> RPC 00:03:44.740 --> 00:03:44.750 align:start position:0% over 2000 users and 14 million RPC 00:03:44.750 --> 00:03:49.330 align:start position:0% over 2000 users and 14 million RPC requests<00:03:45.139> per<00:03:45.379> day<00:03:45.410> thanks<00:03:46.220> to<00:03:46.250> and<00:03:46.519> Fira<00:03:48.340> we 00:03:49.330 --> 00:03:49.340 align:start position:0% requests per day thanks to and Fira we 00:03:49.340 --> 00:03:52.930 align:start position:0% requests per day thanks to and Fira we are<00:03:49.609> chrome<00:03:50.000> live<00:03:50.470> opera<00:03:51.470> edge<00:03:51.739> and<00:03:52.220> Firefox 00:03:52.930 --> 00:03:52.940 align:start position:0% are chrome live opera edge and Firefox 00:03:52.940 --> 00:03:54.939 align:start position:0% are chrome live opera edge and Firefox we<00:03:53.329> are<00:03:53.449> pending<00:03:53.989> and<00:03:54.229> ready<00:03:54.500> we're<00:03:54.739> just 00:03:54.939 --> 00:03:54.949 align:start position:0% we are pending and ready we're just 00:03:54.949 --> 00:03:56.890 align:start position:0% we are pending and ready we're just going<00:03:55.190> through<00:03:55.220> the<00:03:55.789> process<00:03:56.329> of<00:03:56.479> getting<00:03:56.630> it 00:03:56.890 --> 00:03:56.900 align:start position:0% going through the process of getting it 00:03:56.900 --> 00:03:59.630 align:start position:0% going through the process of getting it into<00:03:57.079> the 00:03:59.630 --> 00:03:59.640 align:start position:0% into the 00:03:59.640 --> 00:04:03.060 align:start position:0% into the extension<00:04:00.640> storm<00:04:01.740> unfortunately<00:04:02.740> we<00:04:02.920> won't 00:04:03.060 --> 00:04:03.070 align:start position:0% extension storm unfortunately we won't 00:04:03.070 --> 00:04:05.040 align:start position:0% extension storm unfortunately we won't really<00:04:03.400> be<00:04:03.520> pursuing<00:04:04.060> Safari<00:04:04.480> they<00:04:04.720> don't 00:04:05.040 --> 00:04:05.050 align:start position:0% really be pursuing Safari they don't 00:04:05.050 --> 00:04:07.170 align:start position:0% really be pursuing Safari they don't follow<00:04:05.290> the<00:04:05.470> extension<00:04:06.100> standards<00:04:06.640> and<00:04:06.850> as 00:04:07.170 --> 00:04:07.180 align:start position:0% follow the extension standards and as 00:04:07.180 --> 00:04:09.990 align:start position:0% follow the extension standards and as far<00:04:07.330> as<00:04:07.390> mobile<00:04:07.810> goes<00:04:08.080> it's<00:04:08.740> hard<00:04:09.070> to<00:04:09.310> get<00:04:09.640> we 00:04:09.990 --> 00:04:10.000 align:start position:0% far as mobile goes it's hard to get we 00:04:10.000 --> 00:04:13.860 align:start position:0% far as mobile goes it's hard to get we really<00:04:10.510> don't<00:04:10.810> have<00:04:10.960> any<00:04:11.730> mobile<00:04:12.870> browsers 00:04:13.860 --> 00:04:13.870 align:start position:0% really don't have any mobile browsers 00:04:13.870 --> 00:04:17.099 align:start position:0% really don't have any mobile browsers that<00:04:13.990> support<00:04:14.250> extensions<00:04:15.250> and<00:04:15.720> now<00:04:16.720> to<00:04:16.780> talk 00:04:17.099 --> 00:04:17.109 align:start position:0% that support extensions and now to talk 00:04:17.109 --> 00:04:18.240 align:start position:0% that support extensions and now to talk about<00:04:17.320> how<00:04:17.440> it<00:04:17.560> works<00:04:17.709> I'd<00:04:17.859> like<00:04:17.980> to<00:04:18.100> pass<00:04:18.220> it 00:04:18.240 --> 00:04:18.250 align:start position:0% about how it works I'd like to pass it 00:04:18.250 --> 00:04:25.590 align:start position:0% about how it works I'd like to pass it off<00:04:18.489> to<00:04:18.519> Aaron<00:04:21.570> no<00:04:22.570> no<00:04:23.320> no<00:04:23.590> we're<00:04:24.390> cool 00:04:25.590 --> 00:04:25.600 align:start position:0% off to Aaron no no no we're cool 00:04:25.600 --> 00:04:29.970 align:start position:0% off to Aaron no no no we're cool so<00:04:25.720> minam<00:04:26.380> asked<00:04:26.530> how<00:04:26.770> does<00:04:27.220> it<00:04:27.580> do<00:04:27.760> that<00:04:28.980> so 00:04:29.970 --> 00:04:29.980 align:start position:0% so minam asked how does it do that so 00:04:29.980 --> 00:04:31.830 align:start position:0% so minam asked how does it do that so yeah<00:04:30.430> you<00:04:30.490> wanna<00:04:30.850> you<00:04:31.240> want<00:04:31.390> a<00:04:31.510> theorem<00:04:31.780> in 00:04:31.830 --> 00:04:31.840 align:start position:0% yeah you wanna you want a theorem in 00:04:31.840 --> 00:04:33.420 align:start position:0% yeah you wanna you want a theorem in your<00:04:31.990> browser<00:04:32.170> so<00:04:32.530> just<00:04:32.770> take<00:04:32.980> an<00:04:33.070> F<00:04:33.190> theorem 00:04:33.420 --> 00:04:33.430 align:start position:0% your browser so just take an F theorem 00:04:33.430 --> 00:04:35.780 align:start position:0% your browser so just take an F theorem client<00:04:33.700> and<00:04:33.790> throw<00:04:34.000> in<00:04:34.060> an<00:04:34.330> extension<00:04:35.050> right 00:04:35.780 --> 00:04:35.790 align:start position:0% client and throw in an extension right 00:04:35.790 --> 00:04:37.230 align:start position:0% client and throw in an extension right unfortunately<00:04:36.790> that<00:04:36.880> won't<00:04:36.970> quite<00:04:37.180> work 00:04:37.230 --> 00:04:37.240 align:start position:0% unfortunately that won't quite work 00:04:37.240 --> 00:04:39.150 align:start position:0% unfortunately that won't quite work you're<00:04:37.870> blocked<00:04:38.080> on<00:04:38.200> networking<00:04:38.500> the 00:04:39.150 --> 00:04:39.160 align:start position:0% you're blocked on networking the 00:04:39.160 --> 00:04:41.700 align:start position:0% you're blocked on networking the networking<00:04:39.430> uses<00:04:39.880> TCP<00:04:40.630> UDP<00:04:40.810> you<00:04:41.200> don't<00:04:41.590> have 00:04:41.700 --> 00:04:41.710 align:start position:0% networking uses TCP UDP you don't have 00:04:41.710 --> 00:04:43.800 align:start position:0% networking uses TCP UDP you don't have access<00:04:42.070> to<00:04:42.280> that<00:04:42.430> in<00:04:42.520> the<00:04:42.580> browser<00:04:42.730> even<00:04:43.690> in 00:04:43.800 --> 00:04:43.810 align:start position:0% access to that in the browser even in 00:04:43.810 --> 00:04:47.040 align:start position:0% access to that in the browser even in extensions<00:04:45.060> so<00:04:46.060> what<00:04:46.660> are<00:04:46.720> you<00:04:46.780> gonna<00:04:46.900> do 00:04:47.040 --> 00:04:47.050 align:start position:0% extensions so what are you gonna do 00:04:47.050 --> 00:04:49.950 align:start position:0% extensions so what are you gonna do inside<00:04:47.290> oh<00:04:47.440> yes<00:04:47.800> also<00:04:48.130> for<00:04:48.760> the<00:04:48.970> kind<00:04:49.870> of 00:04:49.950 --> 00:04:49.960 align:start position:0% inside oh yes also for the kind of 00:04:49.960 --> 00:04:52.140 align:start position:0% inside oh yes also for the kind of adoption<00:04:50.260> flow<00:04:50.680> we're<00:04:50.830> looking<00:04:51.100> for<00:04:51.370> the 00:04:52.140 --> 00:04:52.150 align:start position:0% adoption flow we're looking for the 00:04:52.150 --> 00:04:53.730 align:start position:0% adoption flow we're looking for the mandatory<00:04:52.450> sink<00:04:52.840> time<00:04:53.110> is<00:04:53.350> kind<00:04:53.650> of<00:04:53.710> a 00:04:53.730 --> 00:04:53.740 align:start position:0% mandatory sink time is kind of a 00:04:53.740 --> 00:04:55.560 align:start position:0% mandatory sink time is kind of a non-starter<00:04:53.919> I<00:04:54.460> mean<00:04:55.000> the<00:04:55.120> light<00:04:55.270> client 00:04:55.560 --> 00:04:55.570 align:start position:0% non-starter I mean the light client 00:04:55.570 --> 00:04:58.159 align:start position:0% non-starter I mean the light client protocol<00:04:55.870> has<00:04:55.990> improved<00:04:56.260> that<00:04:56.470> significantly 00:04:58.159 --> 00:04:58.169 align:start position:0% protocol has improved that significantly 00:04:58.169 --> 00:05:00.570 align:start position:0% protocol has improved that significantly but<00:04:59.169> so<00:04:59.470> what<00:04:59.620> are<00:04:59.710> we<00:04:59.770> left<00:04:59.890> with<00:04:59.980> we<00:05:00.370> can<00:05:00.490> do 00:05:00.570 --> 00:05:00.580 align:start position:0% but so what are we left with we can do 00:05:00.580 --> 00:05:02.580 align:start position:0% but so what are we left with we can do RPC<00:05:01.240> against<00:05:01.510> a<00:05:01.570> trusted<00:05:01.900> node<00:05:02.050> where<00:05:02.410> we'll 00:05:02.580 --> 00:05:02.590 align:start position:0% RPC against a trusted node where we'll 00:05:02.590 --> 00:05:04.770 align:start position:0% RPC against a trusted node where we'll run<00:05:02.860> the<00:05:03.010> nodes<00:05:03.190> for<00:05:03.460> you<00:05:03.580> and<00:05:03.820> so<00:05:04.600> you<00:05:04.690> have 00:05:04.770 --> 00:05:04.780 align:start position:0% run the nodes for you and so you have 00:05:04.780 --> 00:05:07.230 align:start position:0% run the nodes for you and so you have the<00:05:04.900> zero<00:05:05.110> sync<00:05:05.350> time<00:05:05.610> what<00:05:06.610> do<00:05:06.669> you<00:05:06.730> do<00:05:06.820> for<00:05:07.030> ID 00:05:07.230 --> 00:05:07.240 align:start position:0% the zero sync time what do you do for ID 00:05:07.240 --> 00:05:09.750 align:start position:0% the zero sync time what do you do for ID management<00:05:07.780> we<00:05:08.169> do<00:05:08.290> RPC<00:05:08.980> interception<00:05:09.550> so 00:05:09.750 --> 00:05:09.760 align:start position:0% management we do RPC interception so 00:05:09.760 --> 00:05:11.640 align:start position:0% management we do RPC interception so anything<00:05:10.150> like<00:05:10.330> send<00:05:10.600> transaction<00:05:11.230> or<00:05:11.410> said 00:05:11.640 --> 00:05:11.650 align:start position:0% anything like send transaction or said 00:05:11.650 --> 00:05:13.500 align:start position:0% anything like send transaction or said signing<00:05:12.130> a<00:05:12.190> message<00:05:12.490> that<00:05:12.700> involves<00:05:13.000> usage<00:05:13.330> of 00:05:13.500 --> 00:05:13.510 align:start position:0% signing a message that involves usage of 00:05:13.510 --> 00:05:18.870 align:start position:0% signing a message that involves usage of private<00:05:13.840> keys<00:05:14.370> we<00:05:15.660> intercept<00:05:16.660> that<00:05:17.760> sign<00:05:18.760> the 00:05:18.870 --> 00:05:18.880 align:start position:0% private keys we intercept that sign the 00:05:18.880 --> 00:05:20.700 align:start position:0% private keys we intercept that sign the transaction<00:05:19.390> and<00:05:19.479> pass<00:05:19.660> that<00:05:19.840> on<00:05:19.990> it's<00:05:20.200> a<00:05:20.320> raw 00:05:20.700 --> 00:05:20.710 align:start position:0% transaction and pass that on it's a raw 00:05:20.710 --> 00:05:23.670 align:start position:0% transaction and pass that on it's a raw transaction<00:05:21.340> to<00:05:21.490> the<00:05:21.610> trusted<00:05:21.970> endpoint<00:05:22.680> so 00:05:23.670 --> 00:05:23.680 align:start position:0% transaction to the trusted endpoint so 00:05:23.680 --> 00:05:26.130 align:start position:0% transaction to the trusted endpoint so here's<00:05:23.919> a<00:05:23.950> little<00:05:24.040> chart<00:05:24.250> of<00:05:24.600> how<00:05:25.600> it<00:05:25.720> works 00:05:26.130 --> 00:05:26.140 align:start position:0% here's a little chart of how it works 00:05:26.140 --> 00:05:27.690 align:start position:0% here's a little chart of how it works you<00:05:26.320> have<00:05:26.440> the<00:05:26.500> user<00:05:26.680> at<00:05:26.860> the<00:05:26.950> top<00:05:27.100> they're 00:05:27.690 --> 00:05:27.700 align:start position:0% you have the user at the top they're 00:05:27.700 --> 00:05:29.760 align:start position:0% you have the user at the top they're looking<00:05:27.970> at<00:05:28.090> the<00:05:28.240> gap<00:05:28.930> in<00:05:29.140> the<00:05:29.229> browser<00:05:29.440> and 00:05:29.760 --> 00:05:29.770 align:start position:0% looking at the gap in the browser and 00:05:29.770 --> 00:05:33.600 align:start position:0% looking at the gap in the browser and the<00:05:30.250> meta<00:05:30.400> mask<00:05:30.640> UI<00:05:31.169> the<00:05:32.169> DAP<00:05:32.320> has<00:05:32.560> the<00:05:33.130> UI<00:05:33.280> code 00:05:33.600 --> 00:05:33.610 align:start position:0% the meta mask UI the DAP has the UI code 00:05:33.610 --> 00:05:36.090 align:start position:0% the meta mask UI the DAP has the UI code in<00:05:33.790> it<00:05:33.940> as<00:05:34.060> well<00:05:34.479> as<00:05:34.600> the<00:05:34.750> web<00:05:34.900> 3<00:05:35.200> injected<00:05:35.979> by 00:05:36.090 --> 00:05:36.100 align:start position:0% in it as well as the web 3 injected by 00:05:36.100 --> 00:05:37.650 align:start position:0% in it as well as the web 3 injected by meta<00:05:36.310> mask<00:05:36.490> much<00:05:36.850> like<00:05:37.060> you'd<00:05:37.210> see<00:05:37.360> in<00:05:37.390> mist 00:05:37.650 --> 00:05:37.660 align:start position:0% meta mask much like you'd see in mist 00:05:37.660 --> 00:05:41.880 align:start position:0% meta mask much like you'd see in mist the<00:05:38.620> web<00:05:38.740> 3<00:05:39.330> generates<00:05:40.330> RPC<00:05:40.930> requests<00:05:41.410> that 00:05:41.880 --> 00:05:41.890 align:start position:0% the web 3 generates RPC requests that 00:05:41.890 --> 00:05:44.820 align:start position:0% the web 3 generates RPC requests that are<00:05:41.950> forwarded<00:05:42.430> on<00:05:42.520> to<00:05:42.550> the<00:05:42.790> background<00:05:43.830> this 00:05:44.820 --> 00:05:44.830 align:start position:0% are forwarded on to the background this 00:05:44.830 --> 00:05:46.200 align:start position:0% are forwarded on to the background this goes<00:05:45.040> to<00:05:45.160> the<00:05:45.250> provider<00:05:45.580> engine<00:05:45.880> which<00:05:46.030> I'll 00:05:46.200 --> 00:05:46.210 align:start position:0% goes to the provider engine which I'll 00:05:46.210 --> 00:05:48.330 align:start position:0% goes to the provider engine which I'll explain<00:05:46.300> in<00:05:46.630> a<00:05:46.690> second<00:05:46.990> and<00:05:47.169> and<00:05:47.650> onwards<00:05:48.130> on 00:05:48.330 --> 00:05:48.340 align:start position:0% explain in a second and and onwards on 00:05:48.340 --> 00:05:51.960 align:start position:0% explain in a second and and onwards on to<00:05:48.520> the<00:05:48.640> trusted<00:05:49.240> RPC<00:05:50.370> so<00:05:51.370> the<00:05:51.669> provider 00:05:51.960 --> 00:05:51.970 align:start position:0% to the trusted RPC so the provider 00:05:51.970 --> 00:05:54.540 align:start position:0% to the trusted RPC so the provider engine<00:05:52.300> is<00:05:52.540> a<00:05:52.570> tool<00:05:52.979> for<00:05:53.979> making<00:05:54.070> your<00:05:54.310> own<00:05:54.340> web 00:05:54.540 --> 00:05:54.550 align:start position:0% engine is a tool for making your own web 00:05:54.550 --> 00:05:57.420 align:start position:0% engine is a tool for making your own web 3<00:05:54.820> provider<00:05:55.240> it's<00:05:55.780> basically<00:05:56.169> a<00:05:56.290> stack<00:05:56.800> of<00:05:56.830> RPC 00:05:57.420 --> 00:05:57.430 align:start position:0% 3 provider it's basically a stack of RPC 00:05:57.430 --> 00:05:59.700 align:start position:0% 3 provider it's basically a stack of RPC handling<00:05:58.210> middleware<00:05:58.600> might<00:05:59.470> look<00:05:59.560> something 00:05:59.700 --> 00:05:59.710 align:start position:0% handling middleware might look something 00:05:59.710 --> 00:06:01.230 align:start position:0% handling middleware might look something like<00:05:59.860> this<00:06:00.100> you<00:06:00.280> have<00:06:00.310> a<00:06:00.430> cache<00:06:00.640> layer<00:06:00.940> for 00:06:01.230 --> 00:06:01.240 align:start position:0% like this you have a cache layer for 00:06:01.240 --> 00:06:03.030 align:start position:0% like this you have a cache layer for example<00:06:01.270> if<00:06:01.600> you're<00:06:01.720> asking<00:06:02.470> for<00:06:02.500> the<00:06:02.680> balance 00:06:03.030 --> 00:06:03.040 align:start position:0% example if you're asking for the balance 00:06:03.040 --> 00:06:04.650 align:start position:0% example if you're asking for the balance of<00:06:03.160> an<00:06:03.280> account<00:06:03.550> twice<00:06:03.880> in<00:06:04.090> the<00:06:04.210> same<00:06:04.390> block 00:06:04.650 --> 00:06:04.660 align:start position:0% of an account twice in the same block 00:06:04.660 --> 00:06:06.659 align:start position:0% of an account twice in the same block it's<00:06:04.990> it's<00:06:05.650> going<00:06:05.860> to<00:06:05.979> be<00:06:06.070> the<00:06:06.190> same<00:06:06.370> you<00:06:06.400> don't 00:06:06.659 --> 00:06:06.669 align:start position:0% it's it's going to be the same you don't 00:06:06.669 --> 00:06:08.490 align:start position:0% it's it's going to be the same you don't need<00:06:06.849> to<00:06:06.940> hit<00:06:07.270> the<00:06:07.360> network<00:06:07.599> for<00:06:07.780> that<00:06:07.930> then 00:06:08.490 --> 00:06:08.500 align:start position:0% need to hit the network for that then 00:06:08.500 --> 00:06:09.999 align:start position:0% need to hit the network for that then you<00:06:08.590> got<00:06:08.710> your<00:06:08.830> idea<00:06:09.070> man 00:06:09.999 --> 00:06:10.009 align:start position:0% you got your idea man 00:06:10.009 --> 00:06:11.499 align:start position:0% you got your idea man you<00:06:10.069> management<00:06:10.339> that's<00:06:10.969> where<00:06:11.150> your<00:06:11.270> private 00:06:11.499 --> 00:06:11.509 align:start position:0% you management that's where your private 00:06:11.509 --> 00:06:13.570 align:start position:0% you management that's where your private keys<00:06:11.689> are<00:06:11.869> and<00:06:12.080> then<00:06:12.559> the<00:06:13.129> rest<00:06:13.309> of<00:06:13.339> the<00:06:13.430> data 00:06:13.570 --> 00:06:13.580 align:start position:0% keys are and then the rest of the data 00:06:13.580 --> 00:06:15.369 align:start position:0% keys are and then the rest of the data lookups<00:06:13.969> fall<00:06:14.150> back<00:06:14.330> to<00:06:14.479> the<00:06:14.569> right<00:06:14.809> to<00:06:15.289> the 00:06:15.369 --> 00:06:15.379 align:start position:0% lookups fall back to the right to the 00:06:15.379 --> 00:06:19.209 align:start position:0% lookups fall back to the right to the node<00:06:16.419> a<00:06:17.419> node<00:06:17.930> on<00:06:18.229> filters<00:06:18.979> and<00:06:19.129> load 00:06:19.209 --> 00:06:19.219 align:start position:0% node a node on filters and load 00:06:19.219 --> 00:06:21.189 align:start position:0% node a node on filters and load balancers<00:06:19.580> filters<00:06:19.969> you<00:06:20.449> install<00:06:20.930> them<00:06:21.169> and 00:06:21.189 --> 00:06:21.199 align:start position:0% balancers filters you install them and 00:06:21.199 --> 00:06:23.170 align:start position:0% balancers filters you install them and then<00:06:21.619> you<00:06:21.740> check<00:06:22.009> them<00:06:22.219> you<00:06:22.580> pull<00:06:22.819> against 00:06:23.170 --> 00:06:23.180 align:start position:0% then you check them you pull against 00:06:23.180 --> 00:06:25.149 align:start position:0% then you check them you pull against them<00:06:23.330> as<00:06:23.990> soon<00:06:24.199> as<00:06:24.289> you<00:06:24.379> start<00:06:24.619> using<00:06:24.740> a<00:06:24.979> load 00:06:25.149 --> 00:06:25.159 align:start position:0% them as soon as you start using a load 00:06:25.159 --> 00:06:26.529 align:start position:0% them as soon as you start using a load balancer<00:06:25.339> like<00:06:25.849> we<00:06:25.969> do<00:06:26.119> where<00:06:26.300> we<00:06:26.389> have<00:06:26.509> a 00:06:26.529 --> 00:06:26.539 align:start position:0% balancer like we do where we have a 00:06:26.539 --> 00:06:28.119 align:start position:0% balancer like we do where we have a bunch<00:06:26.719> of<00:06:26.779> get<00:06:26.930> nodes<00:06:27.169> you'll<00:06:27.680> you'll<00:06:27.949> end<00:06:28.069> up 00:06:28.119 --> 00:06:28.129 align:start position:0% bunch of get nodes you'll you'll end up 00:06:28.129 --> 00:06:29.469 align:start position:0% bunch of get nodes you'll you'll end up installing<00:06:28.399> on<00:06:28.729> one<00:06:28.909> machine<00:06:29.059> and<00:06:29.360> then 00:06:29.469 --> 00:06:29.479 align:start position:0% installing on one machine and then 00:06:29.479 --> 00:06:31.119 align:start position:0% installing on one machine and then checking<00:06:29.809> on<00:06:29.899> another<00:06:29.930> but<00:06:30.680> this<00:06:30.800> turns<00:06:31.009> out 00:06:31.119 --> 00:06:31.129 align:start position:0% checking on another but this turns out 00:06:31.129 --> 00:06:32.409 align:start position:0% checking on another but this turns out to<00:06:31.219> be<00:06:31.249> something<00:06:31.580> that's<00:06:31.669> pretty<00:06:31.999> easy<00:06:32.119> to 00:06:32.409 --> 00:06:32.419 align:start position:0% to be something that's pretty easy to 00:06:32.419 --> 00:06:34.989 align:start position:0% to be something that's pretty easy to simpl<00:06:32.779> pretty<00:06:33.409> simple<00:06:33.979> to<00:06:34.189> solve<00:06:34.399> in<00:06:34.729> the 00:06:34.989 --> 00:06:34.999 align:start position:0% simpl pretty simple to solve in the 00:06:34.999 --> 00:06:39.489 align:start position:0% simpl pretty simple to solve in the provider<00:06:35.419> engine<00:06:35.779> level<00:06:37.449> so<00:06:38.449> meadow<00:06:39.169> Maps<00:06:39.349> has 00:06:39.489 --> 00:06:39.499 align:start position:0% provider engine level so meadow Maps has 00:06:39.499 --> 00:06:41.320 align:start position:0% provider engine level so meadow Maps has a<00:06:39.529> bit<00:06:39.740> of<00:06:39.830> a<00:06:39.919> different<00:06:40.219> trust<00:06:40.460> model<00:06:40.849> then 00:06:41.320 --> 00:06:41.330 align:start position:0% a bit of a different trust model then 00:06:41.330 --> 00:06:45.399 align:start position:0% a bit of a different trust model then say<00:06:41.990> myst<00:06:42.819> because<00:06:43.819> we<00:06:43.999> provide<00:06:44.259> out<00:06:45.259> of<00:06:45.289> the 00:06:45.399 --> 00:06:45.409 align:start position:0% say myst because we provide out of the 00:06:45.409 --> 00:06:48.899 align:start position:0% say myst because we provide out of the box<00:06:45.469> by<00:06:45.889> default<00:06:46.279> these<00:06:46.490> the<00:06:47.479> trusted<00:06:47.899> nodes 00:06:48.899 --> 00:06:48.909 align:start position:0% box by default these the trusted nodes 00:06:48.909 --> 00:06:51.309 align:start position:0% box by default these the trusted nodes the<00:06:49.909> yeah<00:06:50.270> the<00:06:50.449> trust<00:06:50.659> model<00:06:50.749> is<00:06:50.990> different 00:06:51.309 --> 00:06:51.319 align:start position:0% the yeah the trust model is different 00:06:51.319 --> 00:06:54.760 align:start position:0% the yeah the trust model is different but<00:06:52.120> we<00:06:53.120> could<00:06:53.389> add<00:06:53.629> optimizations<00:06:54.409> and<00:06:54.620> new 00:06:54.760 --> 00:06:54.770 align:start position:0% but we could add optimizations and new 00:06:54.770 --> 00:06:56.589 align:start position:0% but we could add optimizations and new features<00:06:55.069> quite<00:06:55.249> easily<00:06:55.550> using<00:06:56.089> custom<00:06:56.479> API 00:06:56.589 --> 00:06:56.599 align:start position:0% features quite easily using custom API 00:06:56.599 --> 00:07:00.369 align:start position:0% features quite easily using custom API but<00:06:57.529> we<00:06:57.710> want<00:06:57.919> you<00:06:58.069> to<00:06:58.249> be<00:06:58.370> able<00:06:58.490> to<00:06:59.379> switch 00:07:00.369 --> 00:07:00.379 align:start position:0% but we want you to be able to switch 00:07:00.379 --> 00:07:02.079 align:start position:0% but we want you to be able to switch over<00:07:00.499> to<00:07:00.649> your<00:07:00.919> own<00:07:01.069> local<00:07:01.309> node<00:07:01.580> at<00:07:01.729> any<00:07:01.849> time 00:07:02.079 --> 00:07:02.089 align:start position:0% over to your own local node at any time 00:07:02.089 --> 00:07:07.600 align:start position:0% over to your own local node at any time if<00:07:02.240> you<00:07:02.270> want<00:07:02.539> so<00:07:03.529> we<00:07:03.949> use<00:07:04.159> 100%<00:07:04.809> RPC<00:07:06.610> to 00:07:07.600 --> 00:07:07.610 align:start position:0% if you want so we use 100% RPC to 00:07:07.610 --> 00:07:10.570 align:start position:0% if you want so we use 100% RPC to maintain<00:07:08.240> that<00:07:08.360> standard<00:07:09.309> again<00:07:10.309> if<00:07:10.430> we<00:07:10.550> use 00:07:10.570 --> 00:07:10.580 align:start position:0% maintain that standard again if we use 00:07:10.580 --> 00:07:12.429 align:start position:0% maintain that standard again if we use custom<00:07:11.029> api<00:07:11.300> you'd<00:07:11.569> kind<00:07:11.809> of<00:07:11.839> be<00:07:11.899> locked<00:07:12.229> into 00:07:12.429 --> 00:07:12.439 align:start position:0% custom api you'd kind of be locked into 00:07:12.439 --> 00:07:14.829 align:start position:0% custom api you'd kind of be locked into our<00:07:12.949> metamath<00:07:13.610> servers<00:07:13.969> and<00:07:14.120> we<00:07:14.209> think<00:07:14.449> the 00:07:14.829 --> 00:07:14.839 align:start position:0% our metamath servers and we think the 00:07:14.839 --> 00:07:19.029 align:start position:0% our metamath servers and we think the lock-in<00:07:15.050> sort<00:07:15.559> of<00:07:15.620> devalues<00:07:16.009> the<00:07:16.039> product<00:07:18.039> and 00:07:19.029 --> 00:07:19.039 align:start position:0% lock-in sort of devalues the product and 00:07:19.039 --> 00:07:20.739 align:start position:0% lock-in sort of devalues the product and now<00:07:19.159> Dan's<00:07:19.430> been<00:07:19.639> talked<00:07:19.789> about<00:07:19.819> the<00:07:20.029> lessons 00:07:20.739 --> 00:07:20.749 align:start position:0% now Dan's been talked about the lessons 00:07:20.749 --> 00:07:24.670 align:start position:0% now Dan's been talked about the lessons from<00:07:20.990> working<00:07:21.680> with<00:07:21.709> Def<00:07:21.979> developers<00:07:23.680> thanks 00:07:24.670 --> 00:07:24.680 align:start position:0% from working with Def developers thanks 00:07:24.680 --> 00:07:30.040 align:start position:0% from working with Def developers thanks Aaron<00:07:27.129> hey<00:07:28.129> guys<00:07:28.339> so<00:07:29.120> since<00:07:29.479> we<00:07:29.599> make<00:07:29.839> a 00:07:30.040 --> 00:07:30.050 align:start position:0% Aaron hey guys so since we make a 00:07:30.050 --> 00:07:32.139 align:start position:0% Aaron hey guys so since we make a product<00:07:30.620> that<00:07:30.800> injects<00:07:31.189> web<00:07:31.399> 3<00:07:31.759> into<00:07:32.120> a 00:07:32.139 --> 00:07:32.149 align:start position:0% product that injects web 3 into a 00:07:32.149 --> 00:07:34.299 align:start position:0% product that injects web 3 into a browser<00:07:32.599> we<00:07:32.899> get<00:07:33.050> to<00:07:33.169> talk<00:07:33.349> to<00:07:33.559> web<00:07:33.860> developers 00:07:34.299 --> 00:07:34.309 align:start position:0% browser we get to talk to web developers 00:07:34.309 --> 00:07:36.579 align:start position:0% browser we get to talk to web developers pretty<00:07:34.639> much<00:07:34.789> all<00:07:34.939> day<00:07:34.969> and<00:07:35.419> that's<00:07:36.050> great 00:07:36.579 --> 00:07:36.589 align:start position:0% pretty much all day and that's great 00:07:36.589 --> 00:07:38.889 align:start position:0% pretty much all day and that's great not<00:07:37.189> just<00:07:37.370> web<00:07:37.490> developers<00:07:37.909> web<00:07:38.089> developers 00:07:38.889 --> 00:07:38.899 align:start position:0% not just web developers web developers 00:07:38.899 --> 00:07:41.469 align:start position:0% not just web developers web developers and<00:07:39.139> so<00:07:39.379> we<00:07:39.499> hear<00:07:39.740> cool<00:07:40.159> projects<00:07:40.849> and<00:07:40.999> that 00:07:41.469 --> 00:07:41.479 align:start position:0% and so we hear cool projects and that 00:07:41.479 --> 00:07:43.899 align:start position:0% and so we hear cool projects and that makes<00:07:41.779> the<00:07:41.959> job<00:07:42.139> very<00:07:42.499> inspiring<00:07:42.979> and<00:07:43.339> a<00:07:43.729> lot 00:07:43.899 --> 00:07:43.909 align:start position:0% makes the job very inspiring and a lot 00:07:43.909 --> 00:07:46.600 align:start position:0% makes the job very inspiring and a lot of<00:07:43.939> fun<00:07:44.269> and<00:07:44.990> also<00:07:45.469> we<00:07:45.680> end<00:07:45.800> up<00:07:45.919> being<00:07:46.189> kind<00:07:46.430> of 00:07:46.600 --> 00:07:46.610 align:start position:0% of fun and also we end up being kind of 00:07:46.610 --> 00:07:50.579 align:start position:0% of fun and also we end up being kind of the<00:07:47.180> front<00:07:47.569> guard<00:07:47.899> of<00:07:48.939> questions<00:07:49.939> and<00:07:50.330> and 00:07:50.579 --> 00:07:50.589 align:start position:0% the front guard of questions and and 00:07:50.589 --> 00:07:52.869 align:start position:0% the front guard of questions and and completely<00:07:51.589> you<00:07:51.649> know<00:07:51.709> frustrations<00:07:52.459> and<00:07:52.699> and 00:07:52.869 --> 00:07:52.879 align:start position:0% completely you know frustrations and and 00:07:52.879 --> 00:07:54.100 align:start position:0% completely you know frustrations and and things<00:07:53.029> like<00:07:53.149> that<00:07:53.209> so<00:07:53.509> I'm<00:07:53.659> gonna<00:07:53.809> talk<00:07:54.080> a 00:07:54.100 --> 00:07:54.110 align:start position:0% things like that so I'm gonna talk a 00:07:54.110 --> 00:07:55.570 align:start position:0% things like that so I'm gonna talk a little<00:07:54.379> bit<00:07:54.529> about<00:07:54.559> the<00:07:54.800> lessons<00:07:55.189> and<00:07:55.399> things 00:07:55.570 --> 00:07:55.580 align:start position:0% little bit about the lessons and things 00:07:55.580 --> 00:07:56.829 align:start position:0% little bit about the lessons and things that<00:07:55.639> we've<00:07:55.819> learned<00:07:56.029> about<00:07:56.330> the 00:07:56.829 --> 00:07:56.839 align:start position:0% that we've learned about the 00:07:56.839 --> 00:07:58.779 align:start position:0% that we've learned about the expectations<00:07:57.439> of<00:07:57.559> a<00:07:57.620> web<00:07:57.769> developer<00:07:58.279> in<00:07:58.490> the 00:07:58.779 --> 00:07:58.789 align:start position:0% expectations of a web developer in the 00:07:58.789 --> 00:08:01.809 align:start position:0% expectations of a web developer in the context<00:07:59.269> of<00:07:59.330> writing<00:07:59.689> aetherium<00:08:00.110> Web<00:08:00.289> Apps<00:08:00.819> so 00:08:01.809 --> 00:08:01.819 align:start position:0% context of writing aetherium Web Apps so 00:08:01.819 --> 00:08:03.790 align:start position:0% context of writing aetherium Web Apps so web<00:08:02.269> 3<00:08:02.569> right<00:08:02.749> now<00:08:02.870> it's<00:08:03.110> your<00:08:03.319> portal<00:08:03.620> to<00:08:03.649> the 00:08:03.790 --> 00:08:03.800 align:start position:0% web 3 right now it's your portal to the 00:08:03.800 --> 00:08:05.110 align:start position:0% web 3 right now it's your portal to the blockchain<00:08:03.979> so<00:08:04.370> it's<00:08:04.550> so<00:08:04.669> cool 00:08:05.110 --> 00:08:05.120 align:start position:0% blockchain so it's so cool 00:08:05.120 --> 00:08:07.029 align:start position:0% blockchain so it's so cool but<00:08:05.360> right<00:08:05.599> now<00:08:05.749> it<00:08:05.930> has<00:08:06.080> a<00:08:06.110> very<00:08:06.379> constrictive 00:08:07.029 --> 00:08:07.039 align:start position:0% but right now it has a very constrictive 00:08:07.039 --> 00:08:10.659 align:start position:0% but right now it has a very constrictive API<00:08:07.519> surface<00:08:07.849> so<00:08:08.330> it's<00:08:08.740> we<00:08:09.740> we<00:08:10.189> want<00:08:10.370> to<00:08:10.459> find 00:08:10.659 --> 00:08:10.669 align:start position:0% API surface so it's we we want to find 00:08:10.669 --> 00:08:13.959 align:start position:0% API surface so it's we we want to find ways<00:08:10.909> to<00:08:11.240> make<00:08:11.749> that<00:08:11.870> do<00:08:12.229> what<00:08:12.379> we<00:08:12.499> want<00:08:12.649> a<00:08:12.969> one 00:08:13.959 --> 00:08:13.969 align:start position:0% ways to make that do what we want a one 00:08:13.969 --> 00:08:15.759 align:start position:0% ways to make that do what we want a one way<00:08:14.120> that<00:08:14.419> it's<00:08:14.689> kind<00:08:14.930> of<00:08:14.990> opinionated<00:08:15.620> right 00:08:15.759 --> 00:08:15.769 align:start position:0% way that it's kind of opinionated right 00:08:15.769 --> 00:08:18.639 align:start position:0% way that it's kind of opinionated right now<00:08:15.919> and<00:08:16.219> it<00:08:16.729> may<00:08:16.969> not<00:08:17.240> reflect<00:08:17.599> the<00:08:17.839> the<00:08:18.349> truth 00:08:18.639 --> 00:08:18.649 align:start position:0% now and it may not reflect the the truth 00:08:18.649 --> 00:08:20.170 align:start position:0% now and it may not reflect the the truth of<00:08:18.829> a<00:08:18.919> blockchain<00:08:19.129> is<00:08:19.370> that<00:08:19.639> it<00:08:19.759> kind<00:08:19.939> of<00:08:19.999> has<00:08:20.149> a 00:08:20.170 --> 00:08:20.180 align:start position:0% of a blockchain is that it kind of has a 00:08:20.180 --> 00:08:22.960 align:start position:0% of a blockchain is that it kind of has a single<00:08:20.810> callback<00:08:21.259> nature<00:08:21.769> right<00:08:22.159> we 00:08:22.960 --> 00:08:22.970 align:start position:0% single callback nature right we 00:08:22.970 --> 00:08:25.330 align:start position:0% single callback nature right we we've<00:08:23.240> got<00:08:23.360> callbacks<00:08:23.810> we've<00:08:24.140> got<00:08:24.350> pudding<00:08:25.040> to 00:08:25.330 --> 00:08:25.340 align:start position:0% we've got callbacks we've got pudding to 00:08:25.340 --> 00:08:27.460 align:start position:0% we've got callbacks we've got pudding to wrap<00:08:25.730> things<00:08:25.910> in<00:08:26.060> promises<00:08:26.600> but<00:08:26.960> these<00:08:27.110> these 00:08:27.460 --> 00:08:27.470 align:start position:0% wrap things in promises but these these 00:08:27.470 --> 00:08:29.050 align:start position:0% wrap things in promises but these these paradigms<00:08:28.190> that<00:08:28.310> work<00:08:28.490> well<00:08:28.670> in<00:08:28.700> web 00:08:29.050 --> 00:08:29.060 align:start position:0% paradigms that work well in web 00:08:29.060 --> 00:08:30.850 align:start position:0% paradigms that work well in web development<00:08:29.480> where<00:08:30.050> there's<00:08:30.410> a<00:08:30.470> single 00:08:30.850 --> 00:08:30.860 align:start position:0% development where there's a single 00:08:30.860 --> 00:08:32.770 align:start position:0% development where there's a single resolution<00:08:31.360> aren't<00:08:32.360> completely 00:08:32.770 --> 00:08:32.780 align:start position:0% resolution aren't completely 00:08:32.780 --> 00:08:35.080 align:start position:0% resolution aren't completely representative<00:08:33.590> of<00:08:33.770> the<00:08:34.490> the<00:08:34.849> kind<00:08:35.000> of 00:08:35.080 --> 00:08:35.090 align:start position:0% representative of the the kind of 00:08:35.090 --> 00:08:36.820 align:start position:0% representative of the the kind of statistical<00:08:35.870> certainty<00:08:36.140> of<00:08:36.380> a<00:08:36.590> blockchain 00:08:36.820 --> 00:08:36.830 align:start position:0% statistical certainty of a blockchain 00:08:36.830 --> 00:08:39.000 align:start position:0% statistical certainty of a blockchain where<00:08:37.280> you<00:08:37.849> might<00:08:38.030> have<00:08:38.210> a<00:08:38.240> single 00:08:39.000 --> 00:08:39.010 align:start position:0% where you might have a single 00:08:39.010 --> 00:08:41.050 align:start position:0% where you might have a single confirmation<00:08:40.010> but<00:08:40.250> you<00:08:40.400> you<00:08:40.669> don't<00:08:40.849> know<00:08:40.940> how 00:08:41.050 --> 00:08:41.060 align:start position:0% confirmation but you you don't know how 00:08:41.060 --> 00:08:42.670 align:start position:0% confirmation but you you don't know how many<00:08:41.210> blocks<00:08:41.450> forward<00:08:41.900> it<00:08:42.050> is<00:08:42.169> or<00:08:42.380> how<00:08:42.500> many 00:08:42.670 --> 00:08:42.680 align:start position:0% many blocks forward it is or how many 00:08:42.680 --> 00:08:44.950 align:start position:0% many blocks forward it is or how many additional<00:08:42.979> confirmations<00:08:43.849> there's<00:08:44.720> a<00:08:44.810> lot 00:08:44.950 --> 00:08:44.960 align:start position:0% additional confirmations there's a lot 00:08:44.960 --> 00:08:47.350 align:start position:0% additional confirmations there's a lot more<00:08:45.140> there's<00:08:46.040> kind<00:08:46.220> of<00:08:46.250> a<00:08:46.340> gradual<00:08:46.880> trust 00:08:47.350 --> 00:08:47.360 align:start position:0% more there's kind of a gradual trust 00:08:47.360 --> 00:08:49.570 align:start position:0% more there's kind of a gradual trust process<00:08:47.570> so<00:08:48.020> so<00:08:48.680> yeah<00:08:48.860> if<00:08:49.040> you<00:08:49.160> if<00:08:49.340> you<00:08:49.430> want 00:08:49.570 --> 00:08:49.580 align:start position:0% process so so yeah if you if you want 00:08:49.580 --> 00:08:51.250 align:start position:0% process so so yeah if you if you want one<00:08:49.610> callback<00:08:50.090> you're<00:08:50.570> kind<00:08:50.720> of<00:08:50.750> trusting<00:08:51.140> it 00:08:51.250 --> 00:08:51.260 align:start position:0% one callback you're kind of trusting it 00:08:51.260 --> 00:08:53.470 align:start position:0% one callback you're kind of trusting it but<00:08:51.470> what<00:08:52.250> else<00:08:52.400> could<00:08:52.640> that<00:08:52.820> look<00:08:52.940> like<00:08:53.150> well 00:08:53.470 --> 00:08:53.480 align:start position:0% but what else could that look like well 00:08:53.480 --> 00:08:54.850 align:start position:0% but what else could that look like well coming<00:08:53.870> from<00:08:53.960> JavaScript<00:08:54.560> and<00:08:54.710> node 00:08:54.850 --> 00:08:54.860 align:start position:0% coming from JavaScript and node 00:08:54.860 --> 00:08:56.650 align:start position:0% coming from JavaScript and node sometimes<00:08:55.340> you<00:08:55.580> might<00:08:55.850> want<00:08:55.910> like<00:08:56.210> an<00:08:56.390> event 00:08:56.650 --> 00:08:56.660 align:start position:0% sometimes you might want like an event 00:08:56.660 --> 00:08:59.080 align:start position:0% sometimes you might want like an event listener<00:08:56.930> so<00:08:57.380> this<00:08:57.530> is<00:08:57.680> a<00:08:57.710> kind<00:08:58.430> of<00:08:58.460> suggestion 00:08:59.080 --> 00:08:59.090 align:start position:0% listener so this is a kind of suggestion 00:08:59.090 --> 00:09:01.330 align:start position:0% listener so this is a kind of suggestion this<00:08:59.630> could<00:08:59.810> be<00:08:59.900> done<00:09:00.080> as<00:09:00.320> a<00:09:00.350> layer<00:09:00.800> on<00:09:00.980> top<00:09:01.160> of 00:09:01.330 --> 00:09:01.340 align:start position:0% this could be done as a layer on top of 00:09:01.340 --> 00:09:03.280 align:start position:0% this could be done as a layer on top of web<00:09:01.490> 3<00:09:01.760> but<00:09:02.360> it<00:09:02.450> could<00:09:02.540> be<00:09:02.660> optimized<00:09:03.080> much 00:09:03.280 --> 00:09:03.290 align:start position:0% web 3 but it could be optimized much 00:09:03.290 --> 00:09:05.710 align:start position:0% web 3 but it could be optimized much better<00:09:03.530> if<00:09:03.770> it<00:09:03.950> was<00:09:04.100> implemented<00:09:04.910> at<00:09:05.180> the<00:09:05.210> RPC 00:09:05.710 --> 00:09:05.720 align:start position:0% better if it was implemented at the RPC 00:09:05.720 --> 00:09:08.650 align:start position:0% better if it was implemented at the RPC layer<00:09:06.460> so<00:09:07.460> in<00:09:07.670> in<00:09:07.850> this<00:09:07.970> case<00:09:08.180> you<00:09:08.360> might<00:09:08.480> get 00:09:08.650 --> 00:09:08.660 align:start position:0% layer so in in this case you might get 00:09:08.660 --> 00:09:10.210 align:start position:0% layer so in in this case you might get an<00:09:08.780> additional<00:09:08.990> callback<00:09:09.590> whenever<00:09:09.920> there's 00:09:10.210 --> 00:09:10.220 align:start position:0% an additional callback whenever there's 00:09:10.220 --> 00:09:11.830 align:start position:0% an additional callback whenever there's an<00:09:10.340> additional<00:09:10.670> confirmation<00:09:11.270> or<00:09:11.450> whenever 00:09:11.830 --> 00:09:11.840 align:start position:0% an additional confirmation or whenever 00:09:11.840 --> 00:09:13.630 align:start position:0% an additional confirmation or whenever there's<00:09:12.020> an<00:09:12.110> additional<00:09:12.440> block<00:09:12.740> or<00:09:13.040> maybe 00:09:13.630 --> 00:09:13.640 align:start position:0% there's an additional block or maybe 00:09:13.640 --> 00:09:14.830 align:start position:0% there's an additional block or maybe there<00:09:13.820> could<00:09:13.910> be<00:09:13.970> a<00:09:14.060> callback<00:09:14.420> when<00:09:14.570> there's<00:09:14.750> a 00:09:14.830 --> 00:09:14.840 align:start position:0% there could be a callback when there's a 00:09:14.840 --> 00:09:16.450 align:start position:0% there could be a callback when there's a fork<00:09:15.110> in<00:09:15.230> the<00:09:15.350> blockchain<00:09:15.560> because<00:09:16.130> right<00:09:16.310> now 00:09:16.450 --> 00:09:16.460 align:start position:0% fork in the blockchain because right now 00:09:16.460 --> 00:09:18.070 align:start position:0% fork in the blockchain because right now the<00:09:16.520> RPC<00:09:16.970> doesn't<00:09:17.450> really<00:09:17.630> give<00:09:17.780> you<00:09:17.870> any 00:09:18.070 --> 00:09:18.080 align:start position:0% the RPC doesn't really give you any 00:09:18.080 --> 00:09:20.230 align:start position:0% the RPC doesn't really give you any indication<00:09:18.290> when<00:09:18.800> there's<00:09:18.980> a<00:09:19.040> block<00:09:19.370> fork 00:09:20.230 --> 00:09:20.240 align:start position:0% indication when there's a block fork 00:09:20.240 --> 00:09:22.720 align:start position:0% indication when there's a block fork short<00:09:21.080> of<00:09:21.230> you<00:09:21.380> querying<00:09:21.710> the<00:09:21.980> latest<00:09:22.460> block 00:09:22.720 --> 00:09:22.730 align:start position:0% short of you querying the latest block 00:09:22.730 --> 00:09:24.760 align:start position:0% short of you querying the latest block and<00:09:23.060> going<00:09:23.660> back<00:09:23.870> because<00:09:24.140> you're<00:09:24.620> querying 00:09:24.760 --> 00:09:24.770 align:start position:0% and going back because you're querying 00:09:24.770 --> 00:09:27.730 align:start position:0% and going back because you're querying by<00:09:24.980> block<00:09:25.250> number<00:09:25.580> not<00:09:25.730> by<00:09:25.910> hash<00:09:26.180> so<00:09:26.540> so<00:09:27.170> for<00:09:27.620> an 00:09:27.730 --> 00:09:27.740 align:start position:0% by block number not by hash so so for an 00:09:27.740 --> 00:09:30.040 align:start position:0% by block number not by hash so so for an RPC<00:09:28.040> trust<00:09:28.430> and<00:09:28.580> client<00:09:28.910> like<00:09:29.210> like<00:09:29.690> a<00:09:29.720> web 00:09:30.040 --> 00:09:30.050 align:start position:0% RPC trust and client like like a web 00:09:30.050 --> 00:09:32.950 align:start position:0% RPC trust and client like like a web browser<00:09:30.670> you<00:09:31.670> you<00:09:31.910> you<00:09:32.120> have<00:09:32.270> to<00:09:32.480> you<00:09:32.780> have<00:09:32.810> to 00:09:32.950 --> 00:09:32.960 align:start position:0% browser you you you have to you have to 00:09:32.960 --> 00:09:35.200 align:start position:0% browser you you you have to you have to pound<00:09:33.410> your<00:09:33.590> server<00:09:33.770> very<00:09:34.100> hard<00:09:34.370> just<00:09:35.090> to 00:09:35.200 --> 00:09:35.210 align:start position:0% pound your server very hard just to 00:09:35.210 --> 00:09:36.760 align:start position:0% pound your server very hard just to answer<00:09:35.360> these<00:09:35.570> very<00:09:35.780> basic<00:09:35.930> questions<00:09:36.560> and 00:09:36.760 --> 00:09:36.770 align:start position:0% answer these very basic questions and 00:09:36.770 --> 00:09:38.260 align:start position:0% answer these very basic questions and these<00:09:37.220> are<00:09:37.340> things<00:09:37.460> that<00:09:37.580> the<00:09:37.760> user<00:09:37.880> interface 00:09:38.260 --> 00:09:38.270 align:start position:0% these are things that the user interface 00:09:38.270 --> 00:09:42.010 align:start position:0% these are things that the user interface should<00:09:38.510> reflect<00:09:38.810> anyways<00:09:40.390> also<00:09:41.390> web 00:09:42.010 --> 00:09:42.020 align:start position:0% should reflect anyways also web 00:09:42.020 --> 00:09:43.420 align:start position:0% should reflect anyways also web developers<00:09:42.440> always<00:09:42.620> want<00:09:42.830> to<00:09:42.860> just<00:09:43.010> query<00:09:43.280> the 00:09:43.420 --> 00:09:43.430 align:start position:0% developers always want to just query the 00:09:43.430 --> 00:09:45.430 align:start position:0% developers always want to just query the database<00:09:43.550> and<00:09:44.060> some<00:09:44.270> things<00:09:44.450> are<00:09:44.600> very<00:09:44.840> simple 00:09:45.430 --> 00:09:45.440 align:start position:0% database and some things are very simple 00:09:45.440 --> 00:09:46.990 align:start position:0% database and some things are very simple questions<00:09:45.830> in<00:09:46.070> you<00:09:46.400> know<00:09:46.490> relational 00:09:46.990 --> 00:09:47.000 align:start position:0% questions in you know relational 00:09:47.000 --> 00:09:48.280 align:start position:0% questions in you know relational databases<00:09:47.360> but<00:09:47.660> end<00:09:47.810> up<00:09:47.930> being<00:09:48.140> very 00:09:48.280 --> 00:09:48.290 align:start position:0% databases but end up being very 00:09:48.290 --> 00:09:50.410 align:start position:0% databases but end up being very difficult<00:09:48.530> on<00:09:48.950> the<00:09:49.070> blockchain<00:09:49.280> you<00:09:50.240> might 00:09:50.410 --> 00:09:50.420 align:start position:0% difficult on the blockchain you might 00:09:50.420 --> 00:09:51.820 align:start position:0% difficult on the blockchain you might consider<00:09:50.630> the<00:09:50.990> case<00:09:51.320> of<00:09:51.350> a<00:09:51.530> decentralized 00:09:51.820 --> 00:09:51.830 align:start position:0% consider the case of a decentralized 00:09:51.830 --> 00:09:53.770 align:start position:0% consider the case of a decentralized Twitter<00:09:52.310> you<00:09:52.730> just<00:09:52.910> want<00:09:53.030> the<00:09:53.120> 50<00:09:53.510> latest 00:09:53.770 --> 00:09:53.780 align:start position:0% Twitter you just want the 50 latest 00:09:53.780 --> 00:09:55.840 align:start position:0% Twitter you just want the 50 latest tweets<00:09:54.050> the<00:09:54.560> current<00:09:54.980> basic<00:09:55.400> model<00:09:55.730> is 00:09:55.840 --> 00:09:55.850 align:start position:0% tweets the current basic model is 00:09:55.850 --> 00:09:57.670 align:start position:0% tweets the current basic model is somebody<00:09:56.180> basically<00:09:56.720> querying<00:09:57.200> all<00:09:57.500> the 00:09:57.670 --> 00:09:57.680 align:start position:0% somebody basically querying all the 00:09:57.680 --> 00:09:59.920 align:start position:0% somebody basically querying all the tweets<00:09:57.950> in<00:09:58.160> the<00:09:58.280> in<00:09:58.430> the<00:09:58.550> blockchain<00:09:58.840> you<00:09:59.840> know 00:09:59.920 --> 00:09:59.930 align:start position:0% tweets in the in the blockchain you know 00:09:59.930 --> 00:10:02.200 align:start position:0% tweets in the in the blockchain you know a<00:09:59.960> lot<00:10:00.470> of<00:10:00.500> developers<00:10:00.830> are<00:10:01.370> coming<00:10:02.000> in<00:10:02.090> and 00:10:02.200 --> 00:10:02.210 align:start position:0% a lot of developers are coming in and 00:10:02.210 --> 00:10:03.580 align:start position:0% a lot of developers are coming in and they're<00:10:02.270> saying<00:10:02.450> oh<00:10:02.570> the<00:10:02.750> cheapest<00:10:03.110> gas<00:10:03.260> thing 00:10:03.580 --> 00:10:03.590 align:start position:0% they're saying oh the cheapest gas thing 00:10:03.590 --> 00:10:05.500 align:start position:0% they're saying oh the cheapest gas thing is<00:10:03.740> log<00:10:03.980> so<00:10:04.430> I'm<00:10:04.550> just<00:10:04.670> kind<00:10:04.820> of<00:10:04.850> use<00:10:04.970> logs<00:10:05.300> as 00:10:05.500 --> 00:10:05.510 align:start position:0% is log so I'm just kind of use logs as 00:10:05.510 --> 00:10:07.180 align:start position:0% is log so I'm just kind of use logs as my<00:10:05.630> database<00:10:06.020> and<00:10:06.200> then<00:10:06.620> the<00:10:06.710> method<00:10:06.860> is 00:10:07.180 --> 00:10:07.190 align:start position:0% my database and then the method is 00:10:07.190 --> 00:10:09.040 align:start position:0% my database and then the method is basically<00:10:07.370> logs<00:10:07.880> since<00:10:08.330> the<00:10:08.480> Genesis<00:10:08.900> block 00:10:09.040 --> 00:10:09.050 align:start position:0% basically logs since the Genesis block 00:10:09.050 --> 00:10:11.410 align:start position:0% basically logs since the Genesis block and<00:10:09.410> now<00:10:09.530> the<00:10:09.620> server<00:10:09.920> gets<00:10:10.640> every<00:10:11.030> tweet<00:10:11.300> of 00:10:11.410 --> 00:10:11.420 align:start position:0% and now the server gets every tweet of 00:10:11.420 --> 00:10:12.850 align:start position:0% and now the server gets every tweet of all<00:10:11.540> time<00:10:11.810> and<00:10:11.960> then<00:10:12.080> sends<00:10:12.440> it<00:10:12.530> and<00:10:12.680> it<00:10:12.740> all 00:10:12.850 --> 00:10:12.860 align:start position:0% all time and then sends it and it all 00:10:12.860 --> 00:10:14.290 align:start position:0% all time and then sends it and it all gets<00:10:13.010> loaded<00:10:13.430> up<00:10:13.520> in<00:10:13.640> the<00:10:13.670> browser<00:10:13.970> which<00:10:14.270> is 00:10:14.290 --> 00:10:14.300 align:start position:0% gets loaded up in the browser which is 00:10:14.300 --> 00:10:16.420 align:start position:0% gets loaded up in the browser which is the<00:10:14.660> interface<00:10:15.140> thread<00:10:15.470> which<00:10:15.920> then<00:10:16.130> does<00:10:16.250> all 00:10:16.420 --> 00:10:16.430 align:start position:0% the interface thread which then does all 00:10:16.430 --> 00:10:17.890 align:start position:0% the interface thread which then does all the<00:10:16.610> sorting<00:10:16.940> of<00:10:16.970> its<00:10:17.390> it's<00:10:17.630> impractical 00:10:17.890 --> 00:10:17.900 align:start position:0% the sorting of its it's impractical 00:10:17.900 --> 00:10:20.490 align:start position:0% the sorting of its it's impractical right<00:10:18.290> so<00:10:18.500> so<00:10:19.160> what<00:10:19.280> are<00:10:19.370> solutions<00:10:19.610> to<00:10:19.820> that 00:10:20.490 --> 00:10:20.500 align:start position:0% right so so what are solutions to that 00:10:20.500 --> 00:10:23.110 align:start position:0% right so so what are solutions to that one<00:10:21.500> solution<00:10:21.980> is<00:10:22.160> to<00:10:22.400> write<00:10:22.550> your<00:10:22.730> sorting 00:10:23.110 --> 00:10:23.120 align:start position:0% one solution is to write your sorting 00:10:23.120 --> 00:10:25.450 align:start position:0% one solution is to write your sorting logic<00:10:23.480> in<00:10:23.600> the<00:10:23.690> contract<00:10:24.110> layer<00:10:24.350> and<00:10:24.650> so<00:10:25.280> now 00:10:25.450 --> 00:10:25.460 align:start position:0% logic in the contract layer and so now 00:10:25.460 --> 00:10:27.550 align:start position:0% logic in the contract layer and so now it's<00:10:25.640> it's<00:10:25.850> kind<00:10:26.060> of<00:10:26.089> inflexible<00:10:26.780> and<00:10:27.020> it<00:10:27.350> gets 00:10:27.550 --> 00:10:27.560 align:start position:0% it's it's kind of inflexible and it gets 00:10:27.560 --> 00:10:30.579 align:start position:0% it's it's kind of inflexible and it gets a<00:10:27.710> run<00:10:28.070> on<00:10:28.100> the<00:10:28.310> chain<00:10:28.660> it's<00:10:29.660> still<00:10:29.930> one<00:10:30.380> batch 00:10:30.579 --> 00:10:30.589 align:start position:0% a run on the chain it's still one batch 00:10:30.589 --> 00:10:33.070 align:start position:0% a run on the chain it's still one batch but<00:10:30.950> you<00:10:31.250> know<00:10:31.339> you<00:10:31.400> could<00:10:31.610> write<00:10:31.760> some<00:10:32.089> some 00:10:33.070 --> 00:10:33.080 align:start position:0% but you know you could write some some 00:10:33.080 --> 00:10:36.010 align:start position:0% but you know you could write some some kind<00:10:33.230> of<00:10:33.350> pagination<00:10:34.310> logic<00:10:34.730> maybe<00:10:34.930> there's<00:10:35.930> a 00:10:36.010 --> 00:10:36.020 align:start position:0% kind of pagination logic maybe there's a 00:10:36.020 --> 00:10:36.310 align:start position:0% kind of pagination logic maybe there's a cool 00:10:36.310 --> 00:10:36.320 align:start position:0% cool 00:10:36.320 --> 00:10:38.290 align:start position:0% cool I<00:10:36.350> pee<00:10:36.500> out<00:10:36.710> their<00:10:36.890> 144<00:10:37.610> which<00:10:37.820> would<00:10:38.000> let<00:10:38.150> you 00:10:38.290 --> 00:10:38.300 align:start position:0% I pee out their 144 which would let you 00:10:38.300 --> 00:10:41.410 align:start position:0% I pee out their 144 which would let you send<00:10:38.900> some<00:10:39.560> custom<00:10:40.310> bytecode<00:10:40.880> some<00:10:41.150> evn 00:10:41.410 --> 00:10:41.420 align:start position:0% send some custom bytecode some evn 00:10:41.420 --> 00:10:43.120 align:start position:0% send some custom bytecode some evn bytecode<00:10:41.810> up<00:10:41.960> to<00:10:42.110> the<00:10:42.230> server<00:10:42.440> that<00:10:42.680> it<00:10:43.010> would 00:10:43.120 --> 00:10:43.130 align:start position:0% bytecode up to the server that it would 00:10:43.130 --> 00:10:44.860 align:start position:0% bytecode up to the server that it would run<00:10:43.340> so<00:10:43.610> you<00:10:43.670> could<00:10:43.820> actually<00:10:43.940> request<00:10:44.540> like<00:10:44.840> a 00:10:44.860 --> 00:10:44.870 align:start position:0% run so you could actually request like a 00:10:44.870 --> 00:10:48.070 align:start position:0% run so you could actually request like a custom<00:10:45.380> results<00:10:46.250> for<00:10:46.520> the<00:10:46.790> state<00:10:47.060> tree<00:10:47.270> that's 00:10:48.070 --> 00:10:48.080 align:start position:0% custom results for the state tree that's 00:10:48.080 --> 00:10:49.690 align:start position:0% custom results for the state tree that's an<00:10:48.260> interesting<00:10:48.680> one<00:10:48.800> I<00:10:49.010> encourage<00:10:49.580> you<00:10:49.670> to 00:10:49.690 --> 00:10:49.700 align:start position:0% an interesting one I encourage you to 00:10:49.700 --> 00:10:52.210 align:start position:0% an interesting one I encourage you to check<00:10:49.790> it<00:10:49.970> out<00:10:50.210> there<00:10:50.570> on<00:10:50.660> your<00:10:50.750> two<00:10:51.050> cents<00:10:51.260> oh 00:10:52.210 --> 00:10:52.220 align:start position:0% check it out there on your two cents oh 00:10:52.220 --> 00:10:54.760 align:start position:0% check it out there on your two cents oh there's<00:10:53.030> also<00:10:53.150> a<00:10:53.270> another<00:10:53.930> idea<00:10:54.410> like<00:10:54.560> maybe 00:10:54.760 --> 00:10:54.770 align:start position:0% there's also a another idea like maybe 00:10:54.770 --> 00:10:56.020 align:start position:0% there's also a another idea like maybe there<00:10:54.950> could<00:10:55.040> be<00:10:55.100> an<00:10:55.220> additional<00:10:55.370> method<00:10:55.880> on 00:10:56.020 --> 00:10:56.030 align:start position:0% there could be an additional method on 00:10:56.030 --> 00:10:56.680 align:start position:0% there could be an additional method on the<00:10:56.120> RPC 00:10:56.680 --> 00:10:56.690 align:start position:0% the RPC 00:10:56.690 --> 00:10:59.680 align:start position:0% the RPC like<00:10:56.990> a<00:10:57.020> sequel<00:10:57.950> like<00:10:58.130> query<00:10:58.460> method<00:10:58.820> but<00:10:59.120> this 00:10:59.680 --> 00:10:59.690 align:start position:0% like a sequel like query method but this 00:10:59.690 --> 00:11:01.600 align:start position:0% like a sequel like query method but this kind<00:10:59.930> of<00:10:59.990> requires<00:11:00.320> like<00:11:00.560> indexes<00:11:01.130> so<00:11:01.430> maybe 00:11:01.600 --> 00:11:01.610 align:start position:0% kind of requires like indexes so maybe 00:11:01.610 --> 00:11:04.090 align:start position:0% kind of requires like indexes so maybe we<00:11:01.790> need<00:11:01.820> you<00:11:02.480> know<00:11:02.570> incentivized<00:11:03.560> indexes 00:11:04.090 --> 00:11:04.100 align:start position:0% we need you know incentivized indexes 00:11:04.100 --> 00:11:05.740 align:start position:0% we need you know incentivized indexes because<00:11:04.520> you<00:11:05.120> know<00:11:05.180> logs<00:11:05.570> aren't 00:11:05.740 --> 00:11:05.750 align:start position:0% because you know logs aren't 00:11:05.750 --> 00:11:08.170 align:start position:0% because you know logs aren't incentivized<00:11:06.320> indexes<00:11:06.890> maybe<00:11:07.820> they<00:11:07.970> could<00:11:08.120> be 00:11:08.170 --> 00:11:08.180 align:start position:0% incentivized indexes maybe they could be 00:11:08.180 --> 00:11:09.790 align:start position:0% incentivized indexes maybe they could be a<00:11:08.210> contract<00:11:08.720> maybe<00:11:09.410> we<00:11:09.560> should<00:11:09.710> have 00:11:09.790 --> 00:11:09.800 align:start position:0% a contract maybe we should have 00:11:09.800 --> 00:11:11.110 align:start position:0% a contract maybe we should have standards<00:11:10.130> around<00:11:10.280> those<00:11:10.400> those<00:11:10.910> could<00:11:11.090> be 00:11:11.110 --> 00:11:11.120 align:start position:0% standards around those those could be 00:11:11.120 --> 00:11:14.260 align:start position:0% standards around those those could be helpful<00:11:11.860> sometimes<00:11:12.860> people<00:11:13.280> ask<00:11:13.400> us<00:11:13.610> why<00:11:14.210> is 00:11:14.260 --> 00:11:14.270 align:start position:0% helpful sometimes people ask us why is 00:11:14.270 --> 00:11:16.900 align:start position:0% helpful sometimes people ask us why is this<00:11:14.720> method<00:11:14.960> not<00:11:15.230> acting<00:11:15.620> like<00:11:15.770> death<00:11:15.980> and<00:11:16.190> it 00:11:16.900 --> 00:11:16.910 align:start position:0% this method not acting like death and it 00:11:16.910 --> 00:11:18.490 align:start position:0% this method not acting like death and it turns<00:11:17.270> out<00:11:17.390> that<00:11:17.450> there<00:11:17.930> isn't<00:11:18.200> really<00:11:18.350> a 00:11:18.490 --> 00:11:18.500 align:start position:0% turns out that there isn't really a 00:11:18.500 --> 00:11:20.860 align:start position:0% turns out that there isn't really a standard<00:11:18.920> right<00:11:19.130> now<00:11:19.160> we<00:11:19.730> go<00:11:20.120> to<00:11:20.150> the<00:11:20.300> wiki<00:11:20.630> and 00:11:20.860 --> 00:11:20.870 align:start position:0% standard right now we go to the wiki and 00:11:20.870 --> 00:11:22.660 align:start position:0% standard right now we go to the wiki and then<00:11:21.140> if<00:11:21.440> that<00:11:21.950> doesn't<00:11:22.010> do<00:11:22.430> it<00:11:22.550> then 00:11:22.660 --> 00:11:22.670 align:start position:0% then if that doesn't do it then 00:11:22.670 --> 00:11:23.590 align:start position:0% then if that doesn't do it then sometimes<00:11:23.000> we<00:11:23.090> have<00:11:23.180> to<00:11:23.270> go<00:11:23.360> to<00:11:23.420> the 00:11:23.590 --> 00:11:23.600 align:start position:0% sometimes we have to go to the 00:11:23.600 --> 00:11:25.630 align:start position:0% sometimes we have to go to the individual<00:11:24.080> github<00:11:24.590> repos<00:11:24.980> or<00:11:25.190> oh<00:11:25.340> it<00:11:25.490> turns 00:11:25.630 --> 00:11:25.640 align:start position:0% individual github repos or oh it turns 00:11:25.640 --> 00:11:27.520 align:start position:0% individual github repos or oh it turns out<00:11:25.790> they<00:11:25.910> were<00:11:25.970> using<00:11:26.060> parody<00:11:26.600> there<00:11:27.320> are 00:11:27.520 --> 00:11:27.530 align:start position:0% out they were using parody there are 00:11:27.530 --> 00:11:29.620 align:start position:0% out they were using parody there are fine<00:11:28.000> distinctions<00:11:29.000> and<00:11:29.180> there<00:11:29.270> isn't<00:11:29.540> a 00:11:29.620 --> 00:11:29.630 align:start position:0% fine distinctions and there isn't a 00:11:29.630 --> 00:11:31.750 align:start position:0% fine distinctions and there isn't a singular<00:11:29.870> source<00:11:30.230> of<00:11:30.380> truth<00:11:30.560> right<00:11:30.740> now<00:11:30.920> so<00:11:31.460> I 00:11:31.750 --> 00:11:31.760 align:start position:0% singular source of truth right now so I 00:11:31.760 --> 00:11:33.310 align:start position:0% singular source of truth right now so I would<00:11:31.880> just<00:11:32.060> kind<00:11:32.390> of<00:11:32.450> like<00:11:32.960> to<00:11:33.080> take<00:11:33.200> this 00:11:33.310 --> 00:11:33.320 align:start position:0% would just kind of like to take this 00:11:33.320 --> 00:11:35.620 align:start position:0% would just kind of like to take this opportunity<00:11:33.470> to<00:11:34.160> say<00:11:34.310> hey<00:11:34.820> how<00:11:35.210> about<00:11:35.240> we 00:11:35.620 --> 00:11:35.630 align:start position:0% opportunity to say hey how about we 00:11:35.630 --> 00:11:37.750 align:start position:0% opportunity to say hey how about we develop<00:11:36.110> a<00:11:36.200> web<00:11:36.350> three<00:11:36.560> standards<00:11:36.950> body<00:11:37.160> maybe 00:11:37.750 --> 00:11:37.760 align:start position:0% develop a web three standards body maybe 00:11:37.760 --> 00:11:39.640 align:start position:0% develop a web three standards body maybe we<00:11:37.940> could<00:11:38.120> be<00:11:38.270> decentralized<00:11:38.750> and<00:11:39.230> cool<00:11:39.410> on<00:11:39.620> a 00:11:39.640 --> 00:11:39.650 align:start position:0% we could be decentralized and cool on a 00:11:39.650 --> 00:11:43.870 align:start position:0% we could be decentralized and cool on a blockchain<00:11:39.950> or<00:11:40.370> something<00:11:41.650> have<00:11:42.650> boats<00:11:43.010> you 00:11:43.870 --> 00:11:43.880 align:start position:0% blockchain or something have boats you 00:11:43.880 --> 00:11:46.750 align:start position:0% blockchain or something have boats you know<00:11:43.910> have<00:11:44.300> a<00:11:44.330> may<00:11:45.110> be<00:11:45.220> signing<00:11:46.220> keeper 00:11:46.750 --> 00:11:46.760 align:start position:0% know have a may be signing keeper 00:11:46.760 --> 00:11:48.250 align:start position:0% know have a may be signing keeper implementation<00:11:47.510> and<00:11:47.720> they<00:11:47.780> could<00:11:47.930> say<00:11:48.080> we 00:11:48.250 --> 00:11:48.260 align:start position:0% implementation and they could say we 00:11:48.260 --> 00:11:49.720 align:start position:0% implementation and they could say we definitely<00:11:48.410> support<00:11:48.920> this<00:11:49.250> implementation 00:11:49.720 --> 00:11:49.730 align:start position:0% definitely support this implementation 00:11:49.730 --> 00:11:51.430 align:start position:0% definitely support this implementation and<00:11:50.060> maybe<00:11:50.810> they<00:11:50.930> could<00:11:50.990> be<00:11:51.110> on<00:11:51.200> chain 00:11:51.430 --> 00:11:51.440 align:start position:0% and maybe they could be on chain 00:11:51.440 --> 00:11:52.990 align:start position:0% and maybe they could be on chain validation<00:11:52.010> I<00:11:52.070> don't<00:11:52.220> know<00:11:52.280> whatever<00:11:52.700> I'm 00:11:52.990 --> 00:11:53.000 align:start position:0% validation I don't know whatever I'm 00:11:53.000 --> 00:11:54.010 align:start position:0% validation I don't know whatever I'm sure<00:11:53.180> you<00:11:53.270> guys<00:11:53.390> have<00:11:53.540> lots<00:11:53.660> of<00:11:53.750> great<00:11:53.840> ideas 00:11:54.010 --> 00:11:54.020 align:start position:0% sure you guys have lots of great ideas 00:11:54.020 --> 00:11:57.970 align:start position:0% sure you guys have lots of great ideas about<00:11:54.320> that<00:11:55.720> mgn<00:11:56.720> is<00:11:57.050> a<00:11:57.110> great<00:11:57.440> implementation 00:11:57.970 --> 00:11:57.980 align:start position:0% about that mgn is a great implementation 00:11:57.980 --> 00:11:59.830 align:start position:0% about that mgn is a great implementation a<00:11:58.130> great<00:11:58.520> example<00:11:58.760> of<00:11:59.090> a<00:11:59.210> standard 00:11:59.830 --> 00:11:59.840 align:start position:0% a great example of a standard 00:11:59.840 --> 00:12:03.820 align:start position:0% a great example of a standard documentation<00:12:01.390> so<00:12:02.390> that's<00:12:02.870> the<00:12:03.110> the<00:12:03.410> time<00:12:03.710> I'm 00:12:03.820 --> 00:12:03.830 align:start position:0% documentation so that's the the time I'm 00:12:03.830 --> 00:12:05.020 align:start position:0% documentation so that's the the time I'm gonna<00:12:03.980> spend<00:12:04.130> on<00:12:04.250> that<00:12:04.370> now<00:12:04.640> to<00:12:04.700> talk<00:12:05.000> about 00:12:05.020 --> 00:12:05.030 align:start position:0% gonna spend on that now to talk about 00:12:05.030 --> 00:12:06.400 align:start position:0% gonna spend on that now to talk about the<00:12:05.330> future<00:12:05.450> of<00:12:05.660> meta<00:12:05.990> mask 00:12:06.400 --> 00:12:06.410 align:start position:0% the future of meta mask 00:12:06.410 --> 00:12:16.900 align:start position:0% the future of meta mask here's<00:12:07.010> Combe<00:12:07.670> obvious<00:12:08.440> Thanks 00:12:16.900 --> 00:12:16.910 align:start position:0% 00:12:16.910 --> 00:12:19.120 align:start position:0% hello-oh 00:12:19.120 --> 00:12:19.130 align:start position:0% hello-oh 00:12:19.130 --> 00:12:24.560 align:start position:0% hello-oh the<00:12:20.130> future<00:12:20.460> in<00:12:21.360> space<00:12:23.120> so<00:12:24.120> one<00:12:24.270> thing<00:12:24.420> we've 00:12:24.560 --> 00:12:24.570 align:start position:0% the future in space so one thing we've 00:12:24.570 --> 00:12:26.660 align:start position:0% the future in space so one thing we've been<00:12:24.750> asked<00:12:25.290> for<00:12:25.380> a<00:12:25.440> lot<00:12:25.590> is<00:12:25.740> multiple<00:12:26.279> account 00:12:26.660 --> 00:12:26.670 align:start position:0% been asked for a lot is multiple account 00:12:26.670 --> 00:12:28.330 align:start position:0% been asked for a lot is multiple account types<00:12:26.940> right<00:12:27.480> now<00:12:27.600> we<00:12:27.660> just<00:12:27.960> do<00:12:28.110> the 00:12:28.330 --> 00:12:28.340 align:start position:0% types right now we just do the 00:12:28.340 --> 00:12:31.490 align:start position:0% types right now we just do the deterministic<00:12:29.510> keychain<00:12:30.510> and<00:12:31.080> that's<00:12:31.260> nice 00:12:31.490 --> 00:12:31.500 align:start position:0% deterministic keychain and that's nice 00:12:31.500 --> 00:12:33.890 align:start position:0% deterministic keychain and that's nice really<00:12:31.860> easy<00:12:32.010> to<00:12:32.220> backup<00:12:32.430> and<00:12:32.760> recover 00:12:33.890 --> 00:12:33.900 align:start position:0% really easy to backup and recover 00:12:33.900 --> 00:12:37.010 align:start position:0% really easy to backup and recover but<00:12:34.140> people<00:12:34.440> want<00:12:34.650> to<00:12:34.830> use<00:12:35.220> a<00:12:35.820> proxy<00:12:36.360> contract 00:12:37.010 --> 00:12:37.020 align:start position:0% but people want to use a proxy contract 00:12:37.020 --> 00:12:38.600 align:start position:0% but people want to use a proxy contract identities<00:12:37.470> like<00:12:37.740> those<00:12:38.010> being<00:12:38.220> developed<00:12:38.520> by 00:12:38.600 --> 00:12:38.610 align:start position:0% identities like those being developed by 00:12:38.610 --> 00:12:41.030 align:start position:0% identities like those being developed by you<00:12:38.790> port<00:12:39.120> maybe<00:12:39.720> remote<00:12:40.110> key<00:12:40.350> stores<00:12:40.710> like 00:12:41.030 --> 00:12:41.040 align:start position:0% you port maybe remote key stores like 00:12:41.040 --> 00:12:43.250 align:start position:0% you port maybe remote key stores like you<00:12:41.160> have<00:12:41.310> coinbase<00:12:42.060> hold<00:12:42.540> your<00:12:42.720> private<00:12:43.050> key 00:12:43.250 --> 00:12:43.260 align:start position:0% you have coinbase hold your private key 00:12:43.260 --> 00:12:46.250 align:start position:0% you have coinbase hold your private key and<00:12:43.589> we<00:12:43.740> use<00:12:44.580> an<00:12:44.730> API<00:12:44.880> to<00:12:45.180> get<00:12:45.540> it<00:12:45.690> get<00:12:46.050> over 00:12:46.250 --> 00:12:46.260 align:start position:0% and we use an API to get it get over 00:12:46.260 --> 00:12:51.550 align:start position:0% and we use an API to get it get over there<00:12:48.140> that's<00:12:49.140> that's<00:12:49.710> in<00:12:50.010> the<00:12:50.130> near<00:12:50.279> future 00:12:51.550 --> 00:12:51.560 align:start position:0% there that's that's in the near future 00:12:51.560 --> 00:12:54.410 align:start position:0% there that's that's in the near future also<00:12:52.560> there's<00:12:52.950> some<00:12:53.010> some<00:12:53.640> experiments 00:12:54.410 --> 00:12:54.420 align:start position:0% also there's some some experiments 00:12:54.420 --> 00:12:56.420 align:start position:0% also there's some some experiments coming<00:12:54.600> from<00:12:55.050> the<00:12:55.260> ether<00:12:55.410> mgs<00:12:55.770> community<00:12:56.220> like 00:12:56.420 --> 00:12:56.430 align:start position:0% coming from the ether mgs community like 00:12:56.430 --> 00:12:58.370 align:start position:0% coming from the ether mgs community like turning<00:12:57.000> the<00:12:57.120> browser<00:12:57.330> into<00:12:57.750> a<00:12:57.779> light<00:12:57.990> client 00:12:58.370 --> 00:12:58.380 align:start position:0% turning the browser into a light client 00:12:58.380 --> 00:13:01.160 align:start position:0% turning the browser into a light client by<00:12:58.860> having<00:12:59.190> a<00:12:59.370> separate<00:12:59.940> web<00:13:00.450> RTC<00:13:00.750> based 00:13:01.160 --> 00:13:01.170 align:start position:0% by having a separate web RTC based 00:13:01.170 --> 00:13:03.650 align:start position:0% by having a separate web RTC based peer-to-peer<00:13:01.920> network<00:13:02.400> and<00:13:02.700> some<00:13:03.450> bridge 00:13:03.650 --> 00:13:03.660 align:start position:0% peer-to-peer network and some bridge 00:13:03.660 --> 00:13:07.610 align:start position:0% peer-to-peer network and some bridge nodes<00:13:05.960> little<00:13:06.960> experiment<00:13:07.410> we've<00:13:07.500> been 00:13:07.610 --> 00:13:07.620 align:start position:0% nodes little experiment we've been 00:13:07.620 --> 00:13:09.440 align:start position:0% nodes little experiment we've been working<00:13:07.890> on<00:13:08.010> this<00:13:08.160> they<00:13:08.430> if<00:13:09.029> they're<00:13:09.240> in 00:13:09.440 --> 00:13:09.450 align:start position:0% working on this they if they're in 00:13:09.450 --> 00:13:11.170 align:start position:0% working on this they if they're in transaction<00:13:09.960> visualizer 00:13:11.170 --> 00:13:11.180 align:start position:0% transaction visualizer 00:13:11.180 --> 00:13:13.670 align:start position:0% transaction visualizer visualizer<00:13:12.180> yes<00:13:13.110> it<00:13:13.380> looks<00:13:13.560> a<00:13:13.620> little 00:13:13.670 --> 00:13:13.680 align:start position:0% visualizer yes it looks a little 00:13:13.680 --> 00:13:15.140 align:start position:0% visualizer yes it looks a little something<00:13:13.830> like<00:13:14.010> this<00:13:14.250> this<00:13:14.400> is<00:13:14.580> one<00:13:14.970> of<00:13:15.060> the 00:13:15.140 --> 00:13:15.150 align:start position:0% something like this this is one of the 00:13:15.150 --> 00:13:17.329 align:start position:0% something like this this is one of the dau<00:13:15.360> attacks<00:13:15.810> and<00:13:16.110> so<00:13:16.740> when<00:13:16.890> you<00:13:16.980> play<00:13:17.160> this 00:13:17.329 --> 00:13:17.339 align:start position:0% dau attacks and so when you play this 00:13:17.339 --> 00:13:19.610 align:start position:0% dau attacks and so when you play this one<00:13:17.520> you<00:13:17.640> can<00:13:17.790> see<00:13:17.970> it<00:13:18.320> spiraling<00:13:19.320> in<00:13:19.470> this 00:13:19.610 --> 00:13:19.620 align:start position:0% one you can see it spiraling in this 00:13:19.620 --> 00:13:25.040 align:start position:0% one you can see it spiraling in this circle<00:13:20.040> using<00:13:20.730> that<00:13:21.089> that<00:13:21.870> attack<00:13:22.140> vector<00:13:24.050> and 00:13:25.040 --> 00:13:25.050 align:start position:0% circle using that that attack vector and 00:13:25.050 --> 00:13:27.200 align:start position:0% circle using that that attack vector and so<00:13:25.740> my<00:13:26.070> favorite<00:13:26.339> project<00:13:26.700> right<00:13:26.820> now<00:13:26.850> is<00:13:26.970> this 00:13:27.200 --> 00:13:27.210 align:start position:0% so my favorite project right now is this 00:13:27.210 --> 00:13:28.610 align:start position:0% so my favorite project right now is this little<00:13:27.450> thing<00:13:27.480> we're<00:13:27.660> calling<00:13:27.960> mascara<00:13:28.350> and 00:13:28.610 --> 00:13:28.620 align:start position:0% little thing we're calling mascara and 00:13:28.620 --> 00:13:31.180 align:start position:0% little thing we're calling mascara and it's<00:13:29.010> a<00:13:29.190> sort<00:13:29.460> of<00:13:29.490> a<00:13:29.610> polyfill<00:13:30.089> for<00:13:30.150> meta<00:13:30.570> mask 00:13:31.180 --> 00:13:31.190 align:start position:0% it's a sort of a polyfill for meta mask 00:13:31.190 --> 00:13:33.800 align:start position:0% it's a sort of a polyfill for meta mask so<00:13:32.190> if<00:13:32.280> you<00:13:32.400> have<00:13:32.550> meta<00:13:32.790> maskings<00:13:33.360> oh<00:13:33.450> yes<00:13:33.690> so 00:13:33.800 --> 00:13:33.810 align:start position:0% so if you have meta maskings oh yes so 00:13:33.810 --> 00:13:35.240 align:start position:0% so if you have meta maskings oh yes so it's<00:13:33.930> it's<00:13:34.170> a<00:13:34.290> little<00:13:34.380> JavaScript<00:13:34.710> file<00:13:35.130> you 00:13:35.240 --> 00:13:35.250 align:start position:0% it's it's a little JavaScript file you 00:13:35.250 --> 00:13:37.850 align:start position:0% it's it's a little JavaScript file you just<00:13:35.280> drop<00:13:35.580> in<00:13:35.700> your<00:13:35.790> DAP<00:13:36.000> and<00:13:36.480> if<00:13:37.230> you<00:13:37.500> if 00:13:37.850 --> 00:13:37.860 align:start position:0% just drop in your DAP and if you if 00:13:37.860 --> 00:13:39.920 align:start position:0% just drop in your DAP and if you if you're<00:13:38.040> using<00:13:38.460> mist<00:13:38.760> or<00:13:38.940> meta<00:13:39.089> mask<00:13:39.270> it<00:13:39.510> works 00:13:39.920 --> 00:13:39.930 align:start position:0% you're using mist or meta mask it works 00:13:39.930 --> 00:13:43.250 align:start position:0% you're using mist or meta mask it works fine<00:13:40.530> if<00:13:41.460> you<00:13:42.240> and<00:13:42.540> if<00:13:42.600> your<00:13:42.750> user<00:13:42.900> doesn't 00:13:43.250 --> 00:13:43.260 align:start position:0% fine if you and if your user doesn't 00:13:43.260 --> 00:13:44.870 align:start position:0% fine if you and if your user doesn't have<00:13:43.410> met<00:13:43.680> a<00:13:43.710> mask<00:13:43.920> but<00:13:44.100> you<00:13:44.220> have<00:13:44.400> mascara 00:13:44.870 --> 00:13:44.880 align:start position:0% have met a mask but you have mascara 00:13:44.880 --> 00:13:47.300 align:start position:0% have met a mask but you have mascara installed<00:13:45.420> it'll<00:13:45.900> work<00:13:46.050> just<00:13:46.320> as<00:13:46.500> if<00:13:46.620> meadow 00:13:47.300 --> 00:13:47.310 align:start position:0% installed it'll work just as if meadow 00:13:47.310 --> 00:13:49.040 align:start position:0% installed it'll work just as if meadow mask<00:13:47.490> was<00:13:47.700> there<00:13:47.910> you'll<00:13:48.480> get<00:13:48.570> a<00:13:48.630> little<00:13:48.810> pop 00:13:49.040 --> 00:13:49.050 align:start position:0% mask was there you'll get a little pop 00:13:49.050 --> 00:13:52.190 align:start position:0% mask was there you'll get a little pop up<00:13:49.260> with<00:13:49.500> your<00:13:49.830> identity<00:13:50.580> management<00:13:51.200> the 00:13:52.190 --> 00:13:52.200 align:start position:0% up with your identity management the 00:13:52.200 --> 00:13:54.440 align:start position:0% up with your identity management the keys<00:13:52.470> are<00:13:52.800> stored<00:13:53.040> in<00:13:53.280> a<00:13:53.400> separate<00:13:53.700> context<00:13:54.270> of 00:13:54.440 --> 00:13:54.450 align:start position:0% keys are stored in a separate context of 00:13:54.450 --> 00:13:56.360 align:start position:0% keys are stored in a separate context of the<00:13:54.540> DAP<00:13:54.690> can<00:13:55.020> access<00:13:55.440> them<00:13:55.680> we<00:13:56.040> still<00:13:56.250> assume 00:13:56.360 --> 00:13:56.370 align:start position:0% the DAP can access them we still assume 00:13:56.370 --> 00:13:58.790 align:start position:0% the DAP can access them we still assume the<00:13:56.700> DAP<00:13:56.910> is<00:13:57.180> is<00:13:57.570> a<00:13:57.660> you<00:13:58.020> know<00:13:58.110> potentially 00:13:58.790 --> 00:13:58.800 align:start position:0% the DAP is is a you know potentially 00:13:58.800 --> 00:14:02.480 align:start position:0% the DAP is is a you know potentially evil<00:13:59.100> actor<00:13:59.870> and<00:14:00.870> likewise<00:14:01.230> you<00:14:01.410> can<00:14:01.589> any<00:14:02.010> DAP 00:14:02.480 --> 00:14:02.490 align:start position:0% evil actor and likewise you can any DAP 00:14:02.490 --> 00:14:05.270 align:start position:0% evil actor and likewise you can any DAP that<00:14:02.790> that<00:14:03.120> uses<00:14:03.450> that<00:14:03.630> polyfill<00:14:04.380> can<00:14:04.980> have 00:14:05.270 --> 00:14:05.280 align:start position:0% that that uses that polyfill can have 00:14:05.280 --> 00:14:07.130 align:start position:0% that that uses that polyfill can have you<00:14:05.700> know<00:14:05.760> send<00:14:06.060> transactions<00:14:06.600> that<00:14:06.780> thing<00:14:07.020> in 00:14:07.130 --> 00:14:07.140 align:start position:0% you know send transactions that thing in 00:14:07.140 --> 00:14:12.050 align:start position:0% you know send transactions that thing in your<00:14:07.470> accounts<00:14:08.250> are<00:14:08.370> already<00:14:08.580> there<00:14:09.890> so<00:14:11.060> thank 00:14:12.050 --> 00:14:12.060 align:start position:0% your accounts are already there so thank 00:14:12.060 --> 00:14:16.720 align:start position:0% your accounts are already there so thank you<00:14:12.120> very<00:14:12.150> much 00:14:16.720 --> 00:14:16.730 align:start position:0% 00:14:16.730 --> 00:14:21.680 align:start position:0% Thank<00:14:17.730> You<00:14:17.940> team<00:14:18.470> Mehta<00:14:19.470> man