WEBVTT Kind: captions Language: en 00:00:04.490 --> 00:00:07.330 align:start position:0% I'm<00:00:05.030> talking<00:00:05.420> about<00:00:05.480> how<00:00:05.840> ENS<00:00:06.380> the<00:00:06.770> ca3<00:00:07.160> name 00:00:07.330 --> 00:00:07.340 align:start position:0% I'm talking about how ENS the ca3 name 00:00:07.340 --> 00:00:09.250 align:start position:0% I'm talking about how ENS the ca3 name service<00:00:07.700> is<00:00:07.850> taking<00:00:08.240> aetherium<00:00:08.780> to<00:00:08.930> the<00:00:09.020> rest 00:00:09.250 --> 00:00:09.260 align:start position:0% service is taking aetherium to the rest 00:00:09.260 --> 00:00:10.680 align:start position:0% service is taking aetherium to the rest of<00:00:09.410> the<00:00:09.559> Internet 00:00:10.680 --> 00:00:10.690 align:start position:0% of the Internet 00:00:10.690 --> 00:00:13.480 align:start position:0% of the Internet okay<00:00:11.690> so<00:00:11.750> our<00:00:12.290> name<00:00:12.770> obviously<00:00:13.010> is<00:00:13.370> the 00:00:13.480 --> 00:00:13.490 align:start position:0% okay so our name obviously is the 00:00:13.490 --> 00:00:14.770 align:start position:0% okay so our name obviously is the etherium<00:00:13.910> name<00:00:14.090> service<00:00:14.450> so<00:00:14.539> I<00:00:14.570> want<00:00:14.719> to 00:00:14.770 --> 00:00:14.780 align:start position:0% etherium name service so I want to 00:00:14.780 --> 00:00:16.630 align:start position:0% etherium name service so I want to explain<00:00:14.990> what<00:00:15.320> this<00:00:15.440> means<00:00:15.770> this<00:00:16.070> is<00:00:16.250> going<00:00:16.309> to 00:00:16.630 --> 00:00:16.640 align:start position:0% explain what this means this is going to 00:00:16.640 --> 00:00:20.020 align:start position:0% explain what this means this is going to I<00:00:16.670> think<00:00:16.789> explain<00:00:17.330> a<00:00:17.360> lot<00:00:18.550> so<00:00:19.550> how<00:00:19.730> is<00:00:19.880> it<00:00:19.910> a 00:00:20.020 --> 00:00:20.030 align:start position:0% I think explain a lot so how is it a 00:00:20.030 --> 00:00:22.480 align:start position:0% I think explain a lot so how is it a name<00:00:20.180> service<00:00:20.660> naming<00:00:21.650> services<00:00:22.070> or<00:00:22.189> things 00:00:22.480 --> 00:00:22.490 align:start position:0% name service naming services or things 00:00:22.490 --> 00:00:23.859 align:start position:0% name service naming services or things that<00:00:22.550> people<00:00:22.849> don't<00:00:23.029> think<00:00:23.119> about<00:00:23.449> very<00:00:23.570> much 00:00:23.859 --> 00:00:23.869 align:start position:0% that people don't think about very much 00:00:23.869 --> 00:00:25.240 align:start position:0% that people don't think about very much you<00:00:24.050> know<00:00:24.140> it's<00:00:24.259> it's<00:00:24.439> it's<00:00:24.679> a<00:00:24.800> kind<00:00:25.189> of 00:00:25.240 --> 00:00:25.250 align:start position:0% you know it's it's it's a kind of 00:00:25.250 --> 00:00:28.630 align:start position:0% you know it's it's it's a kind of something<00:00:25.460> in<00:00:25.550> the<00:00:25.640> background<00:00:25.820> and<00:00:26.359> a<00:00:27.580> lot<00:00:28.580> of 00:00:28.630 --> 00:00:28.640 align:start position:0% something in the background and a lot of 00:00:28.640 --> 00:00:29.890 align:start position:0% something in the background and a lot of people<00:00:28.849> actually<00:00:28.910> misunderstand<00:00:29.660> how<00:00:29.779> they 00:00:29.890 --> 00:00:29.900 align:start position:0% people actually misunderstand how they 00:00:29.900 --> 00:00:30.339 align:start position:0% people actually misunderstand how they work 00:00:30.339 --> 00:00:30.349 align:start position:0% work 00:00:30.349 --> 00:00:33.610 align:start position:0% work so<00:00:31.070> naming<00:00:31.580> services<00:00:32.200> naming<00:00:33.200> service<00:00:33.470> is 00:00:33.610 --> 00:00:33.620 align:start position:0% so naming services naming service is 00:00:33.620 --> 00:00:37.090 align:start position:0% so naming services naming service is just<00:00:33.920> a<00:00:34.190> lookup<00:00:34.610> system<00:00:35.030> that's<00:00:35.810> it<00:00:36.100> it 00:00:37.090 --> 00:00:37.100 align:start position:0% just a lookup system that's it it 00:00:37.100 --> 00:00:38.980 align:start position:0% just a lookup system that's it it doesn't<00:00:37.280> do<00:00:37.430> what<00:00:37.520> anything<00:00:37.820> else<00:00:37.970> okay<00:00:38.450> you 00:00:38.980 --> 00:00:38.990 align:start position:0% doesn't do what anything else okay you 00:00:38.990 --> 00:00:40.360 align:start position:0% doesn't do what anything else okay you provide<00:00:39.290> a<00:00:39.320> name<00:00:39.560> it<00:00:39.890> provides<00:00:40.190> with 00:00:40.360 --> 00:00:40.370 align:start position:0% provide a name it provides with 00:00:40.370 --> 00:00:42.280 align:start position:0% provide a name it provides with information<00:00:40.970> that's<00:00:41.720> it 00:00:42.280 --> 00:00:42.290 align:start position:0% information that's it 00:00:42.290 --> 00:00:44.470 align:start position:0% information that's it people<00:00:43.010> overcomplicate<00:00:43.340> this<00:00:43.760> okay<00:00:44.240> your 00:00:44.470 --> 00:00:44.480 align:start position:0% people overcomplicate this okay your 00:00:44.480 --> 00:00:45.910 align:start position:0% people overcomplicate this okay your computer<00:00:44.930> might<00:00:45.140> then<00:00:45.350> do<00:00:45.530> something<00:00:45.770> with 00:00:45.910 --> 00:00:45.920 align:start position:0% computer might then do something with 00:00:45.920 --> 00:00:47.440 align:start position:0% computer might then do something with that<00:00:46.130> information<00:00:46.430> but<00:00:46.850> that<00:00:46.910> is<00:00:47.120> separate 00:00:47.440 --> 00:00:47.450 align:start position:0% that information but that is separate 00:00:47.450 --> 00:00:51.370 align:start position:0% that information but that is separate from<00:00:47.510> the<00:00:47.780> naming<00:00:48.080> service<00:00:49.840> so<00:00:50.840> for<00:00:51.080> example 00:00:51.370 --> 00:00:51.380 align:start position:0% from the naming service so for example 00:00:51.380 --> 00:00:52.660 align:start position:0% from the naming service so for example with<00:00:51.470> the<00:00:51.530> NS<00:00:51.770> a<00:00:51.800> lot<00:00:52.010> of<00:00:52.100> people<00:00:52.310> think<00:00:52.580> that 00:00:52.660 --> 00:00:52.670 align:start position:0% with the NS a lot of people think that 00:00:52.670 --> 00:00:54.370 align:start position:0% with the NS a lot of people think that if<00:00:52.820> you're<00:00:53.180> sending<00:00:53.450> to<00:00:53.660> an<00:00:53.750> e<00:00:53.840> NS<00:00:54.080> address 00:00:54.370 --> 00:00:54.380 align:start position:0% if you're sending to an e NS address 00:00:54.380 --> 00:00:56.770 align:start position:0% if you're sending to an e NS address that<00:00:54.590> ENS<00:00:55.010> like<00:00:55.280> sends<00:00:55.820> the<00:00:55.940> transaction<00:00:56.600> on 00:00:56.770 --> 00:00:56.780 align:start position:0% that ENS like sends the transaction on 00:00:56.780 --> 00:00:58.540 align:start position:0% that ENS like sends the transaction on to<00:00:56.990> them<00:00:57.110> for<00:00:57.380> you<00:00:57.800> or<00:00:57.950> something<00:00:58.220> like<00:00:58.250> that 00:00:58.540 --> 00:00:58.550 align:start position:0% to them for you or something like that 00:00:58.550 --> 00:01:01.270 align:start position:0% to them for you or something like that nope<00:00:59.090> all<00:00:59.330> ENS<00:00:59.990> does<00:01:00.200> is<00:01:00.350> it<00:01:00.470> tells<00:01:00.680> the<00:01:00.860> wallet 00:01:01.270 --> 00:01:01.280 align:start position:0% nope all ENS does is it tells the wallet 00:01:01.280 --> 00:01:03.370 align:start position:0% nope all ENS does is it tells the wallet which<00:01:02.000> address<00:01:02.360> to<00:01:02.510> send<00:01:02.750> to<00:01:02.960> and<00:01:03.200> then<00:01:03.290> the 00:01:03.370 --> 00:01:03.380 align:start position:0% which address to send to and then the 00:01:03.380 --> 00:01:05.560 align:start position:0% which address to send to and then the wallet<00:01:03.800> sends<00:01:04.189> the<00:01:04.339> transaction<00:01:05.030> that<00:01:05.420> all 00:01:05.560 --> 00:01:05.570 align:start position:0% wallet sends the transaction that all 00:01:05.570 --> 00:01:06.700 align:start position:0% wallet sends the transaction that all happens<00:01:05.869> in<00:01:05.960> the<00:01:06.049> background<00:01:06.470> the<00:01:06.590> user 00:01:06.700 --> 00:01:06.710 align:start position:0% happens in the background the user 00:01:06.710 --> 00:01:08.140 align:start position:0% happens in the background the user doesn't<00:01:06.950> see<00:01:07.100> that<00:01:07.340> but<00:01:07.820> that's<00:01:07.970> what's 00:01:08.140 --> 00:01:08.150 align:start position:0% doesn't see that but that's what's 00:01:08.150 --> 00:01:10.390 align:start position:0% doesn't see that but that's what's really<00:01:08.420> happening<00:01:08.890> so<00:01:09.890> why<00:01:10.040> do<00:01:10.100> we<00:01:10.250> have 00:01:10.390 --> 00:01:10.400 align:start position:0% really happening so why do we have 00:01:10.400 --> 00:01:11.950 align:start position:0% really happening so why do we have naming<00:01:10.730> services<00:01:11.120> obviously<00:01:11.330> computer 00:01:11.950 --> 00:01:11.960 align:start position:0% naming services obviously computer 00:01:11.960 --> 00:01:12.700 align:start position:0% naming services obviously computer identifiers<00:01:12.530> x' 00:01:12.700 --> 00:01:12.710 align:start position:0% identifiers x' 00:01:12.710 --> 00:01:14.380 align:start position:0% identifiers x' what<00:01:13.430> makes<00:01:13.640> sense<00:01:13.790> for<00:01:13.940> computers<00:01:14.300> what 00:01:14.380 --> 00:01:14.390 align:start position:0% what makes sense for computers what 00:01:14.390 --> 00:01:19.690 align:start position:0% what makes sense for computers what makes<00:01:14.540> sense<00:01:14.690> for<00:01:14.750> humans<00:01:15.140> don't<00:01:16.010> mix<00:01:18.700> the 00:01:19.690 --> 00:01:19.700 align:start position:0% makes sense for humans don't mix the 00:01:19.700 --> 00:01:21.880 align:start position:0% makes sense for humans don't mix the internet<00:01:20.030> already<00:01:20.450> has<00:01:20.720> a<00:01:20.750> naming<00:01:21.320> system 00:01:21.880 --> 00:01:21.890 align:start position:0% internet already has a naming system 00:01:21.890 --> 00:01:24.310 align:start position:0% internet already has a naming system domain<00:01:22.550> name<00:01:22.700> system<00:01:23.150> so<00:01:23.870> even<00:01:24.140> for 00:01:24.310 --> 00:01:24.320 align:start position:0% domain name system so even for 00:01:24.320 --> 00:01:26.230 align:start position:0% domain name system so even for blockchain<00:01:24.770> things<00:01:25.100> why<00:01:25.460> don't<00:01:25.520> we<00:01:25.850> just<00:01:26.060> use 00:01:26.230 --> 00:01:26.240 align:start position:0% blockchain things why don't we just use 00:01:26.240 --> 00:01:29.470 align:start position:0% blockchain things why don't we just use DNS<00:01:26.600> a<00:01:27.280> lot<00:01:28.280> of<00:01:28.340> people<00:01:28.580> that<00:01:29.180> I've<00:01:29.240> talked<00:01:29.390> to 00:01:29.470 --> 00:01:29.480 align:start position:0% DNS a lot of people that I've talked to 00:01:29.480 --> 00:01:30.670 align:start position:0% DNS a lot of people that I've talked to you<00:01:29.540> haven't<00:01:29.810> even<00:01:30.020> thought<00:01:30.170> I<00:01:30.350> haven't 00:01:30.670 --> 00:01:30.680 align:start position:0% you haven't even thought I haven't 00:01:30.680 --> 00:01:34.660 align:start position:0% you haven't even thought I haven't thought<00:01:30.800> about<00:01:30.920> this<00:01:31.630> DNS<00:01:32.630> could<00:01:33.670> provide 00:01:34.660 --> 00:01:34.670 align:start position:0% thought about this DNS could provide 00:01:34.670 --> 00:01:36.730 align:start position:0% thought about this DNS could provide naming<00:01:35.150> for<00:01:35.540> cryptocurrency<00:01:35.990> dresses 00:01:36.730 --> 00:01:36.740 align:start position:0% naming for cryptocurrency dresses 00:01:36.740 --> 00:01:38.890 align:start position:0% naming for cryptocurrency dresses it's<00:01:37.550> a<00:01:37.640> naming<00:01:37.940> service<00:01:38.270> it<00:01:38.420> can<00:01:38.540> provide 00:01:38.890 --> 00:01:38.900 align:start position:0% it's a naming service it can provide 00:01:38.900 --> 00:01:43.690 align:start position:0% it's a naming service it can provide naming<00:01:39.200> for<00:01:39.320> anything<00:01:41.650> so<00:01:42.650> so<00:01:42.890> so<00:01:43.190> why<00:01:43.370> don't 00:01:43.690 --> 00:01:43.700 align:start position:0% naming for anything so so so why don't 00:01:43.700 --> 00:01:45.520 align:start position:0% naming for anything so so so why don't we<00:01:43.760> well<00:01:44.510> it<00:01:44.600> is<00:01:44.690> because<00:01:44.780> DNS<00:01:45.170> launched<00:01:45.470> in 00:01:45.520 --> 00:01:45.530 align:start position:0% we well it is because DNS launched in 00:01:45.530 --> 00:01:48.190 align:start position:0% we well it is because DNS launched in 1985<00:01:46.010> it's<00:01:46.640> fairly<00:01:46.909> insecure<00:01:47.540> it's<00:01:47.990> fairly 00:01:48.190 --> 00:01:48.200 align:start position:0% 1985 it's fairly insecure it's fairly 00:01:48.200 --> 00:01:49.810 align:start position:0% 1985 it's fairly insecure it's fairly centralized<00:01:48.830> and<00:01:49.130> so<00:01:49.190> it<00:01:49.280> kind<00:01:49.430> of<00:01:49.460> doesn't<00:01:49.640> go 00:01:49.810 --> 00:01:49.820 align:start position:0% centralized and so it kind of doesn't go 00:01:49.820 --> 00:01:51.430 align:start position:0% centralized and so it kind of doesn't go along<00:01:50.000> with<00:01:50.390> the<00:01:50.479> values<00:01:50.870> of<00:01:50.900> blockchain 00:01:51.430 --> 00:01:51.440 align:start position:0% along with the values of blockchain 00:01:51.440 --> 00:01:53.410 align:start position:0% along with the values of blockchain world<00:01:51.650> I<00:01:51.950> just<00:01:52.400> want<00:01:52.549> to<00:01:52.610> point<00:01:52.790> out<00:01:52.940> that<00:01:53.000> DNS 00:01:53.410 --> 00:01:53.420 align:start position:0% world I just want to point out that DNS 00:01:53.420 --> 00:01:54.910 align:start position:0% world I just want to point out that DNS could<00:01:53.780> do<00:01:54.049> all<00:01:54.260> these<00:01:54.409> things<00:01:54.470> for<00:01:54.890> the 00:01:54.910 --> 00:01:54.920 align:start position:0% could do all these things for the 00:01:54.920 --> 00:01:56.649 align:start position:0% could do all these things for the blockchain<00:01:55.159> world<00:01:55.490> if<00:01:55.820> we<00:01:56.000> wanted<00:01:56.240> to<00:01:56.360> use<00:01:56.510> it 00:01:56.649 --> 00:01:56.659 align:start position:0% blockchain world if we wanted to use it 00:01:56.659 --> 00:02:02.380 align:start position:0% blockchain world if we wanted to use it for<00:01:56.780> that<00:01:59.979> so<00:02:00.979> ENS<00:02:01.400> is<00:02:01.580> a<00:02:01.729> naming<00:02:02.030> service 00:02:02.380 --> 00:02:02.390 align:start position:0% for that so ENS is a naming service 00:02:02.390 --> 00:02:04.240 align:start position:0% for that so ENS is a naming service right<00:02:02.630> it<00:02:02.780> has<00:02:02.900> names<00:02:03.200> owners<00:02:03.680> of<00:02:03.799> names<00:02:04.010> as 00:02:04.240 --> 00:02:04.250 align:start position:0% right it has names owners of names as 00:02:04.250 --> 00:02:08.130 align:start position:0% right it has names owners of names as records<00:02:04.640> that<00:02:04.760> can<00:02:04.909> store<00:02:05.180> any<00:02:05.830> information 00:02:08.130 --> 00:02:08.140 align:start position:0% records that can store any information 00:02:08.140 --> 00:02:11.500 align:start position:0% records that can store any information if<00:02:09.140> you<00:02:09.409> have<00:02:09.530> a<00:02:09.560> name<00:02:09.879> you<00:02:10.879> right<00:02:11.150> can<00:02:11.299> look<00:02:11.420> it 00:02:11.500 --> 00:02:11.510 align:start position:0% if you have a name you right can look it 00:02:11.510 --> 00:02:13.420 align:start position:0% if you have a name you right can look it up<00:02:11.709> you<00:02:12.709> can<00:02:12.829> do<00:02:12.920> something<00:02:13.219> with<00:02:13.249> that 00:02:13.420 --> 00:02:13.430 align:start position:0% up you can do something with that 00:02:13.430 --> 00:02:14.739 align:start position:0% up you can do something with that information<00:02:13.549> but<00:02:14.060> this<00:02:14.150> is<00:02:14.329> key<00:02:14.540> you<00:02:14.569> can 00:02:14.739 --> 00:02:14.749 align:start position:0% information but this is key you can 00:02:14.749 --> 00:02:17.009 align:start position:0% information but this is key you can store<00:02:14.930> any<00:02:15.139> information 00:02:17.009 --> 00:02:17.019 align:start position:0% store any information 00:02:17.019 --> 00:02:21.599 align:start position:0% store any information it's<00:02:17.379> not<00:02:17.530> just<00:02:17.829> for<00:02:18.040> aetherium<00:02:20.189> so<00:02:21.189> why<00:02:21.340> is<00:02:21.400> it 00:02:21.599 --> 00:02:21.609 align:start position:0% it's not just for aetherium so why is it 00:02:21.609 --> 00:02:24.780 align:start position:0% it's not just for aetherium so why is it the<00:02:21.700> etherium<00:02:22.359> name<00:02:22.750> service<00:02:23.609> it's<00:02:24.609> not 00:02:24.780 --> 00:02:24.790 align:start position:0% the etherium name service it's not 00:02:24.790 --> 00:02:26.849 align:start position:0% the etherium name service it's not because<00:02:25.329> it's<00:02:25.480> a<00:02:25.569> naming<00:02:25.750> service<00:02:26.200> only<00:02:26.560> for 00:02:26.849 --> 00:02:26.859 align:start position:0% because it's a naming service only for 00:02:26.859 --> 00:02:28.619 align:start position:0% because it's a naming service only for the<00:02:27.010> etherium<00:02:27.430> ecosystem<00:02:28.030> it's<00:02:28.209> because<00:02:28.450> it's 00:02:28.619 --> 00:02:28.629 align:start position:0% the etherium ecosystem it's because it's 00:02:28.629 --> 00:02:31.349 align:start position:0% the etherium ecosystem it's because it's built<00:02:29.019> on<00:02:29.379> aetherium<00:02:30.370> this<00:02:30.819> is<00:02:30.969> common 00:02:31.349 --> 00:02:31.359 align:start position:0% built on aetherium this is common 00:02:31.359 --> 00:02:33.179 align:start position:0% built on aetherium this is common confusion<00:02:31.659> if<00:02:31.930> you're<00:02:32.049> thinking<00:02:32.379> hmm<00:02:32.920> if<00:02:33.010> it's 00:02:33.179 --> 00:02:33.189 align:start position:0% confusion if you're thinking hmm if it's 00:02:33.189 --> 00:02:34.890 align:start position:0% confusion if you're thinking hmm if it's confusing<00:02:33.579> why<00:02:33.730> don't<00:02:33.909> you<00:02:34.030> rebrand<00:02:34.450> well 00:02:34.890 --> 00:02:34.900 align:start position:0% confusing why don't you rebrand well 00:02:34.900 --> 00:02:37.170 align:start position:0% confusing why don't you rebrand well we're<00:02:35.079> thinking<00:02:35.379> about<00:02:35.470> it<00:02:35.970> but<00:02:36.970> right<00:02:37.120> now 00:02:37.170 --> 00:02:37.180 align:start position:0% we're thinking about it but right now 00:02:37.180 --> 00:02:39.630 align:start position:0% we're thinking about it but right now this<00:02:37.510> is<00:02:37.599> very<00:02:37.689> important<00:02:38.109> to<00:02:38.170> understand<00:02:38.640> so 00:02:39.630 --> 00:02:39.640 align:start position:0% this is very important to understand so 00:02:39.640 --> 00:02:41.490 align:start position:0% this is very important to understand so just<00:02:39.819> it<00:02:40.030> it's<00:02:40.689> called<00:02:40.900> this<00:02:41.049> right<00:02:41.260> cuz<00:02:41.379> the 00:02:41.490 --> 00:02:41.500 align:start position:0% just it it's called this right cuz the 00:02:41.500 --> 00:02:43.500 align:start position:0% just it it's called this right cuz the logic<00:02:41.920> and<00:02:42.069> records<00:02:42.370> are<00:02:42.579> stored<00:02:42.939> on<00:02:43.269> the 00:02:43.500 --> 00:02:43.510 align:start position:0% logic and records are stored on the 00:02:43.510 --> 00:02:45.270 align:start position:0% logic and records are stored on the etherion<00:02:43.900> blockchain<00:02:44.409> but<00:02:44.859> it<00:02:44.950> can<00:02:45.069> store 00:02:45.270 --> 00:02:45.280 align:start position:0% etherion blockchain but it can store 00:02:45.280 --> 00:02:46.920 align:start position:0% etherion blockchain but it can store information<00:02:45.579> relevant<00:02:46.209> to<00:02:46.389> anything<00:02:46.629> right 00:02:46.920 --> 00:02:46.930 align:start position:0% information relevant to anything right 00:02:46.930 --> 00:02:48.869 align:start position:0% information relevant to anything right so<00:02:47.019> aetherium<00:02:47.469> is<00:02:47.769> just<00:02:48.010> like<00:02:48.250> the 00:02:48.869 --> 00:02:48.879 align:start position:0% so aetherium is just like the 00:02:48.879 --> 00:02:50.399 align:start position:0% so aetherium is just like the infrastructure<00:02:49.420> in<00:02:49.629> the<00:02:49.659> background<00:02:50.200> that<00:02:50.319> it 00:02:50.399 --> 00:02:50.409 align:start position:0% infrastructure in the background that it 00:02:50.409 --> 00:02:52.349 align:start position:0% infrastructure in the background that it happens<00:02:50.709> to<00:02:50.859> run<00:02:51.010> on<00:02:51.220> but<00:02:51.879> that<00:02:52.000> doesn't 00:02:52.349 --> 00:02:52.359 align:start position:0% happens to run on but that doesn't 00:02:52.359 --> 00:02:54.089 align:start position:0% happens to run on but that doesn't restrict<00:02:52.959> the<00:02:53.170> types<00:02:53.379> of<00:02:53.500> information<00:02:53.709> you 00:02:54.089 --> 00:02:54.099 align:start position:0% restrict the types of information you 00:02:54.099 --> 00:02:55.259 align:start position:0% restrict the types of information you could<00:02:54.250> store<00:02:54.400> on<00:02:54.549> it<00:02:54.669> right<00:02:54.819> you<00:02:54.879> could<00:02:55.000> store 00:02:55.259 --> 00:02:55.269 align:start position:0% could store on it right you could store 00:02:55.269 --> 00:02:58.140 align:start position:0% could store on it right you could store phone<00:02:55.989> numbers<00:02:56.319> you<00:02:56.349> could<00:02:56.680> store<00:02:56.919> your<00:02:57.220> app 00:02:58.140 --> 00:02:58.150 align:start position:0% phone numbers you could store your app 00:02:58.150 --> 00:03:00.059 align:start position:0% phone numbers you could store your app your<00:02:58.359> your<00:02:58.750> home<00:02:58.989> home<00:02:59.470> address<00:02:59.769> you<00:02:59.950> could 00:03:00.059 --> 00:03:00.069 align:start position:0% your your home home address you could 00:03:00.069 --> 00:03:01.470 align:start position:0% your your home home address you could store<00:03:00.280> a<00:03:00.340> Bitcoin<00:03:00.760> address<00:03:01.060> you<00:03:01.180> can<00:03:01.299> store 00:03:01.470 --> 00:03:01.480 align:start position:0% store a Bitcoin address you can store 00:03:01.480 --> 00:03:04.860 align:start position:0% store a Bitcoin address you can store anything<00:03:03.359> it's<00:03:04.359> a<00:03:04.419> common<00:03:04.750> misconception 00:03:04.860 --> 00:03:04.870 align:start position:0% anything it's a common misconception 00:03:04.870 --> 00:03:07.319 align:start position:0% anything it's a common misconception that<00:03:05.470> it<00:03:05.650> can't<00:03:05.889> write<00:03:06.669> we<00:03:06.790> have<00:03:06.939> this<00:03:07.120> right 00:03:07.319 --> 00:03:07.329 align:start position:0% that it can't write we have this right 00:03:07.329 --> 00:03:11.210 align:start position:0% that it can't write we have this right on<00:03:07.450> our<00:03:07.599> website<00:03:07.629> it's<00:03:08.290> been<00:03:08.500> there<00:03:08.620> all<00:03:08.650> along 00:03:11.210 --> 00:03:11.220 align:start position:0% 00:03:11.220 --> 00:03:15.690 align:start position:0% so<00:03:12.220> why<00:03:13.379> do<00:03:14.379> we<00:03:14.680> use<00:03:14.709> etherium<00:03:15.459> as<00:03:15.579> our 00:03:15.690 --> 00:03:15.700 align:start position:0% so why do we use etherium as our 00:03:15.700 --> 00:03:17.849 align:start position:0% so why do we use etherium as our back-end<00:03:16.379> it's<00:03:17.379> a<00:03:17.409> good<00:03:17.530> question<00:03:17.829> right 00:03:17.849 --> 00:03:17.859 align:start position:0% back-end it's a good question right 00:03:17.859 --> 00:03:21.059 align:start position:0% back-end it's a good question right there's<00:03:18.129> other<00:03:18.250> blockchains<00:03:18.760> out<00:03:18.909> there<00:03:20.069> even 00:03:21.059 --> 00:03:21.069 align:start position:0% there's other blockchains out there even 00:03:21.069 --> 00:03:22.500 align:start position:0% there's other blockchains out there even if<00:03:21.220> we<00:03:21.340> want<00:03:21.519> to<00:03:21.549> have<00:03:21.669> a<00:03:21.729> blockchain<00:03:22.000> naming 00:03:22.500 --> 00:03:22.510 align:start position:0% if we want to have a blockchain naming 00:03:22.510 --> 00:03:24.210 align:start position:0% if we want to have a blockchain naming sort<00:03:22.720> a<00:03:22.810> naming<00:03:23.560> service<00:03:23.829> built<00:03:24.040> on<00:03:24.159> a 00:03:24.210 --> 00:03:24.220 align:start position:0% sort a naming service built on a 00:03:24.220 --> 00:03:26.330 align:start position:0% sort a naming service built on a blockchain<00:03:24.510> here's<00:03:25.510> some<00:03:25.720> advantages 00:03:26.330 --> 00:03:26.340 align:start position:0% blockchain here's some advantages 00:03:26.340 --> 00:03:30.059 align:start position:0% blockchain here's some advantages aetherium<00:03:27.340> has<00:03:27.639> a<00:03:27.669> very<00:03:28.090> high<00:03:28.299> security<00:03:29.069> built 00:03:30.059 --> 00:03:30.069 align:start position:0% aetherium has a very high security built 00:03:30.069 --> 00:03:32.699 align:start position:0% aetherium has a very high security built into<00:03:30.400> it<00:03:30.519> you<00:03:31.479> know<00:03:31.750> if<00:03:31.870> you<00:03:31.989> were<00:03:32.139> making<00:03:32.620> our 00:03:32.699 --> 00:03:32.709 align:start position:0% into it you know if you were making our 00:03:32.709 --> 00:03:34.170 align:start position:0% into it you know if you were making our own<00:03:32.739> chain<00:03:33.220> or<00:03:33.489> something<00:03:33.760> like<00:03:33.849> that<00:03:33.909> we<00:03:34.060> have 00:03:34.170 --> 00:03:34.180 align:start position:0% own chain or something like that we have 00:03:34.180 --> 00:03:35.729 align:start position:0% own chain or something like that we have to<00:03:34.269> bootstrap<00:03:34.750> security<00:03:35.290> would<00:03:35.440> be<00:03:35.560> low 00:03:35.729 --> 00:03:35.739 align:start position:0% to bootstrap security would be low 00:03:35.739 --> 00:03:40.349 align:start position:0% to bootstrap security would be low security<00:03:36.129> it'd<00:03:36.519> be<00:03:38.159> in<00:03:39.159> and<00:03:39.370> be<00:03:39.519> probably<00:03:40.090> less 00:03:40.349 --> 00:03:40.359 align:start position:0% security it'd be in and be probably less 00:03:40.359 --> 00:03:42.119 align:start position:0% security it'd be in and be probably less decentralized<00:03:41.049> aetherium<00:03:41.560> we<00:03:41.709> can<00:03:41.829> build<00:03:41.979> on 00:03:42.119 --> 00:03:42.129 align:start position:0% decentralized aetherium we can build on 00:03:42.129 --> 00:03:43.680 align:start position:0% decentralized aetherium we can build on a<00:03:42.159> theorem<00:03:42.489> it<00:03:42.579> has<00:03:42.699> high<00:03:43.269> security 00:03:43.680 --> 00:03:43.690 align:start position:0% a theorem it has high security 00:03:43.690 --> 00:03:48.300 align:start position:0% a theorem it has high security decentralized<00:03:44.260> right<00:03:45.040> out<00:03:45.159> of<00:03:45.190> the<00:03:45.370> bat<00:03:47.310> we 00:03:48.300 --> 00:03:48.310 align:start position:0% decentralized right out of the bat we 00:03:48.310 --> 00:03:50.159 align:start position:0% decentralized right out of the bat we commend<00:03:48.790> benefit<00:03:49.239> from<00:03:49.389> all<00:03:49.540> the<00:03:49.629> ecosystem 00:03:50.159 --> 00:03:50.169 align:start position:0% commend benefit from all the ecosystem 00:03:50.169 --> 00:03:52.140 align:start position:0% commend benefit from all the ecosystem infrastructure<00:03:50.769> it's<00:03:51.250> like<00:03:51.370> meta<00:03:51.579> masks<00:03:51.790> and 00:03:52.140 --> 00:03:52.150 align:start position:0% infrastructure it's like meta masks and 00:03:52.150 --> 00:03:55.710 align:start position:0% infrastructure it's like meta masks and fear<00:03:52.419> I<00:03:52.449> mean<00:03:52.659> tons<00:03:52.930> of<00:03:53.109> services<00:03:54.569> that<00:03:55.569> we 00:03:55.710 --> 00:03:55.720 align:start position:0% fear I mean tons of services that we 00:03:55.720 --> 00:03:57.449 align:start position:0% fear I mean tons of services that we benefit<00:03:56.109> from<00:03:56.169> right<00:03:56.680> right<00:03:56.949> away<00:03:57.159> we<00:03:57.310> don't 00:03:57.449 --> 00:03:57.459 align:start position:0% benefit from right right away we don't 00:03:57.459 --> 00:04:00.000 align:start position:0% benefit from right right away we don't have<00:03:57.579> to<00:03:57.699> reinvent<00:03:58.000> those<00:03:58.359> things<00:03:58.629> we<00:03:59.620> benefit 00:04:00.000 --> 00:04:00.010 align:start position:0% have to reinvent those things we benefit 00:04:00.010 --> 00:04:02.069 align:start position:0% have to reinvent those things we benefit from<00:04:00.040> standards<00:04:00.639> so<00:04:00.760> all<00:04:00.939> dot<00:04:01.359> 'if<00:04:01.569> names<00:04:01.870> are 00:04:02.069 --> 00:04:02.079 align:start position:0% from standards so all dot 'if names are 00:04:02.079 --> 00:04:06.300 align:start position:0% from standards so all dot 'if names are actually<00:04:02.169> ERC<00:04:02.879> 2721<00:04:03.930> compliant<00:04:04.930> so<00:04:05.590> you<00:04:06.189> know 00:04:06.300 --> 00:04:06.310 align:start position:0% actually ERC 2721 compliant so you know 00:04:06.310 --> 00:04:08.909 align:start position:0% actually ERC 2721 compliant so you know a<00:04:06.340> dot<00:04:06.609> eath<00:04:06.760> names<00:04:07.000> can<00:04:07.180> just<00:04:07.299> plug<00:04:07.540> into<00:04:07.919> and 00:04:08.909 --> 00:04:08.919 align:start position:0% a dot eath names can just plug into and 00:04:08.919 --> 00:04:11.520 align:start position:0% a dot eath names can just plug into and if<00:04:09.549> two<00:04:09.729> markets<00:04:10.060> that's<00:04:10.930> a<00:04:11.019> benefit<00:04:11.349> that<00:04:11.470> we 00:04:11.520 --> 00:04:11.530 align:start position:0% if two markets that's a benefit that we 00:04:11.530 --> 00:04:13.939 align:start position:0% if two markets that's a benefit that we have<00:04:11.560> for<00:04:11.889> from<00:04:12.099> from<00:04:12.400> being<00:04:12.609> on<00:04:12.699> aetherium 00:04:13.939 --> 00:04:13.949 align:start position:0% have for from from being on aetherium 00:04:13.949 --> 00:04:16.289 align:start position:0% have for from from being on aetherium programmability<00:04:14.949> so<00:04:15.790> you<00:04:15.849> know<00:04:16.120> you'd<00:04:16.269> have 00:04:16.289 --> 00:04:16.299 align:start position:0% programmability so you know you'd have 00:04:16.299 --> 00:04:17.849 align:start position:0% programmability so you know you'd have things<00:04:16.630> like<00:04:16.750> conditioned<00:04:17.289> ownership<00:04:17.680> of 00:04:17.849 --> 00:04:17.859 align:start position:0% things like conditioned ownership of 00:04:17.859 --> 00:04:20.099 align:start position:0% things like conditioned ownership of name<00:04:18.099> or<00:04:18.759> something<00:04:19.120> that's<00:04:19.239> time<00:04:19.509> locked<00:04:19.780> for 00:04:20.099 --> 00:04:20.109 align:start position:0% name or something that's time locked for 00:04:20.109 --> 00:04:21.870 align:start position:0% name or something that's time locked for a<00:04:20.139> certain<00:04:20.440> period<00:04:20.530> of<00:04:20.680> time<00:04:20.769> and<00:04:21.699> also 00:04:21.870 --> 00:04:21.880 align:start position:0% a certain period of time and also 00:04:21.880 --> 00:04:23.550 align:start position:0% a certain period of time and also interaction<00:04:22.539> with<00:04:22.720> other<00:04:22.870> contracts<00:04:23.349> on<00:04:23.530> the 00:04:23.550 --> 00:04:23.560 align:start position:0% interaction with other contracts on the 00:04:23.560 --> 00:04:25.950 align:start position:0% interaction with other contracts on the theorem<00:04:23.919> this<00:04:24.070> is<00:04:24.250> extremely<00:04:24.700> powerful<00:04:25.000> the 00:04:25.950 --> 00:04:25.960 align:start position:0% theorem this is extremely powerful the 00:04:25.960 --> 00:04:27.659 align:start position:0% theorem this is extremely powerful the fact<00:04:26.169> that<00:04:26.289> NS<00:04:26.680> can<00:04:26.889> do<00:04:27.010> this<00:04:27.190> you<00:04:27.460> know<00:04:27.550> if<00:04:27.610> we 00:04:27.659 --> 00:04:27.669 align:start position:0% fact that NS can do this you know if we 00:04:27.669 --> 00:04:29.490 align:start position:0% fact that NS can do this you know if we were<00:04:27.789> building<00:04:28.060> our<00:04:28.389> on<00:04:28.599> our<00:04:28.630> own<00:04:28.870> chain<00:04:29.200> or<00:04:29.409> on 00:04:29.490 --> 00:04:29.500 align:start position:0% were building our on our own chain or on 00:04:29.500 --> 00:04:30.530 align:start position:0% were building our on our own chain or on different<00:04:29.770> chain<00:04:29.919> we<00:04:30.099> wouldn't 00:04:30.530 --> 00:04:30.540 align:start position:0% different chain we wouldn't 00:04:30.540 --> 00:04:33.110 align:start position:0% different chain we wouldn't benefit<00:04:30.900> from<00:04:31.830> the<00:04:32.070> etherium<00:04:32.490> ecosystem<00:04:32.970> in 00:04:33.110 --> 00:04:33.120 align:start position:0% benefit from the etherium ecosystem in 00:04:33.120 --> 00:04:35.930 align:start position:0% benefit from the etherium ecosystem in this<00:04:33.270> way<00:04:33.560> so<00:04:34.560> so<00:04:34.890> we<00:04:35.250> think<00:04:35.490> this<00:04:35.640> is<00:04:35.760> why<00:04:35.910> a 00:04:35.930 --> 00:04:35.940 align:start position:0% this way so so we think this is why a 00:04:35.940 --> 00:04:39.620 align:start position:0% this way so so we think this is why a theory<00:04:37.220> emitting<00:04:38.220> a<00:04:38.430> blockchain<00:04:39.180> based 00:04:39.620 --> 00:04:39.630 align:start position:0% theory emitting a blockchain based 00:04:39.630 --> 00:04:45.260 align:start position:0% theory emitting a blockchain based naming<00:04:40.170> system<00:04:42.620> so<00:04:43.620> to<00:04:43.650> kind<00:04:43.920> of<00:04:43.950> sum<00:04:44.220> up<00:04:44.270> ENS 00:04:45.260 --> 00:04:45.270 align:start position:0% naming system so to kind of sum up ENS 00:04:45.270 --> 00:04:47.300 align:start position:0% naming system so to kind of sum up ENS uses<00:04:45.720> aetherium<00:04:46.230> to<00:04:46.470> serve<00:04:46.740> the<00:04:46.980> Internet 00:04:47.300 --> 00:04:47.310 align:start position:0% uses aetherium to serve the Internet 00:04:47.310 --> 00:04:50.090 align:start position:0% uses aetherium to serve the Internet including<00:04:47.580> and<00:04:48.270> beyond<00:04:48.750> the<00:04:49.590> etherium 00:04:50.090 --> 00:04:50.100 align:start position:0% including and beyond the etherium 00:04:50.100 --> 00:04:56.300 align:start position:0% including and beyond the etherium ecosystem<00:04:51.650> and<00:04:52.650> as<00:04:52.740> a<00:04:52.830> result<00:04:54.740> ENS<00:04:55.770> and<00:04:56.070> their 00:04:56.300 --> 00:04:56.310 align:start position:0% ecosystem and as a result ENS and their 00:04:56.310 --> 00:04:58.970 align:start position:0% ecosystem and as a result ENS and their if<00:04:56.460> our<00:04:57.210> goal<00:04:57.510> is<00:04:57.540> to<00:04:57.720> make<00:04:57.900> ENS<00:04:58.320> and<00:04:58.350> therefore 00:04:58.970 --> 00:04:58.980 align:start position:0% if our goal is to make ENS and therefore 00:04:58.980 --> 00:05:01.640 align:start position:0% if our goal is to make ENS and therefore aetherium<00:04:59.670> a<00:04:59.850> basic<00:05:00.750> piece<00:05:01.020> of<00:05:01.050> Internet 00:05:01.640 --> 00:05:01.650 align:start position:0% aetherium a basic piece of Internet 00:05:01.650 --> 00:05:04.070 align:start position:0% aetherium a basic piece of Internet infrastructure<00:05:02.220> used<00:05:03.030> widely<00:05:03.300> by<00:05:03.540> people 00:05:04.070 --> 00:05:04.080 align:start position:0% infrastructure used widely by people 00:05:04.080 --> 00:05:05.510 align:start position:0% infrastructure used widely by people whether<00:05:04.320> they<00:05:04.590> are<00:05:04.710> part<00:05:04.980> of<00:05:05.130> the<00:05:05.280> blockchain 00:05:05.510 --> 00:05:05.520 align:start position:0% whether they are part of the blockchain 00:05:05.520 --> 00:05:09.410 align:start position:0% whether they are part of the blockchain community<00:05:06.300> or<00:05:06.540> not<00:05:07.550> and<00:05:08.550> the<00:05:09.030> rest<00:05:09.210> of<00:05:09.330> this 00:05:09.410 --> 00:05:09.420 align:start position:0% community or not and the rest of this 00:05:09.420 --> 00:05:12.410 align:start position:0% community or not and the rest of this presentation<00:05:09.600> is<00:05:10.430> about<00:05:11.430> how<00:05:11.730> we<00:05:11.790> are<00:05:12.090> doing 00:05:12.410 --> 00:05:12.420 align:start position:0% presentation is about how we are doing 00:05:12.420 --> 00:05:17.300 align:start position:0% presentation is about how we are doing that<00:05:14.870> so<00:05:15.870> of<00:05:16.110> course<00:05:16.410> we<00:05:16.650> do<00:05:16.800> support<00:05:17.130> the 00:05:17.300 --> 00:05:17.310 align:start position:0% that so of course we do support the 00:05:17.310 --> 00:05:18.710 align:start position:0% that so of course we do support the etherium<00:05:17.670> ecosystem<00:05:18.210> I<00:05:18.300> don't<00:05:18.450> want<00:05:18.570> to<00:05:18.630> give 00:05:18.710 --> 00:05:18.720 align:start position:0% etherium ecosystem I don't want to give 00:05:18.720 --> 00:05:19.940 align:start position:0% etherium ecosystem I don't want to give the<00:05:18.840> impression<00:05:19.050> that<00:05:19.320> we're<00:05:19.530> moving<00:05:19.650> up 00:05:19.940 --> 00:05:19.950 align:start position:0% the impression that we're moving up 00:05:19.950 --> 00:05:21.830 align:start position:0% the impression that we're moving up beyond<00:05:20.280> the<00:05:20.670> atheneum<00:05:21.180> ecosystem<00:05:21.690> that's 00:05:21.830 --> 00:05:21.840 align:start position:0% beyond the atheneum ecosystem that's 00:05:21.840 --> 00:05:24.410 align:start position:0% beyond the atheneum ecosystem that's still<00:05:22.140> a<00:05:22.380> core<00:05:22.890> thing<00:05:23.100> that<00:05:23.280> we<00:05:23.370> do<00:05:23.550> that's 00:05:24.410 --> 00:05:24.420 align:start position:0% still a core thing that we do that's 00:05:24.420 --> 00:05:27.260 align:start position:0% still a core thing that we do that's kind<00:05:24.630> of<00:05:24.660> our<00:05:24.780> bread<00:05:24.960> and<00:05:24.990> butter<00:05:25.640> but<00:05:26.640> ENS 00:05:27.260 --> 00:05:27.270 align:start position:0% kind of our bread and butter but ENS 00:05:27.270 --> 00:05:29.420 align:start position:0% kind of our bread and butter but ENS does<00:05:27.450> much<00:05:27.900> more<00:05:28.170> than<00:05:28.410> that<00:05:28.440> and<00:05:28.830> many<00:05:29.190> people 00:05:29.420 --> 00:05:29.430 align:start position:0% does much more than that and many people 00:05:29.430 --> 00:05:31.700 align:start position:0% does much more than that and many people don't<00:05:29.640> know<00:05:29.700> that<00:05:30.240> ENS<00:05:30.900> does<00:05:31.140> much<00:05:31.380> more<00:05:31.590> than 00:05:31.700 --> 00:05:31.710 align:start position:0% don't know that ENS does much more than 00:05:31.710 --> 00:05:33.650 align:start position:0% don't know that ENS does much more than that<00:05:31.740> so<00:05:32.040> I'm<00:05:33.000> going<00:05:33.150> to<00:05:33.270> be<00:05:33.360> talking<00:05:33.630> about 00:05:33.650 --> 00:05:33.660 align:start position:0% that so I'm going to be talking about 00:05:33.660 --> 00:05:36.470 align:start position:0% that so I'm going to be talking about more<00:05:34.260> in<00:05:34.290> detail<00:05:34.620> all<00:05:34.770> the<00:05:34.830> non<00:05:35.480> directly 00:05:36.470 --> 00:05:36.480 align:start position:0% more in detail all the non directly 00:05:36.480 --> 00:05:39.100 align:start position:0% more in detail all the non directly etherium<00:05:36.960> related<00:05:37.290> things<00:05:37.500> that<00:05:37.680> we<00:05:37.770> support 00:05:39.100 --> 00:05:39.110 align:start position:0% etherium related things that we support 00:05:39.110 --> 00:05:41.330 align:start position:0% etherium related things that we support okay<00:05:40.110> so<00:05:40.170> ipfs<00:05:40.890> the<00:05:41.070> interplanetary 00:05:41.330 --> 00:05:41.340 align:start position:0% okay so ipfs the interplanetary 00:05:41.340 --> 00:05:44.930 align:start position:0% okay so ipfs the interplanetary filesystem<00:05:43.340> ipfs<00:05:44.370> is<00:05:44.550> a<00:05:44.580> peer-to-peer 00:05:44.930 --> 00:05:44.940 align:start position:0% filesystem ipfs is a peer-to-peer 00:05:44.940 --> 00:05:48.200 align:start position:0% filesystem ipfs is a peer-to-peer decentralized<00:05:45.810> file<00:05:46.440> file<00:05:47.220> system<00:05:47.640> file 00:05:48.200 --> 00:05:48.210 align:start position:0% decentralized file file system file 00:05:48.210 --> 00:05:51.350 align:start position:0% decentralized file file system file sharing<00:05:48.690> protocol<00:05:49.170> ENS<00:05:50.160> is<00:05:50.430> a<00:05:50.490> decentralized 00:05:51.350 --> 00:05:51.360 align:start position:0% sharing protocol ENS is a decentralized 00:05:51.360 --> 00:05:54.380 align:start position:0% sharing protocol ENS is a decentralized naming<00:05:51.750> service<00:05:52.050> so<00:05:52.680> together<00:05:53.060> they<00:05:54.060> are<00:05:54.210> the 00:05:54.380 --> 00:05:54.390 align:start position:0% naming service so together they are the 00:05:54.390 --> 00:05:56.390 align:start position:0% naming service so together they are the decentralized<00:05:54.720> web<00:05:55.080> we<00:05:56.040> actually<00:05:56.280> have<00:05:56.370> a 00:05:56.390 --> 00:05:56.400 align:start position:0% decentralized web we actually have a 00:05:56.400 --> 00:05:58.100 align:start position:0% decentralized web we actually have a partnership<00:05:56.760> with<00:05:56.910> protocol<00:05:57.480> labs<00:05:57.720> of 00:05:58.100 --> 00:05:58.110 align:start position:0% partnership with protocol labs of 00:05:58.110 --> 00:05:59.750 align:start position:0% partnership with protocol labs of building<00:05:58.410> out<00:05:58.500> infrastructure<00:05:58.980> on<00:05:59.280> this<00:05:59.520> and 00:05:59.750 --> 00:05:59.760 align:start position:0% building out infrastructure on this and 00:05:59.760 --> 00:06:03.370 align:start position:0% building out infrastructure on this and promoting<00:06:00.720> this<00:06:00.900> kind<00:06:00.960> of<00:06:01.170> duo<00:06:01.440> of<00:06:02.040> protocols 00:06:03.370 --> 00:06:03.380 align:start position:0% promoting this kind of duo of protocols 00:06:03.380 --> 00:06:06.700 align:start position:0% promoting this kind of duo of protocols we<00:06:04.380> already<00:06:04.740> have<00:06:05.010> native<00:06:05.580> support<00:06:05.610> for<00:06:06.390> this 00:06:06.700 --> 00:06:06.710 align:start position:0% we already have native support for this 00:06:06.710 --> 00:06:11.180 align:start position:0% we already have native support for this pair<00:06:07.710> of<00:06:08.120> protocols<00:06:09.120> in<00:06:09.420> the<00:06:09.930> in<00:06:10.530> Opera<00:06:11.010> and 00:06:11.180 --> 00:06:11.190 align:start position:0% pair of protocols in the in Opera and 00:06:11.190 --> 00:06:13.400 align:start position:0% pair of protocols in the in Opera and brave<00:06:12.060> says<00:06:12.450> they<00:06:12.630> are<00:06:12.720> also<00:06:12.900> working<00:06:13.230> on 00:06:13.400 --> 00:06:13.410 align:start position:0% brave says they are also working on 00:06:13.410 --> 00:06:15.830 align:start position:0% brave says they are also working on adding<00:06:13.620> this<00:06:13.860> so<00:06:14.100> we<00:06:14.820> are<00:06:14.940> getting<00:06:15.090> a<00:06:15.390> native 00:06:15.830 --> 00:06:15.840 align:start position:0% adding this so we are getting a native 00:06:15.840 --> 00:06:18.680 align:start position:0% adding this so we are getting a native browser<00:06:16.320> support<00:06:16.800> but<00:06:17.790> if<00:06:18.090> you're<00:06:18.360> using<00:06:18.480> a 00:06:18.680 --> 00:06:18.690 align:start position:0% browser support but if you're using a 00:06:18.690 --> 00:06:19.930 align:start position:0% browser support but if you're using a browser<00:06:18.900> that<00:06:19.080> doesn't<00:06:19.410> have<00:06:19.500> native<00:06:19.710> support 00:06:19.930 --> 00:06:19.940 align:start position:0% browser that doesn't have native support 00:06:19.940 --> 00:06:23.840 align:start position:0% browser that doesn't have native support we<00:06:20.940> benefit<00:06:21.390> from<00:06:21.420> the<00:06:21.720> from<00:06:22.290> meta<00:06:22.470> mask<00:06:22.850> meta 00:06:23.840 --> 00:06:23.850 align:start position:0% we benefit from the from meta mask meta 00:06:23.850 --> 00:06:26.810 align:start position:0% we benefit from the from meta mask meta mask<00:06:24.090> supports<00:06:25.050> this<00:06:25.230> so<00:06:26.040> if<00:06:26.160> you<00:06:26.370> are<00:06:26.520> using 00:06:26.810 --> 00:06:26.820 align:start position:0% mask supports this so if you are using 00:06:26.820 --> 00:06:29.060 align:start position:0% mask supports this so if you are using Chrome<00:06:27.060> Firefox<00:06:27.450> edge<00:06:28.050> brave<00:06:28.530> or<00:06:28.740> even<00:06:28.980> the 00:06:29.060 --> 00:06:29.070 align:start position:0% Chrome Firefox edge brave or even the 00:06:29.070 --> 00:06:30.470 align:start position:0% Chrome Firefox edge brave or even the tor<00:06:29.280> browser<00:06:29.400> which<00:06:29.850> we'll<00:06:29.970> be<00:06:30.060> talking<00:06:30.210> about 00:06:30.470 --> 00:06:30.480 align:start position:0% tor browser which we'll be talking about 00:06:30.480 --> 00:06:31.820 align:start position:0% tor browser which we'll be talking about here<00:06:30.750> in<00:06:30.810> a<00:06:30.870> second 00:06:31.820 --> 00:06:31.830 align:start position:0% here in a second 00:06:31.830 --> 00:06:35.810 align:start position:0% here in a second you<00:06:32.450> automatically<00:06:34.070> support<00:06:35.070> this 00:06:35.810 --> 00:06:35.820 align:start position:0% you automatically support this 00:06:35.820 --> 00:06:38.360 align:start position:0% you automatically support this decentralized<00:06:36.300> web<00:06:36.660> and<00:06:37.590> you<00:06:38.070> can<00:06:38.190> try<00:06:38.340> it 00:06:38.360 --> 00:06:38.370 align:start position:0% decentralized web and you can try it 00:06:38.370 --> 00:06:41.300 align:start position:0% decentralized web and you can try it right<00:06:38.460> now<00:06:38.700> actually<00:06:38.910> so<00:06:39.330> we<00:06:39.450> recommend<00:06:40.350> this 00:06:41.300 --> 00:06:41.310 align:start position:0% right now actually so we recommend this 00:06:41.310 --> 00:06:43.490 align:start position:0% right now actually so we recommend this is<00:06:41.460> a<00:06:41.490> great<00:06:41.700> starting<00:06:42.030> place<00:06:42.150> I'll<00:06:42.390> monitor 00:06:43.490 --> 00:06:43.500 align:start position:0% is a great starting place I'll monitor 00:06:43.500 --> 00:06:45.950 align:start position:0% is a great starting place I'll monitor 'if<00:06:43.650> if<00:06:44.640> you<00:06:44.790> have<00:06:45.030> to<00:06:45.090> put<00:06:45.210> a<00:06:45.240> slash<00:06:45.600> at<00:06:45.930> the 00:06:45.950 --> 00:06:45.960 align:start position:0% 'if if you have to put a slash at the 00:06:45.960 --> 00:06:47.300 align:start position:0% 'if if you have to put a slash at the end<00:06:46.170> of<00:06:46.290> here<00:06:46.380> if<00:06:46.590> you're<00:06:46.770> doing<00:06:46.920> it<00:06:47.100> in<00:06:47.190> meta 00:06:47.300 --> 00:06:47.310 align:start position:0% end of here if you're doing it in meta 00:06:47.310 --> 00:06:49.040 align:start position:0% end of here if you're doing it in meta masks<00:06:47.730> so<00:06:47.880> it'll<00:06:48.330> recognize<00:06:48.510> that<00:06:48.900> it 00:06:49.040 --> 00:06:49.050 align:start position:0% masks so it'll recognize that it 00:06:49.050 --> 00:06:51.950 align:start position:0% masks so it'll recognize that it recognized<00:06:49.440> it<00:06:49.470> if<00:06:50.190> you<00:06:50.340> type<00:06:50.550> this<00:06:50.730> in<00:06:50.970> it'll 00:06:51.950 --> 00:06:51.960 align:start position:0% recognized it if you type this in it'll 00:06:51.960 --> 00:06:55.660 align:start position:0% recognized it if you type this in it'll it'll<00:06:52.140> load<00:06:52.350> up<00:06:52.500> and<00:06:52.880> this<00:06:53.880> is<00:06:53.940> a<00:06:54.090> directory<00:06:54.750> of 00:06:55.660 --> 00:06:55.670 align:start position:0% it'll load up and this is a directory of 00:06:55.670 --> 00:06:58.370 align:start position:0% it'll load up and this is a directory of websites<00:06:56.670> decentralize<00:06:57.270> websites<00:06:57.690> this<00:06:58.170> is<00:06:58.320> a 00:06:58.370 --> 00:06:58.380 align:start position:0% websites decentralize websites this is a 00:06:58.380 --> 00:06:59.690 align:start position:0% websites decentralize websites this is a great<00:06:58.590> place<00:06:58.800> to<00:06:58.830> start<00:06:59.130> this<00:06:59.340> works<00:06:59.520> right 00:06:59.690 --> 00:06:59.700 align:start position:0% great place to start this works right 00:06:59.700 --> 00:07:03.860 align:start position:0% great place to start this works right now<00:07:01.460> we<00:07:02.460> also<00:07:02.610> have<00:07:02.760> a<00:07:02.790> project<00:07:03.120> called<00:07:03.180> if<00:07:03.420> DNS 00:07:03.860 --> 00:07:03.870 align:start position:0% now we also have a project called if DNS 00:07:03.870 --> 00:07:06.230 align:start position:0% now we also have a project called if DNS which<00:07:04.110> is<00:07:04.230> a<00:07:04.320> bridge<00:07:04.500> between<00:07:04.710> DNS<00:07:05.640> and<00:07:05.880> en<00:07:06.120> s 00:07:06.230 --> 00:07:06.240 align:start position:0% which is a bridge between DNS and en s 00:07:06.240 --> 00:07:09.170 align:start position:0% which is a bridge between DNS and en s plus<00:07:06.450> IP<00:07:06.750> FS<00:07:07.100> there's<00:07:08.100> much<00:07:08.700> more<00:07:08.880> that<00:07:08.940> can<00:07:09.120> be 00:07:09.170 --> 00:07:09.180 align:start position:0% plus IP FS there's much more that can be 00:07:09.180 --> 00:07:10.340 align:start position:0% plus IP FS there's much more that can be said<00:07:09.270> about<00:07:09.450> this<00:07:09.720> we<00:07:09.930> have<00:07:09.960> she<00:07:10.110> just 00:07:10.340 --> 00:07:10.350 align:start position:0% said about this we have she just 00:07:10.350 --> 00:07:12.020 align:start position:0% said about this we have she just published<00:07:10.710> a<00:07:10.800> blog<00:07:10.920> post<00:07:11.310> yesterday<00:07:11.550> with 00:07:12.020 --> 00:07:12.030 align:start position:0% published a blog post yesterday with 00:07:12.030 --> 00:07:13.580 align:start position:0% published a blog post yesterday with more<00:07:12.210> details<00:07:12.570> to<00:07:12.720> go<00:07:12.840> to<00:07:12.900> our<00:07:13.050> medium<00:07:13.380> check 00:07:13.580 --> 00:07:13.590 align:start position:0% more details to go to our medium check 00:07:13.590 --> 00:07:13.970 align:start position:0% more details to go to our medium check it<00:07:13.680> out 00:07:13.970 --> 00:07:13.980 align:start position:0% it out 00:07:13.980 --> 00:07:16.790 align:start position:0% it out but<00:07:14.760> for<00:07:15.030> users<00:07:15.360> the<00:07:15.600> bottom<00:07:15.870> line<00:07:16.080> is<00:07:16.350> we've 00:07:16.790 --> 00:07:16.800 align:start position:0% but for users the bottom line is we've 00:07:16.800 --> 00:07:20.150 align:start position:0% but for users the bottom line is we've we<00:07:17.130> own<00:07:17.370> eath<00:07:17.700> link<00:07:18.450> on<00:07:18.660> DNS<00:07:19.440> we've<00:07:19.740> set<00:07:19.980> up<00:07:20.010> a 00:07:20.150 --> 00:07:20.160 align:start position:0% we own eath link on DNS we've set up a 00:07:20.160 --> 00:07:22.520 align:start position:0% we own eath link on DNS we've set up a special<00:07:20.280> server<00:07:20.730> there<00:07:21.000> so<00:07:21.630> that<00:07:21.840> if<00:07:22.080> there<00:07:22.350> is 00:07:22.520 --> 00:07:22.530 align:start position:0% special server there so that if there is 00:07:22.530 --> 00:07:25.580 align:start position:0% special server there so that if there is a<00:07:22.610> decentralized<00:07:23.610> website<00:07:24.480> and<00:07:24.780> you<00:07:25.290> don't 00:07:25.580 --> 00:07:25.590 align:start position:0% a decentralized website and you don't 00:07:25.590 --> 00:07:27.440 align:start position:0% a decentralized website and you don't have<00:07:25.800> meta<00:07:26.070> mask<00:07:26.310> you're<00:07:26.669> not<00:07:26.790> using<00:07:26.970> opera 00:07:27.440 --> 00:07:27.450 align:start position:0% have meta mask you're not using opera 00:07:27.450 --> 00:07:29.780 align:start position:0% have meta mask you're not using opera you<00:07:27.870> can<00:07:28.020> still<00:07:28.230> access<00:07:28.380> it<00:07:28.710> just<00:07:28.919> add<00:07:29.460> dot 00:07:29.780 --> 00:07:29.790 align:start position:0% you can still access it just add dot 00:07:29.790 --> 00:07:31.250 align:start position:0% you can still access it just add dot link<00:07:30.060> to<00:07:30.419> the<00:07:30.540> end<00:07:30.660> of<00:07:30.780> it<00:07:30.870> and<00:07:31.020> it<00:07:31.169> will 00:07:31.250 --> 00:07:31.260 align:start position:0% link to the end of it and it will 00:07:31.260 --> 00:07:34.040 align:start position:0% link to the end of it and it will resolve<00:07:31.620> like<00:07:31.800> a<00:07:31.830> normal<00:07:32.160> website<00:07:32.750> so<00:07:33.750> this<00:07:33.930> is 00:07:34.040 --> 00:07:34.050 align:start position:0% resolve like a normal website so this is 00:07:34.050 --> 00:07:35.780 align:start position:0% resolve like a normal website so this is a<00:07:34.080> great<00:07:34.470> way<00:07:34.740> if<00:07:34.770> you<00:07:35.160> if<00:07:35.340> you<00:07:35.430> want<00:07:35.580> to<00:07:35.610> put 00:07:35.780 --> 00:07:35.790 align:start position:0% a great way if you if you want to put 00:07:35.790 --> 00:07:38.510 align:start position:0% a great way if you if you want to put your<00:07:35.940> your<00:07:36.360> daps<00:07:36.660> front<00:07:37.200> end<00:07:37.380> on<00:07:37.530> ipfs<00:07:38.190> to<00:07:38.370> make 00:07:38.510 --> 00:07:38.520 align:start position:0% your your daps front end on ipfs to make 00:07:38.520 --> 00:07:41.060 align:start position:0% your your daps front end on ipfs to make it<00:07:38.669> accessible<00:07:38.970> via<00:07:39.540> ens<00:07:40.020> but<00:07:40.620> you<00:07:40.680> still<00:07:40.919> want 00:07:41.060 --> 00:07:41.070 align:start position:0% it accessible via ens but you still want 00:07:41.070 --> 00:07:42.440 align:start position:0% it accessible via ens but you still want normal<00:07:41.370> people<00:07:41.669> to<00:07:41.730> be<00:07:41.820> able<00:07:41.910> to<00:07:42.000> be<00:07:42.180> able<00:07:42.270> to 00:07:42.440 --> 00:07:42.450 align:start position:0% normal people to be able to be able to 00:07:42.450 --> 00:07:48.469 align:start position:0% normal people to be able to be able to access<00:07:42.680> access<00:07:43.680> it<00:07:44.330> use<00:07:45.330> this<00:07:46.610> as<00:07:47.610> two<00:07:48.240> tore 00:07:48.469 --> 00:07:48.479 align:start position:0% access access it use this as two tore 00:07:48.479 --> 00:07:53.060 align:start position:0% access access it use this as two tore down<00:07:48.570> onion<00:07:48.870> addresses<00:07:51.530> so<00:07:52.530> toward<00:07:52.830> on<00:07:52.919> an 00:07:53.060 --> 00:07:53.070 align:start position:0% down onion addresses so toward on an 00:07:53.070 --> 00:07:56.330 align:start position:0% down onion addresses so toward on an onion<00:07:53.720> web<00:07:54.720> sites<00:07:55.050> I've<00:07:55.740> been<00:07:55.950> around<00:07:56.070> for<00:07:56.220> a 00:07:56.330 --> 00:07:56.340 align:start position:0% onion web sites I've been around for a 00:07:56.340 --> 00:07:58.880 align:start position:0% onion web sites I've been around for a while<00:07:56.400> they<00:07:56.790> have<00:07:56.940> a<00:07:56.970> naming<00:07:57.210> problem<00:07:57.890> they 00:07:58.880 --> 00:07:58.890 align:start position:0% while they have a naming problem they 00:07:58.890 --> 00:08:01.490 align:start position:0% while they have a naming problem they have<00:07:59.250> the<00:07:59.370> same<00:07:59.550> naming<00:08:00.419> problem<00:08:00.960> that<00:08:01.110> normal 00:08:01.490 --> 00:08:01.500 align:start position:0% have the same naming problem that normal 00:08:01.500 --> 00:08:05.870 align:start position:0% have the same naming problem that normal websites<00:08:01.860> would<00:08:02.040> have<00:08:02.330> that<00:08:03.330> they<00:08:03.479> have<00:08:04.880> you 00:08:05.870 --> 00:08:05.880 align:start position:0% websites would have that they have you 00:08:05.880 --> 00:08:08.000 align:start position:0% websites would have that they have you know<00:08:05.970> an<00:08:06.090> address<00:08:06.479> to<00:08:06.600> find<00:08:06.750> the<00:08:06.930> server<00:08:07.169> they 00:08:08.000 --> 00:08:08.010 align:start position:0% know an address to find the server they 00:08:08.010 --> 00:08:09.290 align:start position:0% know an address to find the server they need<00:08:08.190> a<00:08:08.220> naming<00:08:08.490> system<00:08:08.760> but<00:08:09.030> they<00:08:09.120> don't 00:08:09.290 --> 00:08:09.300 align:start position:0% need a naming system but they don't 00:08:09.300 --> 00:08:11.600 align:start position:0% need a naming system but they don't trust<00:08:09.570> DNS<00:08:10.110> because<00:08:10.410> DNS<00:08:10.770> is<00:08:10.919> insecure<00:08:11.220> it's 00:08:11.600 --> 00:08:11.610 align:start position:0% trust DNS because DNS is insecure it's 00:08:11.610 --> 00:08:13.280 align:start position:0% trust DNS because DNS is insecure it's centralized<00:08:12.120> right<00:08:12.450> and<00:08:12.660> tor<00:08:12.810> is<00:08:12.900> all<00:08:13.050> about 00:08:13.280 --> 00:08:13.290 align:start position:0% centralized right and tor is all about 00:08:13.290 --> 00:08:16.850 align:start position:0% centralized right and tor is all about security<00:08:13.620> so<00:08:15.080> right<00:08:16.080> now<00:08:16.260> if<00:08:16.440> you<00:08:16.560> wanted<00:08:16.770> to 00:08:16.850 --> 00:08:16.860 align:start position:0% security so right now if you wanted to 00:08:16.860 --> 00:08:18.890 align:start position:0% security so right now if you wanted to go<00:08:16.950> to<00:08:16.979> a<00:08:17.100> dawn<00:08:17.310> onion<00:08:17.610> web<00:08:18.120> site<00:08:18.360> in<00:08:18.600> the<00:08:18.720> tor 00:08:18.890 --> 00:08:18.900 align:start position:0% go to a dawn onion web site in the tor 00:08:18.900 --> 00:08:20.030 align:start position:0% go to a dawn onion web site in the tor browser<00:08:18.930> you<00:08:19.320> have<00:08:19.410> to<00:08:19.500> go<00:08:19.590> to<00:08:19.650> something<00:08:19.830> like 00:08:20.030 --> 00:08:20.040 align:start position:0% browser you have to go to something like 00:08:20.040 --> 00:08:21.320 align:start position:0% browser you have to go to something like this<00:08:20.280> right<00:08:20.580> this<00:08:20.729> is<00:08:20.790> very<00:08:21.030> non 00:08:21.320 --> 00:08:21.330 align:start position:0% this right this is very non 00:08:21.330 --> 00:08:28.640 align:start position:0% this right this is very non user-friendly<00:08:25.520> ens<00:08:26.520> solves<00:08:27.479> this<00:08:27.570> problem<00:08:27.750> so 00:08:28.640 --> 00:08:28.650 align:start position:0% user-friendly ens solves this problem so 00:08:28.650 --> 00:08:30.650 align:start position:0% user-friendly ens solves this problem so ens<00:08:29.070> is<00:08:29.220> obviously<00:08:29.550> a<00:08:29.640> decentralized<00:08:30.240> secure 00:08:30.650 --> 00:08:30.660 align:start position:0% ens is obviously a decentralized secure 00:08:30.660 --> 00:08:34.070 align:start position:0% ens is obviously a decentralized secure naming<00:08:31.380> solution<00:08:31.950> that<00:08:32.430> works<00:08:32.640> today<00:08:33.080> and 00:08:34.070 --> 00:08:34.080 align:start position:0% naming solution that works today and 00:08:34.080 --> 00:08:36.230 align:start position:0% naming solution that works today and we've<00:08:34.380> added<00:08:34.530> support<00:08:34.770> for<00:08:35.039> denim<00:08:35.610> dresses<00:08:36.030> in 00:08:36.230 --> 00:08:36.240 align:start position:0% we've added support for denim dresses in 00:08:36.240 --> 00:08:40.520 align:start position:0% we've added support for denim dresses in our<00:08:36.419> in<00:08:37.080> our<00:08:37.469> records<00:08:38.690> and<00:08:39.690> you<00:08:39.990> can<00:08:40.169> use<00:08:40.349> this 00:08:40.520 --> 00:08:40.530 align:start position:0% our in our records and you can use this 00:08:40.530 --> 00:08:42.500 align:start position:0% our in our records and you can use this in<00:08:40.770> the<00:08:41.010> tor<00:08:41.219> browser<00:08:41.339> if<00:08:41.760> you<00:08:41.789> have<00:08:42.120> metamath 00:08:42.500 --> 00:08:42.510 align:start position:0% in the tor browser if you have metamath 00:08:42.510 --> 00:08:44.480 align:start position:0% in the tor browser if you have metamath so<00:08:42.810> so<00:08:42.990> the<00:08:43.110> tor<00:08:43.289> browser<00:08:43.409> is<00:08:43.710> Firefox<00:08:43.890> based 00:08:44.480 --> 00:08:44.490 align:start position:0% so so the tor browser is Firefox based 00:08:44.490 --> 00:08:48.230 align:start position:0% so so the tor browser is Firefox based and<00:08:45.180> if<00:08:45.270> you<00:08:45.480> add<00:08:45.690> in<00:08:45.960> the<00:08:46.610> put<00:08:47.610> in<00:08:47.730> the<00:08:47.880> add-on 00:08:48.230 --> 00:08:48.240 align:start position:0% and if you add in the put in the add-on 00:08:48.240 --> 00:08:51.890 align:start position:0% and if you add in the put in the add-on meta<00:08:48.660> mask<00:08:49.130> and<00:08:50.130> you<00:08:50.910> type<00:08:51.180> in<00:08:51.360> a<00:08:51.510> dot<00:08:51.720> eath 00:08:51.890 --> 00:08:51.900 align:start position:0% meta mask and you type in a dot eath 00:08:51.900 --> 00:08:53.600 align:start position:0% meta mask and you type in a dot eath name<00:08:52.200> that<00:08:52.620> has<00:08:52.740> a<00:08:52.770> tour<00:08:53.190> down<00:08:53.310> any<00:08:53.459> addresses 00:08:53.600 --> 00:08:53.610 align:start position:0% name that has a tour down any addresses 00:08:53.610 --> 00:08:55.970 align:start position:0% name that has a tour down any addresses records<00:08:54.270> it<00:08:54.630> will<00:08:55.020> resolve<00:08:55.350> to<00:08:55.560> that<00:08:55.709> toward 00:08:55.970 --> 00:08:55.980 align:start position:0% records it will resolve to that toward 00:08:55.980 --> 00:08:57.229 align:start position:0% records it will resolve to that toward onion<00:08:56.310> websites 00:08:57.229 --> 00:08:57.239 align:start position:0% onion websites 00:08:57.239 --> 00:09:01.759 align:start position:0% onion websites so<00:08:57.689> this<00:08:57.869> works<00:08:58.079> today<00:09:00.319> you<00:09:01.319> can<00:09:01.439> try<00:09:01.649> it<00:09:01.709> right 00:09:01.759 --> 00:09:01.769 align:start position:0% so this works today you can try it right 00:09:01.769 --> 00:09:03.949 align:start position:0% so this works today you can try it right now<00:09:01.979> so<00:09:02.189> we<00:09:02.279> actually<00:09:02.399> set<00:09:02.759> up<00:09:02.879> ten<00:09:03.209> ten<00:09:03.869> of 00:09:03.949 --> 00:09:03.959 align:start position:0% now so we actually set up ten ten of 00:09:03.959 --> 00:09:06.529 align:start position:0% now so we actually set up ten ten of these<00:09:04.109> addresses<00:09:04.769> I<00:09:05.099> to<00:09:05.489> kind<00:09:05.699> of<00:09:05.729> show<00:09:06.329> off 00:09:06.529 --> 00:09:06.539 align:start position:0% these addresses I to kind of show off 00:09:06.539 --> 00:09:09.319 align:start position:0% these addresses I to kind of show off this<00:09:06.719> functionality<00:09:07.139> so<00:09:07.829> like<00:09:08.329> DuckDuckGo 00:09:09.319 --> 00:09:09.329 align:start position:0% this functionality so like DuckDuckGo 00:09:09.329 --> 00:09:12.499 align:start position:0% this functionality so like DuckDuckGo tour<00:09:09.689> death<00:09:10.159> Facebook<00:09:11.159> toured<00:09:11.429> eath<00:09:11.759> and<00:09:11.969> all 00:09:12.499 --> 00:09:12.509 align:start position:0% tour death Facebook toured eath and all 00:09:12.509 --> 00:09:15.739 align:start position:0% tour death Facebook toured eath and all these<00:09:12.779> here<00:09:13.159> and<00:09:14.159> we<00:09:14.669> actually<00:09:14.849> set<00:09:15.359> these<00:09:15.539> up 00:09:15.739 --> 00:09:15.749 align:start position:0% these here and we actually set these up 00:09:15.749 --> 00:09:18.079 align:start position:0% these here and we actually set these up and<00:09:15.989> then<00:09:16.139> we<00:09:16.289> gave<00:09:16.469> up<00:09:16.679> control<00:09:16.859> of<00:09:17.189> them<00:09:17.459> so 00:09:18.079 --> 00:09:18.089 align:start position:0% and then we gave up control of them so 00:09:18.089 --> 00:09:20.389 align:start position:0% and then we gave up control of them so we<00:09:18.569> can't<00:09:18.899> change<00:09:19.379> the<00:09:19.679> addresses<00:09:20.129> here<00:09:20.249> so 00:09:20.389 --> 00:09:20.399 align:start position:0% we can't change the addresses here so 00:09:20.399 --> 00:09:21.709 align:start position:0% we can't change the addresses here so this<00:09:20.489> actually<00:09:20.819> is<00:09:20.849> showing<00:09:21.029> off<00:09:21.509> another 00:09:21.709 --> 00:09:21.719 align:start position:0% this actually is showing off another 00:09:21.719 --> 00:09:23.779 align:start position:0% this actually is showing off another functionality<00:09:22.439> of<00:09:22.529> ens<00:09:22.859> this<00:09:23.309> is<00:09:23.459> to<00:09:23.519> prevent 00:09:23.779 --> 00:09:23.789 align:start position:0% functionality of ens this is to prevent 00:09:23.789 --> 00:09:26.299 align:start position:0% functionality of ens this is to prevent phishing<00:09:24.199> you<00:09:25.199> know<00:09:25.289> if<00:09:25.379> I<00:09:25.469> if<00:09:25.499> I<00:09:25.769> set<00:09:25.979> this<00:09:26.099> up 00:09:26.299 --> 00:09:26.309 align:start position:0% phishing you know if I if I set this up 00:09:26.309 --> 00:09:28.159 align:start position:0% phishing you know if I if I set this up I<00:09:26.489> I<00:09:26.549> could<00:09:26.879> set<00:09:27.089> up<00:09:27.179> correctly<00:09:27.449> you<00:09:27.839> could 00:09:28.159 --> 00:09:28.169 align:start position:0% I I could set up correctly you could 00:09:28.169 --> 00:09:30.049 align:start position:0% I I could set up correctly you could start<00:09:28.409> using<00:09:28.619> it<00:09:28.919> and<00:09:28.949> then<00:09:29.219> I<00:09:29.339> could<00:09:29.639> if<00:09:29.969> I 00:09:30.049 --> 00:09:30.059 align:start position:0% start using it and then I could if I 00:09:30.059 --> 00:09:31.819 align:start position:0% start using it and then I could if I really<00:09:30.299> wanted<00:09:30.539> to<00:09:30.629> be<00:09:31.019> bad<00:09:31.229> I<00:09:31.529> could<00:09:31.739> then 00:09:31.819 --> 00:09:31.829 align:start position:0% really wanted to be bad I could then 00:09:31.829 --> 00:09:33.979 align:start position:0% really wanted to be bad I could then change<00:09:32.159> it<00:09:32.339> to<00:09:32.369> a<00:09:32.849> different<00:09:33.269> address<00:09:33.629> and 00:09:33.979 --> 00:09:33.989 align:start position:0% change it to a different address and 00:09:33.989 --> 00:09:35.239 align:start position:0% change it to a different address and then<00:09:34.079> you<00:09:34.199> might<00:09:34.349> not<00:09:34.499> know<00:09:34.679> that<00:09:34.709> I<00:09:34.889> changed 00:09:35.239 --> 00:09:35.249 align:start position:0% then you might not know that I changed 00:09:35.249 --> 00:09:37.129 align:start position:0% then you might not know that I changed it<00:09:35.369> so<00:09:35.459> you're<00:09:35.609> going<00:09:35.789> to<00:09:36.029> and<00:09:36.149> I<00:09:36.179> could<00:09:36.629> go<00:09:37.079> to 00:09:37.129 --> 00:09:37.139 align:start position:0% it so you're going to and I could go to 00:09:37.139 --> 00:09:38.419 align:start position:0% it so you're going to and I could go to a<00:09:37.229> phishing<00:09:37.589> website<00:09:37.979> or<00:09:38.069> something<00:09:38.309> like 00:09:38.419 --> 00:09:38.429 align:start position:0% a phishing website or something like 00:09:38.429 --> 00:09:40.699 align:start position:0% a phishing website or something like that<00:09:38.579> I<00:09:38.789> can't<00:09:39.059> do<00:09:39.509> that<00:09:39.719> so<00:09:40.109> actually<00:09:40.379> nobody 00:09:40.699 --> 00:09:40.709 align:start position:0% that I can't do that so actually nobody 00:09:40.709 --> 00:09:43.309 align:start position:0% that I can't do that so actually nobody owns<00:09:40.889> these<00:09:41.129> addresses<00:09:42.029> but<00:09:42.809> they<00:09:42.899> still<00:09:43.139> work 00:09:43.309 --> 00:09:43.319 align:start position:0% owns these addresses but they still work 00:09:43.319 --> 00:09:45.139 align:start position:0% owns these addresses but they still work that's<00:09:44.069> something<00:09:44.279> you<00:09:44.369> can't<00:09:44.579> do<00:09:44.729> with<00:09:44.759> DNS 00:09:45.139 --> 00:09:45.149 align:start position:0% that's something you can't do with DNS 00:09:45.149 --> 00:09:46.939 align:start position:0% that's something you can't do with DNS by<00:09:45.389> the<00:09:45.449> way<00:09:45.569> somebody<00:09:45.779> always<00:09:46.079> controls<00:09:46.739> the 00:09:46.939 --> 00:09:46.949 align:start position:0% by the way somebody always controls the 00:09:46.949 --> 00:09:49.669 align:start position:0% by the way somebody always controls the DNS<00:09:47.249> records 00:09:49.669 --> 00:09:49.679 align:start position:0% 00:09:49.679 --> 00:09:52.609 align:start position:0% who<00:09:50.189> is<00:09:50.369> actually<00:09:50.729> just<00:09:50.909> launched<00:09:51.389> this<00:09:51.619> with 00:09:52.609 --> 00:09:52.619 align:start position:0% who is actually just launched this with 00:09:52.619 --> 00:09:56.149 align:start position:0% who is actually just launched this with text<00:09:53.159> records<00:09:53.489> in<00:09:53.759> our<00:09:54.209> manager<00:09:54.829> you<00:09:55.829> can<00:09:56.009> now 00:09:56.149 --> 00:09:56.159 align:start position:0% text records in our manager you can now 00:09:56.159 --> 00:09:58.459 align:start position:0% text records in our manager you can now to<00:09:56.789> put<00:09:56.939> it<00:09:56.969> to<00:09:57.179> any<00:09:57.359> ENS<00:09:57.719> naming<00:09:58.049> put<00:09:58.229> like<00:09:58.349> an 00:09:58.459 --> 00:09:58.469 align:start position:0% to put it to any ENS naming put like an 00:09:58.469 --> 00:10:00.979 align:start position:0% to put it to any ENS naming put like an email<00:09:58.769> address<00:09:58.919> website<00:09:59.459> a<00:10:00.029> link<00:10:00.539> to<00:10:00.749> an 00:10:00.979 --> 00:10:00.989 align:start position:0% email address website a link to an 00:10:00.989 --> 00:10:03.199 align:start position:0% email address website a link to an avatar<00:10:01.469> a<00:10:01.739> description<00:10:02.399> anything<00:10:02.819> you<00:10:02.909> wants 00:10:03.199 --> 00:10:03.209 align:start position:0% avatar a description anything you wants 00:10:03.209 --> 00:10:04.939 align:start position:0% avatar a description anything you wants like<00:10:03.599> if<00:10:03.719> you're<00:10:03.839> trying<00:10:03.959> to<00:10:04.049> sell<00:10:04.349> a<00:10:04.379> name<00:10:04.679> or 00:10:04.939 --> 00:10:04.949 align:start position:0% like if you're trying to sell a name or 00:10:04.949 --> 00:10:06.139 align:start position:0% like if you're trying to sell a name or if<00:10:05.069> you<00:10:05.129> just<00:10:05.249> want<00:10:05.429> people<00:10:05.639> to<00:10:05.699> know<00:10:05.819> who<00:10:05.999> you 00:10:06.139 --> 00:10:06.149 align:start position:0% if you just want people to know who you 00:10:06.149 --> 00:10:08.389 align:start position:0% if you just want people to know who you are<00:10:06.179> or<00:10:06.359> however<00:10:06.899> you<00:10:07.229> want<00:10:07.379> to<00:10:07.409> use<00:10:07.469> it<00:10:07.709> this 00:10:08.389 --> 00:10:08.399 align:start position:0% are or however you want to use it this 00:10:08.399 --> 00:10:11.719 align:start position:0% are or however you want to use it this works<00:10:08.609> right<00:10:08.879> now<00:10:09.079> and<00:10:10.399> that<00:10:11.399> we're<00:10:11.519> going<00:10:11.669> to 00:10:11.719 --> 00:10:11.729 align:start position:0% works right now and that we're going to 00:10:11.729 --> 00:10:13.729 align:start position:0% works right now and that we're going to be<00:10:11.789> adding<00:10:12.119> the<00:10:12.269> ability<00:10:12.569> to<00:10:12.629> put<00:10:12.779> custom<00:10:13.199> text 00:10:13.729 --> 00:10:13.739 align:start position:0% be adding the ability to put custom text 00:10:13.739 --> 00:10:16.339 align:start position:0% be adding the ability to put custom text records<00:10:14.039> very<00:10:14.249> soon<00:10:14.929> this<00:10:15.929> is<00:10:16.019> what<00:10:16.139> it<00:10:16.199> looks 00:10:16.339 --> 00:10:16.349 align:start position:0% records very soon this is what it looks 00:10:16.349 --> 00:10:20.659 align:start position:0% records very soon this is what it looks like<00:10:16.409> in<00:10:16.799> our<00:10:16.919> manager<00:10:19.669> other 00:10:20.659 --> 00:10:20.669 align:start position:0% like in our manager other 00:10:20.669 --> 00:10:21.709 align:start position:0% like in our manager other cryptocurrencies 00:10:21.709 --> 00:10:21.719 align:start position:0% cryptocurrencies 00:10:21.719 --> 00:10:23.869 align:start position:0% cryptocurrencies so<00:10:21.869> you<00:10:21.929> heard<00:10:22.829> would<00:10:23.309> have<00:10:23.399> heard<00:10:23.579> about<00:10:23.639> this 00:10:23.869 --> 00:10:23.879 align:start position:0% so you heard would have heard about this 00:10:23.879 --> 00:10:26.029 align:start position:0% so you heard would have heard about this yesterday<00:10:24.179> if<00:10:24.659> you<00:10:24.689> saw<00:10:25.049> Nick<00:10:25.349> Johnson<00:10:25.799> our 00:10:26.029 --> 00:10:26.039 align:start position:0% yesterday if you saw Nick Johnson our 00:10:26.039 --> 00:10:29.479 align:start position:0% yesterday if you saw Nick Johnson our Lee<00:10:26.219> developers<00:10:26.669> presentation<00:10:27.949> but<00:10:28.949> we<00:10:28.979> just 00:10:29.479 --> 00:10:29.489 align:start position:0% Lee developers presentation but we just 00:10:29.489 --> 00:10:31.639 align:start position:0% Lee developers presentation but we just added<00:10:29.699> multi-point<00:10:30.299> support<00:10:30.719> on<00:10:30.929> maintenance 00:10:31.639 --> 00:10:31.649 align:start position:0% added multi-point support on maintenance 00:10:31.649 --> 00:10:34.519 align:start position:0% added multi-point support on maintenance it<00:10:32.039> works<00:10:32.189> right<00:10:32.459> now<00:10:32.599> at<00:10:33.599> least<00:10:33.779> on<00:10:33.989> DNS 00:10:34.519 --> 00:10:34.529 align:start position:0% it works right now at least on DNS 00:10:34.529 --> 00:10:38.209 align:start position:0% it works right now at least on DNS protocol<00:10:34.769> level<00:10:35.099> and<00:10:36.469> basically<00:10:37.469> it<00:10:38.039> works 00:10:38.209 --> 00:10:38.219 align:start position:0% protocol level and basically it works 00:10:38.219 --> 00:10:40.339 align:start position:0% protocol level and basically it works the<00:10:38.429> same<00:10:38.459> way<00:10:38.849> as<00:10:39.329> with<00:10:39.599> aetherium<00:10:39.959> addresses 00:10:40.339 --> 00:10:40.349 align:start position:0% the same way as with aetherium addresses 00:10:40.349 --> 00:10:41.929 align:start position:0% the same way as with aetherium addresses you<00:10:40.439> just<00:10:40.619> store<00:10:40.859> like<00:10:41.189> the<00:10:41.339> Bitcoin<00:10:41.639> address 00:10:41.929 --> 00:10:41.939 align:start position:0% you just store like the Bitcoin address 00:10:41.939 --> 00:10:43.849 align:start position:0% you just store like the Bitcoin address or<00:10:42.149> EOC<00:10:42.389> dress<00:10:42.839> or<00:10:42.989> something<00:10:43.199> like<00:10:43.349> that<00:10:43.439> in 00:10:43.849 --> 00:10:43.859 align:start position:0% or EOC dress or something like that in 00:10:43.859 --> 00:10:46.789 align:start position:0% or EOC dress or something like that in the<00:10:44.219> record<00:10:44.519> and<00:10:45.479> then<00:10:45.929> the<00:10:46.169> the<00:10:46.349> wallet<00:10:46.709> if 00:10:46.789 --> 00:10:46.799 align:start position:0% the record and then the the wallet if 00:10:46.799 --> 00:10:48.229 align:start position:0% the record and then the the wallet if there's<00:10:47.009> someone<00:10:47.159> types<00:10:47.399> in<00:10:47.519> the<00:10:47.609> name<00:10:47.759> can 00:10:48.229 --> 00:10:48.239 align:start position:0% there's someone types in the name can 00:10:48.239 --> 00:10:50.509 align:start position:0% there's someone types in the name can grab<00:10:48.539> that<00:10:48.749> address<00:10:49.199> and<00:10:49.469> then<00:10:49.859> the<00:10:50.129> wallet 00:10:50.509 --> 00:10:50.519 align:start position:0% grab that address and then the wallet 00:10:50.519 --> 00:10:53.779 align:start position:0% grab that address and then the wallet sends<00:10:50.909> the<00:10:51.059> transaction<00:10:51.779> right<00:10:52.579> some<00:10:53.579> people 00:10:53.779 --> 00:10:53.789 align:start position:0% sends the transaction right some people 00:10:53.789 --> 00:10:55.009 align:start position:0% sends the transaction right some people are<00:10:53.849> like<00:10:53.939> well<00:10:54.089> how<00:10:54.179> does<00:10:54.239> that<00:10:54.419> work<00:10:54.629> as<00:10:54.839> you 00:10:55.009 --> 00:10:55.019 align:start position:0% are like well how does that work as you 00:10:55.019 --> 00:10:56.359 align:start position:0% are like well how does that work as you know<00:10:55.109> it's<00:10:55.289> on<00:10:55.559> a<00:10:55.619> different<00:10:55.859> chain<00:10:56.069> well<00:10:56.249> it's 00:10:56.359 --> 00:10:56.369 align:start position:0% know it's on a different chain well it's 00:10:56.369 --> 00:10:57.709 align:start position:0% know it's on a different chain well it's only<00:10:56.519> it's<00:10:56.909> just<00:10:57.149> that<00:10:57.299> where<00:10:57.449> it's<00:10:57.569> being 00:10:57.709 --> 00:10:57.719 align:start position:0% only it's just that where it's being 00:10:57.719 --> 00:11:01.159 align:start position:0% only it's just that where it's being stored<00:10:58.789> see<00:10:59.789> so<00:10:59.999> for<00:11:00.179> any<00:11:00.329> cryptocurrency<00:11:00.869> any 00:11:01.159 --> 00:11:01.169 align:start position:0% stored see so for any cryptocurrency any 00:11:01.169 --> 00:11:02.869 align:start position:0% stored see so for any cryptocurrency any arbitrary<00:11:01.649> cryptocurrency<00:11:02.069> this<00:11:02.429> works<00:11:02.639> for 00:11:02.869 --> 00:11:02.879 align:start position:0% arbitrary cryptocurrency this works for 00:11:02.879 --> 00:11:08.149 align:start position:0% arbitrary cryptocurrency this works for and<00:11:05.899> we<00:11:06.899> have<00:11:07.049> a<00:11:07.079> wallet<00:11:07.379> that's<00:11:07.829> actually 00:11:08.149 --> 00:11:08.159 align:start position:0% and we have a wallet that's actually 00:11:08.159 --> 00:11:10.550 align:start position:0% and we have a wallet that's actually just<00:11:08.909> about<00:11:09.089> ready<00:11:09.359> to<00:11:09.419> launch<00:11:09.839> this 00:11:10.550 --> 00:11:10.560 align:start position:0% just about ready to launch this 00:11:10.560 --> 00:11:12.890 align:start position:0% just about ready to launch this they<00:11:10.920> said<00:11:11.160> that<00:11:11.310> their<00:11:11.520> beta<00:11:11.910> version<00:11:12.840> of 00:11:12.890 --> 00:11:12.900 align:start position:0% they said that their beta version of 00:11:12.900 --> 00:11:15.590 align:start position:0% they said that their beta version of this<00:11:13.050> would<00:11:13.200> be<00:11:13.320> launching<00:11:13.770> either<00:11:14.760> today<00:11:15.210> or 00:11:15.590 --> 00:11:15.600 align:start position:0% this would be launching either today or 00:11:15.600 --> 00:11:17.690 align:start position:0% this would be launching either today or the<00:11:15.810> next<00:11:15.960> couple<00:11:16.050> days<00:11:16.290> and<00:11:16.740> then<00:11:16.920> in<00:11:17.160> normal 00:11:17.690 --> 00:11:17.700 align:start position:0% the next couple days and then in normal 00:11:17.700 --> 00:11:20.060 align:start position:0% the next couple days and then in normal production<00:11:18.110> mobile<00:11:19.110> app<00:11:19.260> by<00:11:19.650> the<00:11:19.680> end<00:11:19.920> of<00:11:19.950> the 00:11:20.060 --> 00:11:20.070 align:start position:0% production mobile app by the end of the 00:11:20.070 --> 00:11:22.610 align:start position:0% production mobile app by the end of the month<00:11:20.250> descent<00:11:21.150> wallet<00:11:21.510> this<00:11:22.020> is<00:11:22.170> a<00:11:22.260> hardware 00:11:22.610 --> 00:11:22.620 align:start position:0% month descent wallet this is a hardware 00:11:22.620 --> 00:11:25.970 align:start position:0% month descent wallet this is a hardware and<00:11:22.950> mobile<00:11:23.450> wallet<00:11:24.450> based<00:11:25.230> out<00:11:25.440> of<00:11:25.470> South 00:11:25.970 --> 00:11:25.980 align:start position:0% and mobile wallet based out of South 00:11:25.980 --> 00:11:27.920 align:start position:0% and mobile wallet based out of South Korea<00:11:26.340> this<00:11:26.940> is<00:11:27.120> their<00:11:27.240> website<00:11:27.420> decent 00:11:27.920 --> 00:11:27.930 align:start position:0% Korea this is their website decent 00:11:27.930 --> 00:11:29.630 align:start position:0% Korea this is their website decent welcome<00:11:28.440> they<00:11:28.620> support<00:11:29.010> a<00:11:29.100> bunch<00:11:29.430> of 00:11:29.630 --> 00:11:29.640 align:start position:0% welcome they support a bunch of 00:11:29.640 --> 00:11:31.700 align:start position:0% welcome they support a bunch of different<00:11:29.910> currencies<00:11:30.030> and<00:11:30.510> they<00:11:31.410> were 00:11:31.700 --> 00:11:31.710 align:start position:0% different currencies and they were 00:11:31.710 --> 00:11:33.530 align:start position:0% different currencies and they were really<00:11:32.220> great<00:11:32.550> to<00:11:32.700> kind<00:11:32.880> of<00:11:32.910> partner<00:11:33.270> with<00:11:33.420> us 00:11:33.530 --> 00:11:33.540 align:start position:0% really great to kind of partner with us 00:11:33.540 --> 00:11:35.770 align:start position:0% really great to kind of partner with us to<00:11:33.750> kind<00:11:33.930> of<00:11:33.990> build<00:11:34.200> this<00:11:34.350> new<00:11:34.530> functionality 00:11:35.770 --> 00:11:35.780 align:start position:0% to kind of build this new functionality 00:11:35.780 --> 00:11:39.500 align:start position:0% to kind of build this new functionality and<00:11:36.780> actually<00:11:37.080> I<00:11:37.110> want<00:11:37.320> to<00:11:37.380> show<00:11:37.880> a<00:11:38.880> video<00:11:39.270> of 00:11:39.500 --> 00:11:39.510 align:start position:0% and actually I want to show a video of 00:11:39.510 --> 00:11:42.860 align:start position:0% and actually I want to show a video of this<00:11:40.100> darn<00:11:41.100> it<00:11:41.250> okay<00:11:41.430> we're<00:11:42.390> not<00:11:42.450> a<00:11:42.510> different 00:11:42.860 --> 00:11:42.870 align:start position:0% this darn it okay we're not a different 00:11:42.870 --> 00:11:44.840 align:start position:0% this darn it okay we're not a different computer<00:11:43.110> so<00:11:44.010> we<00:11:44.160> had<00:11:44.280> a<00:11:44.310> video<00:11:44.520> of<00:11:44.730> this 00:11:44.840 --> 00:11:44.850 align:start position:0% computer so we had a video of this 00:11:44.850 --> 00:11:47.930 align:start position:0% computer so we had a video of this working<00:11:45.120> a<00:11:45.480> demo<00:11:45.930> on<00:11:46.110> main<00:11:46.440> net<00:11:46.820> you<00:11:47.820> can 00:11:47.930 --> 00:11:47.940 align:start position:0% working a demo on main net you can 00:11:47.940 --> 00:11:50.330 align:start position:0% working a demo on main net you can imagine<00:11:48.120> how<00:11:48.720> it<00:11:48.810> works<00:11:49.020> exactly<00:11:49.920> the<00:11:50.250> same 00:11:50.330 --> 00:11:50.340 align:start position:0% imagine how it works exactly the same 00:11:50.340 --> 00:11:51.710 align:start position:0% imagine how it works exactly the same ways<00:11:50.610> the<00:11:50.760> theorem<00:11:51.000> addresses<00:11:51.360> but<00:11:51.540> with 00:11:51.710 --> 00:11:51.720 align:start position:0% ways the theorem addresses but with 00:11:51.720 --> 00:11:53.990 align:start position:0% ways the theorem addresses but with Bitcoin<00:11:52.050> addresses<00:11:52.380> in<00:11:52.590> this<00:11:52.680> video<00:11:52.980> sorry<00:11:53.910> we 00:11:53.990 --> 00:11:54.000 align:start position:0% Bitcoin addresses in this video sorry we 00:11:54.000 --> 00:11:57.440 align:start position:0% Bitcoin addresses in this video sorry we had<00:11:54.090> to<00:11:54.150> switch<00:11:54.330> computers<00:11:55.160> okay<00:11:56.180> but<00:11:57.180> we<00:11:57.300> have 00:11:57.440 --> 00:11:57.450 align:start position:0% had to switch computers okay but we have 00:11:57.450 --> 00:11:59.360 align:start position:0% had to switch computers okay but we have commitments<00:11:58.110> for<00:11:58.380> more<00:11:58.680> than<00:11:58.890> just<00:11:58.920> decent 00:11:59.360 --> 00:11:59.370 align:start position:0% commitments for more than just decent 00:11:59.370 --> 00:12:00.500 align:start position:0% commitments for more than just decent wallet<00:11:59.610> we<00:11:59.730> actually<00:11:59.970> have<00:12:00.060> commitments<00:12:00.450> from 00:12:00.500 --> 00:12:00.510 align:start position:0% wallet we actually have commitments from 00:12:00.510 --> 00:12:02.900 align:start position:0% wallet we actually have commitments from seven<00:12:00.990> other<00:12:01.170> wallets<00:12:01.650> to<00:12:02.580> add<00:12:02.730> this 00:12:02.900 --> 00:12:02.910 align:start position:0% seven other wallets to add this 00:12:02.910 --> 00:12:04.820 align:start position:0% seven other wallets to add this functionality<00:12:03.390> either<00:12:04.050> in<00:12:04.260> the<00:12:04.320> next<00:12:04.560> couple 00:12:04.820 --> 00:12:04.830 align:start position:0% functionality either in the next couple 00:12:04.830 --> 00:12:07.010 align:start position:0% functionality either in the next couple weeks<00:12:04.860> or<00:12:05.190> months<00:12:05.490> they<00:12:06.330> are<00:12:06.360> on<00:12:06.600> board<00:12:06.810> with 00:12:07.010 --> 00:12:07.020 align:start position:0% weeks or months they are on board with 00:12:07.020 --> 00:12:09.080 align:start position:0% weeks or months they are on board with this<00:12:07.110> coin<00:12:07.470> base<00:12:07.650> wallet<00:12:08.100> trust<00:12:08.430> wallet<00:12:08.820> I<00:12:08.940> am 00:12:09.080 --> 00:12:09.090 align:start position:0% this coin base wallet trust wallet I am 00:12:09.090 --> 00:12:12.200 align:start position:0% this coin base wallet trust wallet I am token<00:12:09.540> Haven<00:12:10.500> my<00:12:10.680> crypto<00:12:11.040> Portus<00:12:11.430> and<00:12:11.670> opera 00:12:12.200 --> 00:12:12.210 align:start position:0% token Haven my crypto Portus and opera 00:12:12.210 --> 00:12:13.940 align:start position:0% token Haven my crypto Portus and opera and<00:12:12.510> we<00:12:12.900> are<00:12:13.020> also<00:12:13.200> in<00:12:13.470> discussions<00:12:13.890> with 00:12:13.940 --> 00:12:13.950 align:start position:0% and we are also in discussions with 00:12:13.950 --> 00:12:16.130 align:start position:0% and we are also in discussions with others<00:12:14.280> other<00:12:14.730> wallets<00:12:15.120> so<00:12:15.600> we'd<00:12:15.780> really<00:12:15.990> like 00:12:16.130 --> 00:12:16.140 align:start position:0% others other wallets so we'd really like 00:12:16.140 --> 00:12:18.620 align:start position:0% others other wallets so we'd really like this<00:12:16.320> to<00:12:16.500> be<00:12:16.530> the<00:12:16.950> standard<00:12:17.520> for<00:12:18.030> all<00:12:18.060> well<00:12:18.480> in 00:12:18.620 --> 00:12:18.630 align:start position:0% this to be the standard for all well in 00:12:18.630 --> 00:12:22.940 align:start position:0% this to be the standard for all well in aiming<00:12:19.550> and<00:12:20.550> if<00:12:21.060> you<00:12:21.300> are<00:12:21.710> involved<00:12:22.710> in 00:12:22.940 --> 00:12:22.950 align:start position:0% aiming and if you are involved in 00:12:22.950 --> 00:12:24.890 align:start position:0% aiming and if you are involved in another<00:12:23.100> multi<00:12:23.490> coin<00:12:23.790> wallet<00:12:24.030> please<00:12:24.570> let<00:12:24.870> us 00:12:24.890 --> 00:12:24.900 align:start position:0% another multi coin wallet please let us 00:12:24.900 --> 00:12:26.240 align:start position:0% another multi coin wallet please let us know<00:12:25.050> we'd<00:12:25.350> love<00:12:25.500> to<00:12:25.560> work<00:12:25.800> with<00:12:25.830> you<00:12:26.040> on<00:12:26.070> this 00:12:26.240 --> 00:12:26.250 align:start position:0% know we'd love to work with you on this 00:12:26.250 --> 00:12:30.070 align:start position:0% know we'd love to work with you on this and<00:12:27.650> this<00:12:28.650> new<00:12:28.950> functionality<00:12:29.400> was<00:12:29.670> actually 00:12:30.070 --> 00:12:30.080 align:start position:0% and this new functionality was actually 00:12:30.080 --> 00:12:33.620 align:start position:0% and this new functionality was actually funded<00:12:31.080> by<00:12:31.470> a<00:12:31.500> grant<00:12:31.920> from<00:12:31.980> BA<00:12:32.250> xx<00:12:32.670> so<00:12:33.360> thank 00:12:33.620 --> 00:12:33.630 align:start position:0% funded by a grant from BA xx so thank 00:12:33.630 --> 00:12:35.240 align:start position:0% funded by a grant from BA xx so thank you<00:12:33.750> to<00:12:33.810> you<00:12:33.960> by<00:12:34.200> Nantz<00:12:34.440> X<00:12:34.770> we<00:12:35.010> really 00:12:35.240 --> 00:12:35.250 align:start position:0% you to you by Nantz X we really 00:12:35.250 --> 00:12:38.810 align:start position:0% you to you by Nantz X we really appreciate<00:12:35.640> the<00:12:35.760> support<00:12:37.460> okay<00:12:38.460> we<00:12:38.580> are<00:12:38.670> also 00:12:38.810 --> 00:12:38.820 align:start position:0% appreciate the support okay we are also 00:12:38.820 --> 00:12:44.870 align:start position:0% appreciate the support okay we are also working<00:12:39.210> on<00:12:40.970> DNS<00:12:41.970> namespace<00:12:42.380> integration<00:12:43.880> so 00:12:44.870 --> 00:12:44.880 align:start position:0% working on DNS namespace integration so 00:12:44.880 --> 00:12:46.280 align:start position:0% working on DNS namespace integration so this<00:12:45.180> is<00:12:45.330> this<00:12:45.510> is<00:12:45.690> really<00:12:45.840> important<00:12:46.230> to 00:12:46.280 --> 00:12:46.290 align:start position:0% this is this is really important to 00:12:46.290 --> 00:12:47.900 align:start position:0% this is this is really important to understand<00:12:46.620> a<00:12:46.800> lot<00:12:47.190> of<00:12:47.280> people<00:12:47.520> think<00:12:47.790> that 00:12:47.900 --> 00:12:47.910 align:start position:0% understand a lot of people think that 00:12:47.910 --> 00:12:52.220 align:start position:0% understand a lot of people think that ENS<00:12:48.420> is<00:12:48.720> da<00:12:49.620> teef<00:12:50.060> it's<00:12:51.060> not<00:12:51.300> like<00:12:51.810> banish<00:12:52.200> that 00:12:52.220 --> 00:12:52.230 align:start position:0% ENS is da teef it's not like banish that 00:12:52.230 --> 00:12:55.190 align:start position:0% ENS is da teef it's not like banish that idea<00:12:52.710> from<00:12:52.890> your<00:12:53.040> name<00:12:53.280> banish<00:12:54.240> the<00:12:54.360> idea<00:12:54.720> from 00:12:55.190 --> 00:12:55.200 align:start position:0% idea from your name banish the idea from 00:12:55.200 --> 00:12:56.570 align:start position:0% idea from your name banish the idea from your<00:12:55.350> mind<00:12:55.620> okay 00:12:56.570 --> 00:12:56.580 align:start position:0% your mind okay 00:12:56.580 --> 00:13:00.410 align:start position:0% your mind okay ENS<00:12:57.360> is<00:12:57.540> not<00:12:57.750> da<00:12:58.050> DS<00:12:58.230> names<00:12:58.500> ENS<00:12:59.070> is<00:12:59.310> a<00:12:59.970> naming 00:13:00.410 --> 00:13:00.420 align:start position:0% ENS is not da DS names ENS is a naming 00:13:00.420 --> 00:13:03.800 align:start position:0% ENS is not da DS names ENS is a naming system<00:13:00.780> infrastructure<00:13:01.970> da<00:13:02.970> teef<00:13:03.180> is<00:13:03.420> just 00:13:03.800 --> 00:13:03.810 align:start position:0% system infrastructure da teef is just 00:13:03.810 --> 00:13:06.710 align:start position:0% system infrastructure da teef is just one<00:13:04.380> top-level<00:13:04.890> domain<00:13:05.280> that<00:13:06.030> happens<00:13:06.570> to 00:13:06.710 --> 00:13:06.720 align:start position:0% one top-level domain that happens to 00:13:06.720 --> 00:13:09.680 align:start position:0% one top-level domain that happens to work<00:13:06.839> on<00:13:07.050> it<00:13:07.200> but<00:13:08.190> any<00:13:08.370> name<00:13:08.640> could<00:13:08.910> run<00:13:09.120> on<00:13:09.450> the 00:13:09.680 --> 00:13:09.690 align:start position:0% work on it but any name could run on the 00:13:09.690 --> 00:13:11.570 align:start position:0% work on it but any name could run on the ENS<00:13:10.110> infrastructure<00:13:10.830> this<00:13:10.980> is<00:13:11.040> completely 00:13:11.570 --> 00:13:11.580 align:start position:0% ENS infrastructure this is completely 00:13:11.580 --> 00:13:13.490 align:start position:0% ENS infrastructure this is completely separate<00:13:12.570> things<00:13:12.870> that<00:13:13.050> you<00:13:13.110> need<00:13:13.260> to<00:13:13.350> have 00:13:13.490 --> 00:13:13.500 align:start position:0% separate things that you need to have 00:13:13.500 --> 00:13:16.850 align:start position:0% separate things that you need to have separately<00:13:14.310> in<00:13:14.400> your<00:13:14.550> mind<00:13:15.350> so<00:13:16.350> in<00:13:16.470> this<00:13:16.560> this 00:13:16.850 --> 00:13:16.860 align:start position:0% separately in your mind so in this this 00:13:16.860 --> 00:13:19.130 align:start position:0% separately in your mind so in this this distinction<00:13:17.550> also<00:13:17.760> holds<00:13:18.360> true<00:13:18.510> for<00:13:18.540> DNS<00:13:18.960> so 00:13:19.130 --> 00:13:19.140 align:start position:0% distinction also holds true for DNS so 00:13:19.140 --> 00:13:20.780 align:start position:0% distinction also holds true for DNS so there's<00:13:19.320> like<00:13:19.410> the<00:13:19.470> DNS<00:13:19.920> infrastructure<00:13:20.460> and 00:13:20.780 --> 00:13:20.790 align:start position:0% there's like the DNS infrastructure and 00:13:20.790 --> 00:13:22.450 align:start position:0% there's like the DNS infrastructure and then<00:13:21.180> there's<00:13:21.360> the<00:13:21.540> DNS<00:13:21.960> namespace 00:13:22.450 --> 00:13:22.460 align:start position:0% then there's the DNS namespace 00:13:22.460 --> 00:13:23.510 align:start position:0% then there's the DNS namespace completely 00:13:23.510 --> 00:13:23.520 align:start position:0% completely 00:13:23.520 --> 00:13:25.640 align:start position:0% completely difference<00:13:23.910> the<00:13:24.330> namespace<00:13:24.900> name<00:13:25.170> space 00:13:25.640 --> 00:13:25.650 align:start position:0% difference the namespace name space 00:13:25.650 --> 00:13:27.800 align:start position:0% difference the namespace name space could<00:13:25.920> remain<00:13:26.160> the<00:13:26.370> same<00:13:26.610> even<00:13:26.910> if<00:13:27.690> the 00:13:27.800 --> 00:13:27.810 align:start position:0% could remain the same even if the 00:13:27.810 --> 00:13:30.260 align:start position:0% could remain the same even if the infrastructure<00:13:28.260> changed<00:13:29.090> okay 00:13:30.260 --> 00:13:30.270 align:start position:0% infrastructure changed okay 00:13:30.270 --> 00:13:32.600 align:start position:0% infrastructure changed okay and<00:13:30.600> so<00:13:31.410> ENS<00:13:31.710> could<00:13:31.890> support<00:13:32.130> in<00:13:32.310> principle 00:13:32.600 --> 00:13:32.610 align:start position:0% and so ENS could support in principle 00:13:32.610 --> 00:13:36.560 align:start position:0% and so ENS could support in principle any<00:13:32.760> name<00:13:33.060> and<00:13:34.610> this<00:13:35.610> is<00:13:35.670> exactly<00:13:36.240> what<00:13:36.450> we're 00:13:36.560 --> 00:13:36.570 align:start position:0% any name and this is exactly what we're 00:13:36.570 --> 00:13:38.680 align:start position:0% any name and this is exactly what we're trying<00:13:36.750> to<00:13:36.870> do<00:13:37.050> so<00:13:37.530> so<00:13:37.770> we've<00:13:37.950> actually 00:13:38.680 --> 00:13:38.690 align:start position:0% trying to do so so we've actually 00:13:38.690 --> 00:13:41.390 align:start position:0% trying to do so so we've actually devised<00:13:39.690> a<00:13:39.960> system<00:13:40.170> so<00:13:40.830> that<00:13:40.920> if<00:13:41.040> you<00:13:41.160> own<00:13:41.370> a 00:13:41.390 --> 00:13:41.400 align:start position:0% devised a system so that if you own a 00:13:41.400 --> 00:13:44.990 align:start position:0% devised a system so that if you own a name<00:13:41.850> on<00:13:41.880> DNS<00:13:43.160> only<00:13:44.160> the<00:13:44.310> owner<00:13:44.460> of<00:13:44.640> that<00:13:44.790> name 00:13:44.990 --> 00:13:45.000 align:start position:0% name on DNS only the owner of that name 00:13:45.000 --> 00:13:49.490 align:start position:0% name on DNS only the owner of that name can<00:13:45.960> claim<00:13:46.410> use<00:13:46.710> of<00:13:46.920> that<00:13:47.040> name<00:13:47.370> on<00:13:47.750> ENS<00:13:48.750> not 00:13:49.490 --> 00:13:49.500 align:start position:0% can claim use of that name on ENS not 00:13:49.500 --> 00:13:51.530 align:start position:0% can claim use of that name on ENS not with<00:13:49.710> da<00:13:49.890> teef<00:13:50.100> but<00:13:50.520> with<00:13:50.700> the<00:13:50.820> same<00:13:51.060> top-level 00:13:51.530 --> 00:13:51.540 align:start position:0% with da teef but with the same top-level 00:13:51.540 --> 00:13:54.140 align:start position:0% with da teef but with the same top-level domain<00:13:51.900> so<00:13:52.440> for<00:13:52.620> example<00:13:53.040> a<00:13:53.250> theorem<00:13:53.700> Dorothy 00:13:54.140 --> 00:13:54.150 align:start position:0% domain so for example a theorem Dorothy 00:13:54.150 --> 00:13:57.050 align:start position:0% domain so for example a theorem Dorothy the<00:13:54.360> EF<00:13:54.660> could<00:13:55.500> if<00:13:55.830> they<00:13:56.190> used<00:13:56.550> our<00:13:56.640> system 00:13:57.050 --> 00:13:57.060 align:start position:0% the EF could if they used our system 00:13:57.060 --> 00:13:58.880 align:start position:0% the EF could if they used our system which<00:13:57.210> is<00:13:57.330> coming<00:13:57.600> out<00:13:57.690> here<00:13:57.870> very<00:13:57.990> soon<00:13:58.320> could 00:13:58.880 --> 00:13:58.890 align:start position:0% which is coming out here very soon could 00:13:58.890 --> 00:14:01.460 align:start position:0% which is coming out here very soon could have<00:13:59.010> a<00:13:59.100> DNS<00:13:59.460> record<00:13:59.640> an<00:13:59.970> DNS<00:14:00.510> record<00:14:00.840> for<00:14:01.080> 3mg 00:14:01.460 --> 00:14:01.470 align:start position:0% have a DNS record an DNS record for 3mg 00:14:01.470 --> 00:14:05.410 align:start position:0% have a DNS record an DNS record for 3mg org<00:14:01.770> not<00:14:01.950> etherium<00:14:02.400> DS<00:14:02.670> aetherium<00:14:03.390> dot<00:14:03.690> org 00:14:05.410 --> 00:14:05.420 align:start position:0% org not etherium DS aetherium dot org 00:14:05.420 --> 00:14:10.220 align:start position:0% org not etherium DS aetherium dot org and<00:14:07.130> we<00:14:08.130> use<00:14:08.610> something<00:14:09.210> called<00:14:09.360> DNS<00:14:09.780> set<00:14:10.020> to 00:14:10.220 --> 00:14:10.230 align:start position:0% and we use something called DNS set to 00:14:10.230 --> 00:14:11.450 align:start position:0% and we use something called DNS set to do<00:14:10.350> this<00:14:10.500> I'm<00:14:10.650> not<00:14:10.740> going<00:14:10.890> to<00:14:10.980> explain<00:14:11.250> this<00:14:11.400> in 00:14:11.450 --> 00:14:11.460 align:start position:0% do this I'm not going to explain this in 00:14:11.460 --> 00:14:14.000 align:start position:0% do this I'm not going to explain this in detail<00:14:11.910> but<00:14:12.510> it's<00:14:13.230> a<00:14:13.320> pretty<00:14:13.500> clever<00:14:13.650> system 00:14:14.000 --> 00:14:14.010 align:start position:0% detail but it's a pretty clever system 00:14:14.010 --> 00:14:17.620 align:start position:0% detail but it's a pretty clever system that<00:14:14.310> Nick<00:14:14.730> Johnson<00:14:15.030> came<00:14:15.270> up<00:14:15.390> with<00:14:15.570> here<00:14:16.460> and 00:14:17.620 --> 00:14:17.630 align:start position:0% that Nick Johnson came up with here and 00:14:17.630 --> 00:14:19.970 align:start position:0% that Nick Johnson came up with here and we<00:14:18.630> actually<00:14:18.750> this<00:14:19.170> actually<00:14:19.530> works<00:14:19.740> right 00:14:19.970 --> 00:14:19.980 align:start position:0% we actually this actually works right 00:14:19.980 --> 00:14:22.460 align:start position:0% we actually this actually works right now<00:14:20.010> for<00:14:20.400> dot<00:14:20.550> XYZ<00:14:21.090> so<00:14:21.570> like<00:14:21.750> argent<00:14:22.200> wallet 00:14:22.460 --> 00:14:22.470 align:start position:0% now for dot XYZ so like argent wallet 00:14:22.470 --> 00:14:24.890 align:start position:0% now for dot XYZ so like argent wallet uses<00:14:22.830> this<00:14:23.010> the<00:14:23.700> dot<00:14:24.060> XY<00:14:24.270> Z<00:14:24.480> was<00:14:24.600> kind<00:14:24.750> of<00:14:24.780> our 00:14:24.890 --> 00:14:24.900 align:start position:0% uses this the dot XY Z was kind of our 00:14:24.900 --> 00:14:26.780 align:start position:0% uses this the dot XY Z was kind of our test<00:14:25.140> case<00:14:25.380> and<00:14:25.650> we're<00:14:25.980> now<00:14:26.100> confident<00:14:26.670> in<00:14:26.730> the 00:14:26.780 --> 00:14:26.790 align:start position:0% test case and we're now confident in the 00:14:26.790 --> 00:14:28.070 align:start position:0% test case and we're now confident in the system<00:14:27.120> we're<00:14:27.240> gonna<00:14:27.330> be<00:14:27.480> rolling<00:14:27.630> this<00:14:27.900> out 00:14:28.070 --> 00:14:28.080 align:start position:0% system we're gonna be rolling this out 00:14:28.080 --> 00:14:30.800 align:start position:0% system we're gonna be rolling this out to<00:14:29.070> all<00:14:29.250> other<00:14:29.520> DNS<00:14:30.030> SEC<00:14:30.210> enable<00:14:30.510> DNS 00:14:30.800 --> 00:14:30.810 align:start position:0% to all other DNS SEC enable DNS 00:14:30.810 --> 00:14:32.540 align:start position:0% to all other DNS SEC enable DNS top-level<00:14:31.320> domains<00:14:31.620> which<00:14:31.800> is<00:14:31.920> all<00:14:32.160> the<00:14:32.400> ones 00:14:32.540 --> 00:14:32.550 align:start position:0% top-level domains which is all the ones 00:14:32.550 --> 00:14:34.010 align:start position:0% top-level domains which is all the ones you've<00:14:32.670> heard<00:14:32.850> of<00:14:33.000> we<00:14:33.600> also<00:14:33.720> have<00:14:33.870> some 00:14:34.010 --> 00:14:34.020 align:start position:0% you've heard of we also have some 00:14:34.020 --> 00:14:35.420 align:start position:0% you've heard of we also have some special<00:14:34.170> use<00:14:34.560> cases<00:14:34.830> for<00:14:35.130> these<00:14:35.220> other 00:14:35.420 --> 00:14:35.430 align:start position:0% special use cases for these other 00:14:35.430 --> 00:14:40.990 align:start position:0% special use cases for these other top-level<00:14:35.820> domains<00:14:36.330> dot<00:14:37.170> luxe<00:14:37.380> cred<00:14:37.830> art<00:14:38.190> oh 00:14:40.990 --> 00:14:41.000 align:start position:0% 00:14:41.000 --> 00:14:43.190 align:start position:0% yeah<00:14:42.000> so<00:14:42.240> so<00:14:42.390> some<00:14:42.570> people<00:14:42.810> said<00:14:42.990> well<00:14:43.080> if 00:14:43.190 --> 00:14:43.200 align:start position:0% yeah so so some people said well if 00:14:43.200 --> 00:14:44.300 align:start position:0% yeah so so some people said well if you're<00:14:43.290> gonna<00:14:43.380> integrate<00:14:43.590> the<00:14:43.830> DNS<00:14:44.100> namespace 00:14:44.300 --> 00:14:44.310 align:start position:0% you're gonna integrate the DNS namespace 00:14:44.310 --> 00:14:46.580 align:start position:0% you're gonna integrate the DNS namespace why<00:14:44.670> do<00:14:44.730> we<00:14:44.880> need<00:14:45.000> da<00:14:45.180> teef<00:14:45.390> well<00:14:46.320> because 00:14:46.580 --> 00:14:46.590 align:start position:0% why do we need da teef well because 00:14:46.590 --> 00:14:49.280 align:start position:0% why do we need da teef well because because<00:14:46.860> dot<00:14:47.280> e<00:14:47.400> is<00:14:47.670> native<00:14:48.060> to<00:14:48.090> e<00:14:48.270> NS<00:14:48.600> it<00:14:49.080> has 00:14:49.280 --> 00:14:49.290 align:start position:0% because dot e is native to e NS it has 00:14:49.290 --> 00:14:51.950 align:start position:0% because dot e is native to e NS it has special<00:14:49.680> properties<00:14:50.000> so<00:14:51.000> so<00:14:51.180> DNS<00:14:51.570> names<00:14:51.750> will 00:14:51.950 --> 00:14:51.960 align:start position:0% special properties so so DNS names will 00:14:51.960 --> 00:14:53.810 align:start position:0% special properties so so DNS names will still<00:14:52.140> be<00:14:52.260> subject<00:14:52.440> to<00:14:52.650> DNS<00:14:52.980> controls<00:14:53.400> because 00:14:53.810 --> 00:14:53.820 align:start position:0% still be subject to DNS controls because 00:14:53.820 --> 00:14:56.780 align:start position:0% still be subject to DNS controls because ownership<00:14:54.660> goes<00:14:55.260> only<00:14:55.590> one<00:14:55.770> direction<00:14:55.950> so 00:14:56.780 --> 00:14:56.790 align:start position:0% ownership goes only one direction so 00:14:56.790 --> 00:14:59.990 align:start position:0% ownership goes only one direction so whoever<00:14:57.120> owns<00:14:57.330> the<00:14:57.540> DNS<00:14:57.930> version<00:14:58.380> of<00:14:58.470> its<00:14:59.000> owns 00:14:59.990 --> 00:15:00.000 align:start position:0% whoever owns the DNS version of its owns 00:15:00.000 --> 00:15:02.390 align:start position:0% whoever owns the DNS version of its owns the<00:15:00.390> ens<00:15:00.690> version<00:15:01.050> of<00:15:01.140> it<00:15:01.260> but<00:15:01.740> because<00:15:01.920> da<00:15:02.220> DS 00:15:02.390 --> 00:15:02.400 align:start position:0% the ens version of it but because da DS 00:15:02.400 --> 00:15:06.170 align:start position:0% the ens version of it but because da DS names<00:15:02.670> are<00:15:02.880> native<00:15:03.270> to<00:15:03.870> E<00:15:04.290> and<00:15:04.740> s<00:15:04.940> they<00:15:05.940> have 00:15:06.170 --> 00:15:06.180 align:start position:0% names are native to E and s they have 00:15:06.180 --> 00:15:07.970 align:start position:0% names are native to E and s they have their<00:15:06.570> you<00:15:06.900> have<00:15:07.020> individual<00:15:07.560> ownership<00:15:07.740> or 00:15:07.970 --> 00:15:07.980 align:start position:0% their you have individual ownership or 00:15:07.980 --> 00:15:09.020 align:start position:0% their you have individual ownership or in<00:15:08.100> are<00:15:08.250> not<00:15:08.400> subject<00:15:08.790> to<00:15:08.820> those<00:15:08.970> same 00:15:09.020 --> 00:15:09.030 align:start position:0% in are not subject to those same 00:15:09.030 --> 00:15:13.160 align:start position:0% in are not subject to those same controls<00:15:11.390> some<00:15:12.390> people<00:15:12.660> ask<00:15:12.810> about<00:15:12.960> our 00:15:13.160 --> 00:15:13.170 align:start position:0% controls some people ask about our 00:15:13.170 --> 00:15:15.320 align:start position:0% controls some people ask about our relationship<00:15:13.740> with<00:15:13.770> ICANN<00:15:14.280> I'll<00:15:14.730> say<00:15:15.030> a<00:15:15.060> few 00:15:15.320 --> 00:15:15.330 align:start position:0% relationship with ICANN I'll say a few 00:15:15.330 --> 00:15:17.690 align:start position:0% relationship with ICANN I'll say a few words<00:15:15.510> it's<00:15:16.020> friendly<00:15:16.410> we've<00:15:17.160> gone<00:15:17.370> to<00:15:17.550> their 00:15:17.690 --> 00:15:17.700 align:start position:0% words it's friendly we've gone to their 00:15:17.700 --> 00:15:18.830 align:start position:0% words it's friendly we've gone to their their<00:15:17.970> conferences<00:15:18.450> we've<00:15:18.660> given 00:15:18.830 --> 00:15:18.840 align:start position:0% their conferences we've given 00:15:18.840 --> 00:15:21.830 align:start position:0% their conferences we've given presentations<00:15:19.940> almost<00:15:20.940> everybody<00:15:21.420> is<00:15:21.540> very 00:15:21.830 --> 00:15:21.840 align:start position:0% presentations almost everybody is very 00:15:21.840 --> 00:15:25.520 align:start position:0% presentations almost everybody is very open<00:15:22.470> and<00:15:22.620> receptive<00:15:22.950> to<00:15:23.400> ENS<00:15:24.240> in<00:15:24.480> fact<00:15:25.200> people 00:15:25.520 --> 00:15:25.530 align:start position:0% open and receptive to ENS in fact people 00:15:25.530 --> 00:15:26.780 align:start position:0% open and receptive to ENS in fact people approached<00:15:25.860> us<00:15:26.040> to<00:15:26.190> hey<00:15:26.310> we<00:15:26.460> want<00:15:26.610> to<00:15:26.640> work 00:15:26.780 --> 00:15:26.790 align:start position:0% approached us to hey we want to work 00:15:26.790 --> 00:15:27.140 align:start position:0% approached us to hey we want to work together 00:15:27.140 --> 00:15:27.150 align:start position:0% together 00:15:27.150 --> 00:15:29.750 align:start position:0% together so<00:15:28.080> we've<00:15:28.440> we<00:15:29.130> think<00:15:29.340> there's<00:15:29.460> a<00:15:29.550> lot<00:15:29.730> of 00:15:29.750 --> 00:15:29.760 align:start position:0% so we've we think there's a lot of 00:15:29.760 --> 00:15:31.880 align:start position:0% so we've we think there's a lot of potential<00:15:30.210> to<00:15:30.240> working<00:15:30.630> together<00:15:30.810> also<00:15:31.470> this 00:15:31.880 --> 00:15:31.890 align:start position:0% potential to working together also this 00:15:31.890 --> 00:15:33.440 align:start position:0% potential to working together also this is<00:15:32.010> a<00:15:32.040> key<00:15:32.220> thing<00:15:32.370> to<00:15:32.430> know<00:15:32.610> ICANN<00:15:33.090> is<00:15:33.270> not 00:15:33.440 --> 00:15:33.450 align:start position:0% is a key thing to know ICANN is not 00:15:33.450 --> 00:15:35.090 align:start position:0% is a key thing to know ICANN is not monolithic<00:15:33.780> some<00:15:34.200> people<00:15:34.470> will<00:15:34.560> say<00:15:34.740> this<00:15:34.980> is 00:15:35.090 --> 00:15:35.100 align:start position:0% monolithic some people will say this is 00:15:35.100 --> 00:15:36.240 align:start position:0% monolithic some people will say this is what<00:15:35.220> I<00:15:35.250> can<00:15:35.640> things 00:15:36.240 --> 00:15:36.250 align:start position:0% what I can things 00:15:36.250 --> 00:15:39.240 align:start position:0% what I can things or<00:15:36.340> I<00:15:36.430> can<00:15:36.670> does<00:15:37.120> I<00:15:38.050> cans<00:15:38.530> a<00:15:38.680> lot<00:15:38.860> of<00:15:38.980> different 00:15:39.240 --> 00:15:39.250 align:start position:0% or I can does I cans a lot of different 00:15:39.250 --> 00:15:41.160 align:start position:0% or I can does I cans a lot of different people<00:15:39.490> who<00:15:39.580> think<00:15:39.850> different<00:15:40.120> things<00:15:40.270> they 00:15:41.160 --> 00:15:41.170 align:start position:0% people who think different things they 00:15:41.170 --> 00:15:44.450 align:start position:0% people who think different things they don't<00:15:41.350> always<00:15:41.470> agree<00:15:41.620> so<00:15:42.460> keep<00:15:42.790> that<00:15:42.910> in<00:15:42.970> mind 00:15:44.450 --> 00:15:44.460 align:start position:0% don't always agree so keep that in mind 00:15:44.460 --> 00:15:48.500 align:start position:0% don't always agree so keep that in mind I'm<00:15:45.460> gonna<00:15:45.610> skip<00:15:45.820> this<00:15:46.000> running<00:15:46.720> low<00:15:46.840> on<00:15:46.870> time 00:15:48.500 --> 00:15:48.510 align:start position:0% I'm gonna skip this running low on time 00:15:48.510 --> 00:15:52.080 align:start position:0% I'm gonna skip this running low on time new<00:15:49.510> DNS<00:15:49.930> are<00:15:50.110> are<00:15:50.260> type<00:15:50.500> we<00:15:51.220> are<00:15:51.400> working<00:15:51.700> on 00:15:52.080 --> 00:15:52.090 align:start position:0% new DNS are are type we are working on 00:15:52.090 --> 00:15:55.290 align:start position:0% new DNS are are type we are working on getting<00:15:52.330> a<00:15:52.690> new<00:15:53.290> record<00:15:54.220> type<00:15:54.550> in<00:15:54.790> the<00:15:54.910> DNS 00:15:55.290 --> 00:15:55.300 align:start position:0% getting a new record type in the DNS 00:15:55.300 --> 00:15:58.290 align:start position:0% getting a new record type in the DNS system<00:15:55.480> for<00:15:56.470> a<00:15:56.500> theme<00:15:56.740> addresses<00:15:57.280> so<00:15:58.030> we<00:15:58.150> can 00:15:58.290 --> 00:15:58.300 align:start position:0% system for a theme addresses so we can 00:15:58.300 --> 00:16:01.320 align:start position:0% system for a theme addresses so we can standardize<00:15:58.630> our<00:15:59.200> the<00:15:59.950> our<00:16:00.760> process<00:16:01.300> for 00:16:01.320 --> 00:16:01.330 align:start position:0% standardize our the our process for 00:16:01.330 --> 00:16:04.920 align:start position:0% standardize our the our process for claiming<00:16:02.320> DNS<00:16:02.980> names<00:16:03.250> on<00:16:03.550> ENS<00:16:04.030> but<00:16:04.630> this<00:16:04.750> could 00:16:04.920 --> 00:16:04.930 align:start position:0% claiming DNS names on ENS but this could 00:16:04.930 --> 00:16:06.840 align:start position:0% claiming DNS names on ENS but this could be<00:16:04.990> used<00:16:05.170> beyond<00:16:05.560> DNS<00:16:06.040> just<00:16:06.340> want<00:16:06.580> you<00:16:06.700> to<00:16:06.760> be 00:16:06.840 --> 00:16:06.850 align:start position:0% be used beyond DNS just want you to be 00:16:06.850 --> 00:16:09.540 align:start position:0% be used beyond DNS just want you to be aware<00:16:06.940> of<00:16:07.090> that<00:16:07.350> and<00:16:08.350> we're<00:16:08.950> also<00:16:09.100> working<00:16:09.370> on 00:16:09.540 --> 00:16:09.550 align:start position:0% aware of that and we're also working on 00:16:09.550 --> 00:16:12.630 align:start position:0% aware of that and we're also working on getting<00:16:09.700> each<00:16:09.970> darpa<00:16:10.920> darpa<00:16:11.920> domains<00:16:12.370> are 00:16:12.630 --> 00:16:12.640 align:start position:0% getting each darpa darpa domains are 00:16:12.640 --> 00:16:14.700 align:start position:0% getting each darpa darpa domains are used<00:16:12.850> for<00:16:13.210> a<00:16:13.240> basic<00:16:13.900> internet<00:16:14.230> infrastructure 00:16:14.700 --> 00:16:14.710 align:start position:0% used for a basic internet infrastructure 00:16:14.710 --> 00:16:17.370 align:start position:0% used for a basic internet infrastructure and<00:16:15.040> we<00:16:15.730> are<00:16:15.850> working<00:16:16.060> on<00:16:16.270> getting<00:16:16.450> this<00:16:16.720> for 00:16:17.370 --> 00:16:17.380 align:start position:0% and we are working on getting this for 00:16:17.380 --> 00:16:19.610 align:start position:0% and we are working on getting this for use<00:16:17.620> for<00:16:17.980> the<00:16:18.190> whole<00:16:18.370> etherium<00:16:18.940> community 00:16:19.610 --> 00:16:19.620 align:start position:0% use for the whole etherium community 00:16:19.620 --> 00:16:22.160 align:start position:0% use for the whole etherium community this<00:16:20.620> would<00:16:20.860> be<00:16:20.980> another<00:16:21.220> kind<00:16:21.790> of<00:16:21.910> a 00:16:22.160 --> 00:16:22.170 align:start position:0% this would be another kind of a 00:16:22.170 --> 00:16:25.980 align:start position:0% this would be another kind of a semi-official<00:16:23.170> link<00:16:24.270> etherium<00:16:25.270> to<00:16:25.510> the 00:16:25.980 --> 00:16:25.990 align:start position:0% semi-official link etherium to the 00:16:25.990 --> 00:16:29.610 align:start position:0% semi-official link etherium to the legacy<00:16:26.440> internet<00:16:26.800> and<00:16:28.350> then<00:16:29.350> we're<00:16:29.470> also 00:16:29.610 --> 00:16:29.620 align:start position:0% legacy internet and then we're also 00:16:29.620 --> 00:16:32.700 align:start position:0% legacy internet and then we're also working<00:16:29.890> on<00:16:30.240> traditional<00:16:31.240> DNS<00:16:31.780> records<00:16:32.170> are 00:16:32.700 --> 00:16:32.710 align:start position:0% working on traditional DNS records are 00:16:32.710 --> 00:16:35.070 align:start position:0% working on traditional DNS records are our<00:16:32.950> public<00:16:33.220> resolver<00:16:33.880> actually<00:16:34.720> supports 00:16:35.070 --> 00:16:35.080 align:start position:0% our public resolver actually supports 00:16:35.080 --> 00:16:36.180 align:start position:0% our public resolver actually supports this<00:16:35.170> right<00:16:35.350> now 00:16:36.180 --> 00:16:36.190 align:start position:0% this right now 00:16:36.190 --> 00:16:39.480 align:start position:0% this right now but<00:16:36.490> we<00:16:36.640> have<00:16:36.910> a<00:16:37.270> project<00:16:38.110> going<00:16:38.830> with<00:16:39.250> dock 00:16:39.480 --> 00:16:39.490 align:start position:0% but we have a project going with dock 00:16:39.490 --> 00:16:41.940 align:start position:0% but we have a project going with dock cred<00:16:39.790> credit<00:16:40.120> a<00:16:40.330> dns<00:16:40.690> top-level<00:16:41.110> domain<00:16:41.410> they 00:16:41.940 --> 00:16:41.950 align:start position:0% cred credit a dns top-level domain they 00:16:41.950 --> 00:16:43.500 align:start position:0% cred credit a dns top-level domain they have<00:16:42.070> agreed<00:16:42.400> to<00:16:42.430> work<00:16:42.610> with<00:16:42.790> us<00:16:42.970> to<00:16:43.240> build<00:16:43.390> a 00:16:43.500 --> 00:16:43.510 align:start position:0% have agreed to work with us to build a 00:16:43.510 --> 00:16:46.829 align:start position:0% have agreed to work with us to build a system<00:16:43.720> to<00:16:44.560> use<00:16:44.950> e<00:16:45.250> NS<00:16:45.460> and<00:16:45.670> IP<00:16:45.910> FSU<00:16:46.330> host<00:16:46.600> all 00:16:46.829 --> 00:16:46.839 align:start position:0% system to use e NS and IP FSU host all 00:16:46.839 --> 00:16:49.680 align:start position:0% system to use e NS and IP FSU host all of<00:16:47.290> their<00:16:47.440> DN<00:16:48.339> a--<00:16:48.430> traditional<00:16:48.970> dns<00:16:49.270> records 00:16:49.680 --> 00:16:49.690 align:start position:0% of their DN a-- traditional dns records 00:16:49.690 --> 00:16:52.680 align:start position:0% of their DN a-- traditional dns records for<00:16:49.990> their<00:16:50.080> a<00:16:50.140> whole<00:16:50.350> namespace<00:16:50.940> which<00:16:51.940> would 00:16:52.680 --> 00:16:52.690 align:start position:0% for their a whole namespace which would 00:16:52.690 --> 00:16:54.810 align:start position:0% for their a whole namespace which would be<00:16:52.810> an<00:16:52.930> incredible<00:16:53.500> kind<00:16:54.220> of<00:16:54.310> first<00:16:54.550> step 00:16:54.810 --> 00:16:54.820 align:start position:0% be an incredible kind of first step 00:16:54.820 --> 00:16:58.950 align:start position:0% be an incredible kind of first step towards<00:16:55.330> having<00:16:56.020> ENS<00:16:56.640> be<00:16:57.640> used<00:16:57.850> for<00:16:58.600> that<00:16:58.750> use 00:16:58.950 --> 00:16:58.960 align:start position:0% towards having ENS be used for that use 00:16:58.960 --> 00:17:01.500 align:start position:0% towards having ENS be used for that use case<00:16:59.200> so<00:17:00.160> we<00:17:00.370> are<00:17:00.490> very<00:17:00.730> excited<00:17:01.150> about<00:17:01.210> this 00:17:01.500 --> 00:17:01.510 align:start position:0% case so we are very excited about this 00:17:01.510 --> 00:17:03.420 align:start position:0% case so we are very excited about this it's<00:17:02.290> really<00:17:02.440> it's<00:17:02.650> amazing<00:17:02.860> they've<00:17:03.190> agreed 00:17:03.420 --> 00:17:03.430 align:start position:0% it's really it's amazing they've agreed 00:17:03.430 --> 00:17:04.800 align:start position:0% it's really it's amazing they've agreed to<00:17:03.610> do<00:17:03.730> this<00:17:03.850> with<00:17:04.060> us<00:17:04.150> we've<00:17:04.329> talked<00:17:04.569> to<00:17:04.689> lots 00:17:04.800 --> 00:17:04.810 align:start position:0% to do this with us we've talked to lots 00:17:04.810 --> 00:17:06.360 align:start position:0% to do this with us we've talked to lots of<00:17:04.959> other<00:17:05.050> top-level<00:17:05.380> domains<00:17:05.920> who<00:17:06.040> are<00:17:06.130> kind 00:17:06.360 --> 00:17:06.370 align:start position:0% of other top-level domains who are kind 00:17:06.370 --> 00:17:08.220 align:start position:0% of other top-level domains who are kind of<00:17:06.430> interested<00:17:06.850> but<00:17:07.540> they<00:17:07.720> tend<00:17:07.959> to<00:17:08.020> be<00:17:08.110> very 00:17:08.220 --> 00:17:08.230 align:start position:0% of interested but they tend to be very 00:17:08.230 --> 00:17:09.960 align:start position:0% of interested but they tend to be very conservative<00:17:08.430> so<00:17:09.430> they're<00:17:09.579> willing<00:17:09.760> to 00:17:09.960 --> 00:17:09.970 align:start position:0% conservative so they're willing to 00:17:09.970 --> 00:17:11.670 align:start position:0% conservative so they're willing to experiment<00:17:10.390> with<00:17:10.630> us<00:17:10.750> on<00:17:10.900> this<00:17:11.050> and<00:17:11.260> we're 00:17:11.670 --> 00:17:11.680 align:start position:0% experiment with us on this and we're 00:17:11.680 --> 00:17:14.150 align:start position:0% experiment with us on this and we're very<00:17:11.709> we're<00:17:12.250> very<00:17:12.430> happy<00:17:12.579> about<00:17:12.790> that 00:17:14.150 --> 00:17:14.160 align:start position:0% very we're very happy about that 00:17:14.160 --> 00:17:16.590 align:start position:0% very we're very happy about that so<00:17:15.160> that's<00:17:15.339> it<00:17:15.520> thank<00:17:16.000> you<00:17:16.030> very<00:17:16.180> much 00:17:16.590 --> 00:17:16.600 align:start position:0% so that's it thank you very much 00:17:16.600 --> 00:17:19.679 align:start position:0% so that's it thank you very much here<00:17:16.930> are<00:17:17.110> some<00:17:17.410> important<00:17:17.829> links<00:17:18.180> and<00:17:19.180> we 00:17:19.679 --> 00:17:19.689 align:start position:0% here are some important links and we 00:17:19.689 --> 00:17:21.600 align:start position:0% here are some important links and we have<00:17:19.780> one<00:17:19.990> minute<00:17:20.230> if<00:17:20.560> anybody<00:17:21.160> wants<00:17:21.400> to<00:17:21.430> ask 00:17:21.600 --> 00:17:21.610 align:start position:0% have one minute if anybody wants to ask 00:17:21.610 --> 00:17:25.650 align:start position:0% have one minute if anybody wants to ask a<00:17:21.760> question<00:17:23.550> yeah<00:17:24.550> so<00:17:24.760> just<00:17:24.880> just<00:17:25.240> run<00:17:25.420> up<00:17:25.510> to 00:17:25.650 --> 00:17:25.660 align:start position:0% a question yeah so just just run up to 00:17:25.660 --> 00:17:27.090 align:start position:0% a question yeah so just just run up to the<00:17:25.750> mic<00:17:25.870> here<00:17:26.170> and<00:17:26.319> we<00:17:26.410> have<00:17:26.530> time<00:17:26.709> for<00:17:26.740> maybe 00:17:27.090 --> 00:17:27.100 align:start position:0% the mic here and we have time for maybe 00:17:27.100 --> 00:17:29.550 align:start position:0% the mic here and we have time for maybe one<00:17:27.400> or<00:17:27.430> two<00:17:27.550> I<00:17:27.850> could<00:17:28.690> also<00:17:28.870> talk<00:17:29.110> we<00:17:29.320> can<00:17:29.440> also 00:17:29.550 --> 00:17:29.560 align:start position:0% one or two I could also talk we can also 00:17:29.560 --> 00:17:31.500 align:start position:0% one or two I could also talk we can also talk<00:17:29.770> afterwards<00:17:30.220> we<00:17:30.340> have<00:17:30.430> some<00:17:31.270> of<00:17:31.360> our 00:17:31.500 --> 00:17:31.510 align:start position:0% talk afterwards we have some of our 00:17:31.510 --> 00:17:33.360 align:start position:0% talk afterwards we have some of our developers<00:17:32.140> here<00:17:32.530> as<00:17:32.620> well<00:17:32.770> what<00:17:32.980> happens<00:17:33.250> if 00:17:33.360 --> 00:17:33.370 align:start position:0% developers here as well what happens if 00:17:33.370 --> 00:17:36.240 align:start position:0% developers here as well what happens if DNS<00:17:33.730> want<00:17:33.940> to<00:17:34.000> add<00:17:34.150> or<00:17:34.330> eath<00:17:34.450> names<00:17:35.040> are<00:17:36.040> they 00:17:36.240 --> 00:17:36.250 align:start position:0% DNS want to add or eath names are they 00:17:36.250 --> 00:17:38.850 align:start position:0% DNS want to add or eath names are they going<00:17:36.490> to<00:17:36.670> mean<00:17:37.150> in<00:17:37.360> in<00:17:37.630> the<00:17:37.810> DNS<00:17:38.050> root<00:17:38.230> it's 00:17:38.850 --> 00:17:38.860 align:start position:0% going to mean in in the DNS root it's 00:17:38.860 --> 00:17:40.410 align:start position:0% going to mean in in the DNS root it's currently<00:17:39.220> reserves<00:17:39.640> as<00:17:39.940> a<00:17:40.000> three<00:17:40.270> letter 00:17:40.410 --> 00:17:40.420 align:start position:0% currently reserves as a three letter 00:17:40.420 --> 00:17:43.140 align:start position:0% currently reserves as a three letter country<00:17:40.660> code<00:17:40.840> for<00:17:41.140> Ethiopia<00:17:41.790> although<00:17:42.790> they 00:17:43.140 --> 00:17:43.150 align:start position:0% country code for Ethiopia although they 00:17:43.150 --> 00:17:45.150 align:start position:0% country code for Ethiopia although they are<00:17:43.240> not<00:17:43.390> using<00:17:43.930> any<00:17:44.140> three-letter<00:17:44.830> country 00:17:45.150 --> 00:17:45.160 align:start position:0% are not using any three-letter country 00:17:45.160 --> 00:17:46.590 align:start position:0% are not using any three-letter country codes<00:17:45.370> they're<00:17:45.670> just<00:17:45.790> like<00:17:45.910> reserves<00:17:46.330> in 00:17:46.590 --> 00:17:46.600 align:start position:0% codes they're just like reserves in 00:17:46.600 --> 00:17:48.680 align:start position:0% codes they're just like reserves in defense<00:17:47.020> and<00:17:47.740> I've 00:17:48.680 --> 00:17:48.690 align:start position:0% defense and I've 00:17:48.690 --> 00:17:50.019 align:start position:0% defense and I've to<00:17:48.750> people<00:17:48.990> who<00:17:49.049> say<00:17:49.259> that<00:17:49.440> they're<00:17:49.710> actually 00:17:50.019 --> 00:17:50.029 align:start position:0% to people who say that they're actually 00:17:50.029 --> 00:17:52.190 align:start position:0% to people who say that they're actually probably<00:17:51.029> not<00:17:51.269> going<00:17:51.570> to<00:17:51.690> give<00:17:51.929> them<00:17:52.080> to<00:17:52.169> the 00:17:52.190 --> 00:17:52.200 align:start position:0% probably not going to give them to the 00:17:52.200 --> 00:17:54.499 align:start position:0% probably not going to give them to the country's<00:17:52.590> so<00:17:53.220> at<00:17:53.340> some<00:17:53.580> point<00:17:53.940> we<00:17:54.059> might<00:17:54.299> be 00:17:54.499 --> 00:17:54.509 align:start position:0% country's so at some point we might be 00:17:54.509 --> 00:17:57.200 align:start position:0% country's so at some point we might be able<00:17:54.659> to<00:17:54.750> get<00:17:55.049> da<00:17:55.320> teeth<00:17:55.529> as<00:17:55.769> a<00:17:55.830> gTLD<00:17:56.610> but<00:17:57.090> that 00:17:57.200 --> 00:17:57.210 align:start position:0% able to get da teeth as a gTLD but that 00:17:57.210 --> 00:18:02.509 align:start position:0% able to get da teeth as a gTLD but that may<00:17:57.330> or<00:17:57.450> may<00:17:57.480> not<00:17:57.629> happen<00:17:59.990> okay<00:18:01.190> so<00:18:02.190> it's 00:18:02.509 --> 00:18:02.519 align:start position:0% may or may not happen okay so it's 00:18:02.519 --> 00:18:04.970 align:start position:0% may or may not happen okay so it's probably<00:18:02.850> unclear<00:18:03.509> that<00:18:03.840> ENS<00:18:04.350> would<00:18:04.620> ever<00:18:04.799> be 00:18:04.970 --> 00:18:04.980 align:start position:0% probably unclear that ENS would ever be 00:18:04.980 --> 00:18:08.480 align:start position:0% probably unclear that ENS would ever be able<00:18:05.100> to<00:18:05.159> get<00:18:05.309> the<00:18:05.519> the<00:18:05.789> ddotty<00:18:06.360> TLD<00:18:07.159> so<00:18:08.159> the 00:18:08.480 --> 00:18:08.490 align:start position:0% able to get the the ddotty TLD so the 00:18:08.490 --> 00:18:10.549 align:start position:0% able to get the the ddotty TLD so the main<00:18:08.610> issue<00:18:08.789> is<00:18:08.940> that<00:18:09.059> for<00:18:09.240> you<00:18:09.509> to<00:18:09.600> be<00:18:09.629> and<00:18:10.409> I 00:18:10.549 --> 00:18:10.559 align:start position:0% main issue is that for you to be and I 00:18:10.559 --> 00:18:12.950 align:start position:0% main issue is that for you to be and I can't<00:18:10.919> approve<00:18:11.250> TLD<00:18:11.850> you<00:18:12.360> must<00:18:12.629> abide<00:18:12.899> by 00:18:12.950 --> 00:18:12.960 align:start position:0% can't approve TLD you must abide by 00:18:12.960 --> 00:18:14.930 align:start position:0% can't approve TLD you must abide by something<00:18:13.200> called<00:18:13.320> the<00:18:13.559> what<00:18:14.159> the<00:18:14.519> Uniform 00:18:14.930 --> 00:18:14.940 align:start position:0% something called the what the Uniform 00:18:14.940 --> 00:18:17.240 align:start position:0% something called the what the Uniform domain<00:18:15.360> dispute<00:18:15.840> resolution<00:18:16.289> policy<00:18:16.500> or<00:18:16.889> UD 00:18:17.240 --> 00:18:17.250 align:start position:0% domain dispute resolution policy or UD 00:18:17.250 --> 00:18:19.249 align:start position:0% domain dispute resolution policy or UD RP<00:18:17.580> which<00:18:18.090> basically<00:18:18.419> says<00:18:18.720> things<00:18:18.960> lessons 00:18:19.249 --> 00:18:19.259 align:start position:0% RP which basically says things lessons 00:18:19.259 --> 00:18:20.869 align:start position:0% RP which basically says things lessons that<00:18:19.350> look<00:18:19.529> like<00:18:19.679> let<00:18:19.950> copyrights<00:18:20.519> and 00:18:20.869 --> 00:18:20.879 align:start position:0% that look like let copyrights and 00:18:20.879 --> 00:18:23.450 align:start position:0% that look like let copyrights and trademarks<00:18:21.360> are<00:18:21.899> enforced<00:18:22.350> and<00:18:23.100> we're<00:18:23.309> not 00:18:23.450 --> 00:18:23.460 align:start position:0% trademarks are enforced and we're not 00:18:23.460 --> 00:18:25.369 align:start position:0% trademarks are enforced and we're not we're<00:18:24.419> not<00:18:24.509> really<00:18:24.690> going<00:18:24.960> for<00:18:25.259> that<00:18:25.320> a 00:18:25.369 --> 00:18:25.379 align:start position:0% we're not really going for that a 00:18:25.379 --> 00:18:26.840 align:start position:0% we're not really going for that a technologically<00:18:26.190> can't<00:18:26.429> do<00:18:26.580> that<00:18:26.700> without 00:18:26.840 --> 00:18:26.850 align:start position:0% technologically can't do that without 00:18:26.850 --> 00:18:29.899 align:start position:0% technologically can't do that without ease<00:18:27.149> yeah<00:18:27.509> yeah<00:18:27.779> so<00:18:28.110> so<00:18:29.009> I<00:18:29.039> imagine<00:18:29.789> that's 00:18:29.899 --> 00:18:29.909 align:start position:0% ease yeah yeah so so I imagine that's 00:18:29.909 --> 00:18:33.139 align:start position:0% ease yeah yeah so so I imagine that's probably<00:18:29.970> be<00:18:30.389> like<00:18:30.570> just<00:18:31.049> a<00:18:31.279> non-starter<00:18:32.279> we 00:18:33.139 --> 00:18:33.149 align:start position:0% probably be like just a non-starter we 00:18:33.149 --> 00:18:34.940 align:start position:0% probably be like just a non-starter we so<00:18:33.659> crime<00:18:34.080> can<00:18:34.230> open<00:18:34.409> the<00:18:34.470> idea<00:18:34.710> that<00:18:34.860> you 00:18:34.940 --> 00:18:34.950 align:start position:0% so crime can open the idea that you 00:18:34.950 --> 00:18:36.470 align:start position:0% so crime can open the idea that you could<00:18:35.070> have<00:18:35.250> you<00:18:35.370> know<00:18:35.399> some<00:18:35.789> some<00:18:36.029> I<00:18:36.210> can 00:18:36.470 --> 00:18:36.480 align:start position:0% could have you know some some I can 00:18:36.480 --> 00:18:39.980 align:start position:0% could have you know some some I can approve<00:18:36.809> TL<00:18:37.169> DS<00:18:37.379> that<00:18:37.740> that<00:18:38.429> that<00:18:39.419> do<00:18:39.600> enforce 00:18:39.980 --> 00:18:39.990 align:start position:0% approve TL DS that that that do enforce 00:18:39.990 --> 00:18:42.080 align:start position:0% approve TL DS that that that do enforce trademarks<00:18:40.529> and<00:18:40.769> then<00:18:40.860> some<00:18:41.129> that<00:18:41.279> don't<00:18:41.429> but 00:18:42.080 --> 00:18:42.090 align:start position:0% trademarks and then some that don't but 00:18:42.090 --> 00:18:43.519 align:start position:0% trademarks and then some that don't but they<00:18:42.179> have<00:18:42.299> a<00:18:42.330> very<00:18:42.659> strict<00:18:42.899> requirement 00:18:43.519 --> 00:18:43.529 align:start position:0% they have a very strict requirement 00:18:43.529 --> 00:18:45.799 align:start position:0% they have a very strict requirement anything<00:18:43.889> within<00:18:44.159> their<00:18:44.370> route<00:18:44.580> does<00:18:45.389> enforce 00:18:45.799 --> 00:18:45.809 align:start position:0% anything within their route does enforce 00:18:45.809 --> 00:18:47.240 align:start position:0% anything within their route does enforce trademarks<00:18:46.289> right<00:18:46.649> I<00:18:46.799> mean<00:18:46.919> we'll<00:18:47.039> see<00:18:47.190> how 00:18:47.240 --> 00:18:47.250 align:start position:0% trademarks right I mean we'll see how 00:18:47.250 --> 00:18:48.080 align:start position:0% trademarks right I mean we'll see how that<00:18:47.309> goes<00:18:47.580> right 00:18:48.080 --> 00:18:48.090 align:start position:0% that goes right 00:18:48.090 --> 00:18:50.360 align:start position:0% that goes right yes<00:18:48.330> last<00:18:48.750> question<00:18:49.110> about<00:18:49.259> the<00:18:49.919> hardware 00:18:50.360 --> 00:18:50.370 align:start position:0% yes last question about the hardware 00:18:50.370 --> 00:18:51.619 align:start position:0% yes last question about the hardware wallet<00:18:50.639> integration<00:18:51.029> does<00:18:51.299> the<00:18:51.389> hardware 00:18:51.619 --> 00:18:51.629 align:start position:0% wallet integration does the hardware 00:18:51.629 --> 00:18:53.450 align:start position:0% wallet integration does the hardware wallet<00:18:51.870> actually<00:18:52.259> display<00:18:52.679> the<00:18:52.710> dot<00:18:53.009> e<00:18:53.159> Thames 00:18:53.450 --> 00:18:53.460 align:start position:0% wallet actually display the dot e Thames 00:18:53.460 --> 00:18:55.820 align:start position:0% wallet actually display the dot e Thames when<00:18:53.730> you<00:18:53.820> confirm<00:18:54.350> the<00:18:55.350> what<00:18:55.529> well<00:18:55.710> an 00:18:55.820 --> 00:18:55.830 align:start position:0% when you confirm the what well an 00:18:55.830 --> 00:18:57.379 align:start position:0% when you confirm the what well an integrate<00:18:56.129> with<00:18:56.519> hardware<00:18:56.940> wallets<00:18:57.179> that<00:18:57.330> are 00:18:57.379 --> 00:18:57.389 align:start position:0% integrate with hardware wallets that are 00:18:57.389 --> 00:19:00.619 align:start position:0% integrate with hardware wallets that are using<00:18:57.690> it<00:18:57.809> Hardware<00:18:58.970> yes<00:18:59.970> like<00:19:00.299> well<00:19:00.450> on<00:19:00.539> the 00:19:00.619 --> 00:19:00.629 align:start position:0% using it Hardware yes like well on the 00:19:00.629 --> 00:19:02.690 align:start position:0% using it Hardware yes like well on the device<00:19:00.720> it<00:19:01.019> displays<00:19:01.379> I<00:19:01.620> don't<00:19:02.370> know<00:19:02.460> if<00:19:02.580> it's 00:19:02.690 --> 00:19:02.700 align:start position:0% device it displays I don't know if it's 00:19:02.700 --> 00:19:05.029 align:start position:0% device it displays I don't know if it's on<00:19:02.820> the<00:19:03.000> device<00:19:03.299> good<00:19:03.629> question<00:19:04.049> but<00:19:04.679> in<00:19:04.860> their 00:19:05.029 --> 00:19:05.039 align:start position:0% on the device good question but in their 00:19:05.039 --> 00:19:07.399 align:start position:0% on the device good question but in their mobile<00:19:05.279> app<00:19:05.549> that<00:19:05.759> uses<00:19:06.240> their<00:19:07.049> hardware 00:19:07.399 --> 00:19:07.409 align:start position:0% mobile app that uses their hardware 00:19:07.409 --> 00:19:08.960 align:start position:0% mobile app that uses their hardware wallet<00:19:07.769> okay<00:19:08.220> I<00:19:08.250> was<00:19:08.429> just<00:19:08.549> gonna<00:19:08.610> ask<00:19:08.759> cuz 00:19:08.960 --> 00:19:08.970 align:start position:0% wallet okay I was just gonna ask cuz 00:19:08.970 --> 00:19:10.850 align:start position:0% wallet okay I was just gonna ask cuz it's<00:19:09.149> it's<00:19:09.419> very<00:19:09.809> hard<00:19:10.139> for<00:19:10.169> hardware<00:19:10.590> devices 00:19:10.850 --> 00:19:10.860 align:start position:0% it's it's very hard for hardware devices 00:19:10.860 --> 00:19:13.730 align:start position:0% it's it's very hard for hardware devices to<00:19:11.190> authenticate<00:19:11.789> ENS<00:19:12.320> entries<00:19:13.320> because<00:19:13.529> they 00:19:13.730 --> 00:19:13.740 align:start position:0% to authenticate ENS entries because they 00:19:13.740 --> 00:19:15.379 align:start position:0% to authenticate ENS entries because they can't<00:19:13.950> see<00:19:14.100> the<00:19:14.220> blockchain<00:19:14.429> so<00:19:15.120> they<00:19:15.210> don't 00:19:15.379 --> 00:19:15.389 align:start position:0% can't see the blockchain so they don't 00:19:15.389 --> 00:19:16.879 align:start position:0% can't see the blockchain so they don't know<00:19:15.600> the<00:19:15.779> current<00:19:16.019> state<00:19:16.200> of<00:19:16.230> the<00:19:16.379> NS<00:19:16.649> name 00:19:16.879 --> 00:19:16.889 align:start position:0% know the current state of the NS name 00:19:16.889 --> 00:19:18.649 align:start position:0% know the current state of the NS name and<00:19:17.100> because<00:19:17.730> you<00:19:17.850> can't<00:19:18.000> do<00:19:18.090> multiple 00:19:18.649 --> 00:19:18.659 align:start position:0% and because you can't do multiple 00:19:18.659 --> 00:19:19.610 align:start position:0% and because you can't do multiple function<00:19:18.960> calls<00:19:19.139> inside<00:19:19.350> of<00:19:19.470> a<00:19:19.500> single 00:19:19.610 --> 00:19:19.620 align:start position:0% function calls inside of a single 00:19:19.620 --> 00:19:21.470 align:start position:0% function calls inside of a single transaction<00:19:20.009> you<00:19:20.309> can't<00:19:20.519> just<00:19:20.700> assert<00:19:21.210> that 00:19:21.470 --> 00:19:21.480 align:start position:0% transaction you can't just assert that 00:19:21.480 --> 00:19:24.529 align:start position:0% transaction you can't just assert that the<00:19:21.990> the<00:19:22.529> address<00:19:23.159> is<00:19:23.490> actually<00:19:23.909> an<00:19:24.029> e<00:19:24.120> NS<00:19:24.330> name 00:19:24.529 --> 00:19:24.539 align:start position:0% the the address is actually an e NS name 00:19:24.539 --> 00:19:25.730 align:start position:0% the the address is actually an e NS name so<00:19:24.629> I<00:19:24.690> was<00:19:24.809> curious<00:19:24.929> how<00:19:25.110> you<00:19:25.169> saw<00:19:25.350> oh<00:19:25.529> yeah<00:19:25.710> I 00:19:25.730 --> 00:19:25.740 align:start position:0% so I was curious how you saw oh yeah I 00:19:25.740 --> 00:19:27.619 align:start position:0% so I was curious how you saw oh yeah I know<00:19:25.860> it's<00:19:26.009> all<00:19:26.100> on<00:19:26.159> the<00:19:26.399> mobile<00:19:26.580> app<00:19:26.789> okay<00:19:27.450> you 00:19:27.619 --> 00:19:27.629 align:start position:0% know it's all on the mobile app okay you 00:19:27.629 --> 00:19:28.669 align:start position:0% know it's all on the mobile app okay you guys<00:19:27.750> seen<00:19:27.990> that<00:19:28.019> in<00:19:28.169> the<00:19:28.230> video<00:19:28.440> I'm<00:19:28.620> sorry 00:19:28.669 --> 00:19:28.679 align:start position:0% guys seen that in the video I'm sorry 00:19:28.679 --> 00:19:30.499 align:start position:0% guys seen that in the video I'm sorry the<00:19:28.950> video<00:19:29.039> didn't<00:19:29.370> work<00:19:29.460> okay 00:19:30.499 --> 00:19:30.509 align:start position:0% the video didn't work okay 00:19:30.509 --> 00:19:31.870 align:start position:0% the video didn't work okay thank<00:19:30.750> you<00:19:30.809> very<00:19:30.840> much 00:19:31.870 --> 00:19:31.880 align:start position:0% thank you very much 00:19:31.880 --> 00:19:43.440 align:start position:0% thank you very much [Applause] 00:19:43.440 --> 00:19:43.450 align:start position:0% 00:19:43.450 --> 00:19:45.510 align:start position:0% you