WEBVTT Kind: captions Language: en 00:00:00.230 --> 00:00:02.950 align:start position:0% good<00:00:00.950> afternoon<00:00:01.250> my<00:00:01.970> name<00:00:02.120> is<00:00:02.149> Nick<00:00:02.390> Johnson<00:00:02.810> I 00:00:02.950 --> 00:00:02.960 align:start position:0% good afternoon my name is Nick Johnson I 00:00:02.960 --> 00:00:04.389 align:start position:0% good afternoon my name is Nick Johnson I am<00:00:03.260> the<00:00:03.590> team<00:00:03.889> lead<00:00:04.100> of 00:00:04.389 --> 00:00:04.399 align:start position:0% am the team lead of 00:00:04.399 --> 00:00:07.329 align:start position:0% am the team lead of aetherium<00:00:05.120> name<00:00:05.299> service<00:00:05.689> since<00:00:06.649> we<00:00:06.859> receive 00:00:07.329 --> 00:00:07.339 align:start position:0% aetherium name service since we receive 00:00:07.339 --> 00:00:09.180 align:start position:0% aetherium name service since we receive very<00:00:07.370> generous<00:00:08.120> grant<00:00:08.269> funding<00:00:08.870> from 00:00:09.180 --> 00:00:09.190 align:start position:0% very generous grant funding from 00:00:09.190 --> 00:00:11.789 align:start position:0% very generous grant funding from aetherium<00:00:10.219> about<00:00:10.490> six<00:00:10.730> months<00:00:11.000> ago 00:00:11.789 --> 00:00:11.799 align:start position:0% aetherium about six months ago 00:00:11.799 --> 00:00:16.119 align:start position:0% aetherium about six months ago ENS<00:00:12.799> has<00:00:13.070> turned<00:00:13.339> from<00:00:13.580> a<00:00:13.940> one<00:00:14.690> person's<00:00:15.169> spare 00:00:16.119 --> 00:00:16.129 align:start position:0% ENS has turned from a one person's spare 00:00:16.129 --> 00:00:19.510 align:start position:0% ENS has turned from a one person's spare time<00:00:16.340> project<00:00:17.110> into<00:00:18.110> a<00:00:18.140> fully<00:00:18.800> funded<00:00:18.980> team<00:00:19.280> of 00:00:19.510 --> 00:00:19.520 align:start position:0% time project into a fully funded team of 00:00:19.520 --> 00:00:21.280 align:start position:0% time project into a fully funded team of nine<00:00:19.820> people<00:00:20.030> and<00:00:20.510> we<00:00:20.720> have<00:00:20.840> been<00:00:20.960> spending 00:00:21.280 --> 00:00:21.290 align:start position:0% nine people and we have been spending 00:00:21.290 --> 00:00:23.590 align:start position:0% nine people and we have been spending last<00:00:21.440> six<00:00:21.770> months<00:00:22.100> building<00:00:22.580> out<00:00:22.820> the<00:00:23.030> earnest 00:00:23.590 --> 00:00:23.600 align:start position:0% last six months building out the earnest 00:00:23.600 --> 00:00:26.020 align:start position:0% last six months building out the earnest features<00:00:24.080> and<00:00:24.260> functionality<00:00:24.890> that<00:00:25.100> we<00:00:25.730> think 00:00:26.020 --> 00:00:26.030 align:start position:0% features and functionality that we think 00:00:26.030 --> 00:00:28.540 align:start position:0% features and functionality that we think will<00:00:26.210> make<00:00:26.240> ENS<00:00:26.900> integral<00:00:27.500> to<00:00:28.070> the<00:00:28.160> future<00:00:28.460> of 00:00:28.540 --> 00:00:28.550 align:start position:0% will make ENS integral to the future of 00:00:28.550 --> 00:00:31.330 align:start position:0% will make ENS integral to the future of aetherium<00:00:29.000> n<00:00:29.180> web<00:00:29.330> 3<00:00:29.830> so<00:00:30.830> today<00:00:31.040> we're<00:00:31.250> going 00:00:31.330 --> 00:00:31.340 align:start position:0% aetherium n web 3 so today we're going 00:00:31.340 --> 00:00:35.080 align:start position:0% aetherium n web 3 so today we're going to<00:00:31.430> go<00:00:31.520> over<00:00:31.720> the<00:00:32.720> the<00:00:32.960> new<00:00:33.080> look<00:00:33.910> what<00:00:34.910> we're 00:00:35.080 --> 00:00:35.090 align:start position:0% to go over the the new look what we're 00:00:35.090 --> 00:00:37.450 align:start position:0% to go over the the new look what we're doing<00:00:35.300> about<00:00:35.390> ecosystem<00:00:36.140> support<00:00:36.530> how<00:00:37.310> we've 00:00:37.450 --> 00:00:37.460 align:start position:0% doing about ecosystem support how we've 00:00:37.460 --> 00:00:40.810 align:start position:0% doing about ecosystem support how we've been<00:00:37.580> integrating<00:00:38.150> with<00:00:38.329> dns<00:00:39.040> and<00:00:40.040> new<00:00:40.370> ENS 00:00:40.810 --> 00:00:40.820 align:start position:0% been integrating with dns and new ENS 00:00:40.820 --> 00:00:43.870 align:start position:0% been integrating with dns and new ENS management<00:00:41.300> tools<00:00:41.510> and<00:00:41.870> our<00:00:42.829> D<00:00:43.100> on<00:00:43.430> the<00:00:43.730> new 00:00:43.870 --> 00:00:43.880 align:start position:0% management tools and our D on the new 00:00:43.880 --> 00:00:45.280 align:start position:0% management tools and our D on the new registrar<00:00:44.420> that<00:00:44.630> will<00:00:44.750> replace<00:00:45.020> the<00:00:45.079> current 00:00:45.280 --> 00:00:45.290 align:start position:0% registrar that will replace the current 00:00:45.290 --> 00:00:48.520 align:start position:0% registrar that will replace the current option<00:00:45.950> system<00:00:46.270> so<00:00:47.270> first<00:00:47.780> of<00:00:47.989> all<00:00:48.050> as<00:00:48.350> you've 00:00:48.520 --> 00:00:48.530 align:start position:0% option system so first of all as you've 00:00:48.530 --> 00:00:50.800 align:start position:0% option system so first of all as you've probably<00:00:48.739> noticed<00:00:49.130> already<00:00:49.610> we<00:00:50.480> have<00:00:50.630> a<00:00:50.660> new 00:00:50.800 --> 00:00:50.810 align:start position:0% probably noticed already we have a new 00:00:50.810 --> 00:00:52.900 align:start position:0% probably noticed already we have a new look<00:00:50.989> a<00:00:51.140> shiny<00:00:51.380> new<00:00:51.590> logo<00:00:51.950> and<00:00:52.220> so<00:00:52.399> forth<00:00:52.670> and 00:00:52.900 --> 00:00:52.910 align:start position:0% look a shiny new logo and so forth and 00:00:52.910 --> 00:00:55.660 align:start position:0% look a shiny new logo and so forth and this<00:00:53.630> represents<00:00:54.380> the<00:00:54.530> fact<00:00:54.739> that<00:00:54.860> any<00:00:55.370> sort 00:00:55.660 --> 00:00:55.670 align:start position:0% this represents the fact that any sort 00:00:55.670 --> 00:00:57.639 align:start position:0% this represents the fact that any sort of<00:00:55.730> takes<00:00:56.030> the<00:00:56.210> sharp<00:00:56.450> edges<00:00:56.660> off<00:00:57.110> etherium 00:00:57.639 --> 00:00:57.649 align:start position:0% of takes the sharp edges off etherium 00:00:57.649 --> 00:00:59.650 align:start position:0% of takes the sharp edges off etherium and<00:00:57.860> we've<00:00:58.399> been<00:00:58.550> rolling<00:00:58.730> this<00:00:59.059> out<00:00:59.270> across 00:00:59.650 --> 00:00:59.660 align:start position:0% and we've been rolling this out across 00:00:59.660 --> 00:01:05.259 align:start position:0% and we've been rolling this out across all<00:01:00.530> of<00:01:00.739> our<00:01:00.860> applications<00:01:03.249> so<00:01:04.249> one<00:01:05.059> of<00:01:05.089> the 00:01:05.259 --> 00:01:05.269 align:start position:0% all of our applications so one of the 00:01:05.269 --> 00:01:06.760 align:start position:0% all of our applications so one of the main<00:01:05.449> efforts<00:01:05.810> that<00:01:05.990> we've<00:01:06.109> been<00:01:06.229> engaging<00:01:06.530> in 00:01:06.760 --> 00:01:06.770 align:start position:0% main efforts that we've been engaging in 00:01:06.770 --> 00:01:08.620 align:start position:0% main efforts that we've been engaging in in<00:01:06.950> the<00:01:07.009> last<00:01:07.189> six<00:01:07.460> months<00:01:07.549> is<00:01:07.939> integrating 00:01:08.620 --> 00:01:08.630 align:start position:0% in the last six months is integrating 00:01:08.630 --> 00:01:11.099 align:start position:0% in the last six months is integrating with<00:01:08.810> existing<00:01:09.200> DNS<00:01:09.829> services 00:01:11.099 --> 00:01:11.109 align:start position:0% with existing DNS services 00:01:11.109 --> 00:01:13.690 align:start position:0% with existing DNS services eeeyah<00:01:12.109> nice<00:01:12.350> when<00:01:12.950> it<00:01:13.039> was<00:01:13.130> launched<00:01:13.490> hit 00:01:13.690 --> 00:01:13.700 align:start position:0% eeeyah nice when it was launched hit 00:01:13.700 --> 00:01:15.789 align:start position:0% eeeyah nice when it was launched hit only<00:01:13.850> the<00:01:14.030> dot<00:01:14.329> eath<00:01:14.539> top-level<00:01:15.109> domain<00:01:15.499> and 00:01:15.789 --> 00:01:15.799 align:start position:0% only the dot eath top-level domain and 00:01:15.799 --> 00:01:18.730 align:start position:0% only the dot eath top-level domain and death<00:01:16.429> is<00:01:16.700> exclusive<00:01:17.389> to<00:01:17.689> aetherium<00:01:18.469> into<00:01:18.709> a 00:01:18.730 --> 00:01:18.740 align:start position:0% death is exclusive to aetherium into a 00:01:18.740 --> 00:01:20.980 align:start position:0% death is exclusive to aetherium into a genious<00:01:19.039> it<00:01:19.880> works<00:01:20.149> only<00:01:20.359> to<00:01:20.600> resolve 00:01:20.980 --> 00:01:20.990 align:start position:0% genious it works only to resolve 00:01:20.990 --> 00:01:23.770 align:start position:0% genious it works only to resolve services<00:01:21.499> inside<00:01:21.799> DNS<00:01:22.189> and<00:01:22.399> so<00:01:22.579> on<00:01:22.729> but<00:01:23.600> we 00:01:23.770 --> 00:01:23.780 align:start position:0% services inside DNS and so on but we 00:01:23.780 --> 00:01:25.809 align:start position:0% services inside DNS and so on but we consider<00:01:24.229> it<00:01:24.439> to<00:01:24.469> be<00:01:24.590> a<00:01:24.709> part<00:01:25.039> of<00:01:25.310> the<00:01:25.609> global 00:01:25.809 --> 00:01:25.819 align:start position:0% consider it to be a part of the global 00:01:25.819 --> 00:01:27.819 align:start position:0% consider it to be a part of the global route<00:01:26.209> these<00:01:26.600> sort<00:01:26.869> of<00:01:26.899> shared<00:01:27.200> namespace 00:01:27.819 --> 00:01:27.829 align:start position:0% route these sort of shared namespace 00:01:27.829 --> 00:01:30.969 align:start position:0% route these sort of shared namespace that<00:01:28.219> all<00:01:28.369> DNS<00:01:28.789> names<00:01:29.060> exist<00:01:29.420> in<00:01:29.709> and<00:01:30.709> we're 00:01:30.969 --> 00:01:30.979 align:start position:0% that all DNS names exist in and we're 00:01:30.979 --> 00:01:33.489 align:start position:0% that all DNS names exist in and we're conscious<00:01:31.459> that<00:01:31.639> we<00:01:31.789> want<00:01:31.969> to<00:01:32.029> be<00:01:32.240> a<00:01:32.509> good 00:01:33.489 --> 00:01:33.499 align:start position:0% conscious that we want to be a good 00:01:33.499 --> 00:01:36.069 align:start position:0% conscious that we want to be a good player<00:01:33.799> that<00:01:34.130> we<00:01:34.279> want<00:01:34.490> to<00:01:34.749> integrate<00:01:35.749> well 00:01:36.069 --> 00:01:36.079 align:start position:0% player that we want to integrate well 00:01:36.079 --> 00:01:37.120 align:start position:0% player that we want to integrate well with<00:01:36.109> them<00:01:36.439> we<00:01:36.529> don't<00:01:36.619> want<00:01:36.709> to<00:01:36.859> pollute<00:01:37.069> the 00:01:37.120 --> 00:01:37.130 align:start position:0% with them we don't want to pollute the 00:01:37.130 --> 00:01:39.309 align:start position:0% with them we don't want to pollute the namespace<00:01:37.700> and<00:01:37.999> we<00:01:38.389> also<00:01:38.539> want<00:01:38.840> to<00:01:38.990> integrate 00:01:39.309 --> 00:01:39.319 align:start position:0% namespace and we also want to integrate 00:01:39.319 --> 00:01:41.099 align:start position:0% namespace and we also want to integrate with<00:01:39.529> existing<00:01:39.649> systems<00:01:40.399> wherever<00:01:40.759> possible 00:01:41.099 --> 00:01:41.109 align:start position:0% with existing systems wherever possible 00:01:41.109 --> 00:01:44.949 align:start position:0% with existing systems wherever possible so<00:01:42.109> although<00:01:43.090> it's<00:01:44.090> initially<00:01:44.509> launched<00:01:44.719> with 00:01:44.949 --> 00:01:44.959 align:start position:0% so although it's initially launched with 00:01:44.959 --> 00:01:47.289 align:start position:0% so although it's initially launched with teeth<00:01:45.319> we're<00:01:45.889> pleased<00:01:46.130> to<00:01:46.279> say<00:01:46.459> that<00:01:46.490> we've 00:01:47.289 --> 00:01:47.299 align:start position:0% teeth we're pleased to say that we've 00:01:47.299 --> 00:01:48.910 align:start position:0% teeth we're pleased to say that we've already<00:01:47.479> launched<00:01:47.990> two<00:01:48.469> new<00:01:48.499> top-level 00:01:48.910 --> 00:01:48.920 align:start position:0% already launched two new top-level 00:01:48.920 --> 00:01:52.239 align:start position:0% already launched two new top-level domains<00:01:49.459> inside<00:01:49.939> ENS<00:01:50.299> dot<00:01:50.899> X<00:01:51.109> Y<00:01:51.319> Z<00:01:51.529> n<00:01:51.770> dot<00:01:51.979> luxe 00:01:52.239 --> 00:01:52.249 align:start position:0% domains inside ENS dot X Y Z n dot luxe 00:01:52.249 --> 00:01:54.789 align:start position:0% domains inside ENS dot X Y Z n dot luxe and<00:01:52.609> these<00:01:53.240> both<00:01:53.479> correspond<00:01:54.079> to<00:01:54.229> those<00:01:54.469> same 00:01:54.789 --> 00:01:54.799 align:start position:0% and these both correspond to those same 00:01:54.799 --> 00:01:58.449 align:start position:0% and these both correspond to those same top-level<00:01:55.700> domains<00:01:56.119> in<00:01:56.749> the<00:01:56.810> DNS<00:01:57.229> system<00:01:57.459> so 00:01:58.449 --> 00:01:58.459 align:start position:0% top-level domains in the DNS system so 00:01:58.459 --> 00:02:00.309 align:start position:0% top-level domains in the DNS system so let's<00:01:59.209> have<00:01:59.270> a<00:01:59.329> quick<00:01:59.479> look<00:01:59.779> at<00:01:59.929> how<00:02:00.109> we've 00:02:00.309 --> 00:02:00.319 align:start position:0% let's have a quick look at how we've 00:02:00.319 --> 00:02:02.919 align:start position:0% let's have a quick look at how we've achieved<00:02:00.439> this<00:02:00.770> integration<00:02:01.630> first<00:02:02.630> of<00:02:02.840> all 00:02:02.919 --> 00:02:02.929 align:start position:0% achieved this integration first of all 00:02:02.929 --> 00:02:04.809 align:start position:0% achieved this integration first of all for<00:02:03.200> dot<00:02:03.349> XYZ<00:02:03.919> into<00:02:04.099> what<00:02:04.219> we're<00:02:04.369> doing<00:02:04.639> is 00:02:04.809 --> 00:02:04.819 align:start position:0% for dot XYZ into what we're doing is 00:02:04.819 --> 00:02:07.569 align:start position:0% for dot XYZ into what we're doing is we're<00:02:05.060> using<00:02:05.090> DNS<00:02:05.689> set<00:02:06.099> DNS<00:02:07.099> SEC<00:02:07.369> is<00:02:07.549> the 00:02:07.569 --> 00:02:07.579 align:start position:0% we're using DNS set DNS SEC is the 00:02:07.579 --> 00:02:09.139 align:start position:0% we're using DNS set DNS SEC is the Internet 00:02:09.139 --> 00:02:09.149 align:start position:0% Internet 00:02:09.149 --> 00:02:11.869 align:start position:0% Internet dae-sik<00:02:10.079> as<00:02:10.259> the<00:02:10.379> Internet's<00:02:10.799> system<00:02:11.700> for 00:02:11.869 --> 00:02:11.879 align:start position:0% dae-sik as the Internet's system for 00:02:11.879 --> 00:02:14.360 align:start position:0% dae-sik as the Internet's system for securing<00:02:12.360> domain<00:02:12.629> name<00:02:12.840> lookups<00:02:13.230> and<00:02:13.980> it 00:02:14.360 --> 00:02:14.370 align:start position:0% securing domain name lookups and it 00:02:14.370 --> 00:02:16.190 align:start position:0% securing domain name lookups and it permits<00:02:14.730> us<00:02:14.939> to<00:02:15.209> actually<00:02:15.390> prove<00:02:16.019> the 00:02:16.190 --> 00:02:16.200 align:start position:0% permits us to actually prove the 00:02:16.200 --> 00:02:19.399 align:start position:0% permits us to actually prove the ownership<00:02:16.500> of<00:02:17.269> DNS<00:02:18.269> names<00:02:18.540> and<00:02:18.930> the<00:02:19.019> content 00:02:19.399 --> 00:02:19.409 align:start position:0% ownership of DNS names and the content 00:02:19.409 --> 00:02:20.509 align:start position:0% ownership of DNS names and the content of<00:02:19.560> DNS<00:02:19.950> names 00:02:20.509 --> 00:02:20.519 align:start position:0% of DNS names 00:02:20.519 --> 00:02:24.140 align:start position:0% of DNS names so<00:02:21.390> using<00:02:21.599> that<00:02:21.780> a<00:02:22.200> user<00:02:22.650> is<00:02:22.890> able<00:02:23.040> to<00:02:23.519> register 00:02:24.140 --> 00:02:24.150 align:start position:0% so using that a user is able to register 00:02:24.150 --> 00:02:27.470 align:start position:0% so using that a user is able to register their<00:02:24.569> domain<00:02:24.900> using<00:02:25.530> the<00:02:25.859> regular<00:02:26.760> internet 00:02:27.470 --> 00:02:27.480 align:start position:0% their domain using the regular internet 00:02:27.480 --> 00:02:29.179 align:start position:0% their domain using the regular internet registrar<00:02:28.200> whatever<00:02:28.470> your<00:02:28.650> caller<00:02:28.920> your 00:02:29.179 --> 00:02:29.189 align:start position:0% registrar whatever your caller your 00:02:29.189 --> 00:02:31.729 align:start position:0% registrar whatever your caller your favorite<00:02:29.519> registrar<00:02:30.000> is<00:02:30.150> they<00:02:31.049> enable<00:02:31.409> DNS 00:02:31.729 --> 00:02:31.739 align:start position:0% favorite registrar is they enable DNS 00:02:31.739 --> 00:02:33.380 align:start position:0% favorite registrar is they enable DNS sick<00:02:32.010> which<00:02:32.310> depending<00:02:32.760> on<00:02:32.849> your<00:02:32.939> registrar 00:02:33.380 --> 00:02:33.390 align:start position:0% sick which depending on your registrar 00:02:33.390 --> 00:02:35.660 align:start position:0% sick which depending on your registrar may<00:02:33.599> just<00:02:33.780> be<00:02:33.870> a<00:02:33.900> one-click<00:02:34.230> operation<00:02:34.859> and 00:02:35.660 --> 00:02:35.670 align:start position:0% may just be a one-click operation and 00:02:35.670 --> 00:02:37.369 align:start position:0% may just be a one-click operation and then<00:02:35.819> they<00:02:35.939> add<00:02:36.060> a<00:02:36.090> text<00:02:36.480> record<00:02:36.840> under<00:02:37.230> their 00:02:37.369 --> 00:02:37.379 align:start position:0% then they add a text record under their 00:02:37.379 --> 00:02:39.740 align:start position:0% then they add a text record under their name<00:02:37.590> saying<00:02:38.099> this<00:02:38.640> is<00:02:38.849> the<00:02:38.970> etherium<00:02:39.420> address 00:02:39.740 --> 00:02:39.750 align:start position:0% name saying this is the etherium address 00:02:39.750 --> 00:02:42.680 align:start position:0% name saying this is the etherium address I<00:02:39.959> want<00:02:40.230> to<00:02:40.319> be<00:02:40.409> responsible<00:02:40.980> for<00:02:41.489> this<00:02:42.389> name 00:02:42.680 --> 00:02:42.690 align:start position:0% I want to be responsible for this name 00:02:42.690 --> 00:02:44.930 align:start position:0% I want to be responsible for this name and<00:02:43.049> then<00:02:43.620> finally<00:02:44.069> they<00:02:44.220> go<00:02:44.340> into<00:02:44.489> our<00:02:44.700> tool 00:02:44.930 --> 00:02:44.940 align:start position:0% and then finally they go into our tool 00:02:44.940 --> 00:02:47.479 align:start position:0% and then finally they go into our tool and<00:02:45.150> they<00:02:45.540> submits<00:02:45.989> the<00:02:46.230> proof<00:02:46.739> of<00:02:46.980> it<00:02:47.190> that's 00:02:47.479 --> 00:02:47.489 align:start position:0% and they submits the proof of it that's 00:02:47.489 --> 00:02:49.160 align:start position:0% and they submits the proof of it that's gathered<00:02:47.790> from<00:02:47.970> DNS<00:02:48.299> that<00:02:48.599> proves<00:02:48.840> that<00:02:49.049> they 00:02:49.160 --> 00:02:49.170 align:start position:0% gathered from DNS that proves that they 00:02:49.170 --> 00:02:50.839 align:start position:0% gathered from DNS that proves that they own<00:02:49.290> that<00:02:49.470> name<00:02:49.650> that<00:02:50.250> is<00:02:50.400> the<00:02:50.430> address<00:02:50.700> they 00:02:50.839 --> 00:02:50.849 align:start position:0% own that name that is the address they 00:02:50.849 --> 00:02:53.300 align:start position:0% own that name that is the address they wanted<00:02:51.090> to<00:02:51.150> be<00:02:51.239> assigned<00:02:51.450> to<00:02:51.599> and<00:02:51.959> that<00:02:52.530> tool 00:02:53.300 --> 00:02:53.310 align:start position:0% wanted to be assigned to and that tool 00:02:53.310 --> 00:02:55.129 align:start position:0% wanted to be assigned to and that tool then<00:02:53.609> sends<00:02:54.000> it<00:02:54.060> to<00:02:54.180> a<00:02:54.239> smart<00:02:54.480> contract<00:02:54.689> which 00:02:55.129 --> 00:02:55.139 align:start position:0% then sends it to a smart contract which 00:02:55.139 --> 00:02:56.750 align:start position:0% then sends it to a smart contract which verifies<00:02:55.409> all<00:02:55.680> the<00:02:56.010> cryptographic<00:02:56.280> proofs 00:02:56.750 --> 00:02:56.760 align:start position:0% verifies all the cryptographic proofs 00:02:56.760 --> 00:02:59.030 align:start position:0% verifies all the cryptographic proofs and<00:02:57.060> submits<00:02:57.659> it<00:02:57.750> into<00:02:57.959> a<00:02:57.989> nice<00:02:58.290> and<00:02:58.590> from<00:02:58.859> then 00:02:59.030 --> 00:02:59.040 align:start position:0% and submits it into a nice and from then 00:02:59.040 --> 00:03:01.670 align:start position:0% and submits it into a nice and from then they<00:02:59.280> can<00:02:59.459> manage<00:02:59.790> that<00:02:59.970> name<00:03:00.150> inside<00:03:00.599> Enes<00:03:01.019> so 00:03:01.670 --> 00:03:01.680 align:start position:0% they can manage that name inside Enes so 00:03:01.680 --> 00:03:04.429 align:start position:0% they can manage that name inside Enes so if<00:03:01.769> I<00:03:01.920> own<00:03:02.099> my<00:03:02.730> name<00:03:02.939> die<00:03:03.090> X<00:03:03.269> Y<00:03:03.450> Z<00:03:03.510> I<00:03:03.930> can<00:03:04.170> go 00:03:04.429 --> 00:03:04.439 align:start position:0% if I own my name die X Y Z I can go 00:03:04.439 --> 00:03:06.470 align:start position:0% if I own my name die X Y Z I can go through<00:03:04.650> this<00:03:04.769> process<00:03:05.010> and<00:03:05.639> I<00:03:05.819> can<00:03:06.030> end<00:03:06.329> up 00:03:06.470 --> 00:03:06.480 align:start position:0% through this process and I can end up 00:03:06.480 --> 00:03:08.690 align:start position:0% through this process and I can end up owning<00:03:06.810> my<00:03:07.079> name<00:03:07.290> dot<00:03:07.500> X<00:03:07.650> Y<00:03:07.829> Z<00:03:08.040> inside<00:03:08.519> here 00:03:08.690 --> 00:03:08.700 align:start position:0% owning my name dot X Y Z inside here 00:03:08.700 --> 00:03:10.429 align:start position:0% owning my name dot X Y Z inside here nice<00:03:08.879> and<00:03:09.120> if<00:03:09.299> I<00:03:09.389> go<00:03:09.540> to<00:03:09.599> my<00:03:09.750> favorite<00:03:09.930> wallet 00:03:10.429 --> 00:03:10.439 align:start position:0% nice and if I go to my favorite wallet 00:03:10.439 --> 00:03:12.619 align:start position:0% nice and if I go to my favorite wallet ass<00:03:10.590> I<00:03:10.980> can<00:03:11.189> type<00:03:11.340> my<00:03:11.549> name<00:03:11.609> to<00:03:11.879> X<00:03:12.030> Y<00:03:12.150> Z<00:03:12.329> to<00:03:12.510> see 00:03:12.619 --> 00:03:12.629 align:start position:0% ass I can type my name to X Y Z to see 00:03:12.629 --> 00:03:15.199 align:start position:0% ass I can type my name to X Y Z to see myself<00:03:12.810> funds<00:03:13.230> and<00:03:13.560> so<00:03:13.680> on<00:03:13.799> and<00:03:13.949> so<00:03:14.069> forth<00:03:14.400> so 00:03:15.199 --> 00:03:15.209 align:start position:0% myself funds and so on and so forth so 00:03:15.209 --> 00:03:17.390 align:start position:0% myself funds and so on and so forth so this<00:03:15.870> is<00:03:16.019> a<00:03:16.079> permissionless<00:03:16.560> integration<00:03:17.250> it 00:03:17.390 --> 00:03:17.400 align:start position:0% this is a permissionless integration it 00:03:17.400 --> 00:03:19.729 align:start position:0% this is a permissionless integration it doesn't<00:03:17.699> require<00:03:17.940> any<00:03:18.900> cooperation<00:03:19.169> or 00:03:19.729 --> 00:03:19.739 align:start position:0% doesn't require any cooperation or 00:03:19.739 --> 00:03:21.319 align:start position:0% doesn't require any cooperation or involvement<00:03:20.340> from<00:03:20.519> registrar's<00:03:21.120> or 00:03:21.319 --> 00:03:21.329 align:start position:0% involvement from registrar's or 00:03:21.329 --> 00:03:23.059 align:start position:0% involvement from registrar's or registries<00:03:21.810> or<00:03:21.959> I<00:03:22.019> can<00:03:22.349> because<00:03:22.709> it<00:03:22.799> relies 00:03:23.059 --> 00:03:23.069 align:start position:0% registries or I can because it relies 00:03:23.069 --> 00:03:25.490 align:start position:0% registries or I can because it relies entirely<00:03:24.030> on<00:03:24.180> public<00:03:24.569> infrastructure<00:03:25.079> the 00:03:25.490 --> 00:03:25.500 align:start position:0% entirely on public infrastructure the 00:03:25.500 --> 00:03:29.960 align:start position:0% entirely on public infrastructure the DNS<00:03:26.250> system<00:03:27.470> you<00:03:28.470> can<00:03:28.709> claim<00:03:29.400> your<00:03:29.579> own<00:03:29.730> name 00:03:29.960 --> 00:03:29.970 align:start position:0% DNS system you can claim your own name 00:03:29.970 --> 00:03:35.000 align:start position:0% DNS system you can claim your own name now<00:03:30.209> for<00:03:30.569> dot<00:03:30.720> XYZ<00:03:31.319> via<00:03:31.769> DNS<00:03:32.190> CNS<00:03:33.180> domains<00:03:34.010> and 00:03:35.000 --> 00:03:35.010 align:start position:0% now for dot XYZ via DNS CNS domains and 00:03:35.010 --> 00:03:38.059 align:start position:0% now for dot XYZ via DNS CNS domains and some<00:03:35.400> registrar's<00:03:36.000> such<00:03:36.299> as<00:03:36.480> easy<00:03:36.720> DNS<00:03:37.199> are 00:03:38.059 --> 00:03:38.069 align:start position:0% some registrar's such as easy DNS are 00:03:38.069 --> 00:03:39.830 align:start position:0% some registrar's such as easy DNS are already<00:03:38.430> working<00:03:38.819> to<00:03:38.940> make<00:03:39.060> this<00:03:39.209> easier<00:03:39.599> by 00:03:39.830 --> 00:03:39.840 align:start position:0% already working to make this easier by 00:03:39.840 --> 00:03:41.210 align:start position:0% already working to make this easier by doing<00:03:40.169> most<00:03:40.379> of<00:03:40.500> the<00:03:40.560> work<00:03:40.620> on<00:03:40.949> the<00:03:41.040> backend 00:03:41.210 --> 00:03:41.220 align:start position:0% doing most of the work on the backend 00:03:41.220 --> 00:03:43.939 align:start position:0% doing most of the work on the backend for<00:03:41.699> you<00:03:41.849> if<00:03:42.810> you're<00:03:43.049> a<00:03:43.079> developer<00:03:43.260> there<00:03:43.859> are 00:03:43.939 --> 00:03:43.949 align:start position:0% for you if you're a developer there are 00:03:43.949 --> 00:03:45.289 align:start position:0% for you if you're a developer there are a<00:03:43.979> couple<00:03:44.190> of<00:03:44.370> client<00:03:44.699> libraries<00:03:45.060> there 00:03:45.289 --> 00:03:45.299 align:start position:0% a couple of client libraries there 00:03:45.299 --> 00:03:47.719 align:start position:0% a couple of client libraries there available<00:03:45.510> these<00:03:46.319> automate<00:03:46.979> the<00:03:47.069> process<00:03:47.489> of 00:03:47.719 --> 00:03:47.729 align:start position:0% available these automate the process of 00:03:47.729 --> 00:03:50.899 align:start position:0% available these automate the process of gathering<00:03:48.150> proofs<00:03:48.690> of<00:03:48.989> DNS<00:03:49.639> compiling<00:03:50.639> them 00:03:50.899 --> 00:03:50.909 align:start position:0% gathering proofs of DNS compiling them 00:03:50.909 --> 00:03:52.969 align:start position:0% gathering proofs of DNS compiling them together<00:03:51.060> into<00:03:51.449> the<00:03:52.109> data<00:03:52.319> that<00:03:52.560> our<00:03:52.709> smart 00:03:52.969 --> 00:03:52.979 align:start position:0% together into the data that our smart 00:03:52.979 --> 00:03:54.740 align:start position:0% together into the data that our smart contract<00:03:53.400> recognizes<00:03:53.909> and<00:03:54.150> submitting<00:03:54.510> it<00:03:54.569> to 00:03:54.740 --> 00:03:54.750 align:start position:0% contract recognizes and submitting it to 00:03:54.750 --> 00:03:55.460 align:start position:0% contract recognizes and submitting it to it 00:03:55.460 --> 00:03:55.470 align:start position:0% it 00:03:55.470 --> 00:03:57.710 align:start position:0% it this<00:03:55.799> isn't<00:03:56.040> restricted<00:03:56.310> just<00:03:56.790> to<00:03:56.970> use<00:03:57.389> with<00:03:57.629> E 00:03:57.710 --> 00:03:57.720 align:start position:0% this isn't restricted just to use with E 00:03:57.720 --> 00:03:59.809 align:start position:0% this isn't restricted just to use with E and<00:03:57.750> s<00:03:57.959> either<00:03:58.260> if<00:03:58.919> you<00:03:59.129> have<00:03:59.310> an<00:03:59.400> amp<00:03:59.579> that 00:03:59.809 --> 00:03:59.819 align:start position:0% and s either if you have an amp that 00:03:59.819 --> 00:04:02.420 align:start position:0% and s either if you have an amp that needs<00:04:00.060> insight<00:04:00.569> into<00:04:00.810> DNS<00:04:01.260> you<00:04:01.859> can<00:04:02.010> use<00:04:02.190> this 00:04:02.420 --> 00:04:02.430 align:start position:0% needs insight into DNS you can use this 00:04:02.430 --> 00:04:04.670 align:start position:0% needs insight into DNS you can use this you<00:04:02.699> can<00:04:02.729> use<00:04:03.060> it<00:04:03.239> to<00:04:03.479> fetch<00:04:03.870> any<00:04:04.049> data<00:04:04.319> from 00:04:04.670 --> 00:04:04.680 align:start position:0% you can use it to fetch any data from 00:04:04.680 --> 00:04:07.250 align:start position:0% you can use it to fetch any data from DNS<00:04:05.010> that<00:04:05.069> is<00:04:05.459> in<00:04:05.699> DNA<00:04:06.389> second<00:04:06.750> abled<00:04:07.049> and 00:04:07.250 --> 00:04:07.260 align:start position:0% DNS that is in DNA second abled and 00:04:07.260 --> 00:04:09.710 align:start position:0% DNS that is in DNA second abled and trustless<00:04:08.069> lis<00:04:08.250> prove<00:04:08.519> its<00:04:08.699> existence<00:04:08.790> inside 00:04:09.710 --> 00:04:09.720 align:start position:0% trustless lis prove its existence inside 00:04:09.720 --> 00:04:14.300 align:start position:0% trustless lis prove its existence inside theorem<00:04:12.409> unfortunately<00:04:13.409> of<00:04:13.530> course<00:04:13.560> the<00:04:14.040> the 00:04:14.300 --> 00:04:14.310 align:start position:0% theorem unfortunately of course the the 00:04:14.310 --> 00:04:16.189 align:start position:0% theorem unfortunately of course the the trustless<00:04:14.729> nature<00:04:15.120> of<00:04:15.239> this<00:04:15.389> and<00:04:15.690> the<00:04:15.959> sort<00:04:16.169> of 00:04:16.189 --> 00:04:16.199 align:start position:0% trustless nature of this and the sort of 00:04:16.199 --> 00:04:18.500 align:start position:0% trustless nature of this and the sort of crypto<00:04:16.560> heavy<00:04:16.769> nature<00:04:17.190> of<00:04:17.279> it<00:04:17.400> means<00:04:17.639> that<00:04:18.029> it 00:04:18.500 --> 00:04:18.510 align:start position:0% crypto heavy nature of it means that it 00:04:18.510 --> 00:04:20.209 align:start position:0% crypto heavy nature of it means that it can<00:04:18.779> be<00:04:18.930> a<00:04:18.959> little<00:04:19.139> less<00:04:19.380> user<00:04:19.680> friendly<00:04:20.190> than 00:04:20.209 --> 00:04:20.219 align:start position:0% can be a little less user friendly than 00:04:20.219 --> 00:04:21.979 align:start position:0% can be a little less user friendly than it<00:04:20.519> might<00:04:20.669> otherwise<00:04:20.729> be 00:04:21.979 --> 00:04:21.989 align:start position:0% it might otherwise be 00:04:21.989 --> 00:04:23.450 align:start position:0% it might otherwise be the<00:04:22.109> other<00:04:22.259> integration<00:04:22.830> have<00:04:22.979> been<00:04:23.099> pursuing 00:04:23.450 --> 00:04:23.460 align:start position:0% the other integration have been pursuing 00:04:23.460 --> 00:04:26.120 align:start position:0% the other integration have been pursuing is<00:04:23.849> with<00:04:24.389> dot<00:04:24.630> lux<00:04:24.900> and<00:04:25.259> what<00:04:25.889> we've<00:04:26.009> been 00:04:26.120 --> 00:04:26.130 align:start position:0% is with dot lux and what we've been 00:04:26.130 --> 00:04:27.920 align:start position:0% is with dot lux and what we've been doing<00:04:26.370> here<00:04:26.610> is<00:04:26.789> actually<00:04:26.970> working<00:04:27.360> directly 00:04:27.920 --> 00:04:27.930 align:start position:0% doing here is actually working directly 00:04:27.930 --> 00:04:30.680 align:start position:0% doing here is actually working directly with<00:04:28.050> the<00:04:28.650> daleks<00:04:29.190> registry<00:04:29.910> and<00:04:30.120> registrar's 00:04:30.680 --> 00:04:30.690 align:start position:0% with the daleks registry and registrar's 00:04:30.690 --> 00:04:32.629 align:start position:0% with the daleks registry and registrar's and<00:04:31.050> they've<00:04:31.560> been<00:04:31.740> cooperating<00:04:32.220> to 00:04:32.629 --> 00:04:32.639 align:start position:0% and they've been cooperating to 00:04:32.639 --> 00:04:34.430 align:start position:0% and they've been cooperating to integrate<00:04:33.030> directly<00:04:33.180> with<00:04:33.569> etherium<00:04:34.050> so 00:04:34.430 --> 00:04:34.440 align:start position:0% integrate directly with etherium so 00:04:34.440 --> 00:04:36.800 align:start position:0% integrate directly with etherium so rather<00:04:35.069> than<00:04:35.340> sort<00:04:35.610> of<00:04:35.669> doing<00:04:36.330> it<00:04:36.449> through<00:04:36.630> the 00:04:36.800 --> 00:04:36.810 align:start position:0% rather than sort of doing it through the 00:04:36.810 --> 00:04:39.439 align:start position:0% rather than sort of doing it through the the<00:04:37.080> open<00:04:37.410> route<00:04:37.590> via<00:04:37.830> DNS<00:04:38.789> sick<00:04:39.030> and<00:04:39.240> having 00:04:39.439 --> 00:04:39.449 align:start position:0% the open route via DNS sick and having 00:04:39.449 --> 00:04:41.600 align:start position:0% the open route via DNS sick and having to<00:04:39.539> do<00:04:39.660> everything<00:04:40.050> ourselves<00:04:40.139> this<00:04:41.130> involves 00:04:41.600 --> 00:04:41.610 align:start position:0% to do everything ourselves this involves 00:04:41.610 --> 00:04:43.129 align:start position:0% to do everything ourselves this involves the<00:04:41.759> registrar's<00:04:42.270> and<00:04:42.569> the<00:04:42.630> registry 00:04:43.129 --> 00:04:43.139 align:start position:0% the registrar's and the registry 00:04:43.139 --> 00:04:44.990 align:start position:0% the registrar's and the registry actually<00:04:43.650> working<00:04:43.830> directly<00:04:44.310> with<00:04:44.430> us<00:04:44.669> in 00:04:44.990 --> 00:04:45.000 align:start position:0% actually working directly with us in 00:04:45.000 --> 00:04:48.740 align:start position:0% actually working directly with us in order<00:04:45.569> to<00:04:45.750> support<00:04:46.680> DNS<00:04:47.340> what<00:04:48.090> this<00:04:48.240> means<00:04:48.479> is 00:04:48.740 --> 00:04:48.750 align:start position:0% order to support DNS what this means is 00:04:48.750 --> 00:04:51.320 align:start position:0% order to support DNS what this means is that<00:04:48.780> if<00:04:48.990> you<00:04:49.080> register<00:04:49.650> Lux<00:04:50.099> domain<00:04:50.460> with<00:04:51.300> the 00:04:51.320 --> 00:04:51.330 align:start position:0% that if you register Lux domain with the 00:04:51.330 --> 00:04:53.150 align:start position:0% that if you register Lux domain with the supporting<00:04:51.840> registrar<00:04:52.380> you<00:04:52.620> could<00:04:52.770> simply<00:04:53.039> go 00:04:53.150 --> 00:04:53.160 align:start position:0% supporting registrar you could simply go 00:04:53.160 --> 00:04:55.790 align:start position:0% supporting registrar you could simply go to<00:04:53.190> that<00:04:53.430> registrar's<00:04:53.970> interface<00:04:54.360> you<00:04:55.020> can<00:04:55.259> go 00:04:55.790 --> 00:04:55.800 align:start position:0% to that registrar's interface you can go 00:04:55.800 --> 00:04:57.290 align:start position:0% to that registrar's interface you can go to<00:04:55.860> the<00:04:55.979> control<00:04:56.280> panel<00:04:56.580> and<00:04:56.729> you<00:04:56.940> can<00:04:57.090> paste 00:04:57.290 --> 00:04:57.300 align:start position:0% to the control panel and you can paste 00:04:57.300 --> 00:04:58.610 align:start position:0% to the control panel and you can paste in<00:04:57.569> the<00:04:57.659> address<00:04:57.690> that<00:04:57.990> you<00:04:58.199> want<00:04:58.440> to<00:04:58.530> be 00:04:58.610 --> 00:04:58.620 align:start position:0% in the address that you want to be 00:04:58.620 --> 00:05:00.620 align:start position:0% in the address that you want to be responsible<00:04:59.190> for<00:04:59.220> it<00:04:59.520> inside<00:04:59.849> etherium<00:05:00.300> and 00:05:00.620 --> 00:05:00.630 align:start position:0% responsible for it inside etherium and 00:05:00.630 --> 00:05:02.950 align:start position:0% responsible for it inside etherium and hit<00:05:00.930> go<00:05:01.110> and<00:05:01.139> that<00:05:01.560> certain<00:05:01.949> just<00:05:02.220> one<00:05:02.370> step 00:05:02.950 --> 00:05:02.960 align:start position:0% hit go and that certain just one step 00:05:02.960 --> 00:05:05.300 align:start position:0% hit go and that certain just one step service<00:05:03.960> we<00:05:04.139> think<00:05:04.380> demonstrates<00:05:04.979> the<00:05:05.159> sort 00:05:05.300 --> 00:05:05.310 align:start position:0% service we think demonstrates the sort 00:05:05.310 --> 00:05:07.430 align:start position:0% service we think demonstrates the sort of<00:05:05.370> usability<00:05:05.729> that<00:05:06.120> you<00:05:06.210> can<00:05:06.389> get<00:05:06.599> and<00:05:07.349> the 00:05:07.430 --> 00:05:07.440 align:start position:0% of usability that you can get and the 00:05:07.440 --> 00:05:10.059 align:start position:0% of usability that you can get and the sort<00:05:07.620> of<00:05:07.650> improvements<00:05:08.310> in<00:05:08.550> in<00:05:08.880> usability<00:05:09.180> by 00:05:10.059 --> 00:05:10.069 align:start position:0% sort of improvements in in usability by 00:05:10.069 --> 00:05:12.620 align:start position:0% sort of improvements in in usability by integrating<00:05:11.069> existing<00:05:11.280> systems<00:05:11.970> with<00:05:12.270> with 00:05:12.620 --> 00:05:12.630 align:start position:0% integrating existing systems with with 00:05:12.630 --> 00:05:17.029 align:start position:0% integrating existing systems with with web<00:05:12.810> 3<00:05:14.330> this<00:05:15.330> is<00:05:15.569> dot<00:05:16.139> luxe<00:05:16.349> is<00:05:16.470> available<00:05:16.889> now 00:05:17.029 --> 00:05:17.039 align:start position:0% web 3 this is dot luxe is available now 00:05:17.039 --> 00:05:18.950 align:start position:0% web 3 this is dot luxe is available now for<00:05:17.389> pre-registration<00:05:18.389> and<00:05:18.569> officially 00:05:18.950 --> 00:05:18.960 align:start position:0% for pre-registration and officially 00:05:18.960 --> 00:05:23.270 align:start position:0% for pre-registration and officially launches<00:05:19.380> on<00:05:19.530> November<00:05:20.310> the<00:05:20.430> 6th<00:05:21.770> and<00:05:22.770> before 00:05:23.270 --> 00:05:23.280 align:start position:0% launches on November the 6th and before 00:05:23.280 --> 00:05:24.680 align:start position:0% launches on November the 6th and before we<00:05:23.370> before<00:05:23.729> I<00:05:23.759> continue<00:05:24.000> I<00:05:24.270> should<00:05:24.539> actually 00:05:24.680 --> 00:05:24.690 align:start position:0% we before I continue I should actually 00:05:24.690 --> 00:05:28.100 align:start position:0% we before I continue I should actually say<00:05:25.099> the<00:05:26.419> integration<00:05:27.419> with<00:05:27.539> DNA<00:05:27.840> SiC<00:05:28.080> that 00:05:28.100 --> 00:05:28.110 align:start position:0% say the integration with DNA SiC that 00:05:28.110 --> 00:05:31.370 align:start position:0% say the integration with DNA SiC that we've<00:05:28.440> shown<00:05:28.710> with<00:05:29.039> XYZ<00:05:30.000> we<00:05:30.719> will<00:05:30.900> be<00:05:31.050> rolling 00:05:31.370 --> 00:05:31.380 align:start position:0% we've shown with XYZ we will be rolling 00:05:31.380 --> 00:05:33.020 align:start position:0% we've shown with XYZ we will be rolling out<00:05:31.500> to<00:05:31.710> a<00:05:31.740> number<00:05:32.039> of<00:05:32.219> other<00:05:32.400> top-level 00:05:33.020 --> 00:05:33.030 align:start position:0% out to a number of other top-level 00:05:33.030 --> 00:05:35.600 align:start position:0% out to a number of other top-level domains<00:05:33.620> basically<00:05:34.620> our<00:05:34.770> goal<00:05:34.800> is<00:05:35.190> to<00:05:35.219> support 00:05:35.600 --> 00:05:35.610 align:start position:0% domains basically our goal is to support 00:05:35.610 --> 00:05:37.129 align:start position:0% domains basically our goal is to support any<00:05:35.849> top-level<00:05:36.240> domain<00:05:36.599> that<00:05:36.810> has<00:05:36.990> the 00:05:37.129 --> 00:05:37.139 align:start position:0% any top-level domain that has the 00:05:37.139 --> 00:05:40.100 align:start position:0% any top-level domain that has the necessary<00:05:37.289> Dionysiac<00:05:38.219> tooling<00:05:39.030> setup<00:05:39.840> for<00:05:40.080> it 00:05:40.100 --> 00:05:40.110 align:start position:0% necessary Dionysiac tooling setup for it 00:05:40.110 --> 00:05:42.439 align:start position:0% necessary Dionysiac tooling setup for it and<00:05:41.070> we'll<00:05:41.310> be<00:05:41.460> doing<00:05:41.699> this<00:05:41.820> after<00:05:42.300> we've 00:05:42.439 --> 00:05:42.449 align:start position:0% and we'll be doing this after we've 00:05:42.449 --> 00:05:44.089 align:start position:0% and we'll be doing this after we've finished<00:05:43.050> the<00:05:43.289> new<00:05:43.409> manager<00:05:43.800> and<00:05:43.979> we're 00:05:44.089 --> 00:05:44.099 align:start position:0% finished the new manager and we're 00:05:44.099 --> 00:05:46.189 align:start position:0% finished the new manager and we're confident<00:05:44.550> with<00:05:44.849> the<00:05:45.300> infrastructure<00:05:45.810> and 00:05:46.189 --> 00:05:46.199 align:start position:0% confident with the infrastructure and 00:05:46.199 --> 00:05:47.899 align:start position:0% confident with the infrastructure and the<00:05:46.500> sort<00:05:46.770> of<00:05:46.800> beta<00:05:47.039> period<00:05:47.340> that<00:05:47.639> we're<00:05:47.820> doing 00:05:47.899 --> 00:05:47.909 align:start position:0% the sort of beta period that we're doing 00:05:47.909 --> 00:05:53.600 align:start position:0% the sort of beta period that we're doing now<00:05:49.340> so<00:05:50.340> and<00:05:50.990> another<00:05:51.990> avenue<00:05:52.469> of<00:05:52.610> research 00:05:53.600 --> 00:05:53.610 align:start position:0% now so and another avenue of research 00:05:53.610 --> 00:05:56.270 align:start position:0% now so and another avenue of research and<00:05:54.000> development<00:05:54.479> has<00:05:54.690> been<00:05:55.020> the<00:05:55.259> new<00:05:55.409> d3<00:05:56.069> just 00:05:56.270 --> 00:05:56.280 align:start position:0% and development has been the new d3 just 00:05:56.280 --> 00:05:57.680 align:start position:0% and development has been the new d3 just rawr<00:05:56.460> and<00:05:56.669> this<00:05:56.880> is<00:05:57.000> probably<00:05:57.210> what<00:05:57.479> a<00:05:57.509> lot<00:05:57.569> of 00:05:57.680 --> 00:05:57.690 align:start position:0% rawr and this is probably what a lot of 00:05:57.690 --> 00:05:59.149 align:start position:0% rawr and this is probably what a lot of you<00:05:57.870> have<00:05:57.990> been<00:05:58.110> waiting<00:05:58.289> to<00:05:58.500> hear<00:05:58.710> about<00:05:58.740> for 00:05:59.149 --> 00:05:59.159 align:start position:0% you have been waiting to hear about for 00:05:59.159 --> 00:06:00.279 align:start position:0% you have been waiting to hear about for the<00:05:59.250> last<00:05:59.370> year<00:05:59.819> and<00:05:59.849> a<00:05:59.969> half 00:06:00.279 --> 00:06:00.289 align:start position:0% the last year and a half 00:06:00.289 --> 00:06:02.779 align:start position:0% the last year and a half the<00:06:01.289> initial<00:06:01.650> registrar<00:06:02.159> when<00:06:02.310> we<00:06:02.430> launched 00:06:02.779 --> 00:06:02.789 align:start position:0% the initial registrar when we launched 00:06:02.789 --> 00:06:06.890 align:start position:0% the initial registrar when we launched it<00:06:02.940> in<00:06:03.150> May<00:06:03.449> 2017<00:06:04.229> was<00:06:05.690> option<00:06:06.690> based 00:06:06.890 --> 00:06:06.900 align:start position:0% it in May 2017 was option based 00:06:06.900 --> 00:06:09.140 align:start position:0% it in May 2017 was option based Stiller's<00:06:07.469> and<00:06:08.159> it<00:06:08.340> uses<00:06:08.699> what's<00:06:08.880> called<00:06:08.969> a 00:06:09.140 --> 00:06:09.150 align:start position:0% Stiller's and it uses what's called a 00:06:09.150 --> 00:06:10.879 align:start position:0% Stiller's and it uses what's called a Vickery<00:06:09.419> option<00:06:09.810> the<00:06:10.020> idea<00:06:10.289> is<00:06:10.409> that<00:06:10.440> everyone 00:06:10.879 --> 00:06:10.889 align:start position:0% Vickery option the idea is that everyone 00:06:10.889 --> 00:06:12.559 align:start position:0% Vickery option the idea is that everyone bids<00:06:11.190> on<00:06:11.400> the<00:06:11.490> name<00:06:11.699> and<00:06:11.940> then<00:06:12.360> you<00:06:12.419> have<00:06:12.539> a 00:06:12.559 --> 00:06:12.569 align:start position:0% bids on the name and then you have a 00:06:12.569 --> 00:06:14.659 align:start position:0% bids on the name and then you have a reveal<00:06:12.900> period<00:06:13.319> people<00:06:13.590> reveal<00:06:13.979> lipids<00:06:14.400> and 00:06:14.659 --> 00:06:14.669 align:start position:0% reveal period people reveal lipids and 00:06:14.669 --> 00:06:16.399 align:start position:0% reveal period people reveal lipids and the<00:06:14.729> winner<00:06:15.449> is<00:06:15.630> the<00:06:15.719> person<00:06:15.870> who<00:06:16.110> did<00:06:16.259> the 00:06:16.399 --> 00:06:16.409 align:start position:0% the winner is the person who did the 00:06:16.409 --> 00:06:18.800 align:start position:0% the winner is the person who did the most<00:06:16.699> this<00:06:17.699> system<00:06:18.120> works<00:06:18.300> very<00:06:18.419> well<00:06:18.630> for 00:06:18.800 --> 00:06:18.810 align:start position:0% most this system works very well for 00:06:18.810 --> 00:06:21.080 align:start position:0% most this system works very well for allocating<00:06:19.409> new<00:06:19.830> names<00:06:20.250> initially<00:06:20.849> when<00:06:21.060> you 00:06:21.080 --> 00:06:21.090 align:start position:0% allocating new names initially when you 00:06:21.090 --> 00:06:22.850 align:start position:0% allocating new names initially when you have<00:06:21.270> many<00:06:21.479> competing<00:06:21.840> too<00:06:22.289> many<00:06:22.590> people 00:06:22.850 --> 00:06:22.860 align:start position:0% have many competing too many people 00:06:22.860 --> 00:06:25.309 align:start position:0% have many competing too many people competing<00:06:23.340> to<00:06:23.460> by<00:06:23.580> the<00:06:23.639> same<00:06:23.940> name<00:06:24.169> but<00:06:25.169> we've 00:06:25.309 --> 00:06:25.319 align:start position:0% competing to by the same name but we've 00:06:25.319 --> 00:06:27.189 align:start position:0% competing to by the same name but we've found<00:06:25.560> that<00:06:25.650> it's<00:06:25.770> less<00:06:25.919> effective<00:06:26.490> at 00:06:27.189 --> 00:06:27.199 align:start position:0% found that it's less effective at 00:06:27.199 --> 00:06:30.019 align:start position:0% found that it's less effective at ongoing<00:06:28.199> registration<00:06:28.919> what<00:06:29.430> we<00:06:29.550> find<00:06:29.789> is 00:06:30.019 --> 00:06:30.029 align:start position:0% ongoing registration what we find is 00:06:30.029 --> 00:06:32.689 align:start position:0% ongoing registration what we find is most<00:06:30.419> people<00:06:30.839> most<00:06:31.560> names<00:06:31.889> only<00:06:32.250> get<00:06:32.550> bought 00:06:32.689 --> 00:06:32.699 align:start position:0% most people most names only get bought 00:06:32.699 --> 00:06:34.879 align:start position:0% most people most names only get bought by<00:06:32.729> one<00:06:33.060> person<00:06:33.479> there's<00:06:33.719> the<00:06:34.320> chances<00:06:34.740> of<00:06:34.770> two 00:06:34.879 --> 00:06:34.889 align:start position:0% by one person there's the chances of two 00:06:34.889 --> 00:06:35.870 align:start position:0% by one person there's the chances of two people<00:06:35.400> wanting<00:06:35.729> and 00:06:35.870 --> 00:06:35.880 align:start position:0% people wanting and 00:06:35.880 --> 00:06:37.490 align:start position:0% people wanting and name<00:06:36.000> within<00:06:36.600> a<00:06:36.780> few<00:06:36.930> days<00:06:37.080> of<00:06:37.290> each<00:06:37.350> other 00:06:37.490 --> 00:06:37.500 align:start position:0% name within a few days of each other 00:06:37.500 --> 00:06:39.560 align:start position:0% name within a few days of each other quite<00:06:37.920> low<00:06:38.160> so<00:06:38.760> we<00:06:38.850> end<00:06:38.970> up<00:06:39.030> with<00:06:39.090> quite<00:06:39.360> a<00:06:39.390> lot 00:06:39.560 --> 00:06:39.570 align:start position:0% quite low so we end up with quite a lot 00:06:39.570 --> 00:06:41.420 align:start position:0% quite low so we end up with quite a lot of<00:06:39.600> option<00:06:40.110> over<00:06:40.350> here<00:06:40.380> for<00:06:41.070> relatively 00:06:41.420 --> 00:06:41.430 align:start position:0% of option over here for relatively 00:06:41.430 --> 00:06:43.670 align:start position:0% of option over here for relatively little<00:06:41.610> return<00:06:41.970> so<00:06:42.810> our<00:06:42.930> goal<00:06:43.110> here<00:06:43.320> is<00:06:43.380> that 00:06:43.670 --> 00:06:43.680 align:start position:0% little return so our goal here is that 00:06:43.680 --> 00:06:45.440 align:start position:0% little return so our goal here is that we<00:06:43.770> want<00:06:43.950> to<00:06:43.980> migrate<00:06:44.160> to<00:06:44.520> a<00:06:44.550> new<00:06:44.610> system<00:06:45.120> the 00:06:45.440 --> 00:06:45.450 align:start position:0% we want to migrate to a new system the 00:06:45.450 --> 00:06:48.050 align:start position:0% we want to migrate to a new system the new<00:06:45.570> system<00:06:45.990> will<00:06:46.170> be<00:06:46.460> instant<00:06:47.460> buy<00:06:47.610> so 00:06:48.050 --> 00:06:48.060 align:start position:0% new system will be instant buy so 00:06:48.060 --> 00:06:49.490 align:start position:0% new system will be instant buy so instead<00:06:48.330> of<00:06:48.390> being<00:06:48.570> an<00:06:48.690> option<00:06:49.020> you<00:06:49.140> just<00:06:49.170> buy 00:06:49.490 --> 00:06:49.500 align:start position:0% instead of being an option you just buy 00:06:49.500 --> 00:06:52.490 align:start position:0% instead of being an option you just buy the<00:06:49.560> main<00:06:49.860> for<00:06:50.190> a<00:06:50.220> fixed<00:06:50.460> price<00:06:50.840> and<00:06:51.840> it<00:06:52.380> will 00:06:52.490 --> 00:06:52.500 align:start position:0% the main for a fixed price and it will 00:06:52.500 --> 00:06:54.760 align:start position:0% the main for a fixed price and it will be<00:06:52.650> rent<00:06:52.950> based<00:06:53.130> so<00:06:53.730> similar<00:06:54.270> to<00:06:54.300> existing 00:06:54.760 --> 00:06:54.770 align:start position:0% be rent based so similar to existing 00:06:54.770 --> 00:06:59.030 align:start position:0% be rent based so similar to existing systems<00:06:56.180> with<00:06:57.180> DNS<00:06:57.570> you<00:06:58.020> register<00:06:58.560> a<00:06:58.590> name<00:06:58.770> and 00:06:59.030 --> 00:06:59.040 align:start position:0% systems with DNS you register a name and 00:06:59.040 --> 00:07:02.210 align:start position:0% systems with DNS you register a name and you<00:06:59.100> pay<00:06:59.250> a<00:06:59.280> yearly<00:06:59.550> fee<00:06:59.910> to<00:07:00.270> rent<00:07:00.540> it<00:07:01.220> before 00:07:02.210 --> 00:07:02.220 align:start position:0% you pay a yearly fee to rent it before 00:07:02.220 --> 00:07:03.650 align:start position:0% you pay a yearly fee to rent it before we<00:07:02.310> launch<00:07:02.550> this<00:07:02.790> we<00:07:03.090> will<00:07:03.270> have<00:07:03.360> a<00:07:03.420> one-off 00:07:03.650 --> 00:07:03.660 align:start position:0% we launch this we will have a one-off 00:07:03.660 --> 00:07:05.840 align:start position:0% we launch this we will have a one-off option<00:07:04.290> for<00:07:04.500> shorter<00:07:04.800> names<00:07:05.010> so<00:07:05.430> presently 00:07:05.840 --> 00:07:05.850 align:start position:0% option for shorter names so presently 00:07:05.850 --> 00:07:07.760 align:start position:0% option for shorter names so presently all<00:07:06.210> ENS<00:07:06.720> names<00:07:06.960> are<00:07:07.200> at<00:07:07.260> least<00:07:07.350> seven 00:07:07.760 --> 00:07:07.770 align:start position:0% all ENS names are at least seven 00:07:07.770 --> 00:07:09.710 align:start position:0% all ENS names are at least seven characters<00:07:08.190> will<00:07:08.850> be<00:07:09.000> auctioning<00:07:09.510> names 00:07:09.710 --> 00:07:09.720 align:start position:0% characters will be auctioning names 00:07:09.720 --> 00:07:11.570 align:start position:0% characters will be auctioning names shorter<00:07:10.140> than<00:07:10.290> that<00:07:10.410> on<00:07:10.590> a<00:07:10.620> one-off<00:07:10.830> basis<00:07:11.400> for 00:07:11.570 --> 00:07:11.580 align:start position:0% shorter than that on a one-off basis for 00:07:11.580 --> 00:07:13.790 align:start position:0% shorter than that on a one-off basis for a<00:07:11.640> year's<00:07:11.880> registration<00:07:12.600> before<00:07:13.110> launch<00:07:13.500> and 00:07:13.790 --> 00:07:13.800 align:start position:0% a year's registration before launch and 00:07:13.800 --> 00:07:15.320 align:start position:0% a year's registration before launch and then<00:07:13.980> we'll<00:07:14.130> launch<00:07:14.310> the<00:07:14.520> new<00:07:14.640> registrar<00:07:15.120> and 00:07:15.320 --> 00:07:15.330 align:start position:0% then we'll launch the new registrar and 00:07:15.330 --> 00:07:16.520 align:start position:0% then we'll launch the new registrar and everything<00:07:15.720> will<00:07:15.840> transition<00:07:16.140> to<00:07:16.320> this 00:07:16.520 --> 00:07:16.530 align:start position:0% everything will transition to this 00:07:16.530 --> 00:07:18.590 align:start position:0% everything will transition to this yearly<00:07:16.800> rent<00:07:17.040> the<00:07:17.790> early<00:07:18.030> rent<00:07:18.240> will<00:07:18.360> be<00:07:18.390> the 00:07:18.590 --> 00:07:18.600 align:start position:0% yearly rent the early rent will be the 00:07:18.600 --> 00:07:21.230 align:start position:0% yearly rent the early rent will be the same<00:07:18.780> price<00:07:19.020> for<00:07:19.080> every<00:07:19.470> domain<00:07:19.760> and<00:07:20.760> our<00:07:20.970> goal 00:07:21.230 --> 00:07:21.240 align:start position:0% same price for every domain and our goal 00:07:21.240 --> 00:07:24.110 align:start position:0% same price for every domain and our goal is<00:07:21.450> to<00:07:21.480> set<00:07:21.840> it<00:07:21.870> at<00:07:22.200> a<00:07:22.470> price<00:07:23.190> that<00:07:23.220> discourages 00:07:24.110 --> 00:07:24.120 align:start position:0% is to set it at a price that discourages 00:07:24.120 --> 00:07:25.970 align:start position:0% is to set it at a price that discourages sort<00:07:24.420> of<00:07:24.480> mass<00:07:24.660> squatting<00:07:25.170> but<00:07:25.650> makes<00:07:25.830> it 00:07:25.970 --> 00:07:25.980 align:start position:0% sort of mass squatting but makes it 00:07:25.980 --> 00:07:27.530 align:start position:0% sort of mass squatting but makes it cheap<00:07:26.190> and<00:07:26.280> affordable<00:07:26.550> for<00:07:26.940> people<00:07:27.000> to<00:07:27.330> use 00:07:27.530 --> 00:07:27.540 align:start position:0% cheap and affordable for people to use 00:07:27.540 --> 00:07:29.870 align:start position:0% cheap and affordable for people to use the<00:07:27.720> unis<00:07:27.990> so<00:07:28.560> our<00:07:28.830> target<00:07:29.190> price<00:07:29.310> is<00:07:29.610> more<00:07:29.790> or 00:07:29.870 --> 00:07:29.880 align:start position:0% the unis so our target price is more or 00:07:29.880 --> 00:07:31.520 align:start position:0% the unis so our target price is more or less<00:07:30.000> the<00:07:30.150> same<00:07:30.300> as<00:07:30.480> you<00:07:30.600> see<00:07:30.630> with<00:07:30.900> DNS<00:07:31.200> names 00:07:31.520 --> 00:07:31.530 align:start position:0% less the same as you see with DNS names 00:07:31.530 --> 00:07:34.030 align:start position:0% less the same as you see with DNS names in<00:07:31.860> the<00:07:32.010> region<00:07:32.370> about<00:07:32.610> 10<00:07:32.910> US<00:07:33.150> dollars<00:07:33.450> a<00:07:33.480> year 00:07:34.030 --> 00:07:34.040 align:start position:0% in the region about 10 US dollars a year 00:07:34.040 --> 00:07:38.120 align:start position:0% in the region about 10 US dollars a year at<00:07:35.040> present<00:07:35.550> that<00:07:35.700> will<00:07:36.120> be<00:07:36.270> set<00:07:36.570> by<00:07:37.350> us<00:07:37.590> we've 00:07:38.120 --> 00:07:38.130 align:start position:0% at present that will be set by us we've 00:07:38.130 --> 00:07:41.000 align:start position:0% at present that will be set by us we've been<00:07:38.370> researching<00:07:38.670> mechanisms<00:07:39.510> to<00:07:40.260> set<00:07:40.770> the 00:07:41.000 --> 00:07:41.010 align:start position:0% been researching mechanisms to set the 00:07:41.010 --> 00:07:43.880 align:start position:0% been researching mechanisms to set the rent<00:07:41.400> price<00:07:41.580> effectively<00:07:42.300> autonomously<00:07:43.290> but 00:07:43.880 --> 00:07:43.890 align:start position:0% rent price effectively autonomously but 00:07:43.890 --> 00:07:45.260 align:start position:0% rent price effectively autonomously but we've<00:07:44.100> been<00:07:44.280> unable<00:07:44.400> to<00:07:44.550> come<00:07:44.880> up<00:07:44.970> with<00:07:45.060> one 00:07:45.260 --> 00:07:45.270 align:start position:0% we've been unable to come up with one 00:07:45.270 --> 00:07:47.120 align:start position:0% we've been unable to come up with one that<00:07:45.450> we're<00:07:45.570> confident<00:07:46.050> isn't<00:07:46.470> gamer<00:07:46.710> ball<00:07:46.980> by 00:07:47.120 --> 00:07:47.130 align:start position:0% that we're confident isn't gamer ball by 00:07:47.130 --> 00:07:48.890 align:start position:0% that we're confident isn't gamer ball by people<00:07:47.520> who<00:07:47.670> with<00:07:47.850> sufficient<00:07:48.300> resources<00:07:48.330> to 00:07:48.890 --> 00:07:48.900 align:start position:0% people who with sufficient resources to 00:07:48.900 --> 00:07:50.600 align:start position:0% people who with sufficient resources to influence<00:07:49.560> the<00:07:49.890> price<00:07:50.070> in<00:07:50.310> one<00:07:50.430> way<00:07:50.580> or 00:07:50.600 --> 00:07:50.610 align:start position:0% influence the price in one way or 00:07:50.610 --> 00:07:53.540 align:start position:0% influence the price in one way or another<00:07:51.620> counterbalancing<00:07:52.620> that<00:07:52.800> you<00:07:53.340> can 00:07:53.540 --> 00:07:53.550 align:start position:0% another counterbalancing that you can 00:07:53.550 --> 00:07:55.820 align:start position:0% another counterbalancing that you can register<00:07:53.730> and<00:07:54.390> renew<00:07:54.690> anytime<00:07:55.320> you<00:07:55.440> want<00:07:55.620> and 00:07:55.820 --> 00:07:55.830 align:start position:0% register and renew anytime you want and 00:07:55.830 --> 00:07:57.680 align:start position:0% register and renew anytime you want and for<00:07:55.950> as<00:07:56.040> long<00:07:56.160> as<00:07:56.220> you<00:07:56.430> want<00:07:56.610> so<00:07:57.210> if<00:07:57.510> you're 00:07:57.680 --> 00:07:57.690 align:start position:0% for as long as you want so if you're 00:07:57.690 --> 00:07:59.390 align:start position:0% for as long as you want so if you're happy<00:07:57.960> with<00:07:58.080> the<00:07:58.260> rent<00:07:58.410> price<00:07:58.560> 15<00:07:59.130> dollars<00:07:59.370> a 00:07:59.390 --> 00:07:59.400 align:start position:0% happy with the rent price 15 dollars a 00:07:59.400 --> 00:08:01.070 align:start position:0% happy with the rent price 15 dollars a year<00:07:59.610> and<00:07:59.880> you<00:08:00.210> want<00:08:00.420> your<00:08:00.600> domain<00:08:00.900> to<00:08:00.930> be 00:08:01.070 --> 00:08:01.080 align:start position:0% year and you want your domain to be 00:08:01.080 --> 00:08:02.600 align:start position:0% year and you want your domain to be stable<00:08:01.500> for<00:08:01.530> a<00:08:01.680> long<00:08:01.710> time<00:08:02.010> you<00:08:02.250> can<00:08:02.460> register 00:08:02.600 --> 00:08:02.610 align:start position:0% stable for a long time you can register 00:08:02.610 --> 00:08:05.060 align:start position:0% stable for a long time you can register for<00:08:02.880> a<00:08:03.030> century<00:08:03.450> and<00:08:03.630> then<00:08:03.840> you<00:08:03.960> can<00:08:04.110> say<00:08:04.320> the 00:08:05.060 --> 00:08:05.070 align:start position:0% for a century and then you can say the 00:08:05.070 --> 00:08:06.710 align:start position:0% for a century and then you can say the blockchain<00:08:05.280> ensures<00:08:05.820> that<00:08:06.000> this<00:08:06.300> name<00:08:06.540> will 00:08:06.710 --> 00:08:06.720 align:start position:0% blockchain ensures that this name will 00:08:06.720 --> 00:08:08.060 align:start position:0% blockchain ensures that this name will be<00:08:06.810> owned<00:08:06.960> by<00:08:07.050> this<00:08:07.260> contract<00:08:07.740> for<00:08:07.800> at<00:08:07.950> least 00:08:08.060 --> 00:08:08.070 align:start position:0% be owned by this contract for at least 00:08:08.070 --> 00:08:10.760 align:start position:0% be owned by this contract for at least 100<00:08:08.520> years<00:08:08.790> which<00:08:09.570> we<00:08:09.810> think<00:08:10.020> is<00:08:10.170> pretty<00:08:10.230> close 00:08:10.760 --> 00:08:10.770 align:start position:0% 100 years which we think is pretty close 00:08:10.770 --> 00:08:12.440 align:start position:0% 100 years which we think is pretty close to<00:08:11.010> an<00:08:11.100> ironclad<00:08:11.310> guarantee<00:08:11.910> for<00:08:12.150> things<00:08:12.360> like 00:08:12.440 --> 00:08:12.450 align:start position:0% to an ironclad guarantee for things like 00:08:12.450 --> 00:08:14.960 align:start position:0% to an ironclad guarantee for things like package<00:08:12.930> management<00:08:13.260> systems<00:08:13.710> it<00:08:14.610> will<00:08:14.700> also 00:08:14.960 --> 00:08:14.970 align:start position:0% package management systems it will also 00:08:14.970 --> 00:08:17.180 align:start position:0% package management systems it will also be<00:08:15.090> built<00:08:15.300> for<00:08:15.690> a<00:08:15.750> common<00:08:16.710> infrastructure 00:08:17.180 --> 00:08:17.190 align:start position:0% be built for a common infrastructure 00:08:17.190 --> 00:08:19.190 align:start position:0% be built for a common infrastructure like<00:08:17.520> parent<00:08:18.120> package<00:08:18.390> management<00:08:18.750> systems 00:08:19.190 --> 00:08:19.200 align:start position:0% like parent package management systems 00:08:19.200 --> 00:08:22.400 align:start position:0% like parent package management systems in<00:08:19.590> that<00:08:20.010> it<00:08:20.100> will<00:08:20.160> allow<00:08:20.310> people<00:08:20.820> to<00:08:21.410> renew 00:08:22.400 --> 00:08:22.410 align:start position:0% in that it will allow people to renew 00:08:22.410 --> 00:08:24.200 align:start position:0% in that it will allow people to renew other<00:08:22.800> domains<00:08:23.190> you<00:08:23.490> can<00:08:23.520> always<00:08:23.760> delete<00:08:24.090> your 00:08:24.200 --> 00:08:24.210 align:start position:0% other domains you can always delete your 00:08:24.210 --> 00:08:25.910 align:start position:0% other domains you can always delete your domain<00:08:24.510> if<00:08:24.660> you<00:08:24.750> don't<00:08:24.930> want<00:08:25.080> it<00:08:25.230> but<00:08:25.500> you<00:08:25.590> if 00:08:25.910 --> 00:08:25.920 align:start position:0% domain if you don't want it but you if 00:08:25.920 --> 00:08:27.260 align:start position:0% domain if you don't want it but you if their<00:08:26.100> domain<00:08:26.340> is<00:08:26.490> common<00:08:26.760> infrastructure 00:08:27.260 --> 00:08:27.270 align:start position:0% their domain is common infrastructure 00:08:27.270 --> 00:08:29.210 align:start position:0% their domain is common infrastructure anyone<00:08:28.110> should<00:08:28.350> be<00:08:28.440> able<00:08:28.530> to<00:08:28.620> sort<00:08:28.860> of<00:08:28.890> react 00:08:29.210 --> 00:08:29.220 align:start position:0% anyone should be able to sort of react 00:08:29.220 --> 00:08:34.010 align:start position:0% anyone should be able to sort of react to<00:08:29.580> ensure<00:08:29.880> a<00:08:29.910> continues<00:08:30.390> operating<00:08:33.020> so 00:08:34.010 --> 00:08:34.020 align:start position:0% to ensure a continues operating so 00:08:34.020 --> 00:08:36.260 align:start position:0% to ensure a continues operating so anyone<00:08:34.650> who<00:08:34.800> owns<00:08:34.950> a<00:08:35.190> domain<00:08:35.490> in<00:08:35.729> the<00:08:35.849> existing 00:08:36.260 --> 00:08:36.270 align:start position:0% anyone who owns a domain in the existing 00:08:36.270 --> 00:08:38.719 align:start position:0% anyone who owns a domain in the existing model<00:08:36.539> will<00:08:37.050> have<00:08:37.229> two<00:08:37.500> options<00:08:37.650> in<00:08:38.219> the<00:08:38.610> new 00:08:38.719 --> 00:08:38.729 align:start position:0% model will have two options in the new 00:08:38.729 --> 00:08:41.180 align:start position:0% model will have two options in the new registrar<00:08:39.300> the<00:08:40.169> first<00:08:40.349> option<00:08:40.770> is<00:08:40.919> that<00:08:41.070> they 00:08:41.180 --> 00:08:41.190 align:start position:0% registrar the first option is that they 00:08:41.190 --> 00:08:42.950 align:start position:0% registrar the first option is that they can<00:08:41.370> transfer<00:08:41.820> their<00:08:42.000> existing<00:08:42.419> domain<00:08:42.570> to 00:08:42.950 --> 00:08:42.960 align:start position:0% can transfer their existing domain to 00:08:42.960 --> 00:08:45.320 align:start position:0% can transfer their existing domain to the<00:08:42.990> new<00:08:43.080> registrar<00:08:43.740> they<00:08:44.670> have<00:08:44.820> a<00:08:44.850> full<00:08:45.120> year 00:08:45.320 --> 00:08:45.330 align:start position:0% the new registrar they have a full year 00:08:45.330 --> 00:08:47.390 align:start position:0% the new registrar they have a full year to<00:08:45.390> do<00:08:45.690> that<00:08:45.900> and<00:08:46.170> when<00:08:46.620> they<00:08:46.740> do<00:08:46.800> the<00:08:47.160> domain 00:08:47.390 --> 00:08:47.400 align:start position:0% to do that and when they do the domain 00:08:47.400 --> 00:08:48.700 align:start position:0% to do that and when they do the domain registration<00:08:48.180> get 00:08:48.700 --> 00:08:48.710 align:start position:0% registration get 00:08:48.710 --> 00:08:50.980 align:start position:0% registration get -<00:08:49.070> a<00:08:49.100> year<00:08:49.580> after<00:08:49.970> our<00:08:50.120> the<00:08:50.390> launch<00:08:50.600> of<00:08:50.780> the<00:08:50.870> new 00:08:50.980 --> 00:08:50.990 align:start position:0% - a year after our the launch of the new 00:08:50.990 --> 00:08:52.690 align:start position:0% - a year after our the launch of the new registrar<00:08:51.560> so<00:08:51.950> you<00:08:52.010> get<00:08:52.130> a<00:08:52.160> year's<00:08:52.400> total 00:08:52.690 --> 00:08:52.700 align:start position:0% registrar so you get a year's total 00:08:52.700 --> 00:08:55.570 align:start position:0% registrar so you get a year's total extra<00:08:53.330> registration<00:08:53.990> that<00:08:54.530> costs<00:08:55.010> point<00:08:55.370> zero 00:08:55.570 --> 00:08:55.580 align:start position:0% extra registration that costs point zero 00:08:55.580 --> 00:08:57.280 align:start position:0% extra registration that costs point zero one<00:08:55.790> Aoife<00:08:56.090> and<00:08:56.270> the<00:08:56.660> remainder<00:08:56.960> of<00:08:57.110> your 00:08:57.280 --> 00:08:57.290 align:start position:0% one Aoife and the remainder of your 00:08:57.290 --> 00:08:58.870 align:start position:0% one Aoife and the remainder of your deposit<00:08:57.770> that<00:08:57.890> you<00:08:57.950> paid<00:08:58.280> in<00:08:58.460> the<00:08:58.550> initial 00:08:58.870 --> 00:08:58.880 align:start position:0% deposit that you paid in the initial 00:08:58.880 --> 00:09:00.580 align:start position:0% deposit that you paid in the initial option<00:08:59.240> to<00:08:59.390> register<00:08:59.510> the<00:08:59.840> name<00:08:59.990> gets 00:09:00.580 --> 00:09:00.590 align:start position:0% option to register the name gets 00:09:00.590 --> 00:09:03.250 align:start position:0% option to register the name gets returned<00:09:00.950> to<00:09:01.070> you<00:09:01.540> if<00:09:02.540> you<00:09:02.780> don't<00:09:03.020> do<00:09:03.140> that 00:09:03.250 --> 00:09:03.260 align:start position:0% returned to you if you don't do that 00:09:03.260 --> 00:09:04.630 align:start position:0% returned to you if you don't do that within<00:09:03.440> a<00:09:03.560> year<00:09:03.590> the<00:09:03.950> name<00:09:04.100> becomes<00:09:04.430> available 00:09:04.630 --> 00:09:04.640 align:start position:0% within a year the name becomes available 00:09:04.640 --> 00:09:07.150 align:start position:0% within a year the name becomes available again<00:09:04.940> and<00:09:05.360> people<00:09:05.660> can<00:09:05.900> purchase<00:09:06.710> the<00:09:07.010> name 00:09:07.150 --> 00:09:07.160 align:start position:0% again and people can purchase the name 00:09:07.160 --> 00:09:09.280 align:start position:0% again and people can purchase the name however<00:09:07.730> your<00:09:08.120> deposit<00:09:08.660> will<00:09:08.810> always<00:09:09.110> be 00:09:09.280 --> 00:09:09.290 align:start position:0% however your deposit will always be 00:09:09.290 --> 00:09:11.290 align:start position:0% however your deposit will always be returnable<00:09:09.770> the<00:09:10.310> other<00:09:10.460> option<00:09:10.850> is<00:09:10.970> that<00:09:11.000> at 00:09:11.290 --> 00:09:11.300 align:start position:0% returnable the other option is that at 00:09:11.300 --> 00:09:12.670 align:start position:0% returnable the other option is that at any<00:09:11.450> time<00:09:11.570> after<00:09:11.960> the<00:09:12.110> launch<00:09:12.350> the<00:09:12.560> new 00:09:12.670 --> 00:09:12.680 align:start position:0% any time after the launch the new 00:09:12.680 --> 00:09:14.440 align:start position:0% any time after the launch the new registrar<00:09:13.190> you<00:09:13.430> can<00:09:13.580> release<00:09:13.820> the<00:09:14.030> name<00:09:14.180> and 00:09:14.440 --> 00:09:14.450 align:start position:0% registrar you can release the name and 00:09:14.450 --> 00:09:16.150 align:start position:0% registrar you can release the name and get<00:09:14.570> back<00:09:14.720> the<00:09:14.750> entire<00:09:15.140> deposit<00:09:15.440> you<00:09:15.650> paid<00:09:15.890> in 00:09:16.150 --> 00:09:16.160 align:start position:0% get back the entire deposit you paid in 00:09:16.160 --> 00:09:21.070 align:start position:0% get back the entire deposit you paid in the<00:09:16.250> original<00:09:16.550> option<00:09:18.640> so<00:09:19.810> one<00:09:20.810> of<00:09:20.930> the 00:09:21.070 --> 00:09:21.080 align:start position:0% the original option so one of the 00:09:21.080 --> 00:09:23.740 align:start position:0% the original option so one of the biggest<00:09:21.680> things<00:09:21.980> in<00:09:22.280> building<00:09:22.850> ENS<00:09:23.270> into<00:09:23.720> a 00:09:23.740 --> 00:09:23.750 align:start position:0% biggest things in building ENS into a 00:09:23.750 --> 00:09:25.600 align:start position:0% biggest things in building ENS into a universal<00:09:24.410> platform<00:09:24.500> is<00:09:25.070> making<00:09:25.430> sure<00:09:25.580> that 00:09:25.600 --> 00:09:25.610 align:start position:0% universal platform is making sure that 00:09:25.610 --> 00:09:28.690 align:start position:0% universal platform is making sure that ecosystem<00:09:26.080> support<00:09:27.080> is<00:09:27.260> really<00:09:27.470> good<00:09:27.680> ENS<00:09:28.460> is 00:09:28.690 --> 00:09:28.700 align:start position:0% ecosystem support is really good ENS is 00:09:28.700 --> 00:09:30.610 align:start position:0% ecosystem support is really good ENS is not<00:09:28.940> much<00:09:29.090> use<00:09:29.300> to<00:09:29.330> us<00:09:29.510> if<00:09:29.840> it's<00:09:30.110> just<00:09:30.410> a<00:09:30.470> way<00:09:30.590> to 00:09:30.610 --> 00:09:30.620 align:start position:0% not much use to us if it's just a way to 00:09:30.620 --> 00:09:32.230 align:start position:0% not much use to us if it's just a way to register<00:09:30.860> names<00:09:31.310> and<00:09:31.610> then<00:09:31.730> a<00:09:31.760> way<00:09:31.880> to<00:09:31.940> look<00:09:32.120> at 00:09:32.230 --> 00:09:32.240 align:start position:0% register names and then a way to look at 00:09:32.240 --> 00:09:34.900 align:start position:0% register names and then a way to look at names<00:09:32.480> and<00:09:32.810> none<00:09:33.380> of<00:09:33.410> the<00:09:33.560> apps<00:09:33.680> support<00:09:33.950> it<00:09:34.280> so 00:09:34.900 --> 00:09:34.910 align:start position:0% names and none of the apps support it so 00:09:34.910 --> 00:09:37.570 align:start position:0% names and none of the apps support it so one<00:09:35.300> of<00:09:35.330> our<00:09:35.510> biggest<00:09:35.950> drives<00:09:36.950> in<00:09:37.340> the<00:09:37.430> last 00:09:37.570 --> 00:09:37.580 align:start position:0% one of our biggest drives in the last 00:09:37.580 --> 00:09:39.400 align:start position:0% one of our biggest drives in the last six<00:09:37.850> months<00:09:38.150> has<00:09:38.330> been<00:09:38.510> pushing<00:09:38.750> out<00:09:39.050> more 00:09:39.400 --> 00:09:39.410 align:start position:0% six months has been pushing out more 00:09:39.410 --> 00:09:42.790 align:start position:0% six months has been pushing out more support<00:09:39.970> for<00:09:40.970> the<00:09:41.120> ecosystem<00:09:41.780> for<00:09:41.930> libraries 00:09:42.790 --> 00:09:42.800 align:start position:0% support for the ecosystem for libraries 00:09:42.800 --> 00:09:44.530 align:start position:0% support for the ecosystem for libraries and<00:09:42.830> tooling<00:09:43.310> with<00:09:43.490> the<00:09:43.580> NS<00:09:43.850> and<00:09:44.420> we're 00:09:44.530 --> 00:09:44.540 align:start position:0% and tooling with the NS and we're 00:09:44.540 --> 00:09:47.410 align:start position:0% and tooling with the NS and we're pleased<00:09:44.750> to<00:09:44.780> say<00:09:45.110> that<00:09:45.140> ethers<00:09:46.070> jeaious<00:09:46.610> whips 00:09:47.410 --> 00:09:47.420 align:start position:0% pleased to say that ethers jeaious whips 00:09:47.420 --> 00:09:49.930 align:start position:0% pleased to say that ethers jeaious whips reaper<00:09:47.810> jeaious<00:09:48.260> web<00:09:48.560> 3pi<00:09:49.010> and<00:09:49.400> webster<00:09:49.670> ej 00:09:49.930 --> 00:09:49.940 align:start position:0% reaper jeaious web 3pi and webster ej 00:09:49.940 --> 00:09:51.940 align:start position:0% reaper jeaious web 3pi and webster ej all<00:09:50.210> now<00:09:50.390> have<00:09:50.600> integrated<00:09:51.080> ENS<00:09:51.560> support 00:09:51.940 --> 00:09:51.950 align:start position:0% all now have integrated ENS support 00:09:51.950 --> 00:09:53.770 align:start position:0% all now have integrated ENS support meaning<00:09:52.730> that<00:09:52.850> if<00:09:53.000> you<00:09:53.030> use<00:09:53.300> any<00:09:53.540> of<00:09:53.630> these 00:09:53.770 --> 00:09:53.780 align:start position:0% meaning that if you use any of these 00:09:53.780 --> 00:09:55.180 align:start position:0% meaning that if you use any of these client<00:09:54.170> libraries<00:09:54.530> in<00:09:54.560> your<00:09:54.770> debt 00:09:55.180 --> 00:09:55.190 align:start position:0% client libraries in your debt 00:09:55.190 --> 00:09:57.910 align:start position:0% client libraries in your debt you<00:09:55.490> no<00:09:55.670> longer<00:09:55.820> need<00:09:56.210> to<00:09:56.420> have<00:09:56.900> a<00:09:57.470> separately 00:09:57.910 --> 00:09:57.920 align:start position:0% you no longer need to have a separately 00:09:57.920 --> 00:10:00.340 align:start position:0% you no longer need to have a separately NS<00:09:58.250> library<00:09:58.670> to<00:09:58.760> do<00:09:58.880> name<00:09:59.060> resolution<00:09:59.630> so<00:10:00.170> if 00:10:00.340 --> 00:10:00.350 align:start position:0% NS library to do name resolution so if 00:10:00.350 --> 00:10:01.840 align:start position:0% NS library to do name resolution so if you<00:10:00.650> are<00:10:00.800> using<00:10:01.010> one<00:10:01.190> of<00:10:01.250> these<00:10:01.400> libraries 00:10:01.840 --> 00:10:01.850 align:start position:0% you are using one of these libraries 00:10:01.850 --> 00:10:03.520 align:start position:0% you are using one of these libraries that's<00:10:01.970> possible<00:10:02.390> your<00:10:02.570> app<00:10:02.750> supports<00:10:03.200> NS 00:10:03.520 --> 00:10:03.530 align:start position:0% that's possible your app supports NS 00:10:03.530 --> 00:10:05.890 align:start position:0% that's possible your app supports NS without<00:10:03.890> you<00:10:04.010> even<00:10:04.130> knowing<00:10:04.430> it<00:10:04.640> and<00:10:05.630> in<00:10:05.780> the 00:10:05.890 --> 00:10:05.900 align:start position:0% without you even knowing it and in the 00:10:05.900 --> 00:10:09.700 align:start position:0% without you even knowing it and in the case<00:10:06.080> of<00:10:06.340> web<00:10:07.340> 3<00:10:07.670> so<00:10:08.450> ethers<00:10:08.810> JS<00:10:09.020> for<00:10:09.380> instance 00:10:09.700 --> 00:10:09.710 align:start position:0% case of web 3 so ethers JS for instance 00:10:09.710 --> 00:10:11.680 align:start position:0% case of web 3 so ethers JS for instance it<00:10:09.920> actually<00:10:10.310> does<00:10:10.460> automatic<00:10:11.150> name 00:10:11.680 --> 00:10:11.690 align:start position:0% it actually does automatic name 00:10:11.690 --> 00:10:14.260 align:start position:0% it actually does automatic name resolution<00:10:12.550> anytime<00:10:13.550> there<00:10:13.910> is<00:10:13.940> an<00:10:14.120> address 00:10:14.260 --> 00:10:14.270 align:start position:0% resolution anytime there is an address 00:10:14.270 --> 00:10:16.030 align:start position:0% resolution anytime there is an address field<00:10:14.660> and<00:10:14.870> in<00:10:15.320> the<00:10:15.410> case<00:10:15.620> of<00:10:15.770> some<00:10:15.890> of<00:10:15.950> these 00:10:16.030 --> 00:10:16.040 align:start position:0% field and in the case of some of these 00:10:16.040 --> 00:10:17.560 align:start position:0% field and in the case of some of these other<00:10:16.220> libraries<00:10:16.670> you<00:10:16.850> still<00:10:17.090> need<00:10:17.240> to<00:10:17.360> use<00:10:17.540> a 00:10:17.560 --> 00:10:17.570 align:start position:0% other libraries you still need to use a 00:10:17.570 --> 00:10:19.600 align:start position:0% other libraries you still need to use a separately<00:10:18.080> NS<00:10:18.380> module<00:10:18.770> but<00:10:18.950> it's<00:10:19.070> integrated 00:10:19.600 --> 00:10:19.610 align:start position:0% separately NS module but it's integrated 00:10:19.610 --> 00:10:22.900 align:start position:0% separately NS module but it's integrated that<00:10:20.450> was<00:10:20.600> the<00:10:20.690> library<00:10:21.050> for<00:10:21.260> you<00:10:21.640> we've<00:10:22.640> also 00:10:22.900 --> 00:10:22.910 align:start position:0% that was the library for you we've also 00:10:22.910 --> 00:10:24.550 align:start position:0% that was the library for you we've also of<00:10:23.030> course<00:10:23.180> been<00:10:23.510> pushing<00:10:23.990> it<00:10:24.050> out<00:10:24.200> to<00:10:24.230> more 00:10:24.550 --> 00:10:24.560 align:start position:0% of course been pushing it out to more 00:10:24.560 --> 00:10:26.230 align:start position:0% of course been pushing it out to more wallets<00:10:25.280> and<00:10:25.400> debts<00:10:25.610> and<00:10:25.910> we're<00:10:26.060> very 00:10:26.230 --> 00:10:26.240 align:start position:0% wallets and debts and we're very 00:10:26.240 --> 00:10:28.720 align:start position:0% wallets and debts and we're very grateful<00:10:26.420> for<00:10:26.900> the<00:10:27.380> cooperation<00:10:27.500> of<00:10:28.190> people 00:10:28.720 --> 00:10:28.730 align:start position:0% grateful for the cooperation of people 00:10:28.730 --> 00:10:31.060 align:start position:0% grateful for the cooperation of people such<00:10:28.940> as<00:10:28.970> argent<00:10:29.570> portal<00:10:29.960> network<00:10:30.260> get<00:10:30.860> coin 00:10:31.060 --> 00:10:31.070 align:start position:0% such as argent portal network get coin 00:10:31.070 --> 00:10:32.440 align:start position:0% such as argent portal network get coin especially<00:10:31.610> have<00:10:31.790> been<00:10:31.820> doing<00:10:32.150> a<00:10:32.210> lot<00:10:32.420> of 00:10:32.440 --> 00:10:32.450 align:start position:0% especially have been doing a lot of 00:10:32.450 --> 00:10:35.710 align:start position:0% especially have been doing a lot of integration<00:10:33.050> with<00:10:33.170> us<00:10:33.340> and<00:10:34.340> mellon<00:10:34.700> port<00:10:34.970> and 00:10:35.710 --> 00:10:35.720 align:start position:0% integration with us and mellon port and 00:10:35.720 --> 00:10:37.630 align:start position:0% integration with us and mellon port and this<00:10:35.840> is<00:10:35.990> going<00:10:36.140> to<00:10:36.200> be<00:10:36.350> one<00:10:37.190> of<00:10:37.220> our<00:10:37.430> main 00:10:37.630 --> 00:10:37.640 align:start position:0% this is going to be one of our main 00:10:37.640 --> 00:10:39.490 align:start position:0% this is going to be one of our main efforts<00:10:37.940> going<00:10:38.090> forward<00:10:38.210> is<00:10:38.690> more<00:10:39.110> developer 00:10:39.490 --> 00:10:39.500 align:start position:0% efforts going forward is more developer 00:10:39.500 --> 00:10:40.930 align:start position:0% efforts going forward is more developer relations<00:10:39.680> more<00:10:40.160> reaching<00:10:40.520> out<00:10:40.640> to<00:10:40.760> folks 00:10:40.930 --> 00:10:40.940 align:start position:0% relations more reaching out to folks 00:10:40.940 --> 00:10:43.210 align:start position:0% relations more reaching out to folks like<00:10:41.090> you<00:10:41.420> to<00:10:41.960> make<00:10:42.140> sure<00:10:42.380> that<00:10:42.620> integrating 00:10:43.210 --> 00:10:43.220 align:start position:0% like you to make sure that integrating 00:10:43.220 --> 00:10:46.950 align:start position:0% like you to make sure that integrating NS<00:10:43.490> is<00:10:43.640> the<00:10:43.760> obvious<00:10:44.120> choice<00:10:45.790> finally 00:10:46.950 --> 00:10:46.960 align:start position:0% NS is the obvious choice finally 00:10:46.960 --> 00:10:49.990 align:start position:0% NS is the obvious choice finally outreach<00:10:47.960> such<00:10:48.350> as<00:10:48.500> events<00:10:48.830> like<00:10:48.980> this<00:10:49.250> we 00:10:49.990 --> 00:10:50.000 align:start position:0% outreach such as events like this we 00:10:50.000 --> 00:10:53.380 align:start position:0% outreach such as events like this we held<00:10:50.240> a<00:10:50.450> second<00:10:50.870> ENS<00:10:51.230> workshop<00:10:51.740> in<00:10:51.950> August<00:10:52.430> in 00:10:53.380 --> 00:10:53.390 align:start position:0% held a second ENS workshop in August in 00:10:53.390 --> 00:10:55.510 align:start position:0% held a second ENS workshop in August in which<00:10:53.900> we<00:10:54.080> get<00:10:54.320> a<00:10:54.380> lot<00:10:54.620> of<00:10:54.650> feedback<00:10:55.070> and<00:10:55.100> ideas 00:10:55.510 --> 00:10:55.520 align:start position:0% which we get a lot of feedback and ideas 00:10:55.520 --> 00:10:56.890 align:start position:0% which we get a lot of feedback and ideas that<00:10:55.700> have<00:10:55.820> helped<00:10:56.060> us<00:10:56.210> improve<00:10:56.480> the 00:10:56.890 --> 00:10:56.900 align:start position:0% that have helped us improve the 00:10:56.900 --> 00:10:59.340 align:start position:0% that have helped us improve the permanent<00:10:57.290> registrar<00:10:57.770> and<00:10:57.980> other<00:10:58.100> if 00:10:59.340 --> 00:10:59.350 align:start position:0% permanent registrar and other if 00:10:59.350 --> 00:11:01.740 align:start position:0% permanent registrar and other if we<00:10:59.740> had<00:10:59.950> have<00:11:00.520> onboarding<00:11:01.000> workshops<00:11:01.450> here<00:11:01.660> at 00:11:01.740 --> 00:11:01.750 align:start position:0% we had have onboarding workshops here at 00:11:01.750 --> 00:11:03.750 align:start position:0% we had have onboarding workshops here at DEFCON<00:11:02.140> there's<00:11:02.500> one<00:11:02.650> today<00:11:02.950> at<00:11:03.130> 5:00<00:11:03.310> p.m.<00:11:03.550> if 00:11:03.750 --> 00:11:03.760 align:start position:0% DEFCON there's one today at 5:00 p.m. if 00:11:03.760 --> 00:11:05.310 align:start position:0% DEFCON there's one today at 5:00 p.m. if you<00:11:03.880> you<00:11:04.120> just<00:11:04.300> want<00:11:04.480> to<00:11:04.540> sign<00:11:04.780> up<00:11:04.930> for<00:11:04.960> a<00:11:05.110> name 00:11:05.310 --> 00:11:05.320 align:start position:0% you you just want to sign up for a name 00:11:05.320 --> 00:11:07.860 align:start position:0% you you just want to sign up for a name and<00:11:05.910> Thursday<00:11:06.910> at<00:11:07.030> 10:00<00:11:07.210> a.m.<00:11:07.360> there<00:11:07.750> is<00:11:07.780> a 00:11:07.860 --> 00:11:07.870 align:start position:0% and Thursday at 10:00 a.m. there is a 00:11:07.870 --> 00:11:09.810 align:start position:0% and Thursday at 10:00 a.m. there is a workshop<00:11:08.380> for<00:11:08.410> anyone<00:11:09.040> building<00:11:09.310> adapt<00:11:09.550> or<00:11:09.790> a 00:11:09.810 --> 00:11:09.820 align:start position:0% workshop for anyone building adapt or a 00:11:09.820 --> 00:11:11.550 align:start position:0% workshop for anyone building adapt or a wallet<00:11:10.060> who<00:11:10.330> wants<00:11:10.630> to<00:11:10.780> know<00:11:10.810> how<00:11:11.500> to 00:11:11.550 --> 00:11:11.560 align:start position:0% wallet who wants to know how to 00:11:11.560 --> 00:11:13.260 align:start position:0% wallet who wants to know how to integrate<00:11:11.890> again<00:11:12.280> SPC<00:11:12.640> and<00:11:12.760> would<00:11:13.090> love<00:11:13.210> to 00:11:13.260 --> 00:11:13.270 align:start position:0% integrate again SPC and would love to 00:11:13.270 --> 00:11:14.820 align:start position:0% integrate again SPC and would love to see<00:11:13.450> you<00:11:13.660> there 00:11:14.820 --> 00:11:14.830 align:start position:0% see you there 00:11:14.830 --> 00:11:17.160 align:start position:0% see you there and<00:11:15.190> we've<00:11:15.520> done<00:11:15.700> talks<00:11:16.030> at<00:11:16.270> a<00:11:16.300> wide<00:11:16.690> variety 00:11:17.160 --> 00:11:17.170 align:start position:0% and we've done talks at a wide variety 00:11:17.170 --> 00:11:20.520 align:start position:0% and we've done talks at a wide variety of<00:11:17.200> events<00:11:17.350> with<00:11:17.890> ENS<00:11:18.700> staff<00:11:18.940> members<00:11:19.330> and<00:11:19.540> if 00:11:20.520 --> 00:11:20.530 align:start position:0% of events with ENS staff members and if 00:11:20.530 --> 00:11:22.380 align:start position:0% of events with ENS staff members and if any<00:11:20.890> of<00:11:21.100> you<00:11:21.250> would<00:11:21.520> have<00:11:21.580> an<00:11:21.970> event<00:11:22.210> that 00:11:22.380 --> 00:11:22.390 align:start position:0% any of you would have an event that 00:11:22.390 --> 00:11:24.180 align:start position:0% any of you would have an event that you'd<00:11:22.510> like<00:11:22.690> to<00:11:22.810> see<00:11:22.960> us<00:11:23.080> at<00:11:23.260> please<00:11:23.530> come<00:11:24.010> talk 00:11:24.180 --> 00:11:24.190 align:start position:0% you'd like to see us at please come talk 00:11:24.190 --> 00:11:26.720 align:start position:0% you'd like to see us at please come talk to<00:11:24.340> us<00:11:24.460> afterwards<00:11:24.880> we'd<00:11:25.180> love<00:11:25.330> to<00:11:25.360> be<00:11:25.570> there 00:11:26.720 --> 00:11:26.730 align:start position:0% to us afterwards we'd love to be there 00:11:26.730 --> 00:11:29.940 align:start position:0% to us afterwards we'd love to be there so<00:11:27.730> next<00:11:27.880> up<00:11:28.150> we<00:11:28.780> have<00:11:28.810> been<00:11:29.080> redesigning<00:11:29.620> the 00:11:29.940 --> 00:11:29.950 align:start position:0% so next up we have been redesigning the 00:11:29.950 --> 00:11:33.680 align:start position:0% so next up we have been redesigning the interface<00:11:30.400> for<00:11:30.820> managing<00:11:31.620> ENS<00:11:32.620> names<00:11:33.010> and 00:11:33.680 --> 00:11:33.690 align:start position:0% interface for managing ENS names and 00:11:33.690 --> 00:11:36.570 align:start position:0% interface for managing ENS names and registrations<00:11:34.690> and<00:11:34.990> to<00:11:35.680> demo<00:11:35.950> that<00:11:35.980> I'd<00:11:36.370> like 00:11:36.570 --> 00:11:36.580 align:start position:0% registrations and to demo that I'd like 00:11:36.580 --> 00:11:38.250 align:start position:0% registrations and to demo that I'd like to<00:11:36.760> invite<00:11:37.030> chief<00:11:37.360> flower<00:11:37.600> the<00:11:37.870> lead<00:11:37.990> of<00:11:38.170> the 00:11:38.250 --> 00:11:38.260 align:start position:0% to invite chief flower the lead of the 00:11:38.260 --> 00:11:50.370 align:start position:0% to invite chief flower the lead of the ENS<00:11:38.620> project<00:11:39.040> manager<00:11:40.000> project<00:11:40.180> up<00:11:49.380> hi 00:11:50.370 --> 00:11:50.380 align:start position:0% ENS project manager project up hi 00:11:50.380 --> 00:11:54.030 align:start position:0% ENS project manager project up hi everyone<00:11:51.120> I'm<00:11:52.120> Jeff<00:11:52.480> Lao<00:11:52.720> and<00:11:53.110> I'm<00:11:53.500> the<00:11:53.710> lead 00:11:54.030 --> 00:11:54.040 align:start position:0% everyone I'm Jeff Lao and I'm the lead 00:11:54.040 --> 00:11:56.910 align:start position:0% everyone I'm Jeff Lao and I'm the lead developer<00:11:54.520> of<00:11:54.670> the<00:11:54.940> nest<00:11:55.390> app<00:11:55.740> I've<00:11:56.740> been 00:11:56.910 --> 00:11:56.920 align:start position:0% developer of the nest app I've been 00:11:56.920 --> 00:11:59.760 align:start position:0% developer of the nest app I've been working<00:11:57.310> with<00:11:57.340> ENS<00:11:58.090> since<00:11:58.480> June<00:11:58.840> of<00:11:59.050> 2017 00:11:59.760 --> 00:11:59.770 align:start position:0% working with ENS since June of 2017 00:11:59.770 --> 00:12:02.610 align:start position:0% working with ENS since June of 2017 building<00:12:00.430> the<00:12:00.610> original<00:12:01.150> managed<00:12:02.020> app<00:12:02.200> which 00:12:02.610 --> 00:12:02.620 align:start position:0% building the original managed app which 00:12:02.620 --> 00:12:05.120 align:start position:0% building the original managed app which following<00:12:03.430> the<00:12:03.520> launch<00:12:03.670> of<00:12:03.940> ENS<00:12:04.480> last<00:12:04.750> year 00:12:05.120 --> 00:12:05.130 align:start position:0% following the launch of ENS last year 00:12:05.130 --> 00:12:08.520 align:start position:0% following the launch of ENS last year this<00:12:06.130> was<00:12:06.190> built<00:12:06.460> as<00:12:06.640> a<00:12:06.820> proof<00:12:07.090> of<00:12:07.180> concept<00:12:07.530> for 00:12:08.520 --> 00:12:08.530 align:start position:0% this was built as a proof of concept for 00:12:08.530 --> 00:12:09.810 align:start position:0% this was built as a proof of concept for this<00:12:08.860> new<00:12:09.040> tab<00:12:09.220> but<00:12:09.340> I'm<00:12:09.400> going<00:12:09.550> to<00:12:09.580> show<00:12:09.730> you 00:12:09.810 --> 00:12:09.820 align:start position:0% this new tab but I'm going to show you 00:12:09.820 --> 00:12:11.520 align:start position:0% this new tab but I'm going to show you right<00:12:09.940> now<00:12:10.000> and<00:12:10.360> it<00:12:10.780> was<00:12:10.900> concentrated<00:12:11.440> on 00:12:11.520 --> 00:12:11.530 align:start position:0% right now and it was concentrated on 00:12:11.530 --> 00:12:13.710 align:start position:0% right now and it was concentrated on functionality<00:12:11.920> but<00:12:12.760> with<00:12:13.240> the<00:12:13.330> new<00:12:13.420> funding 00:12:13.710 --> 00:12:13.720 align:start position:0% functionality but with the new funding 00:12:13.720 --> 00:12:16.290 align:start position:0% functionality but with the new funding we<00:12:13.870> got<00:12:14.050> from<00:12:14.380> the<00:12:14.800> foundation<00:12:15.640> earlier<00:12:16.210> this 00:12:16.290 --> 00:12:16.300 align:start position:0% we got from the foundation earlier this 00:12:16.300 --> 00:12:18.480 align:start position:0% we got from the foundation earlier this year<00:12:16.360> we've<00:12:16.990> managed<00:12:17.230> to<00:12:17.290> hire<00:12:17.530> a<00:12:17.890> UX<00:12:18.430> designer 00:12:18.480 --> 00:12:18.490 align:start position:0% year we've managed to hire a UX designer 00:12:18.490 --> 00:12:21.180 align:start position:0% year we've managed to hire a UX designer and<00:12:19.180> a<00:12:19.240> UI<00:12:19.390> designer<00:12:19.510> to<00:12:20.170> help<00:12:20.620> us<00:12:20.740> revamp<00:12:21.100> the 00:12:21.180 --> 00:12:21.190 align:start position:0% and a UI designer to help us revamp the 00:12:21.190 --> 00:12:24.660 align:start position:0% and a UI designer to help us revamp the interface<00:12:21.520> so<00:12:22.420> we're<00:12:23.050> we're<00:12:23.710> focusing<00:12:24.160> on<00:12:24.310> it 00:12:24.660 --> 00:12:24.670 align:start position:0% interface so we're we're focusing on it 00:12:24.670 --> 00:12:26.400 align:start position:0% interface so we're we're focusing on it to<00:12:24.880> be<00:12:25.000> more<00:12:25.210> user<00:12:25.450> friendly<00:12:25.570> and<00:12:26.020> this<00:12:26.260> is 00:12:26.400 --> 00:12:26.410 align:start position:0% to be more user friendly and this is 00:12:26.410 --> 00:12:27.840 align:start position:0% to be more user friendly and this is what<00:12:26.560> the<00:12:26.770> revamp<00:12:27.430> I'm<00:12:27.550> going<00:12:27.670> to<00:12:27.730> show<00:12:27.820> you 00:12:27.840 --> 00:12:27.850 align:start position:0% what the revamp I'm going to show you 00:12:27.850 --> 00:12:30.840 align:start position:0% what the revamp I'm going to show you today<00:12:28.000> is<00:12:28.180> based<00:12:28.690> on<00:12:28.840> so<00:12:29.800> today<00:12:30.580> I'm<00:12:30.670> going<00:12:30.760> to 00:12:30.840 --> 00:12:30.850 align:start position:0% today is based on so today I'm going to 00:12:30.850 --> 00:12:32.700 align:start position:0% today is based on so today I'm going to show<00:12:30.940> you<00:12:30.970> a<00:12:31.090> demo<00:12:31.480> of<00:12:31.540> the<00:12:31.600> new<00:12:31.630> map<00:12:31.840> I'm<00:12:32.080> gonna 00:12:32.700 --> 00:12:32.710 align:start position:0% show you a demo of the new map I'm gonna 00:12:32.710 --> 00:12:34.620 align:start position:0% show you a demo of the new map I'm gonna show<00:12:32.890> you<00:12:32.980> how<00:12:33.100> to<00:12:33.160> set<00:12:33.640> up<00:12:33.670> your<00:12:33.760> ENS<00:12:34.270> name<00:12:34.450> if 00:12:34.620 --> 00:12:34.630 align:start position:0% show you how to set up your ENS name if 00:12:34.630 --> 00:12:36.030 align:start position:0% show you how to set up your ENS name if you<00:12:34.690> have<00:12:34.870> one<00:12:35.050> from<00:12:35.260> start<00:12:35.440> to<00:12:35.590> finish<00:12:35.620> and 00:12:36.030 --> 00:12:36.040 align:start position:0% you have one from start to finish and 00:12:36.040 --> 00:12:37.710 align:start position:0% you have one from start to finish and I'm<00:12:36.850> also<00:12:36.970> going<00:12:37.120> to<00:12:37.180> show<00:12:37.330> you<00:12:37.420> how<00:12:37.510> to<00:12:37.570> add 00:12:37.710 --> 00:12:37.720 align:start position:0% I'm also going to show you how to add 00:12:37.720 --> 00:12:38.370 align:start position:0% I'm also going to show you how to add subdomains 00:12:38.370 --> 00:12:38.380 align:start position:0% subdomains 00:12:38.380 --> 00:12:41.880 align:start position:0% subdomains so<00:12:38.950> this<00:12:39.430> is<00:12:39.640> the<00:12:40.180> new<00:12:40.750> app<00:12:40.990> right<00:12:41.530> now<00:12:41.680> so 00:12:41.880 --> 00:12:41.890 align:start position:0% so this is the new app right now so 00:12:41.890 --> 00:12:43.920 align:start position:0% so this is the new app right now so you're<00:12:42.040> greeted<00:12:42.370> by<00:12:42.400> a<00:12:42.640> large<00:12:42.880> search<00:12:43.660> bar 00:12:43.920 --> 00:12:43.930 align:start position:0% you're greeted by a large search bar 00:12:43.930 --> 00:12:47.010 align:start position:0% you're greeted by a large search bar similar<00:12:44.890> that<00:12:45.100> you<00:12:45.160> see<00:12:45.490> on<00:12:45.700> GoDaddy<00:12:46.510> or<00:12:46.750> any 00:12:47.010 --> 00:12:47.020 align:start position:0% similar that you see on GoDaddy or any 00:12:47.020 --> 00:12:49.500 align:start position:0% similar that you see on GoDaddy or any of<00:12:47.110> the<00:12:47.170> other<00:12:47.320> registrar's<00:12:47.800> and<00:12:48.370> here<00:12:49.300> you 00:12:49.500 --> 00:12:49.510 align:start position:0% of the other registrar's and here you 00:12:49.510 --> 00:12:51.810 align:start position:0% of the other registrar's and here you can<00:12:49.720> be<00:12:49.840> nosy<00:12:50.230> and<00:12:50.410> search<00:12:50.650> any<00:12:50.950> units<00:12:51.430> name<00:12:51.580> in 00:12:51.810 --> 00:12:51.820 align:start position:0% can be nosy and search any units name in 00:12:51.820 --> 00:12:55.080 align:start position:0% can be nosy and search any units name in the<00:12:51.910> registry<00:12:52.860> so<00:12:53.860> however<00:12:54.730> the<00:12:54.820> most<00:12:54.970> useful 00:12:55.080 --> 00:12:55.090 align:start position:0% the registry so however the most useful 00:12:55.090 --> 00:12:56.970 align:start position:0% the registry so however the most useful thing<00:12:55.300> you<00:12:55.390> can<00:12:55.510> do<00:12:55.630> is<00:12:55.870> search<00:12:56.380> for<00:12:56.710> names 00:12:56.970 --> 00:12:56.980 align:start position:0% thing you can do is search for names 00:12:56.980 --> 00:12:59.010 align:start position:0% thing you can do is search for names that<00:12:57.370> you<00:12:57.520> own<00:12:57.700> and<00:12:58.060> you<00:12:58.090> can<00:12:58.270> set<00:12:58.660> them<00:12:58.750> up<00:12:58.870> for 00:12:59.010 --> 00:12:59.020 align:start position:0% that you own and you can set them up for 00:12:59.020 --> 00:13:00.840 align:start position:0% that you own and you can set them up for your<00:12:59.140> own<00:12:59.200> use<00:12:59.380> so<00:13:00.070> I'm<00:13:00.190> gonna<00:13:00.340> do<00:13:00.550> that<00:13:00.670> right 00:13:00.840 --> 00:13:00.850 align:start position:0% your own use so I'm gonna do that right 00:13:00.850 --> 00:13:03.860 align:start position:0% your own use so I'm gonna do that right now<00:13:00.880> and<00:13:01.330> I'm<00:13:01.540> gonna<00:13:01.690> search<00:13:02.080> for<00:13:02.110> true<00:13:03.070> names 00:13:03.860 --> 00:13:03.870 align:start position:0% now and I'm gonna search for true names 00:13:03.870 --> 00:13:09.240 align:start position:0% now and I'm gonna search for true names eath<00:13:04.870> which<00:13:05.710> is<00:13:05.980> the<00:13:07.140> dns<00:13:08.140> name<00:13:08.350> for<00:13:08.830> the 00:13:09.240 --> 00:13:09.250 align:start position:0% eath which is the dns name for the 00:13:09.250 --> 00:13:11.809 align:start position:0% eath which is the dns name for the company<00:13:09.790> that<00:13:10.150> develops<00:13:10.900> Enis 00:13:11.809 --> 00:13:11.819 align:start position:0% company that develops Enis 00:13:11.819 --> 00:13:14.579 align:start position:0% company that develops Enis so<00:13:12.819> as<00:13:12.879> you<00:13:12.970> can<00:13:13.119> see<00:13:13.240> here<00:13:13.660> I'm<00:13:14.379> gonna<00:13:14.499> show 00:13:14.579 --> 00:13:14.589 align:start position:0% so as you can see here I'm gonna show 00:13:14.589 --> 00:13:16.829 align:start position:0% so as you can see here I'm gonna show you<00:13:14.800> there<00:13:15.459> are<00:13:15.490> two<00:13:15.579> stages<00:13:15.910> for<00:13:16.420> setting<00:13:16.720> up 00:13:16.829 --> 00:13:16.839 align:start position:0% you there are two stages for setting up 00:13:16.839 --> 00:13:19.739 align:start position:0% you there are two stages for setting up your<00:13:17.050> DNS<00:13:17.920> name<00:13:18.129> so<00:13:18.610> first<00:13:18.850> we<00:13:19.029> need<00:13:19.059> to<00:13:19.300> set<00:13:19.720> up 00:13:19.739 --> 00:13:19.749 align:start position:0% your DNS name so first we need to set up 00:13:19.749 --> 00:13:22.579 align:start position:0% your DNS name so first we need to set up an<00:13:19.990> ENS<00:13:20.619> resolver<00:13:21.069> for<00:13:21.939> our<00:13:22.059> name<00:13:22.209> and 00:13:22.579 --> 00:13:22.589 align:start position:0% an ENS resolver for our name and 00:13:22.589 --> 00:13:24.960 align:start position:0% an ENS resolver for our name and secondly<00:13:23.589> we<00:13:23.860> need<00:13:23.980> to<00:13:24.040> set<00:13:24.399> up<00:13:24.490> the<00:13:24.670> address 00:13:24.960 --> 00:13:24.970 align:start position:0% secondly we need to set up the address 00:13:24.970 --> 00:13:27.780 align:start position:0% secondly we need to set up the address record<00:13:25.540> for<00:13:25.779> that<00:13:25.869> resolver<00:13:26.519> so<00:13:27.519> what<00:13:27.670> is<00:13:27.759> a 00:13:27.780 --> 00:13:27.790 align:start position:0% record for that resolver so what is a 00:13:27.790 --> 00:13:29.639 align:start position:0% record for that resolver so what is a resolver<00:13:28.269> and<00:13:28.480> how<00:13:28.629> do<00:13:28.689> we<00:13:28.779> set<00:13:28.959> it<00:13:29.050> up<00:13:29.139> well<00:13:29.619> a 00:13:29.639 --> 00:13:29.649 align:start position:0% resolver and how do we set it up well a 00:13:29.649 --> 00:13:32.519 align:start position:0% resolver and how do we set it up well a resolver<00:13:30.220> is<00:13:30.459> a<00:13:30.759> smart<00:13:31.600> contract<00:13:32.139> that<00:13:32.319> allows 00:13:32.519 --> 00:13:32.529 align:start position:0% resolver is a smart contract that allows 00:13:32.529 --> 00:13:36.449 align:start position:0% resolver is a smart contract that allows you<00:13:32.709> to<00:13:32.769> map<00:13:33.129> your<00:13:33.459> DNS<00:13:34.179> name<00:13:34.389> to<00:13:34.839> a<00:13:34.869> record<00:13:35.529> the 00:13:36.449 --> 00:13:36.459 align:start position:0% you to map your DNS name to a record the 00:13:36.459 --> 00:13:37.980 align:start position:0% you to map your DNS name to a record the most<00:13:36.699> important<00:13:37.209> record<00:13:37.480> that<00:13:37.660> you<00:13:37.720> can<00:13:37.839> set 00:13:37.980 --> 00:13:37.990 align:start position:0% most important record that you can set 00:13:37.990 --> 00:13:39.720 align:start position:0% most important record that you can set up<00:13:38.019> is<00:13:38.199> the<00:13:38.350> address<00:13:38.679> so<00:13:39.040> you<00:13:39.100> can<00:13:39.220> resolve 00:13:39.720 --> 00:13:39.730 align:start position:0% up is the address so you can resolve 00:13:39.730 --> 00:13:42.169 align:start position:0% up is the address so you can resolve from<00:13:40.059> true<00:13:40.449> named<00:13:40.600> story--the<00:13:40.959> to<00:13:41.319> your 00:13:42.169 --> 00:13:42.179 align:start position:0% from true named story--the to your 00:13:42.179 --> 00:13:47.009 align:start position:0% from true named story--the to your unreadable<00:13:44.040> burial<00:13:45.040> dress<00:13:45.509> so<00:13:46.509> how<00:13:46.629> do<00:13:46.689> we<00:13:46.839> set 00:13:47.009 --> 00:13:47.019 align:start position:0% unreadable burial dress so how do we set 00:13:47.019 --> 00:13:48.989 align:start position:0% unreadable burial dress so how do we set up<00:13:47.050> a<00:13:47.170> resolver<00:13:47.619> well<00:13:48.220> the<00:13:48.339> easiest<00:13:48.610> way<00:13:48.790> is<00:13:48.970> to 00:13:48.989 --> 00:13:48.999 align:start position:0% up a resolver well the easiest way is to 00:13:48.999 --> 00:13:51.689 align:start position:0% up a resolver well the easiest way is to use<00:13:49.119> the<00:13:49.269> public<00:13:49.629> resolver<00:13:50.079> there<00:13:50.829> is<00:13:51.009> Venus 00:13:51.689 --> 00:13:51.699 align:start position:0% use the public resolver there is Venus 00:13:51.699 --> 00:13:53.970 align:start position:0% use the public resolver there is Venus is<00:13:51.879> deployed<00:13:52.449> a<00:13:52.689> public<00:13:53.110> resolver<00:13:53.529> contract 00:13:53.970 --> 00:13:53.980 align:start position:0% is deployed a public resolver contract 00:13:53.980 --> 00:13:56.009 align:start position:0% is deployed a public resolver contract which<00:13:54.369> is<00:13:54.999> available<00:13:55.360> for<00:13:55.600> everyone<00:13:55.809> to<00:13:55.990> use 00:13:56.009 --> 00:13:56.019 align:start position:0% which is available for everyone to use 00:13:56.019 --> 00:13:59.129 align:start position:0% which is available for everyone to use and<00:13:56.470> it<00:13:56.740> will<00:13:56.829> handle<00:13:57.069> most<00:13:57.490> of<00:13:57.790> the<00:13:58.139> record 00:13:59.129 --> 00:13:59.139 align:start position:0% and it will handle most of the record 00:13:59.139 --> 00:14:02.699 align:start position:0% and it will handle most of the record types<00:13:59.379> that<00:13:59.999> 99.9%<00:14:00.999> of<00:14:01.269> users<00:14:01.509> will<00:14:01.689> need<00:14:01.839> if 00:14:02.699 --> 00:14:02.709 align:start position:0% types that 99.9% of users will need if 00:14:02.709 --> 00:14:03.960 align:start position:0% types that 99.9% of users will need if you<00:14:02.860> have<00:14:03.009> some<00:14:03.220> advanced<00:14:03.519> usage<00:14:03.850> you<00:14:03.939> can 00:14:03.960 --> 00:14:03.970 align:start position:0% you have some advanced usage you can 00:14:03.970 --> 00:14:07.350 align:start position:0% you have some advanced usage you can also<00:14:04.179> deploy<00:14:04.449> your<00:14:04.839> own<00:14:05.050> resolver<00:14:05.970> and<00:14:06.970> point 00:14:07.350 --> 00:14:07.360 align:start position:0% also deploy your own resolver and point 00:14:07.360 --> 00:14:08.730 align:start position:0% also deploy your own resolver and point to<00:14:07.509> that<00:14:07.689> instead<00:14:07.990> but<00:14:08.050> we're<00:14:08.410> just<00:14:08.439> going<00:14:08.679> to 00:14:08.730 --> 00:14:08.740 align:start position:0% to that instead but we're just going to 00:14:08.740 --> 00:14:10.590 align:start position:0% to that instead but we're just going to use<00:14:08.889> the<00:14:09.009> public<00:14:09.249> resolver<00:14:09.670> so<00:14:09.970> if<00:14:10.089> I<00:14:10.179> click<00:14:10.449> on 00:14:10.590 --> 00:14:10.600 align:start position:0% use the public resolver so if I click on 00:14:10.600 --> 00:14:13.379 align:start position:0% use the public resolver so if I click on the<00:14:11.110> pencil<00:14:11.980> tool<00:14:12.339> it<00:14:12.610> will<00:14:12.730> come<00:14:13.059> up<00:14:13.209> with<00:14:13.329> a 00:14:13.379 --> 00:14:13.389 align:start position:0% the pencil tool it will come up with a 00:14:13.389 --> 00:14:16.259 align:start position:0% the pencil tool it will come up with a nice<00:14:13.980> input<00:14:14.980> box<00:14:15.189> to<00:14:15.399> type<00:14:15.579> any<00:14:15.790> resolver<00:14:16.179> you 00:14:16.259 --> 00:14:16.269 align:start position:0% nice input box to type any resolver you 00:14:16.269 --> 00:14:17.460 align:start position:0% nice input box to type any resolver you like<00:14:16.420> but<00:14:16.720> we're<00:14:16.809> just<00:14:16.839> going<00:14:17.050> to<00:14:17.079> click<00:14:17.290> on 00:14:17.460 --> 00:14:17.470 align:start position:0% like but we're just going to click on 00:14:17.470 --> 00:14:19.199 align:start position:0% like but we're just going to click on use<00:14:17.860> public<00:14:18.189> resolver<00:14:18.639> which<00:14:18.819> will 00:14:19.199 --> 00:14:19.209 align:start position:0% use public resolver which will 00:14:19.209 --> 00:14:22.079 align:start position:0% use public resolver which will pre-populate<00:14:19.480> this<00:14:20.079> with<00:14:20.439> the<00:14:21.089> public 00:14:22.079 --> 00:14:22.089 align:start position:0% pre-populate this with the public 00:14:22.089 --> 00:14:25.319 align:start position:0% pre-populate this with the public resolver<00:14:22.600> so<00:14:23.410> I'm<00:14:23.470> gonna<00:14:23.589> click<00:14:23.800> save<00:14:24.189> and<00:14:24.639> run 00:14:25.319 --> 00:14:25.329 align:start position:0% resolver so I'm gonna click save and run 00:14:25.329 --> 00:14:27.869 align:start position:0% resolver so I'm gonna click save and run meta<00:14:25.540> mask<00:14:25.779> and<00:14:26.279> we<00:14:27.279> cheat<00:14:27.490> a<00:14:27.519> little<00:14:27.670> bit<00:14:27.790> here 00:14:27.869 --> 00:14:27.879 align:start position:0% meta mask and we cheat a little bit here 00:14:27.879 --> 00:14:29.669 align:start position:0% meta mask and we cheat a little bit here we're<00:14:28.509> on<00:14:28.569> a<00:14:28.629> private<00:14:28.839> network<00:14:29.019> so<00:14:29.470> this<00:14:29.589> is 00:14:29.669 --> 00:14:29.679 align:start position:0% we're on a private network so this is 00:14:29.679 --> 00:14:32.220 align:start position:0% we're on a private network so this is gonna<00:14:29.829> confirm<00:14:30.429> immediately<00:14:30.970> and<00:14:31.209> it's<00:14:31.959> going 00:14:32.220 --> 00:14:32.230 align:start position:0% gonna confirm immediately and it's going 00:14:32.230 --> 00:14:34.559 align:start position:0% gonna confirm immediately and it's going to<00:14:32.610> yeah<00:14:33.610> I<00:14:33.639> really<00:14:33.850> wish<00:14:33.999> your<00:14:34.240> theorem<00:14:34.480> was 00:14:34.559 --> 00:14:34.569 align:start position:0% to yeah I really wish your theorem was 00:14:34.569 --> 00:14:36.809 align:start position:0% to yeah I really wish your theorem was that<00:14:34.720> fast<00:14:34.899> but<00:14:35.199> uh<00:14:35.259> just<00:14:35.829> for<00:14:36.009> the<00:14:36.069> demo<00:14:36.339> today 00:14:36.809 --> 00:14:36.819 align:start position:0% that fast but uh just for the demo today 00:14:36.819 --> 00:14:40.110 align:start position:0% that fast but uh just for the demo today we're<00:14:37.660> gonna<00:14:37.749> use<00:14:37.929> a<00:14:37.959> private<00:14:38.259> network<00:14:39.120> that's 00:14:40.110 --> 00:14:40.120 align:start position:0% we're gonna use a private network that's 00:14:40.120 --> 00:14:41.040 align:start position:0% we're gonna use a private network that's the<00:14:40.209> resolver<00:14:40.569> set<00:14:40.749> up 00:14:41.040 --> 00:14:41.050 align:start position:0% the resolver set up 00:14:41.050 --> 00:14:43.710 align:start position:0% the resolver set up that<00:14:41.529> means<00:14:41.800> we're<00:14:42.160> now<00:14:42.309> to<00:14:42.370> add<00:14:42.699> up<00:14:42.850> we<00:14:43.509> are 00:14:43.710 --> 00:14:43.720 align:start position:0% that means we're now to add up we are 00:14:43.720 --> 00:14:45.269 align:start position:0% that means we're now to add up we are able<00:14:44.019> to<00:14:44.259> add<00:14:44.350> our<00:14:44.470> own<00:14:44.499> record<00:14:44.860> types<00:14:45.069> we've 00:14:45.269 --> 00:14:45.279 align:start position:0% able to add our own record types we've 00:14:45.279 --> 00:14:46.710 align:start position:0% able to add our own record types we've got<00:14:45.429> this<00:14:45.490> nice<00:14:45.670> little<00:14:45.699> plus<00:14:46.089> here<00:14:46.389> to<00:14:46.569> add 00:14:46.710 --> 00:14:46.720 align:start position:0% got this nice little plus here to add 00:14:46.720 --> 00:14:49.590 align:start position:0% got this nice little plus here to add our<00:14:46.809> own<00:14:46.929> record<00:14:47.730> taking<00:14:48.730> the<00:14:48.910> plus<00:14:49.120> we<00:14:49.389> can 00:14:49.590 --> 00:14:49.600 align:start position:0% our own record taking the plus we can 00:14:49.600 --> 00:14:51.600 align:start position:0% our own record taking the plus we can see<00:14:49.809> a<00:14:49.839> drop<00:14:50.290> down<00:14:50.470> menu<00:14:50.529> that<00:14:51.220> will<00:14:51.309> allow<00:14:51.370> us 00:14:51.600 --> 00:14:51.610 align:start position:0% see a drop down menu that will allow us 00:14:51.610 --> 00:14:53.819 align:start position:0% see a drop down menu that will allow us to<00:14:51.670> choose<00:14:51.910> a<00:14:51.970> record<00:14:52.499> currently<00:14:53.499> we<00:14:53.649> only 00:14:53.819 --> 00:14:53.829 align:start position:0% to choose a record currently we only 00:14:53.829 --> 00:14:56.879 align:start position:0% to choose a record currently we only have<00:14:54.129> each<00:14:54.459> rest<00:14:54.790> and<00:14:55.089> content<00:14:55.660> but<00:14:56.589> in<00:14:56.799> the 00:14:56.879 --> 00:14:56.889 align:start position:0% have each rest and content but in the 00:14:56.889 --> 00:15:00.869 align:start position:0% have each rest and content but in the future<00:14:57.220> we'd<00:14:57.790> like<00:14:58.029> to<00:14:58.329> add<00:14:58.779> new<00:14:59.649> add<00:15:00.490> the<00:15:00.699> rest 00:15:00.869 --> 00:15:00.879 align:start position:0% future we'd like to add new add the rest 00:15:00.879 --> 00:15:02.939 align:start position:0% future we'd like to add new add the rest of<00:15:00.970> the<00:15:01.029> record<00:15:01.959> types<00:15:02.350> that<00:15:02.499> the<00:15:02.620> public 00:15:02.939 --> 00:15:02.949 align:start position:0% of the record types that the public 00:15:02.949 --> 00:15:05.129 align:start position:0% of the record types that the public resolved<00:15:03.309> supports<00:15:04.179> so<00:15:04.779> we're<00:15:04.929> going<00:15:05.079> to 00:15:05.129 --> 00:15:05.139 align:start position:0% resolved supports so we're going to 00:15:05.139 --> 00:15:07.019 align:start position:0% resolved supports so we're going to click<00:15:05.290> address<00:15:05.589> here<00:15:05.980> and<00:15:06.639> we're<00:15:06.819> going<00:15:06.970> to 00:15:07.019 --> 00:15:07.029 align:start position:0% click address here and we're going to 00:15:07.029 --> 00:15:09.119 align:start position:0% click address here and we're going to copy<00:15:07.240> the<00:15:07.809> owner<00:15:08.139> address<00:15:08.559> which<00:15:08.769> is<00:15:08.799> our<00:15:09.009> own 00:15:09.119 --> 00:15:09.129 align:start position:0% copy the owner address which is our own 00:15:09.129 --> 00:15:10.679 align:start position:0% copy the owner address which is our own address<00:15:09.369> so<00:15:09.579> we<00:15:09.730> want<00:15:09.970> to<00:15:10.059> point<00:15:10.240> true<00:15:10.509> names 00:15:10.679 --> 00:15:10.689 align:start position:0% address so we want to point true names 00:15:10.689 --> 00:15:13.439 align:start position:0% address so we want to point true names of<00:15:10.839> each<00:15:10.959> to<00:15:11.290> our<00:15:11.410> own<00:15:11.589> ether<00:15:12.100> dress<00:15:12.399> so<00:15:13.389> I'm 00:15:13.439 --> 00:15:13.449 align:start position:0% of each to our own ether dress so I'm 00:15:13.449 --> 00:15:17.069 align:start position:0% of each to our own ether dress so I'm gonna<00:15:13.540> click<00:15:13.720> Save<00:15:13.749> again<00:15:14.110> and<00:15:15.540> confirm<00:15:16.540> and 00:15:17.069 --> 00:15:17.079 align:start position:0% gonna click Save again and confirm and 00:15:17.079 --> 00:15:19.470 align:start position:0% gonna click Save again and confirm and that's<00:15:17.709> gonna<00:15:17.949> confirm<00:15:18.490> instantly<00:15:18.879> again<00:15:19.089> and 00:15:19.470 --> 00:15:19.480 align:start position:0% that's gonna confirm instantly again and 00:15:19.480 --> 00:15:22.650 align:start position:0% that's gonna confirm instantly again and now<00:15:20.439> we've<00:15:20.679> set<00:15:20.980> up<00:15:21.009> our<00:15:21.249> name<00:15:21.790> so<00:15:22.269> that's 00:15:22.650 --> 00:15:22.660 align:start position:0% now we've set up our name so that's 00:15:22.660 --> 00:15:23.870 align:start position:0% now we've set up our name so that's actually<00:15:22.990> it<00:15:23.259> that 00:15:23.870 --> 00:15:23.880 align:start position:0% actually it that 00:15:23.880 --> 00:15:25.970 align:start position:0% actually it that some<00:15:24.060> how<00:15:24.570> you<00:15:24.630> would<00:15:25.050> set<00:15:25.380> up<00:15:25.470> your<00:15:25.620> earnest 00:15:25.970 --> 00:15:25.980 align:start position:0% some how you would set up your earnest 00:15:25.980 --> 00:15:28.340 align:start position:0% some how you would set up your earnest name<00:15:26.160> once<00:15:26.820> you<00:15:26.940> bought<00:15:27.120> it<00:15:27.240> you<00:15:27.960> set<00:15:28.200> up<00:15:28.260> the 00:15:28.340 --> 00:15:28.350 align:start position:0% name once you bought it you set up the 00:15:28.350 --> 00:15:29.990 align:start position:0% name once you bought it you set up the resolver<00:15:28.800> you<00:15:29.040> set<00:15:29.160> up<00:15:29.250> the<00:15:29.370> address<00:15:29.610> and<00:15:29.820> now 00:15:29.990 --> 00:15:30.000 align:start position:0% resolver you set up the address and now 00:15:30.000 --> 00:15:33.770 align:start position:0% resolver you set up the address and now any<00:15:30.300> ENS<00:15:30.900> any<00:15:31.710> yes<00:15:32.040> enabled<00:15:32.610> app<00:15:32.790> will<00:15:33.240> be<00:15:33.270> able 00:15:33.770 --> 00:15:33.780 align:start position:0% any ENS any yes enabled app will be able 00:15:33.780 --> 00:15:36.770 align:start position:0% any ENS any yes enabled app will be able to<00:15:33.900> resolve<00:15:34.140> true<00:15:34.590> names<00:15:34.740> or<00:15:34.920> ease<00:15:35.040> to<00:15:35.760> 0x9 00:15:36.770 --> 00:15:36.780 align:start position:0% to resolve true names or ease to 0x9 00:15:36.780 --> 00:15:41.180 align:start position:0% to resolve true names or ease to 0x9 of'<00:15:37.380> etc<00:15:38.450> so<00:15:39.450> that's<00:15:39.870> the<00:15:40.020> basics<00:15:40.410> now<00:15:41.100> I'm 00:15:41.180 --> 00:15:41.190 align:start position:0% of' etc so that's the basics now I'm 00:15:41.190 --> 00:15:42.980 align:start position:0% of' etc so that's the basics now I'm gonna<00:15:41.310> show<00:15:41.520> you<00:15:41.550> how<00:15:41.970> to<00:15:42.000> set<00:15:42.630> up<00:15:42.660> subdomains 00:15:42.980 --> 00:15:42.990 align:start position:0% gonna show you how to set up subdomains 00:15:42.990 --> 00:15:44.870 align:start position:0% gonna show you how to set up subdomains so<00:15:43.470> subdomains<00:15:43.740> are<00:15:44.160> an<00:15:44.310> advanced<00:15:44.610> feature 00:15:44.870 --> 00:15:44.880 align:start position:0% so subdomains are an advanced feature 00:15:44.880 --> 00:15:47.390 align:start position:0% so subdomains are an advanced feature that<00:15:45.240> allows<00:15:45.480> you<00:15:45.660> to<00:15:45.780> set<00:15:45.960> up<00:15:46.080> more<00:15:46.680> ENS<00:15:47.130> names 00:15:47.390 --> 00:15:47.400 align:start position:0% that allows you to set up more ENS names 00:15:47.400 --> 00:15:49.160 align:start position:0% that allows you to set up more ENS names under<00:15:47.790> your<00:15:47.940> route<00:15:48.090> name<00:15:48.270> so<00:15:48.780> if<00:15:48.870> I<00:15:48.930> click<00:15:49.140> on 00:15:49.160 --> 00:15:49.170 align:start position:0% under your route name so if I click on 00:15:49.170 --> 00:15:52.220 align:start position:0% under your route name so if I click on the<00:15:49.410> subdomains<00:15:49.950> tab<00:15:50.850> on<00:15:51.030> this<00:15:51.120> side<00:15:51.360> it's 00:15:52.220 --> 00:15:52.230 align:start position:0% the subdomains tab on this side it's 00:15:52.230 --> 00:15:53.480 align:start position:0% the subdomains tab on this side it's going<00:15:52.350> to<00:15:52.410> show<00:15:52.560> us<00:15:52.680> what<00:15:52.740> start<00:15:53.070> domains<00:15:53.280> we 00:15:53.480 --> 00:15:53.490 align:start position:0% going to show us what start domains we 00:15:53.490 --> 00:15:55.190 align:start position:0% going to show us what start domains we have<00:15:53.640> available<00:15:53.820> we<00:15:54.390> don't<00:15:54.930> have<00:15:55.050> any 00:15:55.190 --> 00:15:55.200 align:start position:0% have available we don't have any 00:15:55.200 --> 00:15:56.450 align:start position:0% have available we don't have any subdomain<00:15:55.440> in<00:15:55.650> this<00:15:55.740> right<00:15:55.890> now<00:15:56.040> so<00:15:56.070> I'm<00:15:56.340> gonna 00:15:56.450 --> 00:15:56.460 align:start position:0% subdomain in this right now so I'm gonna 00:15:56.460 --> 00:15:59.030 align:start position:0% subdomain in this right now so I'm gonna set<00:15:56.700> one<00:15:56.730> up<00:15:57.080> so<00:15:58.080> if<00:15:58.170> I<00:15:58.230> click<00:15:58.410> on<00:15:58.500> the<00:15:58.650> button 00:15:59.030 --> 00:15:59.040 align:start position:0% set one up so if I click on the button 00:15:59.040 --> 00:16:01.190 align:start position:0% set one up so if I click on the button here<00:15:59.070> you<00:15:59.430> can<00:15:59.700> add<00:16:00.060> any<00:16:00.330> kind<00:16:00.510> of<00:16:00.630> label<00:16:00.960> for 00:16:01.190 --> 00:16:01.200 align:start position:0% here you can add any kind of label for 00:16:01.200 --> 00:16:02.570 align:start position:0% here you can add any kind of label for your<00:16:01.320> subdomain<00:16:01.650> so<00:16:02.010> we're<00:16:02.280> just<00:16:02.310> gonna 00:16:02.570 --> 00:16:02.580 align:start position:0% your subdomain so we're just gonna 00:16:02.580 --> 00:16:04.640 align:start position:0% your subdomain so we're just gonna create<00:16:03.090> a<00:16:03.150> tip<00:16:03.540> jar<00:16:03.810> for<00:16:04.080> true<00:16:04.290> name<00:16:04.440> store 00:16:04.640 --> 00:16:04.650 align:start position:0% create a tip jar for true name store 00:16:04.650 --> 00:16:06.980 align:start position:0% create a tip jar for true name store east<00:16:04.860> so<00:16:05.610> any<00:16:05.760> of<00:16:05.850> you<00:16:05.940> kind<00:16:06.360> folks<00:16:06.630> we<00:16:06.810> want<00:16:06.900> to 00:16:06.980 --> 00:16:06.990 align:start position:0% east so any of you kind folks we want to 00:16:06.990 --> 00:16:09.220 align:start position:0% east so any of you kind folks we want to donate<00:16:07.230> so<00:16:07.410> often<00:16:07.650> a<00:16:07.830> foundation<00:16:08.430> can<00:16:08.640> do<00:16:08.760> so 00:16:09.220 --> 00:16:09.230 align:start position:0% donate so often a foundation can do so 00:16:09.230 --> 00:16:14.050 align:start position:0% donate so often a foundation can do so so<00:16:10.230> I'm<00:16:10.350> gonna<00:16:10.440> save<00:16:10.740> that<00:16:11.900> meta<00:16:12.900> Moss<00:16:13.080> again 00:16:14.050 --> 00:16:14.060 align:start position:0% so I'm gonna save that meta Moss again 00:16:14.060 --> 00:16:16.970 align:start position:0% so I'm gonna save that meta Moss again superfast<00:16:15.060> etherium<00:16:15.630> we're<00:16:16.020> in<00:16:16.200> subdomain 00:16:16.970 --> 00:16:16.980 align:start position:0% superfast etherium we're in subdomain 00:16:16.980 --> 00:16:19.790 align:start position:0% superfast etherium we're in subdomain created<00:16:17.520> and<00:16:17.900> I'm<00:16:18.900> gonna<00:16:19.020> click<00:16:19.200> on<00:16:19.260> this<00:16:19.590> now 00:16:19.790 --> 00:16:19.800 align:start position:0% created and I'm gonna click on this now 00:16:19.800 --> 00:16:23.650 align:start position:0% created and I'm gonna click on this now to<00:16:19.860> go<00:16:20.340> into<00:16:20.760> our<00:16:21.000> tip<00:16:21.330> jar<00:16:21.510> true<00:16:21.930> names<00:16:22.110> eath 00:16:23.650 --> 00:16:23.660 align:start position:0% to go into our tip jar true names eath 00:16:23.660 --> 00:16:26.990 align:start position:0% to go into our tip jar true names eath so<00:16:24.660> as<00:16:24.750> you<00:16:24.870> can<00:16:24.990> see<00:16:25.170> here<00:16:25.530> the<00:16:26.460> tip<00:16:26.820> jar 00:16:26.990 --> 00:16:27.000 align:start position:0% so as you can see here the tip jar 00:16:27.000 --> 00:16:29.330 align:start position:0% so as you can see here the tip jar subdomain<00:16:27.630> is<00:16:27.990> just<00:16:28.530> like<00:16:28.680> any<00:16:28.860> other<00:16:29.070> in<00:16:29.190> its 00:16:29.330 --> 00:16:29.340 align:start position:0% subdomain is just like any other in its 00:16:29.340 --> 00:16:31.070 align:start position:0% subdomain is just like any other in its name<00:16:29.610> it<00:16:29.940> has<00:16:30.090> all<00:16:30.300> the<00:16:30.420> functionality<00:16:31.050> of 00:16:31.070 --> 00:16:31.080 align:start position:0% name it has all the functionality of 00:16:31.080 --> 00:16:34.550 align:start position:0% name it has all the functionality of true<00:16:31.800> name<00:16:31.950> story--the<00:16:32.310> and<00:16:33.290> has<00:16:34.290> the<00:16:34.410> owner 00:16:34.550 --> 00:16:34.560 align:start position:0% true name story--the and has the owner 00:16:34.560 --> 00:16:37.310 align:start position:0% true name story--the and has the owner it<00:16:34.950> has<00:16:35.100> the<00:16:35.250> resolver<00:16:35.790> and<00:16:36.120> it<00:16:36.330> also<00:16:36.480> has<00:16:36.930> all 00:16:37.310 --> 00:16:37.320 align:start position:0% it has the resolver and it also has all 00:16:37.320 --> 00:16:39.530 align:start position:0% it has the resolver and it also has all the<00:16:37.380> record<00:16:37.680> fields<00:16:37.980> available<00:16:38.160> to<00:16:38.550> it<00:16:38.700> so<00:16:39.510> I 00:16:39.530 --> 00:16:39.540 align:start position:0% the record fields available to it so I 00:16:39.540 --> 00:16:40.910 align:start position:0% the record fields available to it so I could<00:16:39.780> do<00:16:39.900> the<00:16:40.020> same<00:16:40.170> thing<00:16:40.440> as<00:16:40.590> we<00:16:40.710> did<00:16:40.860> before 00:16:40.910 --> 00:16:40.920 align:start position:0% could do the same thing as we did before 00:16:40.920 --> 00:16:43.190 align:start position:0% could do the same thing as we did before I<00:16:41.130> could<00:16:41.370> set<00:16:41.490> up<00:16:41.520> the<00:16:41.670> puppet<00:16:41.820> resolver<00:16:42.390> save 00:16:43.190 --> 00:16:43.200 align:start position:0% I could set up the puppet resolver save 00:16:43.200 --> 00:16:46.460 align:start position:0% I could set up the puppet resolver save that<00:16:43.490> confirm<00:16:44.490> it<00:16:44.640> etc<00:16:44.760> and<00:16:45.300> that's<00:16:46.170> all<00:16:46.290> set 00:16:46.460 --> 00:16:46.470 align:start position:0% that confirm it etc and that's all set 00:16:46.470 --> 00:16:49.370 align:start position:0% that confirm it etc and that's all set up<00:16:46.590> nice<00:16:46.950> and<00:16:46.980> quickly<00:16:47.900> the<00:16:48.900> other<00:16:49.020> thing<00:16:49.230> we 00:16:49.370 --> 00:16:49.380 align:start position:0% up nice and quickly the other thing we 00:16:49.380 --> 00:16:51.920 align:start position:0% up nice and quickly the other thing we can<00:16:49.560> do<00:16:49.740> is<00:16:49.980> change<00:16:50.970> the<00:16:51.090> owner<00:16:51.270> so<00:16:51.660> your 00:16:51.920 --> 00:16:51.930 align:start position:0% can do is change the owner so your 00:16:51.930 --> 00:16:54.170 align:start position:0% can do is change the owner so your subdomains<00:16:52.200> don't<00:16:52.620> have<00:16:52.950> to<00:16:53.340> be<00:16:53.790> the<00:16:53.970> same 00:16:54.170 --> 00:16:54.180 align:start position:0% subdomains don't have to be the same 00:16:54.180 --> 00:16:56.630 align:start position:0% subdomains don't have to be the same owner<00:16:54.420> as<00:16:54.750> the<00:16:55.020> root<00:16:55.260> domain<00:16:55.530> and<00:16:55.770> so<00:16:56.400> we<00:16:56.520> can 00:16:56.630 --> 00:16:56.640 align:start position:0% owner as the root domain and so we can 00:16:56.640 --> 00:16:58.040 align:start position:0% owner as the root domain and so we can actually<00:16:56.730> transfer<00:16:57.150> this<00:16:57.300> to<00:16:57.450> say<00:16:57.600> a<00:16:57.630> family 00:16:58.040 --> 00:16:58.050 align:start position:0% actually transfer this to say a family 00:16:58.050 --> 00:17:00.260 align:start position:0% actually transfer this to say a family member<00:16:58.350> or<00:16:58.380> maybe<00:16:59.070> for<00:16:59.700> us<00:16:59.790> maybe<00:17:00.030> like<00:17:00.240> a 00:17:00.260 --> 00:17:00.270 align:start position:0% member or maybe for us maybe like a 00:17:00.270 --> 00:17:02.390 align:start position:0% member or maybe for us maybe like a multi-sig<00:17:00.900> wallet<00:17:01.200> for<00:17:01.530> the<00:17:01.920> true<00:17:02.190> names 00:17:02.390 --> 00:17:02.400 align:start position:0% multi-sig wallet for the true names 00:17:02.400 --> 00:17:04.340 align:start position:0% multi-sig wallet for the true names don't<00:17:02.670> eat<00:17:02.820> foundation<00:17:03.360> so<00:17:04.020> I'm<00:17:04.199> going<00:17:04.319> to 00:17:04.340 --> 00:17:04.350 align:start position:0% don't eat foundation so I'm going to 00:17:04.350 --> 00:17:07.030 align:start position:0% don't eat foundation so I'm going to show<00:17:04.500> you<00:17:04.530> that<00:17:04.709> now<00:17:04.920> I'm<00:17:05.310> just<00:17:05.430> gonna<00:17:05.579> copy<00:17:06.360> a 00:17:07.030 --> 00:17:07.040 align:start position:0% show you that now I'm just gonna copy a 00:17:07.040 --> 00:17:10.579 align:start position:0% show you that now I'm just gonna copy a address<00:17:08.040> I<00:17:08.189> saved<00:17:08.670> earlier<00:17:09.199> might<00:17:10.199> be<00:17:10.319> my<00:17:10.470> own 00:17:10.579 --> 00:17:10.589 align:start position:0% address I saved earlier might be my own 00:17:10.589 --> 00:17:15.050 align:start position:0% address I saved earlier might be my own address<00:17:11.540> and<00:17:13.160> paste<00:17:14.160> that<00:17:14.310> in<00:17:14.459> there<00:17:14.640> click 00:17:15.050 --> 00:17:15.060 align:start position:0% address and paste that in there click 00:17:15.060 --> 00:17:17.960 align:start position:0% address and paste that in there click transfer<00:17:16.069> confirm<00:17:17.069> that<00:17:17.189> transaction<00:17:17.730> as<00:17:17.850> you 00:17:17.960 --> 00:17:17.970 align:start position:0% transfer confirm that transaction as you 00:17:17.970 --> 00:17:20.210 align:start position:0% transfer confirm that transaction as you can<00:17:18.089> see<00:17:18.240> and<00:17:18.510> that<00:17:18.740> changes<00:17:19.740> the<00:17:19.800> owner 00:17:20.210 --> 00:17:20.220 align:start position:0% can see and that changes the owner 00:17:20.220 --> 00:17:24.530 align:start position:0% can see and that changes the owner address<00:17:20.550> the<00:17:21.510> one<00:17:21.630> I<00:17:21.660> just<00:17:21.930> pasted<00:17:22.670> so<00:17:23.670> that's 00:17:24.530 --> 00:17:24.540 align:start position:0% address the one I just pasted so that's 00:17:24.540 --> 00:17:26.179 align:start position:0% address the one I just pasted so that's pretty<00:17:24.689> much<00:17:24.810> it<00:17:24.990> for<00:17:25.020> the<00:17:25.500> basics<00:17:25.890> of<00:17:26.040> the 00:17:26.179 --> 00:17:26.189 align:start position:0% pretty much it for the basics of the 00:17:26.189 --> 00:17:30.170 align:start position:0% pretty much it for the basics of the enos<00:17:26.490> manager<00:17:27.650> we<00:17:28.650> also<00:17:28.800> have<00:17:29.130> added<00:17:29.280> in<00:17:29.640> some 00:17:30.170 --> 00:17:30.180 align:start position:0% enos manager we also have added in some 00:17:30.180 --> 00:17:31.880 align:start position:0% enos manager we also have added in some new<00:17:30.270> functionality<00:17:30.630> for<00:17:30.990> favoriting<00:17:31.440> so<00:17:31.680> if<00:17:31.800> I 00:17:31.880 --> 00:17:31.890 align:start position:0% new functionality for favoriting so if I 00:17:31.890 --> 00:17:33.630 align:start position:0% new functionality for favoriting so if I click<00:17:32.130> on<00:17:32.160> this<00:17:32.460> heart<00:17:32.670> button 00:17:33.630 --> 00:17:33.640 align:start position:0% click on this heart button 00:17:33.640 --> 00:17:36.480 align:start position:0% click on this heart button that<00:17:34.270> will<00:17:34.420> fill<00:17:34.900> it<00:17:34.990> up<00:17:35.080> and<00:17:35.350> I<00:17:35.710> can<00:17:36.040> go<00:17:36.190> to<00:17:36.250> the 00:17:36.480 --> 00:17:36.490 align:start position:0% that will fill it up and I can go to the 00:17:36.490 --> 00:17:38.970 align:start position:0% that will fill it up and I can go to the favourites<00:17:36.820> panel<00:17:37.120> and<00:17:37.450> that<00:17:37.960> shows<00:17:38.410> you 00:17:38.970 --> 00:17:38.980 align:start position:0% favourites panel and that shows you 00:17:38.980 --> 00:17:41.700 align:start position:0% favourites panel and that shows you we've<00:17:39.460> got<00:17:39.640> favoriting<00:17:40.180> abilities<00:17:40.570> to<00:17:40.930> save 00:17:41.700 --> 00:17:41.710 align:start position:0% we've got favoriting abilities to save 00:17:41.710 --> 00:17:43.320 align:start position:0% we've got favoriting abilities to save the<00:17:41.830> local<00:17:42.100> storage<00:17:42.340> your<00:17:42.790> domain<00:17:43.030> so<00:17:43.240> this 00:17:43.320 --> 00:17:43.330 align:start position:0% the local storage your domain so this 00:17:43.330 --> 00:17:44.910 align:start position:0% the local storage your domain so this makes<00:17:43.540> it<00:17:43.660> easier<00:17:43.960> for<00:17:44.050> you<00:17:44.290> if<00:17:44.530> you've<00:17:44.650> earned 00:17:44.910 --> 00:17:44.920 align:start position:0% makes it easier for you if you've earned 00:17:44.920 --> 00:17:47.190 align:start position:0% makes it easier for you if you've earned quite<00:17:45.280> a<00:17:45.370> few<00:17:45.550> domains<00:17:45.670> to<00:17:46.150> to<00:17:46.750> manage<00:17:47.050> them 00:17:47.190 --> 00:17:47.200 align:start position:0% quite a few domains to to manage them 00:17:47.200 --> 00:17:49.890 align:start position:0% quite a few domains to to manage them all<00:17:47.320> separately<00:17:47.770> and<00:17:48.610> I<00:17:48.700> can<00:17:48.880> get<00:17:49.630> rid<00:17:49.780> of<00:17:49.810> that 00:17:49.890 --> 00:17:49.900 align:start position:0% all separately and I can get rid of that 00:17:49.900 --> 00:17:53.270 align:start position:0% all separately and I can get rid of that heart<00:17:50.230> and<00:17:50.410> it<00:17:50.830> will<00:17:50.980> get<00:17:51.520> rid<00:17:51.550> of<00:17:51.670> my<00:17:51.820> favorite 00:17:53.270 --> 00:17:53.280 align:start position:0% heart and it will get rid of my favorite 00:17:53.280 --> 00:17:55.590 align:start position:0% heart and it will get rid of my favorite so<00:17:54.280> that's<00:17:54.430> all<00:17:54.550> the<00:17:54.640> functionality<00:17:55.270> for<00:17:55.480> the 00:17:55.590 --> 00:17:55.600 align:start position:0% so that's all the functionality for the 00:17:55.600 --> 00:17:57.030 align:start position:0% so that's all the functionality for the new<00:17:55.750> in<00:17:55.960> a<00:17:56.080> snap<00:17:56.320> there's<00:17:56.530> a<00:17:56.590> lot<00:17:56.710> of<00:17:56.800> things 00:17:57.030 --> 00:17:57.040 align:start position:0% new in a snap there's a lot of things 00:17:57.040 --> 00:18:00.300 align:start position:0% new in a snap there's a lot of things that<00:17:57.310> we<00:17:57.430> want<00:17:57.640> to<00:17:57.850> add<00:17:58.150> to<00:17:58.390> this<00:17:59.130> let<00:18:00.130> me<00:18:00.220> go 00:18:00.300 --> 00:18:00.310 align:start position:0% that we want to add to this let me go 00:18:00.310 --> 00:18:07.620 align:start position:0% that we want to add to this let me go back<00:18:00.460> to<00:18:00.520> the<00:18:00.820> presentation<00:18:01.690> so<00:18:04.650> present<00:18:06.630> so 00:18:07.620 --> 00:18:07.630 align:start position:0% back to the presentation so present so 00:18:07.630 --> 00:18:09.300 align:start position:0% back to the presentation so present so in<00:18:07.960> the<00:18:08.110> future<00:18:08.380> we<00:18:08.530> want<00:18:08.680> to<00:18:08.740> add<00:18:08.860> things<00:18:09.190> like 00:18:09.300 --> 00:18:09.310 align:start position:0% in the future we want to add things like 00:18:09.310 --> 00:18:11.190 align:start position:0% in the future we want to add things like reverse<00:18:10.000> record<00:18:10.330> support<00:18:10.570> which<00:18:10.930> will<00:18:11.080> bring 00:18:11.190 --> 00:18:11.200 align:start position:0% reverse record support which will bring 00:18:11.200 --> 00:18:12.960 align:start position:0% reverse record support which will bring up<00:18:11.350> up<00:18:11.680> to<00:18:11.920> feature<00:18:12.220> parity<00:18:12.400> for<00:18:12.670> the<00:18:12.820> old 00:18:12.960 --> 00:18:12.970 align:start position:0% up up to feature parity for the old 00:18:12.970 --> 00:18:15.420 align:start position:0% up up to feature parity for the old manager<00:18:13.330> we<00:18:13.930> want<00:18:14.110> to<00:18:14.170> be<00:18:14.260> able<00:18:14.380> to<00:18:14.530> like<00:18:15.220> Nick 00:18:15.420 --> 00:18:15.430 align:start position:0% manager we want to be able to like Nick 00:18:15.430 --> 00:18:17.820 align:start position:0% manager we want to be able to like Nick said<00:18:15.670> same<00:18:16.150> DNS<00:18:16.570> names<00:18:16.780> via<00:18:16.990> DNS<00:18:17.380> SEC<00:18:17.620> have 00:18:17.820 --> 00:18:17.830 align:start position:0% said same DNS names via DNS SEC have 00:18:17.830 --> 00:18:20.430 align:start position:0% said same DNS names via DNS SEC have that<00:18:17.950> integrated<00:18:18.490> into<00:18:18.820> the<00:18:19.000> DAP<00:18:19.440> auctions 00:18:20.430 --> 00:18:20.440 align:start position:0% that integrated into the DAP auctions 00:18:20.440 --> 00:18:23.090 align:start position:0% that integrated into the DAP auctions for<00:18:20.500> short<00:18:20.740> names<00:18:20.950> three<00:18:21.220> to<00:18:21.340> six<00:18:21.520> characters 00:18:23.090 --> 00:18:23.100 align:start position:0% for short names three to six characters 00:18:23.100 --> 00:18:25.260 align:start position:0% for short names three to six characters Department<00:18:24.100> of<00:18:24.160> registrar<00:18:24.520> support<00:18:24.940> so<00:18:25.180> the 00:18:25.260 --> 00:18:25.270 align:start position:0% Department of registrar support so the 00:18:25.270 --> 00:18:27.240 align:start position:0% Department of registrar support so the instant<00:18:25.570> by<00:18:25.720> ian<00:18:26.470> is<00:18:26.560> now<00:18:26.710> which<00:18:26.920> has<00:18:27.040> already 00:18:27.240 --> 00:18:27.250 align:start position:0% instant by ian is now which has already 00:18:27.250 --> 00:18:29.070 align:start position:0% instant by ian is now which has already hosted<00:18:27.820> an<00:18:28.090> outtie<00:18:28.270> nest<00:18:28.660> of<00:18:28.750> the<00:18:28.810> mains<00:18:28.990> but 00:18:29.070 --> 00:18:29.080 align:start position:0% hosted an outtie nest of the mains but 00:18:29.080 --> 00:18:30.060 align:start position:0% hosted an outtie nest of the mains but we<00:18:29.170> want<00:18:29.320> to<00:18:29.380> integrate<00:18:29.680> it<00:18:29.920> with<00:18:30.010> the 00:18:30.060 --> 00:18:30.070 align:start position:0% we want to integrate it with the 00:18:30.070 --> 00:18:32.010 align:start position:0% we want to integrate it with the original<00:18:30.220> app<00:18:30.550> and<00:18:30.970> also<00:18:31.270> advanced<00:18:31.780> features 00:18:32.010 --> 00:18:32.020 align:start position:0% original app and also advanced features 00:18:32.020 --> 00:18:34.080 align:start position:0% original app and also advanced features like<00:18:32.050> name<00:18:32.620> and<00:18:32.770> resolver<00:18:33.040> history<00:18:33.370> and<00:18:33.820> I'm 00:18:34.080 --> 00:18:34.090 align:start position:0% like name and resolver history and I'm 00:18:34.090 --> 00:18:35.940 align:start position:0% like name and resolver history and I'm going<00:18:34.240> to<00:18:34.300> hand<00:18:34.420> it<00:18:34.480> back<00:18:34.570> to<00:18:34.630> Nick<00:18:34.900> to<00:18:35.170> finish 00:18:35.940 --> 00:18:35.950 align:start position:0% going to hand it back to Nick to finish 00:18:35.950 --> 00:18:43.210 align:start position:0% going to hand it back to Nick to finish off<00:18:36.070> the<00:18:36.160> rest<00:18:36.220> of<00:18:36.520> the<00:18:36.580> presentation 00:18:43.210 --> 00:18:43.220 align:start position:0% 00:18:43.220 --> 00:18:47.799 align:start position:0% so<00:18:44.220> finally<00:18:44.820> to<00:18:44.940> wrap<00:18:45.090> up<00:18:45.299> what's<00:18:45.869> next<00:18:46.259> for<00:18:46.379> us 00:18:47.799 --> 00:18:47.809 align:start position:0% so finally to wrap up what's next for us 00:18:47.809 --> 00:18:50.600 align:start position:0% so finally to wrap up what's next for us obviously<00:18:48.809> we<00:18:49.019> need<00:18:49.230> our<00:18:49.739> top<00:18:49.980> priority<00:18:50.460> we 00:18:50.600 --> 00:18:50.610 align:start position:0% obviously we need our top priority we 00:18:50.610 --> 00:18:52.999 align:start position:0% obviously we need our top priority we want<00:18:50.789> to<00:18:50.909> finish<00:18:51.590> permanent<00:18:52.590> registrar 00:18:52.999 --> 00:18:53.009 align:start position:0% want to finish permanent registrar 00:18:53.009 --> 00:18:55.159 align:start position:0% want to finish permanent registrar design<00:18:53.309> and<00:18:53.489> implementation<00:18:53.970> our<00:18:54.720> goal<00:18:54.989> is 00:18:55.159 --> 00:18:55.169 align:start position:0% design and implementation our goal is 00:18:55.169 --> 00:18:57.169 align:start position:0% design and implementation our goal is still<00:18:55.259> to<00:18:55.409> get<00:18:55.590> this<00:18:55.739> rolled<00:18:56.009> out<00:18:56.190> in<00:18:56.489> May<00:18:56.999> next 00:18:57.169 --> 00:18:57.179 align:start position:0% still to get this rolled out in May next 00:18:57.179 --> 00:18:58.940 align:start position:0% still to get this rolled out in May next year<00:18:57.389> so<00:18:57.779> everyone<00:18:58.139> can<00:18:58.289> transition<00:18:58.619> to<00:18:58.799> a 00:18:58.940 --> 00:18:58.950 align:start position:0% year so everyone can transition to a 00:18:58.950 --> 00:19:00.950 align:start position:0% year so everyone can transition to a more<00:18:59.129> permanent<00:18:59.340> model<00:18:59.820> for<00:19:00.119> registration 00:19:00.950 --> 00:19:00.960 align:start position:0% more permanent model for registration 00:19:00.960 --> 00:19:02.989 align:start position:0% more permanent model for registration and<00:19:01.409> so<00:19:01.860> that<00:19:01.980> we<00:19:02.039> can<00:19:02.159> ease<00:19:02.249> the<00:19:02.279> registration 00:19:02.989 --> 00:19:02.999 align:start position:0% and so that we can ease the registration 00:19:02.999 --> 00:19:06.229 align:start position:0% and so that we can ease the registration process<00:19:03.389> for<00:19:03.419> new<00:19:03.659> users<00:19:04.639> we<00:19:05.639> want<00:19:05.879> to<00:19:06.090> of 00:19:06.229 --> 00:19:06.239 align:start position:0% process for new users we want to of 00:19:06.239 --> 00:19:07.759 align:start position:0% process for new users we want to of course<00:19:06.269> deploy<00:19:06.690> this<00:19:06.899> and<00:19:07.139> migrate<00:19:07.409> everyone 00:19:07.759 --> 00:19:07.769 align:start position:0% course deploy this and migrate everyone 00:19:07.769 --> 00:19:10.460 align:start position:0% course deploy this and migrate everyone over<00:19:08.360> we're<00:19:09.360> completing<00:19:09.779> work<00:19:09.989> on<00:19:10.200> the<00:19:10.320> new 00:19:10.460 --> 00:19:10.470 align:start position:0% over we're completing work on the new 00:19:10.470 --> 00:19:12.409 align:start position:0% over we're completing work on the new management<00:19:10.980> at<00:19:11.220> face<00:19:11.460> that<00:19:11.759> Jeff<00:19:11.940> just<00:19:12.149> showed 00:19:12.409 --> 00:19:12.419 align:start position:0% management at face that Jeff just showed 00:19:12.419 --> 00:19:14.509 align:start position:0% management at face that Jeff just showed us<00:19:12.570> and<00:19:12.840> of<00:19:13.230> course<00:19:13.440> this<00:19:13.619> is<00:19:13.739> the<00:19:13.889> ongoing 00:19:14.509 --> 00:19:14.519 align:start position:0% us and of course this is the ongoing 00:19:14.519 --> 00:19:17.330 align:start position:0% us and of course this is the ongoing outreach<00:19:14.669> our<00:19:15.320> biggest<00:19:16.320> ongoing<00:19:16.889> task<00:19:17.129> is 00:19:17.330 --> 00:19:17.340 align:start position:0% outreach our biggest ongoing task is 00:19:17.340 --> 00:19:19.129 align:start position:0% outreach our biggest ongoing task is always<00:19:17.609> going<00:19:17.789> to<00:19:17.879> be<00:19:17.999> making<00:19:18.600> sure<00:19:18.629> that 00:19:19.129 --> 00:19:19.139 align:start position:0% always going to be making sure that 00:19:19.139 --> 00:19:21.049 align:start position:0% always going to be making sure that Ian's<00:19:19.799> asus<00:19:20.070> is<00:19:20.100> widely<00:19:20.429> deployed<00:19:20.820> as 00:19:21.049 --> 00:19:21.059 align:start position:0% Ian's asus is widely deployed as 00:19:21.059 --> 00:19:22.820 align:start position:0% Ian's asus is widely deployed as possible<00:19:21.480> it's<00:19:21.600> as<00:19:21.749> useful<00:19:21.929> as<00:19:22.169> possible<00:19:22.200> and 00:19:22.820 --> 00:19:22.830 align:start position:0% possible it's as useful as possible and 00:19:22.830 --> 00:19:24.950 align:start position:0% possible it's as useful as possible and convincing<00:19:23.700> as<00:19:23.789> many<00:19:23.999> of<00:19:24.090> you<00:19:24.239> fine<00:19:24.480> folks<00:19:24.509> as 00:19:24.950 --> 00:19:24.960 align:start position:0% convincing as many of you fine folks as 00:19:24.960 --> 00:19:26.479 align:start position:0% convincing as many of you fine folks as possible<00:19:25.409> to<00:19:25.529> integrate<00:19:25.950> it<00:19:26.039> into<00:19:26.100> your<00:19:26.249> apps 00:19:26.479 --> 00:19:26.489 align:start position:0% possible to integrate it into your apps 00:19:26.489 --> 00:19:28.609 align:start position:0% possible to integrate it into your apps so<00:19:27.090> that's<00:19:27.539> it<00:19:27.720> for<00:19:27.840> today<00:19:28.049> thank<00:19:28.440> you<00:19:28.499> very 00:19:28.609 --> 00:19:28.619 align:start position:0% so that's it for today thank you very 00:19:28.619 --> 00:19:29.650 align:start position:0% so that's it for today thank you very much 00:19:29.650 --> 00:19:29.660 align:start position:0% much 00:19:29.660 --> 00:19:40.200 align:start position:0% much [Applause] 00:19:40.200 --> 00:19:40.210 align:start position:0% 00:19:40.210 --> 00:19:42.270 align:start position:0% you