WEBVTT Kind: captions Language: en 00:00:19.030 --> 00:00:22.000 align:start position:0% hi<00:00:20.030> there<00:00:20.240> my<00:00:20.870> name<00:00:21.050> as<00:00:21.320> you<00:00:21.350> already<00:00:21.619> know<00:00:21.860> is 00:00:22.000 --> 00:00:22.010 align:start position:0% hi there my name as you already know is 00:00:22.010 --> 00:00:23.350 align:start position:0% hi there my name as you already know is Nick<00:00:22.160> Johnson<00:00:22.520> I<00:00:22.760> work<00:00:22.940> for<00:00:23.150> the<00:00:23.210> foundation 00:00:23.350 --> 00:00:23.360 align:start position:0% Nick Johnson I work for the foundation 00:00:23.360 --> 00:00:26.200 align:start position:0% Nick Johnson I work for the foundation on<00:00:24.020> the<00:00:24.740> NGO<00:00:24.860> aetherium<00:00:25.189> team<00:00:25.520> and<00:00:25.760> on<00:00:25.880> Swarm 00:00:26.200 --> 00:00:26.210 align:start position:0% on the NGO aetherium team and on Swarm 00:00:26.210 --> 00:00:28.300 align:start position:0% on the NGO aetherium team and on Swarm and<00:00:26.450> I'm<00:00:27.170> here<00:00:27.350> to<00:00:27.439> talk<00:00:27.590> to<00:00:27.740> you<00:00:27.830> about<00:00:27.920> the 00:00:28.300 --> 00:00:28.310 align:start position:0% and I'm here to talk to you about the 00:00:28.310 --> 00:00:30.970 align:start position:0% and I'm here to talk to you about the ENS<00:00:28.880> the<00:00:29.150> etherium<00:00:29.570> name<00:00:29.750> service<00:00:30.170> can<00:00:30.829> I<00:00:30.860> have 00:00:30.970 --> 00:00:30.980 align:start position:0% ENS the etherium name service can I have 00:00:30.980 --> 00:00:33.760 align:start position:0% ENS the etherium name service can I have some<00:00:31.130> slides<00:00:31.750> excellent<00:00:32.750> I<00:00:32.870> don't<00:00:33.380> know<00:00:33.530> if<00:00:33.680> I 00:00:33.760 --> 00:00:33.770 align:start position:0% some slides excellent I don't know if I 00:00:33.770 --> 00:00:34.990 align:start position:0% some slides excellent I don't know if I can<00:00:33.920> recite<00:00:34.130> the<00:00:34.280> whole<00:00:34.370> thing<00:00:34.550> from<00:00:34.700> memory 00:00:34.990 --> 00:00:35.000 align:start position:0% can recite the whole thing from memory 00:00:35.000 --> 00:00:39.040 align:start position:0% can recite the whole thing from memory so<00:00:36.550> so<00:00:37.550> the<00:00:38.510> first<00:00:38.540> thing<00:00:38.900> you're<00:00:39.020> probably 00:00:39.040 --> 00:00:39.050 align:start position:0% so so the first thing you're probably 00:00:39.050 --> 00:00:41.170 align:start position:0% so so the first thing you're probably asking<00:00:39.530> is<00:00:39.950> why<00:00:40.220> do<00:00:40.280> we<00:00:40.489> need<00:00:40.670> another<00:00:40.700> name 00:00:41.170 --> 00:00:41.180 align:start position:0% asking is why do we need another name 00:00:41.180 --> 00:00:43.420 align:start position:0% asking is why do we need another name service<00:00:41.630> this<00:00:42.410> comic<00:00:42.739> is<00:00:42.860> probably<00:00:43.220> familiar 00:00:43.420 --> 00:00:43.430 align:start position:0% service this comic is probably familiar 00:00:43.430 --> 00:00:45.580 align:start position:0% service this comic is probably familiar to<00:00:43.790> a<00:00:43.820> significant<00:00:44.540> proportion<00:00:44.810> of<00:00:45.140> you<00:00:45.320> and 00:00:45.580 --> 00:00:45.590 align:start position:0% to a significant proportion of you and 00:00:45.590 --> 00:00:47.200 align:start position:0% to a significant proportion of you and first<00:00:46.280> of<00:00:46.430> all<00:00:46.489> why<00:00:46.670> do<00:00:46.730> we<00:00:46.880> need<00:00:47.030> a<00:00:47.060> name 00:00:47.200 --> 00:00:47.210 align:start position:0% first of all why do we need a name 00:00:47.210 --> 00:00:50.350 align:start position:0% first of all why do we need a name service<00:00:47.630> at<00:00:47.750> all<00:00:48.130> our<00:00:49.130> goal<00:00:49.400> is<00:00:49.640> to<00:00:49.670> be<00:00:49.970> able<00:00:50.090> to 00:00:50.350 --> 00:00:50.360 align:start position:0% service at all our goal is to be able to 00:00:50.360 --> 00:00:53.770 align:start position:0% service at all our goal is to be able to name<00:00:50.510> users<00:00:50.930> wallets<00:00:51.290> to<00:00:52.010> name<00:00:52.190> contracts<00:00:52.910> and 00:00:53.770 --> 00:00:53.780 align:start position:0% name users wallets to name contracts and 00:00:53.780 --> 00:00:55.750 align:start position:0% name users wallets to name contracts and to<00:00:53.960> name<00:00:54.170> resources<00:00:54.860> on<00:00:55.100> Swarm<00:00:55.460> and<00:00:55.640> IP 00:00:55.750 --> 00:00:55.760 align:start position:0% to name resources on Swarm and IP 00:00:55.760 --> 00:00:57.930 align:start position:0% to name resources on Swarm and IP affairs<00:00:56.210> and<00:00:56.480> as<00:00:56.960> denise<00:00:57.440> has<00:00:57.620> demonstrated 00:00:57.930 --> 00:00:57.940 align:start position:0% affairs and as denise has demonstrated 00:00:57.940 --> 00:01:01.090 align:start position:0% affairs and as denise has demonstrated there's<00:00:58.940> a<00:00:59.030> vast<00:00:59.240> number<00:00:59.600> of<00:00:59.630> other<00:01:00.070> uses<00:01:01.070> for 00:01:01.090 --> 00:01:01.100 align:start position:0% there's a vast number of other uses for 00:01:01.100 --> 00:01:03.970 align:start position:0% there's a vast number of other uses for a<00:01:01.370> good<00:01:01.670> and<00:01:01.940> robust<00:01:02.390> name<00:01:02.600> service<00:01:02.990> and<00:01:03.320> as 00:01:03.970 --> 00:01:03.980 align:start position:0% a good and robust name service and as 00:01:03.980 --> 00:01:05.890 align:start position:0% a good and robust name service and as for<00:01:04.220> why<00:01:04.309> we<00:01:04.460> need<00:01:04.489> another<00:01:04.850> one<00:01:05.030> if<00:01:05.720> you're 00:01:05.890 --> 00:01:05.900 align:start position:0% for why we need another one if you're 00:01:05.900 --> 00:01:07.240 align:start position:0% for why we need another one if you're familiar<00:01:06.020> with<00:01:06.259> name<00:01:06.590> reg<00:01:06.799> you'll<00:01:07.070> know<00:01:07.220> that 00:01:07.240 --> 00:01:07.250 align:start position:0% familiar with name reg you'll know that 00:01:07.250 --> 00:01:09.160 align:start position:0% familiar with name reg you'll know that this<00:01:07.610> isn't<00:01:07.909> the<00:01:08.000> first<00:01:08.150> name<00:01:08.450> service<00:01:08.900> on 00:01:09.160 --> 00:01:09.170 align:start position:0% this isn't the first name service on 00:01:09.170 --> 00:01:12.130 align:start position:0% this isn't the first name service on etherium<00:01:09.710> the<00:01:10.610> reason<00:01:10.939> is<00:01:11.060> that<00:01:11.090> the<00:01:11.540> existing 00:01:12.130 --> 00:01:12.140 align:start position:0% etherium the reason is that the existing 00:01:12.140 --> 00:01:14.200 align:start position:0% etherium the reason is that the existing name<00:01:12.560> services<00:01:13.100> are<00:01:13.280> paradoxically<00:01:13.970> quite 00:01:14.200 --> 00:01:14.210 align:start position:0% name services are paradoxically quite 00:01:14.210 --> 00:01:16.840 align:start position:0% name services are paradoxically quite centralized<00:01:14.810> they<00:01:15.740> have<00:01:15.890> a<00:01:15.920> single<00:01:16.369> central 00:01:16.840 --> 00:01:16.850 align:start position:0% centralized they have a single central 00:01:16.850 --> 00:01:18.490 align:start position:0% centralized they have a single central contract<00:01:17.299> there's<00:01:17.659> no<00:01:17.780> facility<00:01:18.049> for 00:01:18.490 --> 00:01:18.500 align:start position:0% contract there's no facility for 00:01:18.500 --> 00:01:20.620 align:start position:0% contract there's no facility for upgradability<00:01:19.220> there's<00:01:19.880> no<00:01:20.000> facility<00:01:20.450> for 00:01:20.620 --> 00:01:20.630 align:start position:0% upgradability there's no facility for 00:01:20.630 --> 00:01:22.899 align:start position:0% upgradability there's no facility for adding<00:01:20.930> new<00:01:20.960> record<00:01:21.470> types<00:01:21.740> in<00:01:21.950> the<00:01:22.040> future<00:01:22.370> so 00:01:22.899 --> 00:01:22.909 align:start position:0% adding new record types in the future so 00:01:22.909 --> 00:01:23.950 align:start position:0% adding new record types in the future so it's<00:01:23.060> useful<00:01:23.240> to<00:01:23.450> be<00:01:23.570> able<00:01:23.630> to<00:01:23.810> build 00:01:23.950 --> 00:01:23.960 align:start position:0% it's useful to be able to build 00:01:23.960 --> 00:01:25.510 align:start position:0% it's useful to be able to build something<00:01:24.260> that<00:01:24.440> well<00:01:24.770> still<00:01:25.130> being<00:01:25.370> as 00:01:25.510 --> 00:01:25.520 align:start position:0% something that well still being as 00:01:25.520 --> 00:01:27.340 align:start position:0% something that well still being as simple<00:01:25.820> as<00:01:25.909> possible<00:01:26.390> is<00:01:26.570> a<00:01:26.600> lot<00:01:26.780> more<00:01:26.930> robust 00:01:27.340 --> 00:01:27.350 align:start position:0% simple as possible is a lot more robust 00:01:27.350 --> 00:01:30.550 align:start position:0% simple as possible is a lot more robust and<00:01:27.620> a<00:01:27.800> lot<00:01:27.950> more<00:01:28.010> future<00:01:28.370> proof<00:01:29.260> so<00:01:30.260> what 00:01:30.550 --> 00:01:30.560 align:start position:0% and a lot more future proof so what 00:01:30.560 --> 00:01:32.680 align:start position:0% and a lot more future proof so what makes<00:01:30.740> a<00:01:30.830> good<00:01:30.950> name<00:01:31.159> service<00:01:31.600> separation<00:01:32.600> of 00:01:32.680 --> 00:01:32.690 align:start position:0% makes a good name service separation of 00:01:32.690 --> 00:01:35.170 align:start position:0% makes a good name service separation of concerns<00:01:32.979> there<00:01:33.979> are<00:01:34.130> three<00:01:34.670> separate<00:01:35.150> things 00:01:35.170 --> 00:01:35.180 align:start position:0% concerns there are three separate things 00:01:35.180 --> 00:01:37.600 align:start position:0% concerns there are three separate things three<00:01:36.080> separate<00:01:36.380> components<00:01:36.470> and<00:01:37.400> a<00:01:37.460> good 00:01:37.600 --> 00:01:37.610 align:start position:0% three separate components and a good 00:01:37.610 --> 00:01:40.120 align:start position:0% three separate components and a good name<00:01:37.790> service<00:01:38.210> at<00:01:38.390> least<00:01:38.540> in<00:01:38.720> my<00:01:38.840> mind<00:01:39.080> one<00:01:40.010> of 00:01:40.120 --> 00:01:40.130 align:start position:0% name service at least in my mind one of 00:01:40.130 --> 00:01:42.130 align:start position:0% name service at least in my mind one of them<00:01:40.340> is<00:01:40.520> the<00:01:41.180> actual<00:01:41.479> resolution<00:01:41.720> of<00:01:42.080> the 00:01:42.130 --> 00:01:42.140 align:start position:0% them is the actual resolution of the 00:01:42.140 --> 00:01:45.130 align:start position:0% them is the actual resolution of the names<00:01:42.350> one<00:01:43.220> of<00:01:43.250> them<00:01:43.520> is<00:01:43.729> the<00:01:44.000> updating<00:01:44.990> and 00:01:45.130 --> 00:01:45.140 align:start position:0% names one of them is the updating and 00:01:45.140 --> 00:01:46.780 align:start position:0% names one of them is the updating and the<00:01:45.200> registration<00:01:45.620> of<00:01:45.860> names<00:01:46.100> and<00:01:46.460> the<00:01:46.580> third 00:01:46.780 --> 00:01:46.790 align:start position:0% the registration of names and the third 00:01:46.790 --> 00:01:49.810 align:start position:0% the registration of names and the third one<00:01:47.030> is<00:01:47.470> registrar's<00:01:48.470> so<00:01:48.890> how<00:01:49.460> you<00:01:49.520> actually 00:01:49.810 --> 00:01:49.820 align:start position:0% one is registrar's so how you actually 00:01:49.820 --> 00:01:51.490 align:start position:0% one is registrar's so how you actually get<00:01:50.240> the<00:01:50.420> top-level<00:01:50.780> name<00:01:51.049> in<00:01:51.229> the<00:01:51.290> first 00:01:51.490 --> 00:01:51.500 align:start position:0% get the top-level name in the first 00:01:51.500 --> 00:01:53.320 align:start position:0% get the top-level name in the first place<00:01:51.740> where<00:01:52.100> you<00:01:52.280> would<00:01:52.430> go<00:01:52.610> to<00:01:52.640> you<00:01:53.210> know 00:01:53.320 --> 00:01:53.330 align:start position:0% place where you would go to you know 00:01:53.330 --> 00:01:56.080 align:start position:0% place where you would go to you know GoDaddy<00:01:53.780> or<00:01:54.110> Gandhi<00:01:54.830> or<00:01:55.130> whatever<00:01:55.490> on<00:01:55.640> the<00:01:55.760> DNS 00:01:56.080 --> 00:01:56.090 align:start position:0% GoDaddy or Gandhi or whatever on the DNS 00:01:56.090 --> 00:01:58.899 align:start position:0% GoDaddy or Gandhi or whatever on the DNS system<00:01:56.530> and<00:01:57.530> existing<00:01:57.950> systems<00:01:58.369> can<00:01:58.700> plate 00:01:58.899 --> 00:01:58.909 align:start position:0% system and existing systems can plate 00:01:58.909 --> 00:02:01.149 align:start position:0% system and existing systems can plate those<00:01:59.180> and<00:01:59.560> there's<00:02:00.560> the<00:02:00.860> matter<00:02:01.010> of 00:02:01.149 --> 00:02:01.159 align:start position:0% those and there's the matter of 00:02:01.159 --> 00:02:03.370 align:start position:0% those and there's the matter of distributed<00:02:02.090> Authority<00:02:02.570> and<00:02:02.750> implementation 00:02:03.370 --> 00:02:03.380 align:start position:0% distributed Authority and implementation 00:02:03.380 --> 00:02:05.680 align:start position:0% distributed Authority and implementation as<00:02:03.530> I<00:02:03.680> already<00:02:03.950> alluded<00:02:04.040> to<00:02:04.490> it<00:02:05.270> needs<00:02:05.510> to<00:02:05.630> be 00:02:05.680 --> 00:02:05.690 align:start position:0% as I already alluded to it needs to be 00:02:05.690 --> 00:02:07.990 align:start position:0% as I already alluded to it needs to be Ford<00:02:05.930> compatible<00:02:06.470> we<00:02:06.619> there<00:02:07.010> will<00:02:07.190> be<00:02:07.220> uses 00:02:07.990 --> 00:02:08.000 align:start position:0% Ford compatible we there will be uses 00:02:08.000 --> 00:02:09.430 align:start position:0% Ford compatible we there will be uses for<00:02:08.179> the<00:02:08.239> name<00:02:08.420> system<00:02:08.840> we<00:02:08.959> haven't<00:02:09.259> thought 00:02:09.430 --> 00:02:09.440 align:start position:0% for the name system we haven't thought 00:02:09.440 --> 00:02:12.130 align:start position:0% for the name system we haven't thought of<00:02:09.500> yet<00:02:09.939> and<00:02:10.939> it<00:02:11.150> needs<00:02:11.299> to<00:02:11.450> have<00:02:11.569> efficient<00:02:11.989> on 00:02:12.130 --> 00:02:12.140 align:start position:0% of yet and it needs to have efficient on 00:02:12.140 --> 00:02:14.619 align:start position:0% of yet and it needs to have efficient on chain<00:02:12.379> resolution<00:02:12.950> so<00:02:13.430> a<00:02:13.730> lot<00:02:14.390> of<00:02:14.510> the 00:02:14.619 --> 00:02:14.629 align:start position:0% chain resolution so a lot of the 00:02:14.629 --> 00:02:17.050 align:start position:0% chain resolution so a lot of the applications<00:02:14.750> are<00:02:15.620> in<00:02:15.769> depth<00:02:16.069> there<00:02:16.519> in<00:02:16.670> swarm 00:02:17.050 --> 00:02:17.060 align:start position:0% applications are in depth there in swarm 00:02:17.060 --> 00:02:19.270 align:start position:0% applications are in depth there in swarm and<00:02:17.420> browsers<00:02:18.110> but<00:02:18.620> it's<00:02:18.799> also<00:02:18.920> very<00:02:19.189> useful 00:02:19.270 --> 00:02:19.280 align:start position:0% and browsers but it's also very useful 00:02:19.280 --> 00:02:21.009 align:start position:0% and browsers but it's also very useful for<00:02:19.849> contracts<00:02:20.330> to<00:02:20.450> be<00:02:20.540> able<00:02:20.689> to<00:02:20.750> refer<00:02:20.989> to 00:02:21.009 --> 00:02:21.019 align:start position:0% for contracts to be able to refer to 00:02:21.019 --> 00:02:22.839 align:start position:0% for contracts to be able to refer to other<00:02:21.290> contracts<00:02:21.890> by<00:02:22.040> name<00:02:22.250> because<00:02:22.580> it<00:02:22.670> makes 00:02:22.839 --> 00:02:22.849 align:start position:0% other contracts by name because it makes 00:02:22.849 --> 00:02:26.140 align:start position:0% other contracts by name because it makes for<00:02:22.970> better<00:02:23.150> upgrade<00:02:23.330> ability<00:02:24.580> so<00:02:25.580> these<00:02:25.940> are 00:02:26.140 --> 00:02:26.150 align:start position:0% for better upgrade ability so these are 00:02:26.150 --> 00:02:28.520 align:start position:0% for better upgrade ability so these are the<00:02:26.300> three<00:02:26.660> main<00:02:26.840> components<00:02:27.020> of<00:02:27.470> the<00:02:27.590> ens 00:02:28.520 --> 00:02:28.530 align:start position:0% the three main components of the ens 00:02:28.530 --> 00:02:30.710 align:start position:0% the three main components of the ens we<00:02:28.710> have<00:02:28.950> the<00:02:29.160> ENS<00:02:29.580> registry<00:02:30.180> which<00:02:30.480> is<00:02:30.510> the 00:02:30.710 --> 00:02:30.720 align:start position:0% we have the ENS registry which is the 00:02:30.720 --> 00:02:33.830 align:start position:0% we have the ENS registry which is the centralized<00:02:31.200> contract<00:02:31.850> and<00:02:32.850> somebody's<00:02:33.600> skip 00:02:33.830 --> 00:02:33.840 align:start position:0% centralized contract and somebody's skip 00:02:33.840 --> 00:02:36.380 align:start position:0% centralized contract and somebody's skip to<00:02:33.930> hidden<00:02:34.110> my<00:02:34.230> slides<00:02:34.500> nevermind<00:02:35.390> the 00:02:36.380 --> 00:02:36.390 align:start position:0% to hidden my slides nevermind the 00:02:36.390 --> 00:02:38.750 align:start position:0% to hidden my slides nevermind the centralized<00:02:36.870> contract<00:02:37.410> which<00:02:37.710> contains<00:02:38.490> the 00:02:38.750 --> 00:02:38.760 align:start position:0% centralized contract which contains the 00:02:38.760 --> 00:02:41.210 align:start position:0% centralized contract which contains the entire<00:02:38.880> name<00:02:39.360> tree<00:02:39.720> it's<00:02:40.290> the<00:02:40.350> only<00:02:40.620> component 00:02:41.210 --> 00:02:41.220 align:start position:0% entire name tree it's the only component 00:02:41.220 --> 00:02:42.710 align:start position:0% entire name tree it's the only component to<00:02:41.280> the<00:02:41.370> system<00:02:41.730> that<00:02:41.850> isn't<00:02:42.030> upgradable 00:02:42.710 --> 00:02:42.720 align:start position:0% to the system that isn't upgradable 00:02:42.720 --> 00:02:44.840 align:start position:0% to the system that isn't upgradable because<00:02:43.050> it's<00:02:43.170> extremely<00:02:43.770> simple<00:02:44.040> and<00:02:44.340> its 00:02:44.840 --> 00:02:44.850 align:start position:0% because it's extremely simple and its 00:02:44.850 --> 00:02:46.580 align:start position:0% because it's extremely simple and its job<00:02:45.120> is<00:02:45.300> simply<00:02:45.540> to<00:02:45.630> map<00:02:45.900> from<00:02:45.930> the<00:02:46.230> name<00:02:46.410> you 00:02:46.580 --> 00:02:46.590 align:start position:0% job is simply to map from the name you 00:02:46.590 --> 00:02:50.480 align:start position:0% job is simply to map from the name you enter<00:02:46.920> into<00:02:47.160> the<00:02:48.380> the<00:02:49.380> resolver<00:02:49.980> so<00:02:50.400> the 00:02:50.480 --> 00:02:50.490 align:start position:0% enter into the the resolver so the 00:02:50.490 --> 00:02:51.970 align:start position:0% enter into the the resolver so the second<00:02:50.790> component<00:02:51.240> is<00:02:51.330> the<00:02:51.360> resolvers 00:02:51.970 --> 00:02:51.980 align:start position:0% second component is the resolvers 00:02:51.980 --> 00:02:54.470 align:start position:0% second component is the resolvers resolvers<00:02:52.980> can<00:02:53.190> be<00:02:53.310> written<00:02:53.640> by<00:02:53.880> individual 00:02:54.470 --> 00:02:54.480 align:start position:0% resolvers can be written by individual 00:02:54.480 --> 00:02:56.750 align:start position:0% resolvers can be written by individual users<00:02:54.840> or<00:02:55.050> you<00:02:55.170> can<00:02:55.350> use<00:02:55.500> a<00:02:55.530> premade<00:02:55.950> one<00:02:56.220> they 00:02:56.750 --> 00:02:56.760 align:start position:0% users or you can use a premade one they 00:02:56.760 --> 00:02:58.699 align:start position:0% users or you can use a premade one they can<00:02:56.940> use<00:02:57.090> any<00:02:57.300> system<00:02:57.720> they<00:02:57.870> like<00:02:58.080> and<00:02:58.350> they<00:02:58.500> go 00:02:58.699 --> 00:02:58.709 align:start position:0% can use any system they like and they go 00:02:58.709 --> 00:03:02.570 align:start position:0% can use any system they like and they go from<00:02:58.980> the<00:02:59.670> name<00:03:00.360> to<00:03:00.840> the<00:03:01.110> record<00:03:01.680> so<00:03:02.220> when<00:03:02.489> you 00:03:02.570 --> 00:03:02.580 align:start position:0% from the name to the record so when you 00:03:02.580 --> 00:03:04.040 align:start position:0% from the name to the record so when you do<00:03:02.700> a<00:03:02.730> name<00:03:02.940> lookup<00:03:03.239> first<00:03:03.570> you<00:03:03.720> ask<00:03:03.870> the 00:03:04.040 --> 00:03:04.050 align:start position:0% do a name lookup first you ask the 00:03:04.050 --> 00:03:06.920 align:start position:0% do a name lookup first you ask the registry<00:03:04.590> where<00:03:05.190> is<00:03:05.340> the<00:03:05.459> resolver<00:03:06.000> for<00:03:06.030> Nik 00:03:06.920 --> 00:03:06.930 align:start position:0% registry where is the resolver for Nik 00:03:06.930 --> 00:03:10.010 align:start position:0% registry where is the resolver for Nik death<00:03:07.350> and<00:03:07.650> then<00:03:08.250> you<00:03:08.430> ask<00:03:08.700> the<00:03:08.940> resolver<00:03:09.480> what 00:03:10.010 --> 00:03:10.020 align:start position:0% death and then you ask the resolver what 00:03:10.020 --> 00:03:13.100 align:start position:0% death and then you ask the resolver what is<00:03:10.200> the<00:03:10.470> address<00:03:11.040> of<00:03:11.280> Nik<00:03:11.580> Dottie's<00:03:12.110> so 00:03:13.100 --> 00:03:13.110 align:start position:0% is the address of Nik Dottie's so 00:03:13.110 --> 00:03:16.910 align:start position:0% is the address of Nik Dottie's so looking<00:03:13.709> at<00:03:13.800> the<00:03:13.890> registry<00:03:14.900> there<00:03:15.900> we<00:03:15.959> go<00:03:16.140> we 00:03:16.910 --> 00:03:16.920 align:start position:0% looking at the registry there we go we 00:03:16.920 --> 00:03:19.250 align:start position:0% looking at the registry there we go we conceptually<00:03:17.880> it's<00:03:18.209> structured<00:03:18.810> like<00:03:18.959> a<00:03:18.989> tree 00:03:19.250 --> 00:03:19.260 align:start position:0% conceptually it's structured like a tree 00:03:19.260 --> 00:03:20.900 align:start position:0% conceptually it's structured like a tree you<00:03:19.470> have<00:03:19.500> the<00:03:19.739> root<00:03:19.920> node<00:03:20.130> under<00:03:20.489> there<00:03:20.790> you 00:03:20.900 --> 00:03:20.910 align:start position:0% you have the root node under there you 00:03:20.910 --> 00:03:22.310 align:start position:0% you have the root node under there you have<00:03:21.030> all<00:03:21.060> the<00:03:21.239> top-level<00:03:21.570> domains<00:03:21.959> under 00:03:22.310 --> 00:03:22.320 align:start position:0% have all the top-level domains under 00:03:22.320 --> 00:03:23.990 align:start position:0% have all the top-level domains under that<00:03:22.530> you<00:03:22.680> have<00:03:22.830> all<00:03:22.950> the<00:03:23.070> users<00:03:23.400> domains<00:03:23.700> like 00:03:23.990 --> 00:03:24.000 align:start position:0% that you have all the users domains like 00:03:24.000 --> 00:03:25.370 align:start position:0% that you have all the users domains like Swati<00:03:24.540> Earth<00:03:24.720> Wallet<00:03:25.080> dotty 00:03:25.370 --> 00:03:25.380 align:start position:0% Swati Earth Wallet dotty 00:03:25.380 --> 00:03:27.979 align:start position:0% Swati Earth Wallet dotty and<00:03:25.709> so<00:03:25.890> on<00:03:26.040> it's<00:03:26.550> hierarchical<00:03:27.060> so<00:03:27.510> once<00:03:27.840> you 00:03:27.979 --> 00:03:27.989 align:start position:0% and so on it's hierarchical so once you 00:03:27.989 --> 00:03:29.630 align:start position:0% and so on it's hierarchical so once you own<00:03:28.110> a<00:03:28.140> name<00:03:28.440> you<00:03:28.680> can<00:03:28.800> create<00:03:29.040> names<00:03:29.370> under 00:03:29.630 --> 00:03:29.640 align:start position:0% own a name you can create names under 00:03:29.640 --> 00:03:33.050 align:start position:0% own a name you can create names under that<00:03:29.989> each<00:03:30.989> of<00:03:31.050> these<00:03:31.440> is<00:03:31.830> associated<00:03:32.670> with<00:03:32.700> a 00:03:33.050 --> 00:03:33.060 align:start position:0% that each of these is associated with a 00:03:33.060 --> 00:03:35.509 align:start position:0% that each of these is associated with a node<00:03:33.299> ID<00:03:33.510> and<00:03:33.870> the<00:03:34.170> node<00:03:34.350> ID<00:03:34.560> represents<00:03:35.370> the 00:03:35.509 --> 00:03:35.519 align:start position:0% node ID and the node ID represents the 00:03:35.519 --> 00:03:37.940 align:start position:0% node ID and the node ID represents the name<00:03:35.730> so<00:03:36.540> although<00:03:36.900> the<00:03:37.290> conceptual 00:03:37.940 --> 00:03:37.950 align:start position:0% name so although the conceptual 00:03:37.950 --> 00:03:41.270 align:start position:0% name so although the conceptual structure<00:03:38.400> here<00:03:38.640> is<00:03:38.670> a<00:03:39.480> tree<00:03:40.200> internally<00:03:41.190> it 00:03:41.270 --> 00:03:41.280 align:start position:0% structure here is a tree internally it 00:03:41.280 --> 00:03:43.220 align:start position:0% structure here is a tree internally it looks<00:03:41.459> quite<00:03:41.730> different<00:03:41.760> it's<00:03:42.600> actually<00:03:42.959> just 00:03:43.220 --> 00:03:43.230 align:start position:0% looks quite different it's actually just 00:03:43.230 --> 00:03:44.990 align:start position:0% looks quite different it's actually just a<00:03:43.440> big<00:03:43.560> lookup<00:03:43.890> table<00:03:44.250> which<00:03:44.370> is<00:03:44.519> why<00:03:44.670> it's 00:03:44.990 --> 00:03:45.000 align:start position:0% a big lookup table which is why it's 00:03:45.000 --> 00:03:46.940 align:start position:0% a big lookup table which is why it's such<00:03:45.209> a<00:03:45.269> simple<00:03:45.570> contract<00:03:46.170> and<00:03:46.380> why<00:03:46.560> we 00:03:46.940 --> 00:03:46.950 align:start position:0% such a simple contract and why we 00:03:46.950 --> 00:03:49.160 align:start position:0% such a simple contract and why we believe<00:03:47.400> that<00:03:47.790> we<00:03:48.090> can<00:03:48.269> deploy<00:03:48.510> it<00:03:48.750> without<00:03:48.989> a 00:03:49.160 --> 00:03:49.170 align:start position:0% believe that we can deploy it without a 00:03:49.170 --> 00:03:52.610 align:start position:0% believe that we can deploy it without a built-in<00:03:49.739> upgrade<00:03:50.100> facility<00:03:50.840> it<00:03:51.840> Maps<00:03:52.170> a<00:03:52.380> node 00:03:52.610 --> 00:03:52.620 align:start position:0% built-in upgrade facility it Maps a node 00:03:52.620 --> 00:03:55.550 align:start position:0% built-in upgrade facility it Maps a node number<00:03:53.280> which<00:03:53.610> represents<00:03:54.239> the<00:03:54.360> name<00:03:54.570> to<00:03:55.290> an 00:03:55.550 --> 00:03:55.560 align:start position:0% number which represents the name to an 00:03:55.560 --> 00:03:57.860 align:start position:0% number which represents the name to an owner<00:03:55.769> who<00:03:56.250> is<00:03:56.430> the<00:03:56.640> account<00:03:57.510> that<00:03:57.690> has<00:03:57.840> the 00:03:57.860 --> 00:03:57.870 align:start position:0% owner who is the account that has the 00:03:57.870 --> 00:04:00.080 align:start position:0% owner who is the account that has the right<00:03:58.079> to<00:03:58.260> update<00:03:58.590> the<00:03:58.709> name<00:03:58.890> and<00:03:59.160> a<00:03:59.519> resolver 00:04:00.080 --> 00:04:00.090 align:start position:0% right to update the name and a resolver 00:04:00.090 --> 00:04:02.720 align:start position:0% right to update the name and a resolver which<00:04:00.239> if<00:04:00.660> it<00:04:00.780> exists<00:04:01.230> turns<00:04:01.950> names<00:04:02.340> into 00:04:02.720 --> 00:04:02.730 align:start position:0% which if it exists turns names into 00:04:02.730 --> 00:04:06.620 align:start position:0% which if it exists turns names into values<00:04:03.920> you<00:04:04.920> might<00:04:05.070> be<00:04:05.220> wondering<00:04:05.400> how<00:04:05.850> the 00:04:06.620 --> 00:04:06.630 align:start position:0% values you might be wondering how the 00:04:06.630 --> 00:04:10.580 align:start position:0% values you might be wondering how the last<00:04:07.560> I<00:04:07.890> really<00:04:08.370> have<00:04:09.290> you<00:04:10.290> might<00:04:10.470> be 00:04:10.580 --> 00:04:10.590 align:start position:0% last I really have you might be 00:04:10.590 --> 00:04:14.680 align:start position:0% last I really have you might be wondering<00:04:10.799> how<00:04:11.790> you<00:04:11.820> go<00:04:12.209> from<00:04:12.570> a<00:04:12.959> name<00:04:13.860> to<00:04:14.310> a 00:04:14.680 --> 00:04:14.690 align:start position:0% wondering how you go from a name to a 00:04:14.690 --> 00:04:18.170 align:start position:0% wondering how you go from a name to a node<00:04:15.690> ID<00:04:16.100> this<00:04:17.100> is<00:04:17.250> using<00:04:17.430> a<00:04:17.579> system<00:04:17.940> called 00:04:18.170 --> 00:04:18.180 align:start position:0% node ID this is using a system called 00:04:18.180 --> 00:04:21.229 align:start position:0% node ID this is using a system called name<00:04:18.510> hash<00:04:18.950> what<00:04:19.950> we<00:04:20.040> do<00:04:20.190> first<00:04:20.489> is<00:04:20.790> you<00:04:20.940> break 00:04:21.229 --> 00:04:21.239 align:start position:0% name hash what we do first is you break 00:04:21.239 --> 00:04:22.909 align:start position:0% name hash what we do first is you break the<00:04:21.419> name<00:04:21.570> up<00:04:21.750> into<00:04:21.959> components<00:04:22.470> so<00:04:22.710> you<00:04:22.800> can 00:04:22.909 --> 00:04:22.919 align:start position:0% the name up into components so you can 00:04:22.919 --> 00:04:25.430 align:start position:0% the name up into components so you can see<00:04:23.100> there<00:04:23.280> we<00:04:23.400> head<00:04:23.610> Nick<00:04:24.210> wallet<00:04:24.750> Earth<00:04:25.110> has 00:04:25.430 --> 00:04:25.440 align:start position:0% see there we head Nick wallet Earth has 00:04:25.440 --> 00:04:27.080 align:start position:0% see there we head Nick wallet Earth has been<00:04:25.620> broken<00:04:25.860> up<00:04:26.010> into<00:04:26.190> three<00:04:26.430> components<00:04:26.910> you 00:04:27.080 --> 00:04:27.090 align:start position:0% been broken up into three components you 00:04:27.090 --> 00:04:29.480 align:start position:0% been broken up into three components you reverse<00:04:27.900> them<00:04:28.140> so<00:04:28.440> you<00:04:28.530> start<00:04:28.800> with<00:04:28.860> if<00:04:29.190> and 00:04:29.480 --> 00:04:29.490 align:start position:0% reverse them so you start with if and 00:04:29.490 --> 00:04:32.060 align:start position:0% reverse them so you start with if and you<00:04:30.030> char<00:04:30.900> three<00:04:31.140> hash<00:04:31.320> that<00:04:31.590> and<00:04:31.860> you<00:04:31.950> get 00:04:32.060 --> 00:04:32.070 align:start position:0% you char three hash that and you get 00:04:32.070 --> 00:04:36.469 align:start position:0% you char three hash that and you get that<00:04:32.220> first<00:04:32.490> value<00:04:33.169> here<00:04:34.729> then<00:04:35.729> you<00:04:36.000> take<00:04:36.240> that 00:04:36.469 --> 00:04:36.479 align:start position:0% that first value here then you take that 00:04:36.479 --> 00:04:39.020 align:start position:0% that first value here then you take that and<00:04:36.750> you<00:04:36.810> shower<00:04:37.140> through<00:04:37.440> it<00:04:37.560> with<00:04:38.030> zero 00:04:39.020 --> 00:04:39.030 align:start position:0% and you shower through it with zero 00:04:39.030 --> 00:04:41.360 align:start position:0% and you shower through it with zero which<00:04:39.330> is<00:04:39.510> the<00:04:39.660> root<00:04:39.990> node<00:04:40.229> and<00:04:40.500> you<00:04:41.130> take<00:04:41.340> that 00:04:41.360 --> 00:04:41.370 align:start position:0% which is the root node and you take that 00:04:41.370 --> 00:04:42.140 align:start position:0% which is the root node and you take that and<00:04:41.760> you 00:04:42.140 --> 00:04:42.150 align:start position:0% and you 00:04:42.150 --> 00:04:43.670 align:start position:0% and you that<00:04:42.300> and<00:04:42.630> you<00:04:42.720> do<00:04:42.840> the<00:04:42.930> whole<00:04:43.080> operation<00:04:43.560> all 00:04:43.670 --> 00:04:43.680 align:start position:0% that and you do the whole operation all 00:04:43.680 --> 00:04:46.220 align:start position:0% that and you do the whole operation all over<00:04:43.920> again<00:04:44.010> you<00:04:44.400> feed<00:04:44.850> us<00:04:44.880> in<00:04:45.180> as<00:04:45.330> the<00:04:45.570> as<00:04:45.960> the 00:04:46.220 --> 00:04:46.230 align:start position:0% over again you feed us in as the as the 00:04:46.230 --> 00:04:48.440 align:start position:0% over again you feed us in as the as the parent<00:04:46.560> node<00:04:46.740> you<00:04:47.040> share<00:04:47.280> three<00:04:47.520> wallet<00:04:47.850> you 00:04:48.440 --> 00:04:48.450 align:start position:0% parent node you share three wallet you 00:04:48.450 --> 00:04:50.180 align:start position:0% parent node you share three wallet you put<00:04:48.660> it<00:04:48.750> into<00:04:48.900> the<00:04:48.990> next<00:04:49.200> one<00:04:49.440> you<00:04:49.800> shower 00:04:50.180 --> 00:04:50.190 align:start position:0% put it into the next one you shower 00:04:50.190 --> 00:04:52.130 align:start position:0% put it into the next one you shower through<00:04:50.430> that<00:04:50.610> with<00:04:50.790> NICU<00:04:51.270> feeds<00:04:51.810> into<00:04:51.990> the 00:04:52.130 --> 00:04:52.140 align:start position:0% through that with NICU feeds into the 00:04:52.140 --> 00:04:54.590 align:start position:0% through that with NICU feeds into the next<00:04:52.230> one<00:04:52.530> and<00:04:52.710> what<00:04:52.860> you<00:04:52.950> get<00:04:53.130> out<00:04:53.370> if<00:04:53.910> I<00:04:54.420> can 00:04:54.590 --> 00:04:54.600 align:start position:0% next one and what you get out if I can 00:04:54.600 --> 00:05:03.050 align:start position:0% next one and what you get out if I can make<00:04:54.750> my<00:04:54.900> slides<00:04:55.200> work<00:05:00.050> is<00:05:01.310> the<00:05:02.310> final<00:05:02.640> note<00:05:02.820> - 00:05:03.050 --> 00:05:03.060 align:start position:0% make my slides work is the final note - 00:05:03.060 --> 00:05:05.630 align:start position:0% make my slides work is the final note - the<00:05:03.750> purpose<00:05:04.080> of<00:05:04.200> all<00:05:04.320> of<00:05:04.470> us<00:05:04.640> convoluted 00:05:05.630 --> 00:05:05.640 align:start position:0% the purpose of all of us convoluted 00:05:05.640 --> 00:05:07.340 align:start position:0% the purpose of all of us convoluted though<00:05:05.730> it<00:05:05.820> may<00:05:05.940> seem<00:05:06.240> is<00:05:06.480> that<00:05:06.960> you<00:05:07.020> can<00:05:07.200> look 00:05:07.340 --> 00:05:07.350 align:start position:0% though it may seem is that you can look 00:05:07.350 --> 00:05:10.040 align:start position:0% though it may seem is that you can look up<00:05:07.500> a<00:05:07.530> no-name<00:05:08.490> of<00:05:08.790> arbitrary<00:05:09.240> dips<00:05:09.450> you<00:05:09.600> food 00:05:10.040 --> 00:05:10.050 align:start position:0% up a no-name of arbitrary dips you food 00:05:10.050 --> 00:05:13.010 align:start position:0% up a no-name of arbitrary dips you food Bardot<00:05:10.500> pears<00:05:10.740> quack<00:05:11.310> studies<00:05:11.910> in<00:05:12.210> a<00:05:12.690> single 00:05:13.010 --> 00:05:13.020 align:start position:0% Bardot pears quack studies in a single 00:05:13.020 --> 00:05:15.860 align:start position:0% Bardot pears quack studies in a single lookup<00:05:13.290> operation<00:05:13.860> and<00:05:14.070> yet<00:05:14.610> the<00:05:14.870> registry 00:05:15.860 --> 00:05:15.870 align:start position:0% lookup operation and yet the registry 00:05:15.870 --> 00:05:17.480 align:start position:0% lookup operation and yet the registry contract<00:05:16.350> can<00:05:16.590> still<00:05:16.830> deter<00:05:17.070> answer 00:05:17.480 --> 00:05:17.490 align:start position:0% contract can still deter answer 00:05:17.490 --> 00:05:19.760 align:start position:0% contract can still deter answer questions<00:05:17.940> like<00:05:18.180> does<00:05:18.720> this<00:05:18.930> person<00:05:19.380> own<00:05:19.560> the 00:05:19.760 --> 00:05:19.770 align:start position:0% questions like does this person own the 00:05:19.770 --> 00:05:21.800 align:start position:0% questions like does this person own the parent<00:05:20.100> name<00:05:20.280> for<00:05:20.640> this<00:05:20.760> name<00:05:21.000> and<00:05:21.360> so<00:05:21.510> forth 00:05:21.800 --> 00:05:21.810 align:start position:0% parent name for this name and so forth 00:05:21.810 --> 00:05:23.870 align:start position:0% parent name for this name and so forth which<00:05:22.290> allows<00:05:22.590> the<00:05:22.890> distributed<00:05:23.460> Authority 00:05:23.870 --> 00:05:23.880 align:start position:0% which allows the distributed Authority 00:05:23.880 --> 00:05:27.320 align:start position:0% which allows the distributed Authority and<00:05:24.060> allows<00:05:24.330> assignment<00:05:24.960> of<00:05:25.050> authority<00:05:26.330> so 00:05:27.320 --> 00:05:27.330 align:start position:0% and allows assignment of authority so 00:05:27.330 --> 00:05:29.300 align:start position:0% and allows assignment of authority so the<00:05:27.450> next<00:05:27.630> component<00:05:27.960> of<00:05:28.200> ENS<00:05:28.560> is<00:05:28.830> the 00:05:29.300 --> 00:05:29.310 align:start position:0% the next component of ENS is the 00:05:29.310 --> 00:05:32.060 align:start position:0% the next component of ENS is the resolvers<00:05:30.350> resolvers<00:05:31.350> can<00:05:31.560> be<00:05:31.650> written<00:05:31.950> by 00:05:32.060 --> 00:05:32.070 align:start position:0% resolvers resolvers can be written by 00:05:32.070 --> 00:05:34.370 align:start position:0% resolvers resolvers can be written by individual<00:05:32.550> users<00:05:32.910> they<00:05:33.660> can<00:05:33.690> be<00:05:33.900> extremely 00:05:34.370 --> 00:05:34.380 align:start position:0% individual users they can be extremely 00:05:34.380 --> 00:05:35.480 align:start position:0% individual users they can be extremely simple<00:05:34.530> or<00:05:34.860> they<00:05:34.950> can<00:05:35.070> be<00:05:35.160> very<00:05:35.250> sophisticated 00:05:35.480 --> 00:05:35.490 align:start position:0% simple or they can be very sophisticated 00:05:35.490 --> 00:05:38.840 align:start position:0% simple or they can be very sophisticated they're<00:05:36.270> an<00:05:36.630> extremely<00:05:37.230> simple<00:05:37.850> resolver 00:05:38.840 --> 00:05:38.850 align:start position:0% they're an extremely simple resolver 00:05:38.850 --> 00:05:40.670 align:start position:0% they're an extremely simple resolver here<00:05:39.060> that<00:05:39.420> is<00:05:39.600> owned<00:05:39.840> by<00:05:39.990> a<00:05:40.140> particular<00:05:40.440> user 00:05:40.670 --> 00:05:40.680 align:start position:0% here that is owned by a particular user 00:05:40.680 --> 00:05:43.010 align:start position:0% here that is owned by a particular user and<00:05:40.980> only<00:05:41.460> registers<00:05:41.970> names<00:05:42.210> for<00:05:42.540> them<00:05:42.660> is 00:05:43.010 --> 00:05:43.020 align:start position:0% and only registers names for them is 00:05:43.020 --> 00:05:46.160 align:start position:0% and only registers names for them is here<00:05:43.470> it<00:05:44.310> has<00:05:44.490> three<00:05:44.760> main<00:05:44.790> functions<00:05:45.420> has 00:05:46.160 --> 00:05:46.170 align:start position:0% here it has three main functions has 00:05:46.170 --> 00:05:49.100 align:start position:0% here it has three main functions has answers<00:05:47.130> the<00:05:47.250> question<00:05:47.700> do<00:05:48.330> you<00:05:48.510> know<00:05:48.720> the 00:05:49.100 --> 00:05:49.110 align:start position:0% answers the question do you know the 00:05:49.110 --> 00:05:51.080 align:start position:0% answers the question do you know the answer<00:05:49.470> to<00:05:49.500> this<00:05:49.710> particular<00:05:49.860> question<00:05:50.220> so<00:05:51.000> in 00:05:51.080 --> 00:05:51.090 align:start position:0% answer to this particular question so in 00:05:51.090 --> 00:05:52.820 align:start position:0% answer to this particular question so in this<00:05:51.210> case<00:05:51.450> it<00:05:51.600> only<00:05:51.630> supports<00:05:52.110> address 00:05:52.820 --> 00:05:52.830 align:start position:0% this case it only supports address 00:05:52.830 --> 00:05:54.770 align:start position:0% this case it only supports address records<00:05:53.340> and<00:05:53.580> it<00:05:53.940> only<00:05:54.060> supports<00:05:54.510> the<00:05:54.630> ones 00:05:54.770 --> 00:05:54.780 align:start position:0% records and it only supports the ones 00:05:54.780 --> 00:05:56.480 align:start position:0% records and it only supports the ones that<00:05:54.960> have<00:05:55.050> been<00:05:55.110> added<00:05:55.410> to<00:05:55.440> it<00:05:55.590> and<00:05:55.890> if<00:05:56.190> it<00:05:56.310> has 00:05:56.480 --> 00:05:56.490 align:start position:0% that have been added to it and if it has 00:05:56.490 --> 00:05:59.390 align:start position:0% that have been added to it and if it has it<00:05:56.700> returns<00:05:57.000> true<00:05:57.500> the<00:05:58.500> second<00:05:58.830> function<00:05:59.010> is 00:05:59.390 --> 00:05:59.400 align:start position:0% it returns true the second function is 00:05:59.400 --> 00:06:00.860 align:start position:0% it returns true the second function is the<00:05:59.550> one<00:05:59.700> that<00:05:59.850> everyone<00:06:00.180> trying<00:06:00.540> to<00:06:00.660> resolve 00:06:00.860 --> 00:06:00.870 align:start position:0% the one that everyone trying to resolve 00:06:00.870 --> 00:06:03.710 align:start position:0% the one that everyone trying to resolve names<00:06:01.170> calls<00:06:01.590> its<00:06:02.310> error<00:06:02.580> so<00:06:03.060> you<00:06:03.090> pass<00:06:03.390> in<00:06:03.630> the 00:06:03.710 --> 00:06:03.720 align:start position:0% names calls its error so you pass in the 00:06:03.720 --> 00:06:05.180 align:start position:0% names calls its error so you pass in the node<00:06:03.900> which<00:06:04.170> again<00:06:04.410> is<00:06:04.560> the<00:06:04.680> value<00:06:04.950> of<00:06:04.980> this 00:06:05.180 --> 00:06:05.190 align:start position:0% node which again is the value of this 00:06:05.190 --> 00:06:07.820 align:start position:0% node which again is the value of this operation<00:06:05.580> previously<00:06:06.360> if<00:06:07.110> it<00:06:07.260> has<00:06:07.440> it<00:06:07.620> it 00:06:07.820 --> 00:06:07.830 align:start position:0% operation previously if it has it it 00:06:07.830 --> 00:06:09.590 align:start position:0% operation previously if it has it it returns<00:06:08.190> it<00:06:08.400> if<00:06:08.580> it<00:06:08.700> doesn't<00:06:09.060> throw<00:06:09.450> as<00:06:09.510> an 00:06:09.590 --> 00:06:09.600 align:start position:0% returns it if it doesn't throw as an 00:06:09.600 --> 00:06:11.780 align:start position:0% returns it if it doesn't throw as an exception<00:06:10.080> and<00:06:10.370> finally<00:06:11.370> you<00:06:11.550> have<00:06:11.670> the 00:06:11.780 --> 00:06:11.790 align:start position:0% exception and finally you have the 00:06:11.790 --> 00:06:13.490 align:start position:0% exception and finally you have the function<00:06:12.210> that<00:06:12.240> this<00:06:12.690> is<00:06:12.840> not<00:06:13.020> part<00:06:13.260> of<00:06:13.380> the 00:06:13.490 --> 00:06:13.500 align:start position:0% function that this is not part of the 00:06:13.500 --> 00:06:16.100 align:start position:0% function that this is not part of the spec<00:06:13.770> it's<00:06:14.010> part<00:06:14.280> of<00:06:14.460> the<00:06:15.240> interface<00:06:15.900> of<00:06:16.080> your 00:06:16.100 --> 00:06:16.110 align:start position:0% spec it's part of the interface of your 00:06:16.110 --> 00:06:18.110 align:start position:0% spec it's part of the interface of your individual<00:06:16.590> resolver<00:06:17.070> which<00:06:17.550> is<00:06:17.730> set<00:06:17.910> error 00:06:18.110 --> 00:06:18.120 align:start position:0% individual resolver which is set error 00:06:18.120 --> 00:06:19.610 align:start position:0% individual resolver which is set error which<00:06:18.450> leads<00:06:18.660> the<00:06:18.780> owner<00:06:19.050> set<00:06:19.290> the<00:06:19.440> address 00:06:19.610 --> 00:06:19.620 align:start position:0% which leads the owner set the address 00:06:19.620 --> 00:06:21.830 align:start position:0% which leads the owner set the address and<00:06:20.070> as<00:06:20.820> you<00:06:20.940> can<00:06:21.090> see<00:06:21.210> it's<00:06:21.330> an<00:06:21.390> extremely 00:06:21.830 --> 00:06:21.840 align:start position:0% and as you can see it's an extremely 00:06:21.840 --> 00:06:23.420 align:start position:0% and as you can see it's an extremely simple<00:06:21.990> contract<00:06:22.560> and<00:06:22.770> that<00:06:22.860> is<00:06:23.010> the<00:06:23.130> entirety 00:06:23.420 --> 00:06:23.430 align:start position:0% simple contract and that is the entirety 00:06:23.430 --> 00:06:27.800 align:start position:0% simple contract and that is the entirety of<00:06:23.820> a<00:06:24.600> fully<00:06:25.380> functional<00:06:25.890> resolver<00:06:26.810> finally 00:06:27.800 --> 00:06:27.810 align:start position:0% of a fully functional resolver finally 00:06:27.810 --> 00:06:29.210 align:start position:0% of a fully functional resolver finally the<00:06:27.990> third<00:06:28.170> component<00:06:28.470> of<00:06:28.680> ENS<00:06:28.980> is<00:06:29.130> the 00:06:29.210 --> 00:06:29.220 align:start position:0% the third component of ENS is the 00:06:29.220 --> 00:06:31.670 align:start position:0% the third component of ENS is the registrar's<00:06:29.930> registrar's<00:06:30.930> are<00:06:31.110> the<00:06:31.230> owners 00:06:31.670 --> 00:06:31.680 align:start position:0% registrar's registrar's are the owners 00:06:31.680 --> 00:06:35.090 align:start position:0% registrar's registrar's are the owners in<00:06:31.950> the<00:06:32.070> ENS<00:06:32.760> registry<00:06:33.330> and<00:06:34.320> their<00:06:34.560> job<00:06:34.800> is<00:06:35.070> to 00:06:35.090 --> 00:06:35.100 align:start position:0% in the ENS registry and their job is to 00:06:35.100 --> 00:06:37.820 align:start position:0% in the ENS registry and their job is to assign<00:06:35.580> names<00:06:35.820> to<00:06:36.000> people<00:06:36.360> with<00:06:37.290> the<00:06:37.470> simplest 00:06:37.820 --> 00:06:37.830 align:start position:0% assign names to people with the simplest 00:06:37.830 --> 00:06:40.400 align:start position:0% assign names to people with the simplest possible<00:06:38.070> registrar<00:06:38.790> is<00:06:39.030> me<00:06:39.360> I<00:06:39.600> can<00:06:40.020> actually 00:06:40.400 --> 00:06:40.410 align:start position:0% possible registrar is me I can actually 00:06:40.410 --> 00:06:42.680 align:start position:0% possible registrar is me I can actually own<00:06:40.620> it<00:06:40.650> own<00:06:41.400> a<00:06:41.460> domain<00:06:41.670> using<00:06:42.090> my<00:06:42.330> external 00:06:42.680 --> 00:06:42.690 align:start position:0% own it own a domain using my external 00:06:42.690 --> 00:06:44.810 align:start position:0% own it own a domain using my external address<00:06:42.900> if<00:06:43.230> you<00:06:43.380> come<00:06:43.530> up<00:06:43.560> to<00:06:43.800> me<00:06:43.920> I<00:06:44.160> can<00:06:44.670> give 00:06:44.810 --> 00:06:44.820 align:start position:0% address if you come up to me I can give 00:06:44.820 --> 00:06:47.510 align:start position:0% address if you come up to me I can give you<00:06:45.030> a<00:06:45.060> sub<00:06:45.510> name<00:06:45.720> no<00:06:46.710> contracts<00:06:47.160> need<00:06:47.400> be 00:06:47.510 --> 00:06:47.520 align:start position:0% you a sub name no contracts need be 00:06:47.520 --> 00:06:50.300 align:start position:0% you a sub name no contracts need be involved<00:06:48.030> but<00:06:48.630> for<00:06:48.870> top-level<00:06:49.200> names<00:06:49.530> it's 00:06:50.300 --> 00:06:50.310 align:start position:0% involved but for top-level names it's 00:06:50.310 --> 00:06:52.580 align:start position:0% involved but for top-level names it's helpful<00:06:50.700> to<00:06:50.940> have<00:06:51.300> a<00:06:51.570> smart<00:06:51.810> contract<00:06:52.290> because 00:06:52.580 --> 00:06:52.590 align:start position:0% helpful to have a smart contract because 00:06:52.590 --> 00:06:54.740 align:start position:0% helpful to have a smart contract because it's<00:06:53.070> automated<00:06:53.460> and<00:06:53.880> it<00:06:54.000> ensures<00:06:54.270> fairness 00:06:54.740 --> 00:06:54.750 align:start position:0% it's automated and it ensures fairness 00:06:54.750 --> 00:06:56.390 align:start position:0% it's automated and it ensures fairness and<00:06:54.960> everyone<00:06:55.290> knows<00:06:55.500> what<00:06:55.740> the<00:06:55.830> registration 00:06:56.390 --> 00:06:56.400 align:start position:0% and everyone knows what the registration 00:06:56.400 --> 00:06:58.370 align:start position:0% and everyone knows what the registration rules<00:06:56.610> are<00:06:56.790> and<00:06:57.060> more<00:06:57.570> importantly<00:06:57.990> everyone 00:06:58.370 --> 00:06:58.380 align:start position:0% rules are and more importantly everyone 00:06:58.380 --> 00:07:00.290 align:start position:0% rules are and more importantly everyone knows<00:06:58.650> that<00:06:59.040> I<00:06:59.250> won't<00:06:59.699> come<00:06:59.880> along<00:07:00.150> and 00:07:00.290 --> 00:07:00.300 align:start position:0% knows that I won't come along and 00:07:00.300 --> 00:07:02.240 align:start position:0% knows that I won't come along and Abbot's<00:07:00.630> really<00:07:00.900> decide<00:07:01.229> actually<00:07:01.740> I<00:07:01.770> really 00:07:02.240 --> 00:07:02.250 align:start position:0% Abbot's really decide actually I really 00:07:02.250 --> 00:07:03.140 align:start position:0% Abbot's really decide actually I really want<00:07:02.430> toaster<00:07:02.880> dotty 00:07:03.140 --> 00:07:03.150 align:start position:0% want toaster dotty 00:07:03.150 --> 00:07:05.840 align:start position:0% want toaster dotty I'm<00:07:03.419> gonna<00:07:03.540> take<00:07:03.750> it<00:07:03.780> back<00:07:04.020> off<00:07:04.169> you<00:07:04.520> so<00:07:05.520> the 00:07:05.840 --> 00:07:05.850 align:start position:0% I'm gonna take it back off you so the 00:07:05.850 --> 00:07:07.939 align:start position:0% I'm gonna take it back off you so the registrar<00:07:06.360> is<00:07:06.570> similarly<00:07:07.110> simple<00:07:07.560> this<00:07:07.770> is<00:07:07.830> a 00:07:07.939 --> 00:07:07.949 align:start position:0% registrar is similarly simple this is a 00:07:07.949 --> 00:07:09.710 align:start position:0% registrar is similarly simple this is a really<00:07:08.250> simple<00:07:08.430> registrar<00:07:09.090> that<00:07:09.120> replicates 00:07:09.710 --> 00:07:09.720 align:start position:0% really simple registrar that replicates 00:07:09.720 --> 00:07:11.360 align:start position:0% really simple registrar that replicates more<00:07:10.110> or<00:07:10.199> less<00:07:10.320> functionality<00:07:10.889> of<00:07:11.250> the 00:07:11.360 --> 00:07:11.370 align:start position:0% more or less functionality of the 00:07:11.370 --> 00:07:13.850 align:start position:0% more or less functionality of the existing<00:07:11.789> name<00:07:11.970> Ridge<00:07:12.229> the<00:07:13.229> first<00:07:13.470> person<00:07:13.830> to 00:07:13.850 --> 00:07:13.860 align:start position:0% existing name Ridge the first person to 00:07:13.860 --> 00:07:16.370 align:start position:0% existing name Ridge the first person to ask<00:07:14.070> for<00:07:14.310> a<00:07:14.400> name<00:07:14.580> gets<00:07:14.880> it<00:07:15.090> if<00:07:15.990> they<00:07:16.169> already 00:07:16.370 --> 00:07:16.380 align:start position:0% ask for a name gets it if they already 00:07:16.380 --> 00:07:17.689 align:start position:0% ask for a name gets it if they already own<00:07:16.590> the<00:07:16.710> name<00:07:16.860> they<00:07:17.130> can<00:07:17.280> assign<00:07:17.490> it<00:07:17.669> to 00:07:17.689 --> 00:07:17.699 align:start position:0% own the name they can assign it to 00:07:17.699 --> 00:07:20.240 align:start position:0% own the name they can assign it to someone<00:07:17.970> else<00:07:18.210> and<00:07:19.139> all<00:07:19.320> it<00:07:19.440> does<00:07:19.590> here<00:07:19.860> is<00:07:20.070> it 00:07:20.240 --> 00:07:20.250 align:start position:0% someone else and all it does here is it 00:07:20.250 --> 00:07:23.390 align:start position:0% someone else and all it does here is it has<00:07:21.120> the<00:07:21.300> address<00:07:21.449> of<00:07:21.720> the<00:07:21.900> registry<00:07:22.650> and<00:07:22.860> when 00:07:23.390 --> 00:07:23.400 align:start position:0% has the address of the registry and when 00:07:23.400 --> 00:07:26.210 align:start position:0% has the address of the registry and when it's<00:07:23.520> asked<00:07:23.820> to<00:07:24.000> it<00:07:24.470> updates<00:07:25.470> the<00:07:25.710> name<00:07:25.889> in<00:07:26.100> the 00:07:26.210 --> 00:07:26.220 align:start position:0% it's asked to it updates the name in the 00:07:26.220 --> 00:07:29.480 align:start position:0% it's asked to it updates the name in the registry<00:07:26.610> so<00:07:27.949> those<00:07:28.949> are<00:07:29.100> the<00:07:29.160> basic 00:07:29.480 --> 00:07:29.490 align:start position:0% registry so those are the basic 00:07:29.490 --> 00:07:31.219 align:start position:0% registry so those are the basic components<00:07:29.580> of<00:07:30.030> ENS<00:07:30.360> and<00:07:30.600> it<00:07:30.810> pretty<00:07:31.050> much 00:07:31.219 --> 00:07:31.229 align:start position:0% components of ENS and it pretty much 00:07:31.229 --> 00:07:32.510 align:start position:0% components of ENS and it pretty much describes<00:07:31.710> the<00:07:31.860> entire<00:07:32.130> technical 00:07:32.510 --> 00:07:32.520 align:start position:0% describes the entire technical 00:07:32.520 --> 00:07:35.719 align:start position:0% describes the entire technical implementation<00:07:33.470> the<00:07:34.470> remaining<00:07:35.250> component 00:07:35.719 --> 00:07:35.729 align:start position:0% implementation the remaining component 00:07:35.729 --> 00:07:37.790 align:start position:0% implementation the remaining component the<00:07:36.000> the<00:07:36.270> only<00:07:36.419> remaining<00:07:36.960> component<00:07:37.530> which 00:07:37.790 --> 00:07:37.800 align:start position:0% the the only remaining component which 00:07:37.800 --> 00:07:38.900 align:start position:0% the the only remaining component which you'd<00:07:38.039> think<00:07:38.070> is<00:07:38.430> really<00:07:38.789> quite 00:07:38.900 --> 00:07:38.910 align:start position:0% you'd think is really quite 00:07:38.910 --> 00:07:40.640 align:start position:0% you'd think is really quite straightforward<00:07:39.240> but<00:07:39.750> really<00:07:40.110> really<00:07:40.500> isn't 00:07:40.640 --> 00:07:40.650 align:start position:0% straightforward but really really isn't 00:07:40.650 --> 00:07:43.610 align:start position:0% straightforward but really really isn't is<00:07:40.949> governance<00:07:41.990> governance<00:07:42.990> is<00:07:43.229> an<00:07:43.440> ongoing 00:07:43.610 --> 00:07:43.620 align:start position:0% is governance governance is an ongoing 00:07:43.620 --> 00:07:46.310 align:start position:0% is governance governance is an ongoing issue<00:07:44.070> the<00:07:44.310> question<00:07:44.490> is<00:07:44.850> how<00:07:45.570> how<00:07:45.990> should<00:07:46.199> we 00:07:46.310 --> 00:07:46.320 align:start position:0% issue the question is how how should we 00:07:46.320 --> 00:07:49.129 align:start position:0% issue the question is how how should we administer<00:07:46.919> the<00:07:46.949> domain<00:07:47.669> system<00:07:48.150> who<00:07:48.930> should 00:07:49.129 --> 00:07:49.139 align:start position:0% administer the domain system who should 00:07:49.139 --> 00:07:50.990 align:start position:0% administer the domain system who should we<00:07:49.229> assign<00:07:49.500> names<00:07:49.710> to<00:07:49.919> should<00:07:50.699> they<00:07:50.820> have<00:07:50.940> to 00:07:50.990 --> 00:07:51.000 align:start position:0% we assign names to should they have to 00:07:51.000 --> 00:07:52.700 align:start position:0% we assign names to should they have to pay<00:07:51.120> who<00:07:51.599> should<00:07:51.780> get<00:07:51.930> the<00:07:52.020> money<00:07:52.139> and<00:07:52.470> so 00:07:52.700 --> 00:07:52.710 align:start position:0% pay who should get the money and so 00:07:52.710 --> 00:07:54.890 align:start position:0% pay who should get the money and so forth<00:07:52.979> and<00:07:53.820> our<00:07:54.000> conversations<00:07:54.660> around 00:07:54.890 --> 00:07:54.900 align:start position:0% forth and our conversations around 00:07:54.900 --> 00:07:56.980 align:start position:0% forth and our conversations around governance<00:07:55.199> always<00:07:55.650> seem<00:07:55.889> to<00:07:55.919> go<00:07:56.190> like<00:07:56.400> this 00:07:56.980 --> 00:07:56.990 align:start position:0% governance always seem to go like this 00:07:56.990 --> 00:07:59.570 align:start position:0% governance always seem to go like this so<00:07:57.990> I<00:07:58.020> go<00:07:58.289> I've<00:07:58.560> got<00:07:58.620> this<00:07:58.919> really<00:07:59.220> great<00:07:59.520> idea 00:07:59.570 --> 00:07:59.580 align:start position:0% so I go I've got this really great idea 00:07:59.580 --> 00:08:01.640 align:start position:0% so I go I've got this really great idea on<00:08:00.150> how<00:08:00.300> we<00:08:00.360> can<00:08:00.539> assign<00:08:00.780> names<00:08:01.020> we<00:08:01.349> should<00:08:01.560> do 00:08:01.640 --> 00:08:01.650 align:start position:0% on how we can assign names we should do 00:08:01.650 --> 00:08:03.290 align:start position:0% on how we can assign names we should do it<00:08:01.800> like<00:08:01.830> this<00:08:02.190> sorry<00:08:02.849> Nick 00:08:03.290 --> 00:08:03.300 align:start position:0% it like this sorry Nick 00:08:03.300 --> 00:08:04.909 align:start position:0% it like this sorry Nick this<00:08:03.449> is<00:08:03.570> a<00:08:03.660> terrible<00:08:04.080> idea<00:08:04.229> I<00:08:04.440> have<00:08:04.620> a<00:08:04.650> bunch 00:08:04.909 --> 00:08:04.919 align:start position:0% this is a terrible idea I have a bunch 00:08:04.919 --> 00:08:07.640 align:start position:0% this is a terrible idea I have a bunch of<00:08:04.979> other<00:08:05.130> thing<00:08:05.490> we<00:08:05.880> can<00:08:06.030> do<00:08:06.349> actually<00:08:07.349> both 00:08:07.640 --> 00:08:07.650 align:start position:0% of other thing we can do actually both 00:08:07.650 --> 00:08:08.990 align:start position:0% of other thing we can do actually both of<00:08:07.680> you<00:08:08.010> are<00:08:08.160> wrong<00:08:08.310> we<00:08:08.550> should<00:08:08.729> let<00:08:08.849> the 00:08:08.990 --> 00:08:09.000 align:start position:0% of you are wrong we should let the 00:08:09.000 --> 00:08:13.399 align:start position:0% of you are wrong we should let the market<00:08:09.419> decide<00:08:11.300> well<00:08:12.300> actually<00:08:12.930> that's<00:08:13.289> a 00:08:13.399 --> 00:08:13.409 align:start position:0% market decide well actually that's a 00:08:13.409 --> 00:08:15.950 align:start position:0% market decide well actually that's a good<00:08:13.530> idea<00:08:13.680> but<00:08:14.070> then<00:08:14.430> who<00:08:14.789> gets<00:08:15.060> who<00:08:15.570> gets<00:08:15.780> the 00:08:15.950 --> 00:08:15.960 align:start position:0% good idea but then who gets who gets the 00:08:15.960 --> 00:08:19.100 align:start position:0% good idea but then who gets who gets the top-level<00:08:16.409> nine<00:08:16.710> innings<00:08:17.599> I've<00:08:18.599> got<00:08:18.870> a<00:08:18.900> great 00:08:19.100 --> 00:08:19.110 align:start position:0% top-level nine innings I've got a great 00:08:19.110 --> 00:08:21.370 align:start position:0% top-level nine innings I've got a great idea<00:08:19.349> on<00:08:19.770> how<00:08:19.889> we<00:08:19.949> should<00:08:20.190> assign<00:08:20.400> names<00:08:20.729> and 00:08:21.370 --> 00:08:21.380 align:start position:0% idea on how we should assign names and 00:08:21.380 --> 00:08:25.100 align:start position:0% idea on how we should assign names and so<00:08:22.380> forth<00:08:22.849> so<00:08:23.849> we<00:08:24.120> have<00:08:24.360> come<00:08:24.539> up<00:08:24.570> with<00:08:24.690> what 00:08:25.100 --> 00:08:25.110 align:start position:0% so forth so we have come up with what 00:08:25.110 --> 00:08:28.939 align:start position:0% so forth so we have come up with what Alex<00:08:25.680> calls<00:08:26.010> the<00:08:26.699> Macdonald<00:08:27.180> solution<00:08:27.949> and 00:08:28.939 --> 00:08:28.949 align:start position:0% Alex calls the Macdonald solution and 00:08:28.949 --> 00:08:31.100 align:start position:0% Alex calls the Macdonald solution and I'll<00:08:29.099> go<00:08:29.250> into<00:08:29.490> more<00:08:29.610> detail<00:08:30.000> in<00:08:30.030> it<00:08:30.780> shortly 00:08:31.100 --> 00:08:31.110 align:start position:0% I'll go into more detail in it shortly 00:08:31.110 --> 00:08:33.350 align:start position:0% I'll go into more detail in it shortly but<00:08:31.470> basically<00:08:31.830> our<00:08:32.070> plan<00:08:32.219> is<00:08:32.520> to<00:08:32.760> deploy<00:08:33.089> an 00:08:33.350 --> 00:08:33.360 align:start position:0% but basically our plan is to deploy an 00:08:33.360 --> 00:08:35.390 align:start position:0% but basically our plan is to deploy an interim<00:08:33.719> registrar<00:08:34.289> which<00:08:34.860> uses<00:08:35.159> a<00:08:35.190> very 00:08:35.390 --> 00:08:35.400 align:start position:0% interim registrar which uses a very 00:08:35.400 --> 00:08:38.000 align:start position:0% interim registrar which uses a very simple<00:08:35.700> registration<00:08:36.120> scheme<00:08:36.750> and<00:08:37.680> people 00:08:38.000 --> 00:08:38.010 align:start position:0% simple registration scheme and people 00:08:38.010 --> 00:08:40.940 align:start position:0% simple registration scheme and people can<00:08:38.219> then<00:08:38.370> register<00:08:38.940> names<00:08:39.419> and<00:08:39.810> we'll<00:08:40.740> what 00:08:40.940 --> 00:08:40.950 align:start position:0% can then register names and we'll what 00:08:40.950 --> 00:08:42.440 align:start position:0% can then register names and we'll what we<00:08:41.070> plan<00:08:41.310> on<00:08:41.430> launching<00:08:41.610> this<00:08:41.940> towards<00:08:42.360> the 00:08:42.440 --> 00:08:42.450 align:start position:0% we plan on launching this towards the 00:08:42.450 --> 00:08:45.380 align:start position:0% we plan on launching this towards the end<00:08:42.539> of<00:08:42.719> the<00:08:42.810> year<00:08:43.700> about<00:08:44.700> a<00:08:44.760> year<00:08:45.089> from<00:08:45.300> now 00:08:45.380 --> 00:08:45.390 align:start position:0% end of the year about a year from now 00:08:45.390 --> 00:08:48.590 align:start position:0% end of the year about a year from now we'll<00:08:45.900> starts<00:08:46.410> accepting<00:08:47.400> submissions<00:08:47.580> for<00:08:48.300> a 00:08:48.590 --> 00:08:48.600 align:start position:0% we'll starts accepting submissions for a 00:08:48.600 --> 00:08:50.510 align:start position:0% we'll starts accepting submissions for a permanent<00:08:48.990> registrar<00:08:49.620> which<00:08:49.890> we<00:08:50.070> expect<00:08:50.370> will 00:08:50.510 --> 00:08:50.520 align:start position:0% permanent registrar which we expect will 00:08:50.520 --> 00:08:52.100 align:start position:0% permanent registrar which we expect will be<00:08:50.550> more<00:08:50.760> complicated<00:08:51.060> more<00:08:51.510> sophisticated 00:08:52.100 --> 00:08:52.110 align:start position:0% be more complicated more sophisticated 00:08:52.110 --> 00:08:53.600 align:start position:0% be more complicated more sophisticated it<00:08:52.380> will<00:08:52.500> take<00:08:52.680> care<00:08:52.830> of<00:08:52.950> things<00:08:53.070> I<00:08:53.250> could<00:08:53.400> use 00:08:53.600 --> 00:08:53.610 align:start position:0% it will take care of things I could use 00:08:53.610 --> 00:08:56.660 align:start position:0% it will take care of things I could use and<00:08:53.880> so<00:08:54.060> forth<00:08:54.440> and<00:08:55.440> the<00:08:56.070> reason<00:08:56.400> for<00:08:56.430> the 00:08:56.660 --> 00:08:56.670 align:start position:0% and so forth and the reason for the 00:08:56.670 --> 00:08:58.430 align:start position:0% and so forth and the reason for the delay<00:08:56.790> is<00:08:57.180> that<00:08:57.360> we<00:08:57.450> want<00:08:57.660> to<00:08:57.900> get<00:08:58.260> some 00:08:58.430 --> 00:08:58.440 align:start position:0% delay is that we want to get some 00:08:58.440 --> 00:08:59.900 align:start position:0% delay is that we want to get some experience<00:08:58.800> with<00:08:59.160> operating<00:08:59.670> the<00:08:59.760> name 00:08:59.900 --> 00:08:59.910 align:start position:0% experience with operating the name 00:08:59.910 --> 00:09:01.370 align:start position:0% experience with operating the name system<00:09:00.360> we<00:09:00.480> want<00:09:00.660> to<00:09:00.750> learn<00:09:00.900> what<00:09:01.140> the<00:09:01.230> real 00:09:01.370 --> 00:09:01.380 align:start position:0% system we want to learn what the real 00:09:01.380 --> 00:09:03.650 align:start position:0% system we want to learn what the real practical<00:09:01.800> problems<00:09:02.310> are<00:09:02.520> we<00:09:03.330> want<00:09:03.510> to<00:09:03.570> be 00:09:03.650 --> 00:09:03.660 align:start position:0% practical problems are we want to be 00:09:03.660 --> 00:09:05.360 align:start position:0% practical problems are we want to be able<00:09:03.750> to<00:09:03.900> use<00:09:04.350> those<00:09:04.589> to<00:09:04.860> build<00:09:04.890> a<00:09:05.130> bit<00:09:05.279> of 00:09:05.360 --> 00:09:05.370 align:start position:0% able to use those to build a bit of 00:09:05.370 --> 00:09:07.699 align:start position:0% able to use those to build a bit of registrar<00:09:05.850> and<00:09:06.089> then<00:09:06.839> with<00:09:07.020> a<00:09:07.050> goal<00:09:07.290> of<00:09:07.500> about 00:09:07.699 --> 00:09:07.709 align:start position:0% registrar and then with a goal of about 00:09:07.709 --> 00:09:09.530 align:start position:0% registrar and then with a goal of about a<00:09:07.770> year<00:09:08.010> from<00:09:08.160> there<00:09:08.400> I'm<00:09:08.670> sorry<00:09:09.180> but<00:09:09.420> these 00:09:09.530 --> 00:09:09.540 align:start position:0% a year from there I'm sorry but these 00:09:09.540 --> 00:09:10.280 align:start position:0% a year from there I'm sorry but these are<00:09:09.750> slightly 00:09:10.280 --> 00:09:10.290 align:start position:0% are slightly 00:09:10.290 --> 00:09:11.990 align:start position:0% are slightly date<00:09:10.470> slides<00:09:10.769> please<00:09:11.070> pretend<00:09:11.430> those<00:09:11.639> of<00:09:11.790> Vega 00:09:11.990 --> 00:09:12.000 align:start position:0% date slides please pretend those of Vega 00:09:12.000 --> 00:09:14.810 align:start position:0% date slides please pretend those of Vega and<00:09:12.300> they're<00:09:12.449> not<00:09:12.600> November<00:09:13.130> we<00:09:14.130> will<00:09:14.339> we 00:09:14.810 --> 00:09:14.820 align:start position:0% and they're not November we will we 00:09:14.820 --> 00:09:16.699 align:start position:0% and they're not November we will we intend<00:09:15.120> to<00:09:15.209> launch<00:09:15.570> the<00:09:15.839> permanent<00:09:16.199> registrar 00:09:16.699 --> 00:09:16.709 align:start position:0% intend to launch the permanent registrar 00:09:16.709 --> 00:09:18.710 align:start position:0% intend to launch the permanent registrar to<00:09:16.889> replace<00:09:17.160> the<00:09:17.339> into<00:09:17.579> the<00:09:17.850> intermediate<00:09:18.509> one 00:09:18.710 --> 00:09:18.720 align:start position:0% to replace the into the intermediate one 00:09:18.720 --> 00:09:21.410 align:start position:0% to replace the into the intermediate one so<00:09:19.709> what<00:09:19.920> does<00:09:20.100> the<00:09:20.339> temporary<00:09:20.910> registrar 00:09:21.410 --> 00:09:21.420 align:start position:0% so what does the temporary registrar 00:09:21.420 --> 00:09:24.290 align:start position:0% so what does the temporary registrar looks<00:09:21.630> like<00:09:21.870> it's<00:09:22.230> an<00:09:22.500> auction<00:09:22.850> only<00:09:23.850> names 00:09:24.290 --> 00:09:24.300 align:start position:0% looks like it's an auction only names 00:09:24.300 --> 00:09:26.060 align:start position:0% looks like it's an auction only names and<00:09:24.570> a<00:09:24.660> dot<00:09:24.810> if<00:09:24.990> they're<00:09:25.230> available<00:09:25.320> so<00:09:25.920> we'll 00:09:26.060 --> 00:09:26.070 align:start position:0% and a dot if they're available so we'll 00:09:26.070 --> 00:09:27.920 align:start position:0% and a dot if they're available so we'll only<00:09:26.250> have<00:09:26.339> one<00:09:26.639> top-level<00:09:27.089> domain<00:09:27.480> with<00:09:27.810> the 00:09:27.920 --> 00:09:27.930 align:start position:0% only have one top-level domain with the 00:09:27.930 --> 00:09:31.370 align:start position:0% only have one top-level domain with the goal<00:09:28.079> of<00:09:28.670> preventing<00:09:29.870> collision<00:09:30.870> with<00:09:31.050> exist 00:09:31.370 --> 00:09:31.380 align:start position:0% goal of preventing collision with exist 00:09:31.380 --> 00:09:33.740 align:start position:0% goal of preventing collision with exist the<00:09:31.500> existing<00:09:31.529> domain<00:09:32.009> name<00:09:32.310> system<00:09:32.759> names 00:09:33.740 --> 00:09:33.750 align:start position:0% the existing domain name system names 00:09:33.750 --> 00:09:35.960 align:start position:0% the existing domain name system names are<00:09:33.959> optional<00:09:34.350> fusing<00:09:34.889> a<00:09:35.040> blind<00:09:35.370> second<00:09:35.790> price 00:09:35.960 --> 00:09:35.970 align:start position:0% are optional fusing a blind second price 00:09:35.970 --> 00:09:37.759 align:start position:0% are optional fusing a blind second price option<00:09:36.480> which<00:09:36.720> is<00:09:36.750> also<00:09:37.079> called<00:09:37.410> a<00:09:37.500> Vickrey 00:09:37.759 --> 00:09:37.769 align:start position:0% option which is also called a Vickrey 00:09:37.769 --> 00:09:40.639 align:start position:0% option which is also called a Vickrey auction<00:09:38.420> names<00:09:39.420> shorter<00:09:39.870> than<00:09:40.019> actually<00:09:40.470> that 00:09:40.639 --> 00:09:40.649 align:start position:0% auction names shorter than actually that 00:09:40.649 --> 00:09:42.680 align:start position:0% auction names shorter than actually that seven<00:09:41.069> characters<00:09:41.670> are<00:09:41.910> prohibited<00:09:42.389> which 00:09:42.680 --> 00:09:42.690 align:start position:0% seven characters are prohibited which 00:09:42.690 --> 00:09:44.420 align:start position:0% seven characters are prohibited which may<00:09:42.899> sound<00:09:43.079> restrictive<00:09:43.680> but<00:09:43.889> our<00:09:43.980> goal<00:09:44.190> is<00:09:44.399> to 00:09:44.420 --> 00:09:44.430 align:start position:0% may sound restrictive but our goal is to 00:09:44.430 --> 00:09:46.910 align:start position:0% may sound restrictive but our goal is to save<00:09:45.329> the<00:09:45.600> really<00:09:45.870> high<00:09:46.019> value<00:09:46.079> names<00:09:46.589> for 00:09:46.910 --> 00:09:46.920 align:start position:0% save the really high value names for 00:09:46.920 --> 00:09:48.290 align:start position:0% save the really high value names for when<00:09:47.040> we<00:09:47.160> have<00:09:47.279> a<00:09:47.310> system<00:09:47.670> that<00:09:47.730> we<00:09:47.940> will<00:09:48.120> know 00:09:48.290 --> 00:09:48.300 align:start position:0% when we have a system that we will know 00:09:48.300 --> 00:09:50.230 align:start position:0% when we have a system that we will know we<00:09:48.630> know<00:09:48.810> will<00:09:49.050> fairly<00:09:49.290> hand<00:09:49.560> them<00:09:49.680> out 00:09:50.230 --> 00:09:50.240 align:start position:0% we know will fairly hand them out 00:09:50.240 --> 00:09:52.519 align:start position:0% we know will fairly hand them out winning<00:09:51.240> bidders<00:09:51.509> deposits<00:09:52.050> are<00:09:52.170> held<00:09:52.350> in 00:09:52.519 --> 00:09:52.529 align:start position:0% winning bidders deposits are held in 00:09:52.529 --> 00:09:54.829 align:start position:0% winning bidders deposits are held in contract<00:09:53.069> accounts<00:09:53.519> and<00:09:53.699> after<00:09:54.420> six<00:09:54.630> months 00:09:54.829 --> 00:09:54.839 align:start position:0% contract accounts and after six months 00:09:54.839 --> 00:09:57.139 align:start position:0% contract accounts and after six months you<00:09:55.079> can<00:09:55.470> delete<00:09:56.130> your<00:09:56.279> name<00:09:56.519> and<00:09:56.819> recover 00:09:57.139 --> 00:09:57.149 align:start position:0% you can delete your name and recover 00:09:57.149 --> 00:09:59.990 align:start position:0% you can delete your name and recover your<00:09:57.209> deposit<00:09:57.779> or<00:09:58.459> once<00:09:59.459> the<00:09:59.670> new<00:09:59.819> read 00:09:59.990 --> 00:10:00.000 align:start position:0% your deposit or once the new read 00:10:00.000 --> 00:10:02.030 align:start position:0% your deposit or once the new read permanent<00:10:00.449> registrar<00:10:00.899> is<00:10:01.019> available<00:10:01.529> you<00:10:01.860> can 00:10:02.030 --> 00:10:02.040 align:start position:0% permanent registrar is available you can 00:10:02.040 --> 00:10:03.559 align:start position:0% permanent registrar is available you can transfer<00:10:02.430> your<00:10:02.519> deposit<00:10:02.910> to<00:10:03.000> the<00:10:03.060> registrar 00:10:03.559 --> 00:10:03.569 align:start position:0% transfer your deposit to the registrar 00:10:03.569 --> 00:10:05.240 align:start position:0% transfer your deposit to the registrar and<00:10:03.750> keep<00:10:03.990> the<00:10:04.139> name<00:10:04.319> under<00:10:04.589> whatever<00:10:04.860> rules 00:10:05.240 --> 00:10:05.250 align:start position:0% and keep the name under whatever rules 00:10:05.250 --> 00:10:06.680 align:start position:0% and keep the name under whatever rules are<00:10:05.459> established<00:10:05.579> for<00:10:06.180> that<00:10:06.269> eventual 00:10:06.680 --> 00:10:06.690 align:start position:0% are established for that eventual 00:10:06.690 --> 00:10:09.199 align:start position:0% are established for that eventual registrar<00:10:07.199> the<00:10:07.769> goal<00:10:07.949> is<00:10:08.160> that<00:10:08.459> switching<00:10:09.089> to 00:10:09.199 --> 00:10:09.209 align:start position:0% registrar the goal is that switching to 00:10:09.209 --> 00:10:10.759 align:start position:0% registrar the goal is that switching to the<00:10:09.300> eventual<00:10:09.690> registrar<00:10:10.259> will<00:10:10.529> be 00:10:10.759 --> 00:10:10.769 align:start position:0% the eventual registrar will be 00:10:10.769 --> 00:10:13.100 align:start position:0% the eventual registrar will be consensual<00:10:11.310> you<00:10:11.819> if<00:10:11.970> you<00:10:12.120> don't<00:10:12.569> wish<00:10:12.750> to<00:10:12.930> use 00:10:13.100 --> 00:10:13.110 align:start position:0% consensual you if you don't wish to use 00:10:13.110 --> 00:10:14.569 align:start position:0% consensual you if you don't wish to use the<00:10:13.259> new<00:10:13.380> registrar<00:10:13.889> you<00:10:14.040> can<00:10:14.220> get<00:10:14.339> your<00:10:14.459> money 00:10:14.569 --> 00:10:14.579 align:start position:0% the new registrar you can get your money 00:10:14.579 --> 00:10:16.370 align:start position:0% the new registrar you can get your money back<00:10:14.699> if<00:10:15.060> you<00:10:15.209> do<00:10:15.389> then<00:10:15.660> you<00:10:15.779> can<00:10:15.930> pass<00:10:16.110> it<00:10:16.290> on 00:10:16.370 --> 00:10:16.380 align:start position:0% back if you do then you can pass it on 00:10:16.380 --> 00:10:19.189 align:start position:0% back if you do then you can pass it on which<00:10:17.040> means<00:10:17.310> that<00:10:17.579> we<00:10:17.699> hope<00:10:18.089> that<00:10:18.930> whatever 00:10:19.189 --> 00:10:19.199 align:start position:0% which means that we hope that whatever 00:10:19.199 --> 00:10:21.110 align:start position:0% which means that we hope that whatever registrar<00:10:19.889> eventuates<00:10:20.459> will<00:10:20.730> be<00:10:20.819> one<00:10:21.000> that 00:10:21.110 --> 00:10:21.120 align:start position:0% registrar eventuates will be one that 00:10:21.120 --> 00:10:22.639 align:start position:0% registrar eventuates will be one that the<00:10:21.240> majority<00:10:21.360> of<00:10:21.720> people<00:10:22.110> think<00:10:22.290> is<00:10:22.500> a<00:10:22.529> good 00:10:22.639 --> 00:10:22.649 align:start position:0% the majority of people think is a good 00:10:22.649 --> 00:10:26.329 align:start position:0% the majority of people think is a good idea<00:10:23.420> and<00:10:24.420> that's<00:10:25.290> it<00:10:25.500> for<00:10:25.649> the<00:10:25.769> etherium<00:10:26.190> name 00:10:26.329 --> 00:10:26.339 align:start position:0% idea and that's it for the etherium name 00:10:26.339 --> 00:10:27.800 align:start position:0% idea and that's it for the etherium name service<00:10:26.760> I<00:10:26.940> have<00:10:27.089> about<00:10:27.269> a<00:10:27.329> minute<00:10:27.569> for 00:10:27.800 --> 00:10:27.810 align:start position:0% service I have about a minute for 00:10:27.810 --> 00:10:29.269 align:start position:0% service I have about a minute for questions<00:10:28.319> but<00:10:28.560> I<00:10:28.649> don't<00:10:28.829> think<00:10:28.949> we're<00:10:29.130> taking 00:10:29.269 --> 00:10:29.279 align:start position:0% questions but I don't think we're taking 00:10:29.279 --> 00:10:32.000 align:start position:0% questions but I don't think we're taking them<00:10:29.639> if<00:10:30.480> your<00:10:30.750> interest<00:10:31.230> is<00:10:31.410> more<00:10:31.709> you<00:10:31.980> can 00:10:32.000 --> 00:10:32.010 align:start position:0% them if your interest is more you can 00:10:32.010 --> 00:10:34.519 align:start position:0% them if your interest is more you can email<00:10:32.279> me<00:10:32.639> in<00:10:32.880> at<00:10:33.240> Nikita<00:10:33.810> theorem<00:10:34.199> dot<00:10:34.350> org 00:10:34.519 --> 00:10:34.529 align:start position:0% email me in at Nikita theorem dot org 00:10:34.529 --> 00:10:37.370 align:start position:0% email me in at Nikita theorem dot org join<00:10:35.430> the<00:10:35.579> conversation<00:10:36.269> at<00:10:36.540> Gator<00:10:36.959> in<00:10:37.319> the 00:10:37.370 --> 00:10:37.380 align:start position:0% join the conversation at Gator in the 00:10:37.380 --> 00:10:41.150 align:start position:0% join the conversation at Gator in the name<00:10:38.100> registry<00:10:38.639> room<00:10:38.930> and<00:10:39.930> the<00:10:40.319> EIP<00:10:40.680> which 00:10:41.150 --> 00:10:41.160 align:start position:0% name registry room and the EIP which 00:10:41.160 --> 00:10:43.309 align:start position:0% name registry room and the EIP which officially<00:10:41.579> defines<00:10:41.940> ENS<00:10:42.329> is<00:10:42.569> there<00:10:42.930> please 00:10:43.309 --> 00:10:43.319 align:start position:0% officially defines ENS is there please 00:10:43.319 --> 00:10:45.050 align:start position:0% officially defines ENS is there please read<00:10:43.620> and<00:10:43.769> comment<00:10:43.980> we<00:10:44.639> welcome<00:10:44.970> your 00:10:45.050 --> 00:10:45.060 align:start position:0% read and comment we welcome your 00:10:45.060 --> 00:10:48.100 align:start position:0% read and comment we welcome your feedback<00:10:45.240> thank<00:10:45.810> you<00:10:45.899> very<00:10:46.019> much 00:10:48.100 --> 00:10:48.110 align:start position:0% feedback thank you very much 00:10:48.110 --> 00:10:50.170 align:start position:0% feedback thank you very much you