WEBVTT Kind: captions Language: en 00:00:00.000 --> 00:00:04.350 align:start position:0% foreign 00:00:04.350 --> 00:00:04.360 align:start position:0% 00:00:04.360 --> 00:00:16.150 align:start position:0% [Music] 00:00:16.150 --> 00:00:16.160 align:start position:0% 00:00:16.160 --> 00:00:19.250 align:start position:0% I'm<00:00:17.160> Nick<00:00:17.340> Johnson<00:00:17.580> founder<00:00:18.359> of<00:00:18.480> ens<00:00:18.960> and<00:00:19.140> lead 00:00:19.250 --> 00:00:19.260 align:start position:0% I'm Nick Johnson founder of ens and lead 00:00:19.260 --> 00:00:21.410 align:start position:0% I'm Nick Johnson founder of ens and lead developer<00:00:19.800> and<00:00:20.520> I'm<00:00:20.640> here<00:00:20.880> to<00:00:21.000> give<00:00:21.119> you<00:00:21.240> an 00:00:21.410 --> 00:00:21.420 align:start position:0% developer and I'm here to give you an 00:00:21.420 --> 00:00:23.450 align:start position:0% developer and I'm here to give you an update<00:00:21.720> on<00:00:22.140> what's<00:00:22.439> happened<00:00:22.619> with<00:00:22.859> enes<00:00:23.279> in 00:00:23.450 --> 00:00:23.460 align:start position:0% update on what's happened with enes in 00:00:23.460 --> 00:00:25.250 align:start position:0% update on what's happened with enes in the<00:00:23.580> last<00:00:23.699> three<00:00:23.939> years<00:00:24.180> which<00:00:24.660> is<00:00:24.779> give<00:00:25.019> or 00:00:25.250 --> 00:00:25.260 align:start position:0% the last three years which is give or 00:00:25.260 --> 00:00:28.089 align:start position:0% the last three years which is give or take<00:00:25.439> 300<00:00:26.160> years<00:00:26.580> in<00:00:26.820> crypto 00:00:28.089 --> 00:00:28.099 align:start position:0% take 300 years in crypto 00:00:28.099 --> 00:00:32.210 align:start position:0% take 300 years in crypto before<00:00:29.099> I<00:00:29.400> actually<00:00:29.640> start<00:00:30.619> can<00:00:31.619> anyone<00:00:31.980> who's 00:00:32.210 --> 00:00:32.220 align:start position:0% before I actually start can anyone who's 00:00:32.220 --> 00:00:34.549 align:start position:0% before I actually start can anyone who's got<00:00:32.520> an<00:00:32.700> ens<00:00:33.120> card<00:00:33.360> hold<00:00:33.719> it<00:00:33.960> up<00:00:34.079> above<00:00:34.380> their 00:00:34.549 --> 00:00:34.559 align:start position:0% got an ens card hold it up above their 00:00:34.559 --> 00:00:35.690 align:start position:0% got an ens card hold it up above their head 00:00:35.690 --> 00:00:35.700 align:start position:0% head 00:00:35.700 --> 00:00:39.170 align:start position:0% head wonderful<00:00:36.660> probably<00:00:37.200> about<00:00:37.500> half<00:00:37.920> of<00:00:38.160> you<00:00:38.340> I'm 00:00:39.170 --> 00:00:39.180 align:start position:0% wonderful probably about half of you I'm 00:00:39.180 --> 00:00:40.970 align:start position:0% wonderful probably about half of you I'm so<00:00:39.420> delighted<00:00:39.780> with<00:00:39.960> how<00:00:40.320> everyone's<00:00:40.800> been 00:00:40.970 --> 00:00:40.980 align:start position:0% so delighted with how everyone's been 00:00:40.980 --> 00:00:42.950 align:start position:0% so delighted with how everyone's been doing<00:00:41.100> with<00:00:41.280> this<00:00:41.460> if<00:00:42.180> the<00:00:42.360> person<00:00:42.480> next<00:00:42.780> to 00:00:42.950 --> 00:00:42.960 align:start position:0% doing with this if the person next to 00:00:42.960 --> 00:00:45.470 align:start position:0% doing with this if the person next to you<00:00:43.020> held<00:00:43.440> a<00:00:43.500> card<00:00:43.620> up<00:00:43.860> have<00:00:44.820> a<00:00:44.940> word<00:00:45.059> with<00:00:45.239> them 00:00:45.470 --> 00:00:45.480 align:start position:0% you held a card up have a word with them 00:00:45.480 --> 00:00:49.010 align:start position:0% you held a card up have a word with them say<00:00:45.840> hi<00:00:46.140> tap<00:00:47.100> your<00:00:47.280> phone<00:00:47.640> to<00:00:47.940> their<00:00:48.120> card<00:00:48.420> and 00:00:49.010 --> 00:00:49.020 align:start position:0% say hi tap your phone to their card and 00:00:49.020 --> 00:00:50.690 align:start position:0% say hi tap your phone to their card and you'll<00:00:49.260> get<00:00:49.379> a<00:00:49.500> poab<00:00:49.800> that<00:00:50.039> proves<00:00:50.340> that<00:00:50.520> you 00:00:50.690 --> 00:00:50.700 align:start position:0% you'll get a poab that proves that you 00:00:50.700 --> 00:00:53.990 align:start position:0% you'll get a poab that proves that you visit<00:00:50.879> uh<00:00:51.239> that<00:00:51.420> you<00:00:51.539> met<00:00:51.660> them<00:00:51.899> at<00:00:52.559> Defcon<00:00:53.039> uh 00:00:53.990 --> 00:00:54.000 align:start position:0% visit uh that you met them at Defcon uh 00:00:54.000 --> 00:00:55.490 align:start position:0% visit uh that you met them at Defcon uh we<00:00:54.239> still<00:00:54.360> have<00:00:54.480> a<00:00:54.600> few<00:00:54.719> of<00:00:54.840> these<00:00:55.020> cards<00:00:55.320> left 00:00:55.490 --> 00:00:55.500 align:start position:0% we still have a few of these cards left 00:00:55.500 --> 00:00:58.369 align:start position:0% we still have a few of these cards left at<00:00:55.680> our<00:00:55.860> booth<00:00:56.160> on<00:00:56.280> level<00:00:56.399> three<00:00:56.899> uh<00:00:57.899> so<00:00:58.140> after 00:00:58.369 --> 00:00:58.379 align:start position:0% at our booth on level three uh so after 00:00:58.379 --> 00:01:00.410 align:start position:0% at our booth on level three uh so after the<00:00:58.620> event<00:00:58.800> come<00:00:59.280> down<00:00:59.460> we'll<00:00:59.760> print<00:01:00.000> one<00:01:00.239> for 00:01:00.410 --> 00:01:00.420 align:start position:0% the event come down we'll print one for 00:01:00.420 --> 00:01:03.229 align:start position:0% the event come down we'll print one for you<00:01:00.600> with<00:01:00.899> your<00:01:01.079> ens<00:01:01.620> name<00:01:01.860> and<00:01:02.640> your<00:01:02.820> ens 00:01:03.229 --> 00:01:03.239 align:start position:0% you with your ens name and your ens 00:01:03.239 --> 00:01:05.990 align:start position:0% you with your ens name and your ens avatar<00:01:03.660> on<00:01:03.840> it<00:01:04.220> we<00:01:05.220> expect<00:01:05.400> we'll<00:01:05.700> run<00:01:05.880> out 00:01:05.990 --> 00:01:06.000 align:start position:0% avatar on it we expect we'll run out 00:01:06.000 --> 00:01:08.090 align:start position:0% avatar on it we expect we'll run out sometime<00:01:06.420> this<00:01:06.600> evening<00:01:06.780> so<00:01:07.200> I'm<00:01:07.320> sorry<00:01:07.560> if<00:01:07.860> we 00:01:08.090 --> 00:01:08.100 align:start position:0% sometime this evening so I'm sorry if we 00:01:08.100 --> 00:01:10.789 align:start position:0% sometime this evening so I'm sorry if we don't<00:01:08.760> get<00:01:08.939> to<00:01:09.060> everyone 00:01:10.789 --> 00:01:10.799 align:start position:0% don't get to everyone 00:01:10.799 --> 00:01:12.530 align:start position:0% don't get to everyone um<00:01:10.860> but<00:01:11.100> this<00:01:11.280> is<00:01:11.400> a<00:01:11.580> great<00:01:11.700> opportunity<00:01:12.119> to 00:01:12.530 --> 00:01:12.540 align:start position:0% um but this is a great opportunity to 00:01:12.540 --> 00:01:14.270 align:start position:0% um but this is a great opportunity to meet<00:01:12.659> the<00:01:12.900> person<00:01:13.020> next<00:01:13.320> to<00:01:13.500> you<00:01:13.619> and<00:01:13.920> have 00:01:14.270 --> 00:01:14.280 align:start position:0% meet the person next to you and have 00:01:14.280 --> 00:01:17.390 align:start position:0% meet the person next to you and have cryptographic<00:01:14.939> proof<00:01:15.240> of<00:01:15.360> that<00:01:15.540> afterwards 00:01:17.390 --> 00:01:17.400 align:start position:0% cryptographic proof of that afterwards 00:01:17.400 --> 00:01:20.450 align:start position:0% cryptographic proof of that afterwards so<00:01:18.119> uh<00:01:18.479> first<00:01:18.720> off<00:01:18.900> the<00:01:19.080> agenda<00:01:19.500> uh<00:01:20.040> I'm<00:01:20.280> going 00:01:20.450 --> 00:01:20.460 align:start position:0% so uh first off the agenda uh I'm going 00:01:20.460 --> 00:01:21.950 align:start position:0% so uh first off the agenda uh I'm going to<00:01:20.520> recap<00:01:20.880> everything<00:01:21.119> we've<00:01:21.479> done<00:01:21.659> in<00:01:21.840> the 00:01:21.950 --> 00:01:21.960 align:start position:0% to recap everything we've done in the 00:01:21.960 --> 00:01:24.170 align:start position:0% to recap everything we've done in the last<00:01:22.080> three<00:01:22.320> years<00:01:22.560> and<00:01:23.159> then<00:01:23.520> go<00:01:23.700> on<00:01:23.820> to<00:01:24.000> talk 00:01:24.170 --> 00:01:24.180 align:start position:0% last three years and then go on to talk 00:01:24.180 --> 00:01:26.270 align:start position:0% last three years and then go on to talk about<00:01:24.360> what<00:01:25.080> we're<00:01:25.200> working<00:01:25.380> on<00:01:25.619> now<00:01:25.860> and<00:01:26.100> what 00:01:26.270 --> 00:01:26.280 align:start position:0% about what we're working on now and what 00:01:26.280 --> 00:01:29.210 align:start position:0% about what we're working on now and what we're<00:01:26.400> working<00:01:26.580> on<00:01:26.820> next<00:01:27.380> uh<00:01:28.380> first<00:01:28.740> of<00:01:28.920> all<00:01:28.979> in 00:01:29.210 --> 00:01:29.220 align:start position:0% we're working on next uh first of all in 00:01:29.220 --> 00:01:31.670 align:start position:0% we're working on next uh first of all in the<00:01:29.400> next<00:01:29.520> category<00:01:30.000> uh<00:01:30.840> Thorin<00:01:31.320> which<00:01:31.560> is 00:01:31.670 --> 00:01:31.680 align:start position:0% the next category uh Thorin which is 00:01:31.680 --> 00:01:34.010 align:start position:0% the next category uh Thorin which is ens's<00:01:32.340> New<00:01:32.520> Look<00:01:32.700> and<00:01:32.880> design<00:01:33.060> system<00:01:33.420> and<00:01:33.780> new 00:01:34.010 --> 00:01:34.020 align:start position:0% ens's New Look and design system and new 00:01:34.020 --> 00:01:37.069 align:start position:0% ens's New Look and design system and new app<00:01:34.400> second<00:01:35.400> of<00:01:35.640> all<00:01:35.820> talking<00:01:36.119> about<00:01:36.360> scaling 00:01:37.069 --> 00:01:37.079 align:start position:0% app second of all talking about scaling 00:01:37.079 --> 00:01:41.270 align:start position:0% app second of all talking about scaling ens<00:01:37.619> with<00:01:38.579> off-chain<00:01:39.060> reads<00:01:39.479> and<00:01:39.600> writes<00:01:40.280> next 00:01:41.270 --> 00:01:41.280 align:start position:0% ens with off-chain reads and writes next 00:01:41.280 --> 00:01:43.190 align:start position:0% ens with off-chain reads and writes next the<00:01:41.640> name<00:01:41.820> wrapper<00:01:42.360> which<00:01:42.780> you<00:01:42.960> may<00:01:43.079> have 00:01:43.190 --> 00:01:43.200 align:start position:0% the name wrapper which you may have 00:01:43.200 --> 00:01:45.830 align:start position:0% the name wrapper which you may have heard<00:01:43.320> about<00:01:43.560> is<00:01:43.860> a<00:01:44.040> way<00:01:44.220> to<00:01:44.659> improve<00:01:45.659> the 00:01:45.830 --> 00:01:45.840 align:start position:0% heard about is a way to improve the 00:01:45.840 --> 00:01:47.749 align:start position:0% heard about is a way to improve the functionality<00:01:46.259> of<00:01:46.380> igneous<00:01:46.860> names<00:01:47.100> and<00:01:47.579> the 00:01:47.749 --> 00:01:47.759 align:start position:0% functionality of igneous names and the 00:01:47.759 --> 00:01:50.109 align:start position:0% functionality of igneous names and the ability<00:01:48.000> to<00:01:48.299> issue<00:01:48.600> trustless<00:01:48.960> subdomains 00:01:50.109 --> 00:01:50.119 align:start position:0% ability to issue trustless subdomains 00:01:50.119 --> 00:01:53.510 align:start position:0% ability to issue trustless subdomains finally<00:01:51.119> zero<00:01:52.079> gas<00:01:52.200> DNS<00:01:52.619> integration<00:01:52.979> how<00:01:53.340> we 00:01:53.510 --> 00:01:53.520 align:start position:0% finally zero gas DNS integration how we 00:01:53.520 --> 00:01:55.130 align:start position:0% finally zero gas DNS integration how we can<00:01:53.640> use<00:01:53.820> these<00:01:54.240> other<00:01:54.360> components<00:01:54.899> we've 00:01:55.130 --> 00:01:55.140 align:start position:0% can use these other components we've 00:01:55.140 --> 00:01:58.490 align:start position:0% can use these other components we've built<00:01:55.439> to<00:01:56.040> make<00:01:56.159> ens<00:01:56.700> integration<00:01:57.500> possible 00:01:58.490 --> 00:01:58.500 align:start position:0% built to make ens integration possible 00:01:58.500 --> 00:02:02.149 align:start position:0% built to make ens integration possible for<00:01:58.920> DNS<00:01:59.460> names<00:01:59.700> without<00:02:00.479> any<00:02:00.780> guest<00:02:01.140> fees<00:02:01.439> and 00:02:02.149 --> 00:02:02.159 align:start position:0% for DNS names without any guest fees and 00:02:02.159 --> 00:02:03.889 align:start position:0% for DNS names without any guest fees and then<00:02:02.280> the<00:02:02.460> conclusion 00:02:03.889 --> 00:02:03.899 align:start position:0% then the conclusion 00:02:03.899 --> 00:02:06.170 align:start position:0% then the conclusion so<00:02:04.500> first<00:02:04.740> of<00:02:04.920> all<00:02:04.979> the<00:02:05.100> recap<00:02:05.460> it's<00:02:05.700> been<00:02:05.939> a 00:02:06.170 --> 00:02:06.180 align:start position:0% so first of all the recap it's been a 00:02:06.180 --> 00:02:08.150 align:start position:0% so first of all the recap it's been a long<00:02:06.299> long<00:02:06.600> time<00:02:06.899> since<00:02:07.560> I've<00:02:07.740> been<00:02:07.920> at<00:02:08.039> a 00:02:08.150 --> 00:02:08.160 align:start position:0% long long time since I've been at a 00:02:08.160 --> 00:02:09.529 align:start position:0% long long time since I've been at a conference<00:02:08.399> since<00:02:08.640> I've<00:02:08.819> talked<00:02:09.119> on<00:02:09.239> a<00:02:09.360> stage 00:02:09.529 --> 00:02:09.539 align:start position:0% conference since I've talked on a stage 00:02:09.539 --> 00:02:11.690 align:start position:0% conference since I've talked on a stage in<00:02:09.780> front<00:02:09.899> of<00:02:10.020> a<00:02:10.140> lot<00:02:10.259> of<00:02:10.380> people<00:02:10.500> uh<00:02:11.459> since 00:02:11.690 --> 00:02:11.700 align:start position:0% in front of a lot of people uh since 00:02:11.700 --> 00:02:14.990 align:start position:0% in front of a lot of people uh since I've<00:02:11.819> given<00:02:12.120> anyone<00:02:12.420> an<00:02:12.660> update<00:02:12.900> on<00:02:13.140> ens<00:02:14.000> last 00:02:14.990 --> 00:02:15.000 align:start position:0% I've given anyone an update on ens last 00:02:15.000 --> 00:02:17.270 align:start position:0% I've given anyone an update on ens last time<00:02:15.180> I<00:02:15.360> spoke<00:02:15.540> was<00:02:15.720> at<00:02:15.900> last<00:02:16.020> Devcon<00:02:16.560> October 00:02:17.270 --> 00:02:17.280 align:start position:0% time I spoke was at last Devcon October 00:02:17.280 --> 00:02:20.570 align:start position:0% time I spoke was at last Devcon October 2019<00:02:17.700> uh<00:02:18.660> we're<00:02:18.959> just<00:02:19.200> transitioned<00:02:20.160> from<00:02:20.459> the 00:02:20.570 --> 00:02:20.580 align:start position:0% 2019 uh we're just transitioned from the 00:02:20.580 --> 00:02:23.270 align:start position:0% 2019 uh we're just transitioned from the interim<00:02:21.120> uh<00:02:21.720> auction<00:02:22.319> registrar<00:02:22.920> to<00:02:23.040> the 00:02:23.270 --> 00:02:23.280 align:start position:0% interim uh auction registrar to the 00:02:23.280 --> 00:02:25.550 align:start position:0% interim uh auction registrar to the permanent<00:02:23.580> registrar<00:02:24.200> featuring<00:02:25.200> its 00:02:25.550 --> 00:02:25.560 align:start position:0% permanent registrar featuring its 00:02:25.560 --> 00:02:28.910 align:start position:0% permanent registrar featuring its current<00:02:25.620> renewal<00:02:26.160> model<00:02:26.780> and<00:02:27.780> that<00:02:28.680> was<00:02:28.800> a 00:02:28.910 --> 00:02:28.920 align:start position:0% current renewal model and that was a 00:02:28.920 --> 00:02:30.890 align:start position:0% current renewal model and that was a mere<00:02:29.040> five<00:02:29.340> months<00:02:29.580> ago<00:02:29.819> and<00:02:30.420> while<00:02:30.599> it<00:02:30.780> was 00:02:30.890 --> 00:02:30.900 align:start position:0% mere five months ago and while it was 00:02:30.900 --> 00:02:32.570 align:start position:0% mere five months ago and while it was doing<00:02:31.020> well<00:02:31.260> at<00:02:31.440> the<00:02:31.620> time<00:02:31.800> we<00:02:32.160> had<00:02:32.340> very 00:02:32.570 --> 00:02:32.580 align:start position:0% doing well at the time we had very 00:02:32.580 --> 00:02:35.270 align:start position:0% doing well at the time we had very little<00:02:32.760> idea<00:02:33.180> of<00:02:33.599> the<00:02:34.080> phenomenon<00:02:34.560> ens<00:02:35.099> was 00:02:35.270 --> 00:02:35.280 align:start position:0% little idea of the phenomenon ens was 00:02:35.280 --> 00:02:38.030 align:start position:0% little idea of the phenomenon ens was going<00:02:35.459> to<00:02:35.580> be<00:02:35.640> coming<00:02:35.819> in<00:02:36.239> the<00:02:36.360> next<00:02:36.739> few<00:02:37.739> years 00:02:38.030 --> 00:02:38.040 align:start position:0% going to be coming in the next few years 00:02:38.040 --> 00:02:41.150 align:start position:0% going to be coming in the next few years we<00:02:38.760> had<00:02:38.879> about<00:02:39.180> 50<00:02:39.660> Integrations<00:02:40.319> with 00:02:41.150 --> 00:02:41.160 align:start position:0% we had about 50 Integrations with 00:02:41.160 --> 00:02:43.990 align:start position:0% we had about 50 Integrations with various<00:02:41.819> wallets<00:02:42.360> including<00:02:43.200> metamask 00:02:43.990 --> 00:02:44.000 align:start position:0% various wallets including metamask 00:02:44.000 --> 00:02:48.170 align:start position:0% various wallets including metamask applications<00:02:45.000> such<00:02:45.540> as<00:02:46.099> etherscan<00:02:47.099> and<00:02:47.819> so 00:02:48.170 --> 00:02:48.180 align:start position:0% applications such as etherscan and so 00:02:48.180 --> 00:02:50.509 align:start position:0% applications such as etherscan and so forth<00:02:48.540> that's<00:02:49.379> changed<00:02:49.800> a<00:02:49.920> bit<00:02:50.040> in<00:02:50.280> the<00:02:50.400> last 00:02:50.509 --> 00:02:50.519 align:start position:0% forth that's changed a bit in the last 00:02:50.519 --> 00:02:53.630 align:start position:0% forth that's changed a bit in the last three<00:02:50.819> years<00:02:51.140> our<00:02:52.140> set<00:02:52.379> of<00:02:52.560> Integrations<00:02:53.099> now 00:02:53.630 --> 00:02:53.640 align:start position:0% three years our set of Integrations now 00:02:53.640 --> 00:02:55.910 align:start position:0% three years our set of Integrations now looks<00:02:54.120> more<00:02:54.300> like<00:02:54.540> this 00:02:55.910 --> 00:02:55.920 align:start position:0% looks more like this 00:02:55.920 --> 00:03:01.970 align:start position:0% looks more like this laughs 00:03:01.970 --> 00:03:01.980 align:start position:0% 00:03:01.980 --> 00:03:03.830 align:start position:0% so<00:03:02.459> as<00:03:02.580> you<00:03:02.760> can<00:03:02.819> see<00:03:02.940> we've<00:03:03.239> come<00:03:03.360> a<00:03:03.540> long<00:03:03.660> way 00:03:03.830 --> 00:03:03.840 align:start position:0% so as you can see we've come a long way 00:03:03.840 --> 00:03:06.890 align:start position:0% so as you can see we've come a long way from<00:03:04.500> under<00:03:04.800> 50<00:03:05.040> Integrations<00:03:05.700> to<00:03:06.180> over<00:03:06.300> 500 00:03:06.890 --> 00:03:06.900 align:start position:0% from under 50 Integrations to over 500 00:03:06.900 --> 00:03:10.250 align:start position:0% from under 50 Integrations to over 500 we<00:03:07.800> had<00:03:07.920> about<00:03:08.099> 300<00:03:09.000> 000<00:03:09.180> registrations<00:03:09.780> back 00:03:10.250 --> 00:03:10.260 align:start position:0% we had about 300 000 registrations back 00:03:10.260 --> 00:03:12.290 align:start position:0% we had about 300 000 registrations back in<00:03:10.379> the<00:03:10.560> day<00:03:10.680> that's<00:03:11.280> now<00:03:11.519> over<00:03:11.700> two<00:03:12.000> and<00:03:12.180> a 00:03:12.290 --> 00:03:12.300 align:start position:0% in the day that's now over two and a 00:03:12.300 --> 00:03:15.890 align:start position:0% in the day that's now over two and a half million<00:03:13.260> uh<00:03:14.040> we<00:03:14.400> had<00:03:14.519> about<00:03:14.760> 96<00:03:15.780> 000 00:03:15.890 --> 00:03:15.900 align:start position:0% half million uh we had about 96 000 00:03:15.900 --> 00:03:17.930 align:start position:0% half million uh we had about 96 000 ethereum<00:03:16.440> addresses<00:03:16.920> that<00:03:17.220> had<00:03:17.400> interacted 00:03:17.930 --> 00:03:17.940 align:start position:0% ethereum addresses that had interacted 00:03:17.940 --> 00:03:21.050 align:start position:0% ethereum addresses that had interacted with<00:03:18.360> ens<00:03:19.260> in<00:03:19.500> some<00:03:19.680> way<00:03:19.860> that's<00:03:20.400> now<00:03:20.640> over<00:03:20.819> a 00:03:21.050 --> 00:03:21.060 align:start position:0% with ens in some way that's now over a 00:03:21.060 --> 00:03:23.089 align:start position:0% with ens in some way that's now over a million<00:03:21.300> addresses 00:03:23.089 --> 00:03:23.099 align:start position:0% million addresses 00:03:23.099 --> 00:03:26.930 align:start position:0% million addresses um<00:03:23.180> 66<00:03:24.180> 700<00:03:25.140> years<00:03:25.620> of<00:03:25.920> registration<00:03:26.459> had<00:03:26.760> been 00:03:26.930 --> 00:03:26.940 align:start position:0% um 66 700 years of registration had been 00:03:26.940 --> 00:03:29.390 align:start position:0% um 66 700 years of registration had been purchased<00:03:27.420> that's<00:03:27.959> now<00:03:28.260> over<00:03:28.500> six<00:03:29.040> and<00:03:29.220> a<00:03:29.340> half 00:03:29.390 --> 00:03:29.400 align:start position:0% purchased that's now over six and a half 00:03:29.400 --> 00:03:31.970 align:start position:0% purchased that's now over six and a half million<00:03:29.959> uh<00:03:30.959> if<00:03:31.140> you<00:03:31.260> strung<00:03:31.560> them<00:03:31.680> all<00:03:31.800> into 00:03:31.970 --> 00:03:31.980 align:start position:0% million uh if you strung them all into 00:03:31.980 --> 00:03:35.750 align:start position:0% million uh if you strung them all into in<00:03:32.400> figuratively<00:03:33.360> uh<00:03:34.200> and<00:03:34.560> the<00:03:34.800> nascent<00:03:35.280> EMS 00:03:35.750 --> 00:03:35.760 align:start position:0% in figuratively uh and the nascent EMS 00:03:35.760 --> 00:03:39.050 align:start position:0% in figuratively uh and the nascent EMS treasury<00:03:36.120> had<00:03:36.420> a<00:03:36.599> stunning<00:03:37.379> 382<00:03:38.220> ethernet<00:03:38.819> at 00:03:39.050 --> 00:03:39.060 align:start position:0% treasury had a stunning 382 ethernet at 00:03:39.060 --> 00:03:42.350 align:start position:0% treasury had a stunning 382 ethernet at the<00:03:39.180> time<00:03:39.300> that's<00:03:40.019> now<00:03:40.260> 38<00:03:41.040> 000<00:03:41.159> teeth<00:03:41.400> and 00:03:42.350 --> 00:03:42.360 align:start position:0% the time that's now 38 000 teeth and 00:03:42.360 --> 00:03:44.149 align:start position:0% the time that's now 38 000 teeth and I'll<00:03:42.540> talk<00:03:42.720> soon<00:03:42.959> about<00:03:43.200> the<00:03:43.440> Dow<00:03:43.680> and<00:03:43.920> how 00:03:44.149 --> 00:03:44.159 align:start position:0% I'll talk soon about the Dow and how 00:03:44.159 --> 00:03:47.570 align:start position:0% I'll talk soon about the Dow and how it's<00:03:44.340> able<00:03:44.940> to<00:03:45.060> put<00:03:45.180> that<00:03:45.360> to<00:03:45.480> use 00:03:47.570 --> 00:03:47.580 align:start position:0% it's able to put that to use 00:03:47.580 --> 00:03:49.930 align:start position:0% it's able to put that to use of<00:03:48.420> course<00:03:48.599> it's<00:03:48.900> not<00:03:49.080> all<00:03:49.200> about<00:03:49.379> the<00:03:49.680> numbers 00:03:49.930 --> 00:03:49.940 align:start position:0% of course it's not all about the numbers 00:03:49.940 --> 00:03:52.250 align:start position:0% of course it's not all about the numbers ens<00:03:50.940> has<00:03:51.120> accomplished<00:03:51.540> a<00:03:51.720> lot<00:03:51.840> on<00:03:52.080> both 00:03:52.250 --> 00:03:52.260 align:start position:0% ens has accomplished a lot on both 00:03:52.260 --> 00:03:54.110 align:start position:0% ens has accomplished a lot on both Technical<00:03:52.680> and<00:03:52.920> governance<00:03:53.340> fronts<00:03:53.819> in<00:03:54.000> the 00:03:54.110 --> 00:03:54.120 align:start position:0% Technical and governance fronts in the 00:03:54.120 --> 00:03:56.390 align:start position:0% Technical and governance fronts in the past<00:03:54.239> three<00:03:54.540> years<00:03:54.780> uh<00:03:55.680> some<00:03:55.799> of<00:03:55.920> it<00:03:56.040> will<00:03:56.159> seem 00:03:56.390 --> 00:03:56.400 align:start position:0% past three years uh some of it will seem 00:03:56.400 --> 00:03:58.270 align:start position:0% past three years uh some of it will seem like<00:03:56.519> old<00:03:56.760> news<00:03:56.940> but<00:03:57.299> it's<00:03:57.420> been<00:03:57.659> a<00:03:57.780> long<00:03:57.900> time 00:03:58.270 --> 00:03:58.280 align:start position:0% like old news but it's been a long time 00:03:58.280 --> 00:04:01.670 align:start position:0% like old news but it's been a long time uh<00:03:59.280> at<00:03:59.580> divcon<00:04:00.000> 5<00:04:00.299> we<00:04:00.720> had<00:04:00.840> limited<00:04:01.319> DNS 00:04:01.670 --> 00:04:01.680 align:start position:0% uh at divcon 5 we had limited DNS 00:04:01.680 --> 00:04:04.430 align:start position:0% uh at divcon 5 we had limited DNS integration<00:04:02.220> with<00:04:02.819> only<00:04:02.940> the<00:04:03.180> dot<00:04:03.540> XYZ<00:04:04.019> TLD 00:04:04.430 --> 00:04:04.440 align:start position:0% integration with only the dot XYZ TLD 00:04:04.440 --> 00:04:07.990 align:start position:0% integration with only the dot XYZ TLD supported<00:04:05.099> uh<00:04:05.940> you<00:04:06.480> could<00:04:06.599> take<00:04:07.200> a<00:04:07.319> neonessner 00:04:07.990 --> 00:04:08.000 align:start position:0% supported uh you could take a neonessner 00:04:08.000 --> 00:04:11.149 align:start position:0% supported uh you could take a neonessner sorry.e<00:04:09.000> XYZ<00:04:09.540> name<00:04:09.720> you<00:04:10.439> could<00:04:10.560> import<00:04:10.860> it 00:04:11.149 --> 00:04:11.159 align:start position:0% sorry.e XYZ name you could import it 00:04:11.159 --> 00:04:13.009 align:start position:0% sorry.e XYZ name you could import it into<00:04:11.280> ens<00:04:11.760> and<00:04:12.000> use<00:04:12.239> it<00:04:12.420> just<00:04:12.599> like<00:04:12.780> you<00:04:12.900> would 00:04:13.009 --> 00:04:13.019 align:start position:0% into ens and use it just like you would 00:04:13.019 --> 00:04:16.310 align:start position:0% into ens and use it just like you would any<00:04:13.260> dot<00:04:13.620> ethname<00:04:14.540> since<00:04:15.540> then<00:04:15.720> this<00:04:16.019> has<00:04:16.139> been 00:04:16.310 --> 00:04:16.320 align:start position:0% any dot ethname since then this has been 00:04:16.320 --> 00:04:18.050 align:start position:0% any dot ethname since then this has been expanded<00:04:16.799> to<00:04:16.979> nearly<00:04:17.340> every<00:04:17.639> top<00:04:17.820> level 00:04:18.050 --> 00:04:18.060 align:start position:0% expanded to nearly every top level 00:04:18.060 --> 00:04:21.830 align:start position:0% expanded to nearly every top level domain<00:04:18.560> uh<00:04:19.560> that<00:04:20.160> supports<00:04:20.459> DNS<00:04:20.880> Tech<00:04:21.180> so 00:04:21.830 --> 00:04:21.840 align:start position:0% domain uh that supports DNS Tech so 00:04:21.840 --> 00:04:23.570 align:start position:0% domain uh that supports DNS Tech so that's<00:04:22.019> nearly<00:04:22.380> 90<00:04:22.560> of<00:04:23.100> all<00:04:23.220> top<00:04:23.340> level 00:04:23.570 --> 00:04:23.580 align:start position:0% that's nearly 90 of all top level 00:04:23.580 --> 00:04:26.210 align:start position:0% that's nearly 90 of all top level domains<00:04:24.259> nearly<00:04:25.259> any<00:04:25.380> name<00:04:25.680> can<00:04:25.919> now<00:04:26.100> be 00:04:26.210 --> 00:04:26.220 align:start position:0% domains nearly any name can now be 00:04:26.220 --> 00:04:28.070 align:start position:0% domains nearly any name can now be imported<00:04:26.580> into<00:04:26.699> enes<00:04:27.180> and<00:04:27.419> used<00:04:27.600> as<00:04:27.780> a<00:04:27.900> native 00:04:28.070 --> 00:04:28.080 align:start position:0% imported into enes and used as a native 00:04:28.080 --> 00:04:30.830 align:start position:0% imported into enes and used as a native name<00:04:28.320> uh<00:04:29.220> just<00:04:29.460> ask<00:04:29.699> our<00:04:30.000> developer<00:04:30.479> Advocate 00:04:30.830 --> 00:04:30.840 align:start position:0% name uh just ask our developer Advocate 00:04:30.840 --> 00:04:33.110 align:start position:0% name uh just ask our developer Advocate Loop<00:04:31.199> dot<00:04:31.440> computer<00:04:31.560> it's<00:04:32.520> printed<00:04:32.880> on<00:04:33.000> his 00:04:33.110 --> 00:04:33.120 align:start position:0% Loop dot computer it's printed on his 00:04:33.120 --> 00:04:34.510 align:start position:0% Loop dot computer it's printed on his badge<00:04:33.479> I<00:04:33.600> believe 00:04:34.510 --> 00:04:34.520 align:start position:0% badge I believe 00:04:34.520 --> 00:04:37.129 align:start position:0% badge I believe there<00:04:35.520> are<00:04:35.639> transaction<00:04:36.060> fees<00:04:36.479> associated 00:04:37.129 --> 00:04:37.139 align:start position:0% there are transaction fees associated 00:04:37.139 --> 00:04:39.830 align:start position:0% there are transaction fees associated with<00:04:37.500> importing<00:04:37.979> any<00:04:38.100> of<00:04:38.280> these<00:04:38.460> names<00:04:38.660> and<00:04:39.660> at 00:04:39.830 --> 00:04:39.840 align:start position:0% with importing any of these names and at 00:04:39.840 --> 00:04:41.689 align:start position:0% with importing any of these names and at times<00:04:40.080> when<00:04:40.560> gas<00:04:40.800> prices<00:04:41.040> have<00:04:41.400> been<00:04:41.520> very 00:04:41.689 --> 00:04:41.699 align:start position:0% times when gas prices have been very 00:04:41.699 --> 00:04:43.490 align:start position:0% times when gas prices have been very high<00:04:42.000> and<00:04:42.300> The<00:04:42.540> Ether<00:04:42.720> price<00:04:42.960> has<00:04:43.139> been<00:04:43.259> very 00:04:43.490 --> 00:04:43.500 align:start position:0% high and The Ether price has been very 00:04:43.500 --> 00:04:46.310 align:start position:0% high and The Ether price has been very high<00:04:43.740> it's<00:04:44.580> been<00:04:44.759> quite<00:04:44.940> pricey<00:04:45.419> but<00:04:45.780> we've 00:04:46.310 --> 00:04:46.320 align:start position:0% high it's been quite pricey but we've 00:04:46.320 --> 00:04:48.710 align:start position:0% high it's been quite pricey but we've got<00:04:46.860> a<00:04:46.979> plan<00:04:47.160> to<00:04:47.520> improve<00:04:48.180> that<00:04:48.300> massively 00:04:48.710 --> 00:04:48.720 align:start position:0% got a plan to improve that massively 00:04:48.720 --> 00:04:50.450 align:start position:0% got a plan to improve that massively which<00:04:48.900> I'll<00:04:49.139> talk<00:04:49.320> about<00:04:49.440> shortly 00:04:50.450 --> 00:04:50.460 align:start position:0% which I'll talk about shortly 00:04:50.460 --> 00:04:53.330 align:start position:0% which I'll talk about shortly another<00:04:51.120> major<00:04:51.479> Improvement<00:04:52.020> has<00:04:52.440> been<00:04:52.620> ens's 00:04:53.330 --> 00:04:53.340 align:start position:0% another major Improvement has been ens's 00:04:53.340 --> 00:04:55.730 align:start position:0% another major Improvement has been ens's transition<00:04:53.699> away<00:04:54.240> from<00:04:54.600> being<00:04:54.900> just<00:04:55.259> a<00:04:55.380> way<00:04:55.560> to 00:04:55.730 --> 00:04:55.740 align:start position:0% transition away from being just a way to 00:04:55.740 --> 00:04:58.430 align:start position:0% transition away from being just a way to name<00:04:55.979> wallets<00:04:56.580> and<00:04:57.080> decentralized<00:04:58.080> content 00:04:58.430 --> 00:04:58.440 align:start position:0% name wallets and decentralized content 00:04:58.440 --> 00:05:01.670 align:start position:0% name wallets and decentralized content to<00:04:59.340> being<00:04:59.699> a<00:05:00.120> web<00:05:00.360> 3<00:05:00.660> native<00:05:01.080> identity 00:05:01.670 --> 00:05:01.680 align:start position:0% to being a web 3 native identity 00:05:01.680 --> 00:05:04.129 align:start position:0% to being a web 3 native identity platform<00:05:02.100> with<00:05:02.820> the<00:05:03.060> introduction<00:05:03.419> of<00:05:03.600> Avatar 00:05:04.129 --> 00:05:04.139 align:start position:0% platform with the introduction of Avatar 00:05:04.139 --> 00:05:06.950 align:start position:0% platform with the introduction of Avatar records<00:05:04.740> and<00:05:05.699> text<00:05:06.060> fields<00:05:06.540> that<00:05:06.660> provide 00:05:06.950 --> 00:05:06.960 align:start position:0% records and text fields that provide 00:05:06.960 --> 00:05:08.870 align:start position:0% records and text fields that provide information<00:05:07.199> about<00:05:07.740> your<00:05:07.979> profiles<00:05:08.520> such<00:05:08.699> as 00:05:08.870 --> 00:05:08.880 align:start position:0% information about your profiles such as 00:05:08.880 --> 00:05:10.189 align:start position:0% information about your profiles such as your<00:05:09.060> Twitter<00:05:09.120> handle<00:05:09.540> your<00:05:09.720> email<00:05:09.900> address 00:05:10.189 --> 00:05:10.199 align:start position:0% your Twitter handle your email address 00:05:10.199 --> 00:05:13.670 align:start position:0% your Twitter handle your email address your<00:05:10.919> ens<00:05:11.400> name<00:05:11.580> now<00:05:11.820> represents<00:05:12.419> you<00:05:12.660> as<00:05:13.139> your 00:05:13.670 --> 00:05:13.680 align:start position:0% your ens name now represents you as your 00:05:13.680 --> 00:05:16.670 align:start position:0% your ens name now represents you as your web3<00:05:14.040> identity<00:05:14.600> it's<00:05:15.600> a<00:05:15.780> universal<00:05:16.259> portable 00:05:16.670 --> 00:05:16.680 align:start position:0% web3 identity it's a universal portable 00:05:16.680 --> 00:05:19.610 align:start position:0% web3 identity it's a universal portable identity<00:05:17.300> and<00:05:18.300> one<00:05:18.780> project<00:05:19.020> that's<00:05:19.380> been 00:05:19.610 --> 00:05:19.620 align:start position:0% identity and one project that's been 00:05:19.620 --> 00:05:21.950 align:start position:0% identity and one project that's been bringing<00:05:19.979> that<00:05:20.160> to<00:05:20.340> more<00:05:20.520> users<00:05:20.880> is<00:05:21.479> sign<00:05:21.720> in 00:05:21.950 --> 00:05:21.960 align:start position:0% bringing that to more users is sign in 00:05:21.960 --> 00:05:25.490 align:start position:0% bringing that to more users is sign in with<00:05:22.080> ethereum<00:05:22.820> it<00:05:23.820> started<00:05:24.180> out<00:05:24.360> as<00:05:24.780> an<00:05:25.020> RFP 00:05:25.490 --> 00:05:25.500 align:start position:0% with ethereum it started out as an RFP 00:05:25.500 --> 00:05:28.310 align:start position:0% with ethereum it started out as an RFP issued<00:05:26.100> by<00:05:26.220> ens<00:05:26.759> and<00:05:27.360> it<00:05:27.479> was<00:05:27.600> funded<00:05:27.960> by<00:05:28.199> a 00:05:28.310 --> 00:05:28.320 align:start position:0% issued by ens and it was funded by a 00:05:28.320 --> 00:05:30.529 align:start position:0% issued by ens and it was funded by a joint<00:05:28.560> Grant<00:05:28.860> from<00:05:29.280> ens<00:05:29.759> and<00:05:29.940> the<00:05:30.120> ethereum 00:05:30.529 --> 00:05:30.539 align:start position:0% joint Grant from ens and the ethereum 00:05:30.539 --> 00:05:31.450 align:start position:0% joint Grant from ens and the ethereum foundation 00:05:31.450 --> 00:05:31.460 align:start position:0% foundation 00:05:31.460 --> 00:05:34.249 align:start position:0% foundation Spruce<00:05:32.460> won<00:05:32.699> the<00:05:32.880> bid<00:05:33.060> for<00:05:33.300> that<00:05:33.419> and<00:05:33.780> has<00:05:34.020> done 00:05:34.249 --> 00:05:34.259 align:start position:0% Spruce won the bid for that and has done 00:05:34.259 --> 00:05:36.650 align:start position:0% Spruce won the bid for that and has done an<00:05:34.500> outstanding<00:05:35.100> job<00:05:35.400> of<00:05:36.000> growing<00:05:36.300> it<00:05:36.479> into 00:05:36.650 --> 00:05:36.660 align:start position:0% an outstanding job of growing it into 00:05:36.660 --> 00:05:38.510 align:start position:0% an outstanding job of growing it into the<00:05:36.900> primary<00:05:37.199> way<00:05:37.440> that<00:05:37.680> people<00:05:37.860> authenticate 00:05:38.510 --> 00:05:38.520 align:start position:0% the primary way that people authenticate 00:05:38.520 --> 00:05:42.189 align:start position:0% the primary way that people authenticate with<00:05:38.699> ethereum<00:05:39.620> replacing<00:05:40.620> a<00:05:40.919> plethora<00:05:41.520> of 00:05:42.189 --> 00:05:42.199 align:start position:0% with ethereum replacing a plethora of 00:05:42.199 --> 00:05:44.629 align:start position:0% with ethereum replacing a plethora of incompatible<00:05:43.199> and<00:05:43.560> and<00:05:43.919> different<00:05:44.160> standards 00:05:44.629 --> 00:05:44.639 align:start position:0% incompatible and and different standards 00:05:44.639 --> 00:05:46.430 align:start position:0% incompatible and and different standards for<00:05:44.880> citing<00:05:45.240> messages<00:05:45.479> to<00:05:46.020> assert<00:05:46.259> your 00:05:46.430 --> 00:05:46.440 align:start position:0% for citing messages to assert your 00:05:46.440 --> 00:05:49.550 align:start position:0% for citing messages to assert your identity<00:05:47.180> with<00:05:48.180> a<00:05:48.360> symbol<00:05:48.780> system<00:05:48.960> that<00:05:49.380> can 00:05:49.550 --> 00:05:49.560 align:start position:0% identity with a symbol system that can 00:05:49.560 --> 00:05:53.390 align:start position:0% identity with a symbol system that can be<00:05:49.740> thank<00:05:50.100> you<00:05:50.400> uh<00:05:51.120> that<00:05:51.720> can<00:05:51.900> be<00:05:52.620> um<00:05:52.620> easily 00:05:53.390 --> 00:05:53.400 align:start position:0% be thank you uh that can be um easily 00:05:53.400 --> 00:05:55.550 align:start position:0% be thank you uh that can be um easily plugged<00:05:53.759> into<00:05:53.820> existing<00:05:54.419> systems<00:05:54.900> including 00:05:55.550 --> 00:05:55.560 align:start position:0% plugged into existing systems including 00:05:55.560 --> 00:05:58.070 align:start position:0% plugged into existing systems including web<00:05:55.979> 2<00:05:56.220> Legacy<00:05:56.820> systems 00:05:58.070 --> 00:05:58.080 align:start position:0% web 2 Legacy systems 00:05:58.080 --> 00:06:00.170 align:start position:0% web 2 Legacy systems but<00:05:58.560> of<00:05:58.740> course<00:05:58.919> when<00:05:59.160> I<00:05:59.340> talk<00:05:59.460> about<00:05:59.639> the<00:06:00.000> last 00:06:00.170 --> 00:06:00.180 align:start position:0% but of course when I talk about the last 00:06:00.180 --> 00:06:01.850 align:start position:0% but of course when I talk about the last three<00:06:00.419> years<00:06:00.660> and<00:06:01.080> particularly<00:06:01.440> the<00:06:01.620> last 00:06:01.850 --> 00:06:01.860 align:start position:0% three years and particularly the last 00:06:01.860 --> 00:06:04.430 align:start position:0% three years and particularly the last year<00:06:02.100> top<00:06:02.820> of<00:06:03.000> most<00:06:03.180> people's<00:06:03.600> minds<00:06:04.020> will<00:06:04.259> be 00:06:04.430 --> 00:06:04.440 align:start position:0% year top of most people's minds will be 00:06:04.440 --> 00:06:06.950 align:start position:0% year top of most people's minds will be the<00:06:04.620> launch<00:06:04.800> of<00:06:04.979> the<00:06:05.160> ens<00:06:05.639> Dow<00:06:06.000> which<00:06:06.720> is<00:06:06.780> now 00:06:06.950 --> 00:06:06.960 align:start position:0% the launch of the ens Dow which is now 00:06:06.960 --> 00:06:08.570 align:start position:0% the launch of the ens Dow which is now one<00:06:07.199> of<00:06:07.320> the<00:06:07.440> largest<00:06:07.740> and<00:06:08.039> most<00:06:08.220> active 00:06:08.570 --> 00:06:08.580 align:start position:0% one of the largest and most active 00:06:08.580 --> 00:06:12.409 align:start position:0% one of the largest and most active dowels<00:06:09.120> in<00:06:09.300> web3<00:06:10.100> which<00:06:11.100> I<00:06:11.340> am<00:06:11.520> absolutely 00:06:12.409 --> 00:06:12.419 align:start position:0% dowels in web3 which I am absolutely 00:06:12.419 --> 00:06:14.950 align:start position:0% dowels in web3 which I am absolutely both<00:06:12.780> Blown<00:06:13.380> Away<00:06:13.500> about 00:06:14.950 --> 00:06:14.960 align:start position:0% both Blown Away about 00:06:14.960 --> 00:06:17.689 align:start position:0% both Blown Away about ens<00:06:15.960> has<00:06:16.440> always<00:06:16.560> aimed<00:06:17.100> for<00:06:17.220> gradual 00:06:17.689 --> 00:06:17.699 align:start position:0% ens has always aimed for gradual 00:06:17.699 --> 00:06:20.090 align:start position:0% ens has always aimed for gradual decentralization<00:06:18.539> starting<00:06:19.500> with<00:06:19.919> the 00:06:20.090 --> 00:06:20.100 align:start position:0% decentralization starting with the 00:06:20.100 --> 00:06:22.850 align:start position:0% decentralization starting with the minimum<00:06:20.580> set<00:06:20.820> of<00:06:20.940> emissions<00:06:21.360> held<00:06:22.319> by<00:06:22.620> the 00:06:22.850 --> 00:06:22.860 align:start position:0% minimum set of emissions held by the 00:06:22.860 --> 00:06:24.770 align:start position:0% minimum set of emissions held by the widest<00:06:23.220> number<00:06:23.400> of<00:06:23.520> people<00:06:23.699> we<00:06:23.940> could<00:06:24.120> which 00:06:24.770 --> 00:06:24.780 align:start position:0% widest number of people we could which 00:06:24.780 --> 00:06:26.749 align:start position:0% widest number of people we could which was<00:06:24.960> the<00:06:25.259> original<00:06:25.440> uh<00:06:26.160> four<00:06:26.460> of<00:06:26.639> seven 00:06:26.749 --> 00:06:26.759 align:start position:0% was the original uh four of seven 00:06:26.759 --> 00:06:29.930 align:start position:0% was the original uh four of seven multi-sig<00:06:27.740> unlike<00:06:28.740> most<00:06:28.919> multi-seekers<00:06:29.759> it 00:06:29.930 --> 00:06:29.940 align:start position:0% multi-sig unlike most multi-seekers it 00:06:29.940 --> 00:06:32.270 align:start position:0% multi-sig unlike most multi-seekers it included<00:06:30.360> participants<00:06:31.080> from<00:06:31.560> around<00:06:31.919> the 00:06:32.270 --> 00:06:32.280 align:start position:0% included participants from around the 00:06:32.280 --> 00:06:35.390 align:start position:0% included participants from around the ecosystem<00:06:32.759> not<00:06:33.180> team<00:06:33.419> members<00:06:34.039> and<00:06:35.039> they<00:06:35.280> had 00:06:35.390 --> 00:06:35.400 align:start position:0% ecosystem not team members and they had 00:06:35.400 --> 00:06:37.490 align:start position:0% ecosystem not team members and they had limited<00:06:35.819> powers<00:06:36.060> to<00:06:36.419> upgrade<00:06:36.780> enes<00:06:37.259> to 00:06:37.490 --> 00:06:37.500 align:start position:0% limited powers to upgrade enes to 00:06:37.500 --> 00:06:40.070 align:start position:0% limited powers to upgrade enes to replace<00:06:37.620> components<00:06:38.340> our<00:06:39.300> goal<00:06:39.660> was<00:06:39.840> always 00:06:40.070 --> 00:06:40.080 align:start position:0% replace components our goal was always 00:06:40.080 --> 00:06:43.730 align:start position:0% replace components our goal was always to<00:06:40.620> move<00:06:40.800> from<00:06:41.160> that<00:06:41.460> to<00:06:42.000> a<00:06:42.180> system<00:06:42.360> where<00:06:42.900> ens 00:06:43.730 --> 00:06:43.740 align:start position:0% to move from that to a system where ens 00:06:43.740 --> 00:06:45.770 align:start position:0% to move from that to a system where ens was<00:06:44.340> governed<00:06:44.759> by<00:06:45.060> a<00:06:45.300> decentralized 00:06:45.770 --> 00:06:45.780 align:start position:0% was governed by a decentralized 00:06:45.780 --> 00:06:48.409 align:start position:0% was governed by a decentralized organization<00:06:46.580> since<00:06:47.580> we<00:06:47.759> launched<00:06:48.060> all<00:06:48.240> the 00:06:48.409 --> 00:06:48.419 align:start position:0% organization since we launched all the 00:06:48.419 --> 00:06:51.650 align:start position:0% organization since we launched all the way<00:06:48.479> back<00:06:48.660> in<00:06:48.900> 2017<00:06:49.699> the<00:06:50.699> only<00:06:50.819> example<00:06:51.300> we<00:06:51.479> had 00:06:51.650 --> 00:06:51.660 align:start position:0% way back in 2017 the only example we had 00:06:51.660 --> 00:06:55.189 align:start position:0% way back in 2017 the only example we had to<00:06:51.780> go<00:06:51.960> on<00:06:52.139> was<00:06:52.639> vdao<00:06:53.639> which<00:06:54.419> needless<00:06:54.900> to<00:06:55.080> say 00:06:55.189 --> 00:06:55.199 align:start position:0% to go on was vdao which needless to say 00:06:55.199 --> 00:06:57.290 align:start position:0% to go on was vdao which needless to say was<00:06:55.500> not<00:06:55.740> a<00:06:55.860> stunning<00:06:56.220> success<00:06:56.520> that<00:06:56.819> inspired 00:06:57.290 --> 00:06:57.300 align:start position:0% was not a stunning success that inspired 00:06:57.300 --> 00:07:00.050 align:start position:0% was not a stunning success that inspired us<00:06:57.419> to<00:06:57.660> immediately<00:06:58.080> decentralize<00:06:59.060> but 00:07:00.050 --> 00:07:00.060 align:start position:0% us to immediately decentralize but 00:07:00.060 --> 00:07:02.390 align:start position:0% us to immediately decentralize but things<00:07:00.240> changed<00:07:00.780> a<00:07:00.960> lot<00:07:01.080> and<00:07:01.560> the<00:07:01.800> Dow<00:07:01.979> space 00:07:02.390 --> 00:07:02.400 align:start position:0% things changed a lot and the Dow space 00:07:02.400 --> 00:07:04.430 align:start position:0% things changed a lot and the Dow space is<00:07:02.699> now<00:07:02.819> a<00:07:03.000> lot<00:07:03.120> more<00:07:03.240> mature<00:07:03.660> than<00:07:03.900> it<00:07:04.080> was<00:07:04.199> in 00:07:04.430 --> 00:07:04.440 align:start position:0% is now a lot more mature than it was in 00:07:04.440 --> 00:07:07.550 align:start position:0% is now a lot more mature than it was in the<00:07:04.560> past<00:07:04.740> and<00:07:05.699> we<00:07:06.120> decided<00:07:06.600> that<00:07:06.960> you<00:07:07.500> know 00:07:07.550 --> 00:07:07.560 align:start position:0% the past and we decided that you know 00:07:07.560 --> 00:07:08.930 align:start position:0% the past and we decided that you know the<00:07:07.740> time<00:07:07.919> had<00:07:08.160> come<00:07:08.340> that<00:07:08.520> things<00:07:08.759> were 00:07:08.930 --> 00:07:08.940 align:start position:0% the time had come that things were 00:07:08.940 --> 00:07:11.390 align:start position:0% the time had come that things were mature<00:07:09.360> enough<00:07:09.479> that<00:07:09.840> we<00:07:10.020> could<00:07:10.259> let<00:07:10.800> the<00:07:10.979> ens 00:07:11.390 --> 00:07:11.400 align:start position:0% mature enough that we could let the ens 00:07:11.400 --> 00:07:14.930 align:start position:0% mature enough that we could let the ens Community<00:07:11.639> govern<00:07:12.060> ens<00:07:13.139> uh<00:07:13.800> and<00:07:14.039> the<00:07:14.220> Dow<00:07:14.400> is 00:07:14.930 --> 00:07:14.940 align:start position:0% Community govern ens uh and the Dow is 00:07:14.940 --> 00:07:17.029 align:start position:0% Community govern ens uh and the Dow is the<00:07:15.120> major<00:07:15.419> Milestone<00:07:15.900> along<00:07:16.259> that<00:07:16.560> path<00:07:16.740> of 00:07:17.029 --> 00:07:17.039 align:start position:0% the major Milestone along that path of 00:07:17.039 --> 00:07:19.969 align:start position:0% the major Milestone along that path of gradual<00:07:17.400> decentralization<00:07:18.199> uh<00:07:19.199> the<00:07:19.440> Dow<00:07:19.680> was 00:07:19.969 --> 00:07:19.979 align:start position:0% gradual decentralization uh the Dow was 00:07:19.979 --> 00:07:21.589 align:start position:0% gradual decentralization uh the Dow was now<00:07:20.160> responsible<00:07:20.639> for<00:07:21.000> almost<00:07:21.240> all 00:07:21.589 --> 00:07:21.599 align:start position:0% now responsible for almost all 00:07:21.599 --> 00:07:23.150 align:start position:0% now responsible for almost all governance<00:07:22.020> leaders<00:07:22.500> and<00:07:22.680> controls 00:07:23.150 --> 00:07:23.160 align:start position:0% governance leaders and controls 00:07:23.160 --> 00:07:25.490 align:start position:0% governance leaders and controls available<00:07:23.460> to<00:07:23.759> ens<00:07:24.240> including<00:07:25.020> approving 00:07:25.490 --> 00:07:25.500 align:start position:0% available to ens including approving 00:07:25.500 --> 00:07:27.650 align:start position:0% available to ens including approving contract<00:07:25.860> upgrades<00:07:26.520> changes<00:07:27.300> to<00:07:27.479> core 00:07:27.650 --> 00:07:27.660 align:start position:0% contract upgrades changes to core 00:07:27.660 --> 00:07:29.809 align:start position:0% contract upgrades changes to core parameters<00:07:28.259> such<00:07:28.680> as<00:07:28.800> pricing<00:07:29.340> and<00:07:29.580> how 00:07:29.809 --> 00:07:29.819 align:start position:0% parameters such as pricing and how 00:07:29.819 --> 00:07:32.210 align:start position:0% parameters such as pricing and how expired<00:07:30.300> names<00:07:30.479> are<00:07:30.780> used<00:07:31.020> it's<00:07:31.860> also 00:07:32.210 --> 00:07:32.220 align:start position:0% expired names are used it's also 00:07:32.220 --> 00:07:34.490 align:start position:0% expired names are used it's also responsible<00:07:32.699> for<00:07:33.120> treasury<00:07:33.539> grants<00:07:33.960> and 00:07:34.490 --> 00:07:34.500 align:start position:0% responsible for treasury grants and 00:07:34.500 --> 00:07:36.710 align:start position:0% responsible for treasury grants and projects<00:07:35.280> using<00:07:35.699> the<00:07:35.880> funding<00:07:36.180> gathered<00:07:36.539> from 00:07:36.710 --> 00:07:36.720 align:start position:0% projects using the funding gathered from 00:07:36.720 --> 00:07:37.909 align:start position:0% projects using the funding gathered from the<00:07:36.900> protocol 00:07:37.909 --> 00:07:37.919 align:start position:0% the protocol 00:07:37.919 --> 00:07:40.969 align:start position:0% the protocol in<00:07:38.699> the<00:07:38.880> years<00:07:39.000> since<00:07:39.360> the<00:07:39.539> Dow's<00:07:39.960> launch<00:07:40.199> the 00:07:40.969 --> 00:07:40.979 align:start position:0% in the years since the Dow's launch the 00:07:40.979 --> 00:07:42.469 align:start position:0% in the years since the Dow's launch the yiniest<00:07:41.400> hour<00:07:41.639> has<00:07:41.880> shown<00:07:42.060> that<00:07:42.180> it<00:07:42.360> can 00:07:42.469 --> 00:07:42.479 align:start position:0% yiniest hour has shown that it can 00:07:42.479 --> 00:07:44.150 align:start position:0% yiniest hour has shown that it can maintain<00:07:42.780> a<00:07:42.960> high<00:07:43.080> level<00:07:43.319> of<00:07:43.620> civilized 00:07:44.150 --> 00:07:44.160 align:start position:0% maintain a high level of civilized 00:07:44.160 --> 00:07:47.029 align:start position:0% maintain a high level of civilized discussion<00:07:44.660> uh<00:07:45.660> made<00:07:46.199> useful<00:07:46.680> progress 00:07:47.029 --> 00:07:47.039 align:start position:0% discussion uh made useful progress 00:07:47.039 --> 00:07:48.730 align:start position:0% discussion uh made useful progress forward<00:07:47.280> and<00:07:47.580> improving<00:07:47.940> the<00:07:48.060> protocol 00:07:48.730 --> 00:07:48.740 align:start position:0% forward and improving the protocol 00:07:48.740 --> 00:07:50.809 align:start position:0% forward and improving the protocol besides<00:07:49.740> budgeting<00:07:50.220> and<00:07:50.400> day-to-day 00:07:50.809 --> 00:07:50.819 align:start position:0% besides budgeting and day-to-day 00:07:50.819 --> 00:07:52.790 align:start position:0% besides budgeting and day-to-day bookkeeping<00:07:51.360> it's<00:07:51.660> made<00:07:51.900> meaningful<00:07:52.380> changes 00:07:52.790 --> 00:07:52.800 align:start position:0% bookkeeping it's made meaningful changes 00:07:52.800 --> 00:07:55.010 align:start position:0% bookkeeping it's made meaningful changes to<00:07:53.039> the<00:07:53.220> protocol<00:07:53.520> including<00:07:54.360> changing<00:07:54.840> how 00:07:55.010 --> 00:07:55.020 align:start position:0% to the protocol including changing how 00:07:55.020 --> 00:07:57.070 align:start position:0% to the protocol including changing how expired<00:07:55.560> names<00:07:55.680> are<00:07:55.919> handled<00:07:56.280> in<00:07:56.759> order<00:07:56.940> to 00:07:57.070 --> 00:07:57.080 align:start position:0% expired names are handled in order to 00:07:57.080 --> 00:07:59.629 align:start position:0% expired names are handled in order to safeguard<00:07:58.080> the<00:07:58.319> stability<00:07:58.680> and<00:07:59.039> fairness<00:07:59.400> of 00:07:59.629 --> 00:07:59.639 align:start position:0% safeguard the stability and fairness of 00:07:59.639 --> 00:08:02.089 align:start position:0% safeguard the stability and fairness of the<00:07:59.759> system<00:07:59.940> the<00:08:00.840> Dow<00:08:01.080> has<00:08:01.380> also<00:08:01.620> started<00:08:01.979> to 00:08:02.089 --> 00:08:02.099 align:start position:0% the system the Dow has also started to 00:08:02.099 --> 00:08:04.249 align:start position:0% the system the Dow has also started to build<00:08:02.280> out<00:08:02.520> public<00:08:02.819> goods<00:08:03.300> and<00:08:03.479> grants 00:08:04.249 --> 00:08:04.259 align:start position:0% build out public goods and grants 00:08:04.259 --> 00:08:07.189 align:start position:0% build out public goods and grants programs<00:08:04.800> of<00:08:04.919> its<00:08:05.220> own<00:08:05.479> one<00:08:06.479> example<00:08:06.840> of<00:08:07.020> this 00:08:07.189 --> 00:08:07.199 align:start position:0% programs of its own one example of this 00:08:07.199 --> 00:08:09.890 align:start position:0% programs of its own one example of this is<00:08:07.620> the<00:08:08.039> small<00:08:08.520> grants<00:08:09.000> rounds<00:08:09.419> that<00:08:09.599> we<00:08:09.720> now 00:08:09.890 --> 00:08:09.900 align:start position:0% is the small grants rounds that we now 00:08:09.900 --> 00:08:14.150 align:start position:0% is the small grants rounds that we now run<00:08:10.460> inspired<00:08:11.460> by<00:08:11.639> nouns<00:08:12.120> props<00:08:12.900> room<00:08:13.080> this<00:08:14.039> is 00:08:14.150 --> 00:08:14.160 align:start position:0% run inspired by nouns props room this is 00:08:14.160 --> 00:08:16.730 align:start position:0% run inspired by nouns props room this is a<00:08:14.400> regular<00:08:14.699> system<00:08:15.120> where<00:08:15.660> anyone<00:08:16.020> can<00:08:16.319> submit 00:08:16.730 --> 00:08:16.740 align:start position:0% a regular system where anyone can submit 00:08:16.740 --> 00:08:18.650 align:start position:0% a regular system where anyone can submit a<00:08:16.919> proposal<00:08:17.340> for<00:08:17.520> work<00:08:17.759> they<00:08:18.000> want<00:08:18.180> to<00:08:18.300> do<00:08:18.419> or 00:08:18.650 --> 00:08:18.660 align:start position:0% a proposal for work they want to do or 00:08:18.660 --> 00:08:20.930 align:start position:0% a proposal for work they want to do or work<00:08:18.900> they<00:08:19.080> have<00:08:19.259> done<00:08:19.440> anyone<00:08:20.340> with<00:08:20.460> ens 00:08:20.930 --> 00:08:20.940 align:start position:0% work they have done anyone with ens 00:08:20.940 --> 00:08:23.629 align:start position:0% work they have done anyone with ens tokens<00:08:21.360> from<00:08:21.599> the<00:08:21.780> Dow<00:08:21.960> can<00:08:22.259> vote<00:08:22.500> on<00:08:22.680> them<00:08:22.800> and 00:08:23.629 --> 00:08:23.639 align:start position:0% tokens from the Dow can vote on them and 00:08:23.639 --> 00:08:25.610 align:start position:0% tokens from the Dow can vote on them and the<00:08:23.819> top<00:08:23.940> five<00:08:24.180> in<00:08:24.479> each<00:08:24.660> category<00:08:25.080> we<00:08:25.319> have<00:08:25.440> a 00:08:25.610 --> 00:08:25.620 align:start position:0% the top five in each category we have a 00:08:25.620 --> 00:08:27.469 align:start position:0% the top five in each category we have a public<00:08:25.800> goods<00:08:26.220> category<00:08:26.639> and<00:08:26.879> an<00:08:27.060> ecosystem 00:08:27.469 --> 00:08:27.479 align:start position:0% public goods category and an ecosystem 00:08:27.479 --> 00:08:30.650 align:start position:0% public goods category and an ecosystem category<00:08:28.220> then<00:08:29.220> receive<00:08:29.639> one<00:08:29.879> e<00:08:30.060> feature<00:08:30.599> and 00:08:30.650 --> 00:08:30.660 align:start position:0% category then receive one e feature and 00:08:30.660 --> 00:08:33.409 align:start position:0% category then receive one e feature and funding<00:08:31.020> to<00:08:31.259> pursue<00:08:31.620> it<00:08:31.800> the<00:08:32.640> public<00:08:32.760> goods<00:08:33.240> is 00:08:33.409 --> 00:08:33.419 align:start position:0% funding to pursue it the public goods is 00:08:33.419 --> 00:08:35.389 align:start position:0% funding to pursue it the public goods is focused<00:08:33.779> on<00:08:33.899> anything<00:08:34.260> in<00:08:34.560> the<00:08:34.680> wider<00:08:34.979> ens 00:08:35.389 --> 00:08:35.399 align:start position:0% focused on anything in the wider ens 00:08:35.399 --> 00:08:39.350 align:start position:0% focused on anything in the wider ens ecosystem<00:08:36.200> and<00:08:37.200> the<00:08:37.440> Eco<00:08:37.860> ecosystem<00:08:38.399> category 00:08:39.350 --> 00:08:39.360 align:start position:0% ecosystem and the Eco ecosystem category 00:08:39.360 --> 00:08:41.149 align:start position:0% ecosystem and the Eco ecosystem category is<00:08:39.599> focused<00:08:40.020> more<00:08:40.200> on<00:08:40.320> things<00:08:40.560> that<00:08:40.800> relate 00:08:41.149 --> 00:08:41.159 align:start position:0% is focused more on things that relate 00:08:41.159 --> 00:08:42.709 align:start position:0% is focused more on things that relate directly<00:08:41.520> to<00:08:41.760> ens 00:08:42.709 --> 00:08:42.719 align:start position:0% directly to ens 00:08:42.719 --> 00:08:45.290 align:start position:0% directly to ens and<00:08:43.380> we<00:08:43.500> hope<00:08:43.680> this<00:08:43.919> can<00:08:44.159> work<00:08:44.339> to<00:08:44.760> better 00:08:45.290 --> 00:08:45.300 align:start position:0% and we hope this can work to better 00:08:45.300 --> 00:08:48.350 align:start position:0% and we hope this can work to better incubate<00:08:46.020> and<00:08:46.320> start<00:08:46.620> up<00:08:46.860> new<00:08:47.580> projects<00:08:48.060> both 00:08:48.350 --> 00:08:48.360 align:start position:0% incubate and start up new projects both 00:08:48.360 --> 00:08:50.690 align:start position:0% incubate and start up new projects both for<00:08:48.660> enes<00:08:49.200> and<00:08:49.380> for<00:08:49.620> the<00:08:49.740> wider<00:08:50.100> public<00:08:50.279> goods 00:08:50.690 --> 00:08:50.700 align:start position:0% for enes and for the wider public goods 00:08:50.700 --> 00:08:53.509 align:start position:0% for enes and for the wider public goods on<00:08:50.940> ethereum<00:08:51.480> and<00:08:51.600> web3<00:08:52.019> ecosystem<00:08:52.680> working 00:08:53.509 --> 00:08:53.519 align:start position:0% on ethereum and web3 ecosystem working 00:08:53.519 --> 00:08:55.670 align:start position:0% on ethereum and web3 ecosystem working groups<00:08:54.000> have<00:08:54.180> also<00:08:54.480> funded<00:08:54.839> initiatives<00:08:55.260> on 00:08:55.670 --> 00:08:55.680 align:start position:0% groups have also funded initiatives on 00:08:55.680 --> 00:08:59.090 align:start position:0% groups have also funded initiatives on scales<00:08:56.100> small<00:08:56.339> to<00:08:56.519> large<00:08:57.080> ranging<00:08:58.080> from<00:08:58.320> a<00:08:58.440> 200 00:08:59.090 --> 00:08:59.100 align:start position:0% scales small to large ranging from a 200 00:08:59.100 --> 00:09:03.410 align:start position:0% scales small to large ranging from a 200 000<00:08:59.279> k<00:08:59.580> Sorry<00:09:00.240> 200k<00:09:01.080> ens<00:09:01.920> token<00:09:02.339> Grant<00:09:02.700> to<00:09:03.240> the 00:09:03.410 --> 00:09:03.420 align:start position:0% 000 k Sorry 200k ens token Grant to the 00:09:03.420 --> 00:09:05.750 align:start position:0% 000 k Sorry 200k ens token Grant to the protocol<00:09:03.660> Guild<00:09:04.080> who<00:09:04.680> are<00:09:04.860> formed<00:09:05.279> to<00:09:05.459> help 00:09:05.750 --> 00:09:05.760 align:start position:0% protocol Guild who are formed to help 00:09:05.760 --> 00:09:07.790 align:start position:0% protocol Guild who are formed to help fund<00:09:06.240> core<00:09:06.480> developers<00:09:07.019> throughout<00:09:07.680> the 00:09:07.790 --> 00:09:07.800 align:start position:0% fund core developers throughout the 00:09:07.800 --> 00:09:09.550 align:start position:0% fund core developers throughout the platform 00:09:09.550 --> 00:09:09.560 align:start position:0% platform 00:09:09.560 --> 00:09:13.009 align:start position:0% platform 169k<00:09:10.560> Bitcoin<00:09:11.519> matching<00:09:12.000> pool<00:09:12.180> and<00:09:12.839> we 00:09:13.009 --> 00:09:13.019 align:start position:0% 169k Bitcoin matching pool and we 00:09:13.019 --> 00:09:16.310 align:start position:0% 169k Bitcoin matching pool and we continue<00:09:13.200> to<00:09:13.620> fund<00:09:13.920> and<00:09:14.040> support<00:09:14.220> Bitcoin<00:09:15.320> and 00:09:16.310 --> 00:09:16.320 align:start position:0% continue to fund and support Bitcoin and 00:09:16.320 --> 00:09:19.070 align:start position:0% continue to fund and support Bitcoin and smaller<00:09:16.800> projects<00:09:17.220> such<00:09:17.519> as<00:09:17.700> this<00:09:18.240> plugin<00:09:18.899> for 00:09:19.070 --> 00:09:19.080 align:start position:0% smaller projects such as this plugin for 00:09:19.080 --> 00:09:21.410 align:start position:0% smaller projects such as this plugin for discourse<00:09:19.620> forums<00:09:20.100> which<00:09:20.640> provides<00:09:21.060> you<00:09:21.180> with 00:09:21.410 --> 00:09:21.420 align:start position:0% discourse forums which provides you with 00:09:21.420 --> 00:09:25.250 align:start position:0% discourse forums which provides you with insight<00:09:21.839> into<00:09:22.399> the<00:09:23.399> roles<00:09:23.820> of<00:09:24.000> delegates<00:09:24.600> and 00:09:25.250 --> 00:09:25.260 align:start position:0% insight into the roles of delegates and 00:09:25.260 --> 00:09:27.410 align:start position:0% insight into the roles of delegates and their<00:09:25.440> participation<00:09:25.920> on<00:09:26.160> the<00:09:26.339> Forum<00:09:26.640> which 00:09:27.410 --> 00:09:27.420 align:start position:0% their participation on the Forum which 00:09:27.420 --> 00:09:29.150 align:start position:0% their participation on the Forum which is<00:09:27.540> something<00:09:27.779> that<00:09:28.140> any<00:09:28.320> dowel<00:09:28.860> that<00:09:28.980> uses 00:09:29.150 --> 00:09:29.160 align:start position:0% is something that any dowel that uses 00:09:29.160 --> 00:09:30.949 align:start position:0% is something that any dowel that uses discourse<00:09:29.760> can<00:09:29.940> take<00:09:30.060> and<00:09:30.300> plug<00:09:30.480> into<00:09:30.660> their 00:09:30.949 --> 00:09:30.959 align:start position:0% discourse can take and plug into their 00:09:30.959 --> 00:09:32.090 align:start position:0% discourse can take and plug into their own<00:09:31.080> system 00:09:32.090 --> 00:09:32.100 align:start position:0% own system 00:09:32.100 --> 00:09:35.030 align:start position:0% own system uh<00:09:32.760> this<00:09:33.060> was<00:09:33.240> built<00:09:33.660> by<00:09:34.080> Karma<00:09:34.800> and 00:09:35.030 --> 00:09:35.040 align:start position:0% uh this was built by Karma and 00:09:35.040 --> 00:09:36.530 align:start position:0% uh this was built by Karma and integrates<00:09:35.459> with<00:09:35.640> all<00:09:35.760> their<00:09:36.000> stuff<00:09:36.240> you<00:09:36.480> can 00:09:36.530 --> 00:09:36.540 align:start position:0% integrates with all their stuff you can 00:09:36.540 --> 00:09:38.690 align:start position:0% integrates with all their stuff you can also<00:09:36.779> just<00:09:37.019> use<00:09:37.320> it<00:09:37.440> to<00:09:37.620> provide<00:09:37.920> insight<00:09:38.459> into 00:09:38.690 --> 00:09:38.700 align:start position:0% also just use it to provide insight into 00:09:38.700 --> 00:09:41.150 align:start position:0% also just use it to provide insight into how<00:09:39.420> your<00:09:39.600> delegates<00:09:40.019> are<00:09:40.140> voted<00:09:40.500> how<00:09:40.860> active 00:09:41.150 --> 00:09:41.160 align:start position:0% how your delegates are voted how active 00:09:41.160 --> 00:09:43.250 align:start position:0% how your delegates are voted how active they<00:09:41.339> are<00:09:41.459> how<00:09:41.760> many<00:09:41.880> tokens<00:09:42.300> they<00:09:42.660> have<00:09:42.839> and 00:09:43.250 --> 00:09:43.260 align:start position:0% they are how many tokens they have and 00:09:43.260 --> 00:09:46.130 align:start position:0% they are how many tokens they have and so<00:09:43.500> forth<00:09:44.279> the<00:09:44.760> Dow<00:09:44.940> has<00:09:45.240> also<00:09:45.480> resulted<00:09:45.959> in 00:09:46.130 --> 00:09:46.140 align:start position:0% so forth the Dow has also resulted in 00:09:46.140 --> 00:09:47.930 align:start position:0% so forth the Dow has also resulted in more<00:09:46.380> Community<00:09:46.620> participation<00:09:47.339> in<00:09:47.640> the<00:09:47.760> core 00:09:47.930 --> 00:09:47.940 align:start position:0% more Community participation in the core 00:09:47.940 --> 00:09:50.990 align:start position:0% more Community participation in the core protocol<00:09:48.360> uh<00:09:49.320> one<00:09:49.680> major<00:09:49.860> success<00:09:50.339> story<00:09:50.640> is 00:09:50.990 --> 00:09:51.000 align:start position:0% protocol uh one major success story is 00:09:51.000 --> 00:09:53.030 align:start position:0% protocol uh one major success story is rafi's<00:09:51.600> work<00:09:51.720> on<00:09:51.959> improving<00:09:52.380> ans's 00:09:53.030 --> 00:09:53.040 align:start position:0% rafi's work on improving ans's 00:09:53.040 --> 00:09:54.790 align:start position:0% rafi's work on improving ans's normalization<00:09:53.580> functions 00:09:54.790 --> 00:09:54.800 align:start position:0% normalization functions 00:09:54.800 --> 00:09:56.990 align:start position:0% normalization functions normalization<00:09:55.800> is<00:09:56.100> how<00:09:56.279> we<00:09:56.459> handle<00:09:56.700> names 00:09:56.990 --> 00:09:57.000 align:start position:0% normalization is how we handle names 00:09:57.000 --> 00:09:59.389 align:start position:0% normalization is how we handle names like<00:09:57.420> uppercase<00:09:58.260> neck<00:09:58.560> being<00:09:58.860> different<00:09:59.100> from 00:09:59.389 --> 00:09:59.399 align:start position:0% like uppercase neck being different from 00:09:59.399 --> 00:10:02.530 align:start position:0% like uppercase neck being different from lowercase<00:09:59.880> neck<00:10:00.320> and<00:10:01.320> ambiguous<00:10:01.860> emojis 00:10:02.530 --> 00:10:02.540 align:start position:0% lowercase neck and ambiguous emojis 00:10:02.540 --> 00:10:05.750 align:start position:0% lowercase neck and ambiguous emojis hidden<00:10:03.540> characters<00:10:03.720> and<00:10:04.140> so<00:10:04.320> forth<00:10:04.620> to<00:10:05.580> start 00:10:05.750 --> 00:10:05.760 align:start position:0% hidden characters and so forth to start 00:10:05.760 --> 00:10:07.630 align:start position:0% hidden characters and so forth to start we<00:10:06.000> used<00:10:06.180> a<00:10:06.360> well-tested<00:10:06.959> system<00:10:07.200> called 00:10:07.630 --> 00:10:07.640 align:start position:0% we used a well-tested system called 00:10:07.640 --> 00:10:09.889 align:start position:0% we used a well-tested system called uts-46<00:10:08.640> which<00:10:09.060> is<00:10:09.120> what<00:10:09.300> the<00:10:09.480> domain<00:10:09.720> World 00:10:09.889 --> 00:10:09.899 align:start position:0% uts-46 which is what the domain World 00:10:09.899 --> 00:10:12.710 align:start position:0% uts-46 which is what the domain World uses<00:10:10.519> but<00:10:11.519> it's<00:10:11.640> become<00:10:11.940> clear<00:10:12.120> over<00:10:12.420> time 00:10:12.710 --> 00:10:12.720 align:start position:0% uses but it's become clear over time 00:10:12.720 --> 00:10:14.810 align:start position:0% uses but it's become clear over time that<00:10:13.019> ens<00:10:13.500> has<00:10:13.740> some<00:10:13.920> unique<00:10:14.220> requirements 00:10:14.810 --> 00:10:14.820 align:start position:0% that ens has some unique requirements 00:10:14.820 --> 00:10:17.690 align:start position:0% that ens has some unique requirements and<00:10:15.660> we<00:10:16.200> wanted<00:10:16.320> to<00:10:16.500> enable<00:10:16.740> things<00:10:17.100> such<00:10:17.519> as 00:10:17.690 --> 00:10:17.700 align:start position:0% and we wanted to enable things such as 00:10:17.700 --> 00:10:20.269 align:start position:0% and we wanted to enable things such as emoji<00:10:18.540> and<00:10:18.839> other<00:10:19.080> characters<00:10:19.380> that<00:10:20.040> are 00:10:20.269 --> 00:10:20.279 align:start position:0% emoji and other characters that are 00:10:20.279 --> 00:10:21.949 align:start position:0% emoji and other characters that are popular<00:10:20.580> in<00:10:20.880> the<00:10:21.060> community<00:10:21.180> but<00:10:21.720> not 00:10:21.949 --> 00:10:21.959 align:start position:0% popular in the community but not 00:10:21.959 --> 00:10:23.930 align:start position:0% popular in the community but not supported<00:10:22.380> directly<00:10:22.740> by<00:10:22.920> DNS 00:10:23.930 --> 00:10:23.940 align:start position:0% supported directly by DNS 00:10:23.940 --> 00:10:26.150 align:start position:0% supported directly by DNS uh<00:10:24.600> so<00:10:24.779> refi<00:10:25.320> has<00:10:25.560> been<00:10:25.680> working<00:10:25.920> on 00:10:26.150 --> 00:10:26.160 align:start position:0% uh so refi has been working on 00:10:26.160 --> 00:10:28.430 align:start position:0% uh so refi has been working on harmonizing<00:10:26.760> all<00:10:26.940> of<00:10:27.120> this<00:10:27.240> we're<00:10:28.019> very<00:10:28.200> close 00:10:28.430 --> 00:10:28.440 align:start position:0% harmonizing all of this we're very close 00:10:28.440 --> 00:10:29.870 align:start position:0% harmonizing all of this we're very close to<00:10:28.620> rolling<00:10:28.920> out<00:10:29.040> their<00:10:29.220> new<00:10:29.399> standard<00:10:29.700> for 00:10:29.870 --> 00:10:29.880 align:start position:0% to rolling out their new standard for 00:10:29.880 --> 00:10:32.210 align:start position:0% to rolling out their new standard for Dow<00:10:30.120> approval<00:10:30.600> and<00:10:31.200> it<00:10:31.320> will<00:10:31.440> enable<00:10:31.740> a<00:10:32.100> much 00:10:32.210 --> 00:10:32.220 align:start position:0% Dow approval and it will enable a much 00:10:32.220 --> 00:10:33.949 align:start position:0% Dow approval and it will enable a much wider<00:10:32.580> array<00:10:32.880> of<00:10:33.000> characters<00:10:33.180> while<00:10:33.660> also 00:10:33.949 --> 00:10:33.959 align:start position:0% wider array of characters while also 00:10:33.959 --> 00:10:35.509 align:start position:0% wider array of characters while also providing<00:10:34.320> more<00:10:34.560> protections<00:10:35.220> against 00:10:35.509 --> 00:10:35.519 align:start position:0% providing more protections against 00:10:35.519 --> 00:10:37.730 align:start position:0% providing more protections against deceptive<00:10:36.180> names 00:10:37.730 --> 00:10:37.740 align:start position:0% deceptive names 00:10:37.740 --> 00:10:40.490 align:start position:0% deceptive names the<00:10:38.700> last<00:10:38.820> three<00:10:39.060> years<00:10:39.300> has<00:10:39.600> also<00:10:39.899> seen<00:10:40.260> an 00:10:40.490 --> 00:10:40.500 align:start position:0% the last three years has also seen an 00:10:40.500 --> 00:10:42.410 align:start position:0% the last three years has also seen an explosion<00:10:40.980> in<00:10:41.220> community-led<00:10:41.880> ens 00:10:42.410 --> 00:10:42.420 align:start position:0% explosion in community-led ens 00:10:42.420 --> 00:10:45.650 align:start position:0% explosion in community-led ens initiatives<00:10:43.100> uh<00:10:44.100> independent<00:10:44.820> projects<00:10:45.360> that 00:10:45.650 --> 00:10:45.660 align:start position:0% initiatives uh independent projects that 00:10:45.660 --> 00:10:48.470 align:start position:0% initiatives uh independent projects that build<00:10:45.839> on<00:10:46.079> top<00:10:46.200> of<00:10:46.320> the<00:10:46.380> ens<00:10:46.740> ecosystem<00:10:47.480> one 00:10:48.470 --> 00:10:48.480 align:start position:0% build on top of the ens ecosystem one 00:10:48.480 --> 00:10:50.329 align:start position:0% build on top of the ens ecosystem one popular<00:10:48.720> example<00:10:49.200> you<00:10:49.380> may<00:10:49.560> have<00:10:49.680> seen<00:10:49.860> is<00:10:50.100> the 00:10:50.329 --> 00:10:50.339 align:start position:0% popular example you may have seen is the 00:10:50.339 --> 00:10:53.569 align:start position:0% popular example you may have seen is the ens<00:10:50.760> leaderboard<00:10:51.500> which<00:10:52.500> shows<00:10:52.920> people<00:10:53.399> with 00:10:53.569 --> 00:10:53.579 align:start position:0% ens leaderboard which shows people with 00:10:53.579 --> 00:10:56.269 align:start position:0% ens leaderboard which shows people with Twitter<00:10:53.820> handles<00:10:54.360> that<00:10:54.720> contain<00:10:55.019> Dot<00:10:55.380> eth<00:10:55.680> and 00:10:56.269 --> 00:10:56.279 align:start position:0% Twitter handles that contain Dot eth and 00:10:56.279 --> 00:10:57.970 align:start position:0% Twitter handles that contain Dot eth and their<00:10:56.519> ranking<00:10:56.940> relative<00:10:57.360> to<00:10:57.540> followers 00:10:57.970 --> 00:10:57.980 align:start position:0% their ranking relative to followers 00:10:57.980 --> 00:11:00.290 align:start position:0% their ranking relative to followers we've<00:10:58.980> had<00:10:59.100> some<00:10:59.339> pretty<00:10:59.579> popular<00:10:59.820> ones 00:11:00.290 --> 00:11:00.300 align:start position:0% we've had some pretty popular ones 00:11:00.300 --> 00:11:02.030 align:start position:0% we've had some pretty popular ones including<00:11:00.779> Paris<00:11:01.200> Hilton<00:11:01.500> for<00:11:01.800> instance 00:11:02.030 --> 00:11:02.040 align:start position:0% including Paris Hilton for instance 00:11:02.040 --> 00:11:04.190 align:start position:0% including Paris Hilton for instance right<00:11:02.339> up<00:11:02.579> the<00:11:02.700> top<00:11:02.820> of<00:11:02.880> the<00:11:03.000> leaderboard<00:11:03.360> I 00:11:04.190 --> 00:11:04.200 align:start position:0% right up the top of the leaderboard I 00:11:04.200 --> 00:11:05.870 align:start position:0% right up the top of the leaderboard I myself<00:11:04.380> am<00:11:04.860> now<00:11:05.040> ranked<00:11:05.339> I<00:11:05.519> don't<00:11:05.640> know<00:11:05.700> number 00:11:05.870 --> 00:11:05.880 align:start position:0% myself am now ranked I don't know number 00:11:05.880 --> 00:11:07.730 align:start position:0% myself am now ranked I don't know number 400<00:11:06.300> or<00:11:06.600> something 00:11:07.730 --> 00:11:07.740 align:start position:0% 400 or something 00:11:07.740 --> 00:11:08.389 align:start position:0% 400 or something um 00:11:08.389 --> 00:11:08.399 align:start position:0% um 00:11:08.399 --> 00:11:11.210 align:start position:0% um we've<00:11:09.360> uh<00:11:09.600> had<00:11:09.839> the<00:11:10.140> launch<00:11:10.320> of<00:11:10.500> ens<00:11:10.920> Vision 00:11:11.210 --> 00:11:11.220 align:start position:0% we've uh had the launch of ens Vision 00:11:11.220 --> 00:11:13.610 align:start position:0% we've uh had the launch of ens Vision which<00:11:11.700> is<00:11:11.820> a<00:11:12.120> third-party<00:11:12.720> ens<00:11:13.200> trading 00:11:13.610 --> 00:11:13.620 align:start position:0% which is a third-party ens trading 00:11:13.620 --> 00:11:14.470 align:start position:0% which is a third-party ens trading Market 00:11:14.470 --> 00:11:14.480 align:start position:0% Market 00:11:14.480 --> 00:11:17.509 align:start position:0% Market allows<00:11:15.480> people<00:11:15.660> to<00:11:16.140> now<00:11:16.380> register<00:11:16.860> names<00:11:17.160> from 00:11:17.509 --> 00:11:17.519 align:start position:0% allows people to now register names from 00:11:17.519 --> 00:11:20.470 align:start position:0% allows people to now register names from scratch<00:11:17.760> and<00:11:18.060> also<00:11:18.360> trade<00:11:18.660> existing<00:11:19.140> names 00:11:20.470 --> 00:11:20.480 align:start position:0% scratch and also trade existing names 00:11:20.480 --> 00:11:24.230 align:start position:0% scratch and also trade existing names and<00:11:21.480> projects<00:11:22.019> such<00:11:22.200> as<00:11:22.380> nimi<00:11:22.860> which<00:11:23.459> is<00:11:23.640> a<00:11:23.940> web 00:11:24.230 --> 00:11:24.240 align:start position:0% and projects such as nimi which is a web 00:11:24.240 --> 00:11:25.970 align:start position:0% and projects such as nimi which is a web 3<00:11:24.600> profile 00:11:25.970 --> 00:11:25.980 align:start position:0% 3 profile 00:11:25.980 --> 00:11:28.190 align:start position:0% 3 profile um site<00:11:26.820> it<00:11:27.300> lets<00:11:27.600> you<00:11:27.660> generate<00:11:28.079> a 00:11:28.190 --> 00:11:28.200 align:start position:0% um site it lets you generate a 00:11:28.200 --> 00:11:30.410 align:start position:0% um site it lets you generate a customized<00:11:28.740> profile<00:11:29.100> and<00:11:29.820> in<00:11:30.000> fact<00:11:30.120> the 00:11:30.410 --> 00:11:30.420 align:start position:0% customized profile and in fact the 00:11:30.420 --> 00:11:32.630 align:start position:0% customized profile and in fact the eth.limo<00:11:31.320> Gateway<00:11:31.680> folks<00:11:32.040> have<00:11:32.220> integrated 00:11:32.630 --> 00:11:32.640 align:start position:0% eth.limo Gateway folks have integrated 00:11:32.640 --> 00:11:34.910 align:start position:0% eth.limo Gateway folks have integrated with<00:11:32.820> nimi<00:11:33.300> so<00:11:33.779> if<00:11:33.899> you<00:11:34.019> have<00:11:34.140> an<00:11:34.260> ens<00:11:34.740> name 00:11:34.910 --> 00:11:34.920 align:start position:0% with nimi so if you have an ens name 00:11:34.920 --> 00:11:37.069 align:start position:0% with nimi so if you have an ens name that<00:11:35.160> doesn't<00:11:35.339> have<00:11:35.519> content<00:11:36.000> set<00:11:36.240> up<00:11:36.420> it<00:11:36.959> will 00:11:37.069 --> 00:11:37.079 align:start position:0% that doesn't have content set up it will 00:11:37.079 --> 00:11:39.230 align:start position:0% that doesn't have content set up it will automatically<00:11:37.680> show<00:11:38.100> your<00:11:38.459> profile<00:11:38.940> with 00:11:39.230 --> 00:11:39.240 align:start position:0% automatically show your profile with 00:11:39.240 --> 00:11:41.090 align:start position:0% automatically show your profile with your<00:11:39.420> pipes<00:11:39.959> and<00:11:40.079> so<00:11:40.200> forth<00:11:40.500> then<00:11:40.680> you<00:11:40.920> can 00:11:41.090 --> 00:11:41.100 align:start position:0% your pipes and so forth then you can 00:11:41.100 --> 00:11:43.490 align:start position:0% your pipes and so forth then you can customize<00:11:41.579> it<00:11:41.760> as<00:11:41.940> you<00:11:42.120> wish 00:11:43.490 --> 00:11:43.500 align:start position:0% customize it as you wish 00:11:43.500 --> 00:11:45.590 align:start position:0% customize it as you wish uh<00:11:44.160> before<00:11:44.399> we<00:11:44.640> start<00:11:44.760> talking<00:11:45.000> about<00:11:45.240> what's 00:11:45.590 --> 00:11:45.600 align:start position:0% uh before we start talking about what's 00:11:45.600 --> 00:11:48.410 align:start position:0% uh before we start talking about what's new<00:11:45.899> one<00:11:46.380> small<00:11:46.680> announcement<00:11:47.240> true<00:11:48.240> names 00:11:48.410 --> 00:11:48.420 align:start position:0% new one small announcement true names 00:11:48.420 --> 00:11:50.449 align:start position:0% new one small announcement true names limited<00:11:49.019> is<00:11:49.260> the<00:11:49.440> name<00:11:49.560> of<00:11:49.800> the<00:11:49.980> development 00:11:50.449 --> 00:11:50.459 align:start position:0% limited is the name of the development 00:11:50.459 --> 00:11:52.490 align:start position:0% limited is the name of the development company<00:11:50.700> that<00:11:51.060> builds<00:11:51.300> enes<00:11:51.779> the<00:11:52.079> company<00:11:52.260> I 00:11:52.490 --> 00:11:52.500 align:start position:0% company that builds enes the company I 00:11:52.500 --> 00:11:54.050 align:start position:0% company that builds enes the company I founded<00:11:52.920> that<00:11:53.100> gets<00:11:53.399> paid<00:11:53.519> by<00:11:53.700> the<00:11:53.880> Dow 00:11:54.050 --> 00:11:54.060 align:start position:0% founded that gets paid by the Dow 00:11:54.060 --> 00:11:57.170 align:start position:0% founded that gets paid by the Dow employees<00:11:54.779> about<00:11:55.440> dozen<00:11:56.040> of<00:11:56.220> us<00:11:56.339> to<00:11:56.700> build<00:11:56.880> our 00:11:57.170 --> 00:11:57.180 align:start position:0% employees about dozen of us to build our 00:11:57.180 --> 00:12:00.889 align:start position:0% employees about dozen of us to build our ens<00:11:57.980> when<00:11:58.980> we<00:11:59.160> formed<00:11:59.519> it<00:11:59.640> we<00:12:00.540> didn't<00:12:00.660> really 00:12:00.889 --> 00:12:00.899 align:start position:0% ens when we formed it we didn't really 00:12:00.899 --> 00:12:02.449 align:start position:0% ens when we formed it we didn't really think<00:12:01.140> of<00:12:01.320> it<00:12:01.440> as<00:12:01.620> a<00:12:01.800> name<00:12:01.920> that<00:12:02.160> would<00:12:02.339> be 00:12:02.449 --> 00:12:02.459 align:start position:0% think of it as a name that would be 00:12:02.459 --> 00:12:04.190 align:start position:0% think of it as a name that would be visible<00:12:02.880> to<00:12:03.060> people<00:12:03.240> that<00:12:03.480> was<00:12:03.660> purely<00:12:04.019> an 00:12:04.190 --> 00:12:04.200 align:start position:0% visible to people that was purely an 00:12:04.200 --> 00:12:07.009 align:start position:0% visible to people that was purely an internal<00:12:04.560> thing<00:12:04.800> but<00:12:05.640> in<00:12:06.180> the<00:12:06.300> intervening 00:12:07.009 --> 00:12:07.019 align:start position:0% internal thing but in the intervening 00:12:07.019 --> 00:12:08.750 align:start position:0% internal thing but in the intervening time<00:12:07.140> it's<00:12:07.560> become<00:12:07.980> more<00:12:08.160> and<00:12:08.279> more<00:12:08.459> visible 00:12:08.750 --> 00:12:08.760 align:start position:0% time it's become more and more visible 00:12:08.760 --> 00:12:11.389 align:start position:0% time it's become more and more visible and<00:12:09.720> every<00:12:09.899> time<00:12:10.140> we<00:12:10.440> have<00:12:10.560> to<00:12:10.680> say<00:12:10.860> we're<00:12:11.160> from 00:12:11.389 --> 00:12:11.399 align:start position:0% and every time we have to say we're from 00:12:11.399 --> 00:12:12.769 align:start position:0% and every time we have to say we're from True<00:12:11.579> names<00:12:11.760> limited<00:12:12.240> the<00:12:12.420> company<00:12:12.540> that 00:12:12.769 --> 00:12:12.779 align:start position:0% True names limited the company that 00:12:12.779 --> 00:12:14.810 align:start position:0% True names limited the company that develops<00:12:13.140> ens<00:12:13.560> and<00:12:13.800> it<00:12:13.920> gets<00:12:14.160> a<00:12:14.220> bit<00:12:14.279> tiresome 00:12:14.810 --> 00:12:14.820 align:start position:0% develops ens and it gets a bit tiresome 00:12:14.820 --> 00:12:17.750 align:start position:0% develops ens and it gets a bit tiresome so<00:12:15.480> we're<00:12:15.720> renaming<00:12:16.260> to<00:12:16.380> ens<00:12:16.860> Labs<00:12:17.220> limited<00:12:17.579> to 00:12:17.750 --> 00:12:17.760 align:start position:0% so we're renaming to ens Labs limited to 00:12:17.760 --> 00:12:20.389 align:start position:0% so we're renaming to ens Labs limited to better<00:12:17.880> reflect<00:12:18.420> what<00:12:19.079> we<00:12:19.200> do<00:12:19.320> and<00:12:19.440> Who<00:12:19.620> We<00:12:19.740> Are 00:12:20.389 --> 00:12:20.399 align:start position:0% better reflect what we do and Who We Are 00:12:20.399 --> 00:12:22.970 align:start position:0% better reflect what we do and Who We Are uh<00:12:21.000> so<00:12:21.240> what's<00:12:21.420> next<00:12:21.720> uh<00:12:22.380> first<00:12:22.620> we're<00:12:22.800> going 00:12:22.970 --> 00:12:22.980 align:start position:0% uh so what's next uh first we're going 00:12:22.980 --> 00:12:26.150 align:start position:0% uh so what's next uh first we're going to<00:12:23.100> talk<00:12:23.160> about<00:12:23.339> Thorin<00:12:24.360> Thorin<00:12:25.079> is<00:12:25.320> ens's<00:12:25.920> new 00:12:26.150 --> 00:12:26.160 align:start position:0% to talk about Thorin Thorin is ens's new 00:12:26.160 --> 00:12:28.009 align:start position:0% to talk about Thorin Thorin is ens's new design<00:12:26.339> system<00:12:26.700> and<00:12:27.300> it's<00:12:27.420> built<00:12:27.720> from<00:12:27.839> the 00:12:28.009 --> 00:12:28.019 align:start position:0% design system and it's built from the 00:12:28.019 --> 00:12:30.590 align:start position:0% design system and it's built from the ground<00:12:28.140> up<00:12:28.440> with<00:12:28.800> usability<00:12:29.339> and<00:12:29.760> web3<00:12:30.180> in 00:12:30.590 --> 00:12:30.600 align:start position:0% ground up with usability and web3 in 00:12:30.600 --> 00:12:32.690 align:start position:0% ground up with usability and web3 in mind<00:12:30.779> we've<00:12:31.440> used<00:12:31.620> it<00:12:31.800> to<00:12:31.980> completely<00:12:32.279> rewrite 00:12:32.690 --> 00:12:32.700 align:start position:0% mind we've used it to completely rewrite 00:12:32.700 --> 00:12:35.329 align:start position:0% mind we've used it to completely rewrite the<00:12:32.940> ens<00:12:33.360> app<00:12:33.540> from<00:12:33.779> the<00:12:33.899> ground<00:12:34.019> up<00:12:34.339> coupled 00:12:35.329 --> 00:12:35.339 align:start position:0% the ens app from the ground up coupled 00:12:35.339 --> 00:12:37.250 align:start position:0% the ens app from the ground up coupled with<00:12:35.459> improvements<00:12:36.120> to<00:12:36.300> the<00:12:36.540> smart<00:12:36.720> contracts 00:12:37.250 --> 00:12:37.260 align:start position:0% with improvements to the smart contracts 00:12:37.260 --> 00:12:39.530 align:start position:0% with improvements to the smart contracts behind<00:12:37.560> DNS<00:12:38.040> this<00:12:38.579> enables<00:12:39.120> a<00:12:39.300> huge 00:12:39.530 --> 00:12:39.540 align:start position:0% behind DNS this enables a huge 00:12:39.540 --> 00:12:42.430 align:start position:0% behind DNS this enables a huge Improvement<00:12:39.959> in<00:12:40.140> usability<00:12:40.560> for<00:12:40.980> ens<00:12:41.459> users 00:12:42.430 --> 00:12:42.440 align:start position:0% Improvement in usability for ens users 00:12:42.440 --> 00:12:45.470 align:start position:0% Improvement in usability for ens users the<00:12:43.440> ensui<00:12:44.279> faces<00:12:44.700> kind<00:12:45.000> of<00:12:45.060> a<00:12:45.240> unique 00:12:45.470 --> 00:12:45.480 align:start position:0% the ensui faces kind of a unique 00:12:45.480 --> 00:12:48.230 align:start position:0% the ensui faces kind of a unique Challenge<00:12:45.839> from<00:12:46.380> amongst<00:12:46.920> web3<00:12:47.459> apps<00:12:47.880> and<00:12:48.060> in 00:12:48.230 --> 00:12:48.240 align:start position:0% Challenge from amongst web3 apps and in 00:12:48.240 --> 00:12:50.810 align:start position:0% Challenge from amongst web3 apps and in fact<00:12:48.360> kind<00:12:48.660> of<00:12:48.779> apps<00:12:49.079> in<00:12:49.200> general<00:12:49.380> in<00:12:50.160> that<00:12:50.339> it 00:12:50.810 --> 00:12:50.820 align:start position:0% fact kind of apps in general in that it 00:12:50.820 --> 00:12:52.550 align:start position:0% fact kind of apps in general in that it needs<00:12:51.060> to<00:12:51.120> provide<00:12:51.420> an<00:12:51.600> interface<00:12:52.019> that<00:12:52.380> is 00:12:52.550 --> 00:12:52.560 align:start position:0% needs to provide an interface that is 00:12:52.560 --> 00:12:54.829 align:start position:0% needs to provide an interface that is both<00:12:52.860> easy<00:12:53.519> and<00:12:53.760> user-friendly<00:12:54.420> for<00:12:54.660> new 00:12:54.829 --> 00:12:54.839 align:start position:0% both easy and user-friendly for new 00:12:54.839 --> 00:12:57.410 align:start position:0% both easy and user-friendly for new users<00:12:55.200> but<00:12:55.800> has<00:12:56.040> the<00:12:56.339> advanced<00:12:56.700> levers<00:12:57.240> and 00:12:57.410 --> 00:12:57.420 align:start position:0% users but has the advanced levers and 00:12:57.420 --> 00:12:59.930 align:start position:0% users but has the advanced levers and and<00:12:57.740> sophisticated<00:12:58.740> interaction<00:12:59.279> required 00:12:59.930 --> 00:12:59.940 align:start position:0% and sophisticated interaction required 00:12:59.940 --> 00:13:01.910 align:start position:0% and sophisticated interaction required by<00:13:00.120> Advanced<00:13:00.540> users<00:13:00.899> we<00:13:01.500> don't<00:13:01.620> want<00:13:01.800> to 00:13:01.910 --> 00:13:01.920 align:start position:0% by Advanced users we don't want to 00:13:01.920 --> 00:13:04.370 align:start position:0% by Advanced users we don't want to create<00:13:02.040> a<00:13:02.339> situation<00:13:02.760> where<00:13:03.240> the<00:13:04.079> app<00:13:04.200> is 00:13:04.370 --> 00:13:04.380 align:start position:0% create a situation where the app is 00:13:04.380 --> 00:13:05.810 align:start position:0% create a situation where the app is sufficiently<00:13:04.860> flexible<00:13:05.279> to<00:13:05.519> do<00:13:05.639> anything 00:13:05.810 --> 00:13:05.820 align:start position:0% sufficiently flexible to do anything 00:13:05.820 --> 00:13:08.629 align:start position:0% sufficiently flexible to do anything with<00:13:06.060> ens<00:13:06.600> but<00:13:07.139> deters<00:13:07.620> existing<00:13:08.040> users<00:13:08.399> which 00:13:08.629 --> 00:13:08.639 align:start position:0% with ens but deters existing users which 00:13:08.639 --> 00:13:09.829 align:start position:0% with ens but deters existing users which is<00:13:08.760> a<00:13:08.940> little<00:13:09.000> bit<00:13:09.120> the<00:13:09.300> case<00:13:09.420> in<00:13:09.600> the<00:13:09.720> current 00:13:09.829 --> 00:13:09.839 align:start position:0% is a little bit the case in the current 00:13:09.839 --> 00:13:12.110 align:start position:0% is a little bit the case in the current APP<00:13:10.139> or<00:13:11.040> is<00:13:11.279> so<00:13:11.459> straightforward<00:13:11.940> and 00:13:12.110 --> 00:13:12.120 align:start position:0% APP or is so straightforward and 00:13:12.120 --> 00:13:13.610 align:start position:0% APP or is so straightforward and wizard-based<00:13:12.839> that<00:13:13.079> you<00:13:13.260> need<00:13:13.380> to<00:13:13.500> go 00:13:13.610 --> 00:13:13.620 align:start position:0% wizard-based that you need to go 00:13:13.620 --> 00:13:15.230 align:start position:0% wizard-based that you need to go somewhere<00:13:13.980> else<00:13:14.100> if<00:13:14.459> you<00:13:14.579> do<00:13:14.700> have<00:13:14.940> more<00:13:15.120> than 00:13:15.230 --> 00:13:15.240 align:start position:0% somewhere else if you do have more than 00:13:15.240 --> 00:13:16.550 align:start position:0% somewhere else if you do have more than basic<00:13:15.600> needs 00:13:16.550 --> 00:13:16.560 align:start position:0% basic needs 00:13:16.560 --> 00:13:19.129 align:start position:0% basic needs by<00:13:17.519> surfacing<00:13:18.000> the<00:13:18.120> important<00:13:18.480> details<00:13:18.959> and 00:13:19.129 --> 00:13:19.139 align:start position:0% by surfacing the important details and 00:13:19.139 --> 00:13:21.230 align:start position:0% by surfacing the important details and flows<00:13:19.500> while<00:13:20.160> still<00:13:20.459> making<00:13:20.639> Advanced 00:13:21.230 --> 00:13:21.240 align:start position:0% flows while still making Advanced 00:13:21.240 --> 00:13:22.990 align:start position:0% flows while still making Advanced functionality<00:13:21.779> available<00:13:22.019> under<00:13:22.440> the<00:13:22.620> covers 00:13:22.990 --> 00:13:23.000 align:start position:0% functionality available under the covers 00:13:23.000 --> 00:13:25.069 align:start position:0% functionality available under the covers the<00:13:24.000> front-end<00:13:24.360> team<00:13:24.600> have<00:13:24.779> done<00:13:24.899> an 00:13:25.069 --> 00:13:25.079 align:start position:0% the front-end team have done an 00:13:25.079 --> 00:13:26.930 align:start position:0% the front-end team have done an outstanding<00:13:25.500> job<00:13:25.740> of<00:13:25.920> writing<00:13:26.339> an<00:13:26.459> app<00:13:26.639> that 00:13:26.930 --> 00:13:26.940 align:start position:0% outstanding job of writing an app that 00:13:26.940 --> 00:13:29.389 align:start position:0% outstanding job of writing an app that is<00:13:27.839> all<00:13:28.019> for<00:13:28.200> all<00:13:28.380> users 00:13:29.389 --> 00:13:29.399 align:start position:0% is all for all users 00:13:29.399 --> 00:13:31.190 align:start position:0% is all for all users aside<00:13:29.940> from<00:13:30.120> the<00:13:30.300> functional<00:13:30.660> improvements 00:13:31.190 --> 00:13:31.200 align:start position:0% aside from the functional improvements 00:13:31.200 --> 00:13:33.050 align:start position:0% aside from the functional improvements we've<00:13:31.740> hugely<00:13:31.980> improved<00:13:32.399> the<00:13:32.519> loading<00:13:32.880> times 00:13:33.050 --> 00:13:33.060 align:start position:0% we've hugely improved the loading times 00:13:33.060 --> 00:13:36.310 align:start position:0% we've hugely improved the loading times and<00:13:33.899> made<00:13:34.139> the<00:13:34.380> new<00:13:34.440> app<00:13:34.620> 100<00:13:34.860> mobile<00:13:35.519> friendly 00:13:36.310 --> 00:13:36.320 align:start position:0% and made the new app 100 mobile friendly 00:13:36.320 --> 00:13:39.290 align:start position:0% and made the new app 100 mobile friendly the<00:13:37.320> new<00:13:37.440> app<00:13:37.620> is<00:13:37.800> at<00:13:38.040> feature<00:13:38.399> parity<00:13:38.700> and 00:13:39.290 --> 00:13:39.300 align:start position:0% the new app is at feature parity and 00:13:39.300 --> 00:13:41.690 align:start position:0% the new app is at feature parity and live<00:13:39.480> now<00:13:39.720> on<00:13:39.899> the<00:13:40.019> girly<00:13:40.320> test<00:13:40.500> net<00:13:40.680> would<00:13:41.579> be 00:13:41.690 --> 00:13:41.700 align:start position:0% live now on the girly test net would be 00:13:41.700 --> 00:13:43.129 align:start position:0% live now on the girly test net would be live<00:13:41.820> on<00:13:42.000> robston<00:13:42.420> but<00:13:42.600> that's<00:13:42.779> already<00:13:42.959> been 00:13:43.129 --> 00:13:43.139 align:start position:0% live on robston but that's already been 00:13:43.139 --> 00:13:44.410 align:start position:0% live on robston but that's already been deprecated 00:13:44.410 --> 00:13:44.420 align:start position:0% deprecated 00:13:44.420 --> 00:13:47.810 align:start position:0% deprecated and<00:13:45.420> you<00:13:45.959> can<00:13:46.079> try<00:13:46.200> it<00:13:46.320> out<00:13:46.440> now<00:13:46.620> at<00:13:46.820> alpha.eds 00:13:47.810 --> 00:13:47.820 align:start position:0% and you can try it out now at alpha.eds 00:13:47.820 --> 00:13:50.750 align:start position:0% and you can try it out now at alpha.eds domains<00:13:48.500> just<00:13:49.500> to<00:13:49.680> emphasize<00:13:50.100> it's<00:13:50.399> only<00:13:50.579> on 00:13:50.750 --> 00:13:50.760 align:start position:0% domains just to emphasize it's only on 00:13:50.760 --> 00:13:53.629 align:start position:0% domains just to emphasize it's only on girly<00:13:51.120> it<00:13:51.480> is<00:13:51.600> a<00:13:51.779> little<00:13:51.899> bit<00:13:52.160> you<00:13:53.160> know<00:13:53.220> sharp 00:13:53.629 --> 00:13:53.639 align:start position:0% girly it is a little bit you know sharp 00:13:53.639 --> 00:13:56.210 align:start position:0% girly it is a little bit you know sharp edges<00:13:54.000> still<00:13:54.240> the<00:13:55.139> team<00:13:55.260> really<00:13:55.560> raced<00:13:55.980> to<00:13:56.100> get 00:13:56.210 --> 00:13:56.220 align:start position:0% edges still the team really raced to get 00:13:56.220 --> 00:13:58.430 align:start position:0% edges still the team really raced to get it<00:13:56.339> out<00:13:56.459> in<00:13:56.700> time<00:13:56.940> and<00:13:57.600> did<00:13:57.720> an<00:13:57.899> amazing<00:13:58.200> job 00:13:58.430 --> 00:13:58.440 align:start position:0% it out in time and did an amazing job 00:13:58.440 --> 00:14:01.670 align:start position:0% it out in time and did an amazing job please<00:13:59.399> send<00:13:59.700> us<00:13:59.940> your<00:14:00.480> bug<00:14:00.720> reports<00:14:01.200> but<00:14:01.500> we 00:14:01.670 --> 00:14:01.680 align:start position:0% please send us your bug reports but we 00:14:01.680 --> 00:14:04.129 align:start position:0% please send us your bug reports but we aim<00:14:01.980> to<00:14:02.040> have<00:14:02.220> this<00:14:02.579> launch<00:14:03.540> on<00:14:03.720> Main<00:14:03.899> net 00:14:04.129 --> 00:14:04.139 align:start position:0% aim to have this launch on Main net 00:14:04.139 --> 00:14:06.470 align:start position:0% aim to have this launch on Main net shortly<00:14:04.500> after<00:14:04.680> Devcon<00:14:05.279> once<00:14:06.180> the<00:14:06.300> name 00:14:06.470 --> 00:14:06.480 align:start position:0% shortly after Devcon once the name 00:14:06.480 --> 00:14:08.150 align:start position:0% shortly after Devcon once the name wrapper<00:14:06.959> and<00:14:07.079> other<00:14:07.260> contracts<00:14:07.740> are<00:14:07.860> approved 00:14:08.150 --> 00:14:08.160 align:start position:0% wrapper and other contracts are approved 00:14:08.160 --> 00:14:10.490 align:start position:0% wrapper and other contracts are approved by<00:14:08.279> the<00:14:08.459> Dow<00:14:08.700> as<00:14:09.060> I'll<00:14:09.240> discuss<00:14:09.540> shortly<00:14:09.899> so 00:14:10.490 --> 00:14:10.500 align:start position:0% by the Dow as I'll discuss shortly so 00:14:10.500 --> 00:14:12.470 align:start position:0% by the Dow as I'll discuss shortly so keep<00:14:10.740> your<00:14:10.860> eyes<00:14:10.980> peeled 00:14:12.470 --> 00:14:12.480 align:start position:0% keep your eyes peeled 00:14:12.480 --> 00:14:15.290 align:start position:0% keep your eyes peeled Thorin<00:14:13.260> isn't<00:14:13.560> just<00:14:13.740> for<00:14:13.920> ens<00:14:14.399> either<00:14:14.760> we've 00:14:15.290 --> 00:14:15.300 align:start position:0% Thorin isn't just for ens either we've 00:14:15.300 --> 00:14:17.090 align:start position:0% Thorin isn't just for ens either we've made<00:14:15.600> it<00:14:15.779> available<00:14:15.959> as<00:14:16.320> a<00:14:16.500> standard<00:14:16.800> react 00:14:17.090 --> 00:14:17.100 align:start position:0% made it available as a standard react 00:14:17.100 --> 00:14:18.829 align:start position:0% made it available as a standard react library<00:14:17.339> that<00:14:17.760> anyone<00:14:18.120> can<00:14:18.300> use<00:14:18.420> for<00:14:18.720> their 00:14:18.829 --> 00:14:18.839 align:start position:0% library that anyone can use for their 00:14:18.839 --> 00:14:21.230 align:start position:0% library that anyone can use for their web<00:14:18.959> 3<00:14:19.200> apps<00:14:19.620> you<00:14:20.459> can<00:14:20.579> check<00:14:20.700> it<00:14:20.880> out<00:14:21.000> on 00:14:21.230 --> 00:14:21.240 align:start position:0% web 3 apps you can check it out on 00:14:21.240 --> 00:14:23.870 align:start position:0% web 3 apps you can check it out on sauron.ens<00:14:22.019> domains<00:14:22.740> and<00:14:23.519> you<00:14:23.639> may<00:14:23.760> have 00:14:23.870 --> 00:14:23.880 align:start position:0% sauron.ens domains and you may have 00:14:23.880 --> 00:14:25.550 align:start position:0% sauron.ens domains and you may have noticed<00:14:24.180> it<00:14:24.360> powering<00:14:24.779> a<00:14:24.899> number<00:14:25.019> of<00:14:25.260> our 00:14:25.550 --> 00:14:25.560 align:start position:0% noticed it powering a number of our 00:14:25.560 --> 00:14:28.750 align:start position:0% noticed it powering a number of our other<00:14:26.040> sites<00:14:26.459> such<00:14:26.639> as<00:14:26.820> the<00:14:27.120> swag<00:14:27.620> microsite 00:14:28.750 --> 00:14:28.760 align:start position:0% other sites such as the swag microsite 00:14:28.760 --> 00:14:30.829 align:start position:0% other sites such as the swag microsite and<00:14:29.760> so<00:14:29.880> forth 00:14:30.829 --> 00:14:30.839 align:start position:0% and so forth 00:14:30.839 --> 00:14:33.829 align:start position:0% and so forth one<00:14:31.680> of<00:14:31.800> our<00:14:31.920> major<00:14:32.160> ongoing<00:14:32.700> projects<00:14:33.300> is 00:14:33.829 --> 00:14:33.839 align:start position:0% one of our major ongoing projects is 00:14:33.839 --> 00:14:36.769 align:start position:0% one of our major ongoing projects is scaling<00:14:34.260> ens<00:14:34.740> for<00:14:35.700> many<00:14:35.820> projects<00:14:36.420> this<00:14:36.660> is 00:14:36.769 --> 00:14:36.779 align:start position:0% scaling ens for many projects this is 00:14:36.779 --> 00:14:38.150 align:start position:0% scaling ens for many projects this is accomplished<00:14:37.139> by<00:14:37.320> going<00:14:37.500> multi-chain 00:14:38.150 --> 00:14:38.160 align:start position:0% accomplished by going multi-chain 00:14:38.160 --> 00:14:40.129 align:start position:0% accomplished by going multi-chain deploying<00:14:38.700> to<00:14:38.880> just<00:14:39.060> multiple<00:14:39.420> chains<00:14:39.839> if 00:14:40.129 --> 00:14:40.139 align:start position:0% deploying to just multiple chains if 00:14:40.139 --> 00:14:42.350 align:start position:0% deploying to just multiple chains if you're<00:14:40.260> uniswap<00:14:40.920> for<00:14:41.160> instance<00:14:41.399> you<00:14:41.940> fragment 00:14:42.350 --> 00:14:42.360 align:start position:0% you're uniswap for instance you fragment 00:14:42.360 --> 00:14:46.009 align:start position:0% you're uniswap for instance you fragment your<00:14:42.680> liquidity<00:14:43.680> a<00:14:43.920> bit<00:14:44.040> but<00:14:44.579> you<00:14:44.760> can<00:14:44.880> work<00:14:45.180> in 00:14:46.009 --> 00:14:46.019 align:start position:0% your liquidity a bit but you can work in 00:14:46.019 --> 00:14:48.590 align:start position:0% your liquidity a bit but you can work in parallel<00:14:46.380> across<00:14:46.680> multiple<00:14:47.040> chains<00:14:47.459> ens<00:14:48.360> is 00:14:48.590 --> 00:14:48.600 align:start position:0% parallel across multiple chains ens is 00:14:48.600 --> 00:14:50.509 align:start position:0% parallel across multiple chains ens is in<00:14:48.779> kind<00:14:48.899> of<00:14:49.019> a<00:14:49.139> unique<00:14:49.320> position<00:14:49.560> here<00:14:49.980> we 00:14:50.509 --> 00:14:50.519 align:start position:0% in kind of a unique position here we 00:14:50.519 --> 00:14:52.370 align:start position:0% in kind of a unique position here we need<00:14:50.639> to<00:14:50.760> maintain<00:14:51.180> a<00:14:51.600> single<00:14:51.899> cohesive 00:14:52.370 --> 00:14:52.380 align:start position:0% need to maintain a single cohesive 00:14:52.380 --> 00:14:54.710 align:start position:0% need to maintain a single cohesive registry<00:14:52.800> of<00:14:52.980> names<00:14:53.220> and<00:14:53.940> it's<00:14:54.120> far<00:14:54.360> too<00:14:54.540> early 00:14:54.710 --> 00:14:54.720 align:start position:0% registry of names and it's far too early 00:14:54.720 --> 00:14:57.650 align:start position:0% registry of names and it's far too early in<00:14:55.019> the<00:14:55.199> L2<00:14:55.680> and<00:14:55.980> the<00:14:56.160> roll-up<00:14:56.459> ecosystem<00:14:57.000> to 00:14:57.650 --> 00:14:57.660 align:start position:0% in the L2 and the roll-up ecosystem to 00:14:57.660 --> 00:14:59.449 align:start position:0% in the L2 and the roll-up ecosystem to pick<00:14:57.779> a<00:14:57.959> single<00:14:58.320> Service<00:14:58.500> as<00:14:58.860> the<00:14:59.040> winner<00:14:59.220> that 00:14:59.449 --> 00:14:59.459 align:start position:0% pick a single Service as the winner that 00:14:59.459 --> 00:15:02.210 align:start position:0% pick a single Service as the winner that we're<00:14:59.579> going<00:14:59.760> to<00:14:59.880> migrate<00:15:00.300> to<00:15:00.680> instead<00:15:01.680> we've 00:15:02.210 --> 00:15:02.220 align:start position:0% we're going to migrate to instead we've 00:15:02.220 --> 00:15:03.889 align:start position:0% we're going to migrate to instead we've been<00:15:02.339> pursuing<00:15:02.760> options<00:15:03.180> that<00:15:03.540> make<00:15:03.720> it 00:15:03.889 --> 00:15:03.899 align:start position:0% been pursuing options that make it 00:15:03.899 --> 00:15:05.689 align:start position:0% been pursuing options that make it possible<00:15:04.139> for<00:15:04.440> people<00:15:04.560> to<00:15:04.860> host<00:15:04.980> their<00:15:05.279> ens 00:15:05.689 --> 00:15:05.699 align:start position:0% possible for people to host their ens 00:15:05.699 --> 00:15:07.790 align:start position:0% possible for people to host their ens names<00:15:06.000> anywhere<00:15:06.540> without<00:15:07.139> the<00:15:07.440> resolving 00:15:07.790 --> 00:15:07.800 align:start position:0% names anywhere without the resolving 00:15:07.800 --> 00:15:10.610 align:start position:0% names anywhere without the resolving having<00:15:08.040> to<00:15:08.339> know<00:15:08.579> or<00:15:08.880> care<00:15:09.060> where<00:15:09.360> that<00:15:09.540> is 00:15:10.610 --> 00:15:10.620 align:start position:0% having to know or care where that is 00:15:10.620 --> 00:15:13.430 align:start position:0% having to know or care where that is earlier<00:15:11.339> this<00:15:11.639> year<00:15:11.820> we<00:15:12.180> launched<00:15:12.480> ccip<00:15:13.019> read 00:15:13.430 --> 00:15:13.440 align:start position:0% earlier this year we launched ccip read 00:15:13.440 --> 00:15:15.710 align:start position:0% earlier this year we launched ccip read as<00:15:13.800> a<00:15:13.980> collaboration<00:15:14.399> between<00:15:14.760> ens<00:15:15.360> and<00:15:15.600> chain 00:15:15.710 --> 00:15:15.720 align:start position:0% as a collaboration between ens and chain 00:15:15.720 --> 00:15:16.910 align:start position:0% as a collaboration between ens and chain link 00:15:16.910 --> 00:15:16.920 align:start position:0% link 00:15:16.920 --> 00:15:19.370 align:start position:0% link while<00:15:17.399> previous<00:15:17.699> systems<00:15:18.360> such<00:15:18.720> as<00:15:18.839> bridging 00:15:19.370 --> 00:15:19.380 align:start position:0% while previous systems such as bridging 00:15:19.380 --> 00:15:21.410 align:start position:0% while previous systems such as bridging often<00:15:19.980> introduced<00:15:20.399> new<00:15:20.639> trust<00:15:20.940> assumptions 00:15:21.410 --> 00:15:21.420 align:start position:0% often introduced new trust assumptions 00:15:21.420 --> 00:15:24.230 align:start position:0% often introduced new trust assumptions and<00:15:22.079> require<00:15:22.320> L1<00:15:22.920> transactions<00:15:23.639> to<00:15:23.820> execute 00:15:24.230 --> 00:15:24.240 align:start position:0% and require L1 transactions to execute 00:15:24.240 --> 00:15:27.050 align:start position:0% and require L1 transactions to execute ccip<00:15:25.139> read<00:15:25.500> uses<00:15:25.920> a<00:15:26.100> lower<00:15:26.220> level<00:15:26.459> primitive 00:15:27.050 --> 00:15:27.060 align:start position:0% ccip read uses a lower level primitive 00:15:27.060 --> 00:15:29.389 align:start position:0% ccip read uses a lower level primitive proofs<00:15:27.660> which<00:15:28.199> means<00:15:28.500> that<00:15:28.680> in<00:15:28.860> many<00:15:29.040> cases 00:15:29.389 --> 00:15:29.399 align:start position:0% proofs which means that in many cases 00:15:29.399 --> 00:15:31.910 align:start position:0% proofs which means that in many cases such<00:15:29.760> as<00:15:29.880> with<00:15:30.120> l2s<00:15:30.839> this<00:15:31.320> can<00:15:31.500> be<00:15:31.560> done<00:15:31.740> with 00:15:31.910 --> 00:15:31.920 align:start position:0% such as with l2s this can be done with 00:15:31.920 --> 00:15:33.769 align:start position:0% such as with l2s this can be done with no<00:15:32.160> additional<00:15:32.579> trust<00:15:32.940> assumptions<00:15:33.420> over 00:15:33.769 --> 00:15:33.779 align:start position:0% no additional trust assumptions over 00:15:33.779 --> 00:15:36.410 align:start position:0% no additional trust assumptions over those<00:15:34.019> the<00:15:34.199> L2<00:15:34.560> itself<00:15:34.920> requires<00:15:35.519> meaning<00:15:36.120> you 00:15:36.410 --> 00:15:36.420 align:start position:0% those the L2 itself requires meaning you 00:15:36.420 --> 00:15:38.210 align:start position:0% those the L2 itself requires meaning you could<00:15:36.540> host<00:15:36.720> your<00:15:36.899> ens<00:15:37.380> name<00:15:37.560> on<00:15:37.740> optimism 00:15:38.210 --> 00:15:38.220 align:start position:0% could host your ens name on optimism 00:15:38.220 --> 00:15:40.790 align:start position:0% could host your ens name on optimism have<00:15:38.820> users<00:15:39.240> resolve<00:15:39.779> it<00:15:39.839> from<00:15:40.139> any<00:15:40.440> client 00:15:40.790 --> 00:15:40.800 align:start position:0% have users resolve it from any client 00:15:40.800 --> 00:15:42.310 align:start position:0% have users resolve it from any client that<00:15:41.100> doesn't<00:15:41.220> know<00:15:41.399> what<00:15:41.579> optimism<00:15:42.060> is 00:15:42.310 --> 00:15:42.320 align:start position:0% that doesn't know what optimism is 00:15:42.320 --> 00:15:45.110 align:start position:0% that doesn't know what optimism is without<00:15:43.320> introducing<00:15:44.040> any<00:15:44.279> additional<00:15:44.699> trust 00:15:45.110 --> 00:15:45.120 align:start position:0% without introducing any additional trust 00:15:45.120 --> 00:15:47.569 align:start position:0% without introducing any additional trust that<00:15:45.540> relies<00:15:46.139> on<00:15:46.320> the<00:15:46.440> Gateway<00:15:46.740> operator<00:15:47.160> for 00:15:47.569 --> 00:15:47.579 align:start position:0% that relies on the Gateway operator for 00:15:47.579 --> 00:15:50.150 align:start position:0% that relies on the Gateway operator for instance<00:15:48.300> now<00:15:48.899> further<00:15:49.380> the<00:15:49.560> solutions<00:15:49.860> far 00:15:50.150 --> 00:15:50.160 align:start position:0% instance now further the solutions far 00:15:50.160 --> 00:15:52.069 align:start position:0% instance now further the solutions far more<00:15:50.339> flexible<00:15:50.760> than<00:15:50.940> bridging<00:15:51.420> allowing 00:15:52.069 --> 00:15:52.079 align:start position:0% more flexible than bridging allowing 00:15:52.079 --> 00:15:54.590 align:start position:0% more flexible than bridging allowing data<00:15:52.440> to<00:15:52.560> be<00:15:52.680> stored<00:15:53.040> not<00:15:53.279> just<00:15:53.459> on<00:15:53.699> l2s<00:15:54.420> or 00:15:54.590 --> 00:15:54.600 align:start position:0% data to be stored not just on l2s or 00:15:54.600 --> 00:15:56.629 align:start position:0% data to be stored not just on l2s or side<00:15:54.779> chains<00:15:55.199> but<00:15:55.380> on<00:15:55.560> arbitrary<00:15:56.100> systems 00:15:56.629 --> 00:15:56.639 align:start position:0% side chains but on arbitrary systems 00:15:56.639 --> 00:15:59.389 align:start position:0% side chains but on arbitrary systems including<00:15:57.120> centralized<00:15:57.600> databases 00:15:59.389 --> 00:15:59.399 align:start position:0% including centralized databases 00:15:59.399 --> 00:16:02.030 align:start position:0% including centralized databases at<00:15:59.760> its<00:16:00.060> core<00:16:00.180> enes<00:16:01.079> is<00:16:01.260> a<00:16:01.440> way<00:16:01.500> for<00:16:01.740> any 00:16:02.030 --> 00:16:02.040 align:start position:0% at its core enes is a way for any 00:16:02.040 --> 00:16:04.370 align:start position:0% at its core enes is a way for any contracts<00:16:02.639> to<00:16:02.880> fetch<00:16:03.180> data<00:16:03.540> from<00:16:03.839> off-chain 00:16:04.370 --> 00:16:04.380 align:start position:0% contracts to fetch data from off-chain 00:16:04.380 --> 00:16:06.829 align:start position:0% contracts to fetch data from off-chain resources<00:16:04.980> because<00:16:05.760> contracts<00:16:06.600> can't 00:16:06.829 --> 00:16:06.839 align:start position:0% resources because contracts can't 00:16:06.839 --> 00:16:09.949 align:start position:0% resources because contracts can't directly<00:16:07.320> talk<00:16:07.560> HTTP<00:16:08.100> requests<00:16:08.820> this<00:16:09.540> ends<00:16:09.899> up 00:16:09.949 --> 00:16:09.959 align:start position:0% directly talk HTTP requests this ends up 00:16:09.959 --> 00:16:11.629 align:start position:0% directly talk HTTP requests this ends up being<00:16:10.139> a<00:16:10.380> little<00:16:10.500> bit<00:16:10.680> like<00:16:10.920> having<00:16:11.279> one<00:16:11.519> of 00:16:11.629 --> 00:16:11.639 align:start position:0% being a little bit like having one of 00:16:11.639 --> 00:16:14.269 align:start position:0% being a little bit like having one of those<00:16:11.760> conversations<00:16:12.560> with<00:16:13.560> a<00:16:13.740> couple<00:16:13.860> who 00:16:14.269 --> 00:16:14.279 align:start position:0% those conversations with a couple who 00:16:14.279 --> 00:16:15.949 align:start position:0% those conversations with a couple who have<00:16:14.339> had<00:16:14.519> a<00:16:14.639> fight<00:16:14.820> and<00:16:15.060> refusing<00:16:15.540> to<00:16:15.660> talk<00:16:15.779> to 00:16:15.949 --> 00:16:15.959 align:start position:0% have had a fight and refusing to talk to 00:16:15.959 --> 00:16:17.870 align:start position:0% have had a fight and refusing to talk to each<00:16:16.079> other<00:16:16.199> well<00:16:16.860> you<00:16:17.220> tell<00:16:17.399> the<00:16:17.579> Gateway 00:16:17.870 --> 00:16:17.880 align:start position:0% each other well you tell the Gateway 00:16:17.880 --> 00:16:19.610 align:start position:0% each other well you tell the Gateway that<00:16:18.300> I<00:16:18.480> think<00:16:18.720> that<00:16:18.959> they<00:16:19.139> should<00:16:19.320> give<00:16:19.500> you 00:16:19.610 --> 00:16:19.620 align:start position:0% that I think that they should give you 00:16:19.620 --> 00:16:22.069 align:start position:0% that I think that they should give you this<00:16:19.860> data<00:16:20.279> I<00:16:20.459> need<00:16:20.639> so<00:16:21.360> the<00:16:21.600> conversation 00:16:22.069 --> 00:16:22.079 align:start position:0% this data I need so the conversation 00:16:22.079 --> 00:16:25.790 align:start position:0% this data I need so the conversation tends<00:16:22.620> to<00:16:22.680> go<00:16:22.920> like<00:16:23.639> that<00:16:24.139> unfortunately<00:16:25.139> just 00:16:25.790 --> 00:16:25.800 align:start position:0% tends to go like that unfortunately just 00:16:25.800 --> 00:16:27.889 align:start position:0% tends to go like that unfortunately just ask<00:16:25.980> them<00:16:26.220> yourself<00:16:26.459> isn't<00:16:26.940> an<00:16:27.120> option<00:16:27.360> so<00:16:27.720> the 00:16:27.889 --> 00:16:27.899 align:start position:0% ask them yourself isn't an option so the 00:16:27.899 --> 00:16:29.389 align:start position:0% ask them yourself isn't an option so the client<00:16:28.139> has<00:16:28.440> no<00:16:28.680> choice<00:16:28.860> but<00:16:29.100> to<00:16:29.279> play 00:16:29.389 --> 00:16:29.399 align:start position:0% client has no choice but to play 00:16:29.399 --> 00:16:32.269 align:start position:0% client has no choice but to play middleman<00:16:29.880> the<00:16:30.540> end<00:16:30.660> result<00:16:30.839> is<00:16:31.139> good<00:16:31.380> with 00:16:32.269 --> 00:16:32.279 align:start position:0% middleman the end result is good with 00:16:32.279 --> 00:16:34.009 align:start position:0% middleman the end result is good with the<00:16:32.459> resolver<00:16:32.880> and<00:16:33.060> the<00:16:33.180> Gateway<00:16:33.420> agreeing<00:16:33.839> on 00:16:34.009 --> 00:16:34.019 align:start position:0% the resolver and the Gateway agreeing on 00:16:34.019 --> 00:16:36.110 align:start position:0% the resolver and the Gateway agreeing on a<00:16:34.139> protocol<00:16:34.380> it's<00:16:35.040> possible<00:16:35.399> for<00:16:35.639> the<00:16:35.820> client 00:16:36.110 --> 00:16:36.120 align:start position:0% a protocol it's possible for the client 00:16:36.120 --> 00:16:38.749 align:start position:0% a protocol it's possible for the client to<00:16:36.420> facilitate<00:16:36.959> a<00:16:37.199> lookup<00:16:37.620> of<00:16:37.800> off-chain<00:16:38.279> data 00:16:38.749 --> 00:16:38.759 align:start position:0% to facilitate a lookup of off-chain data 00:16:38.759 --> 00:16:40.550 align:start position:0% to facilitate a lookup of off-chain data without<00:16:39.300> any<00:16:39.720> knowledge<00:16:40.079> of<00:16:40.259> what<00:16:40.440> their 00:16:40.550 --> 00:16:40.560 align:start position:0% without any knowledge of what their 00:16:40.560 --> 00:16:42.949 align:start position:0% without any knowledge of what their shared<00:16:40.980> languages<00:16:41.279> or<00:16:42.120> what<00:16:42.300> the<00:16:42.480> off-chain 00:16:42.949 --> 00:16:42.959 align:start position:0% shared languages or what the off-chain 00:16:42.959 --> 00:16:44.870 align:start position:0% shared languages or what the off-chain system<00:16:43.259> in<00:16:43.740> uses 00:16:44.870 --> 00:16:44.880 align:start position:0% system in uses 00:16:44.880 --> 00:16:47.030 align:start position:0% system in uses uh<00:16:45.540> the<00:16:45.779> necessary<00:16:46.139> proofs<00:16:46.620> to<00:16:46.740> make<00:16:46.860> with 00:16:47.030 --> 00:16:47.040 align:start position:0% uh the necessary proofs to make with 00:16:47.040 --> 00:16:48.949 align:start position:0% uh the necessary proofs to make with trustless<00:16:47.519> are<00:16:47.820> encapsulated<00:16:48.480> in<00:16:48.779> the 00:16:48.949 --> 00:16:48.959 align:start position:0% trustless are encapsulated in the 00:16:48.959 --> 00:16:50.749 align:start position:0% trustless are encapsulated in the response<00:16:49.320> sent<00:16:49.500> by<00:16:49.740> the<00:16:49.860> Gateway<00:16:50.160> and 00:16:50.749 --> 00:16:50.759 align:start position:0% response sent by the Gateway and 00:16:50.759 --> 00:16:52.550 align:start position:0% response sent by the Gateway and verified<00:16:51.120> by<00:16:51.600> the<00:16:51.839> resolver<00:16:52.259> before 00:16:52.550 --> 00:16:52.560 align:start position:0% verified by the resolver before 00:16:52.560 --> 00:16:53.930 align:start position:0% verified by the resolver before returning<00:16:53.100> the<00:16:53.220> result<00:16:53.399> from<00:16:53.699> the<00:16:53.820> name 00:16:53.930 --> 00:16:53.940 align:start position:0% returning the result from the name 00:16:53.940 --> 00:16:55.189 align:start position:0% returning the result from the name resolution 00:16:55.189 --> 00:16:55.199 align:start position:0% resolution 00:16:55.199 --> 00:16:56.810 align:start position:0% resolution this<00:16:55.500> means<00:16:55.740> that<00:16:55.860> implementing<00:16:56.459> the<00:16:56.639> base 00:16:56.810 --> 00:16:56.820 align:start position:0% this means that implementing the base 00:16:56.820 --> 00:16:59.030 align:start position:0% this means that implementing the base protocol<00:16:57.240> is<00:16:57.899> enough<00:16:58.019> to<00:16:58.259> enable<00:16:58.500> all<00:16:58.860> current 00:16:59.030 --> 00:16:59.040 align:start position:0% protocol is enough to enable all current 00:16:59.040 --> 00:17:01.129 align:start position:0% protocol is enough to enable all current and<00:16:59.279> future<00:16:59.519> l2s<00:17:00.240> and<00:17:00.480> off-chain<00:17:00.899> storage 00:17:01.129 --> 00:17:01.139 align:start position:0% and future l2s and off-chain storage 00:17:01.139 --> 00:17:03.170 align:start position:0% and future l2s and off-chain storage systems<00:17:01.680> to<00:17:01.860> be<00:17:01.980> used<00:17:02.160> in<00:17:02.399> the<00:17:02.579> ens<00:17:02.940> name 00:17:03.170 --> 00:17:03.180 align:start position:0% systems to be used in the ens name 00:17:03.180 --> 00:17:06.049 align:start position:0% systems to be used in the ens name resolution<00:17:03.620> for<00:17:04.620> instance<00:17:04.880> ethers<00:17:05.880> already 00:17:06.049 --> 00:17:06.059 align:start position:0% resolution for instance ethers already 00:17:06.059 --> 00:17:08.090 align:start position:0% resolution for instance ethers already supports<00:17:06.600> this<00:17:06.720> which<00:17:07.380> means<00:17:07.620> that<00:17:07.799> you<00:17:07.919> can 00:17:08.090 --> 00:17:08.100 align:start position:0% supports this which means that you can 00:17:08.100 --> 00:17:10.730 align:start position:0% supports this which means that you can resolve<00:17:08.520> any<00:17:08.760> ens<00:17:09.299> name<00:17:09.480> that<00:17:09.780> uses<00:17:10.079> it<00:17:10.260> even 00:17:10.730 --> 00:17:10.740 align:start position:0% resolve any ens name that uses it even 00:17:10.740 --> 00:17:13.189 align:start position:0% resolve any ens name that uses it even if<00:17:10.980> it<00:17:11.160> uses<00:17:11.459> an<00:17:11.699> L2<00:17:12.120> that<00:17:12.360> didn't<00:17:12.480> exist<00:17:12.839> when 00:17:13.189 --> 00:17:13.199 align:start position:0% if it uses an L2 that didn't exist when 00:17:13.199 --> 00:17:15.650 align:start position:0% if it uses an L2 that didn't exist when the<00:17:13.380> ether's<00:17:13.919> implementation<00:17:14.339> was<00:17:14.640> written 00:17:15.650 --> 00:17:15.660 align:start position:0% the ether's implementation was written 00:17:15.660 --> 00:17:18.409 align:start position:0% the ether's implementation was written and<00:17:16.319> ccip<00:17:16.860> readers<00:17:17.400> already<00:17:17.640> in<00:17:17.939> use<00:17:18.120> in 00:17:18.409 --> 00:17:18.419 align:start position:0% and ccip readers already in use in 00:17:18.419 --> 00:17:21.470 align:start position:0% and ccip readers already in use in production<00:17:18.860> both<00:17:19.860> ethers<00:17:20.459> and<00:17:20.520> Webster<00:17:20.819> ejs 00:17:21.470 --> 00:17:21.480 align:start position:0% production both ethers and Webster ejs 00:17:21.480 --> 00:17:24.890 align:start position:0% production both ethers and Webster ejs support<00:17:22.260> it<00:17:22.760> and<00:17:23.760> so<00:17:24.120> if<00:17:24.240> you<00:17:24.360> use<00:17:24.480> either<00:17:24.720> of 00:17:24.890 --> 00:17:24.900 align:start position:0% support it and so if you use either of 00:17:24.900 --> 00:17:26.809 align:start position:0% support it and so if you use either of those<00:17:25.079> libraries<00:17:25.500> or<00:17:25.860> in<00:17:25.980> fact<00:17:26.160> as<00:17:26.400> of<00:17:26.579> I 00:17:26.809 --> 00:17:26.819 align:start position:0% those libraries or in fact as of I 00:17:26.819 --> 00:17:28.030 align:start position:0% those libraries or in fact as of I believe<00:17:26.939> today 00:17:28.030 --> 00:17:28.040 align:start position:0% believe today 00:17:28.040 --> 00:17:29.650 align:start position:0% believe today web3.pi 00:17:29.650 --> 00:17:29.660 align:start position:0% web3.pi 00:17:29.660 --> 00:17:31.730 align:start position:0% web3.pi upgrading<00:17:30.660> to<00:17:30.780> the<00:17:30.960> latest<00:17:31.080> version<00:17:31.440> will 00:17:31.730 --> 00:17:31.740 align:start position:0% upgrading to the latest version will 00:17:31.740 --> 00:17:34.250 align:start position:0% upgrading to the latest version will mean<00:17:31.919> you<00:17:32.160> automatically<00:17:32.700> support<00:17:33.020> ens<00:17:34.020> of 00:17:34.250 --> 00:17:34.260 align:start position:0% mean you automatically support ens of 00:17:34.260 --> 00:17:36.350 align:start position:0% mean you automatically support ens of chain<00:17:34.440> resolution<00:17:34.860> some<00:17:35.820> of<00:17:36.000> the<00:17:36.059> largest 00:17:36.350 --> 00:17:36.360 align:start position:0% chain resolution some of the largest 00:17:36.360 --> 00:17:38.029 align:start position:0% chain resolution some of the largest apps<00:17:36.780> and<00:17:36.900> wallets<00:17:37.200> have<00:17:37.440> already<00:17:37.620> upgraded 00:17:38.029 --> 00:17:38.039 align:start position:0% apps and wallets have already upgraded 00:17:38.039 --> 00:17:40.870 align:start position:0% apps and wallets have already upgraded to<00:17:38.220> support<00:17:38.340> it<00:17:38.640> too<00:17:38.820> including<00:17:39.539> metabase 00:17:40.870 --> 00:17:40.880 align:start position:0% to support it too including metabase 00:17:40.880 --> 00:17:44.150 align:start position:0% to support it too including metabase metamask<00:17:41.880> coinbase<00:17:42.780> wallet<00:17:43.320> as<00:17:43.860> well<00:17:44.039> as 00:17:44.150 --> 00:17:44.160 align:start position:0% metamask coinbase wallet as well as 00:17:44.160 --> 00:17:47.150 align:start position:0% metamask coinbase wallet as well as ethereum<00:17:44.640> etherscan<00:17:45.900> there's<00:17:46.440> a<00:17:46.679> long<00:17:46.799> way<00:17:46.980> to 00:17:47.150 --> 00:17:47.160 align:start position:0% ethereum etherscan there's a long way to 00:17:47.160 --> 00:17:49.070 align:start position:0% ethereum etherscan there's a long way to go<00:17:47.340> in<00:17:47.640> terms<00:17:47.820> of<00:17:47.940> making<00:17:48.120> this<00:17:48.419> latest<00:17:48.660> change 00:17:49.070 --> 00:17:49.080 align:start position:0% go in terms of making this latest change 00:17:49.080 --> 00:17:52.070 align:start position:0% go in terms of making this latest change Universal<00:17:50.059> so<00:17:51.059> please<00:17:51.299> reach<00:17:51.660> out<00:17:51.720> to<00:17:51.900> your 00:17:52.070 --> 00:17:52.080 align:start position:0% Universal so please reach out to your 00:17:52.080 --> 00:17:54.110 align:start position:0% Universal so please reach out to your favorite<00:17:52.200> wallets<00:17:52.740> and<00:17:53.039> apps<00:17:53.460> if<00:17:53.880> you<00:17:54.000> see 00:17:54.110 --> 00:17:54.120 align:start position:0% favorite wallets and apps if you see 00:17:54.120 --> 00:17:55.610 align:start position:0% favorite wallets and apps if you see that<00:17:54.299> they<00:17:54.539> don't<00:17:54.660> support<00:17:54.900> these<00:17:55.260> new<00:17:55.380> names 00:17:55.610 --> 00:17:55.620 align:start position:0% that they don't support these new names 00:17:55.620 --> 00:17:57.470 align:start position:0% that they don't support these new names and<00:17:56.039> ask<00:17:56.220> them<00:17:56.520> to<00:17:56.820> let<00:17:56.940> them<00:17:57.120> know<00:17:57.240> how 00:17:57.470 --> 00:17:57.480 align:start position:0% and ask them to let them know how 00:17:57.480 --> 00:18:02.330 align:start position:0% and ask them to let them know how important<00:17:57.840> it<00:17:58.020> is<00:17:58.679> uh<00:17:59.520> like<00:18:00.179> our<00:18:00.419> Thorin<00:18:01.340> ccip 00:18:02.330 --> 00:18:02.340 align:start position:0% important it is uh like our Thorin ccip 00:18:02.340 --> 00:18:04.970 align:start position:0% important it is uh like our Thorin ccip reader<00:18:02.880> also<00:18:03.120> isn't<00:18:03.419> just<00:18:03.539> for<00:18:03.720> ens<00:18:04.200> it<00:18:04.740> can<00:18:04.860> be 00:18:04.970 --> 00:18:04.980 align:start position:0% reader also isn't just for ens it can be 00:18:04.980 --> 00:18:07.070 align:start position:0% reader also isn't just for ens it can be used<00:18:05.100> to<00:18:05.340> add<00:18:05.520> off-chain<00:18:06.360> resolution<00:18:06.720> support 00:18:07.070 --> 00:18:07.080 align:start position:0% used to add off-chain resolution support 00:18:07.080 --> 00:18:09.250 align:start position:0% used to add off-chain resolution support to<00:18:07.500> any<00:18:07.799> project 00:18:09.250 --> 00:18:09.260 align:start position:0% to any project 00:18:09.260 --> 00:18:11.630 align:start position:0% to any project coinbase<00:18:10.260> has<00:18:10.500> gone<00:18:10.679> a<00:18:10.860> step<00:18:11.039> further<00:18:11.400> than 00:18:11.630 --> 00:18:11.640 align:start position:0% coinbase has gone a step further than 00:18:11.640 --> 00:18:13.909 align:start position:0% coinbase has gone a step further than just<00:18:11.940> integrating<00:18:12.480> ctip<00:18:13.140> read<00:18:13.500> for<00:18:13.740> name 00:18:13.909 --> 00:18:13.919 align:start position:0% just integrating ctip read for name 00:18:13.919 --> 00:18:17.150 align:start position:0% just integrating ctip read for name resolution<00:18:14.340> they're<00:18:15.120> using<00:18:15.539> ccip<00:18:16.080> read<00:18:16.440> ens 00:18:17.150 --> 00:18:17.160 align:start position:0% resolution they're using ccip read ens 00:18:17.160 --> 00:18:19.370 align:start position:0% resolution they're using ccip read ens wildcard<00:18:17.640> support<00:18:17.880> and<00:18:18.299> ens's<00:18:18.960> DNS 00:18:19.370 --> 00:18:19.380 align:start position:0% wildcard support and ens's DNS 00:18:19.380 --> 00:18:21.529 align:start position:0% wildcard support and ens's DNS integration<00:18:19.860> together<00:18:20.580> to<00:18:21.120> allow<00:18:21.360> their 00:18:21.529 --> 00:18:21.539 align:start position:0% integration together to allow their 00:18:21.539 --> 00:18:24.289 align:start position:0% integration together to allow their wallet<00:18:21.960> their<00:18:22.799> wallet<00:18:23.160> users<00:18:23.400> to<00:18:23.640> create<00:18:23.760> ens 00:18:24.289 --> 00:18:24.299 align:start position:0% wallet their wallet users to create ens 00:18:24.299 --> 00:18:27.590 align:start position:0% wallet their wallet users to create ens names<00:18:24.539> under<00:18:24.960> the<00:18:25.260> dot<00:18:25.559> CB<00:18:25.860> dot<00:18:26.280> ID<00:18:26.460> domain<00:18:27.360> for 00:18:27.590 --> 00:18:27.600 align:start position:0% names under the dot CB dot ID domain for 00:18:27.600 --> 00:18:29.870 align:start position:0% names under the dot CB dot ID domain for free<00:18:27.780> these<00:18:28.620> names<00:18:28.740> will<00:18:29.039> instantly<00:18:29.460> work<00:18:29.640> in 00:18:29.870 --> 00:18:29.880 align:start position:0% free these names will instantly work in 00:18:29.880 --> 00:18:32.090 align:start position:0% free these names will instantly work in any<00:18:30.059> wallet<00:18:30.480> or<00:18:30.660> dap<00:18:30.960> that<00:18:31.140> supports<00:18:31.500> ens's 00:18:32.090 --> 00:18:32.100 align:start position:0% any wallet or dap that supports ens's 00:18:32.100 --> 00:18:34.370 align:start position:0% any wallet or dap that supports ens's new<00:18:32.340> resolution<00:18:32.700> improvements<00:18:33.600> and<00:18:34.200> they 00:18:34.370 --> 00:18:34.380 align:start position:0% new resolution improvements and they 00:18:34.380 --> 00:18:36.350 align:start position:0% new resolution improvements and they have<00:18:34.500> no<00:18:34.679> transaction<00:18:35.100> fees<00:18:35.520> to<00:18:35.700> set<00:18:35.880> up<00:18:36.059> for 00:18:36.350 --> 00:18:36.360 align:start position:0% have no transaction fees to set up for 00:18:36.360 --> 00:18:38.210 align:start position:0% have no transaction fees to set up for either<00:18:36.480> users<00:18:36.900> or<00:18:37.080> coinbase 00:18:38.210 --> 00:18:38.220 align:start position:0% either users or coinbase 00:18:38.220 --> 00:18:41.630 align:start position:0% either users or coinbase likewise<00:18:39.179> lens<00:18:39.900> is<00:18:40.200> using<00:18:40.500> ccip<00:18:40.980> read<00:18:41.340> to 00:18:41.630 --> 00:18:41.640 align:start position:0% likewise lens is using ccip read to 00:18:41.640 --> 00:18:43.490 align:start position:0% likewise lens is using ccip read to integrate<00:18:42.000> their<00:18:42.240> own<00:18:42.360> dot<00:18:42.720> lens<00:18:43.020> naming 00:18:43.490 --> 00:18:43.500 align:start position:0% integrate their own dot lens naming 00:18:43.500 --> 00:18:46.490 align:start position:0% integrate their own dot lens naming system<00:18:43.679> with<00:18:43.980> ens<00:18:44.780> any.lens<00:18:45.780> name<00:18:46.020> you<00:18:46.320> can 00:18:46.490 --> 00:18:46.500 align:start position:0% system with ens any.lens name you can 00:18:46.500 --> 00:18:50.450 align:start position:0% system with ens any.lens name you can add<00:18:46.799> dot<00:18:47.400> X<00:18:47.520> sorry<00:18:48.240> dot<00:18:48.720> XYZ<00:18:49.320> to<00:18:49.559> the<00:18:49.740> end<00:18:49.860> and 00:18:50.450 --> 00:18:50.460 align:start position:0% add dot X sorry dot XYZ to the end and 00:18:50.460 --> 00:18:52.610 align:start position:0% add dot X sorry dot XYZ to the end and it<00:18:50.580> will<00:18:50.760> resolve<00:18:51.240> in<00:18:51.480> metamask<00:18:52.020> or<00:18:52.260> any<00:18:52.440> other 00:18:52.610 --> 00:18:52.620 align:start position:0% it will resolve in metamask or any other 00:18:52.620 --> 00:18:54.830 align:start position:0% it will resolve in metamask or any other wallet<00:18:52.980> that<00:18:53.160> supports<00:18:53.580> this 00:18:54.830 --> 00:18:54.840 align:start position:0% wallet that supports this 00:18:54.840 --> 00:18:57.650 align:start position:0% wallet that supports this so<00:18:55.440> off<00:18:55.620> chain<00:18:55.860> read<00:18:56.160> support<00:18:56.460> is<00:18:56.760> great<00:18:57.000> but 00:18:57.650 --> 00:18:57.660 align:start position:0% so off chain read support is great but 00:18:57.660 --> 00:18:59.870 align:start position:0% so off chain read support is great but how<00:18:57.900> do<00:18:57.960> we<00:18:58.080> enable<00:18:58.320> writes<00:18:58.860> the<00:18:59.580> default 00:18:59.870 --> 00:18:59.880 align:start position:0% how do we enable writes the default 00:18:59.880 --> 00:19:01.850 align:start position:0% how do we enable writes the default option<00:19:00.179> for<00:19:00.419> every<00:19:00.720> platform<00:19:01.140> is<00:19:01.380> to<00:19:01.620> provide 00:19:01.850 --> 00:19:01.860 align:start position:0% option for every platform is to provide 00:19:01.860 --> 00:19:03.770 align:start position:0% option for every platform is to provide its<00:19:02.160> own<00:19:02.220> interface<00:19:02.700> for<00:19:03.000> users<00:19:03.299> to<00:19:03.539> update 00:19:03.770 --> 00:19:03.780 align:start position:0% its own interface for users to update 00:19:03.780 --> 00:19:05.750 align:start position:0% its own interface for users to update their<00:19:04.020> records<00:19:04.500> meaning<00:19:05.100> if<00:19:05.460> you<00:19:05.580> use 00:19:05.750 --> 00:19:05.760 align:start position:0% their records meaning if you use 00:19:05.760 --> 00:19:07.130 align:start position:0% their records meaning if you use coinbase<00:19:06.240> wallets<00:19:06.660> you<00:19:06.840> have<00:19:06.900> to<00:19:07.020> use 00:19:07.130 --> 00:19:07.140 align:start position:0% coinbase wallets you have to use 00:19:07.140 --> 00:19:09.230 align:start position:0% coinbase wallets you have to use coinbase<00:19:07.620> to<00:19:07.860> update<00:19:08.160> your<00:19:08.340> records<00:19:08.820> if<00:19:09.059> you 00:19:09.230 --> 00:19:09.240 align:start position:0% coinbase to update your records if you 00:19:09.240 --> 00:19:11.270 align:start position:0% coinbase to update your records if you use<00:19:09.419> metamask<00:19:10.380> you'd<00:19:10.679> have<00:19:10.799> to<00:19:10.919> update<00:19:11.100> with 00:19:11.270 --> 00:19:11.280 align:start position:0% use metamask you'd have to update with 00:19:11.280 --> 00:19:14.210 align:start position:0% use metamask you'd have to update with metamask<00:19:12.020> but<00:19:13.020> this<00:19:13.200> leads<00:19:13.500> to<00:19:13.620> fragmentation 00:19:14.210 --> 00:19:14.220 align:start position:0% metamask but this leads to fragmentation 00:19:14.220 --> 00:19:16.310 align:start position:0% metamask but this leads to fragmentation and<00:19:14.700> makes<00:19:14.880> general<00:19:15.179> purpose<00:19:15.660> apps<00:19:16.020> like<00:19:16.140> our 00:19:16.310 --> 00:19:16.320 align:start position:0% and makes general purpose apps like our 00:19:16.320 --> 00:19:19.370 align:start position:0% and makes general purpose apps like our own<00:19:16.500> manager<00:19:17.039> much<00:19:17.580> less<00:19:17.760> useful<00:19:18.240> fixing<00:19:19.200> this 00:19:19.370 --> 00:19:19.380 align:start position:0% own manager much less useful fixing this 00:19:19.380 --> 00:19:22.669 align:start position:0% own manager much less useful fixing this is<00:19:19.620> still<00:19:19.799> a<00:19:19.980> work<00:19:20.100> in<00:19:20.280> progress<00:19:20.640> but<00:19:21.419> Eep<00:19:21.780> 5559 00:19:22.669 --> 00:19:22.679 align:start position:0% is still a work in progress but Eep 5559 00:19:22.679 --> 00:19:25.430 align:start position:0% is still a work in progress but Eep 5559 lays<00:19:23.580> out<00:19:23.760> a<00:19:23.880> way<00:19:24.059> forward<00:19:24.299> by<00:19:24.840> enabling<00:19:25.200> a 00:19:25.430 --> 00:19:25.440 align:start position:0% lays out a way forward by enabling a 00:19:25.440 --> 00:19:27.950 align:start position:0% lays out a way forward by enabling a discovery<00:19:25.919> mechanism<00:19:26.400> that<00:19:27.000> allows<00:19:27.419> clients 00:19:27.950 --> 00:19:27.960 align:start position:0% discovery mechanism that allows clients 00:19:27.960 --> 00:19:30.890 align:start position:0% discovery mechanism that allows clients such<00:19:28.679> as<00:19:28.860> our<00:19:29.039> manager<00:19:29.460> to<00:19:30.000> discover<00:19:30.179> how<00:19:30.780> they 00:19:30.890 --> 00:19:30.900 align:start position:0% such as our manager to discover how they 00:19:30.900 --> 00:19:32.870 align:start position:0% such as our manager to discover how they can<00:19:31.080> send<00:19:31.200> a<00:19:31.440> transaction<00:19:31.860> or<00:19:32.280> an<00:19:32.400> HTTP 00:19:32.870 --> 00:19:32.880 align:start position:0% can send a transaction or an HTTP 00:19:32.880 --> 00:19:35.029 align:start position:0% can send a transaction or an HTTP request<00:19:33.240> to<00:19:33.660> update<00:19:33.960> data<00:19:34.440> that's<00:19:34.620> stored<00:19:34.980> off 00:19:35.029 --> 00:19:35.039 align:start position:0% request to update data that's stored off 00:19:35.039 --> 00:19:36.830 align:start position:0% request to update data that's stored off chain 00:19:36.830 --> 00:19:36.840 align:start position:0% chain 00:19:36.840 --> 00:19:39.010 align:start position:0% chain um<00:19:36.900> it's<00:19:37.140> currently<00:19:37.559> supports<00:19:38.039> writing<00:19:38.520> to 00:19:39.010 --> 00:19:39.020 align:start position:0% um it's currently supports writing to 00:19:39.020 --> 00:19:42.890 align:start position:0% um it's currently supports writing to evm-based<00:19:40.020> l2s<00:19:40.500> or<00:19:40.679> side<00:19:40.860> chains<00:19:41.419> or<00:19:42.419> sending 00:19:42.890 --> 00:19:42.900 align:start position:0% evm-based l2s or side chains or sending 00:19:42.900 --> 00:19:45.710 align:start position:0% evm-based l2s or side chains or sending signed<00:19:43.320> messages<00:19:43.440> to<00:19:43.860> an<00:19:43.980> HTTP<00:19:44.460> API<00:19:45.059> but<00:19:45.539> this 00:19:45.710 --> 00:19:45.720 align:start position:0% signed messages to an HTTP API but this 00:19:45.720 --> 00:19:47.630 align:start position:0% signed messages to an HTTP API but this is<00:19:45.900> extensible<00:19:46.380> with<00:19:46.740> new<00:19:46.980> methods<00:19:47.400> as<00:19:47.520> they 00:19:47.630 --> 00:19:47.640 align:start position:0% is extensible with new methods as they 00:19:47.640 --> 00:19:50.270 align:start position:0% is extensible with new methods as they crop<00:19:47.940> up<00:19:48.480> adding<00:19:49.380> support<00:19:49.500> for<00:19:49.799> this<00:19:49.980> to<00:19:50.220> the 00:19:50.270 --> 00:19:50.280 align:start position:0% crop up adding support for this to the 00:19:50.280 --> 00:19:52.610 align:start position:0% crop up adding support for this to the NS<00:19:50.580> manager<00:19:51.120> and<00:19:51.480> further<00:19:51.780> standardizing<00:19:52.440> the 00:19:52.610 --> 00:19:52.620 align:start position:0% NS manager and further standardizing the 00:19:52.620 --> 00:19:54.650 align:start position:0% NS manager and further standardizing the best<00:19:52.799> practices<00:19:53.280> and<00:19:53.820> making<00:19:54.059> it<00:19:54.360> as<00:19:54.539> as 00:19:54.650 --> 00:19:54.660 align:start position:0% best practices and making it as as 00:19:54.660 --> 00:19:57.110 align:start position:0% best practices and making it as as flexible<00:19:55.260> and<00:19:55.440> accessible<00:19:55.919> as<00:19:56.100> possible<00:19:56.460> is 00:19:57.110 --> 00:19:57.120 align:start position:0% flexible and accessible as possible is 00:19:57.120 --> 00:19:59.750 align:start position:0% flexible and accessible as possible is an<00:19:57.360> active<00:19:57.720> active<00:19:58.260> area<00:19:58.500> of<00:19:58.980> research<00:19:59.460> and 00:19:59.750 --> 00:19:59.760 align:start position:0% an active active area of research and 00:19:59.760 --> 00:20:01.430 align:start position:0% an active active area of research and development<00:20:00.179> for<00:20:00.539> the<00:20:00.660> team 00:20:01.430 --> 00:20:01.440 align:start position:0% development for the team 00:20:01.440 --> 00:20:04.070 align:start position:0% development for the team so<00:20:02.220> next<00:20:02.520> up<00:20:02.640> the<00:20:02.820> name<00:20:02.940> wrapper<00:20:03.419> which<00:20:03.720> you've 00:20:04.070 --> 00:20:04.080 align:start position:0% so next up the name wrapper which you've 00:20:04.080 --> 00:20:05.870 align:start position:0% so next up the name wrapper which you've probably<00:20:04.260> heard<00:20:04.440> about<00:20:04.679> of<00:20:04.980> griping<00:20:05.460> about<00:20:05.580> on 00:20:05.870 --> 00:20:05.880 align:start position:0% probably heard about of griping about on 00:20:05.880 --> 00:20:07.789 align:start position:0% probably heard about of griping about on Twitter<00:20:06.059> because<00:20:06.419> uh<00:20:06.960> it's<00:20:07.260> been<00:20:07.440> underway 00:20:07.789 --> 00:20:07.799 align:start position:0% Twitter because uh it's been underway 00:20:07.799 --> 00:20:09.070 align:start position:0% Twitter because uh it's been underway for<00:20:08.100> a<00:20:08.220> while 00:20:09.070 --> 00:20:09.080 align:start position:0% for a while 00:20:09.080 --> 00:20:11.930 align:start position:0% for a while ens<00:20:10.080> predates<00:20:10.440> all<00:20:10.740> of<00:20:10.860> the<00:20:10.980> nft<00:20:11.280> standards 00:20:11.930 --> 00:20:11.940 align:start position:0% ens predates all of the nft standards 00:20:11.940 --> 00:20:14.150 align:start position:0% ens predates all of the nft standards and<00:20:12.480> while<00:20:12.660> the<00:20:12.900> dot<00:20:13.140> eth<00:20:13.320> registrar<00:20:13.919> was 00:20:14.150 --> 00:20:14.160 align:start position:0% and while the dot eth registrar was 00:20:14.160 --> 00:20:16.970 align:start position:0% and while the dot eth registrar was written<00:20:14.520> after<00:20:14.760> Eep<00:20:15.240> 721<00:20:15.720> came<00:20:15.960> out<00:20:16.080> that 00:20:16.970 --> 00:20:16.980 align:start position:0% written after Eep 721 came out that 00:20:16.980 --> 00:20:18.890 align:start position:0% written after Eep 721 came out that functionality<00:20:17.580> only<00:20:17.820> applies<00:20:18.299> to<00:20:18.539> dot<00:20:18.840> e 00:20:18.890 --> 00:20:18.900 align:start position:0% functionality only applies to dot e 00:20:18.900 --> 00:20:21.830 align:start position:0% functionality only applies to dot e second<00:20:19.200> level<00:20:19.380> domains<00:20:20.039> so<00:20:20.340> nick.heath<00:20:21.299> but 00:20:21.830 --> 00:20:21.840 align:start position:0% second level domains so nick.heath but 00:20:21.840 --> 00:20:23.289 align:start position:0% second level domains so nick.heath but not 00:20:23.289 --> 00:20:23.299 align:start position:0% not 00:20:23.299 --> 00:20:27.010 align:start position:0% not wallet.beck.eth<00:20:24.299> or<00:20:24.980> nick.xyz<00:20:25.980> or<00:20:26.460> whatnot 00:20:27.010 --> 00:20:27.020 align:start position:0% wallet.beck.eth or nick.xyz or whatnot 00:20:27.020 --> 00:20:30.049 align:start position:0% wallet.beck.eth or nick.xyz or whatnot as<00:20:28.020> a<00:20:28.140> result<00:20:28.320> not<00:20:28.679> Alliance<00:20:29.340> names<00:20:29.580> can<00:20:29.880> be 00:20:30.049 --> 00:20:30.059 align:start position:0% as a result not Alliance names can be 00:20:30.059 --> 00:20:32.930 align:start position:0% as a result not Alliance names can be transferred<00:20:31.020> exchanged<00:20:31.799> Etc<00:20:31.919> using<00:20:32.580> standard 00:20:32.930 --> 00:20:32.940 align:start position:0% transferred exchanged Etc using standard 00:20:32.940 --> 00:20:34.610 align:start position:0% transferred exchanged Etc using standard nft<00:20:33.299> interfaces 00:20:34.610 --> 00:20:34.620 align:start position:0% nft interfaces 00:20:34.620 --> 00:20:37.490 align:start position:0% nft interfaces uh<00:20:35.460> further<00:20:35.940> one<00:20:36.240> of<00:20:36.360> the<00:20:36.480> main<00:20:36.720> advantages<00:20:37.200> of 00:20:37.490 --> 00:20:37.500 align:start position:0% uh further one of the main advantages of 00:20:37.500 --> 00:20:39.890 align:start position:0% uh further one of the main advantages of tradability<00:20:37.980> is<00:20:38.280> trustless<00:20:38.700> ownership<00:20:39.059> if 00:20:39.890 --> 00:20:39.900 align:start position:0% tradability is trustless ownership if 00:20:39.900 --> 00:20:42.110 align:start position:0% tradability is trustless ownership if somebody<00:20:40.080> sells<00:20:40.740> you<00:20:40.799> a<00:20:40.980> name<00:20:41.160> or<00:20:41.520> a<00:20:41.640> subdomain 00:20:42.110 --> 00:20:42.120 align:start position:0% somebody sells you a name or a subdomain 00:20:42.120 --> 00:20:44.870 align:start position:0% somebody sells you a name or a subdomain or<00:20:42.720> gives<00:20:42.960> it<00:20:43.140> to<00:20:43.320> you<00:20:43.500> you<00:20:44.220> want<00:20:44.400> to<00:20:44.520> make<00:20:44.700> sure 00:20:44.870 --> 00:20:44.880 align:start position:0% or gives it to you you want to make sure 00:20:44.880 --> 00:20:46.730 align:start position:0% or gives it to you you want to make sure that<00:20:45.179> they<00:20:45.360> can't<00:20:45.539> take<00:20:45.780> it<00:20:45.960> back<00:20:46.140> next<00:20:46.500> week 00:20:46.730 --> 00:20:46.740 align:start position:0% that they can't take it back next week 00:20:46.740 --> 00:20:48.950 align:start position:0% that they can't take it back next week and<00:20:47.160> set<00:20:47.400> it<00:20:47.520> to<00:20:47.640> a<00:20:47.760> different<00:20:47.880> address 00:20:48.950 --> 00:20:48.960 align:start position:0% and set it to a different address 00:20:48.960 --> 00:20:51.049 align:start position:0% and set it to a different address you're<00:20:49.679> kind<00:20:49.860> of<00:20:49.919> reliant<00:20:50.340> on<00:20:50.520> their<00:20:50.700> Goodwill 00:20:51.049 --> 00:20:51.059 align:start position:0% you're kind of reliant on their Goodwill 00:20:51.059 --> 00:20:53.450 align:start position:0% you're kind of reliant on their Goodwill there<00:20:51.960> are<00:20:52.080> solutions<00:20:52.500> to<00:20:52.860> work<00:20:52.980> around<00:20:53.160> this 00:20:53.450 --> 00:20:53.460 align:start position:0% there are solutions to work around this 00:20:53.460 --> 00:20:55.850 align:start position:0% there are solutions to work around this you<00:20:53.940> can<00:20:54.059> give<00:20:54.720> net<00:20:55.020> ownership<00:20:55.380> of<00:20:55.620> the<00:20:55.740> name 00:20:55.850 --> 00:20:55.860 align:start position:0% you can give net ownership of the name 00:20:55.860 --> 00:20:57.890 align:start position:0% you can give net ownership of the name to<00:20:56.100> a<00:20:56.220> contract<00:20:56.520> and<00:20:56.820> we've<00:20:57.059> had<00:20:57.179> a<00:20:57.360> system<00:20:57.539> for 00:20:57.890 --> 00:20:57.900 align:start position:0% to a contract and we've had a system for 00:20:57.900 --> 00:20:59.470 align:start position:0% to a contract and we've had a system for that<00:20:58.080> called 00:20:59.470 --> 00:20:59.480 align:start position:0% that called 00:20:59.480 --> 00:21:02.330 align:start position:0% that called now.ens.domains<00:21:00.480> for<00:21:00.600> some<00:21:00.780> time<00:21:01.020> but<00:21:01.919> it<00:21:02.160> has 00:21:02.330 --> 00:21:02.340 align:start position:0% now.ens.domains for some time but it has 00:21:02.340 --> 00:21:04.370 align:start position:0% now.ens.domains for some time but it has significant<00:21:02.760> shortcomings<00:21:03.360> in<00:21:03.660> that<00:21:03.900> you're 00:21:04.370 --> 00:21:04.380 align:start position:0% significant shortcomings in that you're 00:21:04.380 --> 00:21:05.930 align:start position:0% significant shortcomings in that you're committing<00:21:04.799> your<00:21:04.919> name<00:21:05.100> to<00:21:05.340> a<00:21:05.580> specific 00:21:05.930 --> 00:21:05.940 align:start position:0% committing your name to a specific 00:21:05.940 --> 00:21:07.970 align:start position:0% committing your name to a specific contract<00:21:06.480> where<00:21:07.020> it<00:21:07.200> has<00:21:07.320> to<00:21:07.440> live<00:21:07.620> for<00:21:07.860> the 00:21:07.970 --> 00:21:07.980 align:start position:0% contract where it has to live for the 00:21:07.980 --> 00:21:10.190 align:start position:0% contract where it has to live for the rest<00:21:08.039> of<00:21:08.220> time<00:21:08.480> which<00:21:09.480> limits<00:21:09.840> what<00:21:09.960> you<00:21:10.080> can 00:21:10.190 --> 00:21:10.200 align:start position:0% rest of time which limits what you can 00:21:10.200 --> 00:21:12.770 align:start position:0% rest of time which limits what you can do<00:21:10.260> with<00:21:10.440> it<00:21:10.700> the<00:21:11.700> name<00:21:11.820> ramper<00:21:12.360> solves<00:21:12.660> both 00:21:12.770 --> 00:21:12.780 align:start position:0% do with it the name ramper solves both 00:21:12.780 --> 00:21:15.409 align:start position:0% do with it the name ramper solves both these<00:21:13.140> problems<00:21:13.500> it<00:21:13.919> allows<00:21:14.220> any<00:21:14.400> EMS<00:21:14.940> name<00:21:15.120> at 00:21:15.409 --> 00:21:15.419 align:start position:0% these problems it allows any EMS name at 00:21:15.419 --> 00:21:17.630 align:start position:0% these problems it allows any EMS name at any<00:21:15.539> level<00:21:15.720> whether<00:21:16.200> it's<00:21:16.380> a<00:21:16.559> dodeath<00:21:17.220> or<00:21:17.520> a 00:21:17.630 --> 00:21:17.640 align:start position:0% any level whether it's a dodeath or a 00:21:17.640 --> 00:21:20.810 align:start position:0% any level whether it's a dodeath or a subdomain<00:21:18.179> or<00:21:18.480> a<00:21:18.539> DNS<00:21:18.900> name<00:21:19.140> to<00:21:19.980> be<00:21:20.100> wrapped<00:21:20.580> as 00:21:20.810 --> 00:21:20.820 align:start position:0% subdomain or a DNS name to be wrapped as 00:21:20.820 --> 00:21:25.070 align:start position:0% subdomain or a DNS name to be wrapped as an<00:21:20.940> ERC<00:21:21.360> 1155<00:21:22.140> nft<00:21:22.679> it<00:21:23.640> also<00:21:23.940> allows<00:21:24.539> owners<00:21:24.900> of 00:21:25.070 --> 00:21:25.080 align:start position:0% an ERC 1155 nft it also allows owners of 00:21:25.080 --> 00:21:27.230 align:start position:0% an ERC 1155 nft it also allows owners of wrapped<00:21:25.500> names<00:21:25.679> to<00:21:26.039> revoke<00:21:26.340> permissions<00:21:26.880> such 00:21:27.230 --> 00:21:27.240 align:start position:0% wrapped names to revoke permissions such 00:21:27.240 --> 00:21:29.090 align:start position:0% wrapped names to revoke permissions such as<00:21:27.419> the<00:21:27.660> ability<00:21:27.900> to<00:21:28.260> replace<00:21:28.440> or<00:21:28.860> delete 00:21:29.090 --> 00:21:29.100 align:start position:0% as the ability to replace or delete 00:21:29.100 --> 00:21:32.570 align:start position:0% as the ability to replace or delete subdomains<00:21:29.880> by<00:21:30.480> mechanism<00:21:30.900> we<00:21:31.140> call<00:21:31.380> fuses 00:21:32.570 --> 00:21:32.580 align:start position:0% subdomains by mechanism we call fuses 00:21:32.580 --> 00:21:34.909 align:start position:0% subdomains by mechanism we call fuses fuses<00:21:33.419> allow<00:21:33.840> the<00:21:33.960> owner<00:21:34.320> of<00:21:34.440> a<00:21:34.620> name<00:21:34.740> to 00:21:34.909 --> 00:21:34.919 align:start position:0% fuses allow the owner of a name to 00:21:34.919 --> 00:21:36.890 align:start position:0% fuses allow the owner of a name to revoke<00:21:35.220> their<00:21:35.460> own<00:21:35.640> control<00:21:35.880> and<00:21:36.360> that<00:21:36.539> of<00:21:36.720> any 00:21:36.890 --> 00:21:36.900 align:start position:0% revoke their own control and that of any 00:21:36.900 --> 00:21:38.690 align:start position:0% revoke their own control and that of any subsequent<00:21:37.380> owners<00:21:37.799> over<00:21:38.340> certain 00:21:38.690 --> 00:21:38.700 align:start position:0% subsequent owners over certain 00:21:38.700 --> 00:21:40.549 align:start position:0% subsequent owners over certain functionality<00:21:39.299> on<00:21:39.600> a<00:21:39.720> name<00:21:39.840> such<00:21:40.260> as<00:21:40.380> the 00:21:40.549 --> 00:21:40.559 align:start position:0% functionality on a name such as the 00:21:40.559 --> 00:21:43.190 align:start position:0% functionality on a name such as the ability<00:21:40.799> to<00:21:41.039> unwrap<00:21:41.460> it<00:21:41.580> again<00:21:41.720> to<00:21:42.720> create<00:21:42.840> or 00:21:43.190 --> 00:21:43.200 align:start position:0% ability to unwrap it again to create or 00:21:43.200 --> 00:21:46.610 align:start position:0% ability to unwrap it again to create or to<00:21:43.320> replace<00:21:43.500> subdomains<00:21:44.539> to<00:21:45.539> transfer<00:21:46.380> it<00:21:46.500> to 00:21:46.610 --> 00:21:46.620 align:start position:0% to replace subdomains to transfer it to 00:21:46.620 --> 00:21:49.190 align:start position:0% to replace subdomains to transfer it to another<00:21:46.740> user<00:21:47.159> and<00:21:47.400> so<00:21:47.520> forth<00:21:47.880> once<00:21:48.720> a<00:21:48.780> fuse<00:21:49.020> is 00:21:49.190 --> 00:21:49.200 align:start position:0% another user and so forth once a fuse is 00:21:49.200 --> 00:21:51.230 align:start position:0% another user and so forth once a fuse is burned<00:21:49.620> that<00:21:49.919> fuse<00:21:50.220> can't<00:21:50.460> be<00:21:50.640> reset<00:21:51.000> until 00:21:51.230 --> 00:21:51.240 align:start position:0% burned that fuse can't be reset until 00:21:51.240 --> 00:21:53.990 align:start position:0% burned that fuse can't be reset until the<00:21:51.539> name<00:21:51.720> expires<00:21:52.320> giving<00:21:52.799> a<00:21:53.039> user's<00:21:53.460> a 00:21:53.990 --> 00:21:54.000 align:start position:0% the name expires giving a user's a 00:21:54.000 --> 00:21:56.450 align:start position:0% the name expires giving a user's a guarantee<00:21:54.480> as<00:21:55.020> to<00:21:55.260> what<00:21:55.380> can<00:21:55.559> be<00:21:55.679> done<00:21:55.860> to<00:21:56.220> or 00:21:56.450 --> 00:21:56.460 align:start position:0% guarantee as to what can be done to or 00:21:56.460 --> 00:21:58.130 align:start position:0% guarantee as to what can be done to or with<00:21:56.700> their<00:21:56.940> names<00:21:57.179> until<00:21:57.659> the<00:21:57.960> name 00:21:58.130 --> 00:21:58.140 align:start position:0% with their names until the name 00:21:58.140 --> 00:22:00.830 align:start position:0% with their names until the name expiration<00:21:58.980> is<00:21:59.220> reached<00:21:59.640> the<00:22:00.360> name<00:22:00.480> ramp 00:22:00.830 --> 00:22:00.840 align:start position:0% expiration is reached the name ramp 00:22:00.840 --> 00:22:02.930 align:start position:0% expiration is reached the name ramp attracts<00:22:01.260> these<00:22:01.500> permissions<00:22:01.980> and<00:22:02.520> provides 00:22:02.930 --> 00:22:02.940 align:start position:0% attracts these permissions and provides 00:22:02.940 --> 00:22:05.270 align:start position:0% attracts these permissions and provides a<00:22:03.059> very<00:22:03.179> easy<00:22:03.360> API<00:22:03.960> for<00:22:04.320> fetching<00:22:04.799> the<00:22:04.919> set<00:22:05.100> of 00:22:05.270 --> 00:22:05.280 align:start position:0% a very easy API for fetching the set of 00:22:05.280 --> 00:22:07.190 align:start position:0% a very easy API for fetching the set of restrictions<00:22:05.700> currently<00:22:06.299> applied<00:22:06.659> to<00:22:06.900> a<00:22:07.020> name 00:22:07.190 --> 00:22:07.200 align:start position:0% restrictions currently applied to a name 00:22:07.200 --> 00:22:09.669 align:start position:0% restrictions currently applied to a name and<00:22:07.740> when<00:22:07.860> they'll<00:22:08.100> expire 00:22:09.669 --> 00:22:09.679 align:start position:0% and when they'll expire 00:22:09.679 --> 00:22:11.930 align:start position:0% and when they'll expire alongside<00:22:10.679> the<00:22:10.860> name<00:22:10.980> wrapper<00:22:11.460> we've<00:22:11.760> also 00:22:11.930 --> 00:22:11.940 align:start position:0% alongside the name wrapper we've also 00:22:11.940 --> 00:22:13.490 align:start position:0% alongside the name wrapper we've also implemented<00:22:12.419> a<00:22:12.600> suite<00:22:12.900> of<00:22:13.020> other<00:22:13.140> contract 00:22:13.490 --> 00:22:13.500 align:start position:0% implemented a suite of other contract 00:22:13.500 --> 00:22:15.770 align:start position:0% implemented a suite of other contract improvements<00:22:14.159> including<00:22:15.000> to<00:22:15.179> the<00:22:15.299> dot<00:22:15.539> Heath 00:22:15.770 --> 00:22:15.780 align:start position:0% improvements including to the dot Heath 00:22:15.780 --> 00:22:17.930 align:start position:0% improvements including to the dot Heath registrar<00:22:16.260> controller<00:22:16.740> the<00:22:17.580> reverse 00:22:17.930 --> 00:22:17.940 align:start position:0% registrar controller the reverse 00:22:17.940 --> 00:22:20.570 align:start position:0% registrar controller the reverse registrar<00:22:18.539> and<00:22:18.780> the<00:22:18.900> public<00:22:18.960> resolver<00:22:19.620> all 00:22:20.570 --> 00:22:20.580 align:start position:0% registrar and the public resolver all 00:22:20.580 --> 00:22:21.890 align:start position:0% registrar and the public resolver all together<00:22:20.760> these<00:22:21.120> will<00:22:21.299> prevent<00:22:21.600> a<00:22:21.780> much 00:22:21.890 --> 00:22:21.900 align:start position:0% together these will prevent a much 00:22:21.900 --> 00:22:24.110 align:start position:0% together these will prevent a much smoother<00:22:22.320> registration<00:22:22.860> process<00:22:23.340> for<00:22:23.820> end 00:22:24.110 --> 00:22:24.120 align:start position:0% smoother registration process for end 00:22:24.120 --> 00:22:25.909 align:start position:0% smoother registration process for end users<00:22:24.539> and<00:22:24.780> cut<00:22:25.020> down<00:22:25.200> on<00:22:25.440> the<00:22:25.620> number<00:22:25.679> of 00:22:25.909 --> 00:22:25.919 align:start position:0% users and cut down on the number of 00:22:25.919 --> 00:22:28.310 align:start position:0% users and cut down on the number of transactions<00:22:26.520> and<00:22:26.760> gas<00:22:26.940> required<00:22:27.600> as<00:22:28.080> well<00:22:28.200> as 00:22:28.310 --> 00:22:28.320 align:start position:0% transactions and gas required as well as 00:22:28.320 --> 00:22:30.230 align:start position:0% transactions and gas required as well as other<00:22:28.559> quality<00:22:28.980> of<00:22:29.159> life<00:22:29.340> improvements<00:22:30.000> like 00:22:30.230 --> 00:22:30.240 align:start position:0% other quality of life improvements like 00:22:30.240 --> 00:22:32.270 align:start position:0% other quality of life improvements like allowing<00:22:30.780> contract<00:22:31.140> donors<00:22:31.500> to<00:22:31.740> set<00:22:31.860> primary 00:22:32.270 --> 00:22:32.280 align:start position:0% allowing contract donors to set primary 00:22:32.280 --> 00:22:34.970 align:start position:0% allowing contract donors to set primary names<00:22:32.460> for<00:22:32.700> their<00:22:32.880> contracts<00:22:33.679> the<00:22:34.679> long<00:22:34.860> and 00:22:34.970 --> 00:22:34.980 align:start position:0% names for their contracts the long and 00:22:34.980 --> 00:22:37.250 align:start position:0% names for their contracts the long and short<00:22:35.220> of<00:22:35.400> us<00:22:35.640> is<00:22:35.820> that<00:22:36.179> with<00:22:36.659> the<00:22:36.840> new<00:22:36.960> DOT 00:22:37.250 --> 00:22:37.260 align:start position:0% short of us is that with the new DOT 00:22:37.260 --> 00:22:39.529 align:start position:0% short of us is that with the new DOT ease<00:22:37.440> registrar<00:22:37.980> you<00:22:38.580> will<00:22:38.700> be<00:22:38.880> able<00:22:39.059> to 00:22:39.529 --> 00:22:39.539 align:start position:0% ease registrar you will be able to 00:22:39.539 --> 00:22:43.070 align:start position:0% ease registrar you will be able to register<00:22:40.500> a<00:22:40.799> name<00:22:40.980> wrap<00:22:41.700> it<00:22:41.880> in<00:22:42.539> order<00:22:42.659> to<00:22:42.900> set 00:22:43.070 --> 00:22:43.080 align:start position:0% register a name wrap it in order to set 00:22:43.080 --> 00:22:45.529 align:start position:0% register a name wrap it in order to set permissions<00:22:43.500> burn<00:22:43.860> fuses<00:22:44.460> and<00:22:45.059> set<00:22:45.299> your 00:22:45.529 --> 00:22:45.539 align:start position:0% permissions burn fuses and set your 00:22:45.539 --> 00:22:47.450 align:start position:0% permissions burn fuses and set your primary<00:22:45.900> name<00:22:46.140> all<00:22:46.500> in<00:22:46.679> a<00:22:46.860> single<00:22:47.039> transaction 00:22:47.450 --> 00:22:47.460 align:start position:0% primary name all in a single transaction 00:22:47.460 --> 00:22:49.669 align:start position:0% primary name all in a single transaction and<00:22:48.059> using<00:22:48.419> less<00:22:48.659> gas<00:22:48.960> than<00:22:49.260> doing<00:22:49.440> those 00:22:49.669 --> 00:22:49.679 align:start position:0% and using less gas than doing those 00:22:49.679 --> 00:22:51.770 align:start position:0% and using less gas than doing those operations<00:22:50.100> would<00:22:50.400> cost<00:22:50.580> today 00:22:51.770 --> 00:22:51.780 align:start position:0% operations would cost today 00:22:51.780 --> 00:22:54.289 align:start position:0% operations would cost today uh<00:22:52.500> all<00:22:52.740> of<00:22:52.860> these<00:22:53.039> updates<00:22:53.340> are<00:22:53.640> live<00:22:53.820> now<00:22:54.059> on 00:22:54.289 --> 00:22:54.299 align:start position:0% uh all of these updates are live now on 00:22:54.299 --> 00:22:56.510 align:start position:0% uh all of these updates are live now on the<00:22:54.419> Gurley<00:22:54.780> test<00:22:55.020> net<00:22:55.260> and<00:22:56.100> we're<00:22:56.220> planning 00:22:56.510 --> 00:22:56.520 align:start position:0% the Gurley test net and we're planning 00:22:56.520 --> 00:22:58.130 align:start position:0% the Gurley test net and we're planning to<00:22:56.640> submit<00:22:56.880> them<00:22:57.000> to<00:22:57.179> the<00:22:57.299> Dow<00:22:57.480> for<00:22:57.780> approval 00:22:58.130 --> 00:22:58.140 align:start position:0% to submit them to the Dow for approval 00:22:58.140 --> 00:23:01.730 align:start position:0% to submit them to the Dow for approval on<00:22:58.380> mainnet<00:22:58.919> very<00:22:59.400> shortly<00:22:59.700> after<00:22:59.880> divcom 00:23:01.730 --> 00:23:01.740 align:start position:0% on mainnet very shortly after divcom 00:23:01.740 --> 00:23:08.169 align:start position:0% on mainnet very shortly after divcom uh<00:23:02.460> thank<00:23:03.059> you 00:23:08.169 --> 00:23:08.179 align:start position:0% 00:23:08.179 --> 00:23:10.010 align:start position:0% finally<00:23:09.179> I'm<00:23:09.480> going<00:23:09.659> to<00:23:09.720> talk<00:23:09.840> about 00:23:10.010 --> 00:23:10.020 align:start position:0% finally I'm going to talk about 00:23:10.020 --> 00:23:11.690 align:start position:0% finally I'm going to talk about something<00:23:10.380> else<00:23:10.620> I'm<00:23:10.860> excited<00:23:11.280> we'll<00:23:11.460> be<00:23:11.640> able 00:23:11.690 --> 00:23:11.700 align:start position:0% something else I'm excited we'll be able 00:23:11.700 --> 00:23:14.110 align:start position:0% something else I'm excited we'll be able to<00:23:11.820> release<00:23:12.000> soon<00:23:12.360> gasless<00:23:12.960> DNS<00:23:13.440> integration 00:23:14.110 --> 00:23:14.120 align:start position:0% to release soon gasless DNS integration 00:23:14.120 --> 00:23:17.029 align:start position:0% to release soon gasless DNS integration presently<00:23:15.120> claiming<00:23:15.659> a<00:23:15.780> DNS<00:23:16.140> name<00:23:16.320> in<00:23:16.559> ens 00:23:17.029 --> 00:23:17.039 align:start position:0% presently claiming a DNS name in ens 00:23:17.039 --> 00:23:19.490 align:start position:0% presently claiming a DNS name in ens cost<00:23:17.520> a<00:23:17.880> substantial<00:23:18.240> amount<00:23:18.480> of<00:23:18.659> gas<00:23:18.840> it's 00:23:19.490 --> 00:23:19.500 align:start position:0% cost a substantial amount of gas it's 00:23:19.500 --> 00:23:22.070 align:start position:0% cost a substantial amount of gas it's about<00:23:19.679> 100K<00:23:20.340> to<00:23:20.640> a<00:23:20.820> million<00:23:21.120> gas<00:23:21.360> per 00:23:22.070 --> 00:23:22.080 align:start position:0% about 100K to a million gas per 00:23:22.080 --> 00:23:24.350 align:start position:0% about 100K to a million gas per signature<00:23:22.559> it<00:23:22.679> has<00:23:22.799> to<00:23:22.919> verify<00:23:23.340> depending<00:23:24.240> on 00:23:24.350 --> 00:23:24.360 align:start position:0% signature it has to verify depending on 00:23:24.360 --> 00:23:26.090 align:start position:0% signature it has to verify depending on the<00:23:24.480> ether<00:23:24.720> and<00:23:24.960> gas<00:23:25.080> price<00:23:25.380> that<00:23:25.679> can<00:23:25.860> range 00:23:26.090 --> 00:23:26.100 align:start position:0% the ether and gas price that can range 00:23:26.100 --> 00:23:28.430 align:start position:0% the ether and gas price that can range anywhere<00:23:26.520> from<00:23:26.820> 20<00:23:27.419> bucks<00:23:27.659> to<00:23:28.020> at<00:23:28.260> the 00:23:28.430 --> 00:23:28.440 align:start position:0% anywhere from 20 bucks to at the 00:23:28.440 --> 00:23:29.930 align:start position:0% anywhere from 20 bucks to at the extremes<00:23:28.799> of<00:23:28.919> the<00:23:29.039> bull<00:23:29.159> market<00:23:29.340> a<00:23:29.640> thousand 00:23:29.930 --> 00:23:29.940 align:start position:0% extremes of the bull market a thousand 00:23:29.940 --> 00:23:30.970 align:start position:0% extremes of the bull market a thousand dollars 00:23:30.970 --> 00:23:30.980 align:start position:0% dollars 00:23:30.980 --> 00:23:32.990 align:start position:0% dollars obviously<00:23:31.980> this<00:23:32.280> isn't<00:23:32.520> a<00:23:32.640> particularly 00:23:32.990 --> 00:23:33.000 align:start position:0% obviously this isn't a particularly 00:23:33.000 --> 00:23:35.930 align:start position:0% obviously this isn't a particularly scalable<00:23:33.480> solution<00:23:34.100> and<00:23:35.100> so<00:23:35.220> this<00:23:35.460> can<00:23:35.580> be<00:23:35.760> a 00:23:35.930 --> 00:23:35.940 align:start position:0% scalable solution and so this can be a 00:23:35.940 --> 00:23:38.149 align:start position:0% scalable solution and so this can be a substantial<00:23:36.600> barrier<00:23:37.080> to<00:23:37.260> DNS<00:23:37.679> integration 00:23:38.149 --> 00:23:38.159 align:start position:0% substantial barrier to DNS integration 00:23:38.159 --> 00:23:40.490 align:start position:0% substantial barrier to DNS integration fortunately<00:23:39.120> we<00:23:39.419> have<00:23:39.539> a<00:23:39.720> plan<00:23:39.840> for<00:23:40.080> reducing 00:23:40.490 --> 00:23:40.500 align:start position:0% fortunately we have a plan for reducing 00:23:40.500 --> 00:23:42.169 align:start position:0% fortunately we have a plan for reducing this<00:23:40.620> all<00:23:40.919> the<00:23:41.039> way<00:23:41.100> to<00:23:41.220> zero 00:23:42.169 --> 00:23:42.179 align:start position:0% this all the way to zero 00:23:42.179 --> 00:23:45.049 align:start position:0% this all the way to zero uh<00:23:43.020> so<00:23:43.320> first<00:23:43.500> a<00:23:43.740> quick<00:23:43.860> overview<00:23:44.220> of<00:23:44.460> how<00:23:44.640> DNS 00:23:45.049 --> 00:23:45.059 align:start position:0% uh so first a quick overview of how DNS 00:23:45.059 --> 00:23:48.049 align:start position:0% uh so first a quick overview of how DNS works<00:23:45.539> it<00:23:46.320> uses<00:23:46.620> a<00:23:46.860> chain<00:23:46.980> of<00:23:47.220> trust<00:23:47.460> just<00:23:47.880> like 00:23:48.049 --> 00:23:48.059 align:start position:0% works it uses a chain of trust just like 00:23:48.059 --> 00:23:50.870 align:start position:0% works it uses a chain of trust just like SSL<00:23:48.740> the<00:23:49.740> root<00:23:49.980> zone<00:23:50.220> is<00:23:50.340> signed<00:23:50.700> by<00:23:50.760> a 00:23:50.870 --> 00:23:50.880 align:start position:0% SSL the root zone is signed by a 00:23:50.880 --> 00:23:52.789 align:start position:0% SSL the root zone is signed by a well-known<00:23:51.179> certificate<00:23:51.720> Authority<00:23:52.200> and 00:23:52.789 --> 00:23:52.799 align:start position:0% well-known certificate Authority and 00:23:52.799 --> 00:23:54.350 align:start position:0% well-known certificate Authority and they<00:23:53.100> sign<00:23:53.400> keys<00:23:53.880> for<00:23:54.000> each<00:23:54.120> of<00:23:54.240> the 00:23:54.350 --> 00:23:54.360 align:start position:0% they sign keys for each of the 00:23:54.360 --> 00:23:58.070 align:start position:0% they sign keys for each of the subdomains<00:23:54.900> such<00:23:55.080> as.com<00:23:55.679> dot<00:23:56.100> link<00:23:56.520> Etc<00:23:57.080> uh 00:23:58.070 --> 00:23:58.080 align:start position:0% subdomains such as.com dot link Etc uh 00:23:58.080 --> 00:24:00.230 align:start position:0% subdomains such as.com dot link Etc uh each<00:23:58.559> of<00:23:58.679> those<00:23:58.740> zones<00:23:59.100> uses<00:23:59.460> its<00:23:59.820> keys<00:24:00.059> to 00:24:00.230 --> 00:24:00.240 align:start position:0% each of those zones uses its keys to 00:24:00.240 --> 00:24:02.630 align:start position:0% each of those zones uses its keys to sign<00:24:00.419> this<00:24:00.860> subdomains<00:24:01.860> and<00:24:02.100> so<00:24:02.220> on<00:24:02.340> and<00:24:02.460> so 00:24:02.630 --> 00:24:02.640 align:start position:0% sign this subdomains and so on and so 00:24:02.640 --> 00:24:05.510 align:start position:0% sign this subdomains and so on and so forth<00:24:02.940> our<00:24:03.720> current<00:24:03.960> DNS<00:24:04.440> integration<00:24:04.919> uses 00:24:05.510 --> 00:24:05.520 align:start position:0% forth our current DNS integration uses 00:24:05.520 --> 00:24:07.610 align:start position:0% forth our current DNS integration uses this<00:24:05.700> to<00:24:05.940> allow<00:24:06.179> users<00:24:06.480> to<00:24:06.720> claim<00:24:06.960> DNS<00:24:07.440> names 00:24:07.610 --> 00:24:07.620 align:start position:0% this to allow users to claim DNS names 00:24:07.620 --> 00:24:10.490 align:start position:0% this to allow users to claim DNS names inside<00:24:08.039> DNS<00:24:08.700> our<00:24:09.240> front<00:24:09.480> end<00:24:09.720> collects<00:24:10.140> up<00:24:10.260> all 00:24:10.490 --> 00:24:10.500 align:start position:0% inside DNS our front end collects up all 00:24:10.500 --> 00:24:12.230 align:start position:0% inside DNS our front end collects up all the<00:24:10.679> complete<00:24:10.980> set<00:24:11.100> of<00:24:11.280> proofs<00:24:11.580> necessary<00:24:11.940> and 00:24:12.230 --> 00:24:12.240 align:start position:0% the complete set of proofs necessary and 00:24:12.240 --> 00:24:14.330 align:start position:0% the complete set of proofs necessary and submits<00:24:12.659> them<00:24:12.780> to<00:24:12.960> a<00:24:13.080> Smart<00:24:13.200> contract<00:24:13.679> which 00:24:14.330 --> 00:24:14.340 align:start position:0% submits them to a Smart contract which 00:24:14.340 --> 00:24:15.950 align:start position:0% submits them to a Smart contract which verifies<00:24:14.820> the<00:24:15.000> signatures<00:24:15.419> and<00:24:15.659> if<00:24:15.840> they 00:24:15.950 --> 00:24:15.960 align:start position:0% verifies the signatures and if they 00:24:15.960 --> 00:24:18.169 align:start position:0% verifies the signatures and if they match<00:24:16.140> it<00:24:16.320> lets<00:24:16.679> them<00:24:16.740> claim<00:24:17.039> the<00:24:17.159> name 00:24:18.169 --> 00:24:18.179 align:start position:0% match it lets them claim the name 00:24:18.179 --> 00:24:20.029 align:start position:0% match it lets them claim the name uh<00:24:18.720> if<00:24:18.900> you've<00:24:19.140> been<00:24:19.260> paying<00:24:19.559> attention<00:24:19.799> to 00:24:20.029 --> 00:24:20.039 align:start position:0% uh if you've been paying attention to 00:24:20.039 --> 00:24:21.890 align:start position:0% uh if you've been paying attention to the<00:24:20.220> talk<00:24:20.340> so<00:24:20.700> far<00:24:20.880> this<00:24:21.299> may<00:24:21.480> sound<00:24:21.659> quite 00:24:21.890 --> 00:24:21.900 align:start position:0% the talk so far this may sound quite 00:24:21.900 --> 00:24:24.110 align:start position:0% the talk so far this may sound quite familiar<00:24:22.320> to<00:24:22.500> you<00:24:22.760> similar<00:24:23.760> to<00:24:23.880> something 00:24:24.110 --> 00:24:24.120 align:start position:0% familiar to you similar to something 00:24:24.120 --> 00:24:26.870 align:start position:0% familiar to you similar to something else<00:24:24.299> we've<00:24:24.539> discussed<00:24:25.020> ccip<00:24:25.620> read<00:24:25.980> if<00:24:26.760> we 00:24:26.870 --> 00:24:26.880 align:start position:0% else we've discussed ccip read if we 00:24:26.880 --> 00:24:29.210 align:start position:0% else we've discussed ccip read if we treat<00:24:27.000> the<00:24:27.179> whole<00:24:27.360> of<00:24:27.539> ens<00:24:27.960> as<00:24:28.440> a<00:24:28.919> massive 00:24:29.210 --> 00:24:29.220 align:start position:0% treat the whole of ens as a massive 00:24:29.220 --> 00:24:31.490 align:start position:0% treat the whole of ens as a massive off-chain<00:24:29.760> distributed<00:24:30.360> database<00:24:30.780> we<00:24:31.380> can 00:24:31.490 --> 00:24:31.500 align:start position:0% off-chain distributed database we can 00:24:31.500 --> 00:24:33.950 align:start position:0% off-chain distributed database we can have<00:24:31.620> a<00:24:31.799> Gateway<00:24:32.100> that<00:24:32.460> fetches<00:24:32.880> DNS<00:24:33.539> data 00:24:33.950 --> 00:24:33.960 align:start position:0% have a Gateway that fetches DNS data 00:24:33.960 --> 00:24:36.409 align:start position:0% have a Gateway that fetches DNS data collects<00:24:34.919> all<00:24:34.980> the<00:24:35.159> proofs<00:24:35.400> necessary<00:24:35.820> and 00:24:36.409 --> 00:24:36.419 align:start position:0% collects all the proofs necessary and 00:24:36.419 --> 00:24:38.750 align:start position:0% collects all the proofs necessary and submits<00:24:36.840> it<00:24:36.960> to<00:24:37.080> the<00:24:37.200> chain<00:24:37.380> just<00:24:37.919> like<00:24:38.159> when 00:24:38.750 --> 00:24:38.760 align:start position:0% submits it to the chain just like when 00:24:38.760 --> 00:24:40.789 align:start position:0% submits it to the chain just like when you're<00:24:38.880> resolving<00:24:39.360> a<00:24:39.480> name<00:24:39.659> so<00:24:40.320> then<00:24:40.500> we<00:24:40.740> can 00:24:40.789 --> 00:24:40.799 align:start position:0% you're resolving a name so then we can 00:24:40.799 --> 00:24:43.310 align:start position:0% you're resolving a name so then we can write<00:24:40.980> a<00:24:41.280> resolver<00:24:41.700> for<00:24:41.940> DNS<00:24:42.419> names<00:24:42.659> that<00:24:43.020> uses 00:24:43.310 --> 00:24:43.320 align:start position:0% write a resolver for DNS names that uses 00:24:43.320 --> 00:24:46.210 align:start position:0% write a resolver for DNS names that uses that<00:24:43.559> gateway<00:24:43.919> to<00:24:44.520> resolve<00:24:45.000> names<00:24:45.539> in<00:24:45.780> ens 00:24:46.210 --> 00:24:46.220 align:start position:0% that gateway to resolve names in ens 00:24:46.220 --> 00:24:49.250 align:start position:0% that gateway to resolve names in ens entirely<00:24:47.220> using<00:24:47.520> data<00:24:47.820> stored<00:24:48.120> in<00:24:48.240> DNS<00:24:48.659> users 00:24:49.250 --> 00:24:49.260 align:start position:0% entirely using data stored in DNS users 00:24:49.260 --> 00:24:51.289 align:start position:0% entirely using data stored in DNS users can<00:24:49.380> set<00:24:49.620> DNS<00:24:50.039> records<00:24:50.580> to<00:24:50.760> configure<00:24:51.059> their 00:24:51.289 --> 00:24:51.299 align:start position:0% can set DNS records to configure their 00:24:51.299 --> 00:24:53.450 align:start position:0% can set DNS records to configure their name<00:24:51.480> and<00:24:52.140> they<00:24:52.440> will<00:24:52.559> resolve<00:24:52.980> any<00:24:53.159> from 00:24:53.450 --> 00:24:53.460 align:start position:0% name and they will resolve any from 00:24:53.460 --> 00:24:55.190 align:start position:0% name and they will resolve any from their<00:24:53.640> ens<00:24:54.000> is<00:24:54.179> supported<00:24:54.539> with<00:24:54.780> xero 00:24:55.190 --> 00:24:55.200 align:start position:0% their ens is supported with xero 00:24:55.200 --> 00:24:57.890 align:start position:0% their ens is supported with xero on-chain<00:24:55.620> transactions<00:24:56.280> necessary<00:24:56.900> claiming 00:24:57.890 --> 00:24:57.900 align:start position:0% on-chain transactions necessary claiming 00:24:57.900 --> 00:24:59.570 align:start position:0% on-chain transactions necessary claiming on<00:24:58.020> chain<00:24:58.260> may<00:24:58.559> still<00:24:58.740> be<00:24:58.919> useful<00:24:59.220> in<00:24:59.460> some 00:24:59.570 --> 00:24:59.580 align:start position:0% on chain may still be useful in some 00:24:59.580 --> 00:25:02.090 align:start position:0% on chain may still be useful in some cases<00:24:59.940> for<00:25:00.419> example<00:25:00.659> if<00:25:00.960> you<00:25:01.080> need<00:25:01.320> granular 00:25:02.090 --> 00:25:02.100 align:start position:0% cases for example if you need granular 00:25:02.100 --> 00:25:04.789 align:start position:0% cases for example if you need granular control<00:25:02.340> over<00:25:02.640> the<00:25:02.880> subdomains<00:25:03.539> but<00:25:04.380> for<00:25:04.620> most 00:25:04.789 --> 00:25:04.799 align:start position:0% control over the subdomains but for most 00:25:04.799 --> 00:25:06.649 align:start position:0% control over the subdomains but for most users<00:25:05.220> it'll<00:25:05.580> be<00:25:05.700> possible<00:25:06.000> to<00:25:06.240> claim<00:25:06.480> your 00:25:06.649 --> 00:25:06.659 align:start position:0% users it'll be possible to claim your 00:25:06.659 --> 00:25:08.390 align:start position:0% users it'll be possible to claim your DNS<00:25:07.080> name<00:25:07.320> just<00:25:07.559> by<00:25:07.740> setting<00:25:08.100> some<00:25:08.220> text 00:25:08.390 --> 00:25:08.400 align:start position:0% DNS name just by setting some text 00:25:08.400 --> 00:25:10.789 align:start position:0% DNS name just by setting some text records<00:25:09.000> we're<00:25:09.720> working<00:25:09.960> on<00:25:10.140> this<00:25:10.320> right<00:25:10.559> now 00:25:10.789 --> 00:25:10.799 align:start position:0% records we're working on this right now 00:25:10.799 --> 00:25:13.549 align:start position:0% records we're working on this right now the<00:25:11.280> DNA<00:25:11.700> SEC<00:25:11.880> Oracle<00:25:12.360> changes<00:25:12.720> are<00:25:12.900> done<00:25:13.080> and 00:25:13.549 --> 00:25:13.559 align:start position:0% the DNA SEC Oracle changes are done and 00:25:13.559 --> 00:25:15.289 align:start position:0% the DNA SEC Oracle changes are done and we're<00:25:13.740> working<00:25:13.980> on<00:25:14.159> implementing<00:25:14.640> fixes<00:25:15.059> from 00:25:15.289 --> 00:25:15.299 align:start position:0% we're working on implementing fixes from 00:25:15.299 --> 00:25:17.390 align:start position:0% we're working on implementing fixes from an<00:25:15.480> audit<00:25:15.720> before<00:25:15.960> we<00:25:16.200> roll<00:25:16.320> it<00:25:16.559> out<00:25:16.740> we<00:25:17.280> hope 00:25:17.390 --> 00:25:17.400 align:start position:0% an audit before we roll it out we hope 00:25:17.400 --> 00:25:18.950 align:start position:0% an audit before we roll it out we hope you<00:25:17.520> have<00:25:17.640> it<00:25:17.760> ready<00:25:17.820> to<00:25:18.000> go<00:25:18.059> before<00:25:18.539> the<00:25:18.840> end 00:25:18.950 --> 00:25:18.960 align:start position:0% you have it ready to go before the end 00:25:18.960 --> 00:25:21.049 align:start position:0% you have it ready to go before the end of<00:25:19.020> the<00:25:19.140> year<00:25:19.340> there's<00:25:20.340> been<00:25:20.580> a<00:25:20.700> lot<00:25:20.820> more 00:25:21.049 --> 00:25:21.059 align:start position:0% of the year there's been a lot more 00:25:21.059 --> 00:25:23.090 align:start position:0% of the year there's been a lot more going<00:25:21.299> on<00:25:21.419> and<00:25:21.659> with<00:25:21.900> ens<00:25:22.380> but<00:25:22.620> compressing 00:25:23.090 --> 00:25:23.100 align:start position:0% going on and with ens but compressing 00:25:23.100 --> 00:25:25.190 align:start position:0% going on and with ens but compressing four<00:25:23.340> years<00:25:23.580> down<00:25:24.299> into<00:25:24.480> 25<00:25:24.779> minutes 00:25:25.190 --> 00:25:25.200 align:start position:0% four years down into 25 minutes 00:25:25.200 --> 00:25:27.529 align:start position:0% four years down into 25 minutes naturally<00:25:26.100> means<00:25:26.520> I<00:25:26.820> have<00:25:26.940> to<00:25:27.179> leave<00:25:27.299> some 00:25:27.529 --> 00:25:27.539 align:start position:0% naturally means I have to leave some 00:25:27.539 --> 00:25:30.590 align:start position:0% naturally means I have to leave some things<00:25:27.720> out<00:25:28.159> just<00:25:29.159> one<00:25:29.340> more<00:25:29.520> thing<00:25:29.700> the<00:25:30.360> Dow 00:25:30.590 --> 00:25:30.600 align:start position:0% things out just one more thing the Dow 00:25:30.600 --> 00:25:32.630 align:start position:0% things out just one more thing the Dow was<00:25:30.840> nearly<00:25:31.140> a<00:25:31.260> year<00:25:31.440> old<00:25:31.679> but<00:25:31.980> still<00:25:32.159> in<00:25:32.340> its 00:25:32.630 --> 00:25:32.640 align:start position:0% was nearly a year old but still in its 00:25:32.640 --> 00:25:35.570 align:start position:0% was nearly a year old but still in its infancy<00:25:33.320> we<00:25:34.320> have<00:25:34.440> a<00:25:34.559> lot<00:25:34.679> of<00:25:34.799> a<00:25:35.159> lot<00:25:35.279> to<00:25:35.400> learn 00:25:35.570 --> 00:25:35.580 align:start position:0% infancy we have a lot of a lot to learn 00:25:35.580 --> 00:25:36.950 align:start position:0% infancy we have a lot of a lot to learn and<00:25:35.760> a<00:25:35.880> lot<00:25:35.940> to<00:25:36.120> do<00:25:36.240> and<00:25:36.480> we<00:25:36.659> need<00:25:36.779> your 00:25:36.950 --> 00:25:36.960 align:start position:0% and a lot to do and we need your 00:25:36.960 --> 00:25:39.169 align:start position:0% and a lot to do and we need your expertise<00:25:37.460> please<00:25:38.460> take<00:25:38.700> a<00:25:38.820> look<00:25:38.940> at<00:25:39.059> our 00:25:39.169 --> 00:25:39.179 align:start position:0% expertise please take a look at our 00:25:39.179 --> 00:25:42.289 align:start position:0% expertise please take a look at our governance<00:25:39.600> page<00:25:40.220> reach<00:25:41.220> out<00:25:41.279> to<00:25:41.460> ens<00:25:41.880> domains 00:25:42.289 --> 00:25:42.299 align:start position:0% governance page reach out to ens domains 00:25:42.299 --> 00:25:44.210 align:start position:0% governance page reach out to ens domains on<00:25:42.419> Twitter<00:25:42.539> see<00:25:43.200> how<00:25:43.440> you<00:25:43.559> can<00:25:43.620> get<00:25:43.740> involved 00:25:44.210 --> 00:25:44.220 align:start position:0% on Twitter see how you can get involved 00:25:44.220 --> 00:25:46.669 align:start position:0% on Twitter see how you can get involved and<00:25:44.460> help<00:25:44.700> us<00:25:44.880> build<00:25:45.240> a<00:25:45.539> truly<00:25:46.020> decentralized 00:25:46.669 --> 00:25:46.679 align:start position:0% and help us build a truly decentralized 00:25:46.679 --> 00:25:49.490 align:start position:0% and help us build a truly decentralized public<00:25:46.919> good<00:25:47.220> naming<00:25:48.000> for<00:25:48.179> web<00:25:48.299> 3. 00:25:49.490 --> 00:25:49.500 align:start position:0% public good naming for web 3. 00:25:49.500 --> 00:25:51.350 align:start position:0% public good naming for web 3. and<00:25:50.039> that's<00:25:50.340> all<00:25:50.520> I<00:25:50.700> have<00:25:50.820> for<00:25:50.880> you<00:25:51.000> thank<00:25:51.240> you 00:25:51.350 --> 00:25:51.360 align:start position:0% and that's all I have for you thank you 00:25:51.360 --> 00:25:51.780 align:start position:0% and that's all I have for you thank you very<00:25:51.480> much 00:25:51.780 --> 00:25:51.790 align:start position:0% very much 00:25:51.790 --> 00:25:56.210 align:start position:0% very much [Applause] 00:25:56.210 --> 00:25:56.220 align:start position:0% [Applause] 00:25:56.220 --> 00:25:57.830 align:start position:0% [Applause] awesome 00:25:57.830 --> 00:25:57.840 align:start position:0% awesome 00:25:57.840 --> 00:25:59.810 align:start position:0% awesome do<00:25:58.260> we<00:25:58.500> have<00:25:58.679> any<00:25:58.799> questions<00:25:58.980> for<00:25:59.279> Nick<00:25:59.460> please 00:25:59.810 --> 00:25:59.820 align:start position:0% do we have any questions for Nick please 00:25:59.820 --> 00:26:01.190 align:start position:0% do we have any questions for Nick please raise<00:26:00.059> your<00:26:00.240> hand<00:26:00.360> we'll<00:26:00.539> get<00:26:00.720> you<00:26:00.840> a<00:26:00.960> mic 00:26:01.190 --> 00:26:01.200 align:start position:0% raise your hand we'll get you a mic 00:26:01.200 --> 00:26:02.990 align:start position:0% raise your hand we'll get you a mic there's<00:26:01.919> a<00:26:02.100> lot<00:26:02.220> of<00:26:02.340> things<00:26:02.460> that<00:26:02.640> we<00:26:02.760> talked 00:26:02.990 --> 00:26:03.000 align:start position:0% there's a lot of things that we talked 00:26:03.000 --> 00:26:05.090 align:start position:0% there's a lot of things that we talked about<00:26:03.059> yeah<00:26:03.419> we<00:26:03.779> see<00:26:03.900> a<00:26:04.020> hand<00:26:04.140> over<00:26:04.320> there 00:26:05.090 --> 00:26:05.100 align:start position:0% about yeah we see a hand over there 00:26:05.100 --> 00:26:06.830 align:start position:0% about yeah we see a hand over there keep<00:26:05.460> your<00:26:05.580> hands<00:26:05.760> raised<00:26:06.059> so<00:26:06.240> we<00:26:06.419> can<00:26:06.539> find 00:26:06.830 --> 00:26:06.840 align:start position:0% keep your hands raised so we can find 00:26:06.840 --> 00:26:10.430 align:start position:0% keep your hands raised so we can find you<00:26:07.020> and<00:26:07.559> get<00:26:07.860> the<00:26:07.980> mighty<00:26:08.400> hi<00:26:09.360> Nick<00:26:09.600> thanks<00:26:10.260> a 00:26:10.430 --> 00:26:10.440 align:start position:0% you and get the mighty hi Nick thanks a 00:26:10.440 --> 00:26:11.990 align:start position:0% you and get the mighty hi Nick thanks a lot<00:26:10.500> for<00:26:10.679> the<00:26:10.860> talk 00:26:11.990 --> 00:26:12.000 align:start position:0% lot for the talk 00:26:12.000 --> 00:26:14.510 align:start position:0% lot for the talk um<00:26:12.120> one<00:26:12.419> thing<00:26:12.600> I<00:26:12.779> was<00:26:12.900> thinking<00:26:13.200> about<00:26:13.380> uh<00:26:14.159> you 00:26:14.510 --> 00:26:14.520 align:start position:0% um one thing I was thinking about uh you 00:26:14.520 --> 00:26:20.269 align:start position:0% um one thing I was thinking about uh you should<00:26:14.820> probably<00:26:15.539> be<00:26:15.840> able<00:26:16.080> to<00:26:16.260> use<00:26:17.419> ens<00:26:18.419> to<00:26:19.279> uh 00:26:20.269 --> 00:26:20.279 align:start position:0% should probably be able to use ens to uh 00:26:20.279 --> 00:26:22.850 align:start position:0% should probably be able to use ens to uh the<00:26:20.640> problem<00:26:20.760> is<00:26:21.120> when<00:26:22.080> you 00:26:22.850 --> 00:26:22.860 align:start position:0% the problem is when you 00:26:22.860 --> 00:26:27.049 align:start position:0% the problem is when you use<00:26:23.400> UI<00:26:23.940> to<00:26:24.539> to<00:26:25.020> communicate<00:26:25.500> with<00:26:25.740> a<00:26:25.980> page<00:26:26.220> the 00:26:27.049 --> 00:26:27.059 align:start position:0% use UI to to communicate with a page the 00:26:27.059 --> 00:26:30.169 align:start position:0% use UI to to communicate with a page the metamask<00:26:27.539> will<00:26:27.900> generate<00:26:28.380> you<00:26:29.000> it<00:26:30.000> will 00:26:30.169 --> 00:26:30.179 align:start position:0% metamask will generate you it will 00:26:30.179 --> 00:26:32.450 align:start position:0% metamask will generate you it will provide<00:26:30.419> a<00:26:30.600> transaction<00:26:30.960> for<00:26:31.320> you<00:26:31.460> and 00:26:32.450 --> 00:26:32.460 align:start position:0% provide a transaction for you and 00:26:32.460 --> 00:26:35.450 align:start position:0% provide a transaction for you and basically<00:26:33.000> you<00:26:33.720> have<00:26:33.840> no<00:26:34.080> idea<00:26:34.440> like<00:26:34.860> if 00:26:35.450 --> 00:26:35.460 align:start position:0% basically you have no idea like if 00:26:35.460 --> 00:26:39.110 align:start position:0% basically you have no idea like if actually<00:26:35.760> the<00:26:36.360> UI<00:26:36.919> is<00:26:37.919> the<00:26:38.100> right<00:26:38.279> UI<00:26:38.700> and<00:26:39.000> you 00:26:39.110 --> 00:26:39.120 align:start position:0% actually the UI is the right UI and you 00:26:39.120 --> 00:26:40.610 align:start position:0% actually the UI is the right UI and you if<00:26:39.360> you<00:26:39.539> are<00:26:39.600> calling<00:26:39.900> it<00:26:39.960> a<00:26:40.140> contract<00:26:40.380> you 00:26:40.610 --> 00:26:40.620 align:start position:0% if you are calling it a contract you 00:26:40.620 --> 00:26:43.250 align:start position:0% if you are calling it a contract you want<00:26:40.740> to<00:26:40.919> be<00:26:41.039> calling<00:26:41.400> and<00:26:42.059> I<00:26:42.240> guess<00:26:42.360> you<00:26:43.140> could 00:26:43.250 --> 00:26:43.260 align:start position:0% want to be calling and I guess you could 00:26:43.260 --> 00:26:48.409 align:start position:0% want to be calling and I guess you could UNS<00:26:43.919> you<00:26:44.460> could<00:26:44.640> you<00:26:44.940> you<00:26:45.539> you<00:26:45.980> could<00:26:46.980> UNS 00:26:48.409 --> 00:26:48.419 align:start position:0% UNS you could you you you could UNS 00:26:48.419 --> 00:26:52.850 align:start position:0% UNS you could you you you could UNS for<00:26:48.960> this<00:26:49.260> for<00:26:49.799> linking<00:26:50.279> both<00:26:51.240> the<00:26:51.779> the<00:26:52.380> domain 00:26:52.850 --> 00:26:52.860 align:start position:0% for this for linking both the the domain 00:26:52.860 --> 00:26:55.669 align:start position:0% for this for linking both the the domain and<00:26:53.760> the<00:26:53.940> smart<00:26:54.059> contracts<00:26:54.659> with<00:26:55.320> the<00:26:55.500> same 00:26:55.669 --> 00:26:55.679 align:start position:0% and the smart contracts with the same 00:26:55.679 --> 00:26:59.090 align:start position:0% and the smart contracts with the same ens<00:26:56.279> and<00:26:57.000> have<00:26:57.360> metamask<00:26:58.140> check<00:26:58.440> it<00:26:58.679> basically 00:26:59.090 --> 00:26:59.100 align:start position:0% ens and have metamask check it basically 00:26:59.100 --> 00:27:02.510 align:start position:0% ens and have metamask check it basically to<00:26:59.400> provide<00:26:59.760> a<00:27:00.720> lot<00:27:00.840> of<00:27:01.020> attacks<00:27:01.520> connected 00:27:02.510 --> 00:27:02.520 align:start position:0% to provide a lot of attacks connected 00:27:02.520 --> 00:27:06.409 align:start position:0% to provide a lot of attacks connected with<00:27:02.820> the<00:27:03.059> UI<00:27:03.779> yes<00:27:04.620> spoofing<00:27:05.279> yeah<00:27:06.000> definitely 00:27:06.409 --> 00:27:06.419 align:start position:0% with the UI yes spoofing yeah definitely 00:27:06.419 --> 00:27:08.330 align:start position:0% with the UI yes spoofing yeah definitely uh<00:27:07.020> better<00:27:07.320> user<00:27:07.740> insights<00:27:08.159> into 00:27:08.330 --> 00:27:08.340 align:start position:0% uh better user insights into 00:27:08.340 --> 00:27:10.730 align:start position:0% uh better user insights into transactions<00:27:09.059> is<00:27:09.240> I<00:27:09.480> think<00:27:09.600> probably<00:27:10.140> the 00:27:10.730 --> 00:27:10.740 align:start position:0% transactions is I think probably the 00:27:10.740 --> 00:27:14.330 align:start position:0% transactions is I think probably the major<00:27:11.360> adoption<00:27:12.360> barrier<00:27:12.900> and<00:27:13.260> and<00:27:13.620> fishing 00:27:14.330 --> 00:27:14.340 align:start position:0% major adoption barrier and and fishing 00:27:14.340 --> 00:27:17.830 align:start position:0% major adoption barrier and and fishing and<00:27:14.520> so<00:27:14.640> forth<00:27:14.880> fourth<00:27:15.539> issue<00:27:15.840> in<00:27:16.020> web<00:27:16.200> 3<00:27:16.440> today 00:27:17.830 --> 00:27:17.840 align:start position:0% and so forth fourth issue in web 3 today 00:27:17.840 --> 00:27:20.570 align:start position:0% and so forth fourth issue in web 3 today naming<00:27:18.840> contracts<00:27:19.260> of<00:27:19.380> the<00:27:19.500> units<00:27:19.919> names<00:27:20.039> is 00:27:20.570 --> 00:27:20.580 align:start position:0% naming contracts of the units names is 00:27:20.580 --> 00:27:22.549 align:start position:0% naming contracts of the units names is one<00:27:20.940> big<00:27:21.120> step<00:27:21.299> towards<00:27:21.720> making<00:27:21.900> that<00:27:22.140> a<00:27:22.380> bit 00:27:22.549 --> 00:27:22.559 align:start position:0% one big step towards making that a bit 00:27:22.559 --> 00:27:24.890 align:start position:0% one big step towards making that a bit better<00:27:22.740> and<00:27:23.520> in<00:27:23.700> fact<00:27:23.880> the<00:27:24.240> latest<00:27:24.360> contract 00:27:24.890 --> 00:27:24.900 align:start position:0% better and in fact the latest contract 00:27:24.900 --> 00:27:27.409 align:start position:0% better and in fact the latest contract out<00:27:25.200> dates<00:27:25.559> we're<00:27:25.740> pushing<00:27:26.159> out<00:27:26.340> uh<00:27:27.000> make<00:27:27.240> it 00:27:27.409 --> 00:27:27.419 align:start position:0% out dates we're pushing out uh make it 00:27:27.419 --> 00:27:29.690 align:start position:0% out dates we're pushing out uh make it easier<00:27:27.659> for<00:27:27.900> contracts<00:27:28.380> to<00:27:28.620> get<00:27:28.740> ens<00:27:29.279> primary 00:27:29.690 --> 00:27:29.700 align:start position:0% easier for contracts to get ens primary 00:27:29.700 --> 00:27:31.370 align:start position:0% easier for contracts to get ens primary names 00:27:31.370 --> 00:27:31.380 align:start position:0% names 00:27:31.380 --> 00:27:33.950 align:start position:0% names um<00:27:31.440> I<00:27:32.159> am<00:27:32.460> also<00:27:32.820> the<00:27:33.000> author<00:27:33.240> of<00:27:33.360> a<00:27:33.600> proposal 00:27:33.950 --> 00:27:33.960 align:start position:0% um I am also the author of a proposal 00:27:33.960 --> 00:27:35.930 align:start position:0% um I am also the author of a proposal with<00:27:34.200> Richard<00:27:34.380> Moore<00:27:34.860> on<00:27:35.220> how<00:27:35.460> to<00:27:35.640> better 00:27:35.930 --> 00:27:35.940 align:start position:0% with Richard Moore on how to better 00:27:35.940 --> 00:27:38.210 align:start position:0% with Richard Moore on how to better provide<00:27:36.480> insight<00:27:36.960> into<00:27:37.140> transactions<00:27:37.980> which 00:27:38.210 --> 00:27:38.220 align:start position:0% provide insight into transactions which 00:27:38.220 --> 00:27:40.250 align:start position:0% provide insight into transactions which is<00:27:38.340> also<00:27:38.580> very<00:27:38.760> relevant<00:27:39.120> there 00:27:40.250 --> 00:27:40.260 align:start position:0% is also very relevant there 00:27:40.260 --> 00:27:43.610 align:start position:0% is also very relevant there yeah<00:27:40.559> and<00:27:41.100> could<00:27:41.700> you<00:27:41.880> make<00:27:42.480> uh 00:27:43.610 --> 00:27:43.620 align:start position:0% yeah and could you make uh 00:27:43.620 --> 00:27:46.549 align:start position:0% yeah and could you make uh basically<00:27:44.400> the<00:27:45.120> the<00:27:45.299> calls<00:27:45.779> from<00:27:46.020> the<00:27:46.260> other 00:27:46.549 --> 00:27:46.559 align:start position:0% basically the the calls from the other 00:27:46.559 --> 00:27:48.830 align:start position:0% basically the the calls from the other side<00:27:46.919> meaning 00:27:48.830 --> 00:27:48.840 align:start position:0% side meaning 00:27:48.840 --> 00:27:52.370 align:start position:0% side meaning um<00:27:48.960> metamask<00:27:49.799> could<00:27:50.580> somehow<00:27:51.240> check<00:27:51.480> with<00:27:51.779> DNS 00:27:52.370 --> 00:27:52.380 align:start position:0% um metamask could somehow check with DNS 00:27:52.380 --> 00:27:56.390 align:start position:0% um metamask could somehow check with DNS like<00:27:53.039> what<00:27:53.340> what<00:27:53.580> this<00:27:53.880> contract<00:27:54.740> uh<00:27:55.740> is<00:27:56.159> what 00:27:56.390 --> 00:27:56.400 align:start position:0% like what what this contract uh is what 00:27:56.400 --> 00:27:59.450 align:start position:0% like what what this contract uh is what ens<00:27:56.820> is<00:27:57.059> this<00:27:57.179> contract<00:27:57.480> associated<00:27:58.140> with 00:27:59.450 --> 00:27:59.460 align:start position:0% ens is this contract associated with 00:27:59.460 --> 00:28:03.409 align:start position:0% ens is this contract associated with yes<00:28:00.240> and<00:28:00.900> further<00:28:01.260> you<00:28:01.500> could<00:28:01.880> put<00:28:02.880> authorized 00:28:03.409 --> 00:28:03.419 align:start position:0% yes and further you could put authorized 00:28:03.419 --> 00:28:05.210 align:start position:0% yes and further you could put authorized frontings<00:28:03.840> and<00:28:04.020> your<00:28:04.200> ens<00:28:04.500> records<00:28:04.980> so<00:28:05.100> that 00:28:05.210 --> 00:28:05.220 align:start position:0% frontings and your ens records so that 00:28:05.220 --> 00:28:06.890 align:start position:0% frontings and your ens records so that will<00:28:05.460> warn<00:28:05.760> you<00:28:05.880> if<00:28:06.360> you're<00:28:06.480> making<00:28:06.659> a 00:28:06.890 --> 00:28:06.900 align:start position:0% will warn you if you're making a 00:28:06.900 --> 00:28:08.870 align:start position:0% will warn you if you're making a transaction<00:28:07.200> to<00:28:07.500> say<00:28:07.620> uniswap<00:28:08.220> from<00:28:08.400> a<00:28:08.520> scammy 00:28:08.870 --> 00:28:08.880 align:start position:0% transaction to say uniswap from a scammy 00:28:08.880 --> 00:28:09.649 align:start position:0% transaction to say uniswap from a scammy site 00:28:09.649 --> 00:28:09.659 align:start position:0% site 00:28:09.659 --> 00:28:11.630 align:start position:0% site is<00:28:10.020> an<00:28:10.140> excellent<00:28:10.440> idea<00:28:10.799> yeah<00:28:11.340> perfect 00:28:11.630 --> 00:28:11.640 align:start position:0% is an excellent idea yeah perfect 00:28:11.640 --> 00:28:14.750 align:start position:0% is an excellent idea yeah perfect perfect<00:28:11.940> thanks<00:28:12.299> cool<00:28:12.900> thank<00:28:13.260> you<00:28:13.380> very<00:28:13.440> much 00:28:14.750 --> 00:28:14.760 align:start position:0% perfect thanks cool thank you very much 00:28:14.760 --> 00:28:16.430 align:start position:0% perfect thanks cool thank you very much awesome<00:28:15.120> we<00:28:15.419> have<00:28:15.539> one<00:28:15.659> last<00:28:15.779> question<00:28:16.080> here 00:28:16.430 --> 00:28:16.440 align:start position:0% awesome we have one last question here 00:28:16.440 --> 00:28:19.310 align:start position:0% awesome we have one last question here just<00:28:16.860> at<00:28:17.100> the<00:28:17.220> front<00:28:17.520> row<00:28:17.880> and<00:28:18.419> uh<00:28:18.659> it<00:28:19.080> won't<00:28:19.200> be 00:28:19.310 --> 00:28:19.320 align:start position:0% just at the front row and uh it won't be 00:28:19.320 --> 00:28:20.930 align:start position:0% just at the front row and uh it won't be a<00:28:19.500> time 00:28:20.930 --> 00:28:20.940 align:start position:0% a time 00:28:20.940 --> 00:28:22.669 align:start position:0% a time oh<00:28:21.299> hi<00:28:21.480> I<00:28:21.659> was<00:28:21.720> wondering<00:28:22.020> if<00:28:22.200> you<00:28:22.320> could<00:28:22.500> kind 00:28:22.669 --> 00:28:22.679 align:start position:0% oh hi I was wondering if you could kind 00:28:22.679 --> 00:28:24.529 align:start position:0% oh hi I was wondering if you could kind of<00:28:22.740> give<00:28:22.919> us<00:28:23.039> a<00:28:23.340> state<00:28:23.520> of<00:28:23.700> the<00:28:23.820> union<00:28:24.000> on 00:28:24.529 --> 00:28:24.539 align:start position:0% of give us a state of the union on 00:28:24.539 --> 00:28:27.230 align:start position:0% of give us a state of the union on efforts<00:28:25.020> to<00:28:25.320> resolve<00:28:25.679> Pages<00:28:25.980> via<00:28:26.640> browsers 00:28:27.230 --> 00:28:27.240 align:start position:0% efforts to resolve Pages via browsers 00:28:27.240 --> 00:28:29.149 align:start position:0% efforts to resolve Pages via browsers and<00:28:27.600> at<00:28:27.960> the<00:28:28.080> OS<00:28:28.320> level 00:28:29.149 --> 00:28:29.159 align:start position:0% and at the OS level 00:28:29.159 --> 00:28:32.450 align:start position:0% and at the OS level sure<00:28:29.760> uh<00:28:30.360> so<00:28:30.480> at<00:28:30.720> the<00:28:30.840> OS<00:28:31.080> level<00:28:31.260> is<00:28:31.799> depending 00:28:32.450 --> 00:28:32.460 align:start position:0% sure uh so at the OS level is depending 00:28:32.460 --> 00:28:34.669 align:start position:0% sure uh so at the OS level is depending on<00:28:32.520> you<00:28:32.640> look<00:28:32.820> at<00:28:32.940> it<00:28:33.059> tricky<00:28:33.419> or<00:28:33.539> easy<00:28:33.720> you<00:28:34.620> can 00:28:34.669 --> 00:28:34.679 align:start position:0% on you look at it tricky or easy you can 00:28:34.679 --> 00:28:36.350 align:start position:0% on you look at it tricky or easy you can run<00:28:34.799> your<00:28:34.980> own<00:28:35.100> DNS<00:28:35.520> resolver<00:28:35.940> in<00:28:36.059> which<00:28:36.240> case 00:28:36.350 --> 00:28:36.360 align:start position:0% run your own DNS resolver in which case 00:28:36.360 --> 00:28:38.390 align:start position:0% run your own DNS resolver in which case you<00:28:36.720> personally<00:28:37.080> get<00:28:37.320> to<00:28:37.500> resolve<00:28:37.860> all<00:28:37.919> units 00:28:38.390 --> 00:28:38.400 align:start position:0% you personally get to resolve all units 00:28:38.400 --> 00:28:40.490 align:start position:0% you personally get to resolve all units names<00:28:38.580> getting<00:28:39.179> it<00:28:39.419> rolled<00:28:39.779> out<00:28:39.900> to<00:28:40.200> everybody 00:28:40.490 --> 00:28:40.500 align:start position:0% names getting it rolled out to everybody 00:28:40.500 --> 00:28:43.909 align:start position:0% names getting it rolled out to everybody is<00:28:41.460> a<00:28:41.820> very<00:28:42.059> Steep<00:28:42.480> Hill<00:28:42.659> to<00:28:42.900> climb 00:28:43.909 --> 00:28:43.919 align:start position:0% is a very Steep Hill to climb 00:28:43.919 --> 00:28:45.110 align:start position:0% is a very Steep Hill to climb um<00:28:44.039> I<00:28:44.220> think<00:28:44.340> we're<00:28:44.520> going<00:28:44.700> to<00:28:44.820> have<00:28:44.880> more 00:28:45.110 --> 00:28:45.120 align:start position:0% um I think we're going to have more 00:28:45.120 --> 00:28:46.549 align:start position:0% um I think we're going to have more success<00:28:45.419> getting<00:28:45.659> this<00:28:45.840> integration<00:28:46.320> to 00:28:46.549 --> 00:28:46.559 align:start position:0% success getting this integration to 00:28:46.559 --> 00:28:48.289 align:start position:0% success getting this integration to browsers<00:28:46.860> such<00:28:47.220> as<00:28:47.340> Brave<00:28:47.580> and<00:28:47.760> Opera<00:28:48.120> which 00:28:48.289 --> 00:28:48.299 align:start position:0% browsers such as Brave and Opera which 00:28:48.299 --> 00:28:50.450 align:start position:0% browsers such as Brave and Opera which already<00:28:48.480> support<00:28:48.779> it<00:28:49.279> rather<00:28:50.279> than 00:28:50.450 --> 00:28:50.460 align:start position:0% already support it rather than 00:28:50.460 --> 00:28:52.690 align:start position:0% already support it rather than integrated<00:28:50.880> directly<00:28:51.360> with<00:28:51.539> os's 00:28:52.690 --> 00:28:52.700 align:start position:0% integrated directly with os's 00:28:52.700 --> 00:28:54.890 align:start position:0% integrated directly with os's on<00:28:53.700> the<00:28:53.760> other<00:28:53.820> hand<00:28:54.000> there<00:28:54.299> are<00:28:54.480> efforts 00:28:54.890 --> 00:28:54.900 align:start position:0% on the other hand there are efforts 00:28:54.900 --> 00:28:57.529 align:start position:0% on the other hand there are efforts around<00:28:55.220> talking<00:28:56.220> to<00:28:56.400> Ethiopia<00:28:56.940> about<00:28:57.299> whether 00:28:57.529 --> 00:28:57.539 align:start position:0% around talking to Ethiopia about whether 00:28:57.539 --> 00:28:59.409 align:start position:0% around talking to Ethiopia about whether they<00:28:57.840> would<00:28:57.960> be<00:28:58.080> willing<00:28:58.320> to<00:28:58.559> relinquish<00:28:59.039> that 00:28:59.409 --> 00:28:59.419 align:start position:0% they would be willing to relinquish that 00:28:59.419 --> 00:29:02.390 align:start position:0% they would be willing to relinquish that this<00:29:00.419> is<00:29:00.600> all<00:29:00.840> very<00:29:01.080> nascent<00:29:01.740> however<00:29:02.100> so 00:29:02.390 --> 00:29:02.400 align:start position:0% this is all very nascent however so 00:29:02.400 --> 00:29:04.850 align:start position:0% this is all very nascent however so there's<00:29:02.580> there's<00:29:03.059> nothing<00:29:03.360> uh<00:29:04.080> concrete<00:29:04.679> for 00:29:04.850 --> 00:29:04.860 align:start position:0% there's there's nothing uh concrete for 00:29:04.860 --> 00:29:07.070 align:start position:0% there's there's nothing uh concrete for that<00:29:05.039> right<00:29:05.340> now<00:29:05.520> the<00:29:06.059> shorter<00:29:06.419> term<00:29:06.600> solution 00:29:07.070 --> 00:29:07.080 align:start position:0% that right now the shorter term solution 00:29:07.080 --> 00:29:09.529 align:start position:0% that right now the shorter term solution is<00:29:07.260> as<00:29:07.500> I<00:29:07.740> said<00:29:07.919> browsers<00:29:08.340> I<00:29:08.580> think 00:29:09.529 --> 00:29:09.539 align:start position:0% is as I said browsers I think 00:29:09.539 --> 00:29:11.149 align:start position:0% is as I said browsers I think awesome<00:29:10.140> that's<00:29:10.440> all<00:29:10.620> the<00:29:10.740> time<00:29:10.860> we<00:29:10.980> have 00:29:11.149 --> 00:29:11.159 align:start position:0% awesome that's all the time we have 00:29:11.159 --> 00:29:13.800 align:start position:0% awesome that's all the time we have please<00:29:11.460> give<00:29:11.700> Nick<00:29:11.880> a<00:29:12.179> big<00:29:12.299> round<00:29:12.419> of<00:29:12.600> applause 00:29:13.800 --> 00:29:13.810 align:start position:0% please give Nick a big round of applause 00:29:13.810 --> 00:29:17.890 align:start position:0% please give Nick a big round of applause [Applause]