WEBVTT Kind: captions Language: en 00:00:00.380 --> 00:00:03.469 align:start position:0% very<00:00:01.380> kind<00:00:01.680> of<00:00:01.709> a<00:00:01.829> diverse<00:00:02.370> team<00:00:02.399> people<00:00:03.209> from 00:00:03.469 --> 00:00:03.479 align:start position:0% very kind of a diverse team people from 00:00:03.479 --> 00:00:06.760 align:start position:0% very kind of a diverse team people from you<00:00:03.840> know<00:00:03.870> all<00:00:04.290> around<00:00:04.470> and<00:00:04.890> I<00:00:04.950> speak<00:00:05.550> for<00:00:05.790> mist 00:00:06.760 --> 00:00:06.770 align:start position:0% you know all around and I speak for mist 00:00:06.770 --> 00:00:10.280 align:start position:0% you know all around and I speak for mist itself<00:00:07.770> and<00:00:08.040> that<00:00:08.759> and<00:00:09.269> the<00:00:09.540> theme<00:00:09.809> community 00:00:10.280 --> 00:00:10.290 align:start position:0% itself and that and the theme community 00:00:10.290 --> 00:00:12.549 align:start position:0% itself and that and the theme community as<00:00:10.410> a<00:00:10.440> whole 00:00:12.549 --> 00:00:12.559 align:start position:0% as a whole 00:00:12.559 --> 00:00:16.160 align:start position:0% as a whole so<00:00:13.559> let's<00:00:14.490> you<00:00:14.879> know<00:00:14.999> move<00:00:15.269> with<00:00:15.450> a<00:00:15.480> web<00:00:15.719> 3<00:00:15.959> echo 00:00:16.160 --> 00:00:16.170 align:start position:0% so let's you know move with a web 3 echo 00:00:16.170 --> 00:00:19.750 align:start position:0% so let's you know move with a web 3 echo system<00:00:16.400> and<00:00:17.400> let's<00:00:17.550> talk<00:00:17.700> a<00:00:17.760> little<00:00:18.030> bit<00:00:18.330> about 00:00:19.750 --> 00:00:19.760 align:start position:0% system and let's talk a little bit about 00:00:19.760 --> 00:00:23.420 align:start position:0% system and let's talk a little bit about the<00:00:20.760> current<00:00:20.970> landscape<00:00:21.540> of<00:00:21.930> it<00:00:22.050> so<00:00:23.010> we've<00:00:23.250> got 00:00:23.420 --> 00:00:23.430 align:start position:0% the current landscape of it so we've got 00:00:23.430 --> 00:00:26.600 align:start position:0% the current landscape of it so we've got mist<00:00:23.730> which<00:00:24.420> is<00:00:24.540> a<00:00:24.570> concept<00:00:25.140> browser<00:00:25.470> I<00:00:25.830> can 00:00:26.600 --> 00:00:26.610 align:start position:0% mist which is a concept browser I can 00:00:26.610 --> 00:00:28.870 align:start position:0% mist which is a concept browser I can tell<00:00:26.940> you<00:00:27.060> more<00:00:27.300> about<00:00:27.360> this<00:00:27.660> later<00:00:27.720> of<00:00:28.530> course 00:00:28.870 --> 00:00:28.880 align:start position:0% tell you more about this later of course 00:00:28.880 --> 00:00:31.430 align:start position:0% tell you more about this later of course we've<00:00:29.880> got<00:00:29.910> the<00:00:30.150> amazing<00:00:30.420> meta<00:00:30.810> mask<00:00:31.050> which<00:00:31.410> is 00:00:31.430 --> 00:00:31.440 align:start position:0% we've got the amazing meta mask which is 00:00:31.440 --> 00:00:35.450 align:start position:0% we've got the amazing meta mask which is a<00:00:32.570> it's<00:00:33.570> not<00:00:33.870> only<00:00:34.289> an<00:00:34.469> extension<00:00:34.859> they<00:00:35.339> are 00:00:35.450 --> 00:00:35.460 align:start position:0% a it's not only an extension they are 00:00:35.460 --> 00:00:37.400 align:start position:0% a it's not only an extension they are much<00:00:35.699> more<00:00:35.940> than<00:00:36.149> that 00:00:37.400 --> 00:00:37.410 align:start position:0% much more than that 00:00:37.410 --> 00:00:41.239 align:start position:0% much more than that more<00:00:37.949> they<00:00:38.219> talk<00:00:38.699> more<00:00:38.730> about<00:00:39.769> some<00:00:40.769> other<00:00:40.949> new 00:00:41.239 --> 00:00:41.249 align:start position:0% more they talk more about some other new 00:00:41.249 --> 00:00:45.439 align:start position:0% more they talk more about some other new projects<00:00:41.820> on<00:00:42.480> the<00:00:42.870> second<00:00:43.589> the<00:00:44.070> same<00:00:44.339> room<00:00:44.579> we 00:00:45.439 --> 00:00:45.449 align:start position:0% projects on the second the same room we 00:00:45.449 --> 00:00:48.169 align:start position:0% projects on the second the same room we also<00:00:45.690> have<00:00:46.260> a<00:00:46.679> brave<00:00:47.069> browser<00:00:47.429> that<00:00:47.789> joined 00:00:48.169 --> 00:00:48.179 align:start position:0% also have a brave browser that joined 00:00:48.179 --> 00:00:51.849 align:start position:0% also have a brave browser that joined this<00:00:48.839> deco<00:00:49.079> system<00:00:49.789> you<00:00:50.789> know<00:00:50.879> two<00:00:51.210> years<00:00:51.359> ago 00:00:51.849 --> 00:00:51.859 align:start position:0% this deco system you know two years ago 00:00:51.859 --> 00:00:55.430 align:start position:0% this deco system you know two years ago opera<00:00:52.859> which<00:00:53.579> recently<00:00:54.179> launched<00:00:54.600> the<00:00:54.899> betta 00:00:55.430 --> 00:00:55.440 align:start position:0% opera which recently launched the betta 00:00:55.440 --> 00:00:59.110 align:start position:0% opera which recently launched the betta which<00:00:56.429> has<00:00:56.609> web<00:00:56.819> 3<00:00:57.089> access<00:00:57.600> you<00:00:58.469> know<00:00:58.559> opera<00:00:58.949> is 00:00:59.110 --> 00:00:59.120 align:start position:0% which has web 3 access you know opera is 00:00:59.120 --> 00:01:02.599 align:start position:0% which has web 3 access you know opera is still<00:01:00.120> the<00:01:00.389> fifth<00:01:00.629> major<00:01:01.019> browser<00:01:01.609> worldwide 00:01:02.599 --> 00:01:02.609 align:start position:0% still the fifth major browser worldwide 00:01:02.609 --> 00:01:07.850 align:start position:0% still the fifth major browser worldwide and<00:01:03.089> this<00:01:03.929> is<00:01:04.019> actually<00:01:04.350> pretty<00:01:04.769> big<00:01:05.479> so<00:01:06.860> we 00:01:07.850 --> 00:01:07.860 align:start position:0% and this is actually pretty big so we 00:01:07.860 --> 00:01:11.749 align:start position:0% and this is actually pretty big so we have<00:01:08.070> wallets<00:01:08.460> and<00:01:08.820> some<00:01:09.060> mobile<00:01:10.759> experiences 00:01:11.749 --> 00:01:11.759 align:start position:0% have wallets and some mobile experiences 00:01:11.759 --> 00:01:13.730 align:start position:0% have wallets and some mobile experiences well<00:01:11.969> mobiletrans<00:01:12.630> browsers<00:01:13.140> ciphers<00:01:13.710> that 00:01:13.730 --> 00:01:13.740 align:start position:0% well mobiletrans browsers ciphers that 00:01:13.740 --> 00:01:19.010 align:start position:0% well mobiletrans browsers ciphers that is<00:01:14.310> of<00:01:14.460> course<00:01:15.350> coinbase<00:01:16.789> and<00:01:17.789> the<00:01:18.689> list<00:01:18.869> is 00:01:19.010 --> 00:01:19.020 align:start position:0% is of course coinbase and the list is 00:01:19.020 --> 00:01:28.120 align:start position:0% is of course coinbase and the list is growing<00:01:23.570> can<00:01:24.570> I<00:01:24.689> have<00:01:24.930> this<00:01:25.340> all<00:01:26.340> right 00:01:28.120 --> 00:01:28.130 align:start position:0% growing can I have this all right 00:01:28.130 --> 00:01:33.230 align:start position:0% growing can I have this all right maybe<00:01:29.130> that's<00:01:29.369> too<00:01:29.579> far<00:01:29.789> oh<00:01:30.770> yeah<00:01:32.060> so<00:01:33.060> let's 00:01:33.230 --> 00:01:33.240 align:start position:0% maybe that's too far oh yeah so let's 00:01:33.240 --> 00:01:34.910 align:start position:0% maybe that's too far oh yeah so let's talk<00:01:33.359> about<00:01:33.420> miss<00:01:33.899> history<00:01:34.409> and<00:01:34.560> updates 00:01:34.910 --> 00:01:34.920 align:start position:0% talk about miss history and updates 00:01:34.920 --> 00:01:38.630 align:start position:0% talk about miss history and updates actually<00:01:35.700> actually<00:01:36.000> this<00:01:36.329> is<00:01:36.509> our<00:01:36.710> fifth<00:01:37.710> Def 00:01:38.630 --> 00:01:38.640 align:start position:0% actually actually this is our fifth Def 00:01:38.640 --> 00:01:42.590 align:start position:0% actually actually this is our fifth Def Con<00:01:39.200> we've<00:01:40.200> heard<00:01:40.640> here<00:01:41.640> since<00:01:42.000> the<00:01:42.119> start 00:01:42.590 --> 00:01:42.600 align:start position:0% Con we've heard here since the start 00:01:42.600 --> 00:01:45.889 align:start position:0% Con we've heard here since the start Alex<00:01:43.289> which<00:01:43.500> is<00:01:43.710> there<00:01:44.009> he<00:01:44.850> presented<00:01:45.570> the 00:01:45.889 --> 00:01:45.899 align:start position:0% Alex which is there he presented the 00:01:45.899 --> 00:01:49.240 align:start position:0% Alex which is there he presented the vision<00:01:46.289> and<00:01:46.500> and 00:01:49.240 --> 00:01:49.250 align:start position:0% 00:01:49.250 --> 00:01:52.750 align:start position:0% Alex<00:01:50.250> presented<00:01:50.640> a<00:01:50.730> vision<00:01:50.960> and<00:01:51.960> then 00:01:52.750 --> 00:01:52.760 align:start position:0% Alex presented a vision and then 00:01:52.760 --> 00:01:56.210 align:start position:0% Alex presented a vision and then inspired<00:01:53.760> lots<00:01:54.030> of<00:01:54.150> developers<00:01:54.800> all<00:01:55.800> around 00:01:56.210 --> 00:01:56.220 align:start position:0% inspired lots of developers all around 00:01:56.220 --> 00:01:59.660 align:start position:0% inspired lots of developers all around the<00:01:56.400> community<00:01:56.550> to<00:01:57.240> build<00:01:57.630> other<00:01:58.590> things<00:01:59.010> on 00:01:59.660 --> 00:01:59.670 align:start position:0% the community to build other things on 00:01:59.670 --> 00:02:04.520 align:start position:0% the community to build other things on it<00:01:59.940> and<00:01:59.970> around<00:02:00.420> it<00:02:03.140> we<00:02:04.140> good 00:02:04.520 --> 00:02:04.530 align:start position:0% it and around it we good 00:02:04.530 --> 00:02:08.060 align:start position:0% it and around it we good oh<00:02:05.360> yeah<00:02:06.390> so<00:02:06.630> that's<00:02:06.900> Gavin<00:02:07.440> and<00:02:07.590> Alex<00:02:07.860> you 00:02:08.060 --> 00:02:08.070 align:start position:0% oh yeah so that's Gavin and Alex you 00:02:08.070 --> 00:02:11.240 align:start position:0% oh yeah so that's Gavin and Alex you know<00:02:08.330> several<00:02:09.330> years<00:02:09.450> ago<00:02:09.710> they've<00:02:10.710> gone<00:02:10.920> zero 00:02:11.240 --> 00:02:11.250 align:start position:0% know several years ago they've gone zero 00:02:11.250 --> 00:02:15.320 align:start position:0% know several years ago they've gone zero and<00:02:11.730> then<00:02:12.420> they've<00:02:12.660> gone<00:02:12.960> one<00:02:13.940> can<00:02:14.940> we<00:02:15.000> have<00:02:15.150> it 00:02:15.320 --> 00:02:15.330 align:start position:0% and then they've gone one can we have it 00:02:15.330 --> 00:02:22.100 align:start position:0% and then they've gone one can we have it oh<00:02:17.480> yeah<00:02:18.480> DEFCON<00:02:18.930> one<00:02:19.640> and<00:02:20.640> then<00:02:21.360> while<00:02:21.780> miss 00:02:22.100 --> 00:02:22.110 align:start position:0% oh yeah DEFCON one and then while miss 00:02:22.110 --> 00:02:27.640 align:start position:0% oh yeah DEFCON one and then while miss was<00:02:23.180> a<00:02:24.800> better<00:02:25.800> you<00:02:26.100> know<00:02:26.250> structured<00:02:27.090> concept 00:02:27.640 --> 00:02:27.650 align:start position:0% was a better you know structured concept 00:02:27.650 --> 00:02:30.500 align:start position:0% was a better you know structured concept we<00:02:28.650> got<00:02:28.830> you<00:02:29.010> know<00:02:29.160> lots<00:02:29.490> of<00:02:29.670> wireframes<00:02:30.240> and 00:02:30.500 --> 00:02:30.510 align:start position:0% we got you know lots of wireframes and 00:02:30.510 --> 00:02:34.730 align:start position:0% we got you know lots of wireframes and all<00:02:30.600> and<00:02:31.200> then<00:02:31.500> came<00:02:31.920> the<00:02:32.070> few<00:02:32.310> mullet<00:02:32.730> oh<00:02:33.740> yeah 00:02:34.730 --> 00:02:34.740 align:start position:0% all and then came the few mullet oh yeah 00:02:34.740 --> 00:02:42.170 align:start position:0% all and then came the few mullet oh yeah DEFCON<00:02:35.100> two<00:02:36.020> three<00:02:37.760> that's<00:02:38.760> me<00:02:38.910> and<00:02:39.800> four<00:02:40.800> so<00:02:41.580> I 00:02:42.170 --> 00:02:42.180 align:start position:0% DEFCON two three that's me and four so I 00:02:42.180 --> 00:02:45.190 align:start position:0% DEFCON two three that's me and four so I like<00:02:42.780> to<00:02:42.810> you<00:02:43.080> know<00:02:43.140> make<00:02:43.440> a<00:02:43.470> little<00:02:43.740> bit<00:02:44.040> of 00:02:45.190 --> 00:02:45.200 align:start position:0% like to you know make a little bit of 00:02:45.200 --> 00:02:47.030 align:start position:0% like to you know make a little bit of advertising<00:02:46.200> here<00:02:46.380> there<00:02:46.830> are<00:02:46.920> some 00:02:47.030 --> 00:02:47.040 align:start position:0% advertising here there are some 00:02:47.040 --> 00:02:50.300 align:start position:0% advertising here there are some interesting<00:02:47.430> talks<00:02:47.700> from<00:02:47.970> our<00:02:48.980> former<00:02:49.980> and 00:02:50.300 --> 00:02:50.310 align:start position:0% interesting talks from our former and 00:02:50.310 --> 00:02:51.860 align:start position:0% interesting talks from our former and current<00:02:50.340> team<00:02:51.030> members<00:02:51.360> so<00:02:51.570> there's 00:02:51.860 --> 00:02:51.870 align:start position:0% current team members so there's 00:02:51.870 --> 00:02:53.770 align:start position:0% current team members so there's universal<00:02:52.410> logins<00:02:52.680> by<00:02:52.830> Alex<00:02:53.160> later<00:02:53.430> today 00:02:53.770 --> 00:02:53.780 align:start position:0% universal logins by Alex later today 00:02:53.780 --> 00:02:57.170 align:start position:0% universal logins by Alex later today this<00:02:54.780> room<00:02:55.130> introducing<00:02:56.130> formality<00:02:56.940> by 00:02:57.170 --> 00:02:57.180 align:start position:0% this room introducing formality by 00:02:57.180 --> 00:03:01.760 align:start position:0% this room introducing formality by Victor<00:02:57.540> maíam<00:02:58.580> browser<00:02:59.580> web<00:02:59.910> 3.0<00:03:00.750> how<00:03:01.530> to<00:03:01.590> be 00:03:01.760 --> 00:03:01.770 align:start position:0% Victor maíam browser web 3.0 how to be 00:03:01.770 --> 00:03:04.220 align:start position:0% Victor maíam browser web 3.0 how to be secured<00:03:02.459> by<00:03:02.610> three<00:03:02.820> clients<00:03:03.060> that's<00:03:03.570> actually 00:03:04.220 --> 00:03:04.230 align:start position:0% secured by three clients that's actually 00:03:04.230 --> 00:03:08.810 align:start position:0% secured by three clients that's actually a<00:03:04.440> missed<00:03:05.360> thing<00:03:06.360> and<00:03:07.340> here's<00:03:08.340> our<00:03:08.550> current 00:03:08.810 --> 00:03:08.820 align:start position:0% a missed thing and here's our current 00:03:08.820 --> 00:03:14.630 align:start position:0% a missed thing and here's our current team<00:03:09.560> we<00:03:10.560> got<00:03:11.060> Phillip<00:03:12.060> myself<00:03:12.810> mark<00:03:13.620> Alex<00:03:14.430> and 00:03:14.630 --> 00:03:14.640 align:start position:0% team we got Phillip myself mark Alex and 00:03:14.640 --> 00:03:16.640 align:start position:0% team we got Phillip myself mark Alex and Ryan<00:03:14.790> we<00:03:15.660> managed<00:03:15.900> to<00:03:15.959> grow<00:03:16.260> the<00:03:16.470> team 00:03:16.640 --> 00:03:16.650 align:start position:0% Ryan we managed to grow the team 00:03:16.650 --> 00:03:20.180 align:start position:0% Ryan we managed to grow the team actually<00:03:17.040> we<00:03:17.370> were<00:03:17.519> you<00:03:17.850> know<00:03:17.970> some<00:03:18.330> dark<00:03:19.190> you 00:03:20.180 --> 00:03:20.190 align:start position:0% actually we were you know some dark you 00:03:20.190 --> 00:03:22.250 align:start position:0% actually we were you know some dark you know<00:03:20.370> times<00:03:20.700> where<00:03:20.970> we<00:03:21.090> had<00:03:21.239> you<00:03:21.420> know<00:03:21.450> two 00:03:22.250 --> 00:03:22.260 align:start position:0% know times where we had you know two 00:03:22.260 --> 00:03:24.140 align:start position:0% know times where we had you know two developers<00:03:22.769> now<00:03:23.070> we<00:03:23.130> thanks<00:03:23.970> to<00:03:24.060> the 00:03:24.140 --> 00:03:24.150 align:start position:0% developers now we thanks to the 00:03:24.150 --> 00:03:26.800 align:start position:0% developers now we thanks to the foundation<00:03:24.540> we've<00:03:24.930> got<00:03:25.110> plenty<00:03:25.590> of<00:03:25.769> them 00:03:26.800 --> 00:03:26.810 align:start position:0% foundation we've got plenty of them 00:03:26.810 --> 00:03:29.240 align:start position:0% foundation we've got plenty of them let's<00:03:27.810> talk<00:03:27.930> about<00:03:28.050> things<00:03:28.769> that<00:03:28.860> we've<00:03:29.100> done 00:03:29.240 --> 00:03:29.250 align:start position:0% let's talk about things that we've done 00:03:29.250 --> 00:03:33.759 align:start position:0% let's talk about things that we've done this<00:03:30.000> year<00:03:30.350> so<00:03:31.350> there<00:03:31.980> comes<00:03:32.160> a<00:03:32.250> time<00:03:32.280> where<00:03:32.850> a 00:03:33.759 --> 00:03:33.769 align:start position:0% this year so there comes a time where a 00:03:33.769 --> 00:03:38.360 align:start position:0% this year so there comes a time where a user<00:03:35.269> executes<00:03:36.269> a<00:03:36.540> transaction<00:03:37.110> so<00:03:37.800> that's 00:03:38.360 --> 00:03:38.370 align:start position:0% user executes a transaction so that's 00:03:38.370 --> 00:03:44.650 align:start position:0% user executes a transaction so that's actually<00:03:40.790> one<00:03:41.790> thing<00:03:42.060> that<00:03:42.830> should<00:03:43.830> be<00:03:43.890> really 00:03:44.650 --> 00:03:44.660 align:start position:0% actually one thing that should be really 00:03:44.660 --> 00:03:49.970 align:start position:0% actually one thing that should be really carefully<00:03:45.800> thought<00:03:46.800> about<00:03:47.090> so<00:03:48.800> we've<00:03:49.800> put 00:03:49.970 --> 00:03:49.980 align:start position:0% carefully thought about so we've put 00:03:49.980 --> 00:03:52.640 align:start position:0% carefully thought about so we've put lots<00:03:50.190> of<00:03:50.310> thought<00:03:50.550> into<00:03:50.730> that<00:03:51.650> because 00:03:52.640 --> 00:03:52.650 align:start position:0% lots of thought into that because 00:03:52.650 --> 00:03:54.710 align:start position:0% lots of thought into that because executing<00:03:53.519> transactions<00:03:54.030> is<00:03:54.180> actually<00:03:54.630> the 00:03:54.710 --> 00:03:54.720 align:start position:0% executing transactions is actually the 00:03:54.720 --> 00:03:57.349 align:start position:0% executing transactions is actually the biggest<00:03:55.549> emotion<00:03:56.549> of<00:03:56.639> picking<00:03:57.060> the<00:03:57.180> user 00:03:57.349 --> 00:03:57.359 align:start position:0% biggest emotion of picking the user 00:03:57.359 --> 00:04:01.410 align:start position:0% biggest emotion of picking the user experience<00:03:58.370> picture<00:03:59.370> that<00:03:59.519> you're<00:04:00.299> you<00:04:00.600> know 00:04:01.410 --> 00:04:01.420 align:start position:0% experience picture that you're you know 00:04:01.420 --> 00:04:07.350 align:start position:0% experience picture that you're you know three<00:04:02.730> 100,000<00:04:03.730> ether<00:04:05.010> well<00:04:06.010> I'm<00:04:06.580> pretty<00:04:07.209> sure 00:04:07.350 --> 00:04:07.360 align:start position:0% three 100,000 ether well I'm pretty sure 00:04:07.360 --> 00:04:10.080 align:start position:0% three 100,000 ether well I'm pretty sure that<00:04:07.480> your<00:04:07.780> hands<00:04:08.050> would<00:04:08.170> be<00:04:08.200> sweaty<00:04:08.970> you<00:04:09.970> know 00:04:10.080 --> 00:04:10.090 align:start position:0% that your hands would be sweaty you know 00:04:10.090 --> 00:04:13.050 align:start position:0% that your hands would be sweaty you know you're<00:04:10.739> deploying<00:04:11.739> a<00:04:11.980> mood<00:04:12.310> to<00:04:12.430> sig<00:04:12.640> wallet 00:04:13.050 --> 00:04:13.060 align:start position:0% you're deploying a mood to sig wallet 00:04:13.060 --> 00:04:18.870 align:start position:0% you're deploying a mood to sig wallet that<00:04:13.599> can<00:04:13.750> be<00:04:13.840> dangerous<00:04:14.020> sometimes<00:04:17.430> so<00:04:18.430> in 00:04:18.870 --> 00:04:18.880 align:start position:0% that can be dangerous sometimes so in 00:04:18.880 --> 00:04:23.520 align:start position:0% that can be dangerous sometimes so in order<00:04:19.000> to<00:04:19.950> know<00:04:20.950> to<00:04:21.010> to<00:04:21.579> design<00:04:22.000> and<00:04:22.480> oh<00:04:22.840> thank 00:04:23.520 --> 00:04:23.530 align:start position:0% order to know to to design and oh thank 00:04:23.530 --> 00:04:26.730 align:start position:0% order to know to to design and oh thank you<00:04:23.650> guys<00:04:23.830> in<00:04:24.700> order<00:04:24.880> to<00:04:24.970> design<00:04:25.120> a<00:04:25.410> pretty<00:04:26.410> and 00:04:26.730 --> 00:04:26.740 align:start position:0% you guys in order to design a pretty and 00:04:26.740 --> 00:04:31.050 align:start position:0% you guys in order to design a pretty and useful<00:04:27.639> and<00:04:29.100> transaction<00:04:30.100> window<00:04:30.340> we<00:04:30.760> had<00:04:30.910> to 00:04:31.050 --> 00:04:31.060 align:start position:0% useful and transaction window we had to 00:04:31.060 --> 00:04:33.780 align:start position:0% useful and transaction window we had to you<00:04:31.180> know<00:04:31.300> the<00:04:31.720> user<00:04:31.900> has<00:04:32.110> to<00:04:32.290> know<00:04:32.729> at<00:04:33.729> a 00:04:33.780 --> 00:04:33.790 align:start position:0% you know the user has to know at a 00:04:33.790 --> 00:04:35.850 align:start position:0% you know the user has to know at a glance<00:04:33.910> what's<00:04:34.479> happening<00:04:34.930> it<00:04:35.500> has<00:04:35.650> to<00:04:35.770> be 00:04:35.850 --> 00:04:35.860 align:start position:0% glance what's happening it has to be 00:04:35.860 --> 00:04:37.950 align:start position:0% glance what's happening it has to be around<00:04:36.070> crafted<00:04:36.520> interface<00:04:36.910> with<00:04:37.180> pretty 00:04:37.950 --> 00:04:37.960 align:start position:0% around crafted interface with pretty 00:04:37.960 --> 00:04:42.629 align:start position:0% around crafted interface with pretty clear<00:04:38.290> instructions<00:04:39.660> this<00:04:40.660> is<00:04:40.720> not<00:04:41.050> it<00:04:41.639> this 00:04:42.629 --> 00:04:42.639 align:start position:0% clear instructions this is not it this 00:04:42.639 --> 00:04:46.670 align:start position:0% clear instructions this is not it this is<00:04:42.820> how<00:04:42.910> it<00:04:43.030> used<00:04:43.180> to<00:04:43.330> be<00:04:44.550> but<00:04:45.550> we<00:04:45.700> were<00:04:45.820> pretty 00:04:46.670 --> 00:04:46.680 align:start position:0% is how it used to be but we were pretty 00:04:46.680 --> 00:04:49.230 align:start position:0% is how it used to be but we were pretty you<00:04:47.680> know<00:04:47.710> by<00:04:47.950> the<00:04:48.010> time<00:04:48.250> we<00:04:48.580> did<00:04:48.729> that<00:04:48.790> we<00:04:49.120> were 00:04:49.230 --> 00:04:49.240 align:start position:0% you know by the time we did that we were 00:04:49.240 --> 00:04:50.370 align:start position:0% you know by the time we did that we were pretty<00:04:49.510> happy<00:04:49.600> with<00:04:50.020> that 00:04:50.370 --> 00:04:50.380 align:start position:0% pretty happy with that 00:04:50.380 --> 00:04:53.940 align:start position:0% pretty happy with that but<00:04:51.190> now<00:04:51.340> we're<00:04:51.550> changing<00:04:51.880> this<00:04:52.950> just 00:04:53.940 --> 00:04:53.950 align:start position:0% but now we're changing this just 00:04:53.950 --> 00:04:57.090 align:start position:0% but now we're changing this just something<00:04:54.310> you<00:04:54.580> know<00:04:54.700> more<00:04:55.169> clear<00:04:56.169> more<00:04:56.710> you 00:04:57.090 --> 00:04:57.100 align:start position:0% something you know more clear more you 00:04:57.100 --> 00:05:00.540 align:start position:0% something you know more clear more you know<00:04:57.220> straightforward<00:04:59.010> but<00:05:00.010> it<00:05:00.130> doesn't<00:05:00.430> end 00:05:00.540 --> 00:05:00.550 align:start position:0% know straightforward but it doesn't end 00:05:00.550 --> 00:05:02.610 align:start position:0% know straightforward but it doesn't end that<00:05:00.639> of<00:05:00.910> course<00:05:01.210> you<00:05:01.870> can<00:05:02.020> transfer<00:05:02.410> you<00:05:02.530> know 00:05:02.610 --> 00:05:02.620 align:start position:0% that of course you can transfer you know 00:05:02.620 --> 00:05:07.050 align:start position:0% that of course you can transfer you know tokens<00:05:03.190> you<00:05:03.490> can<00:05:03.669> execute<00:05:04.000> functions<00:05:05.340> and<00:05:06.340> we 00:05:07.050 --> 00:05:07.060 align:start position:0% tokens you can execute functions and we 00:05:07.060 --> 00:05:08.880 align:start position:0% tokens you can execute functions and we are<00:05:07.210> you<00:05:07.450> know<00:05:07.570> growing<00:05:08.140> a<00:05:08.229> bit<00:05:08.380> further<00:05:08.650> than 00:05:08.880 --> 00:05:08.890 align:start position:0% are you know growing a bit further than 00:05:08.890 --> 00:05:10.700 align:start position:0% are you know growing a bit further than that<00:05:08.919> well<00:05:09.490> the<00:05:09.669> user<00:05:09.850> types<00:05:10.180> password 00:05:10.700 --> 00:05:10.710 align:start position:0% that well the user types password 00:05:10.710 --> 00:05:15.029 align:start position:0% that well the user types password execuse<00:05:11.710> transaction<00:05:13.530> then<00:05:14.530> we<00:05:14.620> can<00:05:14.770> have<00:05:14.919> you 00:05:15.029 --> 00:05:15.039 align:start position:0% execuse transaction then we can have you 00:05:15.039 --> 00:05:19.590 align:start position:0% execuse transaction then we can have you know<00:05:15.120> this<00:05:16.120> kind<00:05:16.570> of<00:05:17.550> description<00:05:18.550> thanks<00:05:19.450> to 00:05:19.590 --> 00:05:19.600 align:start position:0% know this kind of description thanks to 00:05:19.600 --> 00:05:22.380 align:start position:0% know this kind of description thanks to nice<00:05:19.780> back<00:05:20.050> roads<00:05:20.380> back<00:05:20.850> also<00:05:21.850> you<00:05:22.300> know 00:05:22.380 --> 00:05:22.390 align:start position:0% nice back roads back also you know 00:05:22.390 --> 00:05:25.010 align:start position:0% nice back roads back also you know thanks<00:05:22.750> to<00:05:22.780> ENS<00:05:23.260> we<00:05:23.440> can<00:05:23.590> have<00:05:23.770> these<00:05:23.979> kind<00:05:24.280> of 00:05:25.010 --> 00:05:25.020 align:start position:0% thanks to ENS we can have these kind of 00:05:25.020 --> 00:05:27.870 align:start position:0% thanks to ENS we can have these kind of more<00:05:26.020> description<00:05:26.830> descriptive<00:05:27.669> information 00:05:27.870 --> 00:05:27.880 align:start position:0% more description descriptive information 00:05:27.880 --> 00:05:32.070 align:start position:0% more description descriptive information about<00:05:28.300> addresses<00:05:29.880> so<00:05:30.880> yeah<00:05:31.240> this<00:05:31.570> is<00:05:31.690> all<00:05:31.900> new 00:05:32.070 --> 00:05:32.080 align:start position:0% about addresses so yeah this is all new 00:05:32.080 --> 00:05:34.020 align:start position:0% about addresses so yeah this is all new transaction<00:05:32.530> window<00:05:32.650> we<00:05:33.010> we<00:05:33.400> gather<00:05:33.669> and 00:05:34.020 --> 00:05:34.030 align:start position:0% transaction window we we gather and 00:05:34.030 --> 00:05:37.320 align:start position:0% transaction window we we gather and makes<00:05:34.500> lots<00:05:35.500> of<00:05:35.710> information<00:05:36.430> together<00:05:36.850> so 00:05:37.320 --> 00:05:37.330 align:start position:0% makes lots of information together so 00:05:37.330 --> 00:05:40.860 align:start position:0% makes lots of information together so we've<00:05:37.990> got<00:05:38.169> gas<00:05:38.890> estimation<00:05:39.520> pricey<00:05:40.450> currency 00:05:40.860 --> 00:05:40.870 align:start position:0% we've got gas estimation pricey currency 00:05:40.870 --> 00:05:45.450 align:start position:0% we've got gas estimation pricey currency feat<00:05:41.729> function<00:05:42.729> API<00:05:43.030> signatures<00:05:43.770> at<00:05:44.770> spec<00:05:45.130> and 00:05:45.450 --> 00:05:45.460 align:start position:0% feat function API signatures at spec and 00:05:45.460 --> 00:05:50.070 align:start position:0% feat function API signatures at spec and in<00:05:46.210> yet<00:05:46.390> Yanis<00:05:46.780> lookup<00:05:47.410> address<00:05:48.220> lookup<00:05:49.080> well 00:05:50.070 --> 00:05:50.080 align:start position:0% in yet Yanis lookup address lookup well 00:05:50.080 --> 00:05:55.469 align:start position:0% in yet Yanis lookup address lookup well syncing<00:05:50.650> that's<00:05:51.010> a<00:05:51.160> major<00:05:51.370> issue<00:05:54.120> back<00:05:55.120> back 00:05:55.469 --> 00:05:55.479 align:start position:0% syncing that's a major issue back back 00:05:55.479 --> 00:05:56.219 align:start position:0% syncing that's a major issue back back in<00:05:55.630> time 00:05:56.219 --> 00:05:56.229 align:start position:0% in time 00:05:56.229 --> 00:05:59.879 align:start position:0% in time back<00:05:56.500> then<00:05:56.740> we<00:05:56.950> one<00:05:57.460> could<00:05:58.770> sink<00:05:59.770> the 00:05:59.879 --> 00:05:59.889 align:start position:0% back then we one could sink the 00:05:59.889 --> 00:06:03.150 align:start position:0% back then we one could sink the blockchain<00:06:00.130> in<00:06:00.789> a<00:06:00.910> matter<00:06:01.090> of<00:06:01.180> minutes<00:06:01.389> so<00:06:02.160> we 00:06:03.150 --> 00:06:03.160 align:start position:0% blockchain in a matter of minutes so we 00:06:03.160 --> 00:06:05.640 align:start position:0% blockchain in a matter of minutes so we know<00:06:03.340> how<00:06:03.610> it<00:06:03.669> is<00:06:03.880> the<00:06:04.000> state<00:06:04.270> of<00:06:04.300> its<00:06:04.660> of<00:06:05.440> this 00:06:05.640 --> 00:06:05.650 align:start position:0% know how it is the state of its of this 00:06:05.650 --> 00:06:09.890 align:start position:0% know how it is the state of its of this nowadays<00:06:07.260> and<00:06:08.260> we<00:06:08.500> used<00:06:08.650> to<00:06:08.710> have<00:06:08.770> this 00:06:09.890 --> 00:06:09.900 align:start position:0% nowadays and we used to have this 00:06:09.900 --> 00:06:11.909 align:start position:0% nowadays and we used to have this loading<00:06:10.900> screen 00:06:11.909 --> 00:06:11.919 align:start position:0% loading screen 00:06:11.919 --> 00:06:13.800 align:start position:0% loading screen it<00:06:12.430> was<00:06:12.580> actually<00:06:12.909> needed<00:06:13.240> because<00:06:13.419> otherwise 00:06:13.800 --> 00:06:13.810 align:start position:0% it was actually needed because otherwise 00:06:13.810 --> 00:06:16.409 align:start position:0% it was actually needed because otherwise all<00:06:14.259> the<00:06:14.740> taps<00:06:14.919> that<00:06:15.009> subscribe<00:06:15.669> it<00:06:15.789> to<00:06:15.969> block 00:06:16.409 --> 00:06:16.419 align:start position:0% all the taps that subscribe it to block 00:06:16.419 --> 00:06:19.429 align:start position:0% all the taps that subscribe it to block new<00:06:16.719> blocks<00:06:17.349> without<00:06:17.889> being<00:06:18.520> bombarded<00:06:18.999> by 00:06:19.429 --> 00:06:19.439 align:start position:0% new blocks without being bombarded by 00:06:19.439 --> 00:06:24.629 align:start position:0% new blocks without being bombarded by you<00:06:20.439> know<00:06:20.529> events<00:06:20.889> from<00:06:21.449> from<00:06:22.449> the<00:06:22.569> node<00:06:23.249> so<00:06:24.249> in 00:06:24.629 --> 00:06:24.639 align:start position:0% you know events from from the node so in 00:06:24.639 --> 00:06:26.790 align:start position:0% you know events from from the node so in order<00:06:24.759> to<00:06:24.909> cope<00:06:25.300> with<00:06:25.569> that<00:06:25.779> and<00:06:26.020> to<00:06:26.289> meet<00:06:26.499> user 00:06:26.790 --> 00:06:26.800 align:start position:0% order to cope with that and to meet user 00:06:26.800 --> 00:06:29.670 align:start position:0% order to cope with that and to meet user expectations<00:06:27.610> we<00:06:27.909> could<00:06:28.060> have<00:06:28.210> you<00:06:28.479> know<00:06:28.680> make 00:06:29.670 --> 00:06:29.680 align:start position:0% expectations we could have you know make 00:06:29.680 --> 00:06:34.769 align:start position:0% expectations we could have you know make the<00:06:29.860> bass<00:06:30.610> loader<00:06:30.939> screen<00:06:31.270> in<00:06:31.479> the<00:06:31.689> world<00:06:33.779> I'm 00:06:34.769 --> 00:06:34.779 align:start position:0% the bass loader screen in the world I'm 00:06:34.779 --> 00:06:36.749 align:start position:0% the bass loader screen in the world I'm pretty<00:06:35.349> sure<00:06:35.529> that<00:06:35.800> no<00:06:35.979> one<00:06:36.129> would<00:06:36.279> stare<00:06:36.639> at 00:06:36.749 --> 00:06:36.759 align:start position:0% pretty sure that no one would stare at 00:06:36.759 --> 00:06:38.959 align:start position:0% pretty sure that no one would stare at it<00:06:36.909> for<00:06:37.270> you<00:06:37.449> know<00:06:37.569> more<00:06:37.840> than<00:06:37.960> five<00:06:38.229> minutes 00:06:38.959 --> 00:06:38.969 align:start position:0% it for you know more than five minutes 00:06:38.969 --> 00:06:44.580 align:start position:0% it for you know more than five minutes so<00:06:39.969> we<00:06:40.150> had<00:06:40.270> to<00:06:40.419> be<00:06:40.810> creative<00:06:41.319> and<00:06:42.479> we<00:06:43.590> devised 00:06:44.580 --> 00:06:44.590 align:start position:0% so we had to be creative and we devised 00:06:44.590 --> 00:06:48.899 align:start position:0% so we had to be creative and we devised that<00:06:44.740> a<00:06:44.800> mechanism<00:06:45.189> to<00:06:46.110> to<00:06:47.110> have<00:06:47.400> two<00:06:48.400> syncing 00:06:48.899 --> 00:06:48.909 align:start position:0% that a mechanism to to have two syncing 00:06:48.909 --> 00:06:51.450 align:start position:0% that a mechanism to to have two syncing mechanisms<00:06:49.479> one<00:06:50.259> with<00:06:50.439> a<00:06:50.469> remote<00:06:50.830> node<00:06:51.009> you 00:06:51.450 --> 00:06:51.460 align:start position:0% mechanisms one with a remote node you 00:06:51.460 --> 00:06:55.290 align:start position:0% mechanisms one with a remote node you can<00:06:51.610> see<00:06:51.759> in<00:06:52.479> food<00:06:52.719> over<00:06:53.020> there<00:06:53.169> and<00:06:54.300> a 00:06:55.290 --> 00:06:55.300 align:start position:0% can see in food over there and a 00:06:55.300 --> 00:06:57.629 align:start position:0% can see in food over there and a background<00:06:55.960> sync<00:06:56.289> using<00:06:56.979> go<00:06:57.069> with<00:06:57.189> you<00:06:57.370> my 00:06:57.629 --> 00:06:57.639 align:start position:0% background sync using go with you my 00:06:57.639 --> 00:07:02.640 align:start position:0% background sync using go with you my client<00:06:58.060> or<00:06:58.270> has<00:06:58.689> sync<00:06:59.400> and<00:07:00.400> when<00:07:01.409> this<00:07:02.409> node 00:07:02.640 --> 00:07:02.650 align:start position:0% client or has sync and when this node 00:07:02.650 --> 00:07:04.980 align:start position:0% client or has sync and when this node was<00:07:02.949> up<00:07:03.550> to<00:07:03.729> date<00:07:03.879> it<00:07:04.150> would<00:07:04.240> take<00:07:04.479> over<00:07:04.870> the 00:07:04.980 --> 00:07:04.990 align:start position:0% was up to date it would take over the 00:07:04.990 --> 00:07:08.820 align:start position:0% was up to date it would take over the connection<00:07:05.439> as<00:07:06.009> a<00:07:06.189> main<00:07:06.520> one<00:07:06.699> so<00:07:07.599> ideally<00:07:08.439> the 00:07:08.820 --> 00:07:08.830 align:start position:0% connection as a main one so ideally the 00:07:08.830 --> 00:07:13.920 align:start position:0% connection as a main one so ideally the user<00:07:08.979> to<00:07:09.219> wait<00:07:09.610> a<00:07:10.210> little<00:07:10.689> time<00:07:11.099> to<00:07:12.099> see<00:07:12.930> and 00:07:13.920 --> 00:07:13.930 align:start position:0% user to wait a little time to see and 00:07:13.930 --> 00:07:18.209 align:start position:0% user to wait a little time to see and interact<00:07:14.199> with<00:07:14.620> the<00:07:15.159> bar<00:07:15.339> chain<00:07:17.069> when<00:07:18.069> the 00:07:18.209 --> 00:07:18.219 align:start position:0% interact with the bar chain when the 00:07:18.219 --> 00:07:20.850 align:start position:0% interact with the bar chain when the node<00:07:18.400> takes<00:07:18.759> over<00:07:19.199> it<00:07:20.199> would<00:07:20.259> be<00:07:20.409> you<00:07:20.560> know<00:07:20.680> in 00:07:20.850 --> 00:07:20.860 align:start position:0% node takes over it would be you know in 00:07:20.860 --> 00:07:23.820 align:start position:0% node takes over it would be you know in a<00:07:20.919> totally<00:07:21.279> secure<00:07:21.490> environment<00:07:22.800> totally<00:07:23.800> a 00:07:23.820 --> 00:07:23.830 align:start position:0% a totally secure environment totally a 00:07:23.830 --> 00:07:29.540 align:start position:0% a totally secure environment totally a centralized<00:07:24.339> fashion<00:07:24.610> oh<00:07:25.469> yeah<00:07:27.149> hi<00:07:28.149> Peter 00:07:29.540 --> 00:07:29.550 align:start position:0% centralized fashion oh yeah hi Peter 00:07:29.550 --> 00:07:32.070 align:start position:0% centralized fashion oh yeah hi Peter that's<00:07:30.550> responsible<00:07:31.210> for<00:07:31.419> the<00:07:31.539> light<00:07:31.689> client 00:07:32.070 --> 00:07:32.080 align:start position:0% that's responsible for the light client 00:07:32.080 --> 00:07:34.129 align:start position:0% that's responsible for the light client and<00:07:32.439> agree<00:07:32.649> with<00:07:32.740> you 00:07:34.129 --> 00:07:34.139 align:start position:0% and agree with you 00:07:34.139 --> 00:07:37.019 align:start position:0% and agree with you so<00:07:35.139> we've<00:07:35.379> got<00:07:35.529> this<00:07:35.680> which<00:07:36.399> we<00:07:36.580> call<00:07:36.759> their 00:07:37.019 --> 00:07:37.029 align:start position:0% so we've got this which we call their 00:07:37.029 --> 00:07:39.360 align:start position:0% so we've got this which we call their notes<00:07:37.300> instantly<00:07:37.990> connected<00:07:38.500> to<00:07:38.919> the<00:07:39.039> barge<00:07:39.189> a 00:07:39.360 --> 00:07:39.370 align:start position:0% notes instantly connected to the barge a 00:07:39.370 --> 00:07:44.459 align:start position:0% notes instantly connected to the barge a via<00:07:39.610> remote<00:07:40.229> provider<00:07:42.659> like<00:07:43.659> line<00:07:43.899> syncing<00:07:44.379> in 00:07:44.459 --> 00:07:44.469 align:start position:0% via remote provider like line syncing in 00:07:44.469 --> 00:07:47.339 align:start position:0% via remote provider like line syncing in the<00:07:44.560> background<00:07:44.949> and<00:07:45.430> well<00:07:46.389> when<00:07:46.719> it<00:07:46.839> up<00:07:47.080> today 00:07:47.339 --> 00:07:47.349 align:start position:0% the background and well when it up today 00:07:47.349 --> 00:07:50.610 align:start position:0% the background and well when it up today it<00:07:47.560> just<00:07:48.159> takes<00:07:48.399> over<00:07:48.639> the<00:07:48.729> connection<00:07:49.620> we 00:07:50.610 --> 00:07:50.620 align:start position:0% it just takes over the connection we 00:07:50.620 --> 00:07:52.760 align:start position:0% it just takes over the connection we implemented<00:07:51.189> a<00:07:51.279> transaction<00:07:51.849> history<00:07:52.089> window 00:07:52.760 --> 00:07:52.770 align:start position:0% implemented a transaction history window 00:07:52.770 --> 00:07:56.029 align:start position:0% implemented a transaction history window which<00:07:53.770> will<00:07:53.949> gather<00:07:54.159> all<00:07:54.659> transactions<00:07:55.659> made 00:07:56.029 --> 00:07:56.039 align:start position:0% which will gather all transactions made 00:07:56.039 --> 00:07:59.040 align:start position:0% which will gather all transactions made in<00:07:57.039> the<00:07:57.189> browser<00:07:57.539> which<00:07:58.539> is<00:07:58.569> pretty 00:07:59.040 --> 00:07:59.050 align:start position:0% in the browser which is pretty 00:07:59.050 --> 00:08:00.600 align:start position:0% in the browser which is pretty convenient<00:07:59.409> for<00:07:59.800> the<00:08:00.009> app<00:08:00.069> developers 00:08:00.600 --> 00:08:00.610 align:start position:0% convenient for the app developers 00:08:00.610 --> 00:08:02.070 align:start position:0% convenient for the app developers because<00:08:00.759> they<00:08:01.149> wouldn't<00:08:01.449> have<00:08:01.719> to<00:08:01.870> implement 00:08:02.070 --> 00:08:02.080 align:start position:0% because they wouldn't have to implement 00:08:02.080 --> 00:08:04.129 align:start position:0% because they wouldn't have to implement that<00:08:02.319> themselves<00:08:03.159> within<00:08:03.520> the<00:08:03.669> their 00:08:04.129 --> 00:08:04.139 align:start position:0% that themselves within the their 00:08:04.139 --> 00:08:09.899 align:start position:0% that themselves within the their websites<00:08:07.589> using<00:08:08.589> our<00:08:08.770> web<00:08:08.979> 31.0<00:08:09.729> with 00:08:09.899 --> 00:08:09.909 align:start position:0% websites using our web 31.0 with 00:08:09.909 --> 00:08:10.709 align:start position:0% websites using our web 31.0 with WebSockets 00:08:10.709 --> 00:08:10.719 align:start position:0% WebSockets 00:08:10.719 --> 00:08:13.800 align:start position:0% WebSockets implemented<00:08:11.939> and<00:08:12.939> there<00:08:13.180> are<00:08:13.270> some<00:08:13.449> breaking 00:08:13.800 --> 00:08:13.810 align:start position:0% implemented and there are some breaking 00:08:13.810 --> 00:08:16.529 align:start position:0% implemented and there are some breaking changes<00:08:14.139> to<00:08:14.319> to<00:08:14.680> how<00:08:14.830> we<00:08:15.550> connect<00:08:15.939> with<00:08:16.389> the 00:08:16.529 --> 00:08:16.539 align:start position:0% changes to to how we connect with the 00:08:16.539 --> 00:08:19.320 align:start position:0% changes to to how we connect with the web<00:08:16.689> sites<00:08:16.960> actually<00:08:17.560> this<00:08:17.680> is<00:08:18.330> coordinated 00:08:19.320 --> 00:08:19.330 align:start position:0% web sites actually this is coordinated 00:08:19.330 --> 00:08:23.159 align:start position:0% web sites actually this is coordinated effort<00:08:19.659> so<00:08:20.349> misuse<00:08:20.889> it<00:08:21.039> to<00:08:21.219> inject<00:08:21.580> web<00:08:21.789> 3j<00:08:22.269> as 00:08:23.159 --> 00:08:23.169 align:start position:0% effort so misuse it to inject web 3j as 00:08:23.169 --> 00:08:26.969 align:start position:0% effort so misuse it to inject web 3j as within<00:08:24.069> the<00:08:24.789> Dom<00:08:25.319> so<00:08:26.319> we<00:08:26.560> don't<00:08:26.770> do<00:08:26.860> that 00:08:26.969 --> 00:08:26.979 align:start position:0% within the Dom so we don't do that 00:08:26.979 --> 00:08:29.070 align:start position:0% within the Dom so we don't do that anymore<00:08:27.249> that<00:08:27.550> subsidy<00:08:28.090> that<00:08:28.270> developers<00:08:28.840> to 00:08:29.070 --> 00:08:29.080 align:start position:0% anymore that subsidy that developers to 00:08:29.080 --> 00:08:33.449 align:start position:0% anymore that subsidy that developers to to<00:08:29.889> choose<00:08:30.129> which<00:08:30.400> versions<00:08:30.849> they<00:08:31.090> reuse<00:08:32.459> and 00:08:33.449 --> 00:08:33.459 align:start position:0% to choose which versions they reuse and 00:08:33.459 --> 00:08:36.240 align:start position:0% to choose which versions they reuse and then<00:08:34.209> we<00:08:34.839> would<00:08:34.990> only<00:08:35.169> provide<00:08:35.560> the<00:08:35.829> web<00:08:36.010> 3 00:08:36.240 --> 00:08:36.250 align:start position:0% then we would only provide the web 3 00:08:36.250 --> 00:08:39.089 align:start position:0% then we would only provide the web 3 that<00:08:36.430> current<00:08:36.700> provider<00:08:37.769> this<00:08:38.769> is<00:08:38.950> now 00:08:39.089 --> 00:08:39.099 align:start position:0% that current provider this is now 00:08:39.099 --> 00:08:42.689 align:start position:0% that current provider this is now changing<00:08:39.130> to<00:08:39.909> window<00:08:40.389> dot<00:08:40.599> ëthere<00:08:41.110> only<00:08:41.699> for 00:08:42.689 --> 00:08:42.699 align:start position:0% changing to window dot ëthere only for 00:08:42.699 --> 00:08:48.629 align:start position:0% changing to window dot ëthere only for simplicity<00:08:43.209> sake<00:08:45.060> so<00:08:46.060> here<00:08:46.420> we<00:08:46.540> can<00:08:46.660> have<00:08:47.639> the 00:08:48.629 --> 00:08:48.639 align:start position:0% simplicity sake so here we can have the 00:08:48.639 --> 00:08:50.850 align:start position:0% simplicity sake so here we can have the method<00:08:49.029> that<00:08:49.420> will<00:08:49.690> request<00:08:50.019> accounts<00:08:50.589> and 00:08:50.850 --> 00:08:50.860 align:start position:0% method that will request accounts and 00:08:50.860 --> 00:08:54.650 align:start position:0% method that will request accounts and then<00:08:51.579> in<00:08:51.699> mist<00:08:52.500> this<00:08:53.500> window<00:08:53.949> will<00:08:54.100> pop<00:08:54.310> up 00:08:54.650 --> 00:08:54.660 align:start position:0% then in mist this window will pop up 00:08:54.660 --> 00:08:59.610 align:start position:0% then in mist this window will pop up which<00:08:55.660> we<00:08:55.810> can<00:08:56.110> you<00:08:56.260> can<00:08:56.290> you<00:08:56.829> know<00:08:56.980> have<00:08:58.620> or 00:08:59.610 --> 00:08:59.620 align:start position:0% which we can you can you know have or 00:08:59.620 --> 00:09:02.579 align:start position:0% which we can you can you know have or create<00:08:59.980> a<00:09:00.130> new<00:09:00.220> account<00:09:00.339> or<00:09:01.050> select<00:09:02.050> one<00:09:02.199> or 00:09:02.579 --> 00:09:02.589 align:start position:0% create a new account or select one or 00:09:02.589 --> 00:09:04.740 align:start position:0% create a new account or select one or multiple<00:09:03.010> accounts<00:09:03.670> you<00:09:03.730> want<00:09:03.850> to<00:09:04.000> provide<00:09:04.269> 2d 00:09:04.740 --> 00:09:04.750 align:start position:0% multiple accounts you want to provide 2d 00:09:04.750 --> 00:09:13.710 align:start position:0% multiple accounts you want to provide 2d to<00:09:05.709> the<00:09:05.829> website<00:09:10.380> right<00:09:11.910> yeah<00:09:12.910> so<00:09:13.120> in<00:09:13.449> order<00:09:13.570> to 00:09:13.710 --> 00:09:13.720 align:start position:0% to the website right yeah so in order to 00:09:13.720 --> 00:09:15.569 align:start position:0% to the website right yeah so in order to implement<00:09:14.050> the<00:09:14.350> change<00:09:14.649> will<00:09:14.800> be<00:09:14.949> simple<00:09:15.430> we 00:09:15.569 --> 00:09:15.579 align:start position:0% implement the change will be simple we 00:09:15.579 --> 00:09:18.629 align:start position:0% implement the change will be simple we have<00:09:15.790> to<00:09:16.000> instance<00:09:16.540> to<00:09:17.290> make<00:09:17.320> by<00:09:17.889> three<00:09:18.130> with 00:09:18.629 --> 00:09:18.639 align:start position:0% have to instance to make by three with 00:09:18.639 --> 00:09:21.269 align:start position:0% have to instance to make by three with this<00:09:18.820> kind<00:09:19.209> of<00:09:19.240> connection<00:09:19.920> pretty<00:09:20.920> simple 00:09:21.269 --> 00:09:21.279 align:start position:0% this kind of connection pretty simple 00:09:21.279 --> 00:09:24.840 align:start position:0% this kind of connection pretty simple change<00:09:21.779> and<00:09:22.779> this<00:09:23.500> is<00:09:23.699> convenient<00:09:24.699> way<00:09:24.820> to 00:09:24.840 --> 00:09:24.850 align:start position:0% change and this is convenient way to 00:09:24.850 --> 00:09:27.329 align:start position:0% change and this is convenient way to access<00:09:25.060> blockchain<00:09:25.930> resources<00:09:26.560> this<00:09:27.279> is 00:09:27.329 --> 00:09:27.339 align:start position:0% access blockchain resources this is 00:09:27.339 --> 00:09:31.350 align:start position:0% access blockchain resources this is actually<00:09:27.820> a<00:09:28.920> collaboration<00:09:29.920> effort<00:09:30.430> madam 00:09:31.350 --> 00:09:31.360 align:start position:0% actually a collaboration effort madam 00:09:31.360 --> 00:09:32.970 align:start position:0% actually a collaboration effort madam asked<00:09:31.510> and<00:09:31.750> lots<00:09:31.899> of<00:09:31.990> other<00:09:32.170> players<00:09:32.500> are<00:09:32.800> on 00:09:32.970 --> 00:09:32.980 align:start position:0% asked and lots of other players are on 00:09:32.980 --> 00:09:37.290 align:start position:0% asked and lots of other players are on this<00:09:33.220> same<00:09:34.209> boat<00:09:34.949> you<00:09:35.949> guys<00:09:36.339> can<00:09:36.730> point<00:09:37.180> your 00:09:37.290 --> 00:09:37.300 align:start position:0% this same boat you guys can point your 00:09:37.300 --> 00:09:40.470 align:start position:0% this same boat you guys can point your devices<00:09:37.810> to<00:09:37.959> this<00:09:38.079> QR<00:09:38.380> code<00:09:38.410> to<00:09:38.980> see<00:09:39.190> more<00:09:40.149> you 00:09:40.470 --> 00:09:40.480 align:start position:0% devices to this QR code to see more you 00:09:40.480 --> 00:09:44.189 align:start position:0% devices to this QR code to see more you know<00:09:40.870> in-depth<00:09:42.300> documentation<00:09:43.300> we<00:09:43.990> are<00:09:44.079> about 00:09:44.189 --> 00:09:44.199 align:start position:0% know in-depth documentation we are about 00:09:44.199 --> 00:09:47.160 align:start position:0% know in-depth documentation we are about to<00:09:44.380> roll<00:09:44.589> out<00:09:44.769> in<00:09:45.220> the<00:09:45.579> next<00:09:45.880> week's<00:09:46.089> and<00:09:46.600> while 00:09:47.160 --> 00:09:47.170 align:start position:0% to roll out in the next week's and while 00:09:47.170 --> 00:09:50.130 align:start position:0% to roll out in the next week's and while of<00:09:47.320> course<00:09:47.350> there's<00:09:47.800> a<00:09:47.860> PR<00:09:48.190> for<00:09:48.339> that<00:09:49.079> we<00:09:50.079> are 00:09:50.130 --> 00:09:50.140 align:start position:0% of course there's a PR for that we are 00:09:50.140 --> 00:09:51.630 align:start position:0% of course there's a PR for that we are also<00:09:50.260> making<00:09:50.529> some<00:09:50.680> deep<00:09:51.070> architecture 00:09:51.630 --> 00:09:51.640 align:start position:0% also making some deep architecture 00:09:51.640 --> 00:09:57.990 align:start position:0% also making some deep architecture changes<00:09:53.910> this<00:09:54.910> is<00:09:55.120> how<00:09:55.300> miss<00:09:56.260> looks<00:09:56.730> at<00:09:57.730> the 00:09:57.990 --> 00:09:58.000 align:start position:0% changes this is how miss looks at the 00:09:58.000 --> 00:10:01.519 align:start position:0% changes this is how miss looks at the moment<00:09:58.360> okay<00:09:58.990> we've<00:09:59.620> got<00:09:59.860> a<00:09:59.890> browser<00:10:00.310> shell 00:10:01.519 --> 00:10:01.529 align:start position:0% moment okay we've got a browser shell 00:10:01.529 --> 00:10:05.280 align:start position:0% moment okay we've got a browser shell which<00:10:02.529> we<00:10:02.680> use<00:10:02.829> electron<00:10:03.399> we've<00:10:03.970> got<00:10:04.149> the<00:10:05.140> back 00:10:05.280 --> 00:10:05.290 align:start position:0% which we use electron we've got the back 00:10:05.290 --> 00:10:06.480 align:start position:0% which we use electron we've got the back end<00:10:05.500> mating<00:10:05.860> nodejs 00:10:06.480 --> 00:10:06.490 align:start position:0% end mating nodejs 00:10:06.490 --> 00:10:10.439 align:start position:0% end mating nodejs and<00:10:06.760> the<00:10:06.850> front<00:10:07.089> end<00:10:07.860> meteor<00:10:09.029> those<00:10:10.029> are<00:10:10.240> all 00:10:10.439 --> 00:10:10.449 align:start position:0% and the front end meteor those are all 00:10:10.449 --> 00:10:12.870 align:start position:0% and the front end meteor those are all tightly<00:10:11.290> coupled<00:10:11.500> that<00:10:12.430> makes<00:10:12.640> quite 00:10:12.870 --> 00:10:12.880 align:start position:0% tightly coupled that makes quite 00:10:12.880 --> 00:10:15.660 align:start position:0% tightly coupled that makes quite difficult<00:10:13.209> for<00:10:13.449> us<00:10:13.660> to<00:10:13.800> to<00:10:14.800> experiment<00:10:15.370> new 00:10:15.660 --> 00:10:15.670 align:start position:0% difficult for us to to experiment new 00:10:15.670 --> 00:10:19.829 align:start position:0% difficult for us to to experiment new technologies<00:10:16.300> to<00:10:16.620> you<00:10:17.620> know<00:10:18.510> especially<00:10:19.510> when 00:10:19.829 --> 00:10:19.839 align:start position:0% technologies to you know especially when 00:10:19.839 --> 00:10:21.059 align:start position:0% technologies to you know especially when there<00:10:19.990> are<00:10:20.019> you<00:10:20.199> know<00:10:20.230> some<00:10:20.500> security 00:10:21.059 --> 00:10:21.069 align:start position:0% there are you know some security 00:10:21.069 --> 00:10:24.540 align:start position:0% there are you know some security concerns<00:10:21.220> which<00:10:22.350> in<00:10:23.350> our<00:10:23.560> industry<00:10:23.980> is<00:10:24.100> fairly 00:10:24.540 --> 00:10:24.550 align:start position:0% concerns which in our industry is fairly 00:10:24.550 --> 00:10:28.900 align:start position:0% concerns which in our industry is fairly common<00:10:25.620> so<00:10:26.620> we're<00:10:26.860> changing<00:10:27.190> too 00:10:28.900 --> 00:10:28.910 align:start position:0% common so we're changing too 00:10:28.910 --> 00:10:33.250 align:start position:0% common so we're changing too this<00:10:29.360> kind<00:10:29.780> of<00:10:29.840> model<00:10:29.960> so<00:10:30.800> we<00:10:30.920> have<00:10:32.260> totally 00:10:33.250 --> 00:10:33.260 align:start position:0% this kind of model so we have totally 00:10:33.260 --> 00:10:37.830 align:start position:0% this kind of model so we have totally isolated<00:10:33.980> a<00:10:34.840> really<00:10:35.840> thin<00:10:36.170> browser<00:10:37.130> shell 00:10:37.830 --> 00:10:37.840 align:start position:0% isolated a really thin browser shell 00:10:37.840 --> 00:10:41.350 align:start position:0% isolated a really thin browser shell still<00:10:38.840> using<00:10:39.170> electron<00:10:39.590> at<00:10:40.130> this<00:10:40.310> moment<00:10:40.460> but 00:10:41.350 --> 00:10:41.360 align:start position:0% still using electron at this moment but 00:10:41.360 --> 00:10:43.570 align:start position:0% still using electron at this moment but the<00:10:41.480> main<00:10:41.660> process<00:10:42.140> will<00:10:42.710> be<00:10:42.800> separated<00:10:43.280> and 00:10:43.570 --> 00:10:43.580 align:start position:0% the main process will be separated and 00:10:43.580 --> 00:10:46.990 align:start position:0% the main process will be separated and the<00:10:44.150> front<00:10:44.390> end<00:10:44.630> will<00:10:44.810> being<00:10:45.020> react<00:10:45.410> and<00:10:46.000> that 00:10:46.990 --> 00:10:47.000 align:start position:0% the front end will being react and that 00:10:47.000 --> 00:10:50.740 align:start position:0% the front end will being react and that will<00:10:47.720> allow<00:10:47.990> us<00:10:48.200> to<00:10:48.230> make<00:10:48.530> such<00:10:48.980> changes<00:10:49.750> we 00:10:50.740 --> 00:10:50.750 align:start position:0% will allow us to make such changes we 00:10:50.750 --> 00:10:54.090 align:start position:0% will allow us to make such changes we can<00:10:50.870> have<00:10:51.050> lots<00:10:51.290> of<00:10:51.440> updates<00:10:52.600> frequent<00:10:53.600> ones 00:10:54.090 --> 00:10:54.100 align:start position:0% can have lots of updates frequent ones 00:10:54.100 --> 00:10:57.340 align:start position:0% can have lots of updates frequent ones dislike<00:10:55.100> continues<00:10:55.730> delivery<00:10:56.140> mechanisms<00:10:57.140> in 00:10:57.340 --> 00:10:57.350 align:start position:0% dislike continues delivery mechanisms in 00:10:57.350 --> 00:11:00.130 align:start position:0% dislike continues delivery mechanisms in the<00:10:57.770> web<00:10:57.920> development<00:10:58.510> so<00:10:59.510> you<00:10:59.540> can<00:10:59.780> have<00:10:59.930> you 00:11:00.130 --> 00:11:00.140 align:start position:0% the web development so you can have you 00:11:00.140 --> 00:11:02.470 align:start position:0% the web development so you can have you know<00:11:00.170> lots<00:11:00.950> of<00:11:01.100> updates<00:11:01.520> the<00:11:01.730> user<00:11:01.910> world<00:11:02.180> you 00:11:02.470 --> 00:11:02.480 align:start position:0% know lots of updates the user world you 00:11:02.480 --> 00:11:04.150 align:start position:0% know lots of updates the user world you can<00:11:02.660> subscribe<00:11:02.990> to<00:11:03.230> those<00:11:03.500> kind<00:11:03.770> of<00:11:03.830> updates 00:11:04.150 --> 00:11:04.160 align:start position:0% can subscribe to those kind of updates 00:11:04.160 --> 00:11:07.090 align:start position:0% can subscribe to those kind of updates and<00:11:04.550> of<00:11:04.820> course<00:11:05.120> with<00:11:06.110> the<00:11:06.200> user<00:11:06.350> constant<00:11:06.890> we 00:11:07.090 --> 00:11:07.100 align:start position:0% and of course with the user constant we 00:11:07.100 --> 00:11:09.850 align:start position:0% and of course with the user constant we will<00:11:07.390> it<00:11:08.390> will<00:11:08.540> be<00:11:08.660> as<00:11:08.900> simple<00:11:09.170> as<00:11:09.440> a<00:11:09.500> browser 00:11:09.850 --> 00:11:09.860 align:start position:0% will it will be as simple as a browser 00:11:09.860 --> 00:11:13.420 align:start position:0% will it will be as simple as a browser reload<00:11:10.520> but<00:11:11.090> you're<00:11:11.240> using<00:11:11.870> an<00:11:12.140> a<00:11:12.430> desktop 00:11:13.420 --> 00:11:13.430 align:start position:0% reload but you're using an a desktop 00:11:13.430 --> 00:11:17.740 align:start position:0% reload but you're using an a desktop application<00:11:15.340> then<00:11:16.340> we<00:11:16.370> can<00:11:16.730> update<00:11:16.970> all<00:11:17.690> the 00:11:17.740 --> 00:11:17.750 align:start position:0% application then we can update all the 00:11:17.750 --> 00:11:20.770 align:start position:0% application then we can update all the main<00:11:18.140> process<00:11:18.650> and<00:11:19.460> eventually<00:11:20.090> when<00:11:20.390> we've 00:11:20.770 --> 00:11:20.780 align:start position:0% main process and eventually when we've 00:11:20.780 --> 00:11:24.790 align:start position:0% main process and eventually when we've got<00:11:20.990> new<00:11:21.290> browser<00:11:22.250> shell<00:11:22.720> versions<00:11:23.800> you'll 00:11:24.790 --> 00:11:24.800 align:start position:0% got new browser shell versions you'll 00:11:24.800 --> 00:11:29.860 align:start position:0% got new browser shell versions you'll update<00:11:24.950> only<00:11:25.310> that<00:11:25.640> again<00:11:28.030> but<00:11:29.030> hey<00:11:29.360> why<00:11:29.810> are 00:11:29.860 --> 00:11:29.870 align:start position:0% update only that again but hey why are 00:11:29.870 --> 00:11:31.450 align:start position:0% update only that again but hey why are you<00:11:30.020> still<00:11:30.350> using<00:11:30.410> electron<00:11:31.160> if<00:11:31.280> you're 00:11:31.450 --> 00:11:31.460 align:start position:0% you still using electron if you're 00:11:31.460 --> 00:11:34.510 align:start position:0% you still using electron if you're building<00:11:31.670> a<00:11:31.850> browser<00:11:32.170> that<00:11:33.170> is<00:11:33.830> so<00:11:33.980> true<00:11:34.220> we 00:11:34.510 --> 00:11:34.520 align:start position:0% building a browser that is so true we 00:11:34.520 --> 00:11:38.370 align:start position:0% building a browser that is so true we agree<00:11:34.760> with<00:11:34.850> that<00:11:35.350> and<00:11:36.350> this<00:11:36.770> is<00:11:37.010> a<00:11:37.040> tweet<00:11:38.030> from 00:11:38.370 --> 00:11:38.380 align:start position:0% agree with that and this is a tweet from 00:11:38.380 --> 00:11:41.410 align:start position:0% agree with that and this is a tweet from young<00:11:39.380> from<00:11:39.770> brave<00:11:40.070> browser<00:11:40.370> they<00:11:41.000> just<00:11:41.240> got 00:11:41.410 --> 00:11:41.420 align:start position:0% young from brave browser they just got 00:11:41.420 --> 00:11:45.040 align:start position:0% young from brave browser they just got rid<00:11:41.630> of<00:11:41.690> electrum<00:11:42.260> altogether<00:11:43.210> and<00:11:44.210> we're 00:11:45.040 --> 00:11:45.050 align:start position:0% rid of electrum altogether and we're 00:11:45.050 --> 00:11:50.110 align:start position:0% rid of electrum altogether and we're playing<00:11:45.350> to<00:11:45.530> do<00:11:45.680> so<00:11:45.950> as<00:11:46.220> well<00:11:46.280> but<00:11:48.400> we<00:11:49.400> came<00:11:49.580> you 00:11:50.110 --> 00:11:50.120 align:start position:0% playing to do so as well but we came you 00:11:50.120 --> 00:11:52.660 align:start position:0% playing to do so as well but we came you know<00:11:50.240> with<00:11:50.390> a<00:11:50.420> different<00:11:50.840> solution<00:11:51.670> we're 00:11:52.660 --> 00:11:52.670 align:start position:0% know with a different solution we're 00:11:52.670 --> 00:11:55.150 align:start position:0% know with a different solution we're using<00:11:53.210> chromium<00:11:53.810> embedded<00:11:54.230> framework<00:11:54.680> in<00:11:55.010> a 00:11:55.150 --> 00:11:55.160 align:start position:0% using chromium embedded framework in a 00:11:55.160 --> 00:11:58.330 align:start position:0% using chromium embedded framework in a project<00:11:55.370> called<00:11:55.580> Tao<00:11:56.860> which<00:11:57.860> I<00:11:58.010> highly 00:11:58.330 --> 00:11:58.340 align:start position:0% project called Tao which I highly 00:11:58.340 --> 00:12:00.760 align:start position:0% project called Tao which I highly recommend<00:11:58.520> you<00:11:59.030> guys<00:11:59.180> to<00:11:59.240> watch<00:11:59.600> Phillip<00:12:00.500> talk 00:12:00.760 --> 00:12:00.770 align:start position:0% recommend you guys to watch Phillip talk 00:12:00.770 --> 00:12:08.640 align:start position:0% recommend you guys to watch Phillip talk would<00:12:01.580> be<00:12:01.700> on<00:12:02.030> day<00:12:03.580> which<00:12:04.580> day<00:12:04.790> and<00:12:05.300> time<00:12:05.510> you 00:12:08.640 --> 00:12:08.650 align:start position:0% 00:12:08.650 --> 00:12:13.840 align:start position:0% guys<00:12:09.650> hear<00:12:09.950> that<00:12:09.980> tomorrow<00:12:10.520> at<00:12:10.640> 2:00<00:12:10.850> I<00:12:12.850> think 00:12:13.840 --> 00:12:13.850 align:start position:0% guys hear that tomorrow at 2:00 I think 00:12:13.850 --> 00:12:15.510 align:start position:0% guys hear that tomorrow at 2:00 I think we'd<00:12:13.940> be<00:12:14.030> here<00:12:14.240> in<00:12:14.360> that<00:12:14.510> same<00:12:14.690> room<00:12:14.840> right 00:12:15.510 --> 00:12:15.520 align:start position:0% we'd be here in that same room right 00:12:15.520 --> 00:12:21.370 align:start position:0% we'd be here in that same room right okay<00:12:18.940> so<00:12:19.940> regarding<00:12:20.660> these<00:12:20.780> deep 00:12:21.370 --> 00:12:21.380 align:start position:0% okay so regarding these deep 00:12:21.380 --> 00:12:24.940 align:start position:0% okay so regarding these deep architecture<00:12:21.980> changes<00:12:22.010> I<00:12:22.580> think<00:12:23.530> in<00:12:24.530> practice 00:12:24.940 --> 00:12:24.950 align:start position:0% architecture changes I think in practice 00:12:24.950 --> 00:12:28.540 align:start position:0% architecture changes I think in practice what<00:12:25.610> can<00:12:25.970> bring<00:12:26.360> us<00:12:26.510> to<00:12:27.070> instead<00:12:28.070> of<00:12:28.130> a<00:12:28.280> eight 00:12:28.540 --> 00:12:28.550 align:start position:0% what can bring us to instead of a eight 00:12:28.550 --> 00:12:31.270 align:start position:0% what can bring us to instead of a eight a<00:12:28.610> megabyte<00:12:29.180> update<00:12:29.600> at<00:12:29.840> least<00:12:30.080> you'd<00:12:31.010> be<00:12:31.040> like 00:12:31.270 --> 00:12:31.280 align:start position:0% a megabyte update at least you'd be like 00:12:31.280 --> 00:12:33.220 align:start position:0% a megabyte update at least you'd be like you<00:12:31.430> know<00:12:31.550> less<00:12:32.000> than<00:12:32.030> five<00:12:32.420> megabyte<00:12:32.810> updates 00:12:33.220 --> 00:12:33.230 align:start position:0% you know less than five megabyte updates 00:12:33.230 --> 00:12:33.880 align:start position:0% you know less than five megabyte updates for<00:12:33.470> the<00:12:33.590> UI 00:12:33.880 --> 00:12:33.890 align:start position:0% for the UI 00:12:33.890 --> 00:12:39.430 align:start position:0% for the UI no<00:12:34.700> that's<00:12:34.910> less<00:12:35.480> than<00:12:35.510> a<00:12:35.840> wide<00:12:36.830> image<00:12:38.080> and<00:12:39.080> you 00:12:39.430 --> 00:12:39.440 align:start position:0% no that's less than a wide image and you 00:12:39.440 --> 00:12:41.170 align:start position:0% no that's less than a wide image and you can<00:12:39.620> do<00:12:39.710> that<00:12:39.830> you<00:12:40.100> know<00:12:40.130> frequently<00:12:40.790> we<00:12:41.030> can 00:12:41.170 --> 00:12:41.180 align:start position:0% can do that you know frequently we can 00:12:41.180 --> 00:12:42.550 align:start position:0% can do that you know frequently we can put<00:12:41.750> our 00:12:42.550 --> 00:12:42.560 align:start position:0% put our 00:12:42.560 --> 00:12:44.769 align:start position:0% put our continuous<00:12:42.920> delivery<00:12:43.040> server<00:12:43.490> to<00:12:43.760> work<00:12:44.330> for 00:12:44.769 --> 00:12:44.779 align:start position:0% continuous delivery server to work for 00:12:44.779 --> 00:12:49.870 align:start position:0% continuous delivery server to work for you<00:12:46.960> so<00:12:47.960> increase<00:12:48.380> it<00:12:48.500> cross<00:12:48.980> OS<00:12:49.340> testing 00:12:49.870 --> 00:12:49.880 align:start position:0% you so increase it cross OS testing 00:12:49.880 --> 00:12:52.390 align:start position:0% you so increase it cross OS testing effort<00:12:50.270> today<00:12:51.140> is<00:12:51.470> actually<00:12:51.890> a<00:12:51.920> pain<00:12:52.160> for<00:12:52.370> us 00:12:52.390 --> 00:12:52.400 align:start position:0% effort today is actually a pain for us 00:12:52.400 --> 00:12:55.269 align:start position:0% effort today is actually a pain for us so<00:12:53.150> we<00:12:53.450> can<00:12:53.660> get<00:12:53.870> rid<00:12:53.990> of<00:12:54.020> this<00:12:54.320> altogether 00:12:55.269 --> 00:12:55.279 align:start position:0% so we can get rid of this altogether 00:12:55.279 --> 00:12:57.910 align:start position:0% so we can get rid of this altogether making<00:12:55.580> those<00:12:56.110> frequent<00:12:57.110> releases<00:12:57.529> for<00:12:57.860> the 00:12:57.910 --> 00:12:57.920 align:start position:0% making those frequent releases for the 00:12:57.920 --> 00:13:03.400 align:start position:0% making those frequent releases for the interface<00:12:59.740> and<00:13:00.940> today<00:13:01.940> we<00:13:02.270> put<00:13:02.510> this<00:13:02.960> creative 00:13:03.400 --> 00:13:03.410 align:start position:0% interface and today we put this creative 00:13:03.410 --> 00:13:07.570 align:start position:0% interface and today we put this creative burden<00:13:03.800> of<00:13:03.920> validating<00:13:04.820> the<00:13:05.390> checksums<00:13:06.580> to 00:13:07.570 --> 00:13:07.580 align:start position:0% burden of validating the checksums to 00:13:07.580 --> 00:13:09.579 align:start position:0% burden of validating the checksums to the<00:13:07.700> users<00:13:08.000> I<00:13:08.210> think<00:13:08.390> that<00:13:08.779> is<00:13:09.020> not<00:13:09.200> really 00:13:09.579 --> 00:13:09.589 align:start position:0% the users I think that is not really 00:13:09.589 --> 00:13:11.769 align:start position:0% the users I think that is not really fair<00:13:09.830> because<00:13:10.130> you<00:13:10.700> know<00:13:11.150> sometimes<00:13:11.510> it 00:13:11.769 --> 00:13:11.779 align:start position:0% fair because you know sometimes it 00:13:11.779 --> 00:13:13.450 align:start position:0% fair because you know sometimes it requires<00:13:11.870> some<00:13:12.290> tooling<00:13:12.680> additional<00:13:13.100> tooling 00:13:13.450 --> 00:13:13.460 align:start position:0% requires some tooling additional tooling 00:13:13.460 --> 00:13:17.230 align:start position:0% requires some tooling additional tooling you<00:13:13.760> know<00:13:14.770> command<00:13:15.770> line<00:13:15.950> instructions<00:13:16.580> and 00:13:17.230 --> 00:13:17.240 align:start position:0% you know command line instructions and 00:13:17.240 --> 00:13:19.120 align:start position:0% you know command line instructions and we<00:13:17.390> can<00:13:17.570> make<00:13:17.960> it<00:13:18.110> better<00:13:18.290> with<00:13:18.620> automatic 00:13:19.120 --> 00:13:19.130 align:start position:0% we can make it better with automatic 00:13:19.130 --> 00:13:24.280 align:start position:0% we can make it better with automatic checksum<00:13:19.730> validation<00:13:20.690> module<00:13:21.170> level<00:13:21.320> a<00:13:23.290> bit 00:13:24.280 --> 00:13:24.290 align:start position:0% checksum validation module level a bit 00:13:24.290 --> 00:13:26.620 align:start position:0% checksum validation module level a bit more<00:13:24.440> about<00:13:24.650> transparency<00:13:25.520> we<00:13:26.240> got<00:13:26.420> some 00:13:26.620 --> 00:13:26.630 align:start position:0% more about transparency we got some 00:13:26.630 --> 00:13:28.960 align:start position:0% more about transparency we got some feedback<00:13:26.810> saying<00:13:27.380> that<00:13:27.770> well<00:13:28.400> a<00:13:28.430> road<00:13:28.790> map 00:13:28.960 --> 00:13:28.970 align:start position:0% feedback saying that well a road map 00:13:28.970 --> 00:13:32.200 align:start position:0% feedback saying that well a road map wasn't<00:13:29.300> quite<00:13:30.170> public<00:13:30.730> people<00:13:31.730> sometimes 00:13:32.200 --> 00:13:32.210 align:start position:0% wasn't quite public people sometimes 00:13:32.210 --> 00:13:34.600 align:start position:0% wasn't quite public people sometimes would<00:13:32.450> know<00:13:32.690> exactly<00:13:33.050> what<00:13:33.410> we<00:13:33.650> were<00:13:34.100> working 00:13:34.600 --> 00:13:34.610 align:start position:0% would know exactly what we were working 00:13:34.610 --> 00:13:37.329 align:start position:0% would know exactly what we were working on<00:13:34.880> so<00:13:35.320> yeah<00:13:36.320> we<00:13:36.560> now<00:13:36.680> have<00:13:36.920> medium 00:13:37.329 --> 00:13:37.339 align:start position:0% on so yeah we now have medium 00:13:37.339 --> 00:13:40.000 align:start position:0% on so yeah we now have medium publications<00:13:37.940> we've<00:13:38.270> got<00:13:38.450> this<00:13:39.110> one<00:13:39.440> public 00:13:40.000 --> 00:13:40.010 align:start position:0% publications we've got this one public 00:13:40.010 --> 00:13:42.460 align:start position:0% publications we've got this one public polls<00:13:40.220> there<00:13:40.490> we've<00:13:41.029> got<00:13:41.060> three<00:13:41.480> more<00:13:41.690> you 00:13:42.460 --> 00:13:42.470 align:start position:0% polls there we've got three more you 00:13:42.470 --> 00:13:44.890 align:start position:0% polls there we've got three more you know<00:13:42.560> just<00:13:42.860> about<00:13:42.980> to<00:13:43.220> be<00:13:43.370> published<00:13:43.820> so<00:13:44.029> if 00:13:44.890 --> 00:13:44.900 align:start position:0% know just about to be published so if 00:13:44.900 --> 00:13:46.540 align:start position:0% know just about to be published so if you<00:13:45.020> guys<00:13:45.140> can<00:13:45.380> follow<00:13:45.560> that<00:13:45.800> as<00:13:46.040> there<00:13:46.310> you 00:13:46.540 --> 00:13:46.550 align:start position:0% you guys can follow that as there you 00:13:46.550 --> 00:13:53.710 align:start position:0% you guys can follow that as there you see<00:13:49.390> our<00:13:50.390> road<00:13:50.600> map<00:13:50.810> would<00:13:51.050> moved<00:13:51.380> from<00:13:52.720> close 00:13:53.710 --> 00:13:53.720 align:start position:0% see our road map would moved from close 00:13:53.720 --> 00:13:57.300 align:start position:0% see our road map would moved from close an<00:13:53.930> application<00:13:54.110> to<00:13:54.740> github<00:13:55.420> projects<00:13:56.420> and 00:13:57.300 --> 00:13:57.310 align:start position:0% an application to github projects and 00:13:57.310 --> 00:14:00.250 align:start position:0% an application to github projects and well<00:13:58.310> today<00:13:58.850> I<00:13:58.880> created<00:13:59.240> if<00:13:59.600> you're<00:13:59.870> miss<00:14:00.050> from 00:14:00.250 --> 00:14:00.260 align:start position:0% well today I created if you're miss from 00:14:00.260 --> 00:14:04.510 align:start position:0% well today I created if you're miss from Twitter<00:14:00.470> so<00:14:00.560> you<00:14:01.190> know<00:14:03.040> it<00:14:04.040> has<00:14:04.160> zero 00:14:04.510 --> 00:14:04.520 align:start position:0% Twitter so you know it has zero 00:14:04.520 --> 00:14:07.710 align:start position:0% Twitter so you know it has zero followers<00:14:04.940> but<00:14:05.150> you<00:14:05.270> can<00:14:05.890> can<00:14:06.890> be<00:14:06.920> the<00:14:07.100> first 00:14:07.710 --> 00:14:07.720 align:start position:0% followers but you can can be the first 00:14:07.720 --> 00:14:13.120 align:start position:0% followers but you can can be the first no<00:14:08.720> formal<00:14:09.080> guys<00:14:10.240> so<00:14:11.240> how<00:14:11.750> to<00:14:11.810> contribute<00:14:12.410> to 00:14:13.120 --> 00:14:13.130 align:start position:0% no formal guys so how to contribute to 00:14:13.130 --> 00:14:15.220 align:start position:0% no formal guys so how to contribute to this<00:14:13.460> project<00:14:13.820> and<00:14:14.300> to<00:14:14.330> this<00:14:14.660> web<00:14:15.020> a 00:14:15.220 --> 00:14:15.230 align:start position:0% this project and to this web a 00:14:15.230 --> 00:14:20.680 align:start position:0% this project and to this web a consistent<00:14:16.600> well<00:14:17.600> we<00:14:17.810> have<00:14:19.480> such<00:14:20.480> an<00:14:20.600> amazing 00:14:20.680 --> 00:14:20.690 align:start position:0% consistent well we have such an amazing 00:14:20.690 --> 00:14:22.840 align:start position:0% consistent well we have such an amazing community<00:14:21.110> we<00:14:21.680> can<00:14:21.830> see<00:14:21.980> from<00:14:22.160> from<00:14:22.490> protocol 00:14:22.840 --> 00:14:22.850 align:start position:0% community we can see from from protocol 00:14:22.850 --> 00:14:28.270 align:start position:0% community we can see from from protocol design<00:14:25.510> studies<00:14:26.510> research<00:14:27.050> and<00:14:27.890> how<00:14:28.070> they 00:14:28.270 --> 00:14:28.280 align:start position:0% design studies research and how they 00:14:28.280 --> 00:14:30.460 align:start position:0% design studies research and how they interact<00:14:28.700> with<00:14:28.880> each<00:14:29.000> other<00:14:29.180> really<00:14:29.839> using<00:14:30.290> I 00:14:30.460 --> 00:14:30.470 align:start position:0% interact with each other really using I 00:14:30.470 --> 00:14:34.870 align:start position:0% interact with each other really using I guess<00:14:30.940> if<00:14:31.940> the<00:14:32.180> research<00:14:32.650> website<00:14:33.650> and<00:14:33.980> some 00:14:34.870 --> 00:14:34.880 align:start position:0% guess if the research website and some 00:14:34.880 --> 00:14:39.269 align:start position:0% guess if the research website and some forums<00:14:35.300> and<00:14:35.660> chats<00:14:37.150> but<00:14:38.150> here<00:14:38.510> about<00:14:38.750> web 00:14:39.269 --> 00:14:39.279 align:start position:0% forums and chats but here about web 00:14:39.279 --> 00:14:43.090 align:start position:0% forums and chats but here about web protocols<00:14:40.279> and<00:14:40.810> changes<00:14:41.810> in<00:14:42.170> discussions<00:14:42.740> we 00:14:43.090 --> 00:14:43.100 align:start position:0% protocols and changes in discussions we 00:14:43.100 --> 00:14:45.310 align:start position:0% protocols and changes in discussions we mainly<00:14:43.279> use<00:14:43.430> the<00:14:43.850> use<00:14:44.180> Ethier<00:14:44.540> Magicians<00:14:45.050> the 00:14:45.310 --> 00:14:45.320 align:start position:0% mainly use the use Ethier Magicians the 00:14:45.320 --> 00:14:48.519 align:start position:0% mainly use the use Ethier Magicians the org<00:14:45.560> website<00:14:45.860> and<00:14:46.610> the<00:14:47.420> EIP<00:14:47.720> is<00:14:47.990> which<00:14:48.290> you're 00:14:48.519 --> 00:14:48.529 align:start position:0% org website and the EIP is which you're 00:14:48.529 --> 00:14:51.220 align:start position:0% org website and the EIP is which you're probably<00:14:48.770> familiar<00:14:49.430> with<00:14:49.700> already 00:14:51.220 --> 00:14:51.230 align:start position:0% probably familiar with already 00:14:51.230 --> 00:14:55.130 align:start position:0% probably familiar with already also<00:14:52.230> we<00:14:52.290> have<00:14:52.470> well<00:14:53.430> a<00:14:54.000> pool<00:14:54.660> requests<00:14:55.020> are 00:14:55.130 --> 00:14:55.140 align:start position:0% also we have well a pool requests are 00:14:55.140 --> 00:14:58.640 align:start position:0% also we have well a pool requests are pretty<00:14:55.620> welcome<00:14:56.070> we<00:14:56.550> can<00:14:56.700> guide<00:14:56.850> you<00:14:57.090> in<00:14:57.650> your 00:14:58.640 --> 00:14:58.650 align:start position:0% pretty welcome we can guide you in your 00:14:58.650 --> 00:15:04.940 align:start position:0% pretty welcome we can guide you in your own<00:14:59.580> adventure<00:15:01.490> and<00:15:02.490> I<00:15:03.240> have<00:15:03.420> you<00:15:03.600> know<00:15:03.950> this 00:15:04.940 --> 00:15:04.950 align:start position:0% own adventure and I have you know this 00:15:04.950 --> 00:15:08.090 align:start position:0% own adventure and I have you know this is<00:15:05.160> something<00:15:05.370> that<00:15:05.930> should<00:15:06.930> be<00:15:07.070> you<00:15:08.070> know 00:15:08.090 --> 00:15:08.100 align:start position:0% is something that should be you know 00:15:08.100 --> 00:15:14.660 align:start position:0% is something that should be you know exposed<00:15:09.770> at<00:15:10.770> least<00:15:11.010> from<00:15:11.130> every<00:15:11.550> oh<00:15:12.020> yeah<00:15:13.670> yeah 00:15:14.660 --> 00:15:14.670 align:start position:0% exposed at least from every oh yeah yeah 00:15:14.670 --> 00:15:17.000 align:start position:0% exposed at least from every oh yeah yeah that's<00:15:14.970> it<00:15:15.120> if<00:15:15.810> we<00:15:15.990> don't<00:15:16.170> stop<00:15:16.410> relying<00:15:16.740> on 00:15:17.000 --> 00:15:17.010 align:start position:0% that's it if we don't stop relying on 00:15:17.010 --> 00:15:21.140 align:start position:0% that's it if we don't stop relying on put<00:15:17.730> any<00:15:18.080> centralized<00:15:19.080> service<00:15:19.860> not<00:15:20.490> just<00:15:20.760> in 00:15:21.140 --> 00:15:21.150 align:start position:0% put any centralized service not just in 00:15:21.150 --> 00:15:23.240 align:start position:0% put any centralized service not just in forever<00:15:21.420> because<00:15:21.630> we're<00:15:21.870> loving<00:15:22.170> foot<00:15:22.380> it<00:15:22.500> but 00:15:23.240 --> 00:15:23.250 align:start position:0% forever because we're loving foot it but 00:15:23.250 --> 00:15:24.860 align:start position:0% forever because we're loving foot it but you<00:15:23.340> know<00:15:23.460> that's<00:15:23.790> I<00:15:24.030> think<00:15:24.150> that's<00:15:24.450> too<00:15:24.690> much 00:15:24.860 --> 00:15:24.870 align:start position:0% you know that's I think that's too much 00:15:24.870 --> 00:15:26.860 align:start position:0% you know that's I think that's too much on<00:15:25.020> their<00:15:25.140> shoulders 00:15:26.860 --> 00:15:26.870 align:start position:0% on their shoulders 00:15:26.870 --> 00:15:29.480 align:start position:0% on their shoulders the<00:15:27.870> vision<00:15:28.230> of<00:15:28.350> a<00:15:28.470> few<00:15:28.710> failed<00:15:28.980> is<00:15:29.310> like 00:15:29.480 --> 00:15:29.490 align:start position:0% the vision of a few failed is like 00:15:29.490 --> 00:15:32.840 align:start position:0% the vision of a few failed is like defeating<00:15:30.210> the<00:15:30.300> Purple's<00:15:31.310> so<00:15:32.310> I<00:15:32.340> think<00:15:32.580> we 00:15:32.840 --> 00:15:32.850 align:start position:0% defeating the Purple's so I think we 00:15:32.850 --> 00:15:34.970 align:start position:0% defeating the Purple's so I think we should<00:15:32.880> you<00:15:33.450> know<00:15:33.570> give<00:15:33.960> more<00:15:34.230> attention<00:15:34.530> and 00:15:34.970 --> 00:15:34.980 align:start position:0% should you know give more attention and 00:15:34.980 --> 00:15:38.960 align:start position:0% should you know give more attention and and<00:15:35.280> to<00:15:36.120> those<00:15:36.330> new<00:15:37.200> projects<00:15:37.830> like<00:15:38.700> line 00:15:38.960 --> 00:15:38.970 align:start position:0% and to those new projects like line 00:15:38.970 --> 00:15:43.700 align:start position:0% and to those new projects like line sensation<00:15:40.100> in<00:15:41.100> cubed<00:15:41.520> that<00:15:42.510> note<00:15:42.780> Vinod 00:15:43.700 --> 00:15:43.710 align:start position:0% sensation in cubed that note Vinod 00:15:43.710 --> 00:15:47.210 align:start position:0% sensation in cubed that note Vinod denote<00:15:44.810> there's<00:15:45.810> madam<00:15:46.320> asked<00:15:46.470> project<00:15:47.010> which 00:15:47.210 --> 00:15:47.220 align:start position:0% denote there's madam asked project which 00:15:47.220 --> 00:15:48.050 align:start position:0% denote there's madam asked project which I<00:15:47.340> can't<00:15:47.610> pronounce 00:15:48.050 --> 00:15:48.060 align:start position:0% I can't pronounce 00:15:48.060 --> 00:15:53.930 align:start position:0% I can't pronounce maybe's<00:15:48.390> was<00:15:48.960> that<00:15:49.890> color<00:15:50.070> maybe<00:15:52.790> well<00:15:53.790> of 00:15:53.930 --> 00:15:53.940 align:start position:0% maybe's was that color maybe well of 00:15:53.940 --> 00:15:55.370 align:start position:0% maybe's was that color maybe well of course<00:15:54.000> universal<00:15:54.660> logins<00:15:54.990> and<00:15:55.230> meta 00:15:55.370 --> 00:15:55.380 align:start position:0% course universal logins and meta 00:15:55.380 --> 00:15:57.860 align:start position:0% course universal logins and meta transactions<00:15:55.980> which<00:15:56.220> you<00:15:56.610> know<00:15:56.730> can<00:15:57.000> remove 00:15:57.860 --> 00:15:57.870 align:start position:0% transactions which you know can remove 00:15:57.870 --> 00:16:04.810 align:start position:0% transactions which you know can remove the<00:15:58.050> burden<00:15:58.380> off<00:15:58.589> of<00:15:59.960> the<00:16:00.960> user<00:16:01.380> interfaces 00:16:04.810 --> 00:16:04.820 align:start position:0% 00:16:04.820 --> 00:16:09.710 align:start position:0% altogether<00:16:07.040> so<00:16:08.040> remember<00:16:08.610> guys<00:16:08.730> d<00:16:09.210> stands<00:16:09.600> for 00:16:09.710 --> 00:16:09.720 align:start position:0% altogether so remember guys d stands for 00:16:09.720 --> 00:16:11.140 align:start position:0% altogether so remember guys d stands for decentralized 00:16:11.140 --> 00:16:11.150 align:start position:0% decentralized 00:16:11.150 --> 00:16:14.780 align:start position:0% decentralized so<00:16:12.150> that<00:16:12.540> that's<00:16:12.990> you<00:16:13.440> know<00:16:13.560> for<00:16:13.890> your<00:16:14.760> own 00:16:14.780 --> 00:16:14.790 align:start position:0% so that that's you know for your own 00:16:14.790 --> 00:16:18.100 align:start position:0% so that that's you know for your own website<00:16:15.150> where<00:16:15.870> you<00:16:16.080> you<00:16:16.500> know<00:16:16.589> is<00:16:17.370> about<00:16:17.490> to 00:16:18.100 --> 00:16:18.110 align:start position:0% website where you you know is about to 00:16:18.110 --> 00:16:22.310 align:start position:0% website where you you know is about to to<00:16:19.110> publish<00:16:19.470> it<00:16:19.650> is<00:16:20.220> about<00:16:20.520> you<00:16:21.020> which<00:16:22.020> kind<00:16:22.260> of 00:16:22.310 --> 00:16:22.320 align:start position:0% to publish it is about you which kind of 00:16:22.320 --> 00:16:25.730 align:start position:0% to publish it is about you which kind of services<00:16:22.800> you<00:16:22.920> connect<00:16:23.250> to<00:16:24.170> this<00:16:25.170> is<00:16:25.380> exactly 00:16:25.730 --> 00:16:25.740 align:start position:0% services you connect to this is exactly 00:16:25.740 --> 00:16:26.780 align:start position:0% services you connect to this is exactly what<00:16:26.010> we're<00:16:26.190> here<00:16:26.430> for 00:16:26.780 --> 00:16:26.790 align:start position:0% what we're here for 00:16:26.790 --> 00:16:31.130 align:start position:0% what we're here for yeah<00:16:28.100> so<00:16:29.100> you<00:16:29.490> know<00:16:29.520> there's<00:16:30.510> a<00:16:30.600> bit<00:16:30.780> yeah<00:16:31.110> a 00:16:31.130 --> 00:16:31.140 align:start position:0% yeah so you know there's a bit yeah a 00:16:31.140 --> 00:16:34.450 align:start position:0% yeah so you know there's a bit yeah a bit<00:16:31.410> more<00:16:31.620> about<00:16:31.890> our<00:16:32.250> features<00:16:33.380> missed 00:16:34.450 --> 00:16:34.460 align:start position:0% bit more about our features missed 00:16:34.460 --> 00:16:37.010 align:start position:0% bit more about our features missed really<00:16:35.460> wants<00:16:35.760> you<00:16:35.850> to<00:16:36.030> have<00:16:36.210> any<00:16:36.450> real<00:16:36.810> with 00:16:37.010 --> 00:16:37.020 align:start position:0% really wants you to have any real with 00:16:37.020 --> 00:16:40.220 align:start position:0% really wants you to have any real with your<00:16:37.320> node<00:16:37.440> in<00:16:37.680> your<00:16:37.710> computer<00:16:38.930> even<00:16:39.930> it's 00:16:40.220 --> 00:16:40.230 align:start position:0% your node in your computer even it's 00:16:40.230 --> 00:16:42.770 align:start position:0% your node in your computer even it's like<00:16:40.950> line<00:16:41.190> for<00:16:41.550> ultralight<00:16:42.000> client<00:16:42.540> in<00:16:42.690> a 00:16:42.770 --> 00:16:42.780 align:start position:0% like line for ultralight client in a 00:16:42.780 --> 00:16:45.170 align:start position:0% like line for ultralight client in a possible<00:16:43.200> future<00:16:43.730> use<00:16:44.730> of<00:16:44.760> swarm 00:16:45.170 --> 00:16:45.180 align:start position:0% possible future use of swarm 00:16:45.180 --> 00:16:48.470 align:start position:0% possible future use of swarm communication<00:16:45.839> layer<00:16:46.280> and<00:16:47.280> yes<00:16:47.760> we<00:16:48.120> can<00:16:48.150> read 00:16:48.470 --> 00:16:48.480 align:start position:0% communication layer and yes we can read 00:16:48.480 --> 00:16:53.550 align:start position:0% communication layer and yes we can read ens<00:16:48.930> content<00:16:49.410> hosted<00:16:49.980> also<00:16:50.430> arm<00:16:51.440> so 00:16:53.550 --> 00:16:53.560 align:start position:0% ens content hosted also arm so 00:16:53.560 --> 00:16:56.460 align:start position:0% ens content hosted also arm so that's<00:16:54.129> pretty<00:16:54.519> much<00:16:54.759> it<00:16:54.970> guys<00:16:55.019> so<00:16:56.019> the<00:16:56.319> web 00:16:56.460 --> 00:16:56.470 align:start position:0% that's pretty much it guys so the web 00:16:56.470 --> 00:16:59.850 align:start position:0% that's pretty much it guys so the web through<00:16:56.680> progress<00:16:57.129> is<00:16:57.939> so<00:16:58.120> exciting<00:16:58.709> and<00:16:59.709> this 00:16:59.850 --> 00:16:59.860 align:start position:0% through progress is so exciting and this 00:16:59.860 --> 00:17:02.610 align:start position:0% through progress is so exciting and this is<00:17:00.069> so<00:17:00.279> proud<00:17:00.550> to<00:17:00.699> be<00:17:00.790> part<00:17:00.999> of<00:17:01.060> it<00:17:01.209> mm-hmm<00:17:01.959> so 00:17:02.610 --> 00:17:02.620 align:start position:0% is so proud to be part of it mm-hmm so 00:17:02.620 --> 00:17:03.569 align:start position:0% is so proud to be part of it mm-hmm so thank<00:17:02.980> you<00:17:03.040> so<00:17:03.100> much 00:17:03.569 --> 00:17:03.579 align:start position:0% thank you so much 00:17:03.579 --> 00:17:05.030 align:start position:0% thank you so much have<00:17:04.059> fun 00:17:05.030 --> 00:17:05.040 align:start position:0% have fun 00:17:05.040 --> 00:17:14.150 align:start position:0% have fun [Applause] 00:17:14.150 --> 00:17:14.160 align:start position:0% 00:17:14.160 --> 00:17:16.220 align:start position:0% you