WEBVTT Kind: captions Language: en 00:00:04.630 --> 00:00:07.110 align:start position:0% my<00:00:05.290> name<00:00:05.500> is<00:00:05.650> Nick<00:00:05.890> Johnson<00:00:06.340> I'm<00:00:06.550> the<00:00:06.880> lead 00:00:07.110 --> 00:00:07.120 align:start position:0% my name is Nick Johnson I'm the lead 00:00:07.120 --> 00:00:09.180 align:start position:0% my name is Nick Johnson I'm the lead developer<00:00:07.600> for<00:00:07.630> the<00:00:07.960> etherium<00:00:08.559> name<00:00:08.770> service 00:00:09.180 --> 00:00:09.190 align:start position:0% developer for the etherium name service 00:00:09.190 --> 00:00:11.430 align:start position:0% developer for the etherium name service and<00:00:09.400> I'm<00:00:09.940> here<00:00:10.150> today<00:00:10.270> to<00:00:10.420> give<00:00:10.780> you<00:00:10.960> thank<00:00:11.379> you 00:00:11.430 --> 00:00:11.440 align:start position:0% and I'm here today to give you thank you 00:00:11.440 --> 00:00:13.500 align:start position:0% and I'm here today to give you thank you very<00:00:11.590> much<00:00:11.830> here<00:00:12.610> today<00:00:12.910> to<00:00:12.969> give<00:00:13.210> you<00:00:13.360> an 00:00:13.500 --> 00:00:13.510 align:start position:0% very much here today to give you an 00:00:13.510 --> 00:00:15.240 align:start position:0% very much here today to give you an update<00:00:13.900> on<00:00:14.110> what<00:00:14.679> we've<00:00:14.830> done<00:00:15.009> in<00:00:15.130> the<00:00:15.219> last 00:00:15.240 --> 00:00:15.250 align:start position:0% update on what we've done in the last 00:00:15.250 --> 00:00:19.440 align:start position:0% update on what we've done in the last year<00:00:15.820> and<00:00:16.540> what<00:00:16.900> we're<00:00:17.050> up<00:00:17.080> to<00:00:17.200> now<00:00:17.970> so<00:00:18.970> first 00:00:19.440 --> 00:00:19.450 align:start position:0% year and what we're up to now so first 00:00:19.450 --> 00:00:22.050 align:start position:0% year and what we're up to now so first for<00:00:19.840> the<00:00:19.960> few<00:00:20.619> of<00:00:20.649> you<00:00:20.860> in<00:00:20.919> the<00:00:21.070> hall<00:00:21.220> who<00:00:21.489> may 00:00:22.050 --> 00:00:22.060 align:start position:0% for the few of you in the hall who may 00:00:22.060 --> 00:00:23.819 align:start position:0% for the few of you in the hall who may not<00:00:22.239> already<00:00:22.419> be<00:00:22.540> intimately<00:00:23.320> familiar<00:00:23.410> with 00:00:23.819 --> 00:00:23.829 align:start position:0% not already be intimately familiar with 00:00:23.829 --> 00:00:25.800 align:start position:0% not already be intimately familiar with the<00:00:23.950> etherium<00:00:24.279> name<00:00:24.430> service<00:00:24.759> what<00:00:24.970> is<00:00:25.090> it 00:00:25.800 --> 00:00:25.810 align:start position:0% the etherium name service what is it 00:00:25.810 --> 00:00:30.060 align:start position:0% the etherium name service what is it the<00:00:26.050> ENS<00:00:26.829> is<00:00:27.070> a<00:00:27.430> naming<00:00:28.239> system<00:00:28.660> that<00:00:29.230> is<00:00:29.380> solds 00:00:30.060 --> 00:00:30.070 align:start position:0% the ENS is a naming system that is solds 00:00:30.070 --> 00:00:31.769 align:start position:0% the ENS is a naming system that is solds what<00:00:30.250> we<00:00:30.369> call<00:00:30.520> Zuko's<00:00:30.880> triangle<00:00:31.419> it's<00:00:31.660> a 00:00:31.769 --> 00:00:31.779 align:start position:0% what we call Zuko's triangle it's a 00:00:31.779 --> 00:00:34.229 align:start position:0% what we call Zuko's triangle it's a trilemma<00:00:32.140> that<00:00:32.439> says<00:00:32.680> no<00:00:33.370> naming<00:00:33.700> servers<00:00:34.030> can 00:00:34.229 --> 00:00:34.239 align:start position:0% trilemma that says no naming servers can 00:00:34.239 --> 00:00:36.330 align:start position:0% trilemma that says no naming servers can be<00:00:34.270> human<00:00:34.719> meaningful<00:00:35.200> decentralized<00:00:36.010> and 00:00:36.330 --> 00:00:36.340 align:start position:0% be human meaningful decentralized and 00:00:36.340 --> 00:00:38.790 align:start position:0% be human meaningful decentralized and secure<00:00:36.700> all<00:00:36.940> at<00:00:37.150> once<00:00:37.330> and<00:00:37.660> for<00:00:38.350> a<00:00:38.380> long<00:00:38.560> time 00:00:38.790 --> 00:00:38.800 align:start position:0% secure all at once and for a long time 00:00:38.800 --> 00:00:40.380 align:start position:0% secure all at once and for a long time people<00:00:39.100> believed<00:00:39.460> that<00:00:39.490> was<00:00:39.790> probably<00:00:40.000> true 00:00:40.380 --> 00:00:40.390 align:start position:0% people believed that was probably true 00:00:40.390 --> 00:00:42.600 align:start position:0% people believed that was probably true the<00:00:40.900> advent<00:00:41.260> of<00:00:41.410> consensus<00:00:42.100> systems<00:00:42.430> with 00:00:42.600 --> 00:00:42.610 align:start position:0% the advent of consensus systems with 00:00:42.610 --> 00:00:44.720 align:start position:0% the advent of consensus systems with block<00:00:42.820> chains<00:00:43.090> has<00:00:43.360> made<00:00:43.630> that<00:00:43.810> untrue<00:00:44.230> and 00:00:44.720 --> 00:00:44.730 align:start position:0% block chains has made that untrue and 00:00:44.730 --> 00:00:46.800 align:start position:0% block chains has made that untrue and following<00:00:45.730> a<00:00:45.820> named<00:00:46.000> Queen's<00:00:46.270> footsteps 00:00:46.800 --> 00:00:46.810 align:start position:0% following a named Queen's footsteps 00:00:46.810 --> 00:00:49.340 align:start position:0% following a named Queen's footsteps we've<00:00:47.590> been<00:00:47.920> able<00:00:48.040> to<00:00:48.160> launch<00:00:48.340> ENS<00:00:48.850> which<00:00:49.120> is 00:00:49.340 --> 00:00:49.350 align:start position:0% we've been able to launch ENS which is 00:00:49.350 --> 00:00:51.360 align:start position:0% we've been able to launch ENS which is satisfies<00:00:50.350> all<00:00:50.590> three<00:00:50.920> of<00:00:51.010> those<00:00:51.130> properties 00:00:51.360 --> 00:00:51.370 align:start position:0% satisfies all three of those properties 00:00:51.370 --> 00:00:55.470 align:start position:0% satisfies all three of those properties and<00:00:51.990> so<00:00:52.990> Ian<00:00:53.530> is<00:00:53.680> the<00:00:54.190> etherium<00:00:54.640> name<00:00:54.850> service 00:00:55.470 --> 00:00:55.480 align:start position:0% and so Ian is the etherium name service 00:00:55.480 --> 00:00:57.540 align:start position:0% and so Ian is the etherium name service it's<00:00:55.870> a<00:00:56.020> naming<00:00:56.200> service<00:00:56.590> built<00:00:56.829> on<00:00:57.040> etherium 00:00:57.540 --> 00:00:57.550 align:start position:0% it's a naming service built on etherium 00:00:57.550 --> 00:00:59.220 align:start position:0% it's a naming service built on etherium but<00:00:57.970> that<00:00:58.090> doesn't<00:00:58.329> mean<00:00:58.420> it's<00:00:58.630> just<00:00:58.930> for 00:00:59.220 --> 00:00:59.230 align:start position:0% but that doesn't mean it's just for 00:00:59.230 --> 00:01:01.080 align:start position:0% but that doesn't mean it's just for etherium<00:00:59.800> it's<00:01:00.010> not<00:01:00.250> for<00:01:00.489> naming<00:01:00.670> just 00:01:01.080 --> 00:01:01.090 align:start position:0% etherium it's not for naming just 00:01:01.090 --> 00:01:02.790 align:start position:0% etherium it's not for naming just aetherium<00:01:01.510> resources<00:01:02.050> you<00:01:02.260> can<00:01:02.380> use<00:01:02.440> it<00:01:02.710> to 00:01:02.790 --> 00:01:02.800 align:start position:0% aetherium resources you can use it to 00:01:02.800 --> 00:01:05.819 align:start position:0% aetherium resources you can use it to name<00:01:02.980> ipfs<00:01:03.579> content<00:01:04.089> swarm<00:01:04.420> content<00:01:04.960> you<00:01:05.680> can 00:01:05.819 --> 00:01:05.829 align:start position:0% name ipfs content swarm content you can 00:01:05.829 --> 00:01:07.800 align:start position:0% name ipfs content swarm content you can use<00:01:05.950> it<00:01:06.070> to<00:01:06.130> insert<00:01:06.369> text<00:01:06.759> records<00:01:07.240> you<00:01:07.689> can 00:01:07.800 --> 00:01:07.810 align:start position:0% use it to insert text records you can 00:01:07.810 --> 00:01:09.480 align:start position:0% use it to insert text records you can use<00:01:07.930> it<00:01:08.020> to<00:01:08.079> point<00:01:08.259> onion<00:01:08.620> sites<00:01:08.920> as<00:01:09.250> I'll<00:01:09.460> show 00:01:09.480 --> 00:01:09.490 align:start position:0% use it to point onion sites as I'll show 00:01:09.490 --> 00:01:13.200 align:start position:0% use it to point onion sites as I'll show you<00:01:09.880> later<00:01:10.950> so<00:01:11.950> we<00:01:12.100> really<00:01:12.370> want<00:01:12.550> it<00:01:12.670> to<00:01:12.700> be<00:01:12.880> the 00:01:13.200 --> 00:01:13.210 align:start position:0% you later so we really want it to be the 00:01:13.210 --> 00:01:15.210 align:start position:0% you later so we really want it to be the new<00:01:13.659> naming<00:01:13.990> service<00:01:14.320> for<00:01:14.440> the<00:01:14.500> internet<00:01:14.920> that 00:01:15.210 --> 00:01:15.220 align:start position:0% new naming service for the internet that 00:01:15.220 --> 00:01:16.920 align:start position:0% new naming service for the internet that satisfies<00:01:15.729> all<00:01:15.909> three<00:01:16.210> of<00:01:16.300> those<00:01:16.450> important 00:01:16.920 --> 00:01:16.930 align:start position:0% satisfies all three of those important 00:01:16.930 --> 00:01:20.070 align:start position:0% satisfies all three of those important properties<00:01:18.090> so<00:01:19.090> today<00:01:19.330> I'm<00:01:19.659> going<00:01:19.810> to<00:01:19.900> talk 00:01:20.070 --> 00:01:20.080 align:start position:0% properties so today I'm going to talk 00:01:20.080 --> 00:01:22.410 align:start position:0% properties so today I'm going to talk about<00:01:20.370> what<00:01:21.370> we've<00:01:21.520> done<00:01:21.640> in<00:01:21.760> the<00:01:21.850> last<00:01:21.880> year 00:01:22.410 --> 00:01:22.420 align:start position:0% about what we've done in the last year 00:01:22.420 --> 00:01:24.630 align:start position:0% about what we've done in the last year and<00:01:22.659> how<00:01:22.900> things<00:01:23.110> have<00:01:23.260> been<00:01:23.290> going<00:01:23.430> I'm<00:01:24.430> going 00:01:24.630 --> 00:01:24.640 align:start position:0% and how things have been going I'm going 00:01:24.640 --> 00:01:26.969 align:start position:0% and how things have been going I'm going to<00:01:24.700> talk<00:01:24.880> about<00:01:24.909> our<00:01:25.690> migration<00:01:26.140> process<00:01:26.740> to 00:01:26.969 --> 00:01:26.979 align:start position:0% to talk about our migration process to 00:01:26.979 --> 00:01:29.010 align:start position:0% to talk about our migration process to the<00:01:27.070> permanent<00:01:27.310> registrar<00:01:27.940> I'm<00:01:28.780> going<00:01:28.960> to 00:01:29.010 --> 00:01:29.020 align:start position:0% the permanent registrar I'm going to 00:01:29.020 --> 00:01:31.080 align:start position:0% the permanent registrar I'm going to talk<00:01:29.200> about<00:01:29.470> the<00:01:29.710> short<00:01:30.010> name<00:01:30.220> option<00:01:30.670> process 00:01:31.080 --> 00:01:31.090 align:start position:0% talk about the short name option process 00:01:31.090 --> 00:01:33.899 align:start position:0% talk about the short name option process which<00:01:31.299> is<00:01:31.420> underway<00:01:31.720> currently<00:01:32.460> then<00:01:33.460> about 00:01:33.899 --> 00:01:33.909 align:start position:0% which is underway currently then about 00:01:33.909 --> 00:01:36.120 align:start position:0% which is underway currently then about DNS<00:01:34.390> namespace<00:01:34.659> integration<00:01:35.590> which<00:01:35.830> is<00:01:35.979> how 00:01:36.120 --> 00:01:36.130 align:start position:0% DNS namespace integration which is how 00:01:36.130 --> 00:01:37.920 align:start position:0% DNS namespace integration which is how we're<00:01:36.340> making<00:01:36.670> it<00:01:36.760> possible<00:01:37.240> for<00:01:37.299> you<00:01:37.570> to<00:01:37.630> use 00:01:37.920 --> 00:01:37.930 align:start position:0% we're making it possible for you to use 00:01:37.930 --> 00:01:42.480 align:start position:0% we're making it possible for you to use your<00:01:38.560> DNS<00:01:39.070> names<00:01:39.369> inside<00:01:40.330> ENS<00:01:40.860> our<00:01:41.860> IP<00:01:42.130> Affairs 00:01:42.480 --> 00:01:42.490 align:start position:0% your DNS names inside ENS our IP Affairs 00:01:42.490 --> 00:01:44.340 align:start position:0% your DNS names inside ENS our IP Affairs and<00:01:42.640> onion<00:01:42.850> integrations<00:01:43.479> and<00:01:43.900> then<00:01:44.080> a<00:01:44.110> brief 00:01:44.340 --> 00:01:44.350 align:start position:0% and onion integrations and then a brief 00:01:44.350 --> 00:01:46.050 align:start position:0% and onion integrations and then a brief preview<00:01:44.680> of<00:01:45.070> the<00:01:45.220> things<00:01:45.430> we're<00:01:45.610> working<00:01:45.640> on 00:01:46.050 --> 00:01:46.060 align:start position:0% preview of the things we're working on 00:01:46.060 --> 00:01:47.460 align:start position:0% preview of the things we're working on now<00:01:46.240> and<00:01:46.270> what<00:01:46.750> we're<00:01:46.900> looking<00:01:47.170> forward<00:01:47.380> to 00:01:47.460 --> 00:01:47.470 align:start position:0% now and what we're looking forward to 00:01:47.470 --> 00:01:50.160 align:start position:0% now and what we're looking forward to launching<00:01:47.860> in<00:01:47.979> the<00:01:48.010> next<00:01:48.100> year<00:01:48.750> so<00:01:49.750> first<00:01:50.020> of 00:01:50.160 --> 00:01:50.170 align:start position:0% launching in the next year so first of 00:01:50.170 --> 00:01:53.250 align:start position:0% launching in the next year so first of all<00:01:50.229> the<00:01:50.920> last<00:01:51.130> year<00:01:51.430> at<00:01:51.520> a<00:01:51.610> glance<00:01:52.200> this<00:01:53.200> is 00:01:53.250 --> 00:01:53.260 align:start position:0% all the last year at a glance this is 00:01:53.260 --> 00:01:55.620 align:start position:0% all the last year at a glance this is the<00:01:53.650> number<00:01:54.159> of<00:01:54.250> names<00:01:54.520> registered<00:01:55.180> on<00:01:55.299> the<00:01:55.390> NS 00:01:55.620 --> 00:01:55.630 align:start position:0% the number of names registered on the NS 00:01:55.630 --> 00:01:58.320 align:start position:0% the number of names registered on the NS how<00:01:55.930> it's<00:01:56.110> evolved<00:01:56.680> over<00:01:56.979> the<00:01:57.520> time<00:01:58.060> since 00:01:58.320 --> 00:01:58.330 align:start position:0% how it's evolved over the time since 00:01:58.330 --> 00:02:00.660 align:start position:0% how it's evolved over the time since we've<00:01:58.479> launched<00:01:58.840> the<00:01:59.680> top<00:01:59.920> line<00:02:00.189> there<00:02:00.460> and 00:02:00.660 --> 00:02:00.670 align:start position:0% we've launched the top line there and 00:02:00.670 --> 00:02:02.609 align:start position:0% we've launched the top line there and the<00:02:00.790> blue<00:02:00.970> is<00:02:01.270> the<00:02:01.299> total<00:02:01.780> number<00:02:02.020> of<00:02:02.049> names<00:02:02.320> in 00:02:02.609 --> 00:02:02.619 align:start position:0% the blue is the total number of names in 00:02:02.619 --> 00:02:04.859 align:start position:0% the blue is the total number of names in the<00:02:02.710> system<00:02:03.040> the<00:02:03.850> second<00:02:04.240> line<00:02:04.390> there<00:02:04.630> in<00:02:04.780> the 00:02:04.859 --> 00:02:04.869 align:start position:0% the system the second line there in the 00:02:04.869 --> 00:02:06.450 align:start position:0% the system the second line there in the red<00:02:05.080> is<00:02:05.470> the<00:02:05.680> number<00:02:05.860> of<00:02:05.920> names<00:02:06.159> with 00:02:06.450 --> 00:02:06.460 align:start position:0% red is the number of names with 00:02:06.460 --> 00:02:08.820 align:start position:0% red is the number of names with resolvers<00:02:07.000> set<00:02:07.270> and<00:02:07.540> the<00:02:07.930> third<00:02:08.140> line<00:02:08.439> is<00:02:08.709> the 00:02:08.820 --> 00:02:08.830 align:start position:0% resolvers set and the third line is the 00:02:08.830 --> 00:02:10.259 align:start position:0% resolvers set and the third line is the number<00:02:09.039> of<00:02:09.129> names<00:02:09.310> that<00:02:09.670> resolve<00:02:10.030> two 00:02:10.259 --> 00:02:10.269 align:start position:0% number of names that resolve two 00:02:10.269 --> 00:02:12.449 align:start position:0% number of names that resolve two addresses<00:02:10.500> so<00:02:11.500> as<00:02:11.620> you<00:02:11.709> can<00:02:11.799> see<00:02:11.860> we've<00:02:12.250> had 00:02:12.449 --> 00:02:12.459 align:start position:0% addresses so as you can see we've had 00:02:12.459 --> 00:02:14.819 align:start position:0% addresses so as you can see we've had steady<00:02:12.790> growth<00:02:13.060> in<00:02:13.659> the<00:02:13.840> nearly<00:02:14.469> three<00:02:14.799> years 00:02:14.819 --> 00:02:14.829 align:start position:0% steady growth in the nearly three years 00:02:14.829 --> 00:02:17.069 align:start position:0% steady growth in the nearly three years since<00:02:15.099> we've<00:02:15.459> launched<00:02:15.790> and<00:02:16.659> let's<00:02:16.870> drill 00:02:17.069 --> 00:02:17.079 align:start position:0% since we've launched and let's drill 00:02:17.079 --> 00:02:18.420 align:start position:0% since we've launched and let's drill down<00:02:17.109> on<00:02:17.290> that<00:02:17.439> a<00:02:17.590> little<00:02:17.739> bit 00:02:18.420 --> 00:02:18.430 align:start position:0% down on that a little bit 00:02:18.430 --> 00:02:21.660 align:start position:0% down on that a little bit October<00:02:19.180> 2018<00:02:19.630> so<00:02:20.110> this<00:02:20.230> time<00:02:20.500> last<00:02:20.800> year<00:02:20.980> we 00:02:21.660 --> 00:02:21.670 align:start position:0% October 2018 so this time last year we 00:02:21.670 --> 00:02:23.130 align:start position:0% October 2018 so this time last year we had<00:02:21.700> two<00:02:22.060> hundred<00:02:22.120> twenty-four<00:02:22.720> thousand 00:02:23.130 --> 00:02:23.140 align:start position:0% had two hundred twenty-four thousand 00:02:23.140 --> 00:02:24.960 align:start position:0% had two hundred twenty-four thousand names<00:02:23.320> registered<00:02:23.560> and<00:02:24.160> this<00:02:24.400> year<00:02:24.610> that's<00:02:24.820> up 00:02:24.960 --> 00:02:24.970 align:start position:0% names registered and this year that's up 00:02:24.970 --> 00:02:27.120 align:start position:0% names registered and this year that's up to<00:02:25.090> three<00:02:25.300> hundred<00:02:25.390> and<00:02:25.630> ten<00:02:25.810> thousand<00:02:26.290> but<00:02:26.890> I 00:02:27.120 --> 00:02:27.130 align:start position:0% to three hundred and ten thousand but I 00:02:27.130 --> 00:02:28.920 align:start position:0% to three hundred and ten thousand but I think<00:02:27.550> the<00:02:27.640> other<00:02:27.790> two<00:02:28.000> figures<00:02:28.360> are<00:02:28.540> the<00:02:28.600> more 00:02:28.920 --> 00:02:28.930 align:start position:0% think the other two figures are the more 00:02:28.930 --> 00:02:31.230 align:start position:0% think the other two figures are the more interesting<00:02:29.620> ones<00:02:29.800> first<00:02:30.490> of<00:02:30.670> all<00:02:30.760> we've<00:02:31.090> got 00:02:31.230 --> 00:02:31.240 align:start position:0% interesting ones first of all we've got 00:02:31.240 --> 00:02:32.850 align:start position:0% interesting ones first of all we've got the<00:02:31.330> number<00:02:31.510> of<00:02:31.570> names<00:02:31.810> with<00:02:32.080> resolvers<00:02:32.590> and 00:02:32.850 --> 00:02:32.860 align:start position:0% the number of names with resolvers and 00:02:32.860 --> 00:02:34.800 align:start position:0% the number of names with resolvers and so<00:02:33.070> this<00:02:33.220> is<00:02:33.370> the<00:02:33.490> first<00:02:33.730> step<00:02:34.060> and<00:02:34.270> setting<00:02:34.690> up 00:02:34.800 --> 00:02:34.810 align:start position:0% so this is the first step and setting up 00:02:34.810 --> 00:02:37.260 align:start position:0% so this is the first step and setting up your<00:02:34.960> name<00:02:35.200> you<00:02:35.440> first<00:02:35.710> by<00:02:36.190> the<00:02:36.250> name<00:02:36.550> and<00:02:36.820> then 00:02:37.260 --> 00:02:37.270 align:start position:0% your name you first by the name and then 00:02:37.270 --> 00:02:39.210 align:start position:0% your name you first by the name and then you<00:02:37.360> set<00:02:37.600> a<00:02:37.630> resolve<00:02:38.020> a<00:02:38.140> contract<00:02:38.590> for<00:02:38.830> it<00:02:39.010> and 00:02:39.210 --> 00:02:39.220 align:start position:0% you set a resolve a contract for it and 00:02:39.220 --> 00:02:41.310 align:start position:0% you set a resolve a contract for it and if<00:02:40.000> you're<00:02:40.270> buying<00:02:40.540> the<00:02:40.780> name<00:02:40.930> just<00:02:41.170> to 00:02:41.310 --> 00:02:41.320 align:start position:0% if you're buying the name just to 00:02:41.320 --> 00:02:43.650 align:start position:0% if you're buying the name just to speculate<00:02:41.800> on<00:02:41.830> it<00:02:41.980> to<00:02:42.760> sell<00:02:43.210> it<00:02:43.240> to<00:02:43.480> somebody 00:02:43.650 --> 00:02:43.660 align:start position:0% speculate on it to sell it to somebody 00:02:43.660 --> 00:02:44.670 align:start position:0% speculate on it to sell it to somebody later<00:02:44.020> for<00:02:44.320> more 00:02:44.670 --> 00:02:44.680 align:start position:0% later for more 00:02:44.680 --> 00:02:46.590 align:start position:0% later for more there's<00:02:45.340> no<00:02:45.460> reason<00:02:45.700> you'd<00:02:45.820> set<00:02:46.030> this<00:02:46.150> up<00:02:46.330> so 00:02:46.590 --> 00:02:46.600 align:start position:0% there's no reason you'd set this up so 00:02:46.600 --> 00:02:48.330 align:start position:0% there's no reason you'd set this up so this<00:02:46.720> is<00:02:46.780> a<00:02:46.900> reasonably<00:02:47.440> good<00:02:47.470> metric<00:02:48.070> for 00:02:48.330 --> 00:02:48.340 align:start position:0% this is a reasonably good metric for 00:02:48.340 --> 00:02:51.660 align:start position:0% this is a reasonably good metric for actual<00:02:48.850> adoption<00:02:49.090> and<00:02:49.450> use<00:02:49.720> for<00:02:50.440> ENS<00:02:50.830> in<00:02:51.430> the 00:02:51.660 --> 00:02:51.670 align:start position:0% actual adoption and use for ENS in the 00:02:51.670 --> 00:02:53.430 align:start position:0% actual adoption and use for ENS in the wild<00:02:52.000> and<00:02:52.210> so<00:02:52.720> it's<00:02:52.870> gone<00:02:53.050> up<00:02:53.230> from 00:02:53.430 --> 00:02:53.440 align:start position:0% wild and so it's gone up from 00:02:53.440 --> 00:02:55.620 align:start position:0% wild and so it's gone up from twenty-eight<00:02:54.190> thousand<00:02:54.700> at<00:02:54.970> this<00:02:55.240> time<00:02:55.450> last 00:02:55.620 --> 00:02:55.630 align:start position:0% twenty-eight thousand at this time last 00:02:55.630 --> 00:02:57.900 align:start position:0% twenty-eight thousand at this time last year<00:02:55.900> to<00:02:56.080> sixty<00:02:56.470> thousand<00:02:56.890> now<00:02:57.040> and<00:02:57.280> it's<00:02:57.760> not 00:02:57.900 --> 00:02:57.910 align:start position:0% year to sixty thousand now and it's not 00:02:57.910 --> 00:02:59.070 align:start position:0% year to sixty thousand now and it's not just<00:02:58.030> an<00:02:58.210> increase<00:02:58.510> in<00:02:58.690> absolute<00:02:59.050> numbers 00:02:59.070 --> 00:02:59.080 align:start position:0% just an increase in absolute numbers 00:02:59.080 --> 00:03:01.350 align:start position:0% just an increase in absolute numbers it's<00:02:59.620> an<00:02:59.710> increase<00:03:00.040> in<00:03:00.220> percentage<00:03:00.700> from 00:03:01.350 --> 00:03:01.360 align:start position:0% it's an increase in percentage from 00:03:01.360 --> 00:03:02.850 align:start position:0% it's an increase in percentage from twelve<00:03:01.750> and<00:03:01.870> a<00:03:01.900> half<00:03:01.930> percent<00:03:02.080> all<00:03:02.590> the<00:03:02.620> way<00:03:02.770> up 00:03:02.850 --> 00:03:02.860 align:start position:0% twelve and a half percent all the way up 00:03:02.860 --> 00:03:04.590 align:start position:0% twelve and a half percent all the way up to<00:03:02.980> that<00:03:03.100> twenty<00:03:03.430> percent<00:03:03.550> so<00:03:04.270> we're<00:03:04.420> really 00:03:04.590 --> 00:03:04.600 align:start position:0% to that twenty percent so we're really 00:03:04.600 --> 00:03:05.880 align:start position:0% to that twenty percent so we're really pleased<00:03:04.900> with<00:03:05.050> that<00:03:05.110> and<00:03:05.290> we<00:03:05.500> want<00:03:05.680> to<00:03:05.740> keep 00:03:05.880 --> 00:03:05.890 align:start position:0% pleased with that and we want to keep 00:03:05.890 --> 00:03:07.050 align:start position:0% pleased with that and we want to keep monitoring<00:03:06.250> this<00:03:06.460> and<00:03:06.520> we<00:03:06.730> hope<00:03:06.850> it'll 00:03:07.050 --> 00:03:07.060 align:start position:0% monitoring this and we hope it'll 00:03:07.060 --> 00:03:08.040 align:start position:0% monitoring this and we hope it'll continue<00:03:07.360> to<00:03:07.600> grow 00:03:08.040 --> 00:03:08.050 align:start position:0% continue to grow 00:03:08.050 --> 00:03:11.490 align:start position:0% continue to grow likewise<00:03:09.030> names<00:03:10.450> sorry<00:03:10.750> addresses<00:03:11.200> aren't 00:03:11.490 --> 00:03:11.500 align:start position:0% likewise names sorry addresses aren't 00:03:11.500 --> 00:03:13.380 align:start position:0% likewise names sorry addresses aren't the<00:03:11.590> only<00:03:11.710> thing<00:03:12.100> you<00:03:12.370> can<00:03:12.580> translate<00:03:13.000> ENS 00:03:13.380 --> 00:03:13.390 align:start position:0% the only thing you can translate ENS 00:03:13.390 --> 00:03:15.450 align:start position:0% the only thing you can translate ENS names<00:03:13.630> to<00:03:13.930> but<00:03:14.470> they're<00:03:14.680> probably<00:03:15.040> the<00:03:15.310> most 00:03:15.450 --> 00:03:15.460 align:start position:0% names to but they're probably the most 00:03:15.460 --> 00:03:17.490 align:start position:0% names to but they're probably the most popular<00:03:15.700> application<00:03:16.480> at<00:03:16.540> the<00:03:16.630> moment<00:03:16.960> so<00:03:17.470> we 00:03:17.490 --> 00:03:17.500 align:start position:0% popular application at the moment so we 00:03:17.500 --> 00:03:19.170 align:start position:0% popular application at the moment so we can<00:03:17.650> monitor<00:03:17.950> similarly<00:03:18.730> the<00:03:18.880> number<00:03:18.970> of 00:03:19.170 --> 00:03:19.180 align:start position:0% can monitor similarly the number of 00:03:19.180 --> 00:03:20.730 align:start position:0% can monitor similarly the number of names<00:03:19.360> of<00:03:19.510> the<00:03:19.600> dresses<00:03:19.990> and<00:03:20.230> that's<00:03:20.350> up<00:03:20.500> from 00:03:20.730 --> 00:03:20.740 align:start position:0% names of the dresses and that's up from 00:03:20.740 --> 00:03:22.320 align:start position:0% names of the dresses and that's up from eight<00:03:20.980> and<00:03:21.190> a<00:03:21.220> half<00:03:21.250> percent<00:03:21.580> a<00:03:21.850> year<00:03:21.880> ago<00:03:22.270> to 00:03:22.320 --> 00:03:22.330 align:start position:0% eight and a half percent a year ago to 00:03:22.330 --> 00:03:25.080 align:start position:0% eight and a half percent a year ago to twelve<00:03:23.230> percent<00:03:23.500> today<00:03:23.650> so<00:03:24.610> we're<00:03:24.910> really 00:03:25.080 --> 00:03:25.090 align:start position:0% twelve percent today so we're really 00:03:25.090 --> 00:03:26.850 align:start position:0% twelve percent today so we're really encouraged<00:03:25.540> to<00:03:25.750> see<00:03:25.930> that<00:03:25.960> this<00:03:26.290> growth<00:03:26.620> in 00:03:26.850 --> 00:03:26.860 align:start position:0% encouraged to see that this growth in 00:03:26.860 --> 00:03:29.460 align:start position:0% encouraged to see that this growth in ENS<00:03:27.220> isn't<00:03:27.640> just<00:03:27.940> more<00:03:28.540> people<00:03:28.870> speculating 00:03:29.460 --> 00:03:29.470 align:start position:0% ENS isn't just more people speculating 00:03:29.470 --> 00:03:31.440 align:start position:0% ENS isn't just more people speculating on<00:03:29.560> names<00:03:29.830> more<00:03:30.070> people<00:03:30.400> died<00:03:30.520> hoping<00:03:31.210> to<00:03:31.300> make 00:03:31.440 --> 00:03:31.450 align:start position:0% on names more people died hoping to make 00:03:31.450 --> 00:03:33.300 align:start position:0% on names more people died hoping to make a<00:03:31.480> profit<00:03:31.600> off<00:03:32.020> reselling<00:03:32.560> them<00:03:32.710> but<00:03:33.160> it's 00:03:33.300 --> 00:03:33.310 align:start position:0% a profit off reselling them but it's 00:03:33.310 --> 00:03:34.740 align:start position:0% a profit off reselling them but it's more<00:03:33.490> people<00:03:33.790> actually<00:03:33.970> using<00:03:34.420> them<00:03:34.720> for 00:03:34.740 --> 00:03:34.750 align:start position:0% more people actually using them for 00:03:34.750 --> 00:03:38.040 align:start position:0% more people actually using them for their<00:03:34.990> intended<00:03:35.260> purpose<00:03:36.450> so<00:03:37.450> next<00:03:37.630> up<00:03:37.840> I'm 00:03:38.040 --> 00:03:38.050 align:start position:0% their intended purpose so next up I'm 00:03:38.050 --> 00:03:40.370 align:start position:0% their intended purpose so next up I'm going<00:03:38.170> to<00:03:38.260> talk<00:03:38.410> about<00:03:38.680> a<00:03:38.950> migration<00:03:39.730> process 00:03:40.370 --> 00:03:40.380 align:start position:0% going to talk about a migration process 00:03:40.380 --> 00:03:44.280 align:start position:0% going to talk about a migration process so<00:03:41.380> a<00:03:41.680> in<00:03:42.520> May<00:03:42.880> on<00:03:43.120> May<00:03:43.300> the<00:03:43.330> 4th<00:03:43.690> we<00:03:43.960> launched 00:03:44.280 --> 00:03:44.290 align:start position:0% so a in May on May the 4th we launched 00:03:44.290 --> 00:03:45.750 align:start position:0% so a in May on May the 4th we launched the<00:03:44.470> new<00:03:44.500> permanent<00:03:45.100> registrar<00:03:45.730> that 00:03:45.750 --> 00:03:45.760 align:start position:0% the new permanent registrar that 00:03:45.760 --> 00:03:47.970 align:start position:0% the new permanent registrar that replaced<00:03:46.330> the<00:03:46.570> option<00:03:46.930> registrar<00:03:47.470> which 00:03:47.970 --> 00:03:47.980 align:start position:0% replaced the option registrar which 00:03:47.980 --> 00:03:50.370 align:start position:0% replaced the option registrar which required<00:03:48.460> a<00:03:48.730> lengthy<00:03:49.420> auction<00:03:49.750> process<00:03:49.930> in 00:03:50.370 --> 00:03:50.380 align:start position:0% required a lengthy auction process in 00:03:50.380 --> 00:03:52.740 align:start position:0% required a lengthy auction process in order<00:03:50.470> to<00:03:50.680> register<00:03:50.830> names<00:03:51.360> with<00:03:52.360> the<00:03:52.570> new 00:03:52.740 --> 00:03:52.750 align:start position:0% order to register names with the new 00:03:52.750 --> 00:03:56.970 align:start position:0% order to register names with the new instant<00:03:53.470> registration<00:03:54.450> so<00:03:55.450> jus<00:03:55.930> when<00:03:56.860> we 00:03:56.970 --> 00:03:56.980 align:start position:0% instant registration so jus when we 00:03:56.980 --> 00:03:58.140 align:start position:0% instant registration so jus when we launched<00:03:57.190> that<00:03:57.310> there's<00:03:57.700> a<00:03:57.760> one-year 00:03:58.140 --> 00:03:58.150 align:start position:0% launched that there's a one-year 00:03:58.150 --> 00:04:00.180 align:start position:0% launched that there's a one-year migration<00:03:58.690> period<00:03:58.900> during<00:03:59.650> that<00:03:59.800> period 00:04:00.180 --> 00:04:00.190 align:start position:0% migration period during that period 00:04:00.190 --> 00:04:01.710 align:start position:0% migration period during that period anyone<00:04:00.550> who<00:04:00.670> owned<00:04:00.850> a<00:04:01.030> name<00:04:01.240> on<00:04:01.270> the<00:04:01.570> old 00:04:01.710 --> 00:04:01.720 align:start position:0% anyone who owned a name on the old 00:04:01.720 --> 00:04:03.480 align:start position:0% anyone who owned a name on the old registrar<00:04:02.350> can<00:04:02.560> migrate<00:04:02.710> it<00:04:03.100> to<00:04:03.130> the<00:04:03.310> new<00:04:03.460> one 00:04:03.480 --> 00:04:03.490 align:start position:0% registrar can migrate it to the new one 00:04:03.490 --> 00:04:05.910 align:start position:0% registrar can migrate it to the new one and<00:04:03.850> when<00:04:04.330> they<00:04:04.480> do<00:04:04.540> that<00:04:04.810> they<00:04:05.380> get<00:04:05.740> their 00:04:05.910 --> 00:04:05.920 align:start position:0% and when they do that they get their 00:04:05.920 --> 00:04:07.710 align:start position:0% and when they do that they get their registration<00:04:06.070> extended<00:04:07.030> until<00:04:07.390> May<00:04:07.570> the 00:04:07.710 --> 00:04:07.720 align:start position:0% registration extended until May the 00:04:07.720 --> 00:04:10.650 align:start position:0% registration extended until May the third<00:04:07.930> 2020<00:04:08.620> and<00:04:08.800> they<00:04:09.490> get<00:04:09.610> a<00:04:09.640> full<00:04:09.850> refund<00:04:10.420> of 00:04:10.650 --> 00:04:10.660 align:start position:0% third 2020 and they get a full refund of 00:04:10.660 --> 00:04:13.080 align:start position:0% third 2020 and they get a full refund of the<00:04:11.140> deposit<00:04:11.710> they<00:04:11.830> put<00:04:12.010> down<00:04:12.220> to<00:04:12.580> originally 00:04:13.080 --> 00:04:13.090 align:start position:0% the deposit they put down to originally 00:04:13.090 --> 00:04:16.080 align:start position:0% the deposit they put down to originally register<00:04:13.540> the<00:04:13.660> name<00:04:14.310> you<00:04:15.310> also<00:04:15.730> have<00:04:15.970> the 00:04:16.080 --> 00:04:16.090 align:start position:0% register the name you also have the 00:04:16.090 --> 00:04:17.820 align:start position:0% register the name you also have the option<00:04:16.390> to<00:04:16.420> just<00:04:16.690> release<00:04:16.930> the<00:04:17.200> name<00:04:17.380> you<00:04:17.650> can 00:04:17.820 --> 00:04:17.830 align:start position:0% option to just release the name you can 00:04:17.830 --> 00:04:19.770 align:start position:0% option to just release the name you can do<00:04:17.950> that<00:04:18.100> and<00:04:18.730> you<00:04:18.820> get<00:04:18.940> deposit<00:04:19.390> back<00:04:19.570> but 00:04:19.770 --> 00:04:19.780 align:start position:0% do that and you get deposit back but 00:04:19.780 --> 00:04:21.330 align:start position:0% do that and you get deposit back but then<00:04:19.930> the<00:04:20.080> name<00:04:20.260> becomes<00:04:20.710> available<00:04:20.950> for 00:04:21.330 --> 00:04:21.340 align:start position:0% then the name becomes available for 00:04:21.340 --> 00:04:23.460 align:start position:0% then the name becomes available for registration<00:04:21.910> by<00:04:22.030> others<00:04:22.330> so<00:04:23.260> there's<00:04:23.440> a 00:04:23.460 --> 00:04:23.470 align:start position:0% registration by others so there's a 00:04:23.470 --> 00:04:25.530 align:start position:0% registration by others so there's a one-year<00:04:23.830> migration<00:04:24.310> period<00:04:24.520> the<00:04:25.390> new 00:04:25.530 --> 00:04:25.540 align:start position:0% one-year migration period the new 00:04:25.540 --> 00:04:27.510 align:start position:0% one-year migration period the new registrar<00:04:26.080> supports<00:04:26.530> instant<00:04:26.919> registration 00:04:27.510 --> 00:04:27.520 align:start position:0% registrar supports instant registration 00:04:27.520 --> 00:04:29.460 align:start position:0% registrar supports instant registration with<00:04:27.669> just<00:04:27.880> two<00:04:28.030> transactions 00:04:29.460 --> 00:04:29.470 align:start position:0% with just two transactions 00:04:29.470 --> 00:04:31.590 align:start position:0% with just two transactions and<00:04:29.770> in<00:04:30.400> order<00:04:30.550> to<00:04:30.730> keep<00:04:30.850> your<00:04:31.060> name<00:04:31.270> you<00:04:31.480> have 00:04:31.590 --> 00:04:31.600 align:start position:0% and in order to keep your name you have 00:04:31.600 --> 00:04:33.530 align:start position:0% and in order to keep your name you have to<00:04:31.690> pay<00:04:31.810> five<00:04:32.080> dollars<00:04:32.440> a<00:04:32.470> year<00:04:32.590> per<00:04:32.740> the<00:04:33.010> name 00:04:33.530 --> 00:04:33.540 align:start position:0% to pay five dollars a year per the name 00:04:33.540 --> 00:04:36.090 align:start position:0% to pay five dollars a year per the name rent<00:04:34.540> and<00:04:34.810> there's<00:04:35.140> no<00:04:35.290> limit<00:04:35.500> on<00:04:35.650> the<00:04:35.770> renewal 00:04:36.090 --> 00:04:36.100 align:start position:0% rent and there's no limit on the renewal 00:04:36.100 --> 00:04:38.280 align:start position:0% rent and there's no limit on the renewal periods<00:04:36.520> so<00:04:37.060> for<00:04:37.240> instance<00:04:37.600> some<00:04:38.140> of<00:04:38.170> these 00:04:38.280 --> 00:04:38.290 align:start position:0% periods so for instance some of these 00:04:38.290 --> 00:04:39.960 align:start position:0% periods so for instance some of these registered<00:04:38.740> Walmart<00:04:39.160> ah<00:04:39.280> teeth<00:04:39.430> and<00:04:39.670> protocol 00:04:39.960 --> 00:04:39.970 align:start position:0% registered Walmart ah teeth and protocol 00:04:39.970 --> 00:04:41.160 align:start position:0% registered Walmart ah teeth and protocol leaf<00:04:40.150> and<00:04:40.420> they've<00:04:40.660> paid<00:04:40.900> the<00:04:41.050> registration 00:04:41.160 --> 00:04:41.170 align:start position:0% leaf and they've paid the registration 00:04:41.170 --> 00:04:43.830 align:start position:0% leaf and they've paid the registration all<00:04:41.800> the<00:04:41.890> way<00:04:41.980> out<00:04:42.070> to<00:04:42.160> 2040<00:04:42.760> which<00:04:43.300> means<00:04:43.540> the 00:04:43.830 --> 00:04:43.840 align:start position:0% all the way out to 2040 which means the 00:04:43.840 --> 00:04:45.960 align:start position:0% all the way out to 2040 which means the bet<00:04:44.110> name<00:04:44.320> is<00:04:44.560> absolutely<00:04:45.340> solidly<00:04:45.790> locked 00:04:45.960 --> 00:04:45.970 align:start position:0% bet name is absolutely solidly locked 00:04:45.970 --> 00:04:48.930 align:start position:0% bet name is absolutely solidly locked into<00:04:46.150> the<00:04:46.300> system<00:04:46.630> at<00:04:46.750> least<00:04:46.870> until<00:04:47.230> then<00:04:47.940> so 00:04:48.930 --> 00:04:48.940 align:start position:0% into the system at least until then so 00:04:48.940 --> 00:04:50.910 align:start position:0% into the system at least until then so we've<00:04:49.060> had<00:04:49.180> 10,000<00:04:49.840> new<00:04:49.900> registrations<00:04:50.590> since 00:04:50.910 --> 00:04:50.920 align:start position:0% we've had 10,000 new registrations since 00:04:50.920 --> 00:04:53.280 align:start position:0% we've had 10,000 new registrations since launch<00:04:51.160> and<00:04:52.090> the<00:04:52.270> migration<00:04:52.570> process<00:04:52.930> is 00:04:53.280 --> 00:04:53.290 align:start position:0% launch and the migration process is 00:04:53.290 --> 00:04:55.830 align:start position:0% launch and the migration process is interesting<00:04:53.800> look<00:04:54.010> at<00:04:54.190> -<00:04:54.400> so<00:04:54.850> on<00:04:55.210> migration 00:04:55.830 --> 00:04:55.840 align:start position:0% interesting look at - so on migration 00:04:55.840 --> 00:04:58.050 align:start position:0% interesting look at - so on migration day<00:04:56.260> E&S<00:04:57.130> had<00:04:57.370> three<00:04:57.580> hundred<00:04:57.850> and<00:04:57.910> nine 00:04:58.050 --> 00:04:58.060 align:start position:0% day E&S had three hundred and nine 00:04:58.060 --> 00:04:59.700 align:start position:0% day E&S had three hundred and nine thousand<00:04:58.600> names<00:04:58.750> registered<00:04:59.290> in<00:04:59.410> it<00:04:59.530> and 00:04:59.700 --> 00:04:59.710 align:start position:0% thousand names registered in it and 00:04:59.710 --> 00:05:01.170 align:start position:0% thousand names registered in it and there<00:05:00.190> was<00:05:00.280> a<00:05:00.310> hundred<00:05:00.670> and<00:05:00.760> seventy-six 00:05:01.170 --> 00:05:01.180 align:start position:0% there was a hundred and seventy-six 00:05:01.180 --> 00:05:03.030 align:start position:0% there was a hundred and seventy-six thousand<00:05:01.750> ether<00:05:02.110> locked<00:05:02.440> in<00:05:02.740> the<00:05:02.860> deed 00:05:03.030 --> 00:05:03.040 align:start position:0% thousand ether locked in the deed 00:05:03.040 --> 00:05:05.220 align:start position:0% thousand ether locked in the deed contracts<00:05:03.700> so<00:05:04.000> when<00:05:04.270> you<00:05:04.360> bid<00:05:04.600> on<00:05:04.750> the<00:05:04.840> name<00:05:05.020> on 00:05:05.220 --> 00:05:05.230 align:start position:0% contracts so when you bid on the name on 00:05:05.230 --> 00:05:06.510 align:start position:0% contracts so when you bid on the name on the<00:05:05.320> interim<00:05:05.590> rich<00:05:05.770> Australia<00:05:06.220> to<00:05:06.340> put<00:05:06.490> a 00:05:06.510 --> 00:05:06.520 align:start position:0% the interim rich Australia to put a 00:05:06.520 --> 00:05:08.340 align:start position:0% the interim rich Australia to put a deposit<00:05:06.700> down<00:05:07.120> and<00:05:07.450> you<00:05:07.810> get<00:05:07.960> that<00:05:08.080> deposit 00:05:08.340 --> 00:05:08.350 align:start position:0% deposit down and you get that deposit 00:05:08.350 --> 00:05:10.080 align:start position:0% deposit down and you get that deposit back<00:05:08.740> when<00:05:09.010> you<00:05:09.100> release<00:05:09.400> the<00:05:09.430> name<00:05:09.760> or<00:05:10.000> you 00:05:10.080 --> 00:05:10.090 align:start position:0% back when you release the name or you 00:05:10.090 --> 00:05:12.180 align:start position:0% back when you release the name or you migrate<00:05:10.450> it<00:05:10.570> to<00:05:10.660> the<00:05:10.780> new<00:05:10.900> register<00:05:11.380> so<00:05:12.070> how 00:05:12.180 --> 00:05:12.190 align:start position:0% migrate it to the new register so how 00:05:12.190 --> 00:05:13.020 align:start position:0% migrate it to the new register so how are<00:05:12.250> we<00:05:12.310> doing<00:05:12.520> today 00:05:13.020 --> 00:05:13.030 align:start position:0% are we doing today 00:05:13.030 --> 00:05:15.510 align:start position:0% are we doing today today<00:05:13.690> we're<00:05:14.350> down<00:05:14.620> to<00:05:14.920> two<00:05:15.160> hundred<00:05:15.280> and 00:05:15.510 --> 00:05:15.520 align:start position:0% today we're down to two hundred and 00:05:15.520 --> 00:05:16.950 align:start position:0% today we're down to two hundred and forty-one<00:05:15.790> thousand<00:05:16.450> that<00:05:16.630> haven't<00:05:16.900> been 00:05:16.950 --> 00:05:16.960 align:start position:0% forty-one thousand that haven't been 00:05:16.960 --> 00:05:18.720 align:start position:0% forty-one thousand that haven't been migrated<00:05:17.560> or<00:05:17.680> released<00:05:17.950> we<00:05:18.370> had<00:05:18.520> four 00:05:18.720 --> 00:05:18.730 align:start position:0% migrated or released we had four 00:05:18.730 --> 00:05:20.490 align:start position:0% migrated or released we had four thousand<00:05:19.150> about<00:05:19.300> one<00:05:19.510> percent<00:05:19.930> were<00:05:20.140> released 00:05:20.490 --> 00:05:20.500 align:start position:0% thousand about one percent were released 00:05:20.500 --> 00:05:22.440 align:start position:0% thousand about one percent were released and<00:05:20.770> fifty-nine<00:05:21.670> thousand<00:05:22.210> thousand 00:05:22.440 --> 00:05:22.450 align:start position:0% and fifty-nine thousand thousand 00:05:22.450 --> 00:05:25.050 align:start position:0% and fifty-nine thousand thousand nineteen<00:05:22.780> bussines<00:05:23.110> have<00:05:23.230> been<00:05:23.350> migrated<00:05:24.060> in 00:05:25.050 --> 00:05:25.060 align:start position:0% nineteen bussines have been migrated in 00:05:25.060 --> 00:05:26.610 align:start position:0% nineteen bussines have been migrated in terms<00:05:25.330> of<00:05:25.480> the<00:05:25.540> ether<00:05:25.840> it's<00:05:26.050> actually<00:05:26.380> even 00:05:26.610 --> 00:05:26.620 align:start position:0% terms of the ether it's actually even 00:05:26.620 --> 00:05:29.430 align:start position:0% terms of the ether it's actually even less<00:05:26.850> the<00:05:27.850> thirteen<00:05:28.450> percent<00:05:28.630> have<00:05:28.990> been<00:05:29.020> of 00:05:29.430 --> 00:05:29.440 align:start position:0% less the thirteen percent have been of 00:05:29.440 --> 00:05:31.110 align:start position:0% less the thirteen percent have been of the<00:05:29.650> ether<00:05:29.950> deposits<00:05:30.460> have<00:05:30.580> been<00:05:30.610> returned 00:05:31.110 --> 00:05:31.120 align:start position:0% the ether deposits have been returned 00:05:31.120 --> 00:05:33.660 align:start position:0% the ether deposits have been returned and<00:05:31.360> eighty<00:05:32.230> six<00:05:32.590> percent<00:05:32.710> are<00:05:33.070> remaining<00:05:33.490> and 00:05:33.660 --> 00:05:33.670 align:start position:0% and eighty six percent are remaining and 00:05:33.670 --> 00:05:35.310 align:start position:0% and eighty six percent are remaining and you<00:05:33.910> can<00:05:34.030> sort<00:05:34.210> of<00:05:34.270> see<00:05:34.510> the<00:05:34.540> progress<00:05:34.870> here 00:05:35.310 --> 00:05:35.320 align:start position:0% you can sort of see the progress here 00:05:35.320 --> 00:05:38.520 align:start position:0% you can sort of see the progress here with<00:05:36.100> the<00:05:36.220> exception<00:05:36.730> of<00:05:36.850> a<00:05:36.970> blip<00:05:37.510> around<00:05:37.930> the 00:05:38.520 --> 00:05:38.530 align:start position:0% with the exception of a blip around the 00:05:38.530 --> 00:05:40.440 align:start position:0% with the exception of a blip around the middle<00:05:38.770> of<00:05:38.860> the<00:05:38.950> year<00:05:39.160> it's<00:05:39.790> been<00:05:39.940> reasonably 00:05:40.440 --> 00:05:40.450 align:start position:0% middle of the year it's been reasonably 00:05:40.450 --> 00:05:42.000 align:start position:0% middle of the year it's been reasonably steady<00:05:40.630> but<00:05:40.960> it's<00:05:41.080> actually<00:05:41.440> tapering<00:05:41.800> off<00:05:41.950> a 00:05:42.000 --> 00:05:42.010 align:start position:0% steady but it's actually tapering off a 00:05:42.010 --> 00:05:44.670 align:start position:0% steady but it's actually tapering off a little<00:05:42.310> bit<00:05:42.430> so<00:05:42.970> if<00:05:43.330> you<00:05:43.480> have<00:05:43.690> ENS<00:05:44.080> names<00:05:44.350> that 00:05:44.670 --> 00:05:44.680 align:start position:0% little bit so if you have ENS names that 00:05:44.680 --> 00:05:46.140 align:start position:0% little bit so if you have ENS names that you<00:05:44.770> registered<00:05:45.250> before<00:05:45.610> may<00:05:45.790> the<00:05:45.940> fourth 00:05:46.140 --> 00:05:46.150 align:start position:0% you registered before may the fourth 00:05:46.150 --> 00:05:47.700 align:start position:0% you registered before may the fourth twenty<00:05:46.540> nineteen<00:05:46.900> there<00:05:47.110> is<00:05:47.260> free<00:05:47.530> money 00:05:47.700 --> 00:05:47.710 align:start position:0% twenty nineteen there is free money 00:05:47.710 --> 00:05:49.440 align:start position:0% twenty nineteen there is free money sitting<00:05:48.340> there<00:05:48.490> waiting<00:05:48.730> for<00:05:48.910> you<00:05:49.120> to<00:05:49.180> claim 00:05:49.440 --> 00:05:49.450 align:start position:0% sitting there waiting for you to claim 00:05:49.450 --> 00:05:52.410 align:start position:0% sitting there waiting for you to claim it<00:05:49.600> back<00:05:49.980> release<00:05:50.980> your<00:05:51.190> name<00:05:51.400> or<00:05:51.670> my<00:05:51.970> gracious 00:05:52.410 --> 00:05:52.420 align:start position:0% it back release your name or my gracious 00:05:52.420 --> 00:05:54.180 align:start position:0% it back release your name or my gracious which<00:05:52.630> is<00:05:52.780> the<00:05:52.870> better<00:05:53.050> option<00:05:53.170> to<00:05:53.950> the<00:05:54.070> new 00:05:54.180 --> 00:05:54.190 align:start position:0% which is the better option to the new 00:05:54.190 --> 00:05:55.530 align:start position:0% which is the better option to the new registrar<00:05:54.730> you'll<00:05:55.150> get<00:05:55.300> your<00:05:55.420> registration 00:05:55.530 --> 00:05:55.540 align:start position:0% registrar you'll get your registration 00:05:55.540 --> 00:05:57.210 align:start position:0% registrar you'll get your registration extended<00:05:56.470> and<00:05:56.620> you'll<00:05:56.710> get<00:05:56.800> all<00:05:56.860> of<00:05:57.040> your 00:05:57.210 --> 00:05:57.220 align:start position:0% extended and you'll get all of your 00:05:57.220 --> 00:05:59.790 align:start position:0% extended and you'll get all of your deposit<00:05:57.580> back<00:05:57.760> and<00:05:58.030> we<00:05:58.930> can<00:05:59.110> stop<00:05:59.350> sitting<00:05:59.680> on 00:05:59.790 --> 00:05:59.800 align:start position:0% deposit back and we can stop sitting on 00:05:59.800 --> 00:06:03.480 align:start position:0% deposit back and we can stop sitting on all<00:05:59.950> of<00:06:00.100> the<00:06:00.220> sefer<00:06:00.610> that's<00:06:00.880> doing<00:06:01.240> nothing<00:06:02.490> so 00:06:03.480 --> 00:06:03.490 align:start position:0% all of the sefer that's doing nothing so 00:06:03.490 --> 00:06:06.150 align:start position:0% all of the sefer that's doing nothing so next<00:06:03.640> up<00:06:03.880> the<00:06:04.060> shortname<00:06:04.420> options<00:06:04.950> we<00:06:05.950> have 00:06:06.150 --> 00:06:06.160 align:start position:0% next up the shortname options we have 00:06:06.160 --> 00:06:08.850 align:start position:0% next up the shortname options we have been<00:06:06.430> moving<00:06:07.120> on<00:06:07.450> with<00:06:07.750> making<00:06:08.050> shorter<00:06:08.650> names 00:06:08.850 --> 00:06:08.860 align:start position:0% been moving on with making shorter names 00:06:08.860 --> 00:06:10.770 align:start position:0% been moving on with making shorter names three<00:06:09.220> to<00:06:09.340> six<00:06:09.550> characters<00:06:10.030> available<00:06:10.540> via 00:06:10.770 --> 00:06:10.780 align:start position:0% three to six characters available via 00:06:10.780 --> 00:06:13.650 align:start position:0% three to six characters available via open<00:06:11.230> sea<00:06:11.440> and<00:06:12.280> some<00:06:12.790> of<00:06:12.910> you<00:06:13.000> probably<00:06:13.030> most 00:06:13.650 --> 00:06:13.660 align:start position:0% open sea and some of you probably most 00:06:13.660 --> 00:06:14.970 align:start position:0% open sea and some of you probably most of<00:06:13.780> you<00:06:13.930> will<00:06:14.140> be<00:06:14.230> aware<00:06:14.470> that<00:06:14.530> we<00:06:14.800> had<00:06:14.950> a 00:06:14.970 --> 00:06:14.980 align:start position:0% of you will be aware that we had a 00:06:14.980 --> 00:06:17.330 align:start position:0% of you will be aware that we had a slight<00:06:15.340> pickup<00:06:15.730> a<00:06:15.910> week<00:06:16.660> or<00:06:16.810> two<00:06:16.930> ago 00:06:17.330 --> 00:06:17.340 align:start position:0% slight pickup a week or two ago 00:06:17.340 --> 00:06:20.100 align:start position:0% slight pickup a week or two ago where<00:06:18.340> somebody<00:06:18.850> managed<00:06:19.390> to<00:06:19.600> obtain<00:06:19.900> a 00:06:20.100 --> 00:06:20.110 align:start position:0% where somebody managed to obtain a 00:06:20.110 --> 00:06:21.930 align:start position:0% where somebody managed to obtain a number<00:06:20.410> of<00:06:20.620> high-value<00:06:20.800> names<00:06:21.340> without 00:06:21.930 --> 00:06:21.940 align:start position:0% number of high-value names without 00:06:21.940 --> 00:06:24.120 align:start position:0% number of high-value names without paying<00:06:22.300> full<00:06:22.450> price<00:06:22.510> for<00:06:22.930> them<00:06:23.020> so<00:06:23.890> I'm<00:06:23.980> going 00:06:24.120 --> 00:06:24.130 align:start position:0% paying full price for them so I'm going 00:06:24.130 --> 00:06:25.710 align:start position:0% paying full price for them so I'm going to<00:06:24.160> go<00:06:24.250> into<00:06:24.400> a<00:06:24.460> bit<00:06:24.580> of<00:06:24.640> detail<00:06:24.820> on<00:06:25.240> just<00:06:25.330> how 00:06:25.710 --> 00:06:25.720 align:start position:0% to go into a bit of detail on just how 00:06:25.720 --> 00:06:27.690 align:start position:0% to go into a bit of detail on just how that<00:06:25.780> happened<00:06:26.230> and<00:06:26.500> what<00:06:27.340> you're<00:06:27.460> seeing 00:06:27.690 --> 00:06:27.700 align:start position:0% that happened and what you're seeing 00:06:27.700 --> 00:06:30.000 align:start position:0% that happened and what you're seeing here<00:06:27.820> on<00:06:28.120> the<00:06:28.240> screen<00:06:28.270> is<00:06:28.780> an<00:06:28.930> example<00:06:29.260> of<00:06:29.650> an 00:06:30.000 --> 00:06:30.010 align:start position:0% here on the screen is an example of an 00:06:30.010 --> 00:06:33.600 align:start position:0% here on the screen is an example of an open<00:06:30.430> sea<00:06:30.700> order<00:06:31.690> message<00:06:32.020> so<00:06:32.830> open<00:06:33.130> sea<00:06:33.340> works 00:06:33.600 --> 00:06:33.610 align:start position:0% open sea order message so open sea works 00:06:33.610 --> 00:06:35.760 align:start position:0% open sea order message so open sea works by<00:06:33.880> people<00:06:34.390> placing<00:06:34.840> bids<00:06:35.020> by<00:06:35.290> signing<00:06:35.710> a 00:06:35.760 --> 00:06:35.770 align:start position:0% by people placing bids by signing a 00:06:35.770 --> 00:06:37.320 align:start position:0% by people placing bids by signing a message<00:06:36.070> offline<00:06:36.460> and<00:06:36.730> sending<00:06:37.060> it<00:06:37.150> to<00:06:37.240> the 00:06:37.320 --> 00:06:37.330 align:start position:0% message offline and sending it to the 00:06:37.330 --> 00:06:39.990 align:start position:0% message offline and sending it to the open<00:06:37.600> sea<00:06:37.750> API<00:06:38.050> and<00:06:38.470> that<00:06:38.979> message<00:06:39.340> contains<00:06:39.790> a 00:06:39.990 --> 00:06:40.000 align:start position:0% open sea API and that message contains a 00:06:40.000 --> 00:06:42.020 align:start position:0% open sea API and that message contains a number<00:06:40.120> of<00:06:40.270> important<00:06:40.690> fields<00:06:41.050> such<00:06:41.229> as 00:06:42.020 --> 00:06:42.030 align:start position:0% number of important fields such as 00:06:42.030 --> 00:06:44.600 align:start position:0% number of important fields such as which<00:06:42.300> exchange<00:06:42.900> contract<00:06:43.380> to<00:06:43.500> use<00:06:43.710> who<00:06:44.460> the 00:06:44.600 --> 00:06:44.610 align:start position:0% which exchange contract to use who the 00:06:44.610 --> 00:06:46.580 align:start position:0% which exchange contract to use who the maker<00:06:44.820> is<00:06:45.090> the<00:06:45.120> person<00:06:45.600> making<00:06:45.810> the<00:06:45.930> bid<00:06:46.170> who 00:06:46.580 --> 00:06:46.590 align:start position:0% maker is the person making the bid who 00:06:46.590 --> 00:06:48.920 align:start position:0% maker is the person making the bid who the<00:06:46.740> taker<00:06:46.980> is<00:06:47.220> that's<00:06:47.430> our<00:06:47.610> contract<00:06:48.060> how 00:06:48.920 --> 00:06:48.930 align:start position:0% the taker is that's our contract how 00:06:48.930 --> 00:06:50.360 align:start position:0% the taker is that's our contract how much<00:06:49.080> they're<00:06:49.260> willing<00:06:49.350> to<00:06:49.500> pay<00:06:49.590> and<00:06:49.950> so<00:06:50.130> forth 00:06:50.360 --> 00:06:50.370 align:start position:0% much they're willing to pay and so forth 00:06:50.370 --> 00:06:53.360 align:start position:0% much they're willing to pay and so forth it<00:06:51.120> also<00:06:51.270> contains<00:06:51.810> the<00:06:51.990> target<00:06:52.830> address<00:06:52.920> the 00:06:53.360 --> 00:06:53.370 align:start position:0% it also contains the target address the 00:06:53.370 --> 00:06:54.680 align:start position:0% it also contains the target address the address<00:06:53.640> that<00:06:53.760> should<00:06:53.970> be<00:06:54.090> called<00:06:54.360> if<00:06:54.570> the 00:06:54.680 --> 00:06:54.690 align:start position:0% address that should be called if the 00:06:54.690 --> 00:06:56.980 align:start position:0% address that should be called if the bids<00:06:54.870> accepted<00:06:55.350> and<00:06:55.500> the<00:06:56.070> call<00:06:56.250> data<00:06:56.460> for<00:06:56.790> it 00:06:56.980 --> 00:06:56.990 align:start position:0% bids accepted and the call data for it 00:06:56.990 --> 00:07:02.260 align:start position:0% bids accepted and the call data for it and<00:06:58.220> we<00:06:59.220> believed<00:06:59.580> that<00:06:59.940> open<00:07:00.510> seas<00:07:00.720> API<00:07:01.110> was 00:07:02.260 --> 00:07:02.270 align:start position:0% and we believed that open seas API was 00:07:02.270 --> 00:07:04.760 align:start position:0% and we believed that open seas API was validating<00:07:03.270> all<00:07:03.420> of<00:07:03.540> this<00:07:03.630> data<00:07:03.840> we<00:07:04.410> also<00:07:04.560> had 00:07:04.760 --> 00:07:04.770 align:start position:0% validating all of this data we also had 00:07:04.770 --> 00:07:06.410 align:start position:0% validating all of this data we also had a<00:07:04.800> series<00:07:05.190> of<00:07:05.220> additional<00:07:05.490> checks<00:07:05.970> of<00:07:06.150> our<00:07:06.270> own 00:07:06.410 --> 00:07:06.420 align:start position:0% a series of additional checks of our own 00:07:06.420 --> 00:07:07.900 align:start position:0% a series of additional checks of our own against<00:07:06.930> many<00:07:07.080> of<00:07:07.170> these<00:07:07.350> fields 00:07:07.900 --> 00:07:07.910 align:start position:0% against many of these fields 00:07:07.910 --> 00:07:10.220 align:start position:0% against many of these fields unfortunately<00:07:08.910> we<00:07:09.180> were<00:07:09.330> mistaken<00:07:09.510> and<00:07:10.080> they 00:07:10.220 --> 00:07:10.230 align:start position:0% unfortunately we were mistaken and they 00:07:10.230 --> 00:07:12.530 align:start position:0% unfortunately we were mistaken and they were<00:07:10.290> mistaken<00:07:10.650> and<00:07:11.220> neither<00:07:12.060> of<00:07:12.090> us<00:07:12.300> was 00:07:12.530 --> 00:07:12.540 align:start position:0% were mistaken and neither of us was 00:07:12.540 --> 00:07:14.960 align:start position:0% were mistaken and neither of us was verifying<00:07:12.990> the<00:07:13.200> target<00:07:13.560> data<00:07:13.790> which<00:07:14.790> is 00:07:14.960 --> 00:07:14.970 align:start position:0% verifying the target data which is 00:07:14.970 --> 00:07:16.490 align:start position:0% verifying the target data which is embarrassing 00:07:16.490 --> 00:07:16.500 align:start position:0% embarrassing 00:07:16.500 --> 00:07:18.650 align:start position:0% embarrassing the<00:07:17.040> result<00:07:17.400> was<00:07:17.580> that<00:07:17.610> somebody<00:07:18.210> was<00:07:18.330> able<00:07:18.480> to 00:07:18.650 --> 00:07:18.660 align:start position:0% the result was that somebody was able to 00:07:18.660 --> 00:07:20.930 align:start position:0% the result was that somebody was able to place<00:07:19.080> birds<00:07:19.410> that<00:07:19.620> were<00:07:19.770> ostensibly<00:07:20.100> against 00:07:20.930 --> 00:07:20.940 align:start position:0% place birds that were ostensibly against 00:07:20.940 --> 00:07:24.080 align:start position:0% place birds that were ostensibly against one<00:07:21.600> low<00:07:21.900> value<00:07:22.290> name<00:07:22.530> that<00:07:22.950> ended<00:07:23.610> quite<00:07:23.820> soon 00:07:24.080 --> 00:07:24.090 align:start position:0% one low value name that ended quite soon 00:07:24.090 --> 00:07:26.300 align:start position:0% one low value name that ended quite soon but<00:07:24.660> in<00:07:24.810> actual<00:07:25.080> fact<00:07:25.169> would<00:07:25.740> finalize 00:07:26.300 --> 00:07:26.310 align:start position:0% but in actual fact would finalize 00:07:26.310 --> 00:07:29.270 align:start position:0% but in actual fact would finalize another<00:07:26.669> name<00:07:26.880> so<00:07:27.300> by<00:07:27.570> bidding<00:07:27.780> on<00:07:28.280> fubar 00:07:29.270 --> 00:07:29.280 align:start position:0% another name so by bidding on fubar 00:07:29.280 --> 00:07:31.909 align:start position:0% another name so by bidding on fubar death<00:07:29.880> they<00:07:30.330> were<00:07:30.390> able<00:07:30.630> to<00:07:30.930> finalize<00:07:31.380> defy 00:07:31.909 --> 00:07:31.919 align:start position:0% death they were able to finalize defy 00:07:31.919 --> 00:07:34.190 align:start position:0% death they were able to finalize defy Dottie's<00:07:32.419> before<00:07:33.419> that<00:07:33.570> option<00:07:33.930> should<00:07:34.080> have 00:07:34.190 --> 00:07:34.200 align:start position:0% Dottie's before that option should have 00:07:34.200 --> 00:07:37.730 align:start position:0% Dottie's before that option should have ended<00:07:34.730> so<00:07:35.730> that<00:07:35.970> resulted<00:07:36.870> in<00:07:36.990> them<00:07:37.169> obtaining 00:07:37.730 --> 00:07:37.740 align:start position:0% ended so that resulted in them obtaining 00:07:37.740 --> 00:07:42.320 align:start position:0% ended so that resulted in them obtaining 17<00:07:38.190> names<00:07:38.460> and<00:07:40.100> for<00:07:41.100> very<00:07:41.700> small<00:07:41.790> birds<00:07:42.150> in 00:07:42.320 --> 00:07:42.330 align:start position:0% 17 names and for very small birds in 00:07:42.330 --> 00:07:45.680 align:start position:0% 17 names and for very small birds in each<00:07:42.419> case<00:07:42.690> so<00:07:43.620> what<00:07:44.220> we<00:07:44.340> did<00:07:44.490> we<00:07:45.090> obviously<00:07:45.270> we 00:07:45.680 --> 00:07:45.690 align:start position:0% each case so what we did we obviously we 00:07:45.690 --> 00:07:48.230 align:start position:0% each case so what we did we obviously we stopped<00:07:45.900> the<00:07:45.990> contract<00:07:46.440> we<00:07:46.770> made<00:07:47.640> an<00:07:47.760> offer<00:07:47.880> to 00:07:48.230 --> 00:07:48.240 align:start position:0% stopped the contract we made an offer to 00:07:48.240 --> 00:07:51.350 align:start position:0% stopped the contract we made an offer to them<00:07:48.419> we<00:07:48.750> said<00:07:49.020> if<00:07:49.979> you<00:07:50.400> want<00:07:50.790> to<00:07:50.850> return<00:07:51.150> those 00:07:51.350 --> 00:07:51.360 align:start position:0% them we said if you want to return those 00:07:51.360 --> 00:07:53.210 align:start position:0% them we said if you want to return those names<00:07:51.630> to<00:07:51.840> us<00:07:51.960> we<00:07:52.229> will<00:07:52.410> re<00:07:52.590> option<00:07:52.979> them<00:07:53.100> the 00:07:53.210 --> 00:07:53.220 align:start position:0% names to us we will re option them the 00:07:53.220 --> 00:07:54.380 align:start position:0% names to us we will re option them the way<00:07:53.310> they<00:07:53.460> were<00:07:53.550> supposed<00:07:53.820> to<00:07:53.880> be<00:07:54.000> optioned 00:07:54.380 --> 00:07:54.390 align:start position:0% way they were supposed to be optioned 00:07:54.390 --> 00:07:56.060 align:start position:0% way they were supposed to be optioned and<00:07:55.080> we'll<00:07:55.229> provide<00:07:55.470> you<00:07:55.530> with<00:07:55.620> a<00:07:55.740> bug<00:07:55.890> bounty 00:07:56.060 --> 00:07:56.070 align:start position:0% and we'll provide you with a bug bounty 00:07:56.070 --> 00:07:59.480 align:start position:0% and we'll provide you with a bug bounty of<00:07:56.520> 25%<00:07:57.300> the<00:07:57.630> final<00:07:57.960> sale<00:07:58.169> price<00:07:58.200> and<00:07:58.800> I'm 00:07:59.480 --> 00:07:59.490 align:start position:0% of 25% the final sale price and I'm 00:07:59.490 --> 00:08:00.770 align:start position:0% of 25% the final sale price and I'm pleased<00:07:59.760> to<00:07:59.850> say<00:08:00.000> that<00:08:00.030> they<00:08:00.270> accepted<00:08:00.660> the 00:08:00.770 --> 00:08:00.780 align:start position:0% pleased to say that they accepted the 00:08:00.780 --> 00:08:02.630 align:start position:0% pleased to say that they accepted the offer<00:08:00.810> they<00:08:01.229> returned<00:08:01.530> the<00:08:01.650> 17<00:08:02.010> names<00:08:02.280> to<00:08:02.490> us 00:08:02.630 --> 00:08:02.640 align:start position:0% offer they returned the 17 names to us 00:08:02.640 --> 00:08:09.500 align:start position:0% offer they returned the 17 names to us and<00:08:02.880> those<00:08:02.970> are<00:08:03.180> now<00:08:03.270> back<00:08:03.570> on<00:08:03.690> auction<00:08:07.760> so<00:08:08.760> if 00:08:09.500 --> 00:08:09.510 align:start position:0% and those are now back on auction so if 00:08:09.510 --> 00:08:12.530 align:start position:0% and those are now back on auction so if you<00:08:09.780> are<00:08:09.930> here<00:08:10.140> thank<00:08:10.650> you<00:08:10.770> very<00:08:10.919> much<00:08:11.300> if<00:08:12.300> you 00:08:12.530 --> 00:08:12.540 align:start position:0% you are here thank you very much if you 00:08:12.540 --> 00:08:14.240 align:start position:0% you are here thank you very much if you want<00:08:12.720> a<00:08:12.810> security<00:08:13.140> consulting<00:08:13.770> job<00:08:13.950> please 00:08:14.240 --> 00:08:14.250 align:start position:0% want a security consulting job please 00:08:14.250 --> 00:08:16.670 align:start position:0% want a security consulting job please talk<00:08:14.550> to<00:08:14.729> us 00:08:16.670 --> 00:08:16.680 align:start position:0% talk to us 00:08:16.680 --> 00:08:18.500 align:start position:0% talk to us there<00:08:17.160> was<00:08:17.250> a<00:08:17.280> second<00:08:17.700> smaller<00:08:18.000> issue<00:08:18.240> with 00:08:18.500 --> 00:08:18.510 align:start position:0% there was a second smaller issue with 00:08:18.510 --> 00:08:20.180 align:start position:0% there was a second smaller issue with the<00:08:18.630> options<00:08:19.050> that<00:08:19.200> we've<00:08:19.440> also<00:08:19.740> resolved 00:08:20.180 --> 00:08:20.190 align:start position:0% the options that we've also resolved 00:08:20.190 --> 00:08:22.010 align:start position:0% the options that we've also resolved while<00:08:20.340> we're<00:08:20.490> paused<00:08:20.760> and<00:08:21.180> it<00:08:21.330> was<00:08:21.479> that<00:08:21.750> some 00:08:22.010 --> 00:08:22.020 align:start position:0% while we're paused and it was that some 00:08:22.020 --> 00:08:23.810 align:start position:0% while we're paused and it was that some that<00:08:22.229> is<00:08:22.410> were<00:08:23.160> given<00:08:23.400> the<00:08:23.490> wrong<00:08:23.640> information 00:08:23.810 --> 00:08:23.820 align:start position:0% that is were given the wrong information 00:08:23.820 --> 00:08:26.600 align:start position:0% that is were given the wrong information in<00:08:24.540> terms<00:08:24.750> of<00:08:25.050> what<00:08:25.380> fields<00:08:25.979> to<00:08:26.130> fill<00:08:26.310> out<00:08:26.460> in 00:08:26.600 --> 00:08:26.610 align:start position:0% in terms of what fields to fill out in 00:08:26.610 --> 00:08:28.730 align:start position:0% in terms of what fields to fill out in the<00:08:26.669> bids<00:08:26.880> so<00:08:27.210> if<00:08:27.300> you<00:08:27.419> were<00:08:27.510> using<00:08:27.720> the<00:08:28.110> user 00:08:28.730 --> 00:08:28.740 align:start position:0% the bids so if you were using the user 00:08:28.740 --> 00:08:30.440 align:start position:0% the bids so if you were using the user interface<00:08:29.190> by<00:08:29.430> your<00:08:29.610> web<00:08:29.760> browser<00:08:30.000> this<00:08:30.270> was 00:08:30.440 --> 00:08:30.450 align:start position:0% interface by your web browser this was 00:08:30.450 --> 00:08:31.310 align:start position:0% interface by your web browser this was absolutely<00:08:30.780> fine 00:08:31.310 --> 00:08:31.320 align:start position:0% absolutely fine 00:08:31.320 --> 00:08:32.870 align:start position:0% absolutely fine but<00:08:31.650> if<00:08:31.770> you<00:08:31.890> were<00:08:32.010> using<00:08:32.219> the<00:08:32.580> SDK 00:08:32.870 --> 00:08:32.880 align:start position:0% but if you were using the SDK 00:08:32.880 --> 00:08:34.790 align:start position:0% but if you were using the SDK integration<00:08:33.780> if<00:08:33.930> you<00:08:34.080> are<00:08:34.260> sending<00:08:34.469> bids 00:08:34.790 --> 00:08:34.800 align:start position:0% integration if you are sending bids 00:08:34.800 --> 00:08:36.560 align:start position:0% integration if you are sending bids yourself<00:08:35.219> automated<00:08:35.880> with<00:08:36.150> an<00:08:36.300> automated 00:08:36.560 --> 00:08:36.570 align:start position:0% yourself automated with an automated 00:08:36.570 --> 00:08:38.719 align:start position:0% yourself automated with an automated solution<00:08:37.169> you<00:08:37.890> may<00:08:38.070> have<00:08:38.190> been<00:08:38.339> submitting 00:08:38.719 --> 00:08:38.729 align:start position:0% solution you may have been submitting 00:08:38.729 --> 00:08:40.550 align:start position:0% solution you may have been submitting bids<00:08:38.849> with<00:08:39.060> the<00:08:39.180> wrong<00:08:39.360> target<00:08:39.599> field<00:08:40.020> we 00:08:40.550 --> 00:08:40.560 align:start position:0% bids with the wrong target field we 00:08:40.560 --> 00:08:42.770 align:start position:0% bids with the wrong target field we identified<00:08:41.159> the<00:08:41.370> roughly<00:08:41.729> 30<00:08:42.000> or<00:08:42.210> so<00:08:42.390> options 00:08:42.770 --> 00:08:42.780 align:start position:0% identified the roughly 30 or so options 00:08:42.780 --> 00:08:44.300 align:start position:0% identified the roughly 30 or so options that<00:08:42.960> are<00:08:43.080> affected<00:08:43.409> by<00:08:43.440> this<00:08:43.620> where<00:08:44.010> the<00:08:44.099> top 00:08:44.300 --> 00:08:44.310 align:start position:0% that are affected by this where the top 00:08:44.310 --> 00:08:46.040 align:start position:0% that are affected by this where the top bid<00:08:44.520> was<00:08:44.760> a<00:08:44.790> bid<00:08:45.030> that<00:08:45.270> didn't<00:08:45.660> have<00:08:45.780> the<00:08:45.900> right 00:08:46.040 --> 00:08:46.050 align:start position:0% bid was a bid that didn't have the right 00:08:46.050 --> 00:08:48.140 align:start position:0% bid was a bid that didn't have the right target<00:08:46.410> field<00:08:46.650> and<00:08:46.890> those<00:08:47.580> options<00:08:47.820> have<00:08:48.120> been 00:08:48.140 --> 00:08:48.150 align:start position:0% target field and those options have been 00:08:48.150 --> 00:08:50.150 align:start position:0% target field and those options have been extended<00:08:48.720> a<00:08:48.750> little<00:08:48.960> further<00:08:49.200> to<00:08:49.860> give<00:08:50.010> those 00:08:50.150 --> 00:08:50.160 align:start position:0% extended a little further to give those 00:08:50.160 --> 00:08:51.949 align:start position:0% extended a little further to give those users<00:08:50.580> an<00:08:50.670> opportunity<00:08:51.209> to<00:08:51.390> play<00:08:51.540> spell<00:08:51.839> of 00:08:51.949 --> 00:08:51.959 align:start position:0% users an opportunity to play spell of 00:08:51.959 --> 00:08:53.420 align:start position:0% users an opportunity to play spell of bids<00:08:52.170> replace<00:08:52.620> them<00:08:52.860> and<00:08:53.040> if<00:08:53.220> you<00:08:53.339> were 00:08:53.420 --> 00:08:53.430 align:start position:0% bids replace them and if you were 00:08:53.430 --> 00:08:54.770 align:start position:0% bids replace them and if you were affected<00:08:53.790> by<00:08:53.910> this<00:08:53.970> you<00:08:54.240> will<00:08:54.270> have<00:08:54.450> received 00:08:54.770 --> 00:08:54.780 align:start position:0% affected by this you will have received 00:08:54.780 --> 00:08:55.639 align:start position:0% affected by this you will have received an<00:08:54.930> email<00:08:55.020> because 00:08:55.639 --> 00:08:55.649 align:start position:0% an email because 00:08:55.649 --> 00:08:58.090 align:start position:0% an email because a full<00:08:55.889> description<00:08:56.430> of<00:08:56.550> how<00:08:57.209> to<00:08:57.240> do<00:08:57.480> that<00:08:57.629> and 00:08:58.090 --> 00:08:58.100 align:start position:0% a full description of how to do that and 00:08:58.100 --> 00:09:00.920 align:start position:0% a full description of how to do that and so<00:08:59.100> the<00:08:59.189> short<00:08:59.339> name<00:08:59.550> options<00:08:59.910> in<00:08:59.999> general<00:09:00.360> we 00:09:00.920 --> 00:09:00.930 align:start position:0% so the short name options in general we 00:09:00.930 --> 00:09:02.900 align:start position:0% so the short name options in general we auction<00:09:01.319> off<00:09:01.410> all<00:09:01.709> three<00:09:02.040> six<00:09:02.459> character 00:09:02.900 --> 00:09:02.910 align:start position:0% auction off all three six character 00:09:02.910 --> 00:09:05.989 align:start position:0% auction off all three six character length<00:09:03.420> domains<00:09:04.040> in<00:09:05.040> partnership<00:09:05.610> with<00:09:05.699> open 00:09:05.989 --> 00:09:05.999 align:start position:0% length domains in partnership with open 00:09:05.999 --> 00:09:09.230 align:start position:0% length domains in partnership with open C<00:09:06.209> we<00:09:07.079> sort<00:09:08.009> of<00:09:08.100> looked<00:09:08.369> at<00:09:08.550> all<00:09:08.730> the<00:09:08.910> effort<00:09:09.149> we 00:09:09.230 --> 00:09:09.240 align:start position:0% C we sort of looked at all the effort we 00:09:09.240 --> 00:09:12.019 align:start position:0% C we sort of looked at all the effort we put<00:09:09.269> in<00:09:09.540> for<00:09:09.839> the<00:09:09.899> original<00:09:10.369> option<00:09:11.369> contract 00:09:12.019 --> 00:09:12.029 align:start position:0% put in for the original option contract 00:09:12.029 --> 00:09:14.059 align:start position:0% put in for the original option contract and<00:09:12.360> we<00:09:13.019> went<00:09:13.199> well<00:09:13.410> we're<00:09:13.529> not<00:09:13.649> an<00:09:13.740> option 00:09:14.059 --> 00:09:14.069 align:start position:0% and we went well we're not an option 00:09:14.069 --> 00:09:16.249 align:start position:0% and we went well we're not an option business<00:09:14.459> where<00:09:14.759> we're<00:09:15.360> trying<00:09:15.509> to<00:09:15.689> do<00:09:15.869> naming 00:09:16.249 --> 00:09:16.259 align:start position:0% business where we're trying to do naming 00:09:16.259 --> 00:09:18.139 align:start position:0% business where we're trying to do naming we're<00:09:16.410> trying<00:09:16.649> to<00:09:16.769> build<00:09:16.920> a<00:09:17.069> naming<00:09:17.249> system<00:09:17.730> we 00:09:18.139 --> 00:09:18.149 align:start position:0% we're trying to build a naming system we 00:09:18.149 --> 00:09:19.939 align:start position:0% we're trying to build a naming system we don't<00:09:18.240> want<00:09:18.449> to<00:09:18.509> put<00:09:18.720> hundreds<00:09:19.439> of<00:09:19.529> our<00:09:19.769> hours 00:09:19.939 --> 00:09:19.949 align:start position:0% don't want to put hundreds of our hours 00:09:19.949 --> 00:09:21.439 align:start position:0% don't want to put hundreds of our hours into<00:09:20.429> building<00:09:20.699> a<00:09:20.759> system<00:09:20.939> that<00:09:21.209> somebody 00:09:21.439 --> 00:09:21.449 align:start position:0% into building a system that somebody 00:09:21.449 --> 00:09:23.119 align:start position:0% into building a system that somebody else<00:09:21.749> has<00:09:21.929> already<00:09:22.050> built<00:09:22.350> and<00:09:22.709> or<00:09:22.889> they 00:09:23.119 --> 00:09:23.129 align:start position:0% else has already built and or they 00:09:23.129 --> 00:09:24.559 align:start position:0% else has already built and or they already<00:09:23.309> know<00:09:23.490> how<00:09:23.579> to<00:09:23.670> operate<00:09:23.759> it<00:09:23.999> so<00:09:24.449> we 00:09:24.559 --> 00:09:24.569 align:start position:0% already know how to operate it so we 00:09:24.569 --> 00:09:26.449 align:start position:0% already know how to operate it so we partnered<00:09:24.959> with<00:09:24.990> them<00:09:25.290> in<00:09:25.769> order<00:09:26.040> to<00:09:26.129> do<00:09:26.309> the 00:09:26.449 --> 00:09:26.459 align:start position:0% partnered with them in order to do the 00:09:26.459 --> 00:09:29.210 align:start position:0% partnered with them in order to do the name<00:09:26.610> allocation<00:09:27.209> so<00:09:28.170> most<00:09:28.410> five<00:09:28.889> to<00:09:29.040> six 00:09:29.210 --> 00:09:29.220 align:start position:0% name allocation so most five to six 00:09:29.220 --> 00:09:31.129 align:start position:0% name allocation so most five to six character<00:09:29.639> names<00:09:29.819> all<00:09:30.329> of<00:09:30.540> these<00:09:30.689> names<00:09:30.929> are 00:09:31.129 --> 00:09:31.139 align:start position:0% character names all of these names are 00:09:31.139 --> 00:09:33.379 align:start position:0% character names all of these names are on<00:09:31.199> option<00:09:31.559> now<00:09:31.709> the<00:09:32.369> five<00:09:32.670> to<00:09:32.790> six<00:09:32.999> character 00:09:33.379 --> 00:09:33.389 align:start position:0% on option now the five to six character 00:09:33.389 --> 00:09:35.629 align:start position:0% on option now the five to six character ones<00:09:33.569> are<00:09:33.809> ending<00:09:34.079> between<00:09:34.350> the<00:09:34.439> 15th<00:09:34.800> or<00:09:34.980> 22nd 00:09:35.629 --> 00:09:35.639 align:start position:0% ones are ending between the 15th or 22nd 00:09:35.639 --> 00:09:37.939 align:start position:0% ones are ending between the 15th or 22nd of<00:09:35.670> October<00:09:36.119> for<00:09:36.899> characters<00:09:37.379> a<00:09:37.410> week<00:09:37.709> later 00:09:37.939 --> 00:09:37.949 align:start position:0% of October for characters a week later 00:09:37.949 --> 00:09:40.999 align:start position:0% of October for characters a week later 22nd<00:09:38.759> to<00:09:38.819> 29th<00:09:39.240> and<00:09:39.540> three<00:09:39.959> carrots<00:09:40.290> character 00:09:40.999 --> 00:09:41.009 align:start position:0% 22nd to 29th and three carrots character 00:09:41.009 --> 00:09:43.100 align:start position:0% 22nd to 29th and three carrots character names<00:09:41.220> the<00:09:41.519> shortest<00:09:41.879> ones<00:09:42.059> ending<00:09:42.990> between 00:09:43.100 --> 00:09:43.110 align:start position:0% names the shortest ones ending between 00:09:43.110 --> 00:09:45.590 align:start position:0% names the shortest ones ending between the<00:09:43.350> 29th<00:09:43.769> from<00:09:43.920> the<00:09:44.040> 5th<00:09:44.220> of<00:09:44.309> November<00:09:44.759> if 00:09:45.590 --> 00:09:45.600 align:start position:0% the 29th from the 5th of November if 00:09:45.600 --> 00:09:47.449 align:start position:0% the 29th from the 5th of November if your<00:09:45.839> interest<00:09:46.290> is<00:09:46.439> in<00:09:46.559> getting<00:09:46.889> a<00:09:46.980> name<00:09:47.129> that 00:09:47.449 --> 00:09:47.459 align:start position:0% your interest is in getting a name that 00:09:47.459 --> 00:09:49.699 align:start position:0% your interest is in getting a name that represents<00:09:47.579> you<00:09:48.119> some<00:09:49.110> of<00:09:49.230> these<00:09:49.319> are<00:09:49.529> quite 00:09:49.699 --> 00:09:49.709 align:start position:0% represents you some of these are quite 00:09:49.709 --> 00:09:51.169 align:start position:0% represents you some of these are quite contentious<00:09:50.249> but<00:09:50.490> many<00:09:50.699> of<00:09:50.850> them<00:09:50.910> are<00:09:51.059> going 00:09:51.169 --> 00:09:51.179 align:start position:0% contentious but many of them are going 00:09:51.179 --> 00:09:53.929 align:start position:0% contentious but many of them are going for<00:09:51.569> the<00:09:51.629> minimum<00:09:51.959> of<00:09:52.079> 5<00:09:52.559> packs<00:09:52.829> a<00:09:52.949> year<00:09:53.189> you 00:09:53.929 --> 00:09:53.939 align:start position:0% for the minimum of 5 packs a year you 00:09:53.939 --> 00:09:55.549 align:start position:0% for the minimum of 5 packs a year you know<00:09:54.059> the<00:09:54.179> auction<00:09:54.449> process<00:09:54.839> exists<00:09:55.350> in<00:09:55.439> order 00:09:55.549 --> 00:09:55.559 align:start position:0% know the auction process exists in order 00:09:55.559 --> 00:09:57.759 align:start position:0% know the auction process exists in order to<00:09:55.800> make<00:09:55.949> sure<00:09:55.980> names<00:09:56.790> are<00:09:56.970> fairly<00:09:57.269> allocated 00:09:57.759 --> 00:09:57.769 align:start position:0% to make sure names are fairly allocated 00:09:57.769 --> 00:09:59.840 align:start position:0% to make sure names are fairly allocated but<00:09:58.769> that<00:09:58.920> doesn't<00:09:59.160> mean<00:09:59.279> that<00:09:59.309> necessarily 00:09:59.840 --> 00:09:59.850 align:start position:0% but that doesn't mean that necessarily 00:09:59.850 --> 00:10:01.850 align:start position:0% but that doesn't mean that necessarily your<00:10:00.209> first<00:10:00.509> name<00:10:00.749> or<00:10:00.779> your<00:10:00.929> last<00:10:01.230> name<00:10:01.470> is 00:10:01.850 --> 00:10:01.860 align:start position:0% your first name or your last name is 00:10:01.860 --> 00:10:03.169 align:start position:0% your first name or your last name is going<00:10:02.009> to<00:10:02.069> be<00:10:02.160> popular<00:10:02.579> amongst<00:10:02.879> a<00:10:02.939> lot<00:10:03.089> of 00:10:03.169 --> 00:10:03.179 align:start position:0% going to be popular amongst a lot of 00:10:03.179 --> 00:10:05.299 align:start position:0% going to be popular amongst a lot of other<00:10:03.300> people<00:10:03.629> so<00:10:03.959> if<00:10:04.379> you<00:10:04.589> want<00:10:04.769> to<00:10:04.800> get<00:10:04.980> it<00:10:05.100> go 00:10:05.299 --> 00:10:05.309 align:start position:0% other people so if you want to get it go 00:10:05.309 --> 00:10:07.369 align:start position:0% other people so if you want to get it go there<00:10:05.550> have<00:10:05.819> a<00:10:05.850> look<00:10:06.029> and<00:10:06.629> maybe<00:10:06.929> snag 00:10:07.369 --> 00:10:07.379 align:start position:0% there have a look and maybe snag 00:10:07.379 --> 00:10:10.819 align:start position:0% there have a look and maybe snag yourself<00:10:07.800> a<00:10:07.920> name<00:10:08.100> that<00:10:08.249> represents<00:10:08.399> you<00:10:09.829> so 00:10:10.819 --> 00:10:10.829 align:start position:0% yourself a name that represents you so 00:10:10.829 --> 00:10:12.499 align:start position:0% yourself a name that represents you so next<00:10:10.980> up<00:10:11.189> I<00:10:11.399> want<00:10:11.459> to<00:10:11.610> talk<00:10:11.730> about<00:10:11.850> the<00:10:12.089> DNS 00:10:12.499 --> 00:10:12.509 align:start position:0% next up I want to talk about the DNS 00:10:12.509 --> 00:10:15.619 align:start position:0% next up I want to talk about the DNS namespace<00:10:12.749> integration<00:10:13.649> so<00:10:14.279> ENS<00:10:15.209> is<00:10:15.389> more 00:10:15.619 --> 00:10:15.629 align:start position:0% namespace integration so ENS is more 00:10:15.629 --> 00:10:17.840 align:start position:0% namespace integration so ENS is more than<00:10:15.779> just<00:10:16.079> da<00:10:16.290> teef<00:10:16.499> da<00:10:17.279> teeth<00:10:17.459> is<00:10:17.730> the 00:10:17.840 --> 00:10:17.850 align:start position:0% than just da teef da teeth is the 00:10:17.850 --> 00:10:19.850 align:start position:0% than just da teef da teeth is the namespace<00:10:18.179> that<00:10:18.360> is<00:10:18.689> native<00:10:19.110> to<00:10:19.139> aetherium 00:10:19.850 --> 00:10:19.860 align:start position:0% namespace that is native to aetherium 00:10:19.860 --> 00:10:21.799 align:start position:0% namespace that is native to aetherium that<00:10:20.279> we<00:10:20.429> sort<00:10:20.699> of<00:10:20.759> completely<00:10:21.240> control<00:10:21.629> we 00:10:21.799 --> 00:10:21.809 align:start position:0% that we sort of completely control we 00:10:21.809 --> 00:10:23.210 align:start position:0% that we sort of completely control we can<00:10:21.959> enforce<00:10:22.290> strong<00:10:22.589> contractual 00:10:23.210 --> 00:10:23.220 align:start position:0% can enforce strong contractual 00:10:23.220 --> 00:10:25.040 align:start position:0% can enforce strong contractual guarantees<00:10:23.639> on<00:10:23.819> it<00:10:23.970> but<00:10:24.420> it's<00:10:24.569> not<00:10:24.720> all<00:10:24.839> there 00:10:25.040 --> 00:10:25.050 align:start position:0% guarantees on it but it's not all there 00:10:25.050 --> 00:10:25.879 align:start position:0% guarantees on it but it's not all there is 00:10:25.879 --> 00:10:25.889 align:start position:0% is 00:10:25.889 --> 00:10:28.009 align:start position:0% is we<00:10:26.189> believe<00:10:26.490> that<00:10:26.519> ENS<00:10:27.089> exists<00:10:27.569> as<00:10:27.660> part<00:10:27.899> of 00:10:28.009 --> 00:10:28.019 align:start position:0% we believe that ENS exists as part of 00:10:28.019 --> 00:10:30.019 align:start position:0% we believe that ENS exists as part of the<00:10:28.139> global<00:10:28.529> namespace<00:10:28.740> the<00:10:29.399> same<00:10:29.699> namespace 00:10:30.019 --> 00:10:30.029 align:start position:0% the global namespace the same namespace 00:10:30.029 --> 00:10:32.329 align:start position:0% the global namespace the same namespace that's<00:10:30.540> inhabited<00:10:30.899> by<00:10:31.019> common<00:10:31.620> expose<00:10:32.129> even 00:10:32.329 --> 00:10:32.339 align:start position:0% that's inhabited by common expose even 00:10:32.339 --> 00:10:34.850 align:start position:0% that's inhabited by common expose even TV<00:10:32.879> and<00:10:33.209> so<00:10:33.389> forth<00:10:33.689> and<00:10:33.870> so<00:10:33.929> we're<00:10:34.559> doing<00:10:34.740> abs 00:10:34.850 --> 00:10:34.860 align:start position:0% TV and so forth and so we're doing abs 00:10:34.860 --> 00:10:36.350 align:start position:0% TV and so forth and so we're doing abs to<00:10:35.100> integrate<00:10:35.459> with<00:10:35.610> that<00:10:35.790> and<00:10:36.089> there's<00:10:36.209> two 00:10:36.350 --> 00:10:36.360 align:start position:0% to integrate with that and there's two 00:10:36.360 --> 00:10:37.879 align:start position:0% to integrate with that and there's two ways<00:10:36.509> we're<00:10:36.720> doing<00:10:36.929> that<00:10:37.110> one<00:10:37.740> is<00:10:37.860> a 00:10:37.879 --> 00:10:37.889 align:start position:0% ways we're doing that one is a 00:10:37.889 --> 00:10:40.129 align:start position:0% ways we're doing that one is a permissionless<00:10:38.459> integration<00:10:39.179> via<00:10:39.509> DNA<00:10:39.779> stick 00:10:40.129 --> 00:10:40.139 align:start position:0% permissionless integration via DNA stick 00:10:40.139 --> 00:10:42.259 align:start position:0% permissionless integration via DNA stick and<00:10:40.350> the<00:10:40.740> second<00:10:41.040> is<00:10:41.160> bespoke<00:10:41.459> integrations 00:10:42.259 --> 00:10:42.269 align:start position:0% and the second is bespoke integrations 00:10:42.269 --> 00:10:43.939 align:start position:0% and the second is bespoke integrations with<00:10:42.540> top-level<00:10:42.959> domains<00:10:43.350> that<00:10:43.649> are<00:10:43.769> working 00:10:43.939 --> 00:10:43.949 align:start position:0% with top-level domains that are working 00:10:43.949 --> 00:10:47.119 align:start position:0% with top-level domains that are working with<00:10:44.220> us<00:10:44.299> so<00:10:45.299> first<00:10:45.629> of<00:10:45.779> all<00:10:45.839> how<00:10:46.319> does<00:10:46.589> the<00:10:46.799> dns 00:10:47.119 --> 00:10:47.129 align:start position:0% with us so first of all how does the dns 00:10:47.129 --> 00:10:49.220 align:start position:0% with us so first of all how does the dns tech<00:10:47.279> integration<00:10:47.459> work<00:10:47.970> it<00:10:48.480> permits<00:10:48.779> anyone 00:10:49.220 --> 00:10:49.230 align:start position:0% tech integration work it permits anyone 00:10:49.230 --> 00:10:52.280 align:start position:0% tech integration work it permits anyone who<00:10:49.439> has<00:10:49.620> a<00:10:49.649> dns<00:10:50.040> domain<00:10:50.069> like<00:10:50.999> my<00:10:51.269> site<00:10:51.540> com<00:10:51.959> to 00:10:52.280 --> 00:10:52.290 align:start position:0% who has a dns domain like my site com to 00:10:52.290 --> 00:10:54.859 align:start position:0% who has a dns domain like my site com to register<00:10:52.679> the<00:10:52.799> same<00:10:52.980> domain<00:10:53.369> on<00:10:53.639> ENS<00:10:54.119> so<00:10:54.720> that 00:10:54.859 --> 00:10:54.869 align:start position:0% register the same domain on ENS so that 00:10:54.869 --> 00:10:57.350 align:start position:0% register the same domain on ENS so that means<00:10:55.079> that<00:10:55.319> if<00:10:55.529> you<00:10:55.949> have<00:10:55.980> my<00:10:56.339> site<00:10:56.579> calm<00:10:57.059> in 00:10:57.350 --> 00:10:57.360 align:start position:0% means that if you have my site calm in 00:10:57.360 --> 00:10:59.660 align:start position:0% means that if you have my site calm in DNS<00:10:57.720> it's<00:10:58.170> your<00:10:58.319> website<00:10:58.470> you<00:10:59.189> can<00:10:59.339> also<00:10:59.490> have 00:10:59.660 --> 00:10:59.670 align:start position:0% DNS it's your website you can also have 00:10:59.670 --> 00:11:01.730 align:start position:0% DNS it's your website you can also have my<00:10:59.819> site<00:11:00.089> calm<00:11:00.480> in<00:11:00.660> nearness<00:11:01.049> and<00:11:01.350> people<00:11:01.589> can 00:11:01.730 --> 00:11:01.740 align:start position:0% my site calm in nearness and people can 00:11:01.740 --> 00:11:04.340 align:start position:0% my site calm in nearness and people can pay<00:11:01.949> you<00:11:02.009> by<00:11:02.429> typing<00:11:02.939> in<00:11:03.029> my<00:11:03.209> site<00:11:03.449> comm<00:11:03.870> they 00:11:04.340 --> 00:11:04.350 align:start position:0% pay you by typing in my site comm they 00:11:04.350 --> 00:11:06.139 align:start position:0% pay you by typing in my site comm they can<00:11:04.529> load<00:11:04.769> up<00:11:04.799> your<00:11:05.160> smart<00:11:05.579> contract<00:11:06.029> by 00:11:06.139 --> 00:11:06.149 align:start position:0% can load up your smart contract by 00:11:06.149 --> 00:11:09.020 align:start position:0% can load up your smart contract by typing<00:11:06.420> in<00:11:06.540> my<00:11:06.689> site<00:11:06.899> comm<00:11:07.319> into<00:11:08.040> any<00:11:08.220> wall 00:11:09.020 --> 00:11:09.030 align:start position:0% typing in my site comm into any wall 00:11:09.030 --> 00:11:12.650 align:start position:0% typing in my site comm into any wall for<00:11:09.210> any<00:11:09.360> application<00:11:10.050> that<00:11:10.080> supports<00:11:10.770> ENS<00:11:11.660> so 00:11:12.650 --> 00:11:12.660 align:start position:0% for any application that supports ENS so 00:11:12.660 --> 00:11:14.270 align:start position:0% for any application that supports ENS so to<00:11:12.720> set<00:11:12.960> this<00:11:13.080> up<00:11:13.230> this<00:11:13.590> is<00:11:13.740> deployed<00:11:14.040> right 00:11:14.270 --> 00:11:14.280 align:start position:0% to set this up this is deployed right 00:11:14.280 --> 00:11:16.940 align:start position:0% to set this up this is deployed right now<00:11:14.490> on<00:11:14.730> dot<00:11:14.880> XYZ<00:11:15.270> and<00:11:15.630> that's<00:11:16.560> our<00:11:16.740> sort<00:11:16.920> of 00:11:16.940 --> 00:11:16.950 align:start position:0% now on dot XYZ and that's our sort of 00:11:16.950 --> 00:11:18.290 align:start position:0% now on dot XYZ and that's our sort of test<00:11:17.160> domain<00:11:17.310> we're<00:11:17.700> going<00:11:17.820> to<00:11:17.880> roll<00:11:18.060> it<00:11:18.180> out 00:11:18.290 --> 00:11:18.300 align:start position:0% test domain we're going to roll it out 00:11:18.300 --> 00:11:20.150 align:start position:0% test domain we're going to roll it out to<00:11:18.360> weigh<00:11:18.810> more<00:11:19.020> top-level<00:11:19.410> domains<00:11:19.800> like 00:11:20.150 --> 00:11:20.160 align:start position:0% to weigh more top-level domains like 00:11:20.160 --> 00:11:23.060 align:start position:0% to weigh more top-level domains like most<00:11:20.430> of<00:11:20.670> the<00:11:20.790> 2300<00:11:21.540> top-level<00:11:21.870> domains<00:11:22.260> early 00:11:23.060 --> 00:11:23.070 align:start position:0% most of the 2300 top-level domains early 00:11:23.070 --> 00:11:25.040 align:start position:0% most of the 2300 top-level domains early next<00:11:23.220> year<00:11:23.370> but<00:11:24.300> right<00:11:24.330> now<00:11:24.630> if<00:11:24.780> you<00:11:24.900> have<00:11:25.020> a 00:11:25.040 --> 00:11:25.050 align:start position:0% next year but right now if you have a 00:11:25.050 --> 00:11:27.320 align:start position:0% next year but right now if you have a dot<00:11:25.230> explosive<00:11:25.710> domain<00:11:26.010> you<00:11:26.220> can<00:11:26.340> go<00:11:26.490> to<00:11:26.550> ApS 00:11:27.320 --> 00:11:27.330 align:start position:0% dot explosive domain you can go to ApS 00:11:27.330 --> 00:11:29.360 align:start position:0% dot explosive domain you can go to ApS top<00:11:27.510> domains<00:11:27.750> which<00:11:28.140> is<00:11:28.320> our<00:11:28.470> new<00:11:28.650> URL<00:11:29.100> for<00:11:29.310> the 00:11:29.360 --> 00:11:29.370 align:start position:0% top domains which is our new URL for the 00:11:29.370 --> 00:11:31.370 align:start position:0% top domains which is our new URL for the manager<00:11:29.730> you<00:11:30.450> can<00:11:30.600> enter<00:11:30.810> your<00:11:30.840> domain<00:11:31.170> name 00:11:31.370 --> 00:11:31.380 align:start position:0% manager you can enter your domain name 00:11:31.380 --> 00:11:32.600 align:start position:0% manager you can enter your domain name and<00:11:31.410> it<00:11:31.650> will<00:11:31.710> provide<00:11:31.950> you<00:11:32.070> with<00:11:32.100> a<00:11:32.250> series<00:11:32.580> of 00:11:32.600 --> 00:11:32.610 align:start position:0% and it will provide you with a series of 00:11:32.610 --> 00:11:35.570 align:start position:0% and it will provide you with a series of instructions<00:11:33.210> setting<00:11:33.690> it<00:11:33.780> up<00:11:34.190> the<00:11:35.190> second 00:11:35.570 --> 00:11:35.580 align:start position:0% instructions setting it up the second 00:11:35.580 --> 00:11:37.220 align:start position:0% instructions setting it up the second sort<00:11:35.880> of<00:11:35.940> integration<00:11:36.480> we're<00:11:36.660> pursuing<00:11:36.930> is 00:11:37.220 --> 00:11:37.230 align:start position:0% sort of integration we're pursuing is 00:11:37.230 --> 00:11:39.350 align:start position:0% sort of integration we're pursuing is the<00:11:37.410> the<00:11:37.650> individual<00:11:38.190> bespoke<00:11:38.520> ones<00:11:38.790> so<00:11:39.210> these 00:11:39.350 --> 00:11:39.360 align:start position:0% the the individual bespoke ones so these 00:11:39.360 --> 00:11:41.420 align:start position:0% the the individual bespoke ones so these are<00:11:39.570> top<00:11:39.870> level<00:11:40.140> domain<00:11:40.380> providers<00:11:40.890> who<00:11:41.400> have 00:11:41.420 --> 00:11:41.430 align:start position:0% are top level domain providers who have 00:11:41.430 --> 00:11:43.670 align:start position:0% are top level domain providers who have decided<00:11:41.760> to<00:11:41.970> work<00:11:42.150> with<00:11:42.180> us<00:11:42.570> directly<00:11:42.990> to<00:11:43.260> make 00:11:43.670 --> 00:11:43.680 align:start position:0% decided to work with us directly to make 00:11:43.680 --> 00:11:45.140 align:start position:0% decided to work with us directly to make it<00:11:43.800> easier<00:11:44.100> for<00:11:44.160> their<00:11:44.460> users<00:11:44.850> to<00:11:44.880> integrate 00:11:45.140 --> 00:11:45.150 align:start position:0% it easier for their users to integrate 00:11:45.150 --> 00:11:47.390 align:start position:0% it easier for their users to integrate with<00:11:45.450> the<00:11:45.570> NS<00:11:45.810> and<00:11:46.080> the<00:11:46.530> first<00:11:46.710> of<00:11:46.920> these<00:11:47.040> was 00:11:47.390 --> 00:11:47.400 align:start position:0% with the NS and the first of these was 00:11:47.400 --> 00:11:50.120 align:start position:0% with the NS and the first of these was dot<00:11:48.030> Lux<00:11:48.270> they<00:11:49.170> launched<00:11:49.560> a<00:11:49.680> bit<00:11:49.830> over<00:11:50.040> a<00:11:50.070> year 00:11:50.120 --> 00:11:50.130 align:start position:0% dot Lux they launched a bit over a year 00:11:50.130 --> 00:11:52.700 align:start position:0% dot Lux they launched a bit over a year ago<00:11:50.460> they<00:11:51.180> have<00:11:51.300> first<00:11:51.570> pass<00:11:51.810> support<00:11:52.230> for<00:11:52.410> ENS 00:11:52.700 --> 00:11:52.710 align:start position:0% ago they have first pass support for ENS 00:11:52.710 --> 00:11:54.920 align:start position:0% ago they have first pass support for ENS which<00:11:52.980> means<00:11:53.250> that<00:11:53.550> if<00:11:53.790> you<00:11:54.030> register<00:11:54.690> a<00:11:54.720> name 00:11:54.920 --> 00:11:54.930 align:start position:0% which means that if you register a name 00:11:54.930 --> 00:11:56.390 align:start position:0% which means that if you register a name with<00:11:55.110> them<00:11:55.290> using<00:11:55.530> one<00:11:55.770> of<00:11:55.800> their<00:11:55.920> supported 00:11:56.390 --> 00:11:56.400 align:start position:0% with them using one of their supported 00:11:56.400 --> 00:11:58.220 align:start position:0% with them using one of their supported registrar's<00:11:56.940> you<00:11:57.180> can<00:11:57.330> go<00:11:57.570> into<00:11:57.840> the<00:11:57.930> control 00:11:58.220 --> 00:11:58.230 align:start position:0% registrar's you can go into the control 00:11:58.230 --> 00:12:00.920 align:start position:0% registrar's you can go into the control panel<00:11:58.260> into<00:11:59.070> your<00:11:59.370> ENS<00:12:00.000> seria<00:12:00.690> theory 00:12:00.920 --> 00:12:00.930 align:start position:0% panel into your ENS seria theory 00:12:00.930 --> 00:12:03.530 align:start position:0% panel into your ENS seria theory murderous<00:12:01.410> hit<00:12:01.950> go<00:12:02.160> and<00:12:02.460> it's<00:12:02.760> just<00:12:02.970> done<00:12:03.150> it's 00:12:03.530 --> 00:12:03.540 align:start position:0% murderous hit go and it's just done it's 00:12:03.540 --> 00:12:05.360 align:start position:0% murderous hit go and it's just done it's you<00:12:03.870> know<00:12:03.990> several<00:12:04.470> steps<00:12:04.710> shorter<00:12:05.130> than<00:12:05.280> the 00:12:05.360 --> 00:12:05.370 align:start position:0% you know several steps shorter than the 00:12:05.370 --> 00:12:07.460 align:start position:0% you know several steps shorter than the DNA<00:12:05.640> stick<00:12:05.850> integration<00:12:06.480> it's<00:12:06.960> as<00:12:07.110> simple<00:12:07.230> as 00:12:07.460 --> 00:12:07.470 align:start position:0% DNA stick integration it's as simple as 00:12:07.470 --> 00:12:09.380 align:start position:0% DNA stick integration it's as simple as it<00:12:07.560> possibly<00:12:07.950> could<00:12:08.340> be<00:12:08.400> so<00:12:09.150> if<00:12:09.240> you're 00:12:09.380 --> 00:12:09.390 align:start position:0% it possibly could be so if you're 00:12:09.390 --> 00:12:11.000 align:start position:0% it possibly could be so if you're interested<00:12:09.600> to<00:12:09.960> get<00:12:10.140> one<00:12:10.320> of<00:12:10.410> those<00:12:10.590> and<00:12:10.950> you 00:12:11.000 --> 00:12:11.010 align:start position:0% interested to get one of those and you 00:12:11.010 --> 00:12:12.950 align:start position:0% interested to get one of those and you can<00:12:11.220> instantly<00:12:11.760> start<00:12:11.880> using<00:12:12.300> it<00:12:12.540> anywhere 00:12:12.950 --> 00:12:12.960 align:start position:0% can instantly start using it anywhere 00:12:12.960 --> 00:12:17.210 align:start position:0% can instantly start using it anywhere that<00:12:12.990> a<00:12:13.410> DNS<00:12:14.190> name<00:12:14.220> is<00:12:14.580> accepted<00:12:15.920> the<00:12:16.920> second 00:12:17.210 --> 00:12:17.220 align:start position:0% that a DNS name is accepted the second 00:12:17.220 --> 00:12:18.680 align:start position:0% that a DNS name is accepted the second integration<00:12:17.550> slightly<00:12:18.150> different<00:12:18.510> we're 00:12:18.680 --> 00:12:18.690 align:start position:0% integration slightly different we're 00:12:18.690 --> 00:12:21.830 align:start position:0% integration slightly different we're working<00:12:19.020> with<00:12:19.170> doc<00:12:19.380> creates<00:12:19.770> the<00:12:20.040> the<00:12:20.280> TLD<00:12:20.850> to 00:12:21.830 --> 00:12:21.840 align:start position:0% working with doc creates the the TLD to 00:12:21.840 --> 00:12:24.380 align:start position:0% working with doc creates the the TLD to support<00:12:22.230> DNS<00:12:23.040> record<00:12:23.370> integration<00:12:23.970> the<00:12:24.150> idea 00:12:24.380 --> 00:12:24.390 align:start position:0% support DNS record integration the idea 00:12:24.390 --> 00:12:27.230 align:start position:0% support DNS record integration the idea is<00:12:24.540> that<00:12:24.690> we<00:12:24.840> can<00:12:25.020> host<00:12:25.260> the<00:12:25.650> DNS<00:12:26.130> zone<00:12:26.490> for<00:12:27.060> doc 00:12:27.230 --> 00:12:27.240 align:start position:0% is that we can host the DNS zone for doc 00:12:27.240 --> 00:12:29.630 align:start position:0% is that we can host the DNS zone for doc Reed<00:12:27.510> on<00:12:27.750> the<00:12:27.780> blockchain<00:12:28.140> and<00:12:28.640> effectively 00:12:29.630 --> 00:12:29.640 align:start position:0% Reed on the blockchain and effectively 00:12:29.640 --> 00:12:32.150 align:start position:0% Reed on the blockchain and effectively this<00:12:29.910> turns<00:12:30.240> every<00:12:30.690> aetherium<00:12:31.260> node<00:12:31.620> in<00:12:32.040> the 00:12:32.150 --> 00:12:32.160 align:start position:0% this turns every aetherium node in the 00:12:32.160 --> 00:12:34.220 align:start position:0% this turns every aetherium node in the world<00:12:32.370> into<00:12:33.120> a<00:12:33.150> secondary<00:12:33.660> name<00:12:33.810> server<00:12:34.080> for 00:12:34.220 --> 00:12:34.230 align:start position:0% world into a secondary name server for 00:12:34.230 --> 00:12:35.870 align:start position:0% world into a secondary name server for creator<00:12:34.680> it<00:12:34.800> means<00:12:35.010> that<00:12:35.280> if<00:12:35.430> you<00:12:35.520> have<00:12:35.550> a<00:12:35.670> doc 00:12:35.870 --> 00:12:35.880 align:start position:0% creator it means that if you have a doc 00:12:35.880 --> 00:12:38.450 align:start position:0% creator it means that if you have a doc read<00:12:36.120> domain<00:12:36.450> it<00:12:37.020> can't<00:12:37.290> be<00:12:37.380> taken<00:12:37.530> out<00:12:37.800> by<00:12:38.100> all 00:12:38.450 --> 00:12:38.460 align:start position:0% read domain it can't be taken out by all 00:12:38.460 --> 00:12:40.550 align:start position:0% read domain it can't be taken out by all that<00:12:38.640> the<00:12:38.790> DNS<00:12:39.300> service<00:12:39.750> can't<00:12:39.990> be<00:12:40.050> taken<00:12:40.440> out 00:12:40.550 --> 00:12:40.560 align:start position:0% that the DNS service can't be taken out 00:12:40.560 --> 00:12:42.590 align:start position:0% that the DNS service can't be taken out by<00:12:40.770> denial<00:12:41.340> of<00:12:41.490> service<00:12:41.850> it<00:12:42.030> can't<00:12:42.240> be<00:12:42.300> taken 00:12:42.590 --> 00:12:42.600 align:start position:0% by denial of service it can't be taken 00:12:42.600 --> 00:12:44.720 align:start position:0% by denial of service it can't be taken out<00:12:42.720> by<00:12:42.900> a<00:12:42.930> service<00:12:43.320> failure<00:12:43.740> because<00:12:44.370> anyone 00:12:44.720 --> 00:12:44.730 align:start position:0% out by a service failure because anyone 00:12:44.730 --> 00:12:46.400 align:start position:0% out by a service failure because anyone in<00:12:44.850> the<00:12:44.910> world<00:12:45.030> can<00:12:45.360> replicate<00:12:45.570> those<00:12:45.900> records 00:12:46.400 --> 00:12:46.410 align:start position:0% in the world can replicate those records 00:12:46.410 --> 00:12:48.290 align:start position:0% in the world can replicate those records and<00:12:46.530> serve<00:12:46.740> them<00:12:46.950> up<00:12:47.040> and<00:12:47.550> verify<00:12:47.940> them<00:12:48.120> for 00:12:48.290 --> 00:12:48.300 align:start position:0% and serve them up and verify them for 00:12:48.300 --> 00:12:49.240 align:start position:0% and serve them up and verify them for themselves 00:12:49.240 --> 00:12:49.250 align:start position:0% themselves 00:12:49.250 --> 00:12:52.280 align:start position:0% themselves finally<00:12:50.250> we're<00:12:50.520> also<00:12:50.670> working<00:12:50.970> with<00:12:51.150> dart<00:12:51.660> you 00:12:52.280 --> 00:12:52.290 align:start position:0% finally we're also working with dart you 00:12:52.290 --> 00:12:54.020 align:start position:0% finally we're also working with dart you might<00:12:52.530> be<00:12:52.650> familiar<00:12:52.830> of<00:12:53.220> the<00:12:53.400> art<00:12:53.730> digital 00:12:54.020 --> 00:12:54.030 align:start position:0% might be familiar of the art digital 00:12:54.030 --> 00:12:56.600 align:start position:0% might be familiar of the art digital twin<00:12:54.510> this<00:12:54.780> is<00:12:54.960> their<00:12:55.170> project<00:12:55.440> to<00:12:56.250> have 00:12:56.600 --> 00:12:56.610 align:start position:0% twin this is their project to have 00:12:56.610 --> 00:12:58.520 align:start position:0% twin this is their project to have physical<00:12:57.210> artworks<00:12:57.810> that<00:12:57.990> have<00:12:58.290> a 00:12:58.520 --> 00:12:58.530 align:start position:0% physical artworks that have a 00:12:58.530 --> 00:13:01.250 align:start position:0% physical artworks that have a corresponding<00:12:59.990> existence<00:13:00.990> on<00:13:01.170> the 00:13:01.250 --> 00:13:01.260 align:start position:0% corresponding existence on the 00:13:01.260 --> 00:13:02.660 align:start position:0% corresponding existence on the blockchain<00:13:01.440> the<00:13:01.860> form<00:13:02.070> of<00:13:02.190> the<00:13:02.280> non-tangible 00:13:02.660 --> 00:13:02.670 align:start position:0% blockchain the form of the non-tangible 00:13:02.670 --> 00:13:05.930 align:start position:0% blockchain the form of the non-tangible token<00:13:03.270> we<00:13:04.080> recently<00:13:04.760> enabled<00:13:05.760> their 00:13:05.930 --> 00:13:05.940 align:start position:0% token we recently enabled their 00:13:05.940 --> 00:13:07.940 align:start position:0% token we recently enabled their namespace<00:13:06.450> on<00:13:06.720> Enes<00:13:07.110> so<00:13:07.440> they'll<00:13:07.560> now<00:13:07.710> be<00:13:07.770> able 00:13:07.940 --> 00:13:07.950 align:start position:0% namespace on Enes so they'll now be able 00:13:07.950 --> 00:13:11.480 align:start position:0% namespace on Enes so they'll now be able to<00:13:08.100> offer<00:13:08.250> domains<00:13:08.580> by<00:13:09.090> a<00:13:09.120> aeneas<00:13:10.340> next<00:13:11.340> up 00:13:11.480 --> 00:13:11.490 align:start position:0% to offer domains by a aeneas next up 00:13:11.490 --> 00:13:14.030 align:start position:0% to offer domains by a aeneas next up we've<00:13:12.210> been<00:13:12.420> working<00:13:12.780> with<00:13:12.810> the<00:13:13.500> IP<00:13:13.650> affairs 00:13:14.030 --> 00:13:14.040 align:start position:0% we've been working with the IP affairs 00:13:14.040 --> 00:13:15.950 align:start position:0% we've been working with the IP affairs team<00:13:14.280> we've<00:13:15.030> got<00:13:15.060> a<00:13:15.210> generous<00:13:15.600> grant<00:13:15.840> from 00:13:15.950 --> 00:13:15.960 align:start position:0% team we've got a generous grant from 00:13:15.960 --> 00:13:17.660 align:start position:0% team we've got a generous grant from them<00:13:16.260> and<00:13:16.800> we've<00:13:16.920> been<00:13:17.070> working<00:13:17.160> with<00:13:17.460> them 00:13:17.660 --> 00:13:17.670 align:start position:0% them and we've been working with them 00:13:17.670 --> 00:13:20.180 align:start position:0% them and we've been working with them and<00:13:17.880> Jim<00:13:18.060> McDonald<00:13:18.510> to<00:13:19.260> build<00:13:19.440> integration 00:13:20.180 --> 00:13:20.190 align:start position:0% and Jim McDonald to build integration 00:13:20.190 --> 00:13:23.080 align:start position:0% and Jim McDonald to build integration closer<00:13:20.580> integration<00:13:20.880> between<00:13:21.540> IP<00:13:21.870> Fes<00:13:22.320> any 00:13:23.080 --> 00:13:23.090 align:start position:0% closer integration between IP Fes any 00:13:23.090 --> 00:13:26.320 align:start position:0% closer integration between IP Fes any the<00:13:23.660> way<00:13:23.780> this<00:13:23.960> works<00:13:24.200> is<00:13:24.500> you<00:13:25.310> can<00:13:25.610> point<00:13:25.970> any 00:13:26.320 --> 00:13:26.330 align:start position:0% the way this works is you can point any 00:13:26.330 --> 00:13:29.080 align:start position:0% the way this works is you can point any ENS<00:13:26.870> site<00:13:27.110> on<00:13:27.410> da<00:13:27.590> teeth<00:13:27.770> or<00:13:28.010> anywhere<00:13:28.310> else<00:13:28.340> at 00:13:29.080 --> 00:13:29.090 align:start position:0% ENS site on da teeth or anywhere else at 00:13:29.090 --> 00:13:32.890 align:start position:0% ENS site on da teeth or anywhere else at an<00:13:29.300> IPF<00:13:30.140> es<00:13:30.320> content<00:13:30.880> and<00:13:31.880> if<00:13:32.300> you<00:13:32.540> use<00:13:32.750> it 00:13:32.890 --> 00:13:32.900 align:start position:0% an IPF es content and if you use it 00:13:32.900 --> 00:13:34.180 align:start position:0% an IPF es content and if you use it right<00:13:33.020> now<00:13:33.200> in<00:13:33.350> Musa<00:13:33.500> mask<00:13:33.710> it<00:13:33.890> will<00:13:34.010> just 00:13:34.180 --> 00:13:34.190 align:start position:0% right now in Musa mask it will just 00:13:34.190 --> 00:13:35.980 align:start position:0% right now in Musa mask it will just resolve<00:13:34.490> but<00:13:34.910> you<00:13:35.150> don't<00:13:35.360> have<00:13:35.540> to<00:13:35.720> be<00:13:35.810> running 00:13:35.980 --> 00:13:35.990 align:start position:0% resolve but you don't have to be running 00:13:35.990 --> 00:13:38.650 align:start position:0% resolve but you don't have to be running meta<00:13:36.260> mask<00:13:36.530> for<00:13:36.770> this<00:13:36.830> to<00:13:36.980> work<00:13:37.160> we<00:13:37.790> the<00:13:38.300> EMS 00:13:38.650 --> 00:13:38.660 align:start position:0% meta mask for this to work we the EMS 00:13:38.660 --> 00:13:41.110 align:start position:0% meta mask for this to work we the EMS team<00:13:38.690> operate<00:13:39.320> a<00:13:39.500> DNS<00:13:39.950> and<00:13:40.190> a<00:13:40.220> nearness<00:13:40.640> and<00:13:40.700> IP 00:13:41.110 --> 00:13:41.120 align:start position:0% team operate a DNS and a nearness and IP 00:13:41.120 --> 00:13:43.480 align:start position:0% team operate a DNS and a nearness and IP at<00:13:41.360> this<00:13:41.480> gateway<00:13:41.900> on<00:13:42.110> East<00:13:42.350> dot<00:13:42.560> link<00:13:42.770> so<00:13:43.370> if 00:13:43.480 --> 00:13:43.490 align:start position:0% at this gateway on East dot link so if 00:13:43.490 --> 00:13:45.910 align:start position:0% at this gateway on East dot link so if you<00:13:43.610> did<00:13:43.880> dot<00:13:44.240> link<00:13:44.540> to<00:13:44.840> any<00:13:45.050> eath<00:13:45.230> domain<00:13:45.620> and 00:13:45.910 --> 00:13:45.920 align:start position:0% you did dot link to any eath domain and 00:13:45.920 --> 00:13:47.920 align:start position:0% you did dot link to any eath domain and that<00:13:45.950> domain<00:13:46.490> has<00:13:46.760> IP<00:13:46.940> at<00:13:47.150> this<00:13:47.300> content<00:13:47.720> it 00:13:47.920 --> 00:13:47.930 align:start position:0% that domain has IP at this content it 00:13:47.930 --> 00:13:49.720 align:start position:0% that domain has IP at this content it will<00:13:48.050> load<00:13:48.260> in<00:13:48.470> any<00:13:48.620> browser<00:13:48.830> anywhere<00:13:49.580> in<00:13:49.640> the 00:13:49.720 --> 00:13:49.730 align:start position:0% will load in any browser anywhere in the 00:13:49.730 --> 00:13:51.820 align:start position:0% will load in any browser anywhere in the world<00:13:49.940> no<00:13:50.270> special<00:13:50.780> integration<00:13:51.290> supported 00:13:51.820 --> 00:13:51.830 align:start position:0% world no special integration supported 00:13:51.830 --> 00:13:54.700 align:start position:0% world no special integration supported so<00:13:52.460> as<00:13:52.760> an<00:13:52.880> example<00:13:53.000> go<00:13:53.630> to<00:13:53.690> El<00:13:53.960> mono<00:13:54.230> teeth 00:13:54.700 --> 00:13:54.710 align:start position:0% so as an example go to El mono teeth 00:13:54.710 --> 00:13:56.920 align:start position:0% so as an example go to El mono teeth link<00:13:55.190> and<00:13:55.400> it<00:13:55.760> will<00:13:55.880> load<00:13:56.000> you<00:13:56.180> a<00:13:56.210> directory<00:13:56.780> of 00:13:56.920 --> 00:13:56.930 align:start position:0% link and it will load you a directory of 00:13:56.930 --> 00:13:58.420 align:start position:0% link and it will load you a directory of decentralized<00:13:57.320> websites<00:13:57.950> that<00:13:58.220> you<00:13:58.310> can 00:13:58.420 --> 00:13:58.430 align:start position:0% decentralized websites that you can 00:13:58.430 --> 00:14:00.970 align:start position:0% decentralized websites that you can access<00:13:58.580> anywhere<00:13:59.380> you<00:14:00.380> can<00:14:00.530> operate<00:14:00.740> your<00:14:00.860> own 00:14:00.970 --> 00:14:00.980 align:start position:0% access anywhere you can operate your own 00:14:00.980 --> 00:14:02.740 align:start position:0% access anywhere you can operate your own gateway<00:14:01.460> you<00:14:01.520> don't<00:14:01.850> have<00:14:01.940> to<00:14:02.030> trust<00:14:02.270> us<00:14:02.480> to 00:14:02.740 --> 00:14:02.750 align:start position:0% gateway you don't have to trust us to 00:14:02.750 --> 00:14:04.660 align:start position:0% gateway you don't have to trust us to correctly<00:14:03.110> serve<00:14:03.380> up<00:14:03.530> the<00:14:03.650> right<00:14:03.830> DNS<00:14:04.190> records 00:14:04.660 --> 00:14:04.670 align:start position:0% correctly serve up the right DNS records 00:14:04.670 --> 00:14:06.790 align:start position:0% correctly serve up the right DNS records and<00:14:04.790> ipfs<00:14:05.240> conch<00:14:05.540> content<00:14:06.230> you<00:14:06.380> can<00:14:06.530> run<00:14:06.680> this 00:14:06.790 --> 00:14:06.800 align:start position:0% and ipfs conch content you can run this 00:14:06.800 --> 00:14:09.160 align:start position:0% and ipfs conch content you can run this yourself<00:14:07.220> and<00:14:08.090> finally<00:14:08.600> something<00:14:08.990> that<00:14:09.020> we 00:14:09.160 --> 00:14:09.170 align:start position:0% yourself and finally something that we 00:14:09.170 --> 00:14:11.020 align:start position:0% yourself and finally something that we got<00:14:09.290> working<00:14:09.890> just<00:14:10.160> in<00:14:10.310> the<00:14:10.430> lead<00:14:10.580> up<00:14:10.730> to<00:14:10.760> this 00:14:11.020 --> 00:14:11.030 align:start position:0% got working just in the lead up to this 00:14:11.030 --> 00:14:13.930 align:start position:0% got working just in the lead up to this we<00:14:11.630> have<00:14:11.780> a<00:14:11.810> DNS<00:14:12.200> over<00:14:12.560> HTTP<00:14:13.160> gateway<00:14:13.520> if<00:14:13.760> your 00:14:13.930 --> 00:14:13.940 align:start position:0% we have a DNS over HTTP gateway if your 00:14:13.940 --> 00:14:15.880 align:start position:0% we have a DNS over HTTP gateway if your browser<00:14:14.180> supports<00:14:14.720> that<00:14:14.900> you<00:14:15.170> can<00:14:15.590> point<00:14:15.740> it 00:14:15.880 --> 00:14:15.890 align:start position:0% browser supports that you can point it 00:14:15.890 --> 00:14:18.250 align:start position:0% browser supports that you can point it at<00:14:16.040> our<00:14:16.190> servers<00:14:16.640> and<00:14:16.850> your<00:14:17.330> browser<00:14:17.570> with<00:14:18.020> no 00:14:18.250 --> 00:14:18.260 align:start position:0% at our servers and your browser with no 00:14:18.260 --> 00:14:20.230 align:start position:0% at our servers and your browser with no plugins<00:14:18.560> with<00:14:19.040> no<00:14:19.250> special<00:14:19.550> support<00:14:20.000> we'll 00:14:20.230 --> 00:14:20.240 align:start position:0% plugins with no special support we'll 00:14:20.240 --> 00:14:22.480 align:start position:0% plugins with no special support we'll start<00:14:20.540> resolving<00:14:20.810> dthe<00:14:21.320> domains<00:14:21.740> in<00:14:22.400> the 00:14:22.480 --> 00:14:22.490 align:start position:0% start resolving dthe domains in the 00:14:22.490 --> 00:14:24.280 align:start position:0% start resolving dthe domains in the browser<00:14:22.820> as<00:14:23.180> if<00:14:23.360> they<00:14:23.510> were<00:14:23.570> top-level 00:14:24.280 --> 00:14:24.290 align:start position:0% browser as if they were top-level 00:14:24.290 --> 00:14:28.060 align:start position:0% browser as if they were top-level domains<00:14:24.620> in<00:14:24.830> the<00:14:24.860> global<00:14:25.220> root<00:14:26.830> and<00:14:27.830> we're 00:14:28.060 --> 00:14:28.070 align:start position:0% domains in the global root and we're 00:14:28.070 --> 00:14:29.860 align:start position:0% domains in the global root and we're also<00:14:28.340> been<00:14:28.730> doing<00:14:28.850> some<00:14:28.970> integration<00:14:29.600> with 00:14:29.860 --> 00:14:29.870 align:start position:0% also been doing some integration with 00:14:29.870 --> 00:14:33.160 align:start position:0% also been doing some integration with the<00:14:30.110> Tor<00:14:30.650> network<00:14:31.060> so<00:14:32.060> we<00:14:32.360> had<00:14:32.570> a<00:14:32.600> hackathon 00:14:33.160 --> 00:14:33.170 align:start position:0% the Tor network so we had a hackathon 00:14:33.170 --> 00:14:36.010 align:start position:0% the Tor network so we had a hackathon project<00:14:33.200> and<00:14:33.800> if<00:14:33.890> New<00:14:34.490> York<00:14:35.090> a<00:14:35.330> project<00:14:35.900> called 00:14:36.010 --> 00:14:36.020 align:start position:0% project and if New York a project called 00:14:36.020 --> 00:14:38.530 align:start position:0% project and if New York a project called East<00:14:36.230> or<00:14:36.440> gate<00:14:36.620> and<00:14:36.830> building<00:14:37.640> on<00:14:37.760> that<00:14:37.790> ENS 00:14:38.530 --> 00:14:38.540 align:start position:0% East or gate and building on that ENS 00:14:38.540 --> 00:14:40.480 align:start position:0% East or gate and building on that ENS can<00:14:38.780> now<00:14:38.900> point<00:14:39.140> at<00:14:39.350> onion<00:14:39.680> hidden<00:14:39.980> services 00:14:40.480 --> 00:14:40.490 align:start position:0% can now point at onion hidden services 00:14:40.490 --> 00:14:44.260 align:start position:0% can now point at onion hidden services which<00:14:41.210> means<00:14:41.420> that<00:14:41.780> you<00:14:41.990> can<00:14:42.230> take<00:14:42.500> in<00:14:43.160> yes<00:14:43.880> yes 00:14:44.260 --> 00:14:44.270 align:start position:0% which means that you can take in yes yes 00:14:44.270 --> 00:14:46.090 align:start position:0% which means that you can take in yes yes the<00:14:44.570> main<00:14:44.720> point<00:14:45.080> of<00:14:45.170> any<00:14:45.500> onion<00:14:45.860> hidden 00:14:46.090 --> 00:14:46.100 align:start position:0% the main point of any onion hidden 00:14:46.100 --> 00:14:48.640 align:start position:0% the main point of any onion hidden service<00:14:46.460> for<00:14:46.730> instant<00:14:47.060> example<00:14:47.600> Facebook<00:14:48.380> tor 00:14:48.640 --> 00:14:48.650 align:start position:0% service for instant example Facebook tor 00:14:48.650 --> 00:14:51.040 align:start position:0% service for instant example Facebook tor death<00:14:49.010> was<00:14:49.400> set<00:14:49.610> up<00:14:49.640> by<00:14:49.850> Asti<00:14:50.240> in<00:14:50.420> its<00:14:50.570> team<00:14:50.810> and 00:14:51.040 --> 00:14:51.050 align:start position:0% death was set up by Asti in its team and 00:14:51.050 --> 00:14:53.560 align:start position:0% death was set up by Asti in its team and when<00:14:51.980> you<00:14:52.100> go<00:14:52.280> there<00:14:52.310> will<00:14:52.790> load<00:14:52.970> the<00:14:53.180> Facebook 00:14:53.560 --> 00:14:53.570 align:start position:0% when you go there will load the Facebook 00:14:53.570 --> 00:14:55.060 align:start position:0% when you go there will load the Facebook hidden<00:14:53.840> service<00:14:54.200> if<00:14:54.380> you<00:14:54.470> load<00:14:54.650> it<00:14:54.830> in<00:14:54.950> a 00:14:55.060 --> 00:14:55.070 align:start position:0% hidden service if you load it in a 00:14:55.070 --> 00:14:57.130 align:start position:0% hidden service if you load it in a browser<00:14:55.700> that<00:14:55.940> has<00:14:56.090> both<00:14:56.420> tor<00:14:56.780> any<00:14:56.990> any 00:14:57.130 --> 00:14:57.140 align:start position:0% browser that has both tor any any 00:14:57.140 --> 00:14:58.960 align:start position:0% browser that has both tor any any support<00:14:57.590> such<00:14:57.830> as<00:14:58.010> the<00:14:58.100> tor<00:14:58.280> browser<00:14:58.310> with 00:14:58.960 --> 00:14:58.970 align:start position:0% support such as the tor browser with 00:14:58.970 --> 00:15:02.110 align:start position:0% support such as the tor browser with meta<00:14:59.240> mask<00:14:59.650> and<00:15:00.650> if<00:15:00.800> you<00:15:00.920> look<00:15:01.160> at<00:15:01.340> the<00:15:01.520> records 00:15:02.110 --> 00:15:02.120 align:start position:0% meta mask and if you look at the records 00:15:02.120 --> 00:15:04.360 align:start position:0% meta mask and if you look at the records for<00:15:02.330> Facebook<00:15:02.660> tor<00:15:02.930> teeth<00:15:03.230> on<00:15:03.500> our<00:15:03.710> manager<00:15:04.160> or 00:15:04.360 --> 00:15:04.370 align:start position:0% for Facebook tor teeth on our manager or 00:15:04.370 --> 00:15:06.160 align:start position:0% for Facebook tor teeth on our manager or on<00:15:04.520> anther<00:15:04.820> scan<00:15:05.090> you'll<00:15:05.660> see<00:15:05.870> that<00:15:05.990> they're 00:15:06.160 --> 00:15:06.170 align:start position:0% on anther scan you'll see that they're 00:15:06.170 --> 00:15:08.230 align:start position:0% on anther scan you'll see that they're actually<00:15:06.290> owned<00:15:06.650> by<00:15:06.740> nobody<00:15:07.160> and<00:15:07.610> what<00:15:08.120> this 00:15:08.230 --> 00:15:08.240 align:start position:0% actually owned by nobody and what this 00:15:08.240 --> 00:15:10.120 align:start position:0% actually owned by nobody and what this means<00:15:08.480> is<00:15:08.810> that<00:15:08.840> once<00:15:09.290> it's<00:15:09.470> been<00:15:09.620> set<00:15:09.830> up<00:15:09.860> it 00:15:10.120 --> 00:15:10.130 align:start position:0% means is that once it's been set up it 00:15:10.130 --> 00:15:11.560 align:start position:0% means is that once it's been set up it is<00:15:10.250> permanently<00:15:10.760> that<00:15:10.970> way<00:15:11.120> you<00:15:11.180> don't<00:15:11.450> have 00:15:11.560 --> 00:15:11.570 align:start position:0% is permanently that way you don't have 00:15:11.570 --> 00:15:13.360 align:start position:0% is permanently that way you don't have to<00:15:11.690> trust<00:15:12.050> that<00:15:12.290> whoever<00:15:12.440> set<00:15:12.860> it<00:15:12.950> up<00:15:13.070> is<00:15:13.250> not 00:15:13.360 --> 00:15:13.370 align:start position:0% to trust that whoever set it up is not 00:15:13.370 --> 00:15:14.800 align:start position:0% to trust that whoever set it up is not going<00:15:13.520> to<00:15:13.640> redirect<00:15:13.910> it<00:15:14.240> to<00:15:14.360> a<00:15:14.390> phishing 00:15:14.800 --> 00:15:14.810 align:start position:0% going to redirect it to a phishing 00:15:14.810 --> 00:15:16.780 align:start position:0% going to redirect it to a phishing version<00:15:15.200> of<00:15:15.290> Facebook<00:15:15.470> tomorrow<00:15:16.010> because 00:15:16.780 --> 00:15:16.790 align:start position:0% version of Facebook tomorrow because 00:15:16.790 --> 00:15:19.330 align:start position:0% version of Facebook tomorrow because that<00:15:17.000> resolution<00:15:17.960> is<00:15:18.350> now<00:15:18.500> locked<00:15:18.740> in<00:15:18.950> and<00:15:19.160> set 00:15:19.330 --> 00:15:19.340 align:start position:0% that resolution is now locked in and set 00:15:19.340 --> 00:15:25.780 align:start position:0% that resolution is now locked in and set in<00:15:19.460> stone<00:15:21.910> so<00:15:22.960> last<00:15:23.960> up<00:15:24.200> finally<00:15:24.740> what<00:15:25.610> are<00:15:25.730> we 00:15:25.780 --> 00:15:25.790 align:start position:0% in stone so last up finally what are we 00:15:25.790 --> 00:15:28.420 align:start position:0% in stone so last up finally what are we working<00:15:25.940> on<00:15:26.210> next<00:15:26.690> so<00:15:27.320> the<00:15:27.890> first<00:15:28.130> and<00:15:28.340> biggest 00:15:28.420 --> 00:15:28.430 align:start position:0% working on next so the first and biggest 00:15:28.430 --> 00:15:29.830 align:start position:0% working on next so the first and biggest thing<00:15:28.760> that<00:15:28.790> we're<00:15:29.030> working<00:15:29.150> on<00:15:29.420> right<00:15:29.480> now<00:15:29.690> is 00:15:29.830 --> 00:15:29.840 align:start position:0% thing that we're working on right now is 00:15:29.840 --> 00:15:32.770 align:start position:0% thing that we're working on right now is multi<00:15:30.650> chain<00:15:30.830> support<00:15:31.280> an<00:15:31.400> DNS<00:15:31.760> that's<00:15:32.420> eep<00:15:32.570> to 00:15:32.770 --> 00:15:32.780 align:start position:0% multi chain support an DNS that's eep to 00:15:32.780 --> 00:15:34.960 align:start position:0% multi chain support an DNS that's eep to 304<00:15:33.320> if<00:15:33.560> you<00:15:33.800> want<00:15:34.010> to<00:15:34.130> read<00:15:34.310> the<00:15:34.520> standards 00:15:34.960 --> 00:15:34.970 align:start position:0% 304 if you want to read the standards 00:15:34.970 --> 00:15:36.020 align:start position:0% 304 if you want to read the standards document 00:15:36.020 --> 00:15:36.030 align:start position:0% document 00:15:36.030 --> 00:15:37.540 align:start position:0% document but<00:15:36.270> what<00:15:36.450> it<00:15:36.540> means<00:15:36.570> is<00:15:37.080> it's<00:15:37.230> a<00:15:37.320> way<00:15:37.500> for 00:15:37.540 --> 00:15:37.550 align:start position:0% but what it means is it's a way for 00:15:37.550 --> 00:15:39.830 align:start position:0% but what it means is it's a way for encoding<00:15:38.550> addresses<00:15:39.090> for<00:15:39.270> multiple<00:15:39.600> chains 00:15:39.830 --> 00:15:39.840 align:start position:0% encoding addresses for multiple chains 00:15:39.840 --> 00:15:41.360 align:start position:0% encoding addresses for multiple chains for<00:15:40.110> Bitcoin<00:15:40.380> based<00:15:40.620> chains<00:15:40.920> for<00:15:41.160> theory 00:15:41.360 --> 00:15:41.370 align:start position:0% for Bitcoin based chains for theory 00:15:41.370 --> 00:15:43.250 align:start position:0% for Bitcoin based chains for theory based<00:15:41.640> chains<00:15:41.940> real<00:15:42.330> space<00:15:42.600> chains<00:15:42.960> for 00:15:43.250 --> 00:15:43.260 align:start position:0% based chains real space chains for 00:15:43.260 --> 00:15:45.650 align:start position:0% based chains real space chains for whatever<00:15:43.410> you<00:15:43.620> want<00:15:43.650> in<00:15:44.460> an<00:15:44.640> e<00:15:44.730> NS<00:15:44.970> record<00:15:45.180> and 00:15:45.650 --> 00:15:45.660 align:start position:0% whatever you want in an e NS record and 00:15:45.660 --> 00:15:47.930 align:start position:0% whatever you want in an e NS record and that<00:15:46.080> means<00:15:46.320> that<00:15:46.590> NS<00:15:47.040> can<00:15:47.220> become<00:15:47.460> the<00:15:47.610> naming 00:15:47.930 --> 00:15:47.940 align:start position:0% that means that NS can become the naming 00:15:47.940 --> 00:15:49.460 align:start position:0% that means that NS can become the naming service<00:15:48.300> not<00:15:48.480> just<00:15:48.720> for<00:15:48.840> a<00:15:48.870> theory<00:15:49.200> and<00:15:49.320> not 00:15:49.460 --> 00:15:49.470 align:start position:0% service not just for a theory and not 00:15:49.470 --> 00:15:51.620 align:start position:0% service not just for a theory and not just<00:15:49.740> for<00:15:49.860> internet<00:15:50.220> resources<00:15:50.730> but<00:15:51.420> for 00:15:51.620 --> 00:15:51.630 align:start position:0% just for internet resources but for 00:15:51.630 --> 00:15:54.200 align:start position:0% just for internet resources but for every<00:15:51.900> single<00:15:52.170> blockchain<00:15:52.530> out<00:15:52.680> there<00:15:52.970> so<00:15:53.970> in 00:15:54.200 --> 00:15:54.210 align:start position:0% every single blockchain out there so in 00:15:54.210 --> 00:15:56.120 align:start position:0% every single blockchain out there so in supported<00:15:54.690> wallets<00:15:55.020> if<00:15:55.290> you<00:15:55.470> have<00:15:55.710> a<00:15:55.740> Bitcoin 00:15:56.120 --> 00:15:56.130 align:start position:0% supported wallets if you have a Bitcoin 00:15:56.130 --> 00:15:57.710 align:start position:0% supported wallets if you have a Bitcoin wallet<00:15:56.160> you'll<00:15:56.550> be<00:15:56.670> able<00:15:56.790> to<00:15:56.970> use<00:15:57.150> my<00:15:57.390> name<00:15:57.570> da 00:15:57.710 --> 00:15:57.720 align:start position:0% wallet you'll be able to use my name da 00:15:57.720 --> 00:16:00.560 align:start position:0% wallet you'll be able to use my name da teeth<00:15:57.900> or<00:15:58.170> my<00:15:58.530> name<00:15:58.740> comm<00:15:59.190> or<00:15:59.460> my<00:15:59.610> name<00:15:59.820> dot<00:16:00.120> XYZ 00:16:00.560 --> 00:16:00.570 align:start position:0% teeth or my name comm or my name dot XYZ 00:16:00.570 --> 00:16:03.710 align:start position:0% teeth or my name comm or my name dot XYZ to<00:16:01.290> load<00:16:01.500> your<00:16:01.890> Bitcoin<00:16:02.730> address<00:16:02.760> or<00:16:03.330> your<00:16:03.510> ear 00:16:03.710 --> 00:16:03.720 align:start position:0% to load your Bitcoin address or your ear 00:16:03.720 --> 00:16:05.690 align:start position:0% to load your Bitcoin address or your ear surgery<00:16:04.080> so<00:16:04.260> your<00:16:04.410> like<00:16:04.560> coin<00:16:04.830> or<00:16:05.010> dogecoin<00:16:05.520> or 00:16:05.690 --> 00:16:05.700 align:start position:0% surgery so your like coin or dogecoin or 00:16:05.700 --> 00:16:08.030 align:start position:0% surgery so your like coin or dogecoin or whatever<00:16:05.940> suits<00:16:06.180> you<00:16:06.390> and<00:16:07.380> we<00:16:07.560> really<00:16:07.710> like<00:16:08.010> to 00:16:08.030 --> 00:16:08.040 align:start position:0% whatever suits you and we really like to 00:16:08.040 --> 00:16:10.130 align:start position:0% whatever suits you and we really like to thank<00:16:08.310> Bonanza<00:16:08.820> X<00:16:08.940> for<00:16:09.240> giving<00:16:09.750> us<00:16:09.840> a<00:16:09.930> grant 00:16:10.130 --> 00:16:10.140 align:start position:0% thank Bonanza X for giving us a grant 00:16:10.140 --> 00:16:12.830 align:start position:0% thank Bonanza X for giving us a grant that<00:16:10.350> helped<00:16:10.620> us<00:16:10.740> get<00:16:11.280> this<00:16:11.460> past<00:16:11.700> the<00:16:11.880> line<00:16:12.060> so 00:16:12.830 --> 00:16:12.840 align:start position:0% that helped us get this past the line so 00:16:12.840 --> 00:16:16.580 align:start position:0% that helped us get this past the line so we<00:16:13.590> wrote<00:16:13.890> the<00:16:14.040> CIP<00:16:14.340> about<00:16:14.820> two<00:16:15.360> weeks<00:16:15.540> ago<00:16:15.810> we 00:16:16.580 --> 00:16:16.590 align:start position:0% we wrote the CIP about two weeks ago we 00:16:16.590 --> 00:16:18.710 align:start position:0% we wrote the CIP about two weeks ago we started<00:16:17.040> sort<00:16:17.340> of<00:16:17.430> talking<00:16:18.000> to<00:16:18.270> wallets<00:16:18.570> and 00:16:18.710 --> 00:16:18.720 align:start position:0% started sort of talking to wallets and 00:16:18.720 --> 00:16:20.630 align:start position:0% started sort of talking to wallets and so<00:16:18.900> on<00:16:19.050> and<00:16:19.260> I'm<00:16:19.680> delighted<00:16:19.980> to<00:16:20.190> say<00:16:20.400> that<00:16:20.550> we 00:16:20.630 --> 00:16:20.640 align:start position:0% so on and I'm delighted to say that we 00:16:20.640 --> 00:16:23.750 align:start position:0% so on and I'm delighted to say that we already<00:16:20.820> have<00:16:21.180> so<00:16:21.570> much<00:16:21.780> support<00:16:22.580> decent<00:16:23.580> were 00:16:23.750 --> 00:16:23.760 align:start position:0% already have so much support decent were 00:16:23.760 --> 00:16:25.430 align:start position:0% already have so much support decent were the<00:16:23.850> first<00:16:24.060> to<00:16:24.210> launch<00:16:24.330> support<00:16:24.630> so<00:16:25.170> thank<00:16:25.350> you 00:16:25.430 --> 00:16:25.440 align:start position:0% the first to launch support so thank you 00:16:25.440 --> 00:16:32.030 align:start position:0% the first to launch support so thank you very<00:16:25.560> much<00:16:28.880> and<00:16:30.080> and<00:16:31.080> I<00:16:31.170> want<00:16:31.410> to<00:16:31.560> I<00:16:31.770> want<00:16:31.800> to 00:16:32.030 --> 00:16:32.040 align:start position:0% very much and and I want to I want to 00:16:32.040 --> 00:16:34.030 align:start position:0% very much and and I want to I want to specifically<00:16:32.490> call<00:16:32.790> out<00:16:32.820> Brantly<00:16:33.420> our 00:16:34.030 --> 00:16:34.040 align:start position:0% specifically call out Brantly our 00:16:34.040 --> 00:16:36.470 align:start position:0% specifically call out Brantly our outreach<00:16:35.040> person<00:16:35.280> because<00:16:35.790> some<00:16:36.240> of<00:16:36.270> these 00:16:36.470 --> 00:16:36.480 align:start position:0% outreach person because some of these 00:16:36.480 --> 00:16:38.870 align:start position:0% outreach person because some of these have<00:16:36.720> arrived<00:16:36.990> just<00:16:37.290> now<00:16:37.490> like<00:16:38.490> literally 00:16:38.870 --> 00:16:38.880 align:start position:0% have arrived just now like literally 00:16:38.880 --> 00:16:40.580 align:start position:0% have arrived just now like literally minutes<00:16:39.270> before<00:16:39.600> the<00:16:39.750> talk<00:16:39.960> we<00:16:40.230> now<00:16:40.410> have 00:16:40.580 --> 00:16:40.590 align:start position:0% minutes before the talk we now have 00:16:40.590 --> 00:16:42.890 align:start position:0% minutes before the talk we now have coinbase<00:16:40.830> wallet<00:16:41.370> trust<00:16:41.910> wallet<00:16:42.240> I<00:16:42.390> am<00:16:42.510> token 00:16:42.890 --> 00:16:42.900 align:start position:0% coinbase wallet trust wallet I am token 00:16:42.900 --> 00:16:45.200 align:start position:0% coinbase wallet trust wallet I am token Haven<00:16:43.290> my<00:16:43.440> crypto<00:16:43.860> Portus<00:16:44.310> and<00:16:44.490> Opera<00:16:44.790> have 00:16:45.200 --> 00:16:45.210 align:start position:0% Haven my crypto Portus and Opera have 00:16:45.210 --> 00:16:46.730 align:start position:0% Haven my crypto Portus and Opera have all<00:16:45.360> committed<00:16:45.630> to<00:16:45.900> add<00:16:46.020> support<00:16:46.260> for<00:16:46.650> this 00:16:46.730 --> 00:16:46.740 align:start position:0% all committed to add support for this 00:16:46.740 --> 00:16:48.380 align:start position:0% all committed to add support for this and<00:16:46.980> their<00:16:47.070> wallets<00:16:47.460> which<00:16:47.970> i<00:16:48.150> think<00:16:48.240> is 00:16:48.380 --> 00:16:48.390 align:start position:0% and their wallets which i think is 00:16:48.390 --> 00:16:54.650 align:start position:0% and their wallets which i think is amazing<00:16:52.580> and<00:16:53.580> if<00:16:53.730> you're<00:16:53.880> building<00:16:54.090> tooling 00:16:54.650 --> 00:16:54.660 align:start position:0% amazing and if you're building tooling 00:16:54.660 --> 00:16:55.970 align:start position:0% amazing and if you're building tooling and<00:16:54.810> you<00:16:54.870> want<00:16:55.050> to<00:16:55.110> do<00:16:55.200> this<00:16:55.290> yourself<00:16:55.440> the<00:16:55.950> e 00:16:55.970 --> 00:16:55.980 align:start position:0% and you want to do this yourself the e 00:16:55.980 --> 00:16:57.770 align:start position:0% and you want to do this yourself the e NS<00:16:56.280> libraries<00:16:56.730> on<00:16:56.880> JavaScript<00:16:57.420> will<00:16:57.510> support 00:16:57.770 --> 00:16:57.780 align:start position:0% NS libraries on JavaScript will support 00:16:57.780 --> 00:16:59.900 align:start position:0% NS libraries on JavaScript will support it<00:16:57.960> but<00:16:58.440> ethos<00:16:58.770> Jas<00:16:59.130> is<00:16:59.160> adding<00:16:59.550> support 00:16:59.900 --> 00:16:59.910 align:start position:0% it but ethos Jas is adding support 00:16:59.910 --> 00:17:01.910 align:start position:0% it but ethos Jas is adding support almost<00:17:00.060> immediately<00:17:00.660> so<00:17:01.230> if<00:17:01.500> you<00:17:01.590> don't<00:17:01.770> use 00:17:01.910 --> 00:17:01.920 align:start position:0% almost immediately so if you don't use 00:17:01.920 --> 00:17:03.470 align:start position:0% almost immediately so if you don't use it<00:17:02.070> already<00:17:02.280> I<00:17:02.430> suggest<00:17:02.820> taking<00:17:03.090> a<00:17:03.150> look<00:17:03.300> at<00:17:03.360> it 00:17:03.470 --> 00:17:03.480 align:start position:0% it already I suggest taking a look at it 00:17:03.480 --> 00:17:05.090 align:start position:0% it already I suggest taking a look at it if<00:17:03.630> you<00:17:03.840> do<00:17:03.990> then<00:17:04.290> you<00:17:04.380> will<00:17:04.530> just<00:17:04.680> be<00:17:04.800> able<00:17:04.920> to 00:17:05.090 --> 00:17:05.100 align:start position:0% if you do then you will just be able to 00:17:05.100 --> 00:17:08.270 align:start position:0% if you do then you will just be able to use<00:17:05.280> this<00:17:05.490> straight<00:17:05.790> away<00:17:06.890> what<00:17:07.890> else<00:17:08.040> are<00:17:08.250> we 00:17:08.270 --> 00:17:08.280 align:start position:0% use this straight away what else are we 00:17:08.280 --> 00:17:10.700 align:start position:0% use this straight away what else are we doing<00:17:08.370> so<00:17:09.000> as<00:17:09.600> I<00:17:09.780> mentioned<00:17:10.170> we're<00:17:10.350> rolling 00:17:10.700 --> 00:17:10.710 align:start position:0% doing so as I mentioned we're rolling 00:17:10.710 --> 00:17:14.210 align:start position:0% doing so as I mentioned we're rolling out<00:17:10.800> DNS<00:17:11.240> support<00:17:12.240> to<00:17:12.480> most<00:17:12.690> TLDs<00:17:13.220> that's 00:17:14.210 --> 00:17:14.220 align:start position:0% out DNS support to most TLDs that's 00:17:14.220 --> 00:17:15.650 align:start position:0% out DNS support to most TLDs that's effectively<00:17:14.730> every<00:17:15.180> internet<00:17:15.480> top-level 00:17:15.650 --> 00:17:15.660 align:start position:0% effectively every internet top-level 00:17:15.660 --> 00:17:17.960 align:start position:0% effectively every internet top-level domain<00:17:16.200> that<00:17:16.410> has<00:17:16.470> DNS<00:17:16.950> SEC<00:17:17.160> enabled<00:17:17.640> which<00:17:17.850> is 00:17:17.960 --> 00:17:17.970 align:start position:0% domain that has DNS SEC enabled which is 00:17:17.970 --> 00:17:21.290 align:start position:0% domain that has DNS SEC enabled which is about<00:17:18.180> 80<00:17:18.390> to<00:17:18.570> 90%<00:17:18.900> of<00:17:19.260> them<00:17:19.520> we're<00:17:20.520> working<00:17:21.180> on 00:17:21.290 --> 00:17:21.300 align:start position:0% about 80 to 90% of them we're working on 00:17:21.300 --> 00:17:22.730 align:start position:0% about 80 to 90% of them we're working on more<00:17:21.450> manager<00:17:21.840> improvements<00:17:22.410> of<00:17:22.530> course 00:17:22.730 --> 00:17:22.740 align:start position:0% more manager improvements of course 00:17:22.740 --> 00:17:25.190 align:start position:0% more manager improvements of course that's<00:17:22.980> our<00:17:23.220> ongoing<00:17:23.400> work<00:17:23.720> we<00:17:24.720> want<00:17:24.960> to<00:17:24.990> make 00:17:25.190 --> 00:17:25.200 align:start position:0% that's our ongoing work we want to make 00:17:25.200 --> 00:17:26.870 align:start position:0% that's our ongoing work we want to make it<00:17:25.350> for<00:17:25.470> instance<00:17:25.830> easier<00:17:26.220> to<00:17:26.340> do<00:17:26.460> multiple 00:17:26.870 --> 00:17:26.880 align:start position:0% it for instance easier to do multiple 00:17:26.880 --> 00:17:28.850 align:start position:0% it for instance easier to do multiple operations<00:17:27.240> updates<00:17:27.930> to<00:17:28.110> resolvers<00:17:28.620> and<00:17:28.830> a 00:17:28.850 --> 00:17:28.860 align:start position:0% operations updates to resolvers and a 00:17:28.860 --> 00:17:31.820 align:start position:0% operations updates to resolvers and a simple<00:17:29.130> single<00:17:29.520> transaction<00:17:30.470> we're<00:17:31.470> working 00:17:31.820 --> 00:17:31.830 align:start position:0% simple single transaction we're working 00:17:31.830 --> 00:17:34.580 align:start position:0% simple single transaction we're working on<00:17:31.980> improving<00:17:32.970> the<00:17:33.300> manager<00:17:33.750> interface<00:17:33.990> short 00:17:34.580 --> 00:17:34.590 align:start position:0% on improving the manager interface short 00:17:34.590 --> 00:17:36.080 align:start position:0% on improving the manager interface short name<00:17:34.770> registration<00:17:35.460> again<00:17:35.760> fewer 00:17:36.080 --> 00:17:36.090 align:start position:0% name registration again fewer 00:17:36.090 --> 00:17:37.670 align:start position:0% name registration again fewer transactions<00:17:36.750> and<00:17:37.020> of<00:17:37.140> course<00:17:37.320> once<00:17:37.560> the 00:17:37.670 --> 00:17:37.680 align:start position:0% transactions and of course once the 00:17:37.680 --> 00:17:39.290 align:start position:0% transactions and of course once the auctions<00:17:38.070> are<00:17:38.220> over<00:17:38.520> you'll<00:17:38.970> be<00:17:39.090> able<00:17:39.150> to 00:17:39.290 --> 00:17:39.300 align:start position:0% auctions are over you'll be able to 00:17:39.300 --> 00:17:41.000 align:start position:0% auctions are over you'll be able to register<00:17:39.510> three<00:17:40.080> to<00:17:40.200> six<00:17:40.410> character<00:17:40.800> names 00:17:41.000 --> 00:17:41.010 align:start position:0% register three to six character names 00:17:41.010 --> 00:17:42.860 align:start position:0% register three to six character names just<00:17:41.370> as<00:17:41.520> you<00:17:41.640> can<00:17:41.850> see<00:17:42.210> them<00:17:42.360> plus<00:17:42.540> character 00:17:42.860 --> 00:17:42.870 align:start position:0% just as you can see them plus character 00:17:42.870 --> 00:17:45.680 align:start position:0% just as you can see them plus character names<00:17:43.170> today<00:17:44.180> adoption<00:17:45.180> adoption<00:17:45.300> adoption 00:17:45.680 --> 00:17:45.690 align:start position:0% names today adoption adoption adoption 00:17:45.690 --> 00:17:48.290 align:start position:0% names today adoption adoption adoption it's<00:17:46.350> unsexy<00:17:46.950> in<00:17:47.040> a<00:17:47.130> way<00:17:47.250> but<00:17:47.610> our<00:17:47.790> main<00:17:48.270> job 00:17:48.290 --> 00:17:48.300 align:start position:0% it's unsexy in a way but our main job 00:17:48.300 --> 00:17:49.310 align:start position:0% it's unsexy in a way but our main job now<00:17:48.810> is<00:17:49.080> make 00:17:49.310 --> 00:17:49.320 align:start position:0% now is make 00:17:49.320 --> 00:17:52.159 align:start position:0% now is make ensure<00:17:49.590> that<00:17:49.620> ENS<00:17:50.159> is<00:17:50.429> as<00:17:50.899> ubiquitous<00:17:51.899> and 00:17:52.159 --> 00:17:52.169 align:start position:0% ensure that ENS is as ubiquitous and 00:17:52.169 --> 00:17:54.110 align:start position:0% ensure that ENS is as ubiquitous and Universal<00:17:52.830> as<00:17:52.950> it<00:17:53.100> possibly<00:17:53.250> can<00:17:53.639> be<00:17:53.700> and<00:17:54.029> that 00:17:54.110 --> 00:17:54.120 align:start position:0% Universal as it possibly can be and that 00:17:54.120 --> 00:17:56.149 align:start position:0% Universal as it possibly can be and that means<00:17:54.659> making<00:17:54.899> sure<00:17:55.049> livery<00:17:55.500> wallet<00:17:55.769> supports 00:17:56.149 --> 00:17:56.159 align:start position:0% means making sure livery wallet supports 00:17:56.159 --> 00:17:57.950 align:start position:0% means making sure livery wallet supports that<00:17:56.250> every<00:17:56.490> toolchain<00:17:56.940> supports<00:17:57.419> that<00:17:57.539> it 00:17:57.950 --> 00:17:57.960 align:start position:0% that every toolchain supports that it 00:17:57.960 --> 00:17:59.120 align:start position:0% that every toolchain supports that it should<00:17:58.110> be<00:17:58.230> the<00:17:58.320> default<00:17:58.590> you<00:17:58.830> should<00:17:58.980> be<00:17:59.070> able 00:17:59.120 --> 00:17:59.130 align:start position:0% should be the default you should be able 00:17:59.130 --> 00:18:01.070 align:start position:0% should be the default you should be able to<00:17:59.250> write<00:17:59.460> a<00:17:59.490> DAP<00:17:59.850> and<00:18:00.029> not<00:18:00.299> even<00:18:00.570> know<00:18:00.779> about 00:18:01.070 --> 00:18:01.080 align:start position:0% to write a DAP and not even know about 00:18:01.080 --> 00:18:03.110 align:start position:0% to write a DAP and not even know about ENS<00:18:01.590> but<00:18:01.889> just<00:18:02.130> have<00:18:02.250> it<00:18:02.370> work<00:18:02.549> because<00:18:02.850> your 00:18:03.110 --> 00:18:03.120 align:start position:0% ENS but just have it work because your 00:18:03.120 --> 00:18:04.340 align:start position:0% ENS but just have it work because your underlying<00:18:03.480> tool<00:18:03.809> chain 00:18:04.340 --> 00:18:04.350 align:start position:0% underlying tool chain 00:18:04.350 --> 00:18:06.289 align:start position:0% underlying tool chain already<00:18:04.860> has<00:18:05.009> support<00:18:05.399> for<00:18:05.549> resolving<00:18:05.970> ENS 00:18:06.289 --> 00:18:06.299 align:start position:0% already has support for resolving ENS 00:18:06.299 --> 00:18:10.850 align:start position:0% already has support for resolving ENS addresses<00:18:08.450> so<00:18:09.450> want<00:18:09.899> to<00:18:09.990> hear<00:18:10.169> more<00:18:10.350> we<00:18:10.679> have<00:18:10.830> a 00:18:10.850 --> 00:18:10.860 align:start position:0% addresses so want to hear more we have a 00:18:10.860 --> 00:18:13.070 align:start position:0% addresses so want to hear more we have a little<00:18:11.039> more<00:18:11.190> detail<00:18:11.610> if<00:18:12.330> you'd<00:18:12.570> like<00:18:12.750> to<00:18:12.899> see 00:18:13.070 --> 00:18:13.080 align:start position:0% little more detail if you'd like to see 00:18:13.080 --> 00:18:14.749 align:start position:0% little more detail if you'd like to see more<00:18:13.259> about<00:18:13.320> how<00:18:13.769> we're<00:18:13.980> reaching<00:18:14.159> out<00:18:14.460> past 00:18:14.749 --> 00:18:14.759 align:start position:0% more about how we're reaching out past 00:18:14.759 --> 00:18:18.379 align:start position:0% more about how we're reaching out past just<00:18:15.210> a<00:18:15.509> name<00:18:15.929> resolution<00:18:16.139> on<00:18:16.649> aetherium<00:18:17.389> then 00:18:18.379 --> 00:18:18.389 align:start position:0% just a name resolution on aetherium then 00:18:18.389 --> 00:18:20.360 align:start position:0% just a name resolution on aetherium then come<00:18:18.960> see<00:18:19.139> grant<00:18:19.380> these<00:18:19.559> talk<00:18:19.740> tomorrow<00:18:19.950> it's 00:18:20.360 --> 00:18:20.370 align:start position:0% come see grant these talk tomorrow it's 00:18:20.370 --> 00:18:22.340 align:start position:0% come see grant these talk tomorrow it's 935<00:18:21.000> in<00:18:21.240> the<00:18:21.299> convention<00:18:21.750> room<00:18:21.929> and<00:18:22.139> we're 00:18:22.340 --> 00:18:22.350 align:start position:0% 935 in the convention room and we're 00:18:22.350 --> 00:18:23.810 align:start position:0% 935 in the convention room and we're talking<00:18:22.470> about<00:18:22.740> how<00:18:22.889> ENS<00:18:23.309> is<00:18:23.490> taking 00:18:23.810 --> 00:18:23.820 align:start position:0% talking about how ENS is taking 00:18:23.820 --> 00:18:25.279 align:start position:0% talking about how ENS is taking aetherium<00:18:24.179> to<00:18:24.509> the<00:18:24.600> rest<00:18:24.779> of<00:18:24.929> the<00:18:24.990> Internet 00:18:25.279 --> 00:18:25.289 align:start position:0% aetherium to the rest of the Internet 00:18:25.289 --> 00:18:27.350 align:start position:0% aetherium to the rest of the Internet and<00:18:25.860> that's<00:18:26.399> all<00:18:26.580> I<00:18:26.639> have<00:18:26.789> today<00:18:26.909> for<00:18:27.299> you 00:18:27.350 --> 00:18:27.360 align:start position:0% and that's all I have today for you 00:18:27.360 --> 00:18:28.690 align:start position:0% and that's all I have today for you thank<00:18:27.600> you<00:18:27.659> very<00:18:27.779> much 00:18:28.690 --> 00:18:28.700 align:start position:0% thank you very much 00:18:28.700 --> 00:18:30.320 align:start position:0% thank you very much [Applause] 00:18:30.320 --> 00:18:30.330 align:start position:0% [Applause] 00:18:30.330 --> 00:18:40.799 align:start position:0% [Applause] [Music] 00:18:40.799 --> 00:18:40.809 align:start position:0% 00:18:40.809 --> 00:18:42.870 align:start position:0% you