WEBVTT Kind: captions Language: en 00:00:01.160 --> 00:00:06.690 align:start position:0% [Music] 00:00:06.690 --> 00:00:06.700 align:start position:0% 00:00:06.700 --> 00:00:09.020 align:start position:0% [Music] 00:00:09.020 --> 00:00:09.030 align:start position:0% [Music] 00:00:09.030 --> 00:00:12.230 align:start position:0% [Music] [Applause] 00:00:12.230 --> 00:00:12.240 align:start position:0% 00:00:12.240 --> 00:00:14.350 align:start position:0% good<00:00:12.400> morning<00:00:12.759> everyone<00:00:13.759> how's<00:00:14.000> everyone 00:00:14.350 --> 00:00:14.360 align:start position:0% good morning everyone how's everyone 00:00:14.360 --> 00:00:16.990 align:start position:0% good morning everyone how's everyone today 00:00:16.990 --> 00:00:17.000 align:start position:0% today 00:00:17.000 --> 00:00:19.390 align:start position:0% today good<00:00:18.000> my<00:00:18.119> name<00:00:18.240> is<00:00:18.359> Jeff<00:00:18.560> LA<00:00:19.000> and<00:00:19.119> I'm<00:00:19.279> a 00:00:19.390 --> 00:00:19.400 align:start position:0% good my name is Jeff LA and I'm a 00:00:19.400 --> 00:00:22.070 align:start position:0% good my name is Jeff LA and I'm a co-founder<00:00:19.840> of<00:00:20.160> En<00:00:21.160> traditionally<00:00:21.720> this<00:00:21.840> talk 00:00:22.070 --> 00:00:22.080 align:start position:0% co-founder of En traditionally this talk 00:00:22.080 --> 00:00:23.870 align:start position:0% co-founder of En traditionally this talk is<00:00:22.199> done<00:00:22.359> by<00:00:22.480> Nick<00:00:22.680> Johnson<00:00:23.119> but<00:00:23.240> sadly<00:00:23.599> he<00:00:23.720> had 00:00:23.870 --> 00:00:23.880 align:start position:0% is done by Nick Johnson but sadly he had 00:00:23.880 --> 00:00:25.990 align:start position:0% is done by Nick Johnson but sadly he had not<00:00:24.080> make<00:00:24.279> it<00:00:24.640> here<00:00:24.840> today<00:00:25.160> out<00:00:25.359> to<00:00:25.519> Thailand 00:00:25.990 --> 00:00:26.000 align:start position:0% not make it here today out to Thailand 00:00:26.000 --> 00:00:28.950 align:start position:0% not make it here today out to Thailand so<00:00:26.160> instead<00:00:27.039> I'll<00:00:27.240> be<00:00:27.400> talking<00:00:27.640> to<00:00:27.760> you 00:00:28.950 --> 00:00:28.960 align:start position:0% so instead I'll be talking to you 00:00:28.960 --> 00:00:31.429 align:start position:0% so instead I'll be talking to you instead<00:00:30.039> the<00:00:30.199> last<00:00:30.359> time<00:00:30.480> I<00:00:30.560> did<00:00:30.720> an<00:00:30.840> ens<00:00:31.199> state 00:00:31.429 --> 00:00:31.439 align:start position:0% instead the last time I did an ens state 00:00:31.439 --> 00:00:34.750 align:start position:0% instead the last time I did an ens state of<00:00:31.560> ens<00:00:31.920> talk<00:00:32.200> was<00:00:32.320> in<00:00:32.480> 2018<00:00:33.480> at<00:00:33.719> Prague<00:00:34.480> who 00:00:34.750 --> 00:00:34.760 align:start position:0% of ens talk was in 2018 at Prague who 00:00:34.760 --> 00:00:36.950 align:start position:0% of ens talk was in 2018 at Prague who here<00:00:35.079> hands<00:00:35.280> up<00:00:35.440> who<00:00:35.559> here<00:00:35.680> was<00:00:35.800> at<00:00:35.879> Devcon<00:00:36.280> 4 00:00:36.950 --> 00:00:36.960 align:start position:0% here hands up who here was at Devcon 4 00:00:36.960 --> 00:00:39.430 align:start position:0% here hands up who here was at Devcon 4 Prague<00:00:37.960> wow<00:00:38.440> wow<00:00:38.760> that's<00:00:38.960> actually<00:00:39.120> more<00:00:39.280> than 00:00:39.430 --> 00:00:39.440 align:start position:0% Prague wow wow that's actually more than 00:00:39.440 --> 00:00:42.510 align:start position:0% Prague wow wow that's actually more than I<00:00:39.559> thought<00:00:40.440> at<00:00:40.680> that<00:00:40.960> time<00:00:41.600> 5<00:00:41.879> years<00:00:42.079> ago<00:00:42.399> we 00:00:42.510 --> 00:00:42.520 align:start position:0% I thought at that time 5 years ago we 00:00:42.520 --> 00:00:44.869 align:start position:0% I thought at that time 5 years ago we were<00:00:42.719> exploring<00:00:43.320> the<00:00:43.480> permanent<00:00:43.879> registar 00:00:44.869 --> 00:00:44.879 align:start position:0% were exploring the permanent registar 00:00:44.879 --> 00:00:46.950 align:start position:0% were exploring the permanent registar and<00:00:45.039> migrating<00:00:45.680> from<00:00:45.840> the<00:00:46.000> vicory<00:00:46.360> auction<00:00:46.800> to 00:00:46.950 --> 00:00:46.960 align:start position:0% and migrating from the vicory auction to 00:00:46.960 --> 00:00:50.430 align:start position:0% and migrating from the vicory auction to the<00:00:47.120> commit<00:00:47.399> reveal<00:00:47.920> registration<00:00:48.840> of<00:00:49.440> today 00:00:50.430 --> 00:00:50.440 align:start position:0% the commit reveal registration of today 00:00:50.440 --> 00:00:52.950 align:start position:0% the commit reveal registration of today since<00:00:50.760> last<00:00:51.039> time<00:00:51.559> so<00:00:51.840> much<00:00:52.039> has<00:00:52.239> changed<00:00:52.840> and 00:00:52.950 --> 00:00:52.960 align:start position:0% since last time so much has changed and 00:00:52.960 --> 00:00:54.470 align:start position:0% since last time so much has changed and I'll<00:00:53.120> be<00:00:53.359> talking<00:00:53.719> about<00:00:54.039> some<00:00:54.160> of<00:00:54.320> those 00:00:54.470 --> 00:00:54.480 align:start position:0% I'll be talking about some of those 00:00:54.480 --> 00:00:57.069 align:start position:0% I'll be talking about some of those things 00:00:57.069 --> 00:00:57.079 align:start position:0% 00:00:57.079 --> 00:01:01.110 align:start position:0% today<00:00:58.079> so<00:00:58.239> who<00:00:58.440> here<00:00:58.640> has<00:00:58.760> heard<00:00:58.920> of<00:00:59.039> ens 00:01:01.110 --> 00:01:01.120 align:start position:0% today so who here has heard of ens 00:01:01.120 --> 00:01:02.590 align:start position:0% today so who here has heard of ens right<00:01:01.320> that's<00:01:01.480> pretty<00:01:01.680> much<00:01:01.920> everyone<00:01:02.359> that's 00:01:02.590 --> 00:01:02.600 align:start position:0% right that's pretty much everyone that's 00:01:02.600 --> 00:01:05.149 align:start position:0% right that's pretty much everyone that's good<00:01:02.879> that's<00:01:03.120> good<00:01:03.719> um<00:01:04.320> vitalic<00:01:04.760> said<00:01:04.920> this<00:01:05.040> in 00:01:05.149 --> 00:01:05.159 align:start position:0% good that's good um vitalic said this in 00:01:05.159 --> 00:01:08.429 align:start position:0% good that's good um vitalic said this in 2024<00:01:05.880> en<00:01:06.280> is<00:01:06.400> our<00:01:06.640> most<00:01:07.439> successful 00:01:08.429 --> 00:01:08.439 align:start position:0% 2024 en is our most successful 00:01:08.439 --> 00:01:17.230 align:start position:0% 2024 en is our most successful non-financial<00:01:09.280> application<00:01:10.240> on<00:01:10.759> ethereum 00:01:17.230 --> 00:01:17.240 align:start position:0% 00:01:17.240 --> 00:01:19.910 align:start position:0% and<00:01:18.240> and<00:01:18.439> I'll<00:01:18.640> go<00:01:18.759> into<00:01:19.040> a<00:01:19.159> little<00:01:19.439> bit<00:01:19.759> of 00:01:19.910 --> 00:01:19.920 align:start position:0% and and I'll go into a little bit of 00:01:19.920 --> 00:01:22.270 align:start position:0% and and I'll go into a little bit of what<00:01:20.079> ens<00:01:20.600> is<00:01:20.920> for<00:01:21.320> the<00:01:21.439> very<00:01:21.600> few<00:01:21.880> people<00:01:22.119> out 00:01:22.270 --> 00:01:22.280 align:start position:0% what ens is for the very few people out 00:01:22.280 --> 00:01:25.590 align:start position:0% what ens is for the very few people out there<00:01:22.400> who<00:01:22.520> don't<00:01:22.680> know<00:01:22.880> what<00:01:22.960> it<00:01:23.560> is<00:01:24.560> so<00:01:24.840> ens 00:01:25.590 --> 00:01:25.600 align:start position:0% there who don't know what it is so ens 00:01:25.600 --> 00:01:29.630 align:start position:0% there who don't know what it is so ens is<00:01:25.840> a<00:01:26.119> user<00:01:26.799> experience<00:01:27.799> protocol<00:01:28.799> and<00:01:29.520> that 00:01:29.630 --> 00:01:29.640 align:start position:0% is a user experience protocol and that 00:01:29.640 --> 00:01:32.230 align:start position:0% is a user experience protocol and that means<00:01:30.000> we<00:01:30.159> put<00:01:30.360> users<00:01:30.840> first<00:01:31.680> and<00:01:31.840> that<00:01:32.000> has 00:01:32.230 --> 00:01:32.240 align:start position:0% means we put users first and that has 00:01:32.240 --> 00:01:34.990 align:start position:0% means we put users first and that has multiple<00:01:32.920> meanings<00:01:33.920> we<00:01:34.079> Endeavor<00:01:34.479> to<00:01:34.680> create 00:01:34.990 --> 00:01:35.000 align:start position:0% multiple meanings we Endeavor to create 00:01:35.000 --> 00:01:36.830 align:start position:0% multiple meanings we Endeavor to create the<00:01:35.159> best<00:01:35.360> user<00:01:35.720> experience<00:01:36.360> to<00:01:36.520> make<00:01:36.680> the 00:01:36.830 --> 00:01:36.840 align:start position:0% the best user experience to make the 00:01:36.840 --> 00:01:39.910 align:start position:0% the best user experience to make the blockchain<00:01:37.520> easier<00:01:37.960> to<00:01:38.560> navigate<00:01:39.560> we<00:01:39.680> want 00:01:39.910 --> 00:01:39.920 align:start position:0% blockchain easier to navigate we want 00:01:39.920 --> 00:01:41.670 align:start position:0% blockchain easier to navigate we want our<00:01:40.079> users<00:01:40.520> to<00:01:40.680> be<00:01:40.840> a<00:01:40.960> control<00:01:41.360> of<00:01:41.479> their 00:01:41.670 --> 00:01:41.680 align:start position:0% our users to be a control of their 00:01:41.680 --> 00:01:45.109 align:start position:0% our users to be a control of their identity<00:01:42.640> creating<00:01:43.159> true<00:01:44.040> trustless 00:01:45.109 --> 00:01:45.119 align:start position:0% identity creating true trustless 00:01:45.119 --> 00:01:47.310 align:start position:0% identity creating true trustless ownership<00:01:46.119> and<00:01:46.240> the<00:01:46.399> protocol<00:01:46.840> is<00:01:46.960> built<00:01:47.200> to 00:01:47.310 --> 00:01:47.320 align:start position:0% ownership and the protocol is built to 00:01:47.320 --> 00:01:49.749 align:start position:0% ownership and the protocol is built to be<00:01:47.560> credibly<00:01:47.920> neutral<00:01:48.759> and<00:01:48.960> permissionless 00:01:49.749 --> 00:01:49.759 align:start position:0% be credibly neutral and permissionless 00:01:49.759 --> 00:01:53.990 align:start position:0% be credibly neutral and permissionless so<00:01:50.079> anyone<00:01:50.920> anywhere<00:01:51.640> can<00:01:51.759> use 00:01:53.990 --> 00:01:54.000 align:start position:0% so anyone anywhere can use 00:01:54.000 --> 00:01:57.069 align:start position:0% so anyone anywhere can use ens<00:01:55.000> 's<00:01:55.680> humble<00:01:56.079> beginning<00:01:56.520> started<00:01:56.960> with 00:01:57.069 --> 00:01:57.079 align:start position:0% ens 's humble beginning started with 00:01:57.079 --> 00:01:58.389 align:start position:0% ens 's humble beginning started with trying<00:01:57.280> to<00:01:57.399> solve<00:01:57.719> one<00:01:57.840> of<00:01:57.920> the<00:01:58.039> innate 00:01:58.389 --> 00:01:58.399 align:start position:0% trying to solve one of the innate 00:01:58.399 --> 00:02:00.350 align:start position:0% trying to solve one of the innate weaknesses<00:01:58.880> of<00:01:59.039> blockchain 00:02:00.350 --> 00:02:00.360 align:start position:0% weaknesses of blockchain 00:02:00.360 --> 00:02:02.109 align:start position:0% weaknesses of blockchain everything<00:02:00.640> is<00:02:00.759> a<00:02:00.880> long<00:02:01.200> number<00:02:01.840> in 00:02:02.109 --> 00:02:02.119 align:start position:0% everything is a long number in 00:02:02.119 --> 00:02:04.029 align:start position:0% everything is a long number in hexadecimal<00:02:03.119> and<00:02:03.240> it's<00:02:03.439> completely 00:02:04.029 --> 00:02:04.039 align:start position:0% hexadecimal and it's completely 00:02:04.039 --> 00:02:06.190 align:start position:0% hexadecimal and it's completely unreadable<00:02:05.039> so<00:02:05.280> really<00:02:05.560> how<00:02:05.680> are<00:02:05.799> we<00:02:05.920> supposed 00:02:06.190 --> 00:02:06.200 align:start position:0% unreadable so really how are we supposed 00:02:06.200 --> 00:02:08.109 align:start position:0% unreadable so really how are we supposed to<00:02:06.280> scale<00:02:06.600> to<00:02:06.920> billions<00:02:07.240> of<00:02:07.360> users<00:02:07.759> if<00:02:07.960> the 00:02:08.109 --> 00:02:08.119 align:start position:0% to scale to billions of users if the 00:02:08.119 --> 00:02:09.710 align:start position:0% to scale to billions of users if the first<00:02:08.319> thing<00:02:08.479> they<00:02:08.599> do<00:02:09.080> they<00:02:09.200> see<00:02:09.440> when<00:02:09.599> they 00:02:09.710 --> 00:02:09.720 align:start position:0% first thing they do they see when they 00:02:09.720 --> 00:02:12.390 align:start position:0% first thing they do they see when they create<00:02:09.959> a<00:02:10.080> wallet<00:02:10.560> is<00:02:10.679> see 00:02:12.390 --> 00:02:12.400 align:start position:0% create a wallet is see 00:02:12.400 --> 00:02:14.990 align:start position:0% create a wallet is see this<00:02:13.400> ens<00:02:13.840> helps<00:02:14.080> you<00:02:14.239> turn<00:02:14.519> that<00:02:14.720> into 00:02:14.990 --> 00:02:15.000 align:start position:0% this ens helps you turn that into 00:02:15.000 --> 00:02:19.309 align:start position:0% this ens helps you turn that into something<00:02:15.640> humans<00:02:16.640> understand<00:02:17.599> a<00:02:18.160> name<00:02:19.160> the 00:02:19.309 --> 00:02:19.319 align:start position:0% something humans understand a name the 00:02:19.319 --> 00:02:21.550 align:start position:0% something humans understand a name the Simplicity<00:02:20.000> of<00:02:20.120> a<00:02:20.319> name<00:02:20.640> is<00:02:20.840> familiar<00:02:21.239> to<00:02:21.400> all 00:02:21.550 --> 00:02:21.560 align:start position:0% Simplicity of a name is familiar to all 00:02:21.560 --> 00:02:24.390 align:start position:0% Simplicity of a name is familiar to all of<00:02:21.720> us<00:02:22.440> as<00:02:22.599> soon<00:02:22.800> as<00:02:22.959> we<00:02:23.120> are<00:02:23.280> born<00:02:24.120> we<00:02:24.239> are 00:02:24.390 --> 00:02:24.400 align:start position:0% of us as soon as we are born we are 00:02:24.400 --> 00:02:27.630 align:start position:0% of us as soon as we are born we are given<00:02:24.599> a<00:02:25.040> name<00:02:26.040> and<00:02:26.160> it<00:02:26.280> forms<00:02:26.760> part<00:02:26.920> of<00:02:27.040> our 00:02:27.630 --> 00:02:27.640 align:start position:0% given a name and it forms part of our 00:02:27.640 --> 00:02:30.070 align:start position:0% given a name and it forms part of our identity<00:02:28.640> whether<00:02:28.879> that<00:02:29.080> large<00:02:29.400> number 00:02:30.070 --> 00:02:30.080 align:start position:0% identity whether that large number 00:02:30.080 --> 00:02:31.750 align:start position:0% identity whether that large number sometimes<00:02:30.280> called<00:02:30.440> a<00:02:30.599> hash<00:02:31.120> represents<00:02:31.560> your 00:02:31.750 --> 00:02:31.760 align:start position:0% sometimes called a hash represents your 00:02:31.760 --> 00:02:33.869 align:start position:0% sometimes called a hash represents your identity<00:02:32.120> on<00:02:32.280> ethereum<00:02:33.120> a<00:02:33.239> decentralized 00:02:33.869 --> 00:02:33.879 align:start position:0% identity on ethereum a decentralized 00:02:33.879 --> 00:02:36.589 align:start position:0% identity on ethereum a decentralized website<00:02:34.680> or<00:02:34.879> something<00:02:35.200> else<00:02:35.599> a<00:02:35.840> name<00:02:36.200> is<00:02:36.319> an 00:02:36.589 --> 00:02:36.599 align:start position:0% website or something else a name is an 00:02:36.599 --> 00:02:40.070 align:start position:0% website or something else a name is an order<00:02:37.000> of<00:02:37.319> magnitude<00:02:38.239> more<00:02:38.480> meaningful<00:02:39.239> to 00:02:40.070 --> 00:02:40.080 align:start position:0% order of magnitude more meaningful to 00:02:40.080 --> 00:02:45.149 align:start position:0% order of magnitude more meaningful to people<00:02:41.080> and<00:02:41.280> ens<00:02:41.720> serves<00:02:42.400> humans<00:02:43.239> not 00:02:45.149 --> 00:02:45.159 align:start position:0% people and ens serves humans not 00:02:45.159 --> 00:02:47.910 align:start position:0% people and ens serves humans not machines<00:02:46.159> ens<00:02:46.599> has<00:02:46.760> several<00:02:47.080> core<00:02:47.360> principles 00:02:47.910 --> 00:02:47.920 align:start position:0% machines ens has several core principles 00:02:47.920 --> 00:02:50.630 align:start position:0% machines ens has several core principles that<00:02:48.080> make<00:02:48.280> our<00:02:48.480> protocol<00:02:49.000> user<00:02:49.400> Centric<00:02:50.400> it's 00:02:50.630 --> 00:02:50.640 align:start position:0% that make our protocol user Centric it's 00:02:50.640 --> 00:02:53.030 align:start position:0% that make our protocol user Centric it's decentralized<00:02:51.480> meaning<00:02:51.920> no<00:02:52.159> single<00:02:52.599> person 00:02:53.030 --> 00:02:53.040 align:start position:0% decentralized meaning no single person 00:02:53.040 --> 00:02:54.589 align:start position:0% decentralized meaning no single person or<00:02:53.280> entity<00:02:53.680> controls<00:02:54.080> the<00:02:54.200> levers<00:02:54.440> and 00:02:54.589 --> 00:02:54.599 align:start position:0% or entity controls the levers and 00:02:54.599 --> 00:02:57.430 align:start position:0% or entity controls the levers and buttons<00:02:55.280> that<00:02:55.440> govern<00:02:55.680> the<00:02:56.239> protocol<00:02:57.239> it's 00:02:57.430 --> 00:02:57.440 align:start position:0% buttons that govern the protocol it's 00:02:57.440 --> 00:02:59.630 align:start position:0% buttons that govern the protocol it's permissionless<00:02:58.319> so<00:02:58.640> anyone<00:02:59.000> can<00:02:59.159> register<00:02:59.480> a 00:02:59.630 --> 00:02:59.640 align:start position:0% permissionless so anyone can register a 00:02:59.640 --> 00:03:01.790 align:start position:0% permissionless so anyone can register a name<00:02:59.879> name<00:03:00.120> and<00:03:00.319> create<00:03:00.599> an<00:03:00.760> identity<00:03:01.519> without 00:03:01.790 --> 00:03:01.800 align:start position:0% name name and create an identity without 00:03:01.800 --> 00:03:03.910 align:start position:0% name name and create an identity without having<00:03:01.959> to<00:03:02.120> State<00:03:02.560> who<00:03:02.760> you<00:03:02.959> are<00:03:03.599> or<00:03:03.799> where 00:03:03.910 --> 00:03:03.920 align:start position:0% having to State who you are or where 00:03:03.920 --> 00:03:06.589 align:start position:0% having to State who you are or where you're<00:03:04.480> from<00:03:05.480> and<00:03:05.680> lastly<00:03:06.040> the<00:03:06.159> protocol 00:03:06.589 --> 00:03:06.599 align:start position:0% you're from and lastly the protocol 00:03:06.599 --> 00:03:08.830 align:start position:0% you're from and lastly the protocol itself<00:03:07.000> is<00:03:07.120> built<00:03:07.319> to<00:03:07.440> be<00:03:07.599> credibly<00:03:08.000> neutral 00:03:08.830 --> 00:03:08.840 align:start position:0% itself is built to be credibly neutral 00:03:08.840 --> 00:03:10.430 align:start position:0% itself is built to be credibly neutral this<00:03:08.959> means<00:03:09.200> we're<00:03:09.400> doing<00:03:09.640> our<00:03:09.840> best<00:03:10.040> to<00:03:10.200> not 00:03:10.430 --> 00:03:10.440 align:start position:0% this means we're doing our best to not 00:03:10.440 --> 00:03:14.190 align:start position:0% this means we're doing our best to not have<00:03:10.640> codified<00:03:11.599> privilege<00:03:12.000> actors<00:03:12.640> in<00:03:12.760> the 00:03:14.190 --> 00:03:14.200 align:start position:0% have codified privilege actors in the 00:03:14.200 --> 00:03:16.390 align:start position:0% have codified privilege actors in the system<00:03:15.200> okay<00:03:15.440> definitions<00:03:15.920> out<00:03:16.080> the<00:03:16.159> way 00:03:16.390 --> 00:03:16.400 align:start position:0% system okay definitions out the way 00:03:16.400 --> 00:03:17.869 align:start position:0% system okay definitions out the way let's<00:03:16.599> talk<00:03:16.760> about<00:03:16.920> the<00:03:17.040> year<00:03:17.239> so<00:03:17.480> far<00:03:17.760> and 00:03:17.869 --> 00:03:17.879 align:start position:0% let's talk about the year so far and 00:03:17.879 --> 00:03:19.710 align:start position:0% let's talk about the year so far and we've<00:03:18.040> had<00:03:18.120> a<00:03:18.280> really<00:03:18.480> great 00:03:19.710 --> 00:03:19.720 align:start position:0% we've had a really great 00:03:19.720 --> 00:03:21.830 align:start position:0% we've had a really great one<00:03:20.720> if<00:03:20.840> you<00:03:20.959> put<00:03:21.120> all<00:03:21.239> of<00:03:21.360> the<00:03:21.440> ens 00:03:21.830 --> 00:03:21.840 align:start position:0% one if you put all of the ens 00:03:21.840 --> 00:03:24.309 align:start position:0% one if you put all of the ens registration<00:03:22.360> durations<00:03:23.000> end<00:03:23.239> to 00:03:24.309 --> 00:03:24.319 align:start position:0% registration durations end to 00:03:24.319 --> 00:03:28.110 align:start position:0% registration durations end to end<00:03:25.319> you'd<00:03:25.560> have<00:03:25.680> to<00:03:25.799> start<00:03:26.239> 9<00:03:27.200> million<00:03:27.840> years 00:03:28.110 --> 00:03:28.120 align:start position:0% end you'd have to start 9 million years 00:03:28.120 --> 00:03:29.869 align:start position:0% end you'd have to start 9 million years ago 00:03:29.869 --> 00:03:29.879 align:start position:0% ago 00:03:29.879 --> 00:03:33.869 align:start position:0% ago in<00:03:30.040> the<00:03:30.239> late<00:03:30.599> Meine<00:03:31.319> Epoch<00:03:32.319> Earth<00:03:32.840> was<00:03:33.000> a<00:03:33.319> wild 00:03:33.869 --> 00:03:33.879 align:start position:0% in the late Meine Epoch Earth was a wild 00:03:33.879 --> 00:03:37.589 align:start position:0% in the late Meine Epoch Earth was a wild range<00:03:34.560> real<00:03:34.920> realm<00:03:35.239> of<00:03:35.879> change<00:03:36.879> saber-tooth 00:03:37.589 --> 00:03:37.599 align:start position:0% range real realm of change saber-tooth 00:03:37.599 --> 00:03:39.990 align:start position:0% range real realm of change saber-tooth tigers<00:03:38.080> stalk<00:03:38.439> sprawling<00:03:38.920> grasslands<00:03:39.680> while 00:03:39.990 --> 00:03:40.000 align:start position:0% tigers stalk sprawling grasslands while 00:03:40.000 --> 00:03:44.869 align:start position:0% tigers stalk sprawling grasslands while Earth<00:03:40.400> early<00:03:40.680> elephants<00:03:41.120> thundercross<00:03:41.720> open 00:03:44.869 --> 00:03:44.879 align:start position:0% 00:03:44.879 --> 00:03:47.390 align:start position:0% savanas<00:03:45.879> and<00:03:46.040> despite<00:03:46.400> an<00:03:46.599> abundance<00:03:47.200> of 00:03:47.390 --> 00:03:47.400 align:start position:0% savanas and despite an abundance of 00:03:47.400 --> 00:03:49.869 align:start position:0% savanas and despite an abundance of large<00:03:47.720> sharp<00:03:48.120> teeth<00:03:49.000> nobody<00:03:49.360> was<00:03:49.519> trying<00:03:49.720> to 00:03:49.869 --> 00:03:49.879 align:start position:0% large sharp teeth nobody was trying to 00:03:49.879 --> 00:03:53.190 align:start position:0% large sharp teeth nobody was trying to sell<00:03:50.280> D<00:03:50.680> Coin<00:03:50.920> to 00:03:53.190 --> 00:03:53.200 align:start position:0% 00:03:53.200 --> 00:03:55.429 align:start position:0% anyone<00:03:54.200> so<00:03:54.439> more<00:03:54.599> seriously<00:03:55.120> though<00:03:55.319> it 00:03:55.429 --> 00:03:55.439 align:start position:0% anyone so more seriously though it 00:03:55.439 --> 00:03:56.990 align:start position:0% anyone so more seriously though it illustrates<00:03:55.879> we're<00:03:56.040> Brewing<00:03:56.480> pretty<00:03:56.720> damn 00:03:56.990 --> 00:03:57.000 align:start position:0% illustrates we're Brewing pretty damn 00:03:57.000 --> 00:04:00.550 align:start position:0% illustrates we're Brewing pretty damn well<00:03:57.560> here's<00:03:57.760> the<00:03:57.879> basic<00:03:58.239> stats<00:03:59.200> nearly<00:03:59.799> 2 00:04:00.550 --> 00:04:00.560 align:start position:0% well here's the basic stats nearly 2 00:04:00.560 --> 00:04:04.670 align:start position:0% well here's the basic stats nearly 2 million<00:04:01.319> e<00:04:01.720> names<00:04:02.720> 900,000<00:04:03.560> users<00:04:04.280> of<00:04:04.439> which 00:04:04.670 --> 00:04:04.680 align:start position:0% million e names 900,000 users of which 00:04:04.680 --> 00:04:07.789 align:start position:0% million e names 900,000 users of which nearly<00:04:05.519> 200,000<00:04:06.519> have<00:04:06.640> set<00:04:06.840> up<00:04:07.000> decentralized 00:04:07.789 --> 00:04:07.799 align:start position:0% nearly 200,000 have set up decentralized 00:04:07.799 --> 00:04:09.990 align:start position:0% nearly 200,000 have set up decentralized profiles<00:04:08.599> for<00:04:08.920> themselves<00:04:09.640> which<00:04:09.760> you<00:04:09.879> can 00:04:09.990 --> 00:04:10.000 align:start position:0% profiles for themselves which you can 00:04:10.000 --> 00:04:13.750 align:start position:0% profiles for themselves which you can view<00:04:10.280> in<00:04:10.400> ethereum<00:04:10.799> F 00:04:13.750 --> 00:04:13.760 align:start position:0% 00:04:13.760 --> 00:04:17.509 align:start position:0% protool<00:04:14.760> but<00:04:14.920> ens<00:04:15.319> was<00:04:15.519> not<00:04:15.840> only<00:04:16.120> about 00:04:17.509 --> 00:04:17.519 align:start position:0% protool but ens was not only about 00:04:17.519 --> 00:04:21.069 align:start position:0% protool but ens was not only about eth<00:04:18.519> a<00:04:18.720> trer<00:04:19.160> picture<00:04:19.519> of<00:04:19.680> 's<00:04:20.280> popularity<00:04:20.959> has 00:04:21.069 --> 00:04:21.079 align:start position:0% eth a trer picture of 's popularity has 00:04:21.079 --> 00:04:23.189 align:start position:0% eth a trer picture of 's popularity has to<00:04:21.280> take<00:04:21.440> into<00:04:21.720> account<00:04:22.280> the<00:04:22.440> enormous<00:04:22.960> number 00:04:23.189 --> 00:04:23.199 align:start position:0% to take into account the enormous number 00:04:23.199 --> 00:04:25.990 align:start position:0% to take into account the enormous number of<00:04:23.360> names<00:04:24.120> using<00:04:24.479> one<00:04:24.600> of<00:04:24.759> our<00:04:25.040> many<00:04:25.479> many 00:04:25.990 --> 00:04:26.000 align:start position:0% of names using one of our many many 00:04:26.000 --> 00:04:27.950 align:start position:0% of names using one of our many many partner<00:04:26.360> Integrations<00:04:27.280> and<00:04:27.400> many<00:04:27.600> of<00:04:27.759> these 00:04:27.950 --> 00:04:27.960 align:start position:0% partner Integrations and many of these 00:04:27.960 --> 00:04:31.469 align:start position:0% partner Integrations and many of these are<00:04:28.160> completely<00:04:28.600> trustless<00:04:29.400> and<00:04:29.720> cost 00:04:31.469 --> 00:04:31.479 align:start position:0% are completely trustless and cost 00:04:31.479 --> 00:04:35.710 align:start position:0% are completely trustless and cost free<00:04:32.479> linear<00:04:33.479> Bas<00:04:34.320> and<00:04:34.520> uni<00:04:35.320> all<00:04:35.560> have 00:04:35.710 --> 00:04:35.720 align:start position:0% free linear Bas and uni all have 00:04:35.720 --> 00:04:38.310 align:start position:0% free linear Bas and uni all have released<00:04:36.120> subdomain<00:04:36.600> registrars<00:04:37.240> this<00:04:37.440> year 00:04:38.310 --> 00:04:38.320 align:start position:0% released subdomain registrars this year 00:04:38.320 --> 00:04:40.909 align:start position:0% released subdomain registrars this year linear<00:04:38.840> has<00:04:39.120> completely<00:04:39.680> trustless<00:04:40.639> on 00:04:40.909 --> 00:04:40.919 align:start position:0% linear has completely trustless on 00:04:40.919 --> 00:04:44.189 align:start position:0% linear has completely trustless on linear<00:04:41.440> L2<00:04:42.120> using<00:04:42.400> State<00:04:42.720> proof<00:04:43.120> on<00:04:43.240> L1<00:04:43.960> for 00:04:44.189 --> 00:04:44.199 align:start position:0% linear L2 using State proof on L1 for 00:04:44.199 --> 00:04:48.310 align:start position:0% linear L2 using State proof on L1 for ccip<00:04:45.199> CCI<00:04:45.919> read<00:04:46.680> verification<00:04:47.680> Bas<00:04:48.000> has<00:04:48.120> them 00:04:48.310 --> 00:04:48.320 align:start position:0% ccip CCI read verification Bas has them 00:04:48.320 --> 00:04:50.550 align:start position:0% ccip CCI read verification Bas has them also<00:04:48.520> stored<00:04:48.800> in<00:04:48.880> L2<00:04:49.479> but<00:04:49.600> uses<00:04:49.919> signature 00:04:50.550 --> 00:04:50.560 align:start position:0% also stored in L2 but uses signature 00:04:50.560 --> 00:04:52.870 align:start position:0% also stored in L2 but uses signature verification<00:04:51.560> and<00:04:51.680> uni.<00:04:52.199> E<00:04:52.479> has<00:04:52.639> them 00:04:52.870 --> 00:04:52.880 align:start position:0% verification and uni. E has them 00:04:52.880 --> 00:04:54.909 align:start position:0% verification and uni. E has them completely<00:04:53.280> offchain<00:04:53.840> and<00:04:54.000> verified<00:04:54.400> using<00:04:54.639> a 00:04:54.909 --> 00:04:54.919 align:start position:0% completely offchain and verified using a 00:04:54.919 --> 00:04:56.830 align:start position:0% completely offchain and verified using a signature<00:04:55.919> this<00:04:56.080> really<00:04:56.280> shows<00:04:56.639> the 00:04:56.830 --> 00:04:56.840 align:start position:0% signature this really shows the 00:04:56.840 --> 00:04:58.710 align:start position:0% signature this really shows the progressive<00:04:57.560> decentralization<00:04:58.560> of 00:04:58.710 --> 00:04:58.720 align:start position:0% progressive decentralization of 00:04:58.720 --> 00:05:01.029 align:start position:0% progressive decentralization of subdomains<00:04:59.280> that<00:04:59.400> can<00:04:59.720> start<00:05:00.000> simple<00:05:00.800> and 00:05:01.029 --> 00:05:01.039 align:start position:0% subdomains that can start simple and 00:05:01.039 --> 00:05:03.710 align:start position:0% subdomains that can start simple and gradually<00:05:01.479> be<00:05:01.680> made<00:05:01.919> trustless<00:05:02.759> using<00:05:03.080> l2s 00:05:03.710 --> 00:05:03.720 align:start position:0% gradually be made trustless using l2s 00:05:03.720 --> 00:05:07.350 align:start position:0% gradually be made trustless using l2s and<00:05:03.880> a<00:05:04.039> state<00:05:04.720> state<00:05:05.080> proof<00:05:05.360> with<00:05:05.520> ccip 00:05:07.350 --> 00:05:07.360 align:start position:0% and a state state proof with ccip 00:05:07.360 --> 00:05:11.070 align:start position:0% and a state state proof with ccip read<00:05:08.360> and<00:05:08.520> lastly<00:05:08.840> the,<00:05:09.520> Guerilla<00:05:10.080> coinbase 00:05:11.070 --> 00:05:11.080 align:start position:0% read and lastly the, Guerilla coinbase 00:05:11.080 --> 00:05:12.670 align:start position:0% read and lastly the, Guerilla coinbase as<00:05:11.160> of<00:05:11.360> today<00:05:11.680> coinbase<00:05:12.160> reports<00:05:12.479> they've 00:05:12.670 --> 00:05:12.680 align:start position:0% as of today coinbase reports they've 00:05:12.680 --> 00:05:15.790 align:start position:0% as of today coinbase reports they've issued<00:05:13.039> over<00:05:13.440> 12<00:05:14.240> million<00:05:14.720> cb.<00:05:15.199> ID<00:05:15.440> names 00:05:15.790 --> 00:05:15.800 align:start position:0% issued over 12 million cb. ID names 00:05:15.800 --> 00:05:20.990 align:start position:0% issued over 12 million cb. ID names their 00:05:20.990 --> 00:05:21.000 align:start position:0% 00:05:21.000 --> 00:05:23.909 align:start position:0% users<00:05:22.000> this<00:05:22.160> marks<00:05:22.520> the<00:05:22.800> largest<00:05:23.400> deployment 00:05:23.909 --> 00:05:23.919 align:start position:0% users this marks the largest deployment 00:05:23.919 --> 00:05:25.710 align:start position:0% users this marks the largest deployment of<00:05:24.039> es<00:05:24.360> names<00:05:24.600> to<00:05:24.720> end<00:05:25.000> users<00:05:25.360> since<00:05:25.560> we 00:05:25.710 --> 00:05:25.720 align:start position:0% of es names to end users since we 00:05:25.720 --> 00:05:27.510 align:start position:0% of es names to end users since we launched<00:05:26.120> and<00:05:26.280> really<00:05:26.600> demonstrating<00:05:27.319> the 00:05:27.510 --> 00:05:27.520 align:start position:0% launched and really demonstrating the 00:05:27.520 --> 00:05:29.830 align:start position:0% launched and really demonstrating the value<00:05:27.800> of<00:05:27.919> rolling<00:05:28.280> out<00:05:28.520> ens<00:05:28.960> infrastructure 00:05:29.830 --> 00:05:29.840 align:start position:0% value of rolling out ens infrastructure 00:05:29.840 --> 00:05:32.189 align:start position:0% value of rolling out ens infrastructure to<00:05:30.120> absolutely 00:05:32.189 --> 00:05:32.199 align:start position:0% to absolutely 00:05:32.199 --> 00:05:34.150 align:start position:0% to absolutely everyone<00:05:33.199> and<00:05:33.319> that<00:05:33.440> has<00:05:33.639> really<00:05:33.840> been<00:05:34.000> the 00:05:34.150 --> 00:05:34.160 align:start position:0% everyone and that has really been the 00:05:34.160 --> 00:05:36.070 align:start position:0% everyone and that has really been the theme<00:05:34.360> of<00:05:34.520> the<00:05:34.720> past<00:05:34.919> year<00:05:35.080> or<00:05:35.280> more<00:05:35.680> bringing 00:05:36.070 --> 00:05:36.080 align:start position:0% theme of the past year or more bringing 00:05:36.080 --> 00:05:40.070 align:start position:0% theme of the past year or more bringing ens<00:05:36.840> to<00:05:37.120> more<00:05:37.440> people<00:05:38.440> more<00:05:38.880> affordably<00:05:39.880> and 00:05:40.070 --> 00:05:40.080 align:start position:0% ens to more people more affordably and 00:05:40.080 --> 00:05:43.070 align:start position:0% ens to more people more affordably and with<00:05:40.240> less<00:05:40.400> knowhow<00:05:41.000> required<00:05:42.000> ccip<00:05:42.680> read<00:05:42.960> and 00:05:43.070 --> 00:05:43.080 align:start position:0% with less knowhow required ccip read and 00:05:43.080 --> 00:05:44.469 align:start position:0% with less knowhow required ccip read and offchain<00:05:43.440> names<00:05:43.680> have<00:05:43.800> been<00:05:43.960> the<00:05:44.080> foundation 00:05:44.469 --> 00:05:44.479 align:start position:0% offchain names have been the foundation 00:05:44.479 --> 00:05:46.710 align:start position:0% offchain names have been the foundation of<00:05:44.680> that<00:05:45.000> and<00:05:45.160> have<00:05:45.319> to<00:05:45.840> have<00:05:46.000> led<00:05:46.160> to<00:05:46.319> a<00:05:46.440> number 00:05:46.710 --> 00:05:46.720 align:start position:0% of that and have to have led to a number 00:05:46.720 --> 00:05:49.629 align:start position:0% of that and have to have led to a number of<00:05:47.000> hugely<00:05:47.400> successful<00:05:48.120> Integrations<00:05:49.120> almost 00:05:49.629 --> 00:05:49.639 align:start position:0% of hugely successful Integrations almost 00:05:49.639 --> 00:05:52.590 align:start position:0% of hugely successful Integrations almost 16<00:05:50.120> million<00:05:50.479> active<00:05:50.800> names<00:05:51.680> more<00:05:51.840> than<00:05:52.000> 14 00:05:52.590 --> 00:05:52.600 align:start position:0% 16 million active names more than 14 00:05:52.600 --> 00:05:55.270 align:start position:0% 16 million active names more than 14 million<00:05:53.000> more<00:05:53.280> than<00:05:53.440> do<00:05:53.639> e<00:05:53.800> names<00:05:54.000> that<00:05:54.280> exist 00:05:55.270 --> 00:05:55.280 align:start position:0% million more than do e names that exist 00:05:55.280 --> 00:05:58.430 align:start position:0% million more than do e names that exist around<00:05:55.560> 10<00:05:55.800> million<00:05:56.120> users<00:05:56.840> and<00:05:57.039> over<00:05:57.440> 400,000 00:05:58.430 --> 00:05:58.440 align:start position:0% around 10 million users and over 400,000 00:05:58.440 --> 00:06:01.270 align:start position:0% around 10 million users and over 400,000 decentralized<00:05:59.080> profiles<00:05:59.960> do<00:06:00.319> eth<00:06:00.919> only 00:06:01.270 --> 00:06:01.280 align:start position:0% decentralized profiles do eth only 00:06:01.280 --> 00:06:04.550 align:start position:0% decentralized profiles do eth only paints<00:06:01.880> a<00:06:02.199> small<00:06:02.880> picture<00:06:03.560> of<00:06:03.680> the<00:06:03.880> success<00:06:04.400> of 00:06:04.550 --> 00:06:04.560 align:start position:0% paints a small picture of the success of 00:06:04.560 --> 00:06:06.629 align:start position:0% paints a small picture of the success of ens<00:06:05.400> but<00:06:05.520> if<00:06:05.600> you<00:06:05.720> include<00:06:06.039> all<00:06:06.199> of<00:06:06.280> our<00:06:06.400> many 00:06:06.629 --> 00:06:06.639 align:start position:0% ens but if you include all of our many 00:06:06.639 --> 00:06:08.790 align:start position:0% ens but if you include all of our many partner<00:06:06.960> Integrations<00:06:07.800> you'll<00:06:08.120> really<00:06:08.400> see 00:06:08.790 --> 00:06:08.800 align:start position:0% partner Integrations you'll really see 00:06:08.800 --> 00:06:13.189 align:start position:0% partner Integrations you'll really see how<00:06:09.120> wide<00:06:09.400> ranging<00:06:10.160> ens<00:06:11.000> truly 00:06:13.189 --> 00:06:13.199 align:start position:0% how wide ranging ens truly 00:06:13.199 --> 00:06:16.589 align:start position:0% how wide ranging ens truly is<00:06:14.199> but<00:06:14.319> ens<00:06:14.759> is<00:06:14.919> not<00:06:15.080> only<00:06:15.319> about<00:06:15.599> subdomains 00:06:16.589 --> 00:06:16.599 align:start position:0% is but ens is not only about subdomains 00:06:16.599 --> 00:06:19.070 align:start position:0% is but ens is not only about subdomains our<00:06:16.919> success<00:06:17.520> is<00:06:17.960> widely<00:06:18.520> how<00:06:18.720> widely 00:06:19.070 --> 00:06:19.080 align:start position:0% our success is widely how widely 00:06:19.080 --> 00:06:21.270 align:start position:0% our success is widely how widely integrated<00:06:19.599> we<00:06:19.720> are<00:06:20.280> allowing<00:06:20.680> names<00:06:21.000> to<00:06:21.120> be 00:06:21.270 --> 00:06:21.280 align:start position:0% integrated we are allowing names to be 00:06:21.280 --> 00:06:24.589 align:start position:0% integrated we are allowing names to be used<00:06:21.919> out<00:06:22.080> in<00:06:22.240> the<00:06:22.800> wild<00:06:23.800> Integrations<00:06:24.440> are 00:06:24.589 --> 00:06:24.599 align:start position:0% used out in the wild Integrations are 00:06:24.599 --> 00:06:26.110 align:start position:0% used out in the wild Integrations are one<00:06:24.720> of<00:06:24.840> the<00:06:25.039> most<00:06:25.319> important<00:06:25.720> success 00:06:26.110 --> 00:06:26.120 align:start position:0% one of the most important success 00:06:26.120 --> 00:06:28.870 align:start position:0% one of the most important success metrics<00:06:26.479> for<00:06:26.840> ens<00:06:27.840> imagine<00:06:28.160> owning<00:06:28.440> a<00:06:28.599> Visa 00:06:28.870 --> 00:06:28.880 align:start position:0% metrics for ens imagine owning a Visa 00:06:28.880 --> 00:06:31.390 align:start position:0% metrics for ens imagine owning a Visa credit<00:06:29.199> card<00:06:29.599> but<00:06:29.759> no<00:06:29.840> one<00:06:30.000> accepts<00:06:30.319> Visa<00:06:31.280> this 00:06:31.390 --> 00:06:31.400 align:start position:0% credit card but no one accepts Visa this 00:06:31.400 --> 00:06:33.150 align:start position:0% credit card but no one accepts Visa this is<00:06:31.520> the<00:06:31.800> problem<00:06:32.199> we<00:06:32.319> need<00:06:32.479> to<00:06:32.639> tackle<00:06:33.039> by 00:06:33.150 --> 00:06:33.160 align:start position:0% is the problem we need to tackle by 00:06:33.160 --> 00:06:35.510 align:start position:0% is the problem we need to tackle by bringing<00:06:33.639> large<00:06:34.000> Integrations<00:06:34.960> that<00:06:35.199> all 00:06:35.510 --> 00:06:35.520 align:start position:0% bringing large Integrations that all 00:06:35.520 --> 00:06:37.830 align:start position:0% bringing large Integrations that all allow<00:06:35.880> the<00:06:36.000> use<00:06:36.199> of<00:06:36.319> ens<00:06:37.199> with<00:06:37.400> the<00:06:37.599> within 00:06:37.830 --> 00:06:37.840 align:start position:0% allow the use of ens with the within 00:06:37.840 --> 00:06:40.629 align:start position:0% allow the use of ens with the within their<00:06:38.039> existing<00:06:38.360> users<00:06:39.199> allowing<00:06:39.680> ens<00:06:40.319> name 00:06:40.629 --> 00:06:40.639 align:start position:0% their existing users allowing ens name 00:06:40.639 --> 00:06:43.550 align:start position:0% their existing users allowing ens name resolution<00:06:41.199> to<00:06:41.479> exist<00:06:42.240> outside<00:06:42.720> of<00:06:42.840> our<00:06:43.000> Echo 00:06:43.550 --> 00:06:43.560 align:start position:0% resolution to exist outside of our Echo 00:06:43.560 --> 00:06:45.390 align:start position:0% resolution to exist outside of our Echo chamber<00:06:44.560> and<00:06:44.680> this<00:06:44.800> year<00:06:45.000> has<00:06:45.120> been<00:06:45.240> a 00:06:45.390 --> 00:06:45.400 align:start position:0% chamber and this year has been a 00:06:45.400 --> 00:06:47.589 align:start position:0% chamber and this year has been a fantastic<00:06:46.000> year<00:06:46.160> for<00:06:46.319> Integrations<00:06:47.319> and<00:06:47.440> I'd 00:06:47.589 --> 00:06:47.599 align:start position:0% fantastic year for Integrations and I'd 00:06:47.599 --> 00:06:50.390 align:start position:0% fantastic year for Integrations and I'd like<00:06:47.759> to<00:06:47.880> tell<00:06:48.039> you<00:06:48.199> about<00:06:48.360> a<00:06:48.440> few<00:06:48.599> of<00:06:48.680> them 00:06:50.390 --> 00:06:50.400 align:start position:0% like to tell you about a few of them 00:06:50.400 --> 00:06:53.150 align:start position:0% like to tell you about a few of them today<00:06:51.400> but<00:06:51.599> first<00:06:52.000> while<00:06:52.199> not<00:06:52.479> an<00:06:52.639> integration 00:06:53.150 --> 00:06:53.160 align:start position:0% today but first while not an integration 00:06:53.160 --> 00:06:55.029 align:start position:0% today but first while not an integration specifically<00:06:54.160> I'd<00:06:54.319> like<00:06:54.440> to<00:06:54.639> quickly 00:06:55.029 --> 00:06:55.039 align:start position:0% specifically I'd like to quickly 00:06:55.039 --> 00:06:57.550 align:start position:0% specifically I'd like to quickly highlight<00:06:55.440> gasless<00:06:55.840> DNS<00:06:56.280> SEC<00:06:56.840> one<00:06:56.960> of<00:06:57.120> our 00:06:57.550 --> 00:06:57.560 align:start position:0% highlight gasless DNS SEC one of our 00:06:57.560 --> 00:07:00.230 align:start position:0% highlight gasless DNS SEC one of our biggest<00:06:58.080> technological<00:06:58.680> advances<00:06:59.319> in<00:06:59.599> ens<00:06:59.960> to 00:07:00.230 --> 00:07:00.240 align:start position:0% biggest technological advances in ens to 00:07:00.240 --> 00:07:02.790 align:start position:0% biggest technological advances in ens to date<00:07:01.240> we've<00:07:01.479> supported<00:07:01.960> DNS<00:07:02.400> top<00:07:02.599> level 00:07:02.790 --> 00:07:02.800 align:start position:0% date we've supported DNS top level 00:07:02.800 --> 00:07:05.510 align:start position:0% date we've supported DNS top level domains<00:07:03.240> inside<00:07:03.560> ens<00:07:04.120> almost<00:07:04.400> since<00:07:04.639> day<00:07:04.840> one 00:07:05.510 --> 00:07:05.520 align:start position:0% domains inside ens almost since day one 00:07:05.520 --> 00:07:06.790 align:start position:0% domains inside ens almost since day one but<00:07:05.680> importing<00:07:06.120> one<00:07:06.360> came<00:07:06.560> with<00:07:06.680> a 00:07:06.790 --> 00:07:06.800 align:start position:0% but importing one came with a 00:07:06.800 --> 00:07:10.430 align:start position:0% but importing one came with a substantial<00:07:07.599> fee<00:07:08.599> gasless<00:07:09.080> DNS<00:07:09.560> set<00:07:09.960> combines 00:07:10.430 --> 00:07:10.440 align:start position:0% substantial fee gasless DNS set combines 00:07:10.440 --> 00:07:14.070 align:start position:0% substantial fee gasless DNS set combines our<00:07:10.840> trustless<00:07:11.840> DNS<00:07:12.440> import<00:07:13.080> functionality 00:07:14.070 --> 00:07:14.080 align:start position:0% our trustless DNS import functionality 00:07:14.080 --> 00:07:16.469 align:start position:0% our trustless DNS import functionality with<00:07:14.240> the<00:07:14.440> Gateway<00:07:14.879> architecture<00:07:15.759> of<00:07:15.919> ccip 00:07:16.469 --> 00:07:16.479 align:start position:0% with the Gateway architecture of ccip 00:07:16.479 --> 00:07:19.070 align:start position:0% with the Gateway architecture of ccip read<00:07:17.319> and<00:07:17.479> makes<00:07:17.680> it<00:07:17.960> possible<00:07:18.520> to<00:07:18.720> make 00:07:19.070 --> 00:07:19.080 align:start position:0% read and makes it possible to make 00:07:19.080 --> 00:07:23.469 align:start position:0% read and makes it possible to make nearly<00:07:19.680> any<00:07:20.120> DNS<00:07:20.720> name<00:07:21.400> function<00:07:22.120> inside<00:07:22.560> ens 00:07:23.469 --> 00:07:23.479 align:start position:0% nearly any DNS name function inside ens 00:07:23.479 --> 00:07:27.270 align:start position:0% nearly any DNS name function inside ens without<00:07:23.840> transactions<00:07:24.840> or<00:07:25.160> gas<00:07:25.400> fees 00:07:27.270 --> 00:07:27.280 align:start position:0% without transactions or gas fees 00:07:27.280 --> 00:07:29.350 align:start position:0% without transactions or gas fees whatsoever<00:07:28.280> and<00:07:28.440> one<00:07:28.560> of<00:07:28.639> the<00:07:28.800> first<00:07:29.039> to<00:07:29.160> use 00:07:29.350 --> 00:07:29.360 align:start position:0% whatsoever and one of the first to use 00:07:29.360 --> 00:07:37.070 align:start position:0% whatsoever and one of the first to use the<00:07:29.520> the<00:07:29.599> power<00:07:29.800> of<00:07:29.919> gases<00:07:30.240> DNS<00:07:30.639> SEC<00:07:31.199> was 00:07:37.070 --> 00:07:37.080 align:start position:0% 00:07:37.080 --> 00:07:39.670 align:start position:0% GoDaddy<00:07:38.080> GoDaddy<00:07:38.599> added<00:07:38.879> built-in<00:07:39.319> support 00:07:39.670 --> 00:07:39.680 align:start position:0% GoDaddy GoDaddy added built-in support 00:07:39.680 --> 00:07:41.990 align:start position:0% GoDaddy GoDaddy added built-in support for<00:07:39.960> every<00:07:40.599> name<00:07:40.960> registered<00:07:41.360> through<00:07:41.560> them 00:07:41.990 --> 00:07:42.000 align:start position:0% for every name registered through them 00:07:42.000 --> 00:07:43.990 align:start position:0% for every name registered through them removing<00:07:42.440> the<00:07:42.560> usability<00:07:43.240> barrier<00:07:43.560> of 00:07:43.990 --> 00:07:44.000 align:start position:0% removing the usability barrier of 00:07:44.000 --> 00:07:46.149 align:start position:0% removing the usability barrier of understanding<00:07:44.319> how<00:07:44.440> to<00:07:44.639> set<00:07:44.800> up<00:07:45.080> DNS<00:07:45.639> SEC<00:07:46.039> and 00:07:46.149 --> 00:07:46.159 align:start position:0% understanding how to set up DNS SEC and 00:07:46.159 --> 00:07:47.950 align:start position:0% understanding how to set up DNS SEC and you<00:07:46.240> can<00:07:46.360> set<00:07:46.560> up<00:07:46.680> your<00:07:46.800> DNS<00:07:47.240> name<00:07:47.440> to<00:07:47.599> work<00:07:47.800> in 00:07:47.950 --> 00:07:47.960 align:start position:0% you can set up your DNS name to work in 00:07:47.960 --> 00:07:51.309 align:start position:0% you can set up your DNS name to work in ens<00:07:48.720> using<00:07:49.039> GoDaddy<00:07:49.840> in<00:07:50.000> just<00:07:50.120> a<00:07:50.240> few<00:07:50.440> clicks 00:07:51.309 --> 00:07:51.319 align:start position:0% ens using GoDaddy in just a few clicks 00:07:51.319 --> 00:07:54.790 align:start position:0% ens using GoDaddy in just a few clicks GoDaddy<00:07:51.919> has<00:07:52.199> over<00:07:52.840> 80<00:07:53.599> million<00:07:54.039> user<00:07:54.440> names 00:07:54.790 --> 00:07:54.800 align:start position:0% GoDaddy has over 80 million user names 00:07:54.800 --> 00:07:56.589 align:start position:0% GoDaddy has over 80 million user names registered<00:07:55.240> with<00:07:55.360> them<00:07:55.800> 20<00:07:56.199> million 00:07:56.589 --> 00:07:56.599 align:start position:0% registered with them 20 million 00:07:56.599 --> 00:07:59.550 align:start position:0% registered with them 20 million customers<00:07:57.440> and<00:07:57.639> just<00:07:57.800> as<00:07:58.080> one<00:07:58.360> integration<00:07:59.120> on 00:07:59.550 --> 00:07:59.560 align:start position:0% customers and just as one integration on 00:07:59.560 --> 00:08:01.469 align:start position:0% customers and just as one integration on it<00:07:59.680> own<00:08:00.240> vastly<00:08:00.599> improves<00:08:00.960> the<00:08:01.080> network 00:08:01.469 --> 00:08:01.479 align:start position:0% it own vastly improves the network 00:08:01.479 --> 00:08:04.230 align:start position:0% it own vastly improves the network effect<00:08:01.919> of 00:08:04.230 --> 00:08:04.240 align:start position:0% 00:08:04.240 --> 00:08:07.990 align:start position:0% ens<00:08:05.240> in<00:08:05.360> collaboration<00:08:05.840> with<00:08:05.960> 3dn<00:08:06.919> dobox<00:08:07.800> is 00:08:07.990 --> 00:08:08.000 align:start position:0% ens in collaboration with 3dn dobox is 00:08:08.000 --> 00:08:10.909 align:start position:0% ens in collaboration with 3dn dobox is the<00:08:08.479> first<00:08:08.879> truly<00:08:09.280> blockchain<00:08:09.800> native<00:08:10.520> fully 00:08:10.909 --> 00:08:10.919 align:start position:0% the first truly blockchain native fully 00:08:10.919 --> 00:08:15.149 align:start position:0% the first truly blockchain native fully ens<00:08:11.319> enabled<00:08:12.080> dnst<00:08:12.879> TLD<00:08:14.159> dotbox 00:08:15.149 --> 00:08:15.159 align:start position:0% ens enabled dnst TLD dotbox 00:08:15.159 --> 00:08:16.589 align:start position:0% ens enabled dnst TLD dotbox registrations<00:08:15.840> are<00:08:16.000> all<00:08:16.120> recorded<00:08:16.440> on 00:08:16.589 --> 00:08:16.599 align:start position:0% registrations are all recorded on 00:08:16.599 --> 00:08:18.790 align:start position:0% registrations are all recorded on ethereum<00:08:17.319> and<00:08:17.560> do<00:08:17.720> every<00:08:17.919> dotbox<00:08:18.400> name<00:08:18.639> is 00:08:18.790 --> 00:08:18.800 align:start position:0% ethereum and do every dotbox name is 00:08:18.800 --> 00:08:21.350 align:start position:0% ethereum and do every dotbox name is automatically<00:08:19.319> ens 00:08:21.350 --> 00:08:21.360 align:start position:0% automatically ens 00:08:21.360 --> 00:08:23.309 align:start position:0% automatically ens enabled<00:08:22.360> it's<00:08:22.520> not<00:08:22.639> just<00:08:22.759> the<00:08:22.840> main<00:08:23.039> related 00:08:23.309 --> 00:08:23.319 align:start position:0% enabled it's not just the main related 00:08:23.319 --> 00:08:25.029 align:start position:0% enabled it's not just the main related nanies<00:08:23.720> that<00:08:23.879> are<00:08:23.960> integrating<00:08:24.360> us<00:08:24.599> though 00:08:25.029 --> 00:08:25.039 align:start position:0% nanies that are integrating us though 00:08:25.039 --> 00:08:27.629 align:start position:0% nanies that are integrating us though bitwise<00:08:25.960> a<00:08:26.120> traditional<00:08:26.680> Finance<00:08:27.080> Company 00:08:27.629 --> 00:08:27.639 align:start position:0% bitwise a traditional Finance Company 00:08:27.639 --> 00:08:29.670 align:start position:0% bitwise a traditional Finance Company who<00:08:27.759> released<00:08:28.120> their<00:08:28.319> ethereum<00:08:28.720> ETF<00:08:29.199> product 00:08:29.670 --> 00:08:29.680 align:start position:0% who released their ethereum ETF product 00:08:29.680 --> 00:08:32.070 align:start position:0% who released their ethereum ETF product this<00:08:29.840> year<00:08:30.400> has<00:08:30.560> created<00:08:30.919> ens<00:08:31.360> subnames<00:08:31.759> for 00:08:32.070 --> 00:08:32.080 align:start position:0% this year has created ens subnames for 00:08:32.080 --> 00:08:34.029 align:start position:0% this year has created ens subnames for each<00:08:32.240> of<00:08:32.360> the<00:08:32.519> addresses<00:08:32.959> that<00:08:33.080> hold<00:08:33.360> the<00:08:33.519> eth 00:08:34.029 --> 00:08:34.039 align:start position:0% each of the addresses that hold the eth 00:08:34.039 --> 00:08:35.110 align:start position:0% each of the addresses that hold the eth back<00:08:34.200> in<00:08:34.360> the 00:08:35.110 --> 00:08:35.120 align:start position:0% back in the 00:08:35.120 --> 00:08:37.589 align:start position:0% back in the ETF<00:08:36.120> this<00:08:36.200> is<00:08:36.320> a<00:08:36.479> great<00:08:36.719> use<00:08:37.039> case<00:08:37.399> and<00:08:37.479> that 00:08:37.589 --> 00:08:37.599 align:start position:0% ETF this is a great use case and that 00:08:37.599 --> 00:08:39.149 align:start position:0% ETF this is a great use case and that hopefully<00:08:37.919> makes<00:08:38.159> tracking<00:08:38.640> custody<00:08:39.039> of 00:08:39.149 --> 00:08:39.159 align:start position:0% hopefully makes tracking custody of 00:08:39.159 --> 00:08:41.870 align:start position:0% hopefully makes tracking custody of Unchained<00:08:39.800> assets<00:08:40.479> more<00:08:40.760> transparent<00:08:41.719> and 00:08:41.870 --> 00:08:41.880 align:start position:0% Unchained assets more transparent and 00:08:41.880 --> 00:08:44.470 align:start position:0% Unchained assets more transparent and more 00:08:44.470 --> 00:08:44.480 align:start position:0% 00:08:44.480 --> 00:08:46.430 align:start position:0% auditable<00:08:45.480> payment<00:08:45.720> providers<00:08:46.080> have<00:08:46.200> started 00:08:46.430 --> 00:08:46.440 align:start position:0% auditable payment providers have started 00:08:46.440 --> 00:08:51.720 align:start position:0% auditable payment providers have started to<00:08:46.519> adopt<00:08:46.800> ens2<00:08:47.800> most<00:08:48.000> notably<00:08:48.959> PayPal<00:08:49.680> and 00:08:51.720 --> 00:08:51.730 align:start position:0% to adopt ens2 most notably PayPal and 00:08:51.730 --> 00:08:55.150 align:start position:0% to adopt ens2 most notably PayPal and [Applause] 00:08:55.150 --> 00:08:55.160 align:start position:0% 00:08:55.160 --> 00:08:57.750 align:start position:0% VMO<00:08:56.160> they<00:08:56.320> rolled<00:08:56.600> out<00:08:56.800> their<00:08:56.959> en<00:08:57.399> support<00:08:57.640> for 00:08:57.750 --> 00:08:57.760 align:start position:0% VMO they rolled out their en support for 00:08:57.760 --> 00:08:59.430 align:start position:0% VMO they rolled out their en support for their<00:08:57.880> crypto<00:08:58.200> wallets<00:08:58.480> to<00:08:58.680> all<00:08:58.920> us<00:08:59.160> users 00:08:59.430 --> 00:08:59.440 align:start position:0% their crypto wallets to all us users 00:08:59.440 --> 00:09:02.350 align:start position:0% their crypto wallets to all us users users<00:08:59.720> earlier<00:09:00.079> this<00:09:00.279> year<00:09:00.920> VMO<00:09:01.480> has<00:09:01.720> 90 00:09:02.350 --> 00:09:02.360 align:start position:0% users earlier this year VMO has 90 00:09:02.360 --> 00:09:06.350 align:start position:0% users earlier this year VMO has 90 million<00:09:03.200> us<00:09:03.560> users<00:09:04.320> and<00:09:04.519> PayPal<00:09:05.079> has<00:09:05.320> over<00:09:05.680> 400 00:09:06.350 --> 00:09:06.360 align:start position:0% million us users and PayPal has over 400 00:09:06.360 --> 00:09:08.190 align:start position:0% million us users and PayPal has over 400 million<00:09:06.760> accounts<00:09:07.079> globally<00:09:07.920> and<00:09:08.040> this 00:09:08.190 --> 00:09:08.200 align:start position:0% million accounts globally and this 00:09:08.200 --> 00:09:11.069 align:start position:0% million accounts globally and this really<00:09:08.399> shows<00:09:08.959> how<00:09:09.120> ens<00:09:09.560> is<00:09:09.760> really<00:09:10.399> super 00:09:11.069 --> 00:09:11.079 align:start position:0% really shows how ens is really super 00:09:11.079 --> 00:09:14.110 align:start position:0% really shows how ens is really super wide<00:09:11.360> ranging<00:09:12.200> and<00:09:13.000> going<00:09:13.279> to<00:09:13.640> millions<00:09:14.000> and 00:09:14.110 --> 00:09:14.120 align:start position:0% wide ranging and going to millions and 00:09:14.120 --> 00:09:15.990 align:start position:0% wide ranging and going to millions and millions<00:09:14.360> of 00:09:15.990 --> 00:09:16.000 align:start position:0% millions of 00:09:16.000 --> 00:09:18.870 align:start position:0% millions of users<00:09:17.000> and<00:09:17.200> lastly<00:09:17.959> can<00:09:18.079> you<00:09:18.240> really<00:09:18.399> say<00:09:18.680> your 00:09:18.870 --> 00:09:18.880 align:start position:0% users and lastly can you really say your 00:09:18.880 --> 00:09:20.470 align:start position:0% users and lastly can you really say your successful<00:09:19.279> protocol<00:09:19.880> until<00:09:20.200> Google 00:09:20.470 --> 00:09:20.480 align:start position:0% successful protocol until Google 00:09:20.480 --> 00:09:21.509 align:start position:0% successful protocol until Google integrates 00:09:21.509 --> 00:09:21.519 align:start position:0% integrates 00:09:21.519 --> 00:09:24.190 align:start position:0% integrates you<00:09:22.519> today<00:09:22.880> you<00:09:23.000> can<00:09:23.120> search<00:09:23.399> your<00:09:23.680> e<00:09:23.880> name<00:09:24.040> on 00:09:24.190 --> 00:09:24.200 align:start position:0% you today you can search your e name on 00:09:24.200 --> 00:09:25.750 align:start position:0% you today you can search your e name on Google<00:09:24.600> and<00:09:24.720> it<00:09:24.800> will<00:09:25.040> automatically<00:09:25.560> show 00:09:25.750 --> 00:09:25.760 align:start position:0% Google and it will automatically show 00:09:25.760 --> 00:09:27.389 align:start position:0% Google and it will automatically show you<00:09:25.920> your<00:09:26.079> balance<00:09:26.600> and<00:09:26.760> your<00:09:26.880> resoled 00:09:27.389 --> 00:09:27.399 align:start position:0% you your balance and your resoled 00:09:27.399 --> 00:09:29.550 align:start position:0% you your balance and your resoled address<00:09:28.279> Google<00:09:28.600> is<00:09:28.720> the<00:09:28.880> gateway<00:09:29.200> to<00:09:29.440> the 00:09:29.550 --> 00:09:29.560 align:start position:0% address Google is the gateway to the 00:09:29.560 --> 00:09:31.470 align:start position:0% address Google is the gateway to the internet<00:09:29.959> and<00:09:30.120> Ian<00:09:30.480> has<00:09:30.640> become<00:09:31.040> important 00:09:31.470 --> 00:09:31.480 align:start position:0% internet and Ian has become important 00:09:31.480 --> 00:09:33.550 align:start position:0% internet and Ian has become important enough<00:09:31.680> to<00:09:31.800> be<00:09:31.959> integrated<00:09:32.399> into<00:09:32.640> the<00:09:32.880> most 00:09:33.550 --> 00:09:33.560 align:start position:0% enough to be integrated into the most 00:09:33.560 --> 00:09:37.250 align:start position:0% enough to be integrated into the most used<00:09:34.160> search 00:09:37.250 --> 00:09:37.260 align:start position:0% 00:09:37.260 --> 00:09:40.470 align:start position:0% [Applause] 00:09:40.470 --> 00:09:40.480 align:start position:0% 00:09:40.480 --> 00:09:42.269 align:start position:0% engine<00:09:41.480> so<00:09:41.640> what<00:09:41.720> do<00:09:41.880> these<00:09:42.000> large 00:09:42.269 --> 00:09:42.279 align:start position:0% engine so what do these large 00:09:42.279 --> 00:09:44.550 align:start position:0% engine so what do these large Integrations<00:09:42.800> bring<00:09:43.000> to<00:09:43.320> ens<00:09:44.320> well 00:09:44.550 --> 00:09:44.560 align:start position:0% Integrations bring to ens well 00:09:44.560 --> 00:09:47.310 align:start position:0% Integrations bring to ens well subdomains<00:09:45.360> means<00:09:45.640> more<00:09:45.880> users<00:09:46.720> more<00:09:47.040> people 00:09:47.310 --> 00:09:47.320 align:start position:0% subdomains means more users more people 00:09:47.320 --> 00:09:49.590 align:start position:0% subdomains means more users more people using<00:09:47.680> ens<00:09:48.320> for<00:09:48.519> the<00:09:48.680> first<00:09:48.959> time<00:09:49.440> and 00:09:49.590 --> 00:09:49.600 align:start position:0% using ens for the first time and 00:09:49.600 --> 00:09:51.590 align:start position:0% using ens for the first time and broadening<00:09:50.120> The<00:09:50.279> Social<00:09:50.600> Network<00:09:51.079> ens 00:09:51.590 --> 00:09:51.600 align:start position:0% broadening The Social Network ens 00:09:51.600 --> 00:09:54.509 align:start position:0% broadening The Social Network ens creates<00:09:52.600> large<00:09:52.920> Integrations<00:09:53.519> like<00:09:53.760> PayPal 00:09:54.509 --> 00:09:54.519 align:start position:0% creates large Integrations like PayPal 00:09:54.519 --> 00:09:57.030 align:start position:0% creates large Integrations like PayPal VMO<00:09:55.160> and<00:09:55.360> Google<00:09:56.120> means<00:09:56.440> there<00:09:56.560> are<00:09:56.720> more 00:09:57.030 --> 00:09:57.040 align:start position:0% VMO and Google means there are more 00:09:57.040 --> 00:10:00.030 align:start position:0% VMO and Google means there are more places<00:09:57.680> for<00:09:57.880> ens<00:09:58.640> to<00:09:58.839> be<00:09:59.000> used 00:10:00.030 --> 00:10:00.040 align:start position:0% places for ens to be used 00:10:00.040 --> 00:10:04.949 align:start position:0% places for ens to be used making<00:10:00.399> ens<00:10:01.399> fundamentally<00:10:02.320> more 00:10:04.949 --> 00:10:04.959 align:start position:0% 00:10:04.959 --> 00:10:07.230 align:start position:0% useful<00:10:05.959> in<00:10:06.079> the<00:10:06.200> same<00:10:06.399> thing<00:10:06.600> we've<00:10:06.800> also<00:10:07.000> been 00:10:07.230 --> 00:10:07.240 align:start position:0% useful in the same thing we've also been 00:10:07.240 --> 00:10:09.990 align:start position:0% useful in the same thing we've also been pushing<00:10:07.760> forward<00:10:08.200> L2<00:10:08.600> ux<00:10:08.959> with<00:10:09.160> some<00:10:09.360> eips<00:10:09.839> in 00:10:09.990 --> 00:10:10.000 align:start position:0% pushing forward L2 ux with some eips in 00:10:10.000 --> 00:10:12.829 align:start position:0% pushing forward L2 ux with some eips in the<00:10:10.120> pipelines<00:10:10.959> the<00:10:11.120> first<00:10:11.320> of<00:10:11.519> which<00:10:11.800> is<00:10:11.959> ERC 00:10:12.829 --> 00:10:12.839 align:start position:0% the pipelines the first of which is ERC 00:10:12.839 --> 00:10:15.670 align:start position:0% the pipelines the first of which is ERC 7785<00:10:13.839> that<00:10:13.920> will<00:10:14.079> enshrine<00:10:14.560> ens<00:10:15.240> to<00:10:15.399> be<00:10:15.560> the 00:10:15.670 --> 00:10:15.680 align:start position:0% 7785 that will enshrine ens to be the 00:10:15.680 --> 00:10:18.550 align:start position:0% 7785 that will enshrine ens to be the name<00:10:16.279> Nam<00:10:16.600> space<00:10:16.880> to<00:10:17.040> allow<00:10:17.560> discovery<00:10:17.839> of<00:10:17.959> new 00:10:18.550 --> 00:10:18.560 align:start position:0% name Nam space to allow discovery of new 00:10:18.560 --> 00:10:20.670 align:start position:0% name Nam space to allow discovery of new l2s<00:10:19.560> in<00:10:19.640> the<00:10:19.760> future<00:10:20.079> we<00:10:20.200> hope<00:10:20.360> to<00:10:20.519> push 00:10:20.670 --> 00:10:20.680 align:start position:0% l2s in the future we hope to push 00:10:20.680 --> 00:10:22.030 align:start position:0% l2s in the future we hope to push further<00:10:21.000> eips<00:10:21.519> that<00:10:21.680> help<00:10:21.880> the 00:10:22.030 --> 00:10:22.040 align:start position:0% further eips that help the 00:10:22.040 --> 00:10:24.350 align:start position:0% further eips that help the fractionalization<00:10:23.040> of<00:10:23.160> L2<00:10:23.560> addresses<00:10:24.200> and 00:10:24.350 --> 00:10:24.360 align:start position:0% fractionalization of L2 addresses and 00:10:24.360 --> 00:10:27.389 align:start position:0% fractionalization of L2 addresses and address<00:10:24.680> this<00:10:24.880> problem<00:10:25.519> headon<00:10:26.519> ens<00:10:27.000> works<00:10:27.240> on 00:10:27.389 --> 00:10:27.399 align:start position:0% address this problem headon ens works on 00:10:27.399 --> 00:10:29.310 align:start position:0% address this problem headon ens works on these<00:10:27.640> problems<00:10:28.120> because<00:10:28.360> of<00:10:28.519> course<00:10:29.000> self 00:10:29.310 --> 00:10:29.320 align:start position:0% these problems because of course self 00:10:29.320 --> 00:10:32.150 align:start position:0% these problems because of course self selfishly<00:10:29.720> it<00:10:29.839> helps<00:10:30.200> ens<00:10:30.959> proliferate<00:10:31.959> but 00:10:32.150 --> 00:10:32.160 align:start position:0% selfishly it helps ens proliferate but 00:10:32.160 --> 00:10:34.190 align:start position:0% selfishly it helps ens proliferate but selfishly<00:10:33.040> it<00:10:33.200> also<00:10:33.440> helps<00:10:33.720> the<00:10:33.880> entire 00:10:34.190 --> 00:10:34.200 align:start position:0% selfishly it also helps the entire 00:10:34.200 --> 00:10:37.430 align:start position:0% selfishly it also helps the entire ethereum<00:10:34.680> ecosystem<00:10:35.279> as 00:10:37.430 --> 00:10:37.440 align:start position:0% ethereum ecosystem as 00:10:37.440 --> 00:10:40.590 align:start position:0% ethereum ecosystem as well<00:10:38.440> born<00:10:38.720> out<00:10:38.839> of<00:10:39.000> ethereum<00:10:39.639> we<00:10:39.839> as<00:10:40.000> en<00:10:40.440> have 00:10:40.590 --> 00:10:40.600 align:start position:0% well born out of ethereum we as en have 00:10:40.600 --> 00:10:42.550 align:start position:0% well born out of ethereum we as en have never<00:10:40.800> forgotten<00:10:41.200> Our<00:10:41.320> Roots<00:10:41.920> all<00:10:42.120> the<00:10:42.240> values 00:10:42.550 --> 00:10:42.560 align:start position:0% never forgotten Our Roots all the values 00:10:42.560 --> 00:10:44.550 align:start position:0% never forgotten Our Roots all the values that<00:10:42.680> have<00:10:42.800> come<00:10:42.920> out<00:10:43.040> of<00:10:43.200> them<00:10:43.839> ethereum<00:10:44.360> is 00:10:44.550 --> 00:10:44.560 align:start position:0% that have come out of them ethereum is 00:10:44.560 --> 00:10:46.550 align:start position:0% that have come out of them ethereum is not<00:10:44.760> just<00:10:44.920> in<00:10:45.040> our<00:10:45.279> name<00:10:45.639> but<00:10:45.760> in<00:10:45.920> the<00:10:46.040> DNA<00:10:46.399> of 00:10:46.550 --> 00:10:46.560 align:start position:0% not just in our name but in the DNA of 00:10:46.560 --> 00:10:49.629 align:start position:0% not just in our name but in the DNA of En 00:10:49.629 --> 00:10:49.639 align:start position:0% 00:10:49.639 --> 00:10:52.430 align:start position:0% itself<00:10:50.639> for<00:10:50.880> seven<00:10:51.240> years<00:10:51.760> primary<00:10:52.120> names 00:10:52.430 --> 00:10:52.440 align:start position:0% itself for seven years primary names 00:10:52.440 --> 00:10:55.150 align:start position:0% itself for seven years primary names have<00:10:52.639> only<00:10:52.880> existed<00:10:53.200> on<00:10:53.639> L1<00:10:54.639> which<00:10:54.800> limits 00:10:55.150 --> 00:10:55.160 align:start position:0% have only existed on L1 which limits 00:10:55.160 --> 00:10:56.550 align:start position:0% have only existed on L1 which limits their<00:10:55.279> use<00:10:55.480> to<00:10:55.680> people<00:10:55.920> who<00:10:56.000> are<00:10:56.120> willing<00:10:56.360> to 00:10:56.550 --> 00:10:56.560 align:start position:0% their use to people who are willing to 00:10:56.560 --> 00:10:59.350 align:start position:0% their use to people who are willing to pay<00:10:56.839> ethereum<00:10:57.360> gas<00:10:57.600> fees 00:10:59.350 --> 00:10:59.360 align:start position:0% pay ethereum gas fees 00:10:59.360 --> 00:11:01.230 align:start position:0% pay ethereum gas fees being<00:10:59.560> able<00:10:59.760> to<00:10:59.880> set<00:11:00.120> a<00:11:00.279> primary<00:11:00.639> name<00:11:00.839> on<00:11:01.040> any 00:11:01.230 --> 00:11:01.240 align:start position:0% being able to set a primary name on any 00:11:01.240 --> 00:11:03.590 align:start position:0% being able to set a primary name on any chain<00:11:01.959> effectively<00:11:02.399> for<00:11:02.600> free<00:11:03.079> will<00:11:03.279> be<00:11:03.399> a 00:11:03.590 --> 00:11:03.600 align:start position:0% chain effectively for free will be a 00:11:03.600 --> 00:11:05.910 align:start position:0% chain effectively for free will be a huge<00:11:03.959> unlock<00:11:04.360> for<00:11:04.480> the<00:11:04.600> web<00:11:04.800> through<00:11:04.959> ux<00:11:05.800> and 00:11:05.910 --> 00:11:05.920 align:start position:0% huge unlock for the web through ux and 00:11:05.920 --> 00:11:07.470 align:start position:0% huge unlock for the web through ux and this<00:11:06.040> is<00:11:06.160> the<00:11:06.320> first<00:11:06.639> example<00:11:07.000> of<00:11:07.160> a<00:11:07.320> more 00:11:07.470 --> 00:11:07.480 align:start position:0% this is the first example of a more 00:11:07.480 --> 00:11:09.110 align:start position:0% this is the first example of a more flexible<00:11:07.959> contract<00:11:08.360> that<00:11:08.440> will<00:11:08.560> be<00:11:08.680> seen<00:11:08.959> to 00:11:09.110 --> 00:11:09.120 align:start position:0% flexible contract that will be seen to 00:11:09.120 --> 00:11:11.910 align:start position:0% flexible contract that will be seen to me<00:11:09.360> broadly<00:11:09.800> in<00:11:10.000> ensv<00:11:10.519> 2<00:11:11.079> which<00:11:11.360> was<00:11:11.519> announced 00:11:11.910 --> 00:11:11.920 align:start position:0% me broadly in ensv 2 which was announced 00:11:11.920 --> 00:11:14.990 align:start position:0% me broadly in ensv 2 which was announced in<00:11:12.079> May<00:11:12.680> and<00:11:12.800> marks<00:11:13.160> the<00:11:13.320> first<00:11:13.920> time<00:11:14.560> that<00:11:14.800> any 00:11:14.990 --> 00:11:15.000 align:start position:0% in May and marks the first time that any 00:11:15.000 --> 00:11:16.910 align:start position:0% in May and marks the first time that any enss<00:11:15.480> contract<00:11:15.800> will<00:11:15.959> it<00:11:16.079> be<00:11:16.240> officially 00:11:16.910 --> 00:11:16.920 align:start position:0% enss contract will it be officially 00:11:16.920 --> 00:11:19.430 align:start position:0% enss contract will it be officially deployed<00:11:17.240> to<00:11:17.399> L2<00:11:18.399> and<00:11:18.519> I'm<00:11:18.680> proud<00:11:18.880> to<00:11:19.040> announce 00:11:19.430 --> 00:11:19.440 align:start position:0% deployed to L2 and I'm proud to announce 00:11:19.440 --> 00:11:21.350 align:start position:0% deployed to L2 and I'm proud to announce that<00:11:19.920> primary<00:11:20.240> names<00:11:20.440> are<00:11:20.560> coming<00:11:20.720> to<00:11:20.839> L2<00:11:21.240> and 00:11:21.350 --> 00:11:21.360 align:start position:0% that primary names are coming to L2 and 00:11:21.360 --> 00:11:29.550 align:start position:0% that primary names are coming to L2 and are<00:11:21.480> available<00:11:21.800> on<00:11:21.920> test<00:11:22.160> Nets<00:11:22.399> today 00:11:29.550 --> 00:11:29.560 align:start position:0% 00:11:29.560 --> 00:11:31.269 align:start position:0% reverse<00:11:29.920> registrars<00:11:30.519> are<00:11:30.639> smart<00:11:30.920> contracts 00:11:31.269 --> 00:11:31.279 align:start position:0% reverse registrars are smart contracts 00:11:31.279 --> 00:11:32.870 align:start position:0% reverse registrars are smart contracts that<00:11:31.399> power<00:11:31.639> L2<00:11:32.000> primary<00:11:32.279> names<00:11:32.519> are<00:11:32.680> live 00:11:32.870 --> 00:11:32.880 align:start position:0% that power L2 primary names are live 00:11:32.880 --> 00:11:34.190 align:start position:0% that power L2 primary names are live today<00:11:33.079> on<00:11:33.160> a<00:11:33.240> handful<00:11:33.560> of<00:11:33.639> test<00:11:33.880> Nets<00:11:34.120> and 00:11:34.190 --> 00:11:34.200 align:start position:0% today on a handful of test Nets and 00:11:34.200 --> 00:11:35.509 align:start position:0% today on a handful of test Nets and should<00:11:34.360> be<00:11:34.519> com<00:11:34.680> to<00:11:34.760> main<00:11:34.959> net<00:11:35.120> by<00:11:35.240> the<00:11:35.279> end<00:11:35.399> of 00:11:35.509 --> 00:11:35.519 align:start position:0% should be com to main net by the end of 00:11:35.519 --> 00:11:36.710 align:start position:0% should be com to main net by the end of this<00:11:35.680> year<00:11:36.040> and<00:11:36.160> to<00:11:36.240> be<00:11:36.360> clear<00:11:36.560> there's 00:11:36.710 --> 00:11:36.720 align:start position:0% this year and to be clear there's 00:11:36.720 --> 00:11:38.430 align:start position:0% this year and to be clear there's nothing<00:11:36.880> for<00:11:37.040> developers<00:11:37.680> non-developers<00:11:38.320> to 00:11:38.430 --> 00:11:38.440 align:start position:0% nothing for developers non-developers to 00:11:38.440 --> 00:11:40.269 align:start position:0% nothing for developers non-developers to do<00:11:38.600> this<00:11:38.800> time<00:11:39.000> but<00:11:39.120> if<00:11:39.200> you're<00:11:39.320> a<00:11:39.440> developer 00:11:40.269 --> 00:11:40.279 align:start position:0% do this time but if you're a developer 00:11:40.279 --> 00:11:43.949 align:start position:0% do this time but if you're a developer you<00:11:40.399> can<00:11:40.519> go<00:11:40.680> to<00:11:40.800> test<00:11:41.040> Nets<00:11:41.279> today<00:11:41.639> and<00:11:41.800> play 00:11:43.949 --> 00:11:43.959 align:start position:0% you can go to test Nets today and play 00:11:43.959 --> 00:11:46.350 align:start position:0% you can go to test Nets today and play around<00:11:44.959> now<00:11:45.200> things<00:11:45.440> have<00:11:45.639> really<00:11:45.880> changed<00:11:46.240> in 00:11:46.350 --> 00:11:46.360 align:start position:0% around now things have really changed in 00:11:46.360 --> 00:11:48.030 align:start position:0% around now things have really changed in the<00:11:46.519> last<00:11:46.680> seven<00:11:46.920> years<00:11:47.160> I<00:11:47.200> mean<00:11:47.360> look<00:11:47.480> at<00:11:47.639> our 00:11:48.030 --> 00:11:48.040 align:start position:0% the last seven years I mean look at our 00:11:48.040 --> 00:11:50.110 align:start position:0% the last seven years I mean look at our old<00:11:48.399> 2017 00:11:50.110 --> 00:11:50.120 align:start position:0% old 2017 00:11:50.120 --> 00:11:53.030 align:start position:0% old 2017 logo<00:11:51.120> l2s<00:11:51.560> are<00:11:51.680> the<00:11:51.800> norm<00:11:52.160> now<00:11:52.560> and<00:11:52.720> smart 00:11:53.030 --> 00:11:53.040 align:start position:0% logo l2s are the norm now and smart 00:11:53.040 --> 00:11:55.310 align:start position:0% logo l2s are the norm now and smart contract<00:11:53.480> accounts<00:11:53.800> are<00:11:53.959> common<00:11:54.279> place<00:11:55.079> gas 00:11:55.310 --> 00:11:55.320 align:start position:0% contract accounts are common place gas 00:11:55.320 --> 00:11:57.470 align:start position:0% contract accounts are common place gas prices<00:11:55.600> are<00:11:55.760> fluctua<00:11:56.560> fluctuating<00:11:57.200> and<00:11:57.320> it's 00:11:57.470 --> 00:11:57.480 align:start position:0% prices are fluctua fluctuating and it's 00:11:57.480 --> 00:12:00.350 align:start position:0% prices are fluctua fluctuating and it's not<00:11:57.680> sustainable<00:11:58.240> to<00:11:58.399> stay<00:11:58.560> on<00:11:58.680> L1<00:11:59.000> anymore 00:12:00.350 --> 00:12:00.360 align:start position:0% not sustainable to stay on L1 anymore 00:12:00.360 --> 00:12:03.550 align:start position:0% not sustainable to stay on L1 anymore more<00:12:01.360> in<00:12:01.560> may<00:12:01.880> we<00:12:02.040> talked<00:12:02.279> about<00:12:02.480> moving<00:12:02.720> to<00:12:02.880> L2 00:12:03.550 --> 00:12:03.560 align:start position:0% more in may we talked about moving to L2 00:12:03.560 --> 00:12:06.350 align:start position:0% more in may we talked about moving to L2 driven<00:12:04.000> by<00:12:04.320> several<00:12:04.760> key<00:12:05.000> reasons<00:12:05.839> the<00:12:06.040> first 00:12:06.350 --> 00:12:06.360 align:start position:0% driven by several key reasons the first 00:12:06.360 --> 00:12:07.990 align:start position:0% driven by several key reasons the first is<00:12:06.560> reducing<00:12:06.959> the<00:12:07.120> overall<00:12:07.560> cost<00:12:07.839> of 00:12:07.990 --> 00:12:08.000 align:start position:0% is reducing the overall cost of 00:12:08.000 --> 00:12:09.230 align:start position:0% is reducing the overall cost of interacting<00:12:08.480> with 00:12:09.230 --> 00:12:09.240 align:start position:0% interacting with 00:12:09.240 --> 00:12:11.910 align:start position:0% interacting with ens<00:12:10.240> the<00:12:10.399> second<00:12:10.880> is<00:12:11.040> reducing<00:12:11.440> the<00:12:11.560> number<00:12:11.760> of 00:12:11.910 --> 00:12:11.920 align:start position:0% ens the second is reducing the number of 00:12:11.920 --> 00:12:14.269 align:start position:0% ens the second is reducing the number of transaction<00:12:12.480> in<00:12:12.680> all<00:12:13.000> possible 00:12:14.269 --> 00:12:14.279 align:start position:0% transaction in all possible 00:12:14.279 --> 00:12:17.030 align:start position:0% transaction in all possible situations<00:12:15.279> and<00:12:15.399> the<00:12:15.600> last<00:12:15.959> is<00:12:16.639> we<00:12:16.760> want<00:12:16.880> to 00:12:17.030 --> 00:12:17.040 align:start position:0% situations and the last is we want to 00:12:17.040 --> 00:12:18.710 align:start position:0% situations and the last is we want to let<00:12:17.240> all<00:12:17.399> users<00:12:17.800> transact<00:12:18.199> from<00:12:18.279> the<00:12:18.399> chain<00:12:18.560> of 00:12:18.710 --> 00:12:18.720 align:start position:0% let all users transact from the chain of 00:12:18.720 --> 00:12:20.430 align:start position:0% let all users transact from the chain of their<00:12:18.880> choice<00:12:19.519> without<00:12:19.760> the<00:12:19.880> need<00:12:20.040> for<00:12:20.160> on<00:12:20.320> and 00:12:20.430 --> 00:12:20.440 align:start position:0% their choice without the need for on and 00:12:20.440 --> 00:12:22.949 align:start position:0% their choice without the need for on and off<00:12:20.600> Rams<00:12:20.880> that<00:12:20.959> can<00:12:21.079> make<00:12:21.240> L2<00:12:21.639> so<00:12:22.079> painful 00:12:22.949 --> 00:12:22.959 align:start position:0% off Rams that can make L2 so painful 00:12:22.959 --> 00:12:24.509 align:start position:0% off Rams that can make L2 so painful with<00:12:23.199> these<00:12:23.360> ux<00:12:23.680> goals<00:12:23.920> in<00:12:24.040> mind<00:12:24.279> we<00:12:24.399> are 00:12:24.509 --> 00:12:24.519 align:start position:0% with these ux goals in mind we are 00:12:24.519 --> 00:12:27.069 align:start position:0% with these ux goals in mind we are aiming<00:12:24.760> to<00:12:24.920> make<00:12:25.120> a<00:12:25.279> true<00:12:25.680> Improvement<00:12:26.399> to<00:12:26.639> ens 00:12:27.069 --> 00:12:27.079 align:start position:0% aiming to make a true Improvement to ens 00:12:27.079 --> 00:12:29.910 align:start position:0% aiming to make a true Improvement to ens ux<00:12:27.800> without<00:12:28.160> the<00:12:28.360> usual<00:12:28.639> trade-offs 00:12:29.910 --> 00:12:29.920 align:start position:0% ux without the usual trade-offs 00:12:29.920 --> 00:12:31.629 align:start position:0% ux without the usual trade-offs and<00:12:30.040> with<00:12:30.199> that<00:12:30.360> on<00:12:30.480> Monday<00:12:30.800> at<00:12:30.959> frns<00:12:31.320> day<00:12:31.519> we 00:12:31.629 --> 00:12:31.639 align:start position:0% and with that on Monday at frns day we 00:12:31.639 --> 00:12:33.110 align:start position:0% and with that on Monday at frns day we announced<00:12:32.000> our<00:12:32.160> plans<00:12:32.440> to<00:12:32.560> build<00:12:32.760> our<00:12:32.920> own 00:12:33.110 --> 00:12:33.120 align:start position:0% announced our plans to build our own 00:12:33.120 --> 00:12:40.750 align:start position:0% announced our plans to build our own chain<00:12:33.839> which<00:12:34.000> we're<00:12:34.199> calling<00:12:35.079> name 00:12:40.750 --> 00:12:40.760 align:start position:0% 00:12:40.760 --> 00:12:43.269 align:start position:0% chain<00:12:41.760> name<00:12:42.000> chain<00:12:42.240> is<00:12:42.360> built<00:12:42.560> on<00:12:42.639> a<00:12:42.760> few<00:12:43.000> core 00:12:43.269 --> 00:12:43.279 align:start position:0% chain name chain is built on a few core 00:12:43.279 --> 00:12:45.910 align:start position:0% chain name chain is built on a few core things<00:12:43.519> that<00:12:43.600> are<00:12:43.839> really<00:12:44.120> important<00:12:44.560> to<00:12:44.760> us 00:12:45.910 --> 00:12:45.920 align:start position:0% things that are really important to us 00:12:45.920 --> 00:12:49.430 align:start position:0% things that are really important to us ANS<00:12:46.920> today<00:12:47.639> zi<00:12:48.079> EVMS<00:12:48.600> are<00:12:48.800> the<00:12:48.880> only<00:12:49.120> way<00:12:49.279> to 00:12:49.430 --> 00:12:49.440 align:start position:0% ANS today zi EVMS are the only way to 00:12:49.440 --> 00:12:51.550 align:start position:0% ANS today zi EVMS are the only way to get<00:12:49.639> transaction<00:12:50.240> finality<00:12:50.880> in<00:12:51.000> a<00:12:51.120> reasonable 00:12:51.550 --> 00:12:51.560 align:start position:0% get transaction finality in a reasonable 00:12:51.560 --> 00:12:54.150 align:start position:0% get transaction finality in a reasonable amount<00:12:51.760> of<00:12:51.920> time<00:12:52.720> and<00:12:52.880> because<00:12:53.279> ens<00:12:53.760> is<00:12:53.880> one<00:12:54.000> of 00:12:54.150 --> 00:12:54.160 align:start position:0% amount of time and because ens is one of 00:12:54.160 --> 00:12:55.670 align:start position:0% amount of time and because ens is one of the<00:12:54.320> only<00:12:54.680> application<00:12:55.199> that<00:12:55.320> requires 00:12:55.670 --> 00:12:55.680 align:start position:0% the only application that requires 00:12:55.680 --> 00:12:57.910 align:start position:0% the only application that requires reading<00:12:56.000> state<00:12:56.560> from<00:12:56.720> L1<00:12:57.440> we<00:12:57.560> need<00:12:57.720> the 00:12:57.910 --> 00:12:57.920 align:start position:0% reading state from L1 we need the 00:12:57.920 --> 00:12:59.870 align:start position:0% reading state from L1 we need the fastest<00:12:58.279> finality<00:12:58.800> we<00:12:58.920> can<00:12:59.279> to<00:12:59.399> ensure<00:12:59.680> that 00:12:59.870 --> 00:12:59.880 align:start position:0% fastest finality we can to ensure that 00:12:59.880 --> 00:13:01.629 align:start position:0% fastest finality we can to ensure that everything<00:13:00.240> can<00:13:00.360> be<00:13:00.519> contrust<00:13:01.000> thisly<00:13:01.240> read 00:13:01.629 --> 00:13:01.639 align:start position:0% everything can be contrust thisly read 00:13:01.639 --> 00:13:02.550 align:start position:0% everything can be contrust thisly read from<00:13:01.839> other 00:13:02.550 --> 00:13:02.560 align:start position:0% from other 00:13:02.560 --> 00:13:05.790 align:start position:0% from other l2s<00:13:03.560> ZK<00:13:04.000> EVMS<00:13:04.519> use<00:13:04.720> ZK<00:13:05.040> proofs<00:13:05.360> to<00:13:05.480> prove<00:13:05.680> the 00:13:05.790 --> 00:13:05.800 align:start position:0% l2s ZK EVMS use ZK proofs to prove the 00:13:05.800 --> 00:13:08.110 align:start position:0% l2s ZK EVMS use ZK proofs to prove the correctness<00:13:06.560> of<00:13:06.680> a<00:13:06.800> state<00:13:07.000> transition<00:13:07.800> on<00:13:07.959> an 00:13:08.110 --> 00:13:08.120 align:start position:0% correctness of a state transition on an 00:13:08.120 --> 00:13:10.990 align:start position:0% correctness of a state transition on an L2<00:13:08.600> and<00:13:08.760> Commit<00:13:09.040> This<00:13:09.160> to<00:13:09.399> L1<00:13:10.399> the<00:13:10.560> ens 00:13:10.990 --> 00:13:11.000 align:start position:0% L2 and Commit This to L1 the ens 00:13:11.000 --> 00:13:13.069 align:start position:0% L2 and Commit This to L1 the ens resolution<00:13:11.480> process<00:13:11.880> can<00:13:12.040> then<00:13:12.199> use<00:13:12.480> ccip 00:13:13.069 --> 00:13:13.079 align:start position:0% resolution process can then use ccip 00:13:13.079 --> 00:13:16.150 align:start position:0% resolution process can then use ccip read<00:13:13.519> to<00:13:13.720> verif<00:13:14.360> verify<00:13:14.720> the<00:13:14.880> data<00:13:15.519> from<00:13:15.760> name 00:13:16.150 --> 00:13:16.160 align:start position:0% read to verif verify the data from name 00:13:16.160 --> 00:13:18.629 align:start position:0% read to verif verify the data from name chain<00:13:17.160> contrasting<00:13:17.760> this<00:13:17.880> to<00:13:18.079> an<00:13:18.199> optimistic 00:13:18.629 --> 00:13:18.639 align:start position:0% chain contrasting this to an optimistic 00:13:18.639 --> 00:13:20.310 align:start position:0% chain contrasting this to an optimistic rollup<00:13:19.040> the<00:13:19.120> industry<00:13:19.519> standard<00:13:20.120> would 00:13:20.310 --> 00:13:20.320 align:start position:0% rollup the industry standard would 00:13:20.320 --> 00:13:22.310 align:start position:0% rollup the industry standard would require<00:13:20.600> us<00:13:20.720> to<00:13:20.880> wait<00:13:21.120> 7<00:13:21.440> days<00:13:21.959> before<00:13:22.160> our 00:13:22.310 --> 00:13:22.320 align:start position:0% require us to wait 7 days before our 00:13:22.320 --> 00:13:25.069 align:start position:0% require us to wait 7 days before our name<00:13:22.560> can<00:13:22.680> be<00:13:22.839> in 00:13:25.069 --> 00:13:25.079 align:start position:0% 00:13:25.079 --> 00:13:27.550 align:start position:0% use<00:13:26.079> the<00:13:26.240> second<00:13:26.600> is<00:13:26.800> of<00:13:26.959> course<00:13:27.120> the<00:13:27.279> stack 00:13:27.550 --> 00:13:27.560 align:start position:0% use the second is of course the stack 00:13:27.560 --> 00:13:29.110 align:start position:0% use the second is of course the stack must<00:13:27.680> be<00:13:27.800> complete<00:13:28.160> open<00:13:28.440> source<00:13:28.839> all 00:13:29.110 --> 00:13:29.120 align:start position:0% must be complete open source all 00:13:29.120 --> 00:13:31.310 align:start position:0% must be complete open source all allowing<00:13:29.360> to<00:13:29.440> be<00:13:29.560> easily<00:13:29.880> audited<00:13:30.600> edited<00:13:31.160> and 00:13:31.310 --> 00:13:31.320 align:start position:0% allowing to be easily audited edited and 00:13:31.320 --> 00:13:32.910 align:start position:0% allowing to be easily audited edited and fought<00:13:31.839> if 00:13:32.910 --> 00:13:32.920 align:start position:0% fought if 00:13:32.920 --> 00:13:35.389 align:start position:0% fought if required<00:13:33.920> and<00:13:34.160> lastly<00:13:34.720> we<00:13:34.880> care<00:13:35.079> about<00:13:35.279> the 00:13:35.389 --> 00:13:35.399 align:start position:0% required and lastly we care about the 00:13:35.399 --> 00:13:37.670 align:start position:0% required and lastly we care about the credible<00:13:35.720> neutrality<00:13:36.399> and<00:13:36.680> decentralization 00:13:37.670 --> 00:13:37.680 align:start position:0% credible neutrality and decentralization 00:13:37.680 --> 00:13:40.269 align:start position:0% credible neutrality and decentralization of<00:13:37.880> ens<00:13:38.600> and<00:13:38.800> maintaining<00:13:39.519> that<00:13:39.880> is<00:13:40.000> a 00:13:40.269 --> 00:13:40.279 align:start position:0% of ens and maintaining that is a 00:13:40.279 --> 00:13:42.710 align:start position:0% of ens and maintaining that is a priority<00:13:41.279> we're<00:13:41.519> exploring<00:13:42.040> whether<00:13:42.360> shared 00:13:42.710 --> 00:13:42.720 align:start position:0% priority we're exploring whether shared 00:13:42.720 --> 00:13:44.629 align:start position:0% priority we're exploring whether shared sequencing<00:13:43.320> or<00:13:43.519> base<00:13:43.760> sequencing<00:13:44.399> makes 00:13:44.629 --> 00:13:44.639 align:start position:0% sequencing or base sequencing makes 00:13:44.639 --> 00:13:46.990 align:start position:0% sequencing or base sequencing makes sense<00:13:44.839> for<00:13:45.000> us<00:13:45.240> at<00:13:45.360> name<00:13:45.600> chain<00:13:46.279> as<00:13:46.399> for 00:13:46.990 --> 00:13:47.000 align:start position:0% sense for us at name chain as for 00:13:47.000 --> 00:13:51.790 align:start position:0% sense for us at name chain as for decentralization<00:13:48.000> is<00:13:48.240> non-negotiable<00:13:49.040> for 00:13:51.790 --> 00:13:51.800 align:start position:0% 00:13:51.800 --> 00:13:54.509 align:start position:0% us<00:13:52.800> we're<00:13:52.959> going<00:13:53.160> to<00:13:53.279> be<00:13:53.399> building<00:13:53.720> L2<00:13:54.079> to<00:13:54.199> L2 00:13:54.509 --> 00:13:54.519 align:start position:0% us we're going to be building L2 to L2 00:13:54.519 --> 00:13:56.189 align:start position:0% us we're going to be building L2 to L2 bridging<00:13:55.000> right<00:13:55.160> into<00:13:55.360> the<00:13:55.480> protocol<00:13:55.959> so<00:13:56.079> you 00:13:56.189 --> 00:13:56.199 align:start position:0% bridging right into the protocol so you 00:13:56.199 --> 00:13:57.949 align:start position:0% bridging right into the protocol so you can<00:13:56.320> do<00:13:56.480> things<00:13:56.759> like<00:13:56.959> commit<00:13:57.560> whilst<00:13:57.800> you 00:13:57.949 --> 00:13:57.959 align:start position:0% can do things like commit whilst you 00:13:57.959 --> 00:14:00.990 align:start position:0% can do things like commit whilst you bridge<00:13:58.639> and<00:13:58.839> pay<00:13:59.240> from<00:13:59.360> your<00:13:59.440> preferred<00:14:00.000> L2 00:14:00.990 --> 00:14:01.000 align:start position:0% bridge and pay from your preferred L2 00:14:01.000 --> 00:14:02.629 align:start position:0% bridge and pay from your preferred L2 this<00:14:01.079> will<00:14:01.279> allow<00:14:01.480> you<00:14:01.600> to<00:14:01.759> start<00:14:02.000> your<00:14:02.199> ens 00:14:02.629 --> 00:14:02.639 align:start position:0% this will allow you to start your ens 00:14:02.639 --> 00:14:05.509 align:start position:0% this will allow you to start your ens Journey<00:14:03.279> from<00:14:03.560> any<00:14:03.839> L2<00:14:04.600> lowering<00:14:05.079> the<00:14:05.199> Barrow 00:14:05.509 --> 00:14:05.519 align:start position:0% Journey from any L2 lowering the Barrow 00:14:05.519 --> 00:14:08.110 align:start position:0% Journey from any L2 lowering the Barrow to<00:14:05.639> entry<00:14:06.240> when<00:14:06.360> you<00:14:06.480> buy<00:14:06.639> your<00:14:06.800> first<00:14:07.120> name 00:14:08.110 --> 00:14:08.120 align:start position:0% to entry when you buy your first name 00:14:08.120 --> 00:14:09.350 align:start position:0% to entry when you buy your first name and<00:14:08.240> this<00:14:08.320> is<00:14:08.440> one<00:14:08.519> of<00:14:08.600> the<00:14:08.720> primary<00:14:09.040> reasons 00:14:09.350 --> 00:14:09.360 align:start position:0% and this is one of the primary reasons 00:14:09.360 --> 00:14:11.430 align:start position:0% and this is one of the primary reasons we<00:14:09.440> wanted<00:14:09.639> to<00:14:09.759> launch<00:14:10.120> our<00:14:10.279> own<00:14:10.519> Chain<00:14:11.120> versus 00:14:11.430 --> 00:14:11.440 align:start position:0% we wanted to launch our own Chain versus 00:14:11.440 --> 00:14:13.430 align:start position:0% we wanted to launch our own Chain versus deploying<00:14:11.800> to<00:14:11.959> another<00:14:12.240> public<00:14:12.480> chain<00:14:13.199> being 00:14:13.430 --> 00:14:13.440 align:start position:0% deploying to another public chain being 00:14:13.440 --> 00:14:15.110 align:start position:0% deploying to another public chain being able<00:14:13.639> to<00:14:13.800> control<00:14:14.160> the<00:14:14.279> entire<00:14:14.600> stack<00:14:14.920> from 00:14:15.110 --> 00:14:15.120 align:start position:0% able to control the entire stack from 00:14:15.120 --> 00:14:16.509 align:start position:0% able to control the entire stack from protal<00:14:15.480> to<00:14:15.600> governance<00:14:15.959> means<00:14:16.199> that<00:14:16.399> this 00:14:16.509 --> 00:14:16.519 align:start position:0% protal to governance means that this 00:14:16.519 --> 00:14:20.110 align:start position:0% protal to governance means that this rollup<00:14:17.360> is<00:14:17.560> here<00:14:17.720> to<00:14:17.880> serve<00:14:18.480> ens<00:14:19.399> and 00:14:20.110 --> 00:14:20.120 align:start position:0% rollup is here to serve ens and 00:14:20.120 --> 00:14:22.749 align:start position:0% rollup is here to serve ens and naming<00:14:21.120> this<00:14:21.240> is<00:14:21.399> super<00:14:21.680> important<00:14:22.000> to<00:14:22.199> us<00:14:22.600> as 00:14:22.749 --> 00:14:22.759 align:start position:0% naming this is super important to us as 00:14:22.759 --> 00:14:27.670 align:start position:0% naming this is super important to us as we<00:14:22.880> are<00:14:23.079> ens<00:14:23.720> are<00:14:23.920> committed<00:14:24.320> to<00:14:24.519> being<00:14:24.800> L2 00:14:27.670 --> 00:14:27.680 align:start position:0% 00:14:27.680 --> 00:14:30.949 align:start position:0% agnostic<00:14:28.680> name<00:14:29.279> is<00:14:29.360> the<00:14:29.440> L2<00:14:29.759> we're<00:14:29.959> building 00:14:30.949 --> 00:14:30.959 align:start position:0% agnostic name is the L2 we're building 00:14:30.959 --> 00:14:34.110 align:start position:0% agnostic name is the L2 we're building but<00:14:31.079> we're<00:14:31.199> not<00:14:31.360> just<00:14:31.480> building<00:14:31.720> an<00:14:32.160> L2<00:14:33.160> ens<00:14:33.600> V2 00:14:34.110 --> 00:14:34.120 align:start position:0% but we're not just building an L2 ens V2 00:14:34.120 --> 00:14:36.470 align:start position:0% but we're not just building an L2 ens V2 is<00:14:34.199> a<00:14:34.399> complete<00:14:34.800> ground<00:14:35.079> up<00:14:35.279> redesign<00:14:35.639> of<00:14:35.800> ens 00:14:36.470 --> 00:14:36.480 align:start position:0% is a complete ground up redesign of ens 00:14:36.480 --> 00:14:38.310 align:start position:0% is a complete ground up redesign of ens and<00:14:36.680> only<00:14:37.000> one<00:14:37.279> component<00:14:37.680> of<00:14:37.800> that<00:14:37.959> is<00:14:38.120> having 00:14:38.310 --> 00:14:38.320 align:start position:0% and only one component of that is having 00:14:38.320 --> 00:14:40.990 align:start position:0% and only one component of that is having a<00:14:38.440> dedicated<00:14:38.920> L2<00:14:39.920> it's<00:14:40.120> designed<00:14:40.440> to<00:14:40.560> be<00:14:40.759> more 00:14:40.990 --> 00:14:41.000 align:start position:0% a dedicated L2 it's designed to be more 00:14:41.000 --> 00:14:43.470 align:start position:0% a dedicated L2 it's designed to be more flexible<00:14:41.920> more<00:14:42.240> accessible<00:14:43.079> and<00:14:43.279> more 00:14:43.470 --> 00:14:43.480 align:start position:0% flexible more accessible and more 00:14:43.480 --> 00:14:45.350 align:start position:0% flexible more accessible and more affordable<00:14:44.000> so<00:14:44.160> we<00:14:44.360> continue<00:14:44.680> the<00:14:44.800> momentum 00:14:45.350 --> 00:14:45.360 align:start position:0% affordable so we continue the momentum 00:14:45.360 --> 00:14:48.389 align:start position:0% affordable so we continue the momentum started<00:14:45.800> with<00:14:45.959> ccpi<00:14:46.600> ccpi<00:14:47.199> read<00:14:47.800> and<00:14:47.959> offchain 00:14:48.389 --> 00:14:48.399 align:start position:0% started with ccpi ccpi read and offchain 00:14:48.399 --> 00:14:50.829 align:start position:0% started with ccpi ccpi read and offchain names<00:14:49.240> and<00:14:49.440> expand<00:14:49.759> its<00:14:49.959> utility<00:14:50.360> to<00:14:50.600> every 00:14:50.829 --> 00:14:50.839 align:start position:0% names and expand its utility to every 00:14:50.839 --> 00:14:53.670 align:start position:0% names and expand its utility to every user<00:14:51.680> and<00:14:51.959> application<00:14:52.639> that<00:14:52.759> needs 00:14:53.670 --> 00:14:53.680 align:start position:0% user and application that needs 00:14:53.680 --> 00:14:56.790 align:start position:0% user and application that needs it<00:14:54.680> so<00:14:54.839> how<00:14:54.959> are<00:14:55.040> we<00:14:55.120> going<00:14:55.199> to<00:14:55.360> do<00:14:55.560> that<00:14:56.519> well 00:14:56.790 --> 00:14:56.800 align:start position:0% it so how are we going to do that well 00:14:56.800 --> 00:14:59.069 align:start position:0% it so how are we going to do that well first<00:14:57.480> we've<00:14:57.759> redefined<00:14:58.399> how<00:14:58.600> names<00:14:58.800> are 00:14:59.069 --> 00:14:59.079 align:start position:0% first we've redefined how names are 00:14:59.079 --> 00:15:00.550 align:start position:0% first we've redefined how names are registered<00:14:59.480> and<00:14:59.680> recorded<00:15:00.279> with<00:15:00.399> a 00:15:00.550 --> 00:15:00.560 align:start position:0% registered and recorded with a 00:15:00.560 --> 00:15:02.509 align:start position:0% registered and recorded with a completely<00:15:00.959> redesigned 00:15:02.509 --> 00:15:02.519 align:start position:0% completely redesigned 00:15:02.519 --> 00:15:05.509 align:start position:0% completely redesigned registry<00:15:03.519> second<00:15:04.440> do<00:15:04.680> e<00:15:04.920> names<00:15:05.160> will<00:15:05.320> be 00:15:05.509 --> 00:15:05.519 align:start position:0% registry second do e names will be 00:15:05.519 --> 00:15:08.110 align:start position:0% registry second do e names will be recorded<00:15:06.279> and<00:15:06.519> by<00:15:06.680> default<00:15:07.320> hosted<00:15:07.759> on<00:15:07.920> our 00:15:08.110 --> 00:15:08.120 align:start position:0% recorded and by default hosted on our 00:15:08.120 --> 00:15:10.389 align:start position:0% recorded and by default hosted on our dedicated<00:15:08.560> L2<00:15:09.320> name 00:15:10.389 --> 00:15:10.399 align:start position:0% dedicated L2 name 00:15:10.399 --> 00:15:12.790 align:start position:0% dedicated L2 name chain<00:15:11.399> and<00:15:11.600> finally<00:15:12.040> a<00:15:12.199> user-driven 00:15:12.790 --> 00:15:12.800 align:start position:0% chain and finally a user-driven 00:15:12.800 --> 00:15:15.430 align:start position:0% chain and finally a user-driven migration<00:15:13.800> with<00:15:13.959> backwards<00:15:14.440> compatibility 00:15:15.430 --> 00:15:15.440 align:start position:0% migration with backwards compatibility 00:15:15.440 --> 00:15:18.670 align:start position:0% migration with backwards compatibility and<00:15:15.600> let's<00:15:15.880> explore<00:15:16.279> these<00:15:16.560> in<00:15:16.680> a<00:15:16.800> bit<00:15:16.920> more 00:15:18.670 --> 00:15:18.680 align:start position:0% and let's explore these in a bit more 00:15:18.680 --> 00:15:21.310 align:start position:0% and let's explore these in a bit more detail<00:15:19.680> e<00:15:19.880> on<00:15:20.040> name<00:15:20.240> chain<00:15:20.519> means<00:15:20.800> that<00:15:21.000> all 00:15:21.310 --> 00:15:21.320 align:start position:0% detail e on name chain means that all 00:15:21.320 --> 00:15:23.269 align:start position:0% detail e on name chain means that all registration<00:15:21.880> renewals<00:15:22.519> will<00:15:22.720> no<00:15:23.000> longer 00:15:23.269 --> 00:15:23.279 align:start position:0% registration renewals will no longer 00:15:23.279 --> 00:15:25.350 align:start position:0% registration renewals will no longer live<00:15:23.440> on<00:15:23.560> ethereum<00:15:23.959> L1<00:15:24.600> but<00:15:24.720> instead<00:15:24.959> on<00:15:25.120> name 00:15:25.350 --> 00:15:25.360 align:start position:0% live on ethereum L1 but instead on name 00:15:25.360 --> 00:15:27.550 align:start position:0% live on ethereum L1 but instead on name chain<00:15:26.120> storing<00:15:26.560> it<00:15:26.680> on<00:15:26.839> name<00:15:27.040> chain<00:15:27.279> means 00:15:27.550 --> 00:15:27.560 align:start position:0% chain storing it on name chain means 00:15:27.560 --> 00:15:29.470 align:start position:0% chain storing it on name chain means that<00:15:27.720> registration<00:15:28.240> renewal<00:15:28.639> gas<00:15:29.040> will<00:15:29.199> be 00:15:29.470 --> 00:15:29.480 align:start position:0% that registration renewal gas will be 00:15:29.480 --> 00:15:30.990 align:start position:0% that registration renewal gas will be significantly 00:15:30.990 --> 00:15:31.000 align:start position:0% significantly 00:15:31.000 --> 00:15:32.990 align:start position:0% significantly lower<00:15:32.000> although<00:15:32.319> ethereum<00:15:32.720> has<00:15:32.880> its 00:15:32.990 --> 00:15:33.000 align:start position:0% lower although ethereum has its 00:15:33.000 --> 00:15:34.550 align:start position:0% lower although ethereum has its conveniences<00:15:33.680> it's<00:15:33.839> not<00:15:33.959> a<00:15:34.079> long-term 00:15:34.550 --> 00:15:34.560 align:start position:0% conveniences it's not a long-term 00:15:34.560 --> 00:15:37.069 align:start position:0% conveniences it's not a long-term solution<00:15:34.880> for<00:15:35.079> gas<00:15:35.319> prices<00:15:35.560> on<00:15:35.759> L1<00:15:36.759> having 00:15:37.069 --> 00:15:37.079 align:start position:0% solution for gas prices on L1 having 00:15:37.079 --> 00:15:38.389 align:start position:0% solution for gas prices on L1 having registration<00:15:37.600> name<00:15:37.759> chain<00:15:37.959> means<00:15:38.160> we<00:15:38.279> can 00:15:38.389 --> 00:15:38.399 align:start position:0% registration name chain means we can 00:15:38.399 --> 00:15:40.110 align:start position:0% registration name chain means we can ensure<00:15:38.720> registration<00:15:39.199> gas<00:15:39.440> costs<00:15:39.759> as<00:15:39.920> close 00:15:40.110 --> 00:15:40.120 align:start position:0% ensure registration gas costs as close 00:15:40.120 --> 00:15:42.030 align:start position:0% ensure registration gas costs as close to<00:15:40.319> zero<00:15:40.639> as 00:15:42.030 --> 00:15:42.040 align:start position:0% to zero as 00:15:42.040 --> 00:15:45.030 align:start position:0% to zero as possible<00:15:43.079> however<00:15:44.079> even<00:15:44.279> though<00:15:44.639> e<00:15:44.800> names 00:15:45.030 --> 00:15:45.040 align:start position:0% possible however even though e names 00:15:45.040 --> 00:15:47.629 align:start position:0% possible however even though e names will<00:15:45.199> move<00:15:45.360> to<00:15:45.519> name<00:15:45.720> chain<00:15:46.560> name<00:15:46.959> resolution 00:15:47.629 --> 00:15:47.639 align:start position:0% will move to name chain name resolution 00:15:47.639 --> 00:15:49.670 align:start position:0% will move to name chain name resolution largely<00:15:48.160> remains<00:15:48.440> untouched<00:15:49.199> and<00:15:49.360> begins 00:15:49.670 --> 00:15:49.680 align:start position:0% largely remains untouched and begins 00:15:49.680 --> 00:15:51.030 align:start position:0% largely remains untouched and begins from<00:15:49.880> ethereum 00:15:51.030 --> 00:15:51.040 align:start position:0% from ethereum 00:15:51.040 --> 00:15:53.829 align:start position:0% from ethereum itself<00:15:52.040> let<00:15:52.160> me<00:15:52.319> reiterate<00:15:52.800> that<00:15:53.399> ens 00:15:53.829 --> 00:15:53.839 align:start position:0% itself let me reiterate that ens 00:15:53.839 --> 00:15:56.910 align:start position:0% itself let me reiterate that ens resolution<00:15:54.759> reading<00:15:55.240> from<00:15:55.440> ens<00:15:55.920> names 00:15:56.910 --> 00:15:56.920 align:start position:0% resolution reading from ens names 00:15:56.920 --> 00:15:59.389 align:start position:0% resolution reading from ens names remains<00:15:57.360> anchored<00:15:57.800> on<00:15:57.959> L1<00:15:58.800> and<00:15:59.000> that<00:15:59.120> is<00:15:59.240> a 00:15:59.389 --> 00:15:59.399 align:start position:0% remains anchored on L1 and that is a 00:15:59.399 --> 00:16:01.749 align:start position:0% remains anchored on L1 and that is a fundamental<00:16:00.040> difference<00:16:00.440> between<00:16:00.800> ens<00:16:01.600> and 00:16:01.749 --> 00:16:01.759 align:start position:0% fundamental difference between ens and 00:16:01.759 --> 00:16:05.150 align:start position:0% fundamental difference between ens and other<00:16:02.040> protocols<00:16:02.560> moving<00:16:02.839> to<00:16:03.040> L2<00:16:04.040> we<00:16:04.279> do<00:16:04.519> not 00:16:05.150 --> 00:16:05.160 align:start position:0% other protocols moving to L2 we do not 00:16:05.160 --> 00:16:07.990 align:start position:0% other protocols moving to L2 we do not fractionalize<00:16:05.959> our<00:16:06.279> protocol<00:16:07.279> we<00:16:07.440> connect<00:16:07.720> it 00:16:07.990 --> 00:16:08.000 align:start position:0% fractionalize our protocol we connect it 00:16:08.000 --> 00:16:10.150 align:start position:0% fractionalize our protocol we connect it together<00:16:08.519> and<00:16:08.759> remain<00:16:08.959> as<00:16:09.160> one<00:16:09.680> and<00:16:09.839> this<00:16:09.959> is 00:16:10.150 --> 00:16:10.160 align:start position:0% together and remain as one and this is 00:16:10.160 --> 00:16:14.150 align:start position:0% together and remain as one and this is how<00:16:10.319> we<00:16:10.560> remain<00:16:10.880> L2 00:16:14.150 --> 00:16:14.160 align:start position:0% 00:16:14.160 --> 00:16:16.990 align:start position:0% agnostic<00:16:15.160> L2<00:16:15.639> was<00:16:15.759> a<00:16:16.160> L2<00:16:16.519> support<00:16:16.800> was<00:16:16.880> a 00:16:16.990 --> 00:16:17.000 align:start position:0% agnostic L2 was a L2 support was a 00:16:17.000 --> 00:16:18.110 align:start position:0% agnostic L2 was a L2 support was a consideration<00:16:17.440> for<00:16:17.600> the<00:16:17.680> beginning<00:16:17.920> of<00:16:18.040> the 00:16:18.110 --> 00:16:18.120 align:start position:0% consideration for the beginning of the 00:16:18.120 --> 00:16:19.990 align:start position:0% consideration for the beginning of the design<00:16:18.399> process<00:16:18.720> of<00:16:18.839> V2<00:16:19.399> and<00:16:19.519> that<00:16:19.639> means<00:16:19.880> we 00:16:19.990 --> 00:16:20.000 align:start position:0% design process of V2 and that means we 00:16:20.000 --> 00:16:22.030 align:start position:0% design process of V2 and that means we can<00:16:20.120> also<00:16:20.399> deploy<00:16:20.759> the<00:16:20.880> V2<00:16:21.240> contracts<00:16:21.600> to<00:16:21.720> L2 00:16:22.030 --> 00:16:22.040 align:start position:0% can also deploy the V2 contracts to L2 00:16:22.040 --> 00:16:24.629 align:start position:0% can also deploy the V2 contracts to L2 networks<00:16:22.959> combined<00:16:23.319> with<00:16:23.399> ccip<00:16:23.959> read<00:16:24.480> this 00:16:24.629 --> 00:16:24.639 align:start position:0% networks combined with ccip read this 00:16:24.639 --> 00:16:26.350 align:start position:0% networks combined with ccip read this makes<00:16:24.800> it<00:16:25.000> possible<00:16:25.279> to<00:16:25.440> seamlessly<00:16:25.959> stitch 00:16:26.350 --> 00:16:26.360 align:start position:0% makes it possible to seamlessly stitch 00:16:26.360 --> 00:16:28.910 align:start position:0% makes it possible to seamlessly stitch together<00:16:26.880> a<00:16:27.120> coherent<00:16:27.639> name<00:16:27.959> space<00:16:28.440> from<00:16:28.680> m 00:16:28.910 --> 00:16:28.920 align:start position:0% together a coherent name space from m 00:16:28.920 --> 00:16:32.949 align:start position:0% together a coherent name space from m multiple<00:16:29.600> distinct<00:16:30.440> networks<00:16:31.040> and<00:16:31.680> l2s<00:16:32.680> this 00:16:32.949 --> 00:16:32.959 align:start position:0% multiple distinct networks and l2s this 00:16:32.959 --> 00:16:34.990 align:start position:0% multiple distinct networks and l2s this architecture<00:16:33.800> reinforces<00:16:34.560> how<00:16:34.720> we<00:16:34.839> are 00:16:34.990 --> 00:16:35.000 align:start position:0% architecture reinforces how we are 00:16:35.000 --> 00:16:37.590 align:start position:0% architecture reinforces how we are staying<00:16:35.639> L2<00:16:36.079> agnostic<00:16:36.880> beginning<00:16:37.279> everything 00:16:37.590 --> 00:16:37.600 align:start position:0% staying L2 agnostic beginning everything 00:16:37.600 --> 00:16:40.269 align:start position:0% staying L2 agnostic beginning everything from<00:16:37.800> L1<00:16:38.480> but<00:16:38.639> only<00:16:38.880> moving<00:16:39.560> eth<00:16:39.880> to<00:16:40.040> name 00:16:40.269 --> 00:16:40.279 align:start position:0% from L1 but only moving eth to name 00:16:40.279 --> 00:16:44.030 align:start position:0% from L1 but only moving eth to name chain<00:16:40.880> while<00:16:41.079> supporting<00:16:41.560> ens<00:16:42.240> on<00:16:42.399> other 00:16:44.030 --> 00:16:44.040 align:start position:0% chain while supporting ens on other 00:16:44.040 --> 00:16:47.189 align:start position:0% chain while supporting ens on other l2s<00:16:45.040> okay<00:16:45.240> let's<00:16:45.519> talk<00:16:45.800> about<00:16:46.560> the<00:16:46.759> complete 00:16:47.189 --> 00:16:47.199 align:start position:0% l2s okay let's talk about the complete 00:16:47.199 --> 00:16:49.269 align:start position:0% l2s okay let's talk about the complete technical<00:16:47.560> rewrite<00:16:48.000> of<00:16:48.079> the<00:16:48.199> ens 00:16:49.269 --> 00:16:49.279 align:start position:0% technical rewrite of the ens 00:16:49.279 --> 00:16:51.749 align:start position:0% technical rewrite of the ens registry<00:16:50.279> Registries<00:16:50.839> are<00:16:51.120> contracts<00:16:51.639> that 00:16:51.749 --> 00:16:51.759 align:start position:0% registry Registries are contracts that 00:16:51.759 --> 00:16:53.910 align:start position:0% registry Registries are contracts that store<00:16:52.079> data<00:16:52.360> about<00:16:52.560> that<00:16:52.720> name<00:16:53.480> the<00:16:53.639> current 00:16:53.910 --> 00:16:53.920 align:start position:0% store data about that name the current 00:16:53.920 --> 00:16:56.230 align:start position:0% store data about that name the current registry<00:16:54.680> stores<00:16:55.040> the<00:16:55.160> owner<00:16:55.600> and<00:16:55.800> resolver 00:16:56.230 --> 00:16:56.240 align:start position:0% registry stores the owner and resolver 00:16:56.240 --> 00:16:58.030 align:start position:0% registry stores the owner and resolver records<00:16:56.839> and<00:16:57.000> currently<00:16:57.480> all<00:16:57.680> names<00:16:57.920> are 00:16:58.030 --> 00:16:58.040 align:start position:0% records and currently all names are 00:16:58.040 --> 00:17:00.710 align:start position:0% records and currently all names are stored<00:16:58.360> in<00:16:58.440> a<00:16:58.519> single<00:16:58.959> flat<00:16:59.560> registry<00:17:00.560> this 00:17:00.710 --> 00:17:00.720 align:start position:0% stored in a single flat registry this 00:17:00.720 --> 00:17:02.710 align:start position:0% stored in a single flat registry this design<00:17:00.959> is<00:17:01.120> straightforward<00:17:02.000> but<00:17:02.160> also<00:17:02.440> has<00:17:02.560> a 00:17:02.710 --> 00:17:02.720 align:start position:0% design is straightforward but also has a 00:17:02.720 --> 00:17:05.029 align:start position:0% design is straightforward but also has a couple<00:17:02.959> of<00:17:03.199> significant<00:17:03.759> drawbacks<00:17:04.720> one<00:17:04.880> of 00:17:05.029 --> 00:17:05.039 align:start position:0% couple of significant drawbacks one of 00:17:05.039 --> 00:17:06.990 align:start position:0% couple of significant drawbacks one of which<00:17:05.240> that<00:17:05.360> is<00:17:05.720> difficult<00:17:05.839> to<00:17:06.079> find<00:17:06.600> custom 00:17:06.990 --> 00:17:07.000 align:start position:0% which that is difficult to find custom 00:17:07.000 --> 00:17:10.189 align:start position:0% which that is difficult to find custom rules<00:17:07.480> for<00:17:07.679> name<00:17:07.919> issuance<00:17:08.640> and<00:17:09.199> ownership 00:17:10.189 --> 00:17:10.199 align:start position:0% rules for name issuance and ownership 00:17:10.199 --> 00:17:12.230 align:start position:0% rules for name issuance and ownership another<00:17:10.559> is<00:17:10.679> that<00:17:10.880> because<00:17:11.240> each<00:17:11.439> name<00:17:11.880> exists 00:17:12.230 --> 00:17:12.240 align:start position:0% another is that because each name exists 00:17:12.240 --> 00:17:14.110 align:start position:0% another is that because each name exists independently<00:17:12.880> in<00:17:13.000> the<00:17:13.120> registry<00:17:13.880> when<00:17:14.000> a 00:17:14.110 --> 00:17:14.120 align:start position:0% independently in the registry when a 00:17:14.120 --> 00:17:16.590 align:start position:0% independently in the registry when a name<00:17:14.280> is<00:17:14.439> transferred<00:17:15.079> or<00:17:15.360> deleted<00:17:16.360> all 00:17:16.590 --> 00:17:16.600 align:start position:0% name is transferred or deleted all 00:17:16.600 --> 00:17:18.390 align:start position:0% name is transferred or deleted all subnames<00:17:17.000> remain 00:17:18.390 --> 00:17:18.400 align:start position:0% subnames remain 00:17:18.400 --> 00:17:20.750 align:start position:0% subnames remain unchanged<00:17:19.400> we're<00:17:19.640> solving<00:17:20.120> both<00:17:20.480> both<00:17:20.640> of 00:17:20.750 --> 00:17:20.760 align:start position:0% unchanged we're solving both both of 00:17:20.760 --> 00:17:22.110 align:start position:0% unchanged we're solving both both of these<00:17:20.959> problems<00:17:21.400> while<00:17:21.559> adding<00:17:21.880> more 00:17:22.110 --> 00:17:22.120 align:start position:0% these problems while adding more 00:17:22.120 --> 00:17:24.630 align:start position:0% these problems while adding more flexibility<00:17:22.640> to<00:17:22.760> the<00:17:22.959> system<00:17:23.520> as<00:17:23.640> a<00:17:23.799> whole<00:17:24.439> by 00:17:24.630 --> 00:17:24.640 align:start position:0% flexibility to the system as a whole by 00:17:24.640 --> 00:17:27.189 align:start position:0% flexibility to the system as a whole by introducing<00:17:25.160> a<00:17:25.280> new<00:17:25.480> registry<00:17:25.959> design<00:17:26.280> in<00:17:26.439> EN 00:17:27.189 --> 00:17:27.199 align:start position:0% introducing a new registry design in EN 00:17:27.199 --> 00:17:30.390 align:start position:0% introducing a new registry design in EN V2<00:17:28.199> in<00:17:28.360> V2<00:17:29.160> each<00:17:29.400> name<00:17:29.720> optionally<00:17:30.120> has<00:17:30.240> its 00:17:30.390 --> 00:17:30.400 align:start position:0% V2 in V2 each name optionally has its 00:17:30.400 --> 00:17:32.470 align:start position:0% V2 in V2 each name optionally has its own<00:17:30.559> registry<00:17:31.240> which<00:17:31.400> deals<00:17:31.880> exclusively 00:17:32.470 --> 00:17:32.480 align:start position:0% own registry which deals exclusively 00:17:32.480 --> 00:17:34.630 align:start position:0% own registry which deals exclusively with<00:17:32.600> its<00:17:32.960> subdomains<00:17:33.960> there's<00:17:34.160> a<00:17:34.320> root 00:17:34.630 --> 00:17:34.640 align:start position:0% with its subdomains there's a root 00:17:34.640 --> 00:17:36.390 align:start position:0% with its subdomains there's a root registry<00:17:35.400> which<00:17:35.559> contains<00:17:35.960> all<00:17:36.080> the<00:17:36.200> top 00:17:36.390 --> 00:17:36.400 align:start position:0% registry which contains all the top 00:17:36.400 --> 00:17:38.710 align:start position:0% registry which contains all the top level<00:17:36.600> names<00:17:37.440> each<00:17:37.679> top<00:17:37.919> level<00:17:38.120> name<00:17:38.440> has<00:17:38.520> a 00:17:38.710 --> 00:17:38.720 align:start position:0% level names each top level name has a 00:17:38.720 --> 00:17:40.430 align:start position:0% level names each top level name has a registry<00:17:39.240> containing<00:17:39.640> all<00:17:39.799> the<00:17:39.919> second<00:17:40.200> level 00:17:40.430 --> 00:17:40.440 align:start position:0% registry containing all the second level 00:17:40.440 --> 00:17:43.470 align:start position:0% registry containing all the second level names<00:17:41.039> such<00:17:41.200> as<00:17:41.320> nick.<00:17:41.720> eth<00:17:41.960> and<00:17:42.120> so 00:17:43.470 --> 00:17:43.480 align:start position:0% names such as nick. eth and so 00:17:43.480 --> 00:17:46.789 align:start position:0% names such as nick. eth and so forth<00:17:44.480> using<00:17:44.880> a<00:17:45.039> hierarchy<00:17:45.840> of<00:17:46.039> Registries 00:17:46.789 --> 00:17:46.799 align:start position:0% forth using a hierarchy of Registries 00:17:46.799 --> 00:17:48.950 align:start position:0% forth using a hierarchy of Registries has<00:17:46.919> a<00:17:47.039> number<00:17:47.200> of<00:17:47.480> advantages<00:17:48.480> anyone<00:17:48.840> who 00:17:48.950 --> 00:17:48.960 align:start position:0% has a number of advantages anyone who 00:17:48.960 --> 00:17:50.830 align:start position:0% has a number of advantages anyone who owns<00:17:49.200> a<00:17:49.360> name<00:17:49.640> can<00:17:49.799> now<00:17:49.960> Supply<00:17:50.320> the<00:17:50.440> registry 00:17:50.830 --> 00:17:50.840 align:start position:0% owns a name can now Supply the registry 00:17:50.840 --> 00:17:53.070 align:start position:0% owns a name can now Supply the registry implementation<00:17:51.600> of<00:17:51.799> their<00:17:52.000> choice<00:17:52.679> giving 00:17:53.070 --> 00:17:53.080 align:start position:0% implementation of their choice giving 00:17:53.080 --> 00:17:55.549 align:start position:0% implementation of their choice giving full<00:17:53.360> control<00:17:53.799> on<00:17:54.039> how<00:17:54.240> subnames<00:17:54.600> are<00:17:54.919> issued 00:17:55.549 --> 00:17:55.559 align:start position:0% full control on how subnames are issued 00:17:55.559 --> 00:17:57.789 align:start position:0% full control on how subnames are issued and<00:17:55.799> controlled<00:17:56.799> this<00:17:56.960> allows<00:17:57.440> all<00:17:57.640> the 00:17:57.789 --> 00:17:57.799 align:start position:0% and controlled this allows all the 00:17:57.799 --> 00:17:59.549 align:start position:0% and controlled this allows all the functionality<00:17:58.400> of<00:17:58.520> the<00:17:58.640> name<00:17:58.840> name<00:17:59.000> rapper 00:17:59.549 --> 00:17:59.559 align:start position:0% functionality of the name name rapper 00:17:59.559 --> 00:18:01.310 align:start position:0% functionality of the name name rapper and<00:17:59.720> more<00:18:00.360> whilst<00:18:00.679> preserving<00:18:01.120> the 00:18:01.310 --> 00:18:01.320 align:start position:0% and more whilst preserving the 00:18:01.320 --> 00:18:03.390 align:start position:0% and more whilst preserving the flexibility<00:18:01.919> for<00:18:02.120> name<00:18:02.320> owners<00:18:02.880> to<00:18:03.039> set<00:18:03.240> their 00:18:03.390 --> 00:18:03.400 align:start position:0% flexibility for name owners to set their 00:18:03.400 --> 00:18:08.669 align:start position:0% flexibility for name owners to set their own<00:18:03.640> rules<00:18:04.360> ownership<00:18:05.360> and<00:18:05.880> even 00:18:08.669 --> 00:18:08.679 align:start position:0% 00:18:08.679 --> 00:18:11.110 align:start position:0% resolution<00:18:09.679> when<00:18:09.840> a<00:18:09.960> name<00:18:10.120> changes<00:18:10.559> hands<00:18:11.000> or 00:18:11.110 --> 00:18:11.120 align:start position:0% resolution when a name changes hands or 00:18:11.120 --> 00:18:12.750 align:start position:0% resolution when a name changes hands or if<00:18:11.200> an<00:18:11.320> owner<00:18:11.559> wants<00:18:11.720> to<00:18:11.840> start<00:18:12.039> from<00:18:12.240> scratch 00:18:12.750 --> 00:18:12.760 align:start position:0% if an owner wants to start from scratch 00:18:12.760 --> 00:18:14.430 align:start position:0% if an owner wants to start from scratch they<00:18:12.880> can<00:18:13.120> easily<00:18:13.520> replace<00:18:13.840> the<00:18:14.000> registry 00:18:14.430 --> 00:18:14.440 align:start position:0% they can easily replace the registry 00:18:14.440 --> 00:18:15.630 align:start position:0% they can easily replace the registry from<00:18:14.640> a<00:18:14.799> name 00:18:15.630 --> 00:18:15.640 align:start position:0% from a name 00:18:15.640 --> 00:18:18.230 align:start position:0% from a name entirely<00:18:16.640> erasing<00:18:17.159> all<00:18:17.440> existing<00:18:17.840> subnames 00:18:18.230 --> 00:18:18.240 align:start position:0% entirely erasing all existing subnames 00:18:18.240 --> 00:18:21.430 align:start position:0% entirely erasing all existing subnames allowing<00:18:18.840> a<00:18:19.080> very<00:18:19.520> easy<00:18:20.320> fuss-free<00:18:20.799> way<00:18:21.280> of 00:18:21.430 --> 00:18:21.440 align:start position:0% allowing a very easy fuss-free way of 00:18:21.440 --> 00:18:24.430 align:start position:0% allowing a very easy fuss-free way of clearing<00:18:21.799> up<00:18:21.960> the<00:18:22.120> hierarchy<00:18:22.600> of<00:18:22.799> your<00:18:23.440> name 00:18:24.430 --> 00:18:24.440 align:start position:0% clearing up the hierarchy of your name 00:18:24.440 --> 00:18:26.789 align:start position:0% clearing up the hierarchy of your name likewise<00:18:25.440> because<00:18:25.760> each<00:18:26.000> registry<00:18:26.440> exists 00:18:26.789 --> 00:18:26.799 align:start position:0% likewise because each registry exists 00:18:26.799 --> 00:18:28.789 align:start position:0% likewise because each registry exists independently<00:18:27.640> we<00:18:27.799> can<00:18:28.039> even<00:18:28.280> insert 00:18:28.789 --> 00:18:28.799 align:start position:0% independently we can even insert 00:18:28.799 --> 00:18:31.590 align:start position:0% independently we can even insert Registries<00:18:29.200> at<00:18:29.400> multiple<00:18:29.799> places<00:18:30.120> in<00:18:30.200> the<00:18:30.360> ens 00:18:31.590 --> 00:18:31.600 align:start position:0% Registries at multiple places in the ens 00:18:31.600 --> 00:18:33.470 align:start position:0% Registries at multiple places in the ens hierarchy<00:18:32.600> when<00:18:32.720> you're<00:18:32.880> ready<00:18:33.039> to<00:18:33.159> move<00:18:33.400> from 00:18:33.470 --> 00:18:33.480 align:start position:0% hierarchy when you're ready to move from 00:18:33.480 --> 00:18:35.549 align:start position:0% hierarchy when you're ready to move from a<00:18:33.640> subname<00:18:34.000> to<00:18:34.159> an<00:18:34.240> eth<00:18:34.559> name<00:18:34.679> of<00:18:34.799> your<00:18:34.919> own<00:18:35.480> you 00:18:35.549 --> 00:18:35.559 align:start position:0% a subname to an eth name of your own you 00:18:35.559 --> 00:18:37.270 align:start position:0% a subname to an eth name of your own you can<00:18:35.760> bring<00:18:36.120> everything<00:18:36.440> with<00:18:36.600> you<00:18:37.120> while 00:18:37.270 --> 00:18:37.280 align:start position:0% can bring everything with you while 00:18:37.280 --> 00:18:39.310 align:start position:0% can bring everything with you while still<00:18:37.559> ensuring<00:18:37.960> your<00:18:38.120> old<00:18:38.360> name<00:18:38.640> functions 00:18:39.310 --> 00:18:39.320 align:start position:0% still ensuring your old name functions 00:18:39.320 --> 00:18:41.990 align:start position:0% still ensuring your old name functions as<00:18:39.400> it<00:18:39.559> did 00:18:41.990 --> 00:18:42.000 align:start position:0% 00:18:42.000 --> 00:18:45.390 align:start position:0% before<00:18:43.000> in<00:18:43.200> line<00:18:43.480> with<00:18:43.640> 's<00:18:44.200> core<00:18:44.480> principles 00:18:45.390 --> 00:18:45.400 align:start position:0% before in line with 's core principles 00:18:45.400 --> 00:18:47.590 align:start position:0% before in line with 's core principles moving<00:18:45.720> to<00:18:45.880> V2<00:18:46.280> is<00:18:46.400> an<00:18:46.600> entirely<00:18:47.039> user-driven 00:18:47.590 --> 00:18:47.600 align:start position:0% moving to V2 is an entirely user-driven 00:18:47.600 --> 00:18:50.310 align:start position:0% moving to V2 is an entirely user-driven and<00:18:48.000> optim<00:18:48.440> process<00:18:49.360> all<00:18:49.600> registrations<00:18:50.159> will 00:18:50.310 --> 00:18:50.320 align:start position:0% and optim process all registrations will 00:18:50.320 --> 00:18:52.430 align:start position:0% and optim process all registrations will be<00:18:50.440> transferred<00:18:50.919> to<00:18:51.000> the<00:18:51.120> new<00:18:51.240> L2<00:18:51.640> chain 00:18:52.430 --> 00:18:52.440 align:start position:0% be transferred to the new L2 chain 00:18:52.440 --> 00:18:54.310 align:start position:0% be transferred to the new L2 chain because<00:18:52.799> by<00:18:52.960> its<00:18:53.120> nature<00:18:53.559> a<00:18:53.679> registry<00:18:54.120> has<00:18:54.200> to 00:18:54.310 --> 00:18:54.320 align:start position:0% because by its nature a registry has to 00:18:54.320 --> 00:18:56.630 align:start position:0% because by its nature a registry has to be<00:18:54.400> stored<00:18:54.840> all<00:18:55.000> in<00:18:55.159> one<00:18:55.400> location<00:18:56.400> but<00:18:56.520> the 00:18:56.630 --> 00:18:56.640 align:start position:0% be stored all in one location but the 00:18:56.640 --> 00:18:59.110 align:start position:0% be stored all in one location but the names<00:18:57.080> themselves<00:18:57.919> their<00:18:58.159> records<00:18:58.919> and 00:18:59.110 --> 00:18:59.120 align:start position:0% names themselves their records and 00:18:59.120 --> 00:19:01.350 align:start position:0% names themselves their records and subnames<00:18:59.520> however<00:19:00.360> can<00:19:00.559> continue<00:19:00.919> to<00:19:01.120> exist 00:19:01.350 --> 00:19:01.360 align:start position:0% subnames however can continue to exist 00:19:01.360 --> 00:19:04.230 align:start position:0% subnames however can continue to exist on<00:19:01.559> ethereum<00:19:02.400> or<00:19:02.679> any<00:19:02.840> other<00:19:03.039> L2<00:19:03.720> or<00:19:03.880> offchain 00:19:04.230 --> 00:19:04.240 align:start position:0% on ethereum or any other L2 or offchain 00:19:04.240 --> 00:19:05.750 align:start position:0% on ethereum or any other L2 or offchain storage 00:19:05.750 --> 00:19:05.760 align:start position:0% storage 00:19:05.760 --> 00:19:08.350 align:start position:0% storage solution<00:19:06.760> after<00:19:07.039> launch<00:19:07.520> users<00:19:07.880> can<00:19:08.039> migrate 00:19:08.350 --> 00:19:08.360 align:start position:0% solution after launch users can migrate 00:19:08.360 --> 00:19:10.230 align:start position:0% solution after launch users can migrate their<00:19:08.480> names<00:19:08.720> to<00:19:08.840> V2<00:19:09.360> with<00:19:09.480> a<00:19:09.600> single 00:19:10.230 --> 00:19:10.240 align:start position:0% their names to V2 with a single 00:19:10.240 --> 00:19:12.149 align:start position:0% their names to V2 with a single transaction<00:19:11.240> this<00:19:11.320> will<00:19:11.480> move<00:19:11.679> the<00:19:11.799> name<00:19:12.039> from 00:19:12.149 --> 00:19:12.159 align:start position:0% transaction this will move the name from 00:19:12.159 --> 00:19:15.470 align:start position:0% transaction this will move the name from The<00:19:12.320> Legacy<00:19:12.919> flat<00:19:13.600> ens<00:19:14.080> registry<00:19:14.760> to<00:19:15.039> new 00:19:15.470 --> 00:19:15.480 align:start position:0% The Legacy flat ens registry to new 00:19:15.480 --> 00:19:18.190 align:start position:0% The Legacy flat ens registry to new hierarchical<00:19:16.400> one<00:19:17.400> at<00:19:17.520> the<00:19:17.600> same<00:19:17.840> time<00:19:18.080> they 00:19:18.190 --> 00:19:18.200 align:start position:0% hierarchical one at the same time they 00:19:18.200 --> 00:19:19.630 align:start position:0% hierarchical one at the same time they can<00:19:18.320> choose<00:19:18.520> to<00:19:18.760> either<00:19:18.919> leave<00:19:19.120> the<00:19:19.240> name<00:19:19.480> on 00:19:19.630 --> 00:19:19.640 align:start position:0% can choose to either leave the name on 00:19:19.640 --> 00:19:22.430 align:start position:0% can choose to either leave the name on L1<00:19:20.400> or<00:19:20.640> migrate<00:19:20.960> it<00:19:21.080> to<00:19:21.200> name 00:19:22.430 --> 00:19:22.440 align:start position:0% L1 or migrate it to name 00:19:22.440 --> 00:19:24.789 align:start position:0% L1 or migrate it to name chain<00:19:23.440> and<00:19:23.640> names<00:19:23.960> that<00:19:24.080> aren't<00:19:24.320> migrated 00:19:24.789 --> 00:19:24.799 align:start position:0% chain and names that aren't migrated 00:19:24.799 --> 00:19:27.070 align:start position:0% chain and names that aren't migrated will<00:19:25.039> continue<00:19:25.400> to<00:19:25.600> function<00:19:26.080> indefinitely 00:19:27.070 --> 00:19:27.080 align:start position:0% will continue to function indefinitely 00:19:27.080 --> 00:19:29.149 align:start position:0% will continue to function indefinitely the<00:19:27.240> new<00:19:27.440> ens<00:19:27.840> contracts<00:19:28.240> are<00:19:28.400> programed<00:19:28.960> to 00:19:29.149 --> 00:19:29.159 align:start position:0% the new ens contracts are programed to 00:19:29.159 --> 00:19:30.789 align:start position:0% the new ens contracts are programed to automatically<00:19:29.760> fall<00:19:30.080> back<00:19:30.200> to<00:19:30.360> looking<00:19:30.640> up 00:19:30.789 --> 00:19:30.799 align:start position:0% automatically fall back to looking up 00:19:30.799 --> 00:19:33.430 align:start position:0% automatically fall back to looking up names<00:19:31.159> in<00:19:31.240> the<00:19:31.480> version<00:19:31.799> one<00:19:32.280> registry<00:19:33.280> this 00:19:33.430 --> 00:19:33.440 align:start position:0% names in the version one registry this 00:19:33.440 --> 00:19:35.110 align:start position:0% names in the version one registry this means<00:19:33.720> that<00:19:33.840> for<00:19:34.000> names<00:19:34.240> that<00:19:34.440> owned<00:19:34.760> by 00:19:35.110 --> 00:19:35.120 align:start position:0% means that for names that owned by 00:19:35.120 --> 00:19:36.870 align:start position:0% means that for names that owned by immutable<00:19:35.640> contracts<00:19:36.080> or<00:19:36.159> for<00:19:36.280> users<00:19:36.679> that 00:19:36.870 --> 00:19:36.880 align:start position:0% immutable contracts or for users that 00:19:36.880 --> 00:19:39.549 align:start position:0% immutable contracts or for users that can't<00:19:37.480> or<00:19:37.679> won't<00:19:38.159> upgrade<00:19:38.840> functionality<00:19:39.480> of 00:19:39.549 --> 00:19:39.559 align:start position:0% can't or won't upgrade functionality of 00:19:39.559 --> 00:19:43.070 align:start position:0% can't or won't upgrade functionality of their<00:19:39.760> name<00:19:40.240> is<00:19:40.400> safeguarded 00:19:43.070 --> 00:19:43.080 align:start position:0% 00:19:43.080 --> 00:19:45.270 align:start position:0% forever<00:19:44.080> it's<00:19:44.240> been<00:19:44.400> 7<00:19:44.799> years<00:19:45.000> since<00:19:45.159> the 00:19:45.270 --> 00:19:45.280 align:start position:0% forever it's been 7 years since the 00:19:45.280 --> 00:19:49.470 align:start position:0% forever it's been 7 years since the Inception<00:19:45.640> of<00:19:45.960> ens<00:19:46.960> Google<00:19:47.640> VMO<00:19:48.440> PayPal 00:19:49.470 --> 00:19:49.480 align:start position:0% Inception of ens Google VMO PayPal 00:19:49.480 --> 00:19:51.750 align:start position:0% Inception of ens Google VMO PayPal GoDaddy<00:19:50.480> wow<00:19:50.640> we<00:19:50.760> couldn't<00:19:50.919> have<00:19:51.120> imagined 00:19:51.750 --> 00:19:51.760 align:start position:0% GoDaddy wow we couldn't have imagined 00:19:51.760 --> 00:19:54.230 align:start position:0% GoDaddy wow we couldn't have imagined seven<00:19:52.039> years<00:19:52.240> ago<00:19:52.480> that<00:19:52.679> we<00:19:52.760> would<00:19:52.919> get<00:19:53.039> so 00:19:54.230 --> 00:19:54.240 align:start position:0% seven years ago that we would get so 00:19:54.240 --> 00:19:57.510 align:start position:0% seven years ago that we would get so far<00:19:55.240> and<00:19:55.400> ens<00:19:55.840> is<00:19:56.120> ethereum<00:19:56.640> aligned<00:19:57.240> and 00:19:57.510 --> 00:19:57.520 align:start position:0% far and ens is ethereum aligned and 00:19:57.520 --> 00:19:59.390 align:start position:0% far and ens is ethereum aligned and always<00:19:57.880> will<00:19:58.120> be<00:19:58.360> that's<00:19:58.480> why<00:19:58.840> we<00:19:59.159> always 00:19:59.390 --> 00:19:59.400 align:start position:0% always will be that's why we always 00:19:59.400 --> 00:20:01.110 align:start position:0% always will be that's why we always enjoy<00:19:59.760> coming<00:20:00.000> and<00:20:00.120> giving<00:20:00.360> the<00:20:00.440> state<00:20:00.679> of<00:20:00.799> ens 00:20:01.110 --> 00:20:01.120 align:start position:0% enjoy coming and giving the state of ens 00:20:01.120 --> 00:20:04.230 align:start position:0% enjoy coming and giving the state of ens to<00:20:01.240> Devcon<00:20:01.799> every<00:20:02.080> single<00:20:02.440> year<00:20:03.039> since<00:20:03.320> Devcon 00:20:04.230 --> 00:20:04.240 align:start position:0% to Devcon every single year since Devcon 00:20:04.240 --> 00:20:06.830 align:start position:0% to Devcon every single year since Devcon one<00:20:05.120> or 00:20:06.830 --> 00:20:06.840 align:start position:0% one or 00:20:06.840 --> 00:20:10.070 align:start position:0% one or two<00:20:07.840> and<00:20:07.960> L2<00:20:08.360> reverse<00:20:08.679> registrars<00:20:09.280> on<00:20:09.400> testnet 00:20:10.070 --> 00:20:10.080 align:start position:0% two and L2 reverse registrars on testnet 00:20:10.080 --> 00:20:12.029 align:start position:0% two and L2 reverse registrars on testnet today<00:20:11.080> it's<00:20:11.240> something<00:20:11.480> we've<00:20:11.640> been<00:20:11.760> working 00:20:12.029 --> 00:20:12.039 align:start position:0% today it's something we've been working 00:20:12.039 --> 00:20:13.710 align:start position:0% today it's something we've been working on<00:20:12.159> for<00:20:12.280> a<00:20:12.400> little<00:20:12.679> little<00:20:12.880> while<00:20:13.120> now<00:20:13.480> and 00:20:13.710 --> 00:20:13.720 align:start position:0% on for a little little while now and 00:20:13.720 --> 00:20:15.789 align:start position:0% on for a little little while now and we're<00:20:13.960> really<00:20:14.240> trying<00:20:14.440> to<00:20:14.679> bring<00:20:14.919> the<00:20:15.039> interop 00:20:15.789 --> 00:20:15.799 align:start position:0% we're really trying to bring the interop 00:20:15.799 --> 00:20:18.750 align:start position:0% we're really trying to bring the interop into<00:20:16.320> ethereum<00:20:17.080> and<00:20:17.200> that's<00:20:17.440> really<00:20:17.600> been<00:20:17.919> the 00:20:18.750 --> 00:20:18.760 align:start position:0% into ethereum and that's really been the 00:20:18.760 --> 00:20:21.870 align:start position:0% into ethereum and that's really been the the<00:20:19.760> um<00:20:19.919> the<00:20:20.120> theme<00:20:20.480> for<00:20:20.679> this 00:20:21.870 --> 00:20:21.880 align:start position:0% the um the theme for this 00:20:21.880 --> 00:20:24.470 align:start position:0% the um the theme for this Devcon<00:20:22.880> and<00:20:23.039> ens<00:20:23.360> is<00:20:23.480> expanding<00:20:23.799> to<00:20:24.240> name 00:20:24.470 --> 00:20:24.480 align:start position:0% Devcon and ens is expanding to name 00:20:24.480 --> 00:20:26.950 align:start position:0% Devcon and ens is expanding to name chain<00:20:25.120> but<00:20:25.440> remaining<00:20:25.679> on<00:20:25.840> L1<00:20:26.520> whilst 00:20:26.950 --> 00:20:26.960 align:start position:0% chain but remaining on L1 whilst 00:20:26.960 --> 00:20:29.430 align:start position:0% chain but remaining on L1 whilst remaining<00:20:27.240> L2<00:20:27.679> agnostic<00:20:28.520> and<00:20:28.640> and<00:20:28.760> ens<00:20:29.080> V2 00:20:29.430 --> 00:20:29.440 align:start position:0% remaining L2 agnostic and and ens V2 00:20:29.440 --> 00:20:31.789 align:start position:0% remaining L2 agnostic and and ens V2 will<00:20:29.600> improve<00:20:29.919> the<00:20:30.039> ux<00:20:30.400> of<00:20:30.559> ens<00:20:31.360> across<00:20:31.679> the 00:20:31.789 --> 00:20:31.799 align:start position:0% will improve the ux of ens across the 00:20:31.799 --> 00:20:34.590 align:start position:0% will improve the ux of ens across the board<00:20:32.480> for<00:20:32.679> years<00:20:32.880> to 00:20:34.590 --> 00:20:34.600 align:start position:0% board for years to 00:20:34.600 --> 00:20:37.310 align:start position:0% board for years to come<00:20:35.600> and<00:20:35.799> lastly<00:20:36.480> this<00:20:36.720> talk<00:20:36.880> was<00:20:37.039> too<00:20:37.200> long 00:20:37.310 --> 00:20:37.320 align:start position:0% come and lastly this talk was too long 00:20:37.320 --> 00:20:39.750 align:start position:0% come and lastly this talk was too long to<00:20:37.480> mention<00:20:37.919> some<00:20:38.039> of<00:20:38.200> the<00:20:38.400> amazing<00:20:39.080> ens<00:20:39.480> Dow 00:20:39.750 --> 00:20:39.760 align:start position:0% to mention some of the amazing ens Dow 00:20:39.760 --> 00:20:42.230 align:start position:0% to mention some of the amazing ens Dow service<00:20:40.120> providers<00:20:40.559> this<00:20:40.799> year<00:20:41.799> we're<00:20:42.000> not 00:20:42.230 --> 00:20:42.240 align:start position:0% service providers this year we're not 00:20:42.240 --> 00:20:44.029 align:start position:0% service providers this year we're not the<00:20:42.360> only<00:20:42.640> ones<00:20:42.880> building<00:20:43.240> ens<00:20:43.760> and<00:20:43.840> it<00:20:43.919> would 00:20:44.029 --> 00:20:44.039 align:start position:0% the only ones building ens and it would 00:20:44.039 --> 00:20:45.990 align:start position:0% the only ones building ens and it would be<00:20:44.159> impossible<00:20:44.720> to<00:20:44.919> expand<00:20:45.360> to<00:20:45.559> a<00:20:45.679> billion 00:20:45.990 --> 00:20:46.000 align:start position:0% be impossible to expand to a billion 00:20:46.000 --> 00:20:48.789 align:start position:0% be impossible to expand to a billion users<00:20:46.480> without<00:20:46.799> help<00:20:47.480> to<00:20:47.640> name<00:20:47.799> a<00:20:47.919> few<00:20:48.280> first 00:20:48.789 --> 00:20:48.799 align:start position:0% users without help to name a few first 00:20:48.799 --> 00:20:50.430 align:start position:0% users without help to name a few first the<00:20:48.919> ethereum<00:20:49.320> fell<00:20:49.640> protocol<00:20:50.000> is<00:20:50.120> bringing 00:20:50.430 --> 00:20:50.440 align:start position:0% the ethereum fell protocol is bringing 00:20:50.440 --> 00:20:53.830 align:start position:0% the ethereum fell protocol is bringing the<00:20:50.600> social<00:20:51.039> profiles<00:20:51.440> of<00:20:51.640> ens<00:20:52.240> to<00:20:52.400> the<00:20:52.840> masses 00:20:53.830 --> 00:20:53.840 align:start position:0% the social profiles of ens to the masses 00:20:53.840 --> 00:20:55.990 align:start position:0% the social profiles of ens to the masses Nam<00:20:54.200> stone<00:20:54.840> is<00:20:55.000> pairing<00:20:55.480> many<00:20:55.720> of<00:20:55.880> the 00:20:55.990 --> 00:20:56.000 align:start position:0% Nam stone is pairing many of the 00:20:56.000 --> 00:20:58.710 align:start position:0% Nam stone is pairing many of the subdomain<00:20:56.640> Integrations<00:20:57.640> and<00:20:57.880> unrug<00:20:58.600> for 00:20:58.710 --> 00:20:58.720 align:start position:0% subdomain Integrations and unrug for 00:20:58.720 --> 00:21:00.270 align:start position:0% subdomain Integrations and unrug for building<00:20:59.039> the<00:20:59.240> generalized<00:20:59.799> gateways<00:21:00.159> that 00:21:00.270 --> 00:21:00.280 align:start position:0% building the generalized gateways that 00:21:00.280 --> 00:21:02.230 align:start position:0% building the generalized gateways that are<00:21:00.480> powering<00:21:00.840> ccip 00:21:02.230 --> 00:21:02.240 align:start position:0% are powering ccip 00:21:02.240 --> 00:21:05.870 align:start position:0% are powering ccip read<00:21:03.240> and<00:21:03.400> of<00:21:03.600> course<00:21:04.240> my<00:21:04.400> ens<00:21:04.760> Labs<00:21:05.080> team<00:21:05.679> for 00:21:05.870 --> 00:21:05.880 align:start position:0% read and of course my ens Labs team for 00:21:05.880 --> 00:21:07.270 align:start position:0% read and of course my ens Labs team for building<00:21:06.280> everything<00:21:06.799> that<00:21:06.919> we've<00:21:07.039> seen 00:21:07.270 --> 00:21:07.280 align:start position:0% building everything that we've seen 00:21:07.280 --> 00:21:10.230 align:start position:0% building everything that we've seen today<00:21:08.039> and<00:21:08.240> supporting<00:21:08.720> us<00:21:09.480> today<00:21:09.919> and<00:21:10.039> for 00:21:10.230 --> 00:21:10.240 align:start position:0% today and supporting us today and for 00:21:10.240 --> 00:21:13.070 align:start position:0% today and supporting us today and for years<00:21:10.400> to 00:21:13.070 --> 00:21:13.080 align:start position:0% 00:21:13.080 --> 00:21:15.350 align:start position:0% come<00:21:14.080> and<00:21:14.240> finally<00:21:14.600> the<00:21:14.720> adventure<00:21:15.039> is<00:21:15.159> not 00:21:15.350 --> 00:21:15.360 align:start position:0% come and finally the adventure is not 00:21:15.360 --> 00:21:17.029 align:start position:0% come and finally the adventure is not over<00:21:15.880> if<00:21:16.000> you're<00:21:16.159> looking<00:21:16.360> for<00:21:16.480> a<00:21:16.640> position<00:21:16.880> at 00:21:17.029 --> 00:21:17.039 align:start position:0% over if you're looking for a position at 00:21:17.039 --> 00:21:19.110 align:start position:0% over if you're looking for a position at ens<00:21:17.480> we're<00:21:17.679> always<00:21:17.960> looking<00:21:18.279> for<00:21:18.520> good<00:21:18.720> people 00:21:19.110 --> 00:21:19.120 align:start position:0% ens we're always looking for good people 00:21:19.120 --> 00:21:20.630 align:start position:0% ens we're always looking for good people so<00:21:19.240> if<00:21:19.320> you'd<00:21:19.480> like<00:21:19.600> to<00:21:19.679> work<00:21:19.840> for<00:21:19.960> ens<00:21:20.320> Labs 00:21:20.630 --> 00:21:20.640 align:start position:0% so if you'd like to work for ens Labs 00:21:20.640 --> 00:21:23.350 align:start position:0% so if you'd like to work for ens Labs please<00:21:20.880> check<00:21:21.400> ens<00:21:21.840> labs.<00:21:22.240> org<00:21:22.640> for<00:21:22.799> job 00:21:23.350 --> 00:21:23.360 align:start position:0% please check ens labs. org for job 00:21:23.360 --> 00:21:25.789 align:start position:0% please check ens labs. org for job postings<00:21:24.360> thank<00:21:24.559> you<00:21:24.720> and<00:21:24.919> enjoy<00:21:25.320> your<00:21:25.559> last 00:21:25.789 --> 00:21:25.799 align:start position:0% postings thank you and enjoy your last 00:21:25.799 --> 00:21:27.140 align:start position:0% postings thank you and enjoy your last day<00:21:25.960> at<00:21:26.039> Devcon 00:21:27.140 --> 00:21:27.150 align:start position:0% day at Devcon 00:21:27.150 --> 00:21:33.230 align:start position:0% day at Devcon [Applause] 00:21:33.230 --> 00:21:33.240 align:start position:0% 00:21:33.240 --> 00:21:35.190 align:start position:0% all<00:21:33.480> right<00:21:33.840> thank<00:21:34.039> you<00:21:34.200> so<00:21:34.440> much<00:21:34.720> Jeff<00:21:35.000> for 00:21:35.190 --> 00:21:35.200 align:start position:0% all right thank you so much Jeff for 00:21:35.200 --> 00:21:37.710 align:start position:0% all right thank you so much Jeff for that<00:21:36.039> I<00:21:36.159> think<00:21:36.320> that<00:21:36.480> was<00:21:36.760> fantastic<00:21:37.440> so<00:21:37.640> as 00:21:37.710 --> 00:21:37.720 align:start position:0% that I think that was fantastic so as 00:21:37.720 --> 00:21:39.470 align:start position:0% that I think that was fantastic so as you<00:21:37.840> can<00:21:37.960> see<00:21:38.279> here<00:21:38.679> if<00:21:38.760> you've<00:21:38.960> already<00:21:39.200> asked 00:21:39.470 --> 00:21:39.480 align:start position:0% you can see here if you've already asked 00:21:39.480 --> 00:21:41.710 align:start position:0% you can see here if you've already asked your<00:21:39.679> questions<00:21:40.120> that<00:21:40.240> is<00:21:40.520> great<00:21:41.360> uh<00:21:41.480> what<00:21:41.600> you 00:21:41.710 --> 00:21:41.720 align:start position:0% your questions that is great uh what you 00:21:41.720 --> 00:21:43.669 align:start position:0% your questions that is great uh what you can<00:21:41.919> do<00:21:42.120> is<00:21:42.240> you<00:21:42.360> can<00:21:42.480> also<00:21:42.720> upvote<00:21:43.159> a<00:21:43.360> question 00:21:43.669 --> 00:21:43.679 align:start position:0% can do is you can also upvote a question 00:21:43.679 --> 00:21:45.149 align:start position:0% can do is you can also upvote a question so<00:21:43.840> if<00:21:43.960> you<00:21:44.120> really<00:21:44.360> really<00:21:44.640> want<00:21:44.760> to<00:21:44.919> have<00:21:45.000> it 00:21:45.149 --> 00:21:45.159 align:start position:0% so if you really really want to have it 00:21:45.159 --> 00:21:46.990 align:start position:0% so if you really really want to have it answered<00:21:45.799> it<00:21:45.960> can<00:21:46.120> move<00:21:46.320> up<00:21:46.480> to<00:21:46.640> the<00:21:46.760> top<00:21:46.880> of 00:21:46.990 --> 00:21:47.000 align:start position:0% answered it can move up to the top of 00:21:47.000 --> 00:21:48.070 align:start position:0% answered it can move up to the top of the<00:21:47.080> question<00:21:47.320> so<00:21:47.440> we're<00:21:47.559> going<00:21:47.640> to<00:21:47.760> start<00:21:47.960> off 00:21:48.070 --> 00:21:48.080 align:start position:0% the question so we're going to start off 00:21:48.080 --> 00:21:50.590 align:start position:0% the question so we're going to start off with<00:21:48.240> the<00:21:48.400> first<00:21:48.640> one<00:21:49.360> what<00:21:49.520> about<00:21:49.960> privacy 00:21:50.590 --> 00:21:50.600 align:start position:0% with the first one what about privacy 00:21:50.600 --> 00:21:53.110 align:start position:0% with the first one what about privacy using<00:21:50.919> ens<00:21:51.440> as<00:21:51.600> a<00:21:51.720> major<00:21:52.120> privacy<00:21:52.559> leag<00:21:52.880> and 00:21:53.110 --> 00:21:53.120 align:start position:0% using ens as a major privacy leag and 00:21:53.120 --> 00:21:56.590 align:start position:0% using ens as a major privacy leag and conducts<00:21:53.640> a<00:21:54.200> user<00:21:55.200> sure<00:21:55.600> I<00:21:55.679> mean<00:21:56.240> this<00:21:56.320> is<00:21:56.440> a 00:21:56.590 --> 00:21:56.600 align:start position:0% conducts a user sure I mean this is a 00:21:56.600 --> 00:21:59.390 align:start position:0% conducts a user sure I mean this is a question<00:21:56.840> we<00:21:56.960> get<00:21:57.159> a<00:21:57.279> lot<00:21:57.760> for<00:21:57.960> us<00:21:58.080> at<00:21:58.200> en 00:21:59.390 --> 00:21:59.400 align:start position:0% question we get a lot for us at en 00:21:59.400 --> 00:22:02.390 align:start position:0% question we get a lot for us at en and<00:22:00.000> for<00:22:00.200> us<00:22:00.480> ens<00:22:01.000> is<00:22:01.120> a<00:22:01.240> usability<00:22:01.880> protocol 00:22:02.390 --> 00:22:02.400 align:start position:0% and for us ens is a usability protocol 00:22:02.400 --> 00:22:04.710 align:start position:0% and for us ens is a usability protocol on<00:22:02.600> top<00:22:02.720> of<00:22:02.880> ethereum<00:22:03.320> and<00:22:03.440> l2s<00:22:04.159> and<00:22:04.320> ethereum 00:22:04.710 --> 00:22:04.720 align:start position:0% on top of ethereum and l2s and ethereum 00:22:04.720 --> 00:22:07.310 align:start position:0% on top of ethereum and l2s and ethereum and<00:22:04.840> l2s<00:22:05.600> have<00:22:05.840> this<00:22:06.000> issue<00:22:06.760> regardless<00:22:07.159> of 00:22:07.310 --> 00:22:07.320 align:start position:0% and l2s have this issue regardless of 00:22:07.320 --> 00:22:09.950 align:start position:0% and l2s have this issue regardless of ens<00:22:08.240> so<00:22:08.480> obviously<00:22:08.799> you<00:22:08.880> need<00:22:09.039> to<00:22:09.600> practice 00:22:09.950 --> 00:22:09.960 align:start position:0% ens so obviously you need to practice 00:22:09.960 --> 00:22:12.390 align:start position:0% ens so obviously you need to practice good<00:22:10.320> obsc<00:22:11.320> and<00:22:11.559> make<00:22:11.720> sure<00:22:11.840> your<00:22:12.000> address<00:22:12.240> is 00:22:12.390 --> 00:22:12.400 align:start position:0% good obsc and make sure your address is 00:22:12.400 --> 00:22:13.830 align:start position:0% good obsc and make sure your address is not<00:22:12.559> linked<00:22:12.919> and<00:22:13.080> do<00:22:13.240> the<00:22:13.320> things<00:22:13.480> that<00:22:13.600> you<00:22:13.720> do 00:22:13.830 --> 00:22:13.840 align:start position:0% not linked and do the things that you do 00:22:13.840 --> 00:22:15.190 align:start position:0% not linked and do the things that you do to<00:22:14.000> protect<00:22:14.200> yourself<00:22:14.480> for<00:22:14.600> the<00:22:14.679> addresses 00:22:15.190 --> 00:22:15.200 align:start position:0% to protect yourself for the addresses 00:22:15.200 --> 00:22:17.230 align:start position:0% to protect yourself for the addresses having<00:22:15.400> a<00:22:15.559> name<00:22:15.760> on<00:22:15.919> it<00:22:16.080> doesn't<00:22:16.600> additionally 00:22:17.230 --> 00:22:17.240 align:start position:0% having a name on it doesn't additionally 00:22:17.240 --> 00:22:20.149 align:start position:0% having a name on it doesn't additionally create<00:22:17.760> less<00:22:18.080> privacy<00:22:19.039> so<00:22:19.679> you<00:22:19.840> obviously 00:22:20.149 --> 00:22:20.159 align:start position:0% create less privacy so you obviously 00:22:20.159 --> 00:22:21.750 align:start position:0% create less privacy so you obviously need<00:22:20.320> to<00:22:20.440> create<00:22:20.679> that<00:22:20.799> good<00:22:20.960> OBC<00:22:21.400> no<00:22:21.520> matter 00:22:21.750 --> 00:22:21.760 align:start position:0% need to create that good OBC no matter 00:22:21.760 --> 00:22:24.269 align:start position:0% need to create that good OBC no matter whether<00:22:21.880> you're<00:22:22.000> using<00:22:22.240> ens<00:22:22.720> or 00:22:24.269 --> 00:22:24.279 align:start position:0% whether you're using ens or 00:22:24.279 --> 00:22:27.630 align:start position:0% whether you're using ens or not<00:22:25.279> all<00:22:25.600> right<00:22:26.320> and<00:22:26.440> then<00:22:26.640> we've<00:22:26.880> got<00:22:27.279> Google 00:22:27.630 --> 00:22:27.640 align:start position:0% not all right and then we've got Google 00:22:27.640 --> 00:22:30.750 align:start position:0% not all right and then we've got Google integration<00:22:28.520> ports.<00:22:29.120> e<00:22:29.440> domains<00:22:30.080> but<00:22:30.320> not<00:22:30.559> the 00:22:30.750 --> 00:22:30.760 align:start position:0% integration ports. e domains but not the 00:22:30.760 --> 00:22:34.110 align:start position:0% integration ports. e domains but not the corresponding<00:22:31.760> subdomains<00:22:32.760> why<00:22:33.000> is<00:22:33.240> that<00:22:34.039> I 00:22:34.110 --> 00:22:34.120 align:start position:0% corresponding subdomains why is that I 00:22:34.120 --> 00:22:35.590 align:start position:0% corresponding subdomains why is that I mean<00:22:34.279> if<00:22:34.400> anyone's<00:22:34.720> from<00:22:34.840> Google<00:22:35.120> here<00:22:35.320> can<00:22:35.440> do 00:22:35.590 --> 00:22:35.600 align:start position:0% mean if anyone's from Google here can do 00:22:35.600 --> 00:22:37.549 align:start position:0% mean if anyone's from Google here can do this<00:22:35.799> we'd<00:22:36.000> be<00:22:36.480> it'd<00:22:36.679> be<00:22:36.840> fantastic<00:22:37.240> if<00:22:37.400> they 00:22:37.549 --> 00:22:37.559 align:start position:0% this we'd be it'd be fantastic if they 00:22:37.559 --> 00:22:39.870 align:start position:0% this we'd be it'd be fantastic if they could<00:22:38.039> um<00:22:38.200> obviously<00:22:38.799> eth<00:22:39.080> is<00:22:39.200> our<00:22:39.360> Flagship 00:22:39.870 --> 00:22:39.880 align:start position:0% could um obviously eth is our Flagship 00:22:39.880 --> 00:22:42.669 align:start position:0% could um obviously eth is our Flagship product<00:22:40.720> Google<00:22:41.520> really<00:22:41.799> respects<00:22:42.240> that<00:22:42.520> and 00:22:42.669 --> 00:22:42.679 align:start position:0% product Google really respects that and 00:22:42.679 --> 00:22:44.669 align:start position:0% product Google really respects that and wants<00:22:42.960> to<00:22:43.480> to<00:22:43.640> do<00:22:43.799> some<00:22:44.000> Integrations<00:22:44.559> and 00:22:44.669 --> 00:22:44.679 align:start position:0% wants to to do some Integrations and 00:22:44.679 --> 00:22:47.990 align:start position:0% wants to to do some Integrations and starting<00:22:44.960> with.<00:22:45.320> e<00:22:46.120> um<00:22:46.840> but<00:22:47.480> hopefully<00:22:47.799> in<00:22:47.880> the 00:22:47.990 --> 00:22:48.000 align:start position:0% starting with. e um but hopefully in the 00:22:48.000 --> 00:22:49.149 align:start position:0% starting with. e um but hopefully in the future<00:22:48.279> we<00:22:48.400> can<00:22:48.520> really<00:22:48.679> push<00:22:48.880> them<00:22:48.960> to<00:22:49.080> do 00:22:49.149 --> 00:22:49.159 align:start position:0% future we can really push them to do 00:22:49.159 --> 00:22:50.990 align:start position:0% future we can really push them to do self-domains<00:22:49.600> as<00:22:49.799> well<00:22:49.960> and<00:22:50.120> if<00:22:50.279> anyone<00:22:50.840> has 00:22:50.990 --> 00:22:51.000 align:start position:0% self-domains as well and if anyone has 00:22:51.000 --> 00:22:53.190 align:start position:0% self-domains as well and if anyone has connections<00:22:51.360> at<00:22:51.559> Google<00:22:52.360> please<00:22:52.720> talk<00:22:52.919> to<00:22:53.039> us 00:22:53.190 --> 00:22:53.200 align:start position:0% connections at Google please talk to us 00:22:53.200 --> 00:22:55.630 align:start position:0% connections at Google please talk to us and<00:22:53.400> we'll<00:22:53.679> we'll<00:22:53.840> try<00:22:53.960> and<00:22:54.080> get<00:22:54.200> that 00:22:55.630 --> 00:22:55.640 align:start position:0% and we'll we'll try and get that 00:22:55.640 --> 00:22:57.909 align:start position:0% and we'll we'll try and get that in<00:22:56.640> okay<00:22:56.880> remember<00:22:57.159> you<00:22:57.240> can<00:22:57.360> still<00:22:57.600> add<00:22:57.799> some 00:22:57.909 --> 00:22:57.919 align:start position:0% in okay remember you can still add some 00:22:57.919 --> 00:22:59.470 align:start position:0% in okay remember you can still add some more<00:22:58.080> questions<00:22:58.640> if<00:22:58.720> you<00:22:58.799> feel<00:22:59.039> like<00:22:59.200> none<00:22:59.360> of 00:22:59.470 --> 00:22:59.480 align:start position:0% more questions if you feel like none of 00:22:59.480 --> 00:23:01.750 align:start position:0% more questions if you feel like none of the<00:22:59.600> ones<00:22:59.799> that<00:22:59.919> you<00:23:00.080> have<00:23:00.279> are<00:23:00.400> on<00:23:00.640> here<00:23:01.440> we've 00:23:01.750 --> 00:23:01.760 align:start position:0% the ones that you have are on here we've 00:23:01.760 --> 00:23:04.789 align:start position:0% the ones that you have are on here we've got<00:23:02.480> can<00:23:03.000> builders<00:23:03.480> use<00:23:03.760> name<00:23:03.960> chain<00:23:04.360> for 00:23:04.789 --> 00:23:04.799 align:start position:0% got can builders use name chain for 00:23:04.799 --> 00:23:07.950 align:start position:0% got can builders use name chain for other<00:23:05.279> stuff<00:23:06.279> yes<00:23:06.520> so<00:23:06.720> as<00:23:06.840> I<00:23:06.960> said<00:23:07.320> name<00:23:07.600> chain 00:23:07.950 --> 00:23:07.960 align:start position:0% other stuff yes so as I said name chain 00:23:07.960 --> 00:23:10.870 align:start position:0% other stuff yes so as I said name chain will<00:23:08.159> be<00:23:08.400> on<00:23:08.559> a<00:23:08.679> ZK<00:23:09.120> evm<00:23:09.559> most<00:23:09.799> likely<00:23:10.440> and<00:23:10.760> that 00:23:10.870 --> 00:23:10.880 align:start position:0% will be on a ZK evm most likely and that 00:23:10.880 --> 00:23:13.190 align:start position:0% will be on a ZK evm most likely and that means<00:23:11.200> it's<00:23:11.400> evm<00:23:11.799> compatible<00:23:12.480> so<00:23:12.880> it's<00:23:13.080> going 00:23:13.190 --> 00:23:13.200 align:start position:0% means it's evm compatible so it's going 00:23:13.200 --> 00:23:15.230 align:start position:0% means it's evm compatible so it's going to<00:23:13.400> be<00:23:14.120> it's<00:23:14.240> going<00:23:14.360> to<00:23:14.480> be<00:23:14.559> a<00:23:14.679> public<00:23:14.960> chain 00:23:15.230 --> 00:23:15.240 align:start position:0% to be it's going to be a public chain 00:23:15.240 --> 00:23:16.870 align:start position:0% to be it's going to be a public chain that<00:23:15.400> anyone<00:23:15.799> can<00:23:16.000> use<00:23:16.400> we're<00:23:16.559> not<00:23:16.679> going<00:23:16.760> to 00:23:16.870 --> 00:23:16.880 align:start position:0% that anyone can use we're not going to 00:23:16.880 --> 00:23:19.110 align:start position:0% that anyone can use we're not going to be<00:23:17.400> you<00:23:17.520> know<00:23:17.760> permissioning<00:23:18.400> the<00:23:18.559> chain<00:23:18.960> so 00:23:19.110 --> 00:23:19.120 align:start position:0% be you know permissioning the chain so 00:23:19.120 --> 00:23:37.110 align:start position:0% be you know permissioning the chain so you<00:23:19.240> can<00:23:19.720> deploy<00:23:20.039> your<00:23:20.159> own<00:23:20.360> resolvers 00:23:37.110 --> 00:23:37.120 align:start position:0% 00:23:37.120 --> 00:23:39.350 align:start position:0% all<00:23:37.360> right<00:23:37.679> then<00:23:37.840> at<00:23:37.960> the<00:23:38.120> top<00:23:38.360> here<00:23:38.559> we've<00:23:38.799> got 00:23:39.350 --> 00:23:39.360 align:start position:0% all right then at the top here we've got 00:23:39.360 --> 00:23:41.310 align:start position:0% all right then at the top here we've got what<00:23:39.520> are<00:23:39.840> some<00:23:40.000> of<00:23:40.159> the<00:23:40.360> problems<00:23:40.840> that<00:23:41.000> stand 00:23:41.310 --> 00:23:41.320 align:start position:0% what are some of the problems that stand 00:23:41.320 --> 00:23:43.310 align:start position:0% what are some of the problems that stand in<00:23:41.480> our<00:23:41.679> way<00:23:41.919> to<00:23:42.200> increase<00:23:42.720> mainstream 00:23:43.310 --> 00:23:43.320 align:start position:0% in our way to increase mainstream 00:23:43.320 --> 00:23:46.510 align:start position:0% in our way to increase mainstream adoption<00:23:44.080> of<00:23:44.559> iness<00:23:45.559> I<00:23:45.640> mean<00:23:45.799> I<00:23:45.880> think<00:23:46.120> this 00:23:46.510 --> 00:23:46.520 align:start position:0% adoption of iness I mean I think this 00:23:46.520 --> 00:23:49.669 align:start position:0% adoption of iness I mean I think this applies<00:23:47.159> to<00:23:47.600> all<00:23:47.760> of<00:23:47.919> ethereum<00:23:48.640> and<00:23:49.120> all<00:23:49.520> all 00:23:49.669 --> 00:23:49.679 align:start position:0% applies to all of ethereum and all all 00:23:49.679 --> 00:23:53.549 align:start position:0% applies to all of ethereum and all all of<00:23:50.120> blockchain<00:23:50.640> itself<00:23:51.640> it's<00:23:51.840> really<00:23:52.559> about 00:23:53.549 --> 00:23:53.559 align:start position:0% of blockchain itself it's really about 00:23:53.559 --> 00:23:54.990 align:start position:0% of blockchain itself it's really about um 00:23:54.990 --> 00:23:55.000 align:start position:0% um 00:23:55.000 --> 00:23:57.470 align:start position:0% um getting<00:23:56.000> improving<00:23:56.520> our<00:23:56.720> wallet<00:23:57.080> user 00:23:57.470 --> 00:23:57.480 align:start position:0% getting improving our wallet user 00:23:57.480 --> 00:24:01.070 align:start position:0% getting improving our wallet user experience<00:23:58.480> having<00:23:59.039> names<00:24:00.000> and<00:24:00.640> all<00:24:00.799> of<00:24:00.919> these 00:24:01.070 --> 00:24:01.080 align:start position:0% experience having names and all of these 00:24:01.080 --> 00:24:02.830 align:start position:0% experience having names and all of these things<00:24:01.360> to<00:24:01.600> replace<00:24:01.960> addresses<00:24:02.440> and<00:24:02.559> once<00:24:02.720> you 00:24:02.830 --> 00:24:02.840 align:start position:0% things to replace addresses and once you 00:24:02.840 --> 00:24:06.029 align:start position:0% things to replace addresses and once you do<00:24:03.039> that<00:24:03.159> you<00:24:03.279> can<00:24:03.440> get<00:24:03.679> more<00:24:04.559> blockchain<00:24:05.360> and 00:24:06.029 --> 00:24:06.039 align:start position:0% do that you can get more blockchain and 00:24:06.039 --> 00:24:08.029 align:start position:0% do that you can get more blockchain and ethereum<00:24:06.600> support<00:24:07.080> across<00:24:07.360> the<00:24:07.480> board<00:24:07.919> you 00:24:08.029 --> 00:24:08.039 align:start position:0% ethereum support across the board you 00:24:08.039 --> 00:24:11.110 align:start position:0% ethereum support across the board you know<00:24:08.159> in<00:24:08.240> your<00:24:08.480> cafes<00:24:09.440> um<00:24:10.120> in<00:24:10.320> your<00:24:10.840> you<00:24:10.919> know 00:24:11.110 --> 00:24:11.120 align:start position:0% know in your cafes um in your you know 00:24:11.120 --> 00:24:12.830 align:start position:0% know in your cafes um in your you know paying<00:24:11.360> for<00:24:11.559> things<00:24:11.840> dayto<00:24:12.200> day<00:24:12.559> and<00:24:12.679> then 00:24:12.830 --> 00:24:12.840 align:start position:0% paying for things dayto day and then 00:24:12.840 --> 00:24:15.990 align:start position:0% paying for things dayto day and then it'll<00:24:13.039> be<00:24:13.200> very<00:24:13.840> easy<00:24:14.200> to<00:24:14.520> kind<00:24:14.640> of<00:24:15.120> improve 00:24:15.990 --> 00:24:16.000 align:start position:0% it'll be very easy to kind of improve 00:24:16.000 --> 00:24:17.630 align:start position:0% it'll be very easy to kind of improve the<00:24:16.120> mainstream<00:24:16.559> ad<00:24:16.679> doct<00:24:16.880> of<00:24:16.960> ens<00:24:17.279> I<00:24:17.400> believe 00:24:17.630 --> 00:24:17.640 align:start position:0% the mainstream ad doct of ens I believe 00:24:17.640 --> 00:24:20.830 align:start position:0% the mainstream ad doct of ens I believe already<00:24:18.600> ens<00:24:19.120> is<00:24:19.679> quite<00:24:19.960> widely<00:24:20.279> supported 00:24:20.830 --> 00:24:20.840 align:start position:0% already ens is quite widely supported 00:24:20.840 --> 00:24:23.269 align:start position:0% already ens is quite widely supported across<00:24:21.440> blockchain<00:24:21.960> so<00:24:22.080> it's<00:24:22.200> really<00:24:22.520> about 00:24:23.269 --> 00:24:23.279 align:start position:0% across blockchain so it's really about 00:24:23.279 --> 00:24:25.470 align:start position:0% across blockchain so it's really about expanding<00:24:23.880> the<00:24:24.039> entire<00:24:24.400> ecosystem<00:24:24.919> itself<00:24:25.279> so 00:24:25.470 --> 00:24:25.480 align:start position:0% expanding the entire ecosystem itself so 00:24:25.480 --> 00:24:30.950 align:start position:0% expanding the entire ecosystem itself so ens<00:24:25.960> can<00:24:26.440> serve<00:24:26.799> a<00:24:26.919> larger<00:24:27.279> ecosystem 00:24:30.950 --> 00:24:30.960 align:start position:0% 00:24:30.960 --> 00:24:33.269 align:start position:0% all<00:24:31.159> right<00:24:31.520> can<00:24:31.880> name<00:24:32.159> chain<00:24:32.480> be<00:24:32.720> key<00:24:33.000> store 00:24:33.269 --> 00:24:33.279 align:start position:0% all right can name chain be key store 00:24:33.279 --> 00:24:36.149 align:start position:0% all right can name chain be key store rollup<00:24:33.960> as<00:24:34.200> well<00:24:35.200> it<00:24:35.360> is<00:24:35.520> something<00:24:35.760> we<00:24:35.919> talked 00:24:36.149 --> 00:24:36.159 align:start position:0% rollup as well it is something we talked 00:24:36.159 --> 00:24:38.830 align:start position:0% rollup as well it is something we talked about<00:24:36.720> and<00:24:37.200> I<00:24:37.399> I<00:24:37.480> don't<00:24:37.720> think<00:24:37.919> it's<00:24:38.480> something 00:24:38.830 --> 00:24:38.840 align:start position:0% about and I I don't think it's something 00:24:38.840 --> 00:24:40.669 align:start position:0% about and I I don't think it's something we<00:24:38.960> have<00:24:39.120> we<00:24:39.200> can<00:24:39.320> Ru<00:24:39.559> out<00:24:39.840> I<00:24:39.919> think<00:24:40.080> a<00:24:40.520> key 00:24:40.669 --> 00:24:40.679 align:start position:0% we have we can Ru out I think a key 00:24:40.679 --> 00:24:42.669 align:start position:0% we have we can Ru out I think a key store<00:24:40.880> rollup<00:24:41.200> would<00:24:41.360> be<00:24:41.480> absolutely<00:24:41.919> great 00:24:42.669 --> 00:24:42.679 align:start position:0% store rollup would be absolutely great 00:24:42.679 --> 00:24:44.470 align:start position:0% store rollup would be absolutely great um<00:24:42.799> but<00:24:42.960> obviously<00:24:43.279> there<00:24:43.360> are<00:24:44.039> technical 00:24:44.470 --> 00:24:44.480 align:start position:0% um but obviously there are technical 00:24:44.480 --> 00:24:45.909 align:start position:0% um but obviously there are technical difficulties<00:24:44.880> to<00:24:45.039> the<00:24:45.120> keystore<00:24:45.480> rollup<00:24:45.799> as 00:24:45.909 --> 00:24:45.919 align:start position:0% difficulties to the keystore rollup as 00:24:45.919 --> 00:24:47.590 align:start position:0% difficulties to the keystore rollup as well<00:24:46.159> so<00:24:46.360> if<00:24:46.480> we<00:24:46.559> can<00:24:46.679> solve<00:24:47.000> them<00:24:47.200> for<00:24:47.440> other 00:24:47.590 --> 00:24:47.600 align:start position:0% well so if we can solve them for other 00:24:47.600 --> 00:24:48.789 align:start position:0% well so if we can solve them for other chains<00:24:47.960> I'm<00:24:48.039> sure<00:24:48.200> we<00:24:48.279> can<00:24:48.360> do<00:24:48.480> it<00:24:48.520> for<00:24:48.640> name 00:24:48.789 --> 00:24:48.799 align:start position:0% chains I'm sure we can do it for name 00:24:48.799 --> 00:24:50.110 align:start position:0% chains I'm sure we can do it for name chain<00:24:49.039> as 00:24:50.110 --> 00:24:50.120 align:start position:0% chain as 00:24:50.120 --> 00:24:52.510 align:start position:0% chain as well<00:24:51.120> all<00:24:51.279> right<00:24:51.480> we<00:24:51.600> got<00:24:51.799> one<00:24:51.960> that<00:24:52.120> just<00:24:52.360> got 00:24:52.510 --> 00:24:52.520 align:start position:0% well all right we got one that just got 00:24:52.520 --> 00:24:55.630 align:start position:0% well all right we got one that just got upvoted<00:24:53.120> quite<00:24:53.360> hard<00:24:54.120> how<00:24:54.320> will<00:24:54.679> the<00:24:55.080> ens 00:24:55.630 --> 00:24:55.640 align:start position:0% upvoted quite hard how will the ens 00:24:55.640 --> 00:24:58.950 align:start position:0% upvoted quite hard how will the ens token<00:24:56.000> be<00:24:56.279> integrated<00:24:56.919> with<00:24:57.080> name<00:24:57.320> chain 00:24:58.950 --> 00:24:58.960 align:start position:0% token be integrated with name chain 00:24:58.960 --> 00:25:00.630 align:start position:0% token be integrated with name chain um<00:24:59.240> that<00:24:59.360> is<00:24:59.480> something<00:24:59.760> for<00:24:59.919> Up<00:25:00.080> For<00:25:00.279> Debate 00:25:00.630 --> 00:25:00.640 align:start position:0% um that is something for Up For Debate 00:25:00.640 --> 00:25:02.630 align:start position:0% um that is something for Up For Debate right<00:25:00.760> now<00:25:01.200> I<00:25:01.360> believe<00:25:02.039> the<00:25:02.200> token<00:25:02.480> is 00:25:02.630 --> 00:25:02.640 align:start position:0% right now I believe the token is 00:25:02.640 --> 00:25:05.389 align:start position:0% right now I believe the token is currently<00:25:03.080> on<00:25:03.279> L1<00:25:03.919> and<00:25:04.520> for<00:25:04.720> now<00:25:04.919> it<00:25:05.039> will<00:25:05.200> stay 00:25:05.389 --> 00:25:05.399 align:start position:0% currently on L1 and for now it will stay 00:25:05.399 --> 00:25:08.149 align:start position:0% currently on L1 and for now it will stay on<00:25:05.520> L1<00:25:06.320> um<00:25:06.720> obviously<00:25:07.279> this<00:25:07.399> is<00:25:07.640> discussions 00:25:08.149 --> 00:25:08.159 align:start position:0% on L1 um obviously this is discussions 00:25:08.159 --> 00:25:10.710 align:start position:0% on L1 um obviously this is discussions about<00:25:08.520> where<00:25:08.760> we<00:25:08.919> would<00:25:09.720> put<00:25:09.919> our<00:25:10.200> Dow<00:25:10.559> and 00:25:10.710 --> 00:25:10.720 align:start position:0% about where we would put our Dow and 00:25:10.720 --> 00:25:12.590 align:start position:0% about where we would put our Dow and governance<00:25:11.159> contracts<00:25:11.760> but<00:25:12.039> um<00:25:12.320> yeah<00:25:12.480> that's 00:25:12.590 --> 00:25:12.600 align:start position:0% governance contracts but um yeah that's 00:25:12.600 --> 00:25:14.029 align:start position:0% governance contracts but um yeah that's still<00:25:12.760> off<00:25:12.919> of 00:25:14.029 --> 00:25:14.039 align:start position:0% still off of 00:25:14.039 --> 00:25:16.389 align:start position:0% still off of discussion<00:25:15.039> and<00:25:15.120> then<00:25:15.240> a<00:25:15.360> few<00:25:15.600> more<00:25:15.880> questions 00:25:16.389 --> 00:25:16.399 align:start position:0% discussion and then a few more questions 00:25:16.399 --> 00:25:18.549 align:start position:0% discussion and then a few more questions here<00:25:16.799> how<00:25:16.960> does<00:25:17.200> ens<00:25:17.760> compare<00:25:18.360> with 00:25:18.549 --> 00:25:18.559 align:start position:0% here how does ens compare with 00:25:18.559 --> 00:25:20.870 align:start position:0% here how does ens compare with unstoppable<00:25:19.360> domains<00:25:20.360> what<00:25:20.440> do<00:25:20.520> you<00:25:20.679> guys 00:25:20.870 --> 00:25:20.880 align:start position:0% unstoppable domains what do you guys 00:25:20.880 --> 00:25:22.110 align:start position:0% unstoppable domains what do you guys think<00:25:21.120> how<00:25:21.200> does<00:25:21.399> ens<00:25:21.720> compare<00:25:22.000> with 00:25:22.110 --> 00:25:22.120 align:start position:0% think how does ens compare with 00:25:22.120 --> 00:25:24.549 align:start position:0% think how does ens compare with unstoppable 00:25:24.549 --> 00:25:24.559 align:start position:0% unstoppable 00:25:24.559 --> 00:25:27.870 align:start position:0% unstoppable domains<00:25:25.559> I<00:25:25.679> think<00:25:25.799> we're<00:25:25.960> doing<00:25:26.200> pretty<00:25:26.880> well 00:25:27.870 --> 00:25:27.880 align:start position:0% domains I think we're doing pretty well 00:25:27.880 --> 00:25:29.590 align:start position:0% domains I think we're doing pretty well I<00:25:27.960> feel<00:25:28.159> like<00:25:28.440> that<00:25:28.559> one<00:25:28.760> was<00:25:29.039> definitely<00:25:29.440> a 00:25:29.590 --> 00:25:29.600 align:start position:0% I feel like that one was definitely a 00:25:29.600 --> 00:25:32.029 align:start position:0% I feel like that one was definitely a trap<00:25:30.559> uh<00:25:30.720> the<00:25:30.880> next<00:25:31.120> question<00:25:31.520> when<00:25:31.679> will<00:25:31.880> the 00:25:32.029 --> 00:25:32.039 align:start position:0% trap uh the next question when will the 00:25:32.039 --> 00:25:35.669 align:start position:0% trap uh the next question when will the ens<00:25:32.559> manager<00:25:33.080> app<00:25:33.399> support<00:25:34.360> efp<00:25:35.360> oh<00:25:35.520> we'll 00:25:35.669 --> 00:25:35.679 align:start position:0% ens manager app support efp oh we'll 00:25:35.679 --> 00:25:36.800 align:start position:0% ens manager app support efp oh we'll have<00:25:35.760> to<00:25:35.880> talk<00:25:36.000> about<00:25:36.159> that 00:25:36.800 --> 00:25:36.810 align:start position:0% have to talk about that 00:25:36.810 --> 00:25:40.310 align:start position:0% have to talk about that [Laughter] 00:25:40.310 --> 00:25:40.320 align:start position:0% [Laughter] 00:25:40.320 --> 00:25:43.149 align:start position:0% [Laughter] bronley<00:25:41.320> all<00:25:41.520> right<00:25:42.200> uh<00:25:42.480> what<00:25:42.640> has<00:25:42.799> been<00:25:43.000> the 00:25:43.149 --> 00:25:43.159 align:start position:0% bronley all right uh what has been the 00:25:43.159 --> 00:25:45.430 align:start position:0% bronley all right uh what has been the greatest<00:25:43.640> challenge<00:25:44.279> for 00:25:45.430 --> 00:25:45.440 align:start position:0% greatest challenge for 00:25:45.440 --> 00:25:49.510 align:start position:0% greatest challenge for en<00:25:46.440> um<00:25:47.399> the<00:25:47.559> greatest<00:25:47.840> challenge<00:25:48.159> for 00:25:49.510 --> 00:25:49.520 align:start position:0% en um the greatest challenge for 00:25:49.520 --> 00:25:53.269 align:start position:0% en um the greatest challenge for en<00:25:50.520> oh<00:25:50.880> there<00:25:51.000> are<00:25:51.200> many<00:25:51.799> I<00:25:51.919> think<00:25:52.159> it<00:25:52.520> probably 00:25:53.269 --> 00:25:53.279 align:start position:0% en oh there are many I think it probably 00:25:53.279 --> 00:25:56.830 align:start position:0% en oh there are many I think it probably starts<00:25:54.279> many<00:25:54.520> many<00:25:54.799> years<00:25:55.039> ago<00:25:55.799> and<00:25:56.600> when 00:25:56.830 --> 00:25:56.840 align:start position:0% starts many many years ago and when 00:25:56.840 --> 00:25:58.630 align:start position:0% starts many many years ago and when people<00:25:57.039> didn't<00:25:57.279> really<00:25:57.559> believe<00:25:58.000> that<00:25:58.440> we 00:25:58.630 --> 00:25:58.640 align:start position:0% people didn't really believe that we 00:25:58.640 --> 00:26:01.110 align:start position:0% people didn't really believe that we were<00:25:59.360> a<00:25:59.559> project<00:25:59.840> worth<00:26:00.080> supporting<00:26:00.919> but<00:26:01.039> I 00:26:01.110 --> 00:26:01.120 align:start position:0% were a project worth supporting but I 00:26:01.120 --> 00:26:03.750 align:start position:0% were a project worth supporting but I think<00:26:01.279> we've<00:26:01.520> overcome<00:26:01.960> that<00:26:02.159> now<00:26:02.799> and<00:26:03.520> it's 00:26:03.750 --> 00:26:03.760 align:start position:0% think we've overcome that now and it's 00:26:03.760 --> 00:26:06.510 align:start position:0% think we've overcome that now and it's really<00:26:04.159> like<00:26:05.120> a<00:26:05.279> non-starter<00:26:05.919> if<00:26:06.000> your<00:26:06.159> app 00:26:06.510 --> 00:26:06.520 align:start position:0% really like a non-starter if your app 00:26:06.520 --> 00:26:08.389 align:start position:0% really like a non-starter if your app application<00:26:06.919> doesn't<00:26:07.120> support<00:26:07.360> ens<00:26:07.720> name<00:26:08.080> so 00:26:08.389 --> 00:26:08.399 align:start position:0% application doesn't support ens name so 00:26:08.399 --> 00:26:10.029 align:start position:0% application doesn't support ens name so I<00:26:08.480> think<00:26:08.679> just<00:26:08.880> overcoming<00:26:09.360> that<00:26:09.600> just<00:26:09.720> shows 00:26:10.029 --> 00:26:10.039 align:start position:0% I think just overcoming that just shows 00:26:10.039 --> 00:26:12.789 align:start position:0% I think just overcoming that just shows we're<00:26:10.279> here<00:26:10.399> to<00:26:10.600> stay<00:26:11.480> and<00:26:11.799> we're<00:26:12.440> here<00:26:12.600> to 00:26:12.789 --> 00:26:12.799 align:start position:0% we're here to stay and we're here to 00:26:12.799 --> 00:26:16.039 align:start position:0% we're here to stay and we're here to help<00:26:13.000> all<00:26:13.120> of<00:26:13.240> you<00:26:13.320> Builders<00:26:13.640> out<00:26:13.840> here