WEBVTT Kind: captions Language: en 00:00:00.030 --> 00:00:03.260 align:start position:0% I'm<00:00:00.840> the<00:00:01.110> UX<00:00:01.319> designer<00:00:01.680> at<00:00:02.040> ENS<00:00:02.730> and<00:00:02.760> we<00:00:03.179> are 00:00:03.260 --> 00:00:03.270 align:start position:0% I'm the UX designer at ENS and we are 00:00:03.270 --> 00:00:05.930 align:start position:0% I'm the UX designer at ENS and we are trying<00:00:03.510> to<00:00:03.629> make<00:00:03.810> everything<00:00:04.620> easier<00:00:05.339> for<00:00:05.700> the 00:00:05.930 --> 00:00:05.940 align:start position:0% trying to make everything easier for the 00:00:05.940 --> 00:00:10.610 align:start position:0% trying to make everything easier for the user<00:00:06.170> and<00:00:07.170> so<00:00:07.710> I'm<00:00:07.890> a<00:00:08.490> bit<00:00:09.210> like<00:00:09.500> doing<00:00:10.500> the 00:00:10.610 --> 00:00:10.620 align:start position:0% user and so I'm a bit like doing the 00:00:10.620 --> 00:00:13.039 align:start position:0% user and so I'm a bit like doing the older<00:00:10.800> social<00:00:11.429> sorry<00:00:11.849> apology<00:00:12.660> for<00:00:12.900> the 00:00:13.039 --> 00:00:13.049 align:start position:0% older social sorry apology for the 00:00:13.049 --> 00:00:15.470 align:start position:0% older social sorry apology for the social<00:00:13.710> media<00:00:13.740> stuff<00:00:14.160> I<00:00:14.549> open<00:00:14.940> at<00:00:15.030> the<00:00:15.150> ENS 00:00:15.470 --> 00:00:15.480 align:start position:0% social media stuff I open at the ENS 00:00:15.480 --> 00:00:18.410 align:start position:0% social media stuff I open at the ENS hackathon<00:00:15.990> and<00:00:16.350> then<00:00:16.770> you<00:00:16.949> know<00:00:17.070> and<00:00:17.369> also<00:00:17.970> I 00:00:18.410 --> 00:00:18.420 align:start position:0% hackathon and then you know and also I 00:00:18.420 --> 00:00:20.029 align:start position:0% hackathon and then you know and also I do<00:00:18.690> actually<00:00:19.140> do<00:00:19.260> a<00:00:19.289> bit<00:00:19.500> of<00:00:19.529> dev<00:00:19.800> work 00:00:20.029 --> 00:00:20.039 align:start position:0% do actually do a bit of dev work 00:00:20.039 --> 00:00:22.429 align:start position:0% do actually do a bit of dev work especially<00:00:20.789> for<00:00:21.210> the<00:00:21.300> DNS<00:00:21.660> integration<00:00:22.260> work 00:00:22.429 --> 00:00:22.439 align:start position:0% especially for the DNS integration work 00:00:22.439 --> 00:00:26.420 align:start position:0% especially for the DNS integration work Nick<00:00:23.400> might<00:00:23.640> have<00:00:23.850> in<00:00:24.449> an<00:00:24.630> explained<00:00:25.430> next 00:00:26.420 --> 00:00:26.430 align:start position:0% Nick might have in an explained next 00:00:26.430 --> 00:00:30.380 align:start position:0% Nick might have in an explained next place<00:00:26.580> yeah<00:00:26.939> so<00:00:28.279> so<00:00:29.279> yeah<00:00:29.460> again<00:00:29.849> as<00:00:30.269> I 00:00:30.380 --> 00:00:30.390 align:start position:0% place yeah so so yeah again as I 00:00:30.390 --> 00:00:32.630 align:start position:0% place yeah so so yeah again as I mentioned<00:00:30.779> it's<00:00:30.900> two<00:00:31.140> parts<00:00:31.320> like<00:00:31.650> how<00:00:31.830> to<00:00:32.340> get 00:00:32.630 --> 00:00:32.640 align:start position:0% mentioned it's two parts like how to get 00:00:32.640 --> 00:00:36.260 align:start position:0% mentioned it's two parts like how to get you<00:00:32.850> this<00:00:33.149> cool<00:00:33.570> ENS<00:00:34.559> thing<00:00:35.370> so<00:00:35.820> that<00:00:35.969> you<00:00:36.090> can 00:00:36.260 --> 00:00:36.270 align:start position:0% you this cool ENS thing so that you can 00:00:36.270 --> 00:00:39.229 align:start position:0% you this cool ENS thing so that you can have<00:00:36.809> the<00:00:36.930> ultimate<00:00:37.050> bragging<00:00:37.860> right<00:00:38.129> like<00:00:38.670> it 00:00:39.229 --> 00:00:39.239 align:start position:0% have the ultimate bragging right like it 00:00:39.239 --> 00:00:41.299 align:start position:0% have the ultimate bragging right like it only<00:00:39.450> happened<00:00:39.899> this<00:00:40.050> year<00:00:40.110> next<00:00:40.559> year<00:00:40.920> we 00:00:41.299 --> 00:00:41.309 align:start position:0% only happened this year next year we 00:00:41.309 --> 00:00:43.459 align:start position:0% only happened this year next year we assume<00:00:41.610> everybody<00:00:41.910> has<00:00:42.090> it<00:00:42.270> so<00:00:42.420> it's<00:00:42.540> not<00:00:42.719> no 00:00:43.459 --> 00:00:43.469 align:start position:0% assume everybody has it so it's not no 00:00:43.469 --> 00:00:45.080 align:start position:0% assume everybody has it so it's not no longer<00:00:43.860> than<00:00:44.010> you<00:00:44.129> know<00:00:44.250> nobility<00:00:44.730> but<00:00:44.940> this 00:00:45.080 --> 00:00:45.090 align:start position:0% longer than you know nobility but this 00:00:45.090 --> 00:00:46.720 align:start position:0% longer than you know nobility but this year<00:00:45.390> you<00:00:45.960> are<00:00:45.989> the<00:00:46.170> cool<00:00:46.379> bunch 00:00:46.720 --> 00:00:46.730 align:start position:0% year you are the cool bunch 00:00:46.730 --> 00:00:47.930 align:start position:0% year you are the cool bunch congratulations 00:00:47.930 --> 00:00:47.940 align:start position:0% congratulations 00:00:47.940 --> 00:00:51.889 align:start position:0% congratulations then<00:00:48.270> once<00:00:48.570> yeah<00:00:48.809> so<00:00:49.079> -<00:00:49.440> Harvey<00:00:49.710> okay<00:00:50.160> so<00:00:50.899> get 00:00:51.889 --> 00:00:51.899 align:start position:0% then once yeah so - Harvey okay so get 00:00:51.899 --> 00:00:56.420 align:start position:0% then once yeah so - Harvey okay so get actor<00:00:52.620> who<00:00:53.129> has<00:00:53.309> no<00:00:53.460> clear<00:00:53.640> awareness<00:00:55.370> okay<00:00:56.370> so 00:00:56.420 --> 00:00:56.430 align:start position:0% actor who has no clear awareness okay so 00:00:56.430 --> 00:00:59.119 align:start position:0% actor who has no clear awareness okay so I<00:00:56.550> don't<00:00:56.940> have<00:00:57.360> to<00:00:57.570> bring<00:00:57.930> Nick<00:00:58.469> to<00:00:58.680> the<00:00:58.859> stage 00:00:59.119 --> 00:00:59.129 align:start position:0% I don't have to bring Nick to the stage 00:00:59.129 --> 00:01:01.729 align:start position:0% I don't have to bring Nick to the stage to<00:00:59.399> go<00:01:00.059> through<00:01:00.270> the<00:01:00.449> state<00:01:00.930> of<00:01:01.079> ENS<00:01:01.469> again 00:01:01.729 --> 00:01:01.739 align:start position:0% to go through the state of ENS again 00:01:01.739 --> 00:01:07.660 align:start position:0% to go through the state of ENS again right<00:01:01.980> so<00:01:02.190> cool<00:01:02.850> so<00:01:03.210> ENS<00:01:03.600> stands<00:01:03.899> for<00:01:06.110> okay 00:01:07.660 --> 00:01:07.670 align:start position:0% right so cool so ENS stands for okay 00:01:07.670 --> 00:01:09.830 align:start position:0% right so cool so ENS stands for okay guys<00:01:08.670> focus 00:01:09.830 --> 00:01:09.840 align:start position:0% guys focus 00:01:09.840 --> 00:01:19.850 align:start position:0% guys focus unis<00:01:10.740> stands<00:01:11.010> for<00:01:13.909> yes<00:01:14.909> stands<00:01:15.180> for<00:01:18.860> service 00:01:19.850 --> 00:01:19.860 align:start position:0% unis stands for yes stands for service 00:01:19.860 --> 00:01:22.789 align:start position:0% unis stands for yes stands for service that<00:01:20.220> is<00:01:20.460> their<00:01:20.729> name<00:01:21.090> service<00:01:21.570> okay<00:01:21.930> so<00:01:21.990> so 00:01:22.789 --> 00:01:22.799 align:start position:0% that is their name service okay so so 00:01:22.799 --> 00:01:26.840 align:start position:0% that is their name service okay so so it's<00:01:23.159> like<00:01:23.250> it<00:01:23.840> like<00:01:24.840> ENS<00:01:25.380> like<00:01:26.310> you<00:01:26.610> know<00:01:26.729> in 00:01:26.840 --> 00:01:26.850 align:start position:0% it's like it like ENS like you know in 00:01:26.850 --> 00:01:28.819 align:start position:0% it's like it like ENS like you know in case<00:01:27.030> of<00:01:27.180> like<00:01:27.509> the<00:01:27.930> compression<00:01:28.380> we<00:01:28.470> make<00:01:28.680> is 00:01:28.819 --> 00:01:28.829 align:start position:0% case of like the compression we make is 00:01:28.829 --> 00:01:30.770 align:start position:0% case of like the compression we make is at<00:01:28.950> the<00:01:29.040> NS<00:01:29.280> right<00:01:29.490> so<00:01:29.670> lucky<00:01:29.909> you<00:01:30.299> have<00:01:30.329> a<00:01:30.479> DNS 00:01:30.770 --> 00:01:30.780 align:start position:0% at the NS right so lucky you have a DNS 00:01:30.780 --> 00:01:33.319 align:start position:0% at the NS right so lucky you have a DNS domain<00:01:30.990> we<00:01:31.650> have<00:01:31.680> also<00:01:32.579> have<00:01:32.700> a<00:01:32.729> DNS<00:01:33.090> domain 00:01:33.319 --> 00:01:33.329 align:start position:0% domain we have also have a DNS domain 00:01:33.329 --> 00:01:36.679 align:start position:0% domain we have also have a DNS domain and<00:01:33.720> also<00:01:34.290> we<00:01:34.470> have<00:01:34.619> a<00:01:34.650> notion<00:01:34.860> of<00:01:35.420> domain<00:01:36.420> and 00:01:36.679 --> 00:01:36.689 align:start position:0% and also we have a notion of domain and 00:01:36.689 --> 00:01:39.380 align:start position:0% and also we have a notion of domain and sub<00:01:36.960> domain<00:01:37.320> it's<00:01:37.920> kind<00:01:38.369> of<00:01:38.520> maps<00:01:38.759> into<00:01:39.240> the 00:01:39.380 --> 00:01:39.390 align:start position:0% sub domain it's kind of maps into the 00:01:39.390 --> 00:01:42.020 align:start position:0% sub domain it's kind of maps into the you<00:01:39.869> know<00:01:39.990> the<00:01:40.350> naming<00:01:41.040> scheme<00:01:41.220> of<00:01:41.520> the<00:01:41.640> US<00:01:41.880> as 00:01:42.020 --> 00:01:42.030 align:start position:0% you know the naming scheme of the US as 00:01:42.030 --> 00:01:44.990 align:start position:0% you know the naming scheme of the US as well<00:01:42.180> for<00:01:42.840> example<00:01:43.229> this<00:01:43.380> domain<00:01:43.890> motto<00:01:44.610> condo 00:01:44.990 --> 00:01:45.000 align:start position:0% well for example this domain motto condo 00:01:45.000 --> 00:01:47.539 align:start position:0% well for example this domain motto condo is<00:01:45.210> this<00:01:45.659> is<00:01:45.780> my<00:01:45.960> East<00:01:46.259> so<00:01:46.439> if<00:01:46.560> you<00:01:46.710> wanna<00:01:46.860> you 00:01:47.539 --> 00:01:47.549 align:start position:0% is this is my East so if you wanna you 00:01:47.549 --> 00:01:54.230 align:start position:0% is this is my East so if you wanna you know<00:01:47.579> like<00:01:48.270> you<00:01:48.420> know<00:01:51.950> ease<00:01:52.950> but<00:01:53.700> at<00:01:53.880> the<00:01:54.030> same 00:01:54.230 --> 00:01:54.240 align:start position:0% know like you know ease but at the same 00:01:54.240 --> 00:01:57.530 align:start position:0% know like you know ease but at the same time<00:01:54.710> yeah<00:01:55.710> I<00:01:55.950> will<00:01:56.250> explain<00:01:56.610> how<00:01:56.820> to<00:01:56.880> get<00:01:57.329> this 00:01:57.530 --> 00:01:57.540 align:start position:0% time yeah I will explain how to get this 00:01:57.540 --> 00:02:00.050 align:start position:0% time yeah I will explain how to get this domain<00:01:58.409> because<00:01:58.770> that's<00:01:58.950> probably<00:01:59.310> people 00:02:00.050 --> 00:02:00.060 align:start position:0% domain because that's probably people 00:02:00.060 --> 00:02:02.929 align:start position:0% domain because that's probably people very<00:02:00.390> keen<00:02:00.630> to<00:02:00.659> you<00:02:00.930> but<00:02:01.460> hotel<00:02:02.460> there<00:02:02.700> is<00:02:02.790> a 00:02:02.929 --> 00:02:02.939 align:start position:0% very keen to you but hotel there is a 00:02:02.939 --> 00:02:04.670 align:start position:0% very keen to you but hotel there is a fast<00:02:03.270> you<00:02:03.570> can't<00:02:03.840> get<00:02:04.049> it<00:02:04.229> today 00:02:04.670 --> 00:02:04.680 align:start position:0% fast you can't get it today 00:02:04.680 --> 00:02:07.760 align:start position:0% fast you can't get it today and<00:02:04.950> I'll<00:02:05.250> explain<00:02:05.640> why<00:02:05.939> so<00:02:06.299> your<00:02:06.719> focus<00:02:07.140> to<00:02:07.170> of 00:02:07.760 --> 00:02:07.770 align:start position:0% and I'll explain why so your focus to of 00:02:07.770 --> 00:02:09.529 align:start position:0% and I'll explain why so your focus to of today<00:02:08.220> will<00:02:08.459> be<00:02:08.610> going<00:02:08.819> to<00:02:09.000> get<00:02:09.239> something 00:02:09.529 --> 00:02:09.539 align:start position:0% today will be going to get something 00:02:09.539 --> 00:02:11.960 align:start position:0% today will be going to get something like<00:02:09.869> a<00:02:09.899> subdomain<00:02:10.800> which<00:02:11.190> is<00:02:11.370> something<00:02:11.670> like 00:02:11.960 --> 00:02:11.970 align:start position:0% like a subdomain which is something like 00:02:11.970 --> 00:02:13.100 align:start position:0% like a subdomain which is something like for<00:02:12.150> example 00:02:13.100 --> 00:02:13.110 align:start position:0% for example 00:02:13.110 --> 00:02:17.000 align:start position:0% for example get<00:02:13.650> coined<00:02:13.920> or<00:02:14.070> eise<00:02:14.780> who<00:02:15.780> does<00:02:16.440> not<00:02:16.710> have<00:02:16.950> a 00:02:17.000 --> 00:02:17.010 align:start position:0% get coined or eise who does not have a 00:02:17.010 --> 00:02:21.500 align:start position:0% get coined or eise who does not have a github<00:02:17.790> account<00:02:19.610> does<00:02:20.610> not<00:02:20.640> have<00:02:21.120> a<00:02:21.150> github 00:02:21.500 --> 00:02:21.510 align:start position:0% github account does not have a github 00:02:21.510 --> 00:02:24.830 align:start position:0% github account does not have a github account<00:02:22.220> okay<00:02:23.220> so<00:02:23.610> everybody<00:02:24.030> could<00:02:24.390> should 00:02:24.830 --> 00:02:24.840 align:start position:0% account okay so everybody could should 00:02:24.840 --> 00:02:29.320 align:start position:0% account okay so everybody could should be<00:02:24.990> able<00:02:25.080> to<00:02:25.290> get<00:02:25.740> that<00:02:27.650> that<00:02:28.650> kind<00:02:28.890> of<00:02:28.950> stuff 00:02:29.320 --> 00:02:29.330 align:start position:0% be able to get that that kind of stuff 00:02:29.330 --> 00:02:31.640 align:start position:0% be able to get that that kind of stuff yeah<00:02:30.360> next<00:02:31.050> please 00:02:31.640 --> 00:02:31.650 align:start position:0% yeah next please 00:02:31.650 --> 00:02:36.590 align:start position:0% yeah next please so<00:02:33.080> that<00:02:34.080> domain<00:02:34.500> for<00:02:35.280> the<00:02:35.400> door<00:02:35.610> if<00:02:35.760> address 00:02:36.590 --> 00:02:36.600 align:start position:0% so that domain for the door if address 00:02:36.600 --> 00:02:38.750 align:start position:0% so that domain for the door if address is<00:02:36.840> i<00:02:37.140> think<00:02:37.710> nick<00:02:37.860> already<00:02:38.040> mentioned<00:02:38.700> the 00:02:38.750 --> 00:02:38.760 align:start position:0% is i think nick already mentioned the 00:02:38.760 --> 00:02:41.390 align:start position:0% is i think nick already mentioned the state<00:02:38.970> of<00:02:39.120> is<00:02:39.209> like<00:02:39.450> a<00:02:39.510> we<00:02:39.810> go<00:02:40.140> through<00:02:40.440> the<00:02:40.709> how 00:02:41.390 --> 00:02:41.400 align:start position:0% state of is like a we go through the how 00:02:41.400 --> 00:02:43.790 align:start position:0% state of is like a we go through the how many<00:02:41.550> days<00:02:41.700> seven<00:02:42.060> days<00:02:42.090> seven<00:02:42.660> seven<00:02:43.500> days<00:02:43.650> of 00:02:43.790 --> 00:02:43.800 align:start position:0% many days seven days seven seven days of 00:02:43.800 --> 00:02:49.250 align:start position:0% many days seven days seven seven days of auction<00:02:44.220> process<00:02:44.640> which<00:02:47.630> so<00:02:48.630> the<00:02:48.930> auction<00:02:49.170> is 00:02:49.250 --> 00:02:49.260 align:start position:0% auction process which so the auction is 00:02:49.260 --> 00:02:52.550 align:start position:0% auction process which so the auction is very<00:02:49.470> complicated<00:02:49.830> and<00:02:50.570> make<00:02:51.570> said<00:02:51.930> luckily 00:02:52.550 --> 00:02:52.560 align:start position:0% very complicated and make said luckily 00:02:52.560 --> 00:02:55.220 align:start position:0% very complicated and make said luckily that<00:02:52.800> we're<00:02:53.130> going<00:02:53.280> to<00:02:53.400> get<00:02:53.580> rid<00:02:53.790> but<00:02:54.030> today<00:02:54.510> to 00:02:55.220 --> 00:02:55.230 align:start position:0% that we're going to get rid but today to 00:02:55.230 --> 00:02:58.550 align:start position:0% that we're going to get rid but today to register<00:02:55.550> you<00:02:56.580> it's<00:02:57.209> a<00:02:57.510> commit<00:02:58.050> and<00:02:58.260> revealed 00:02:58.550 --> 00:02:58.560 align:start position:0% register you it's a commit and revealed 00:02:58.560 --> 00:03:00.890 align:start position:0% register you it's a commit and revealed pattern<00:02:59.040> who<00:02:59.310> doesn't<00:02:59.970> know<00:03:00.180> what<00:03:00.450> commit<00:03:00.750> and 00:03:00.890 --> 00:03:00.900 align:start position:0% pattern who doesn't know what commit and 00:03:00.900 --> 00:03:04.880 align:start position:0% pattern who doesn't know what commit and reveal<00:03:01.140> is<00:03:02.120> okay<00:03:03.120> so<00:03:03.180> it<00:03:03.780> it's<00:03:04.410> one<00:03:04.620> of<00:03:04.739> those 00:03:04.880 --> 00:03:04.890 align:start position:0% reveal is okay so it it's one of those 00:03:04.890 --> 00:03:07.100 align:start position:0% reveal is okay so it it's one of those patterns<00:03:05.130> where<00:03:05.610> you<00:03:05.790> are<00:03:05.970> bidding<00:03:06.750> on<00:03:07.020> a 00:03:07.100 --> 00:03:07.110 align:start position:0% patterns where you are bidding on a 00:03:07.110 --> 00:03:11.800 align:start position:0% patterns where you are bidding on a domain<00:03:07.950> but<00:03:08.940> hidden<00:03:09.930> so<00:03:10.709> your<00:03:10.920> bid<00:03:11.160> is<00:03:11.340> hidden 00:03:11.800 --> 00:03:11.810 align:start position:0% domain but hidden so your bid is hidden 00:03:11.810 --> 00:03:13.729 align:start position:0% domain but hidden so your bid is hidden until<00:03:12.810> you<00:03:13.080> reveal<00:03:13.530> it 00:03:13.729 --> 00:03:13.739 align:start position:0% until you reveal it 00:03:13.739 --> 00:03:16.490 align:start position:0% until you reveal it three<00:03:14.160> days<00:03:14.430> later<00:03:14.700> later<00:03:15.330> and<00:03:15.750> so<00:03:16.020> during<00:03:16.380> the 00:03:16.490 --> 00:03:16.500 align:start position:0% three days later later and so during the 00:03:16.500 --> 00:03:19.130 align:start position:0% three days later later and so during the first<00:03:16.530> three<00:03:17.100> days<00:03:17.459> okay<00:03:18.269> the<00:03:18.420> bidding<00:03:18.750> period 00:03:19.130 --> 00:03:19.140 align:start position:0% first three days okay the bidding period 00:03:19.140 --> 00:03:23.240 align:start position:0% first three days okay the bidding period 72<00:03:19.950> hours<00:03:20.370> anybody<00:03:21.299> could<00:03:21.660> bid<00:03:22.049> on<00:03:22.080> that<00:03:22.739> name 00:03:23.240 --> 00:03:23.250 align:start position:0% 72 hours anybody could bid on that name 00:03:23.250 --> 00:03:26.479 align:start position:0% 72 hours anybody could bid on that name okay<00:03:23.940> your<00:03:24.540> name<00:03:24.810> is<00:03:25.080> hidden<00:03:25.769> if<00:03:25.950> it's<00:03:26.370> a 00:03:26.479 --> 00:03:26.489 align:start position:0% okay your name is hidden if it's a 00:03:26.489 --> 00:03:28.699 align:start position:0% okay your name is hidden if it's a complicated<00:03:27.120> name<00:03:27.480> nobody<00:03:27.780> will<00:03:28.140> ever<00:03:28.380> know 00:03:28.699 --> 00:03:28.709 align:start position:0% complicated name nobody will ever know 00:03:28.709 --> 00:03:32.030 align:start position:0% complicated name nobody will ever know but<00:03:29.580> if<00:03:29.700> it's<00:03:29.880> a<00:03:30.060> it's<00:03:30.870> a<00:03:31.049> name<00:03:31.230> that<00:03:31.440> also<00:03:31.709> has 00:03:32.030 --> 00:03:32.040 align:start position:0% but if it's a it's a name that also has 00:03:32.040 --> 00:03:35.870 align:start position:0% but if it's a it's a name that also has a.com<00:03:32.459> or<00:03:33.090> a<00:03:33.120> famous<00:03:34.049> Tod<00:03:34.860> it<00:03:35.130> can<00:03:35.370> be<00:03:35.549> guessed 00:03:35.870 --> 00:03:35.880 align:start position:0% a.com or a famous Tod it can be guessed 00:03:35.880 --> 00:03:39.170 align:start position:0% a.com or a famous Tod it can be guessed and<00:03:36.239> so<00:03:36.890> somebody<00:03:37.890> else<00:03:37.950> could<00:03:38.370> be<00:03:38.430> bidding<00:03:38.880> on 00:03:39.170 --> 00:03:39.180 align:start position:0% and so somebody else could be bidding on 00:03:39.180 --> 00:03:41.810 align:start position:0% and so somebody else could be bidding on your<00:03:39.630> domain<00:03:40.049> you<00:03:40.739> are<00:03:40.769> bidding<00:03:41.340> different 00:03:41.810 --> 00:03:41.820 align:start position:0% your domain you are bidding different 00:03:41.820 --> 00:03:46.610 align:start position:0% your domain you are bidding different amounts<00:03:42.510> and<00:03:43.850> in<00:03:44.850> the<00:03:45.209> after<00:03:46.110> three<00:03:46.350> days<00:03:46.590> you 00:03:46.610 --> 00:03:46.620 align:start position:0% amounts and in the after three days you 00:03:46.620 --> 00:03:49.100 align:start position:0% amounts and in the after three days you have<00:03:47.100> this<00:03:47.250> reveal<00:03:47.820> period<00:03:48.390> in<00:03:48.570> which<00:03:48.600> you<00:03:48.959> are 00:03:49.100 --> 00:03:49.110 align:start position:0% have this reveal period in which you are 00:03:49.110 --> 00:03:52.850 align:start position:0% have this reveal period in which you are you<00:03:49.440> should<00:03:49.860> reveal<00:03:50.640> your<00:03:51.000> bid<00:03:51.299> okay<00:03:51.930> and<00:03:52.140> the 00:03:52.850 --> 00:03:52.860 align:start position:0% you should reveal your bid okay and the 00:03:52.860 --> 00:03:55.310 align:start position:0% you should reveal your bid okay and the winner<00:03:53.130> will<00:03:53.549> be<00:03:53.580> the<00:03:54.150> one<00:03:54.570> with<00:03:54.840> the<00:03:54.870> highest 00:03:55.310 --> 00:03:55.320 align:start position:0% winner will be the one with the highest 00:03:55.320 --> 00:03:58.610 align:start position:0% winner will be the one with the highest bid<00:03:55.860> but<00:03:56.610> he<00:03:56.820> will<00:03:57.000> only<00:03:57.299> pay<00:03:57.750> the<00:03:57.780> second 00:03:58.610 --> 00:03:58.620 align:start position:0% bid but he will only pay the second 00:03:58.620 --> 00:04:01.460 align:start position:0% bid but he will only pay the second highest<00:03:59.480> bid<00:04:00.480> so<00:04:00.690> he<00:04:00.930> will<00:04:01.080> not<00:04:01.260> pay<00:04:01.440> the 00:04:01.460 --> 00:04:01.470 align:start position:0% highest bid so he will not pay the 00:04:01.470 --> 00:04:03.920 align:start position:0% highest bid so he will not pay the highest<00:04:01.890> price<00:04:02.310> he<00:04:02.519> tried<00:04:02.850> to<00:04:02.970> bid<00:04:03.150> and<00:04:03.630> this 00:04:03.920 --> 00:04:03.930 align:start position:0% highest price he tried to bid and this 00:04:03.930 --> 00:04:06.170 align:start position:0% highest price he tried to bid and this mechanism<00:04:04.290> was<00:04:04.769> made<00:04:05.040> so<00:04:05.430> that<00:04:05.670> there<00:04:05.880> are<00:04:06.000> no 00:04:06.170 --> 00:04:06.180 align:start position:0% mechanism was made so that there are no 00:04:06.180 --> 00:04:09.830 align:start position:0% mechanism was made so that there are no squatters<00:04:06.870> who<00:04:07.940> collect<00:04:08.940> all<00:04:09.390> the<00:04:09.630> names 00:04:09.830 --> 00:04:09.840 align:start position:0% squatters who collect all the names 00:04:09.840 --> 00:04:13.250 align:start position:0% squatters who collect all the names while<00:04:10.560> we<00:04:10.799> are<00:04:10.920> still<00:04:11.190> coming<00:04:12.120> out<00:04:12.360> with<00:04:12.750> with 00:04:13.250 --> 00:04:13.260 align:start position:0% while we are still coming out with with 00:04:13.260 --> 00:04:16.310 align:start position:0% while we are still coming out with with ens<00:04:13.709> and<00:04:14.280> an<00:04:15.239> important<00:04:15.600> limitation<00:04:15.870> today 00:04:16.310 --> 00:04:16.320 align:start position:0% ens and an important limitation today 00:04:16.320 --> 00:04:19.400 align:start position:0% ens and an important limitation today you<00:04:16.380> can<00:04:16.709> buy<00:04:17.130> only<00:04:17.780> domains<00:04:18.780> that<00:04:18.959> are<00:04:19.019> longer 00:04:19.400 --> 00:04:19.410 align:start position:0% you can buy only domains that are longer 00:04:19.410 --> 00:04:23.839 align:start position:0% you can buy only domains that are longer than<00:04:19.680> seven<00:04:20.280> characters<00:04:21.000> okay<00:04:21.690> and<00:04:22.370> after<00:04:23.370> the 00:04:23.839 --> 00:04:23.849 align:start position:0% than seven characters okay and after the 00:04:23.849 --> 00:04:25.900 align:start position:0% than seven characters okay and after the reveal<00:04:24.690> period<00:04:25.169> so<00:04:25.440> there<00:04:25.740> is 00:04:25.900 --> 00:04:25.910 align:start position:0% reveal period so there is 00:04:25.910 --> 00:04:28.420 align:start position:0% reveal period so there is time<00:04:26.240> for<00:04:27.050> 48<00:04:27.650> hours<00:04:27.800> in<00:04:28.070> which<00:04:28.220> you<00:04:28.370> should 00:04:28.420 --> 00:04:28.430 align:start position:0% time for 48 hours in which you should 00:04:28.430 --> 00:04:32.710 align:start position:0% time for 48 hours in which you should you<00:04:29.390> actually<00:04:29.840> you<00:04:29.960> must<00:04:30.320> submit<00:04:30.830> your<00:04:31.720> reveal 00:04:32.710 --> 00:04:32.720 align:start position:0% you actually you must submit your reveal 00:04:32.720 --> 00:04:36.310 align:start position:0% you actually you must submit your reveal otherwise<00:04:33.230> you<00:04:33.410> lose<00:04:33.530> the<00:04:33.680> money<00:04:34.960> someone<00:04:35.960> of 00:04:36.310 --> 00:04:36.320 align:start position:0% otherwise you lose the money someone of 00:04:36.320 --> 00:04:40.060 align:start position:0% otherwise you lose the money someone of the<00:04:36.530> bidders<00:04:36.830> wins<00:04:37.340> and<00:04:38.110> after<00:04:39.110> that<00:04:39.320> the 00:04:40.060 --> 00:04:40.070 align:start position:0% the bidders wins and after that the 00:04:40.070 --> 00:04:43.030 align:start position:0% the bidders wins and after that the winner<00:04:40.340> should<00:04:40.760> finalize<00:04:41.540> the<00:04:41.840> auction<00:04:42.200> thank 00:04:43.030 --> 00:04:43.040 align:start position:0% winner should finalize the auction thank 00:04:43.040 --> 00:04:53.590 align:start position:0% winner should finalize the auction thank you<00:04:43.130> very<00:04:43.280> much<00:04:49.450> now<00:04:50.450> minimum<00:04:51.170> is<00:04:51.320> 0.01<00:04:52.310> so<00:04:53.270> and 00:04:53.590 --> 00:04:53.600 align:start position:0% you very much now minimum is 0.01 so and 00:04:53.600 --> 00:04:56.260 align:start position:0% you very much now minimum is 0.01 so and also<00:04:53.930> it's<00:04:54.050> a<00:04:54.200> deport<00:04:54.860> yeah<00:04:55.580> you<00:04:55.640> keep<00:04:56.060> it 00:04:56.260 --> 00:04:56.270 align:start position:0% also it's a deport yeah you keep it 00:04:56.270 --> 00:04:58.630 align:start position:0% also it's a deport yeah you keep it locked<00:04:56.600> so<00:04:57.230> when<00:04:57.410> you<00:04:57.560> release<00:04:58.100> it<00:04:58.280> you<00:04:58.340> get 00:04:58.630 --> 00:04:58.640 align:start position:0% locked so when you release it you get 00:04:58.640 --> 00:05:02.830 align:start position:0% locked so when you release it you get either<00:04:58.940> back<00:04:59.210> so<00:04:59.750> it's<00:04:59.990> not<00:05:00.140> consumed<00:05:01.840> but 00:05:02.830 --> 00:05:02.840 align:start position:0% either back so it's not consumed but 00:05:02.840 --> 00:05:06.340 align:start position:0% either back so it's not consumed but we'll<00:05:03.050> try<00:05:03.350> to<00:05:03.470> go<00:05:03.800> this<00:05:04.190> one<00:05:04.460> quick<00:05:05.350> really 00:05:06.340 --> 00:05:06.350 align:start position:0% we'll try to go this one quick really 00:05:06.350 --> 00:05:08.590 align:start position:0% we'll try to go this one quick really quickly<00:05:06.830> because<00:05:07.010> again<00:05:08.000> Nick<00:05:08.450> already 00:05:08.590 --> 00:05:08.600 align:start position:0% quickly because again Nick already 00:05:08.600 --> 00:05:10.210 align:start position:0% quickly because again Nick already mentioned<00:05:09.170> that<00:05:09.200> we<00:05:09.290> are<00:05:09.590> going<00:05:09.770> to<00:05:09.860> get<00:05:10.070> rid 00:05:10.210 --> 00:05:10.220 align:start position:0% mentioned that we are going to get rid 00:05:10.220 --> 00:05:13.090 align:start position:0% mentioned that we are going to get rid of<00:05:10.250> the<00:05:10.570> auction<00:05:11.570> at<00:05:11.690> some<00:05:11.900> point<00:05:12.170> but<00:05:12.980> like 00:05:13.090 --> 00:05:13.100 align:start position:0% of the auction at some point but like 00:05:13.100 --> 00:05:15.820 align:start position:0% of the auction at some point but like this<00:05:13.340> is<00:05:13.430> just<00:05:13.700> for<00:05:13.850> the<00:05:14.140> you<00:05:15.140> know<00:05:15.290> brave 00:05:15.820 --> 00:05:15.830 align:start position:0% this is just for the you know brave 00:05:15.830 --> 00:05:18.580 align:start position:0% this is just for the you know brave people<00:05:16.130> who<00:05:16.490> don't<00:05:17.330> mind<00:05:17.570> going<00:05:17.780> for<00:05:18.050> the<00:05:18.230> this 00:05:18.580 --> 00:05:18.590 align:start position:0% people who don't mind going for the this 00:05:18.590 --> 00:05:24.490 align:start position:0% people who don't mind going for the this process<00:05:19.280> and<00:05:20.060> yep<00:05:21.080> so<00:05:21.760> again<00:05:22.760> auction<00:05:23.720> process 00:05:24.490 --> 00:05:24.500 align:start position:0% process and yep so again auction process 00:05:24.500 --> 00:05:27.010 align:start position:0% process and yep so again auction process is<00:05:24.620> something<00:05:24.830> we<00:05:25.070> couldn't<00:05:25.580> we<00:05:26.540> she<00:05:26.780> haven't 00:05:27.010 --> 00:05:27.020 align:start position:0% is something we couldn't we she haven't 00:05:27.020 --> 00:05:28.990 align:start position:0% is something we couldn't we she haven't put<00:05:27.170> into<00:05:27.440> the<00:05:27.680> new<00:05:27.860> unis<00:05:28.400> manager<00:05:28.790> so 00:05:28.990 --> 00:05:29.000 align:start position:0% put into the new unis manager so 00:05:29.000 --> 00:05:31.060 align:start position:0% put into the new unis manager so currently<00:05:29.360> there's<00:05:29.990> a<00:05:30.050> couple<00:05:30.200> option<00:05:30.620> wines 00:05:31.060 --> 00:05:31.070 align:start position:0% currently there's a couple option wines 00:05:31.070 --> 00:05:34.270 align:start position:0% currently there's a couple option wines go<00:05:31.340> to<00:05:31.400> the<00:05:31.640> Registrar<00:05:32.150> UNESCO<00:05:32.900> domains<00:05:33.290> to<00:05:34.100> go 00:05:34.270 --> 00:05:34.280 align:start position:0% go to the Registrar UNESCO domains to go 00:05:34.280 --> 00:05:36.820 align:start position:0% go to the Registrar UNESCO domains to go through<00:05:34.550> it<00:05:34.730> there's<00:05:35.330> a<00:05:35.420> huge<00:05:35.830> duplication 00:05:36.820 --> 00:05:36.830 align:start position:0% through it there's a huge duplication 00:05:36.830 --> 00:05:38.140 align:start position:0% through it there's a huge duplication warning<00:05:37.130> comes<00:05:37.340> out<00:05:37.550> and<00:05:37.700> that<00:05:37.850> there<00:05:38.000> might 00:05:38.140 --> 00:05:38.150 align:start position:0% warning comes out and that there might 00:05:38.150 --> 00:05:40.030 align:start position:0% warning comes out and that there might be<00:05:38.210> bit<00:05:38.450> of<00:05:38.540> bugs<00:05:38.780> so<00:05:38.990> like<00:05:39.140> again<00:05:39.500> for<00:05:39.920> the 00:05:40.030 --> 00:05:40.040 align:start position:0% be bit of bugs so like again for the 00:05:40.040 --> 00:05:42.880 align:start position:0% be bit of bugs so like again for the Braveheart<00:05:40.640> and<00:05:40.910> also<00:05:41.690> some<00:05:42.200> sort<00:05:42.440> party<00:05:42.770> like 00:05:42.880 --> 00:05:42.890 align:start position:0% Braveheart and also some sort party like 00:05:42.890 --> 00:05:44.800 align:start position:0% Braveheart and also some sort party like my<00:05:43.130> crypto<00:05:43.610> my<00:05:43.850> ether-wall<00:05:44.180> there<00:05:44.450> and<00:05:44.660> then 00:05:44.800 --> 00:05:44.810 align:start position:0% my crypto my ether-wall there and then 00:05:44.810 --> 00:05:46.870 align:start position:0% my crypto my ether-wall there and then there<00:05:45.350> might<00:05:45.500> be<00:05:45.530> couple<00:05:45.830> more<00:05:46.040> they<00:05:46.520> do<00:05:46.610> have 00:05:46.870 --> 00:05:46.880 align:start position:0% there might be couple more they do have 00:05:46.880 --> 00:05:48.490 align:start position:0% there might be couple more they do have some<00:05:47.060> similar<00:05:47.450> way<00:05:47.660> of<00:05:47.720> our<00:05:47.990> auction<00:05:48.320> process 00:05:48.490 --> 00:05:48.500 align:start position:0% some similar way of our auction process 00:05:48.500 --> 00:05:51.580 align:start position:0% some similar way of our auction process so<00:05:49.010> if<00:05:49.220> you<00:05:49.340> want<00:05:49.520> to<00:05:49.550> go<00:05:49.669> that<00:05:50.330> route<00:05:50.540> you<00:05:50.840> can 00:05:51.580 --> 00:05:51.590 align:start position:0% so if you want to go that route you can 00:05:51.590 --> 00:05:55.860 align:start position:0% so if you want to go that route you can next<00:05:52.130> please<00:05:52.340> and<00:05:53.320> yeah<00:05:54.320> so<00:05:54.590> is<00:05:55.460> this<00:05:55.610> like 00:05:55.860 --> 00:05:55.870 align:start position:0% next please and yeah so is this like 00:05:55.870 --> 00:05:58.240 align:start position:0% next please and yeah so is this like thing<00:05:56.870> you<00:05:57.470> already<00:05:57.590> can't<00:05:57.890> explain<00:05:58.190> that 00:05:58.240 --> 00:05:58.250 align:start position:0% thing you already can't explain that 00:05:58.250 --> 00:06:00.640 align:start position:0% thing you already can't explain that yeah<00:05:58.669> during<00:05:58.880> bidding<00:05:59.419> process<00:06:00.169> he<00:06:00.290> says<00:06:00.530> like 00:06:00.640 --> 00:06:00.650 align:start position:0% yeah during bidding process he says like 00:06:00.650 --> 00:06:02.650 align:start position:0% yeah during bidding process he says like how<00:06:00.860> many<00:06:01.010> hours<00:06:01.669> you<00:06:01.940> left<00:06:02.150> and<00:06:02.390> all<00:06:02.540> that 00:06:02.650 --> 00:06:02.660 align:start position:0% how many hours you left and all that 00:06:02.660 --> 00:06:05.230 align:start position:0% how many hours you left and all that stuff<00:06:02.870> yeah<00:06:03.860> this<00:06:04.040> has<00:06:04.160> been<00:06:04.190> interface<00:06:05.090> of 00:06:05.230 --> 00:06:05.240 align:start position:0% stuff yeah this has been interface of 00:06:05.240 --> 00:06:07.180 align:start position:0% stuff yeah this has been interface of the<00:06:05.360> new<00:06:05.570> manager<00:06:06.260> or<00:06:06.410> part<00:06:06.710> of<00:06:06.830> it<00:06:06.980> we're 00:06:07.180 --> 00:06:07.190 align:start position:0% the new manager or part of it we're 00:06:07.190 --> 00:06:08.590 align:start position:0% the new manager or part of it we're still<00:06:07.460> working<00:06:08.270> on<00:06:08.419> it 00:06:08.590 --> 00:06:08.600 align:start position:0% still working on it 00:06:08.600 --> 00:06:13.690 align:start position:0% still working on it and<00:06:09.520> this<00:06:10.520> process<00:06:11.950> shows<00:06:12.950> for<00:06:13.220> example<00:06:13.250> that 00:06:13.690 --> 00:06:13.700 align:start position:0% and this process shows for example that 00:06:13.700 --> 00:06:16.270 align:start position:0% and this process shows for example that this<00:06:13.880> domain<00:06:14.240> Visa<00:06:14.690> debit<00:06:15.020> card<00:06:15.260> is<00:06:15.440> inside<00:06:16.100> of 00:06:16.270 --> 00:06:16.280 align:start position:0% this domain Visa debit card is inside of 00:06:16.280 --> 00:06:18.159 align:start position:0% this domain Visa debit card is inside of the<00:06:16.400> bidding<00:06:16.580> period<00:06:17.030> and<00:06:17.300> so<00:06:17.480> anybody<00:06:17.810> even 00:06:18.159 --> 00:06:18.169 align:start position:0% the bidding period and so anybody even 00:06:18.169 --> 00:06:20.500 align:start position:0% the bidding period and so anybody even you<00:06:18.440> you<00:06:18.650> could<00:06:18.890> bid<00:06:19.280> for<00:06:19.700> for<00:06:20.240> this<00:06:20.330> domain 00:06:20.500 --> 00:06:20.510 align:start position:0% you you could bid for for this domain 00:06:20.510 --> 00:06:23.040 align:start position:0% you you could bid for for this domain this<00:06:21.140> is<00:06:21.200> a<00:06:21.350> very<00:06:21.680> complicated<00:06:22.070> process 00:06:23.040 --> 00:06:23.050 align:start position:0% this is a very complicated process 00:06:23.050 --> 00:06:25.630 align:start position:0% this is a very complicated process everybody<00:06:24.050> or<00:06:24.260> almost<00:06:24.620> everybody<00:06:25.040> has<00:06:25.430> had 00:06:25.630 --> 00:06:25.640 align:start position:0% everybody or almost everybody has had 00:06:25.640 --> 00:06:27.970 align:start position:0% everybody or almost everybody has had problems<00:06:26.270> with<00:06:26.419> this<00:06:26.570> lost<00:06:26.990> money<00:06:27.230> forgot<00:06:27.830> to 00:06:27.970 --> 00:06:27.980 align:start position:0% problems with this lost money forgot to 00:06:27.980 --> 00:06:30.909 align:start position:0% problems with this lost money forgot to reveal<00:06:28.930> forgot<00:06:29.930> to<00:06:30.110> bid 00:06:30.909 --> 00:06:30.919 align:start position:0% reveal forgot to bid 00:06:30.919 --> 00:06:32.409 align:start position:0% reveal forgot to bid maybe<00:06:31.130> they<00:06:31.340> open<00:06:31.700> the<00:06:31.790> auction<00:06:32.060> they<00:06:32.150> didn't 00:06:32.409 --> 00:06:32.419 align:start position:0% maybe they open the auction they didn't 00:06:32.419 --> 00:06:35.350 align:start position:0% maybe they open the auction they didn't it<00:06:33.169> so<00:06:33.380> it's<00:06:33.530> a<00:06:33.620> complicated<00:06:34.100> new<00:06:34.400> concept 00:06:35.350 --> 00:06:35.360 align:start position:0% it so it's a complicated new concept 00:06:35.360 --> 00:06:36.520 align:start position:0% it so it's a complicated new concept that<00:06:35.479> a<00:06:35.510> lot<00:06:35.750> of<00:06:35.780> people<00:06:36.110> have<00:06:36.229> made<00:06:36.410> mistakes 00:06:36.520 --> 00:06:36.530 align:start position:0% that a lot of people have made mistakes 00:06:36.530 --> 00:06:39.750 align:start position:0% that a lot of people have made mistakes so<00:06:37.430> if<00:06:37.940> you<00:06:38.240> have<00:06:38.450> problems<00:06:39.200> either 00:06:39.750 --> 00:06:39.760 align:start position:0% so if you have problems either 00:06:39.760 --> 00:06:41.760 align:start position:0% so if you have problems either come<00:06:39.970> talk<00:06:40.180> to<00:06:40.210> us<00:06:40.450> or<00:06:40.750> follow<00:06:41.200> through<00:06:41.530> the 00:06:41.760 --> 00:06:41.770 align:start position:0% come talk to us or follow through the 00:06:41.770 --> 00:06:43.110 align:start position:0% come talk to us or follow through the instructions<00:06:42.250> very<00:06:42.340> well<00:06:42.550> if<00:06:42.820> you<00:06:42.880> want<00:06:43.060> to 00:06:43.110 --> 00:06:43.120 align:start position:0% instructions very well if you want to 00:06:43.120 --> 00:06:44.820 align:start position:0% instructions very well if you want to buy<00:06:43.270> now<00:06:43.480> but<00:06:43.720> Mikoto<00:06:44.170> is<00:06:44.260> going<00:06:44.410> to<00:06:44.500> show<00:06:44.680> us 00:06:44.820 --> 00:06:44.830 align:start position:0% buy now but Mikoto is going to show us 00:06:44.830 --> 00:06:49.380 align:start position:0% buy now but Mikoto is going to show us simpler<00:06:45.280> version<00:06:45.640> today<00:06:47.850> this<00:06:48.850> is<00:06:49.000> the<00:06:49.090> reveal 00:06:49.380 --> 00:06:49.390 align:start position:0% simpler version today this is the reveal 00:06:49.390 --> 00:06:50.760 align:start position:0% simpler version today this is the reveal period<00:06:49.870> again 00:06:50.760 --> 00:06:50.770 align:start position:0% period again 00:06:50.770 --> 00:06:54.930 align:start position:0% period again it<00:06:51.010> moved<00:06:51.250> from<00:06:51.430> bidding<00:06:52.210> to<00:06:52.480> reveal<00:06:53.940> and 00:06:54.930 --> 00:06:54.940 align:start position:0% it moved from bidding to reveal and 00:06:54.940 --> 00:06:57.840 align:start position:0% it moved from bidding to reveal and there's<00:06:55.600> another<00:06:55.900> way<00:06:56.230> of<00:06:56.530> getting<00:06:56.800> so<00:06:57.130> that 00:06:57.840 --> 00:06:57.850 align:start position:0% there's another way of getting so that 00:06:57.850 --> 00:07:01.170 align:start position:0% there's another way of getting so that DNS<00:06:58.330> integration<00:06:59.230> that<00:06:59.440> like<00:07:00.070> people<00:07:00.580> kind<00:07:01.030> of 00:07:01.170 --> 00:07:01.180 align:start position:0% DNS integration that like people kind of 00:07:01.180 --> 00:07:04.230 align:start position:0% DNS integration that like people kind of already<00:07:01.510> associate<00:07:01.960> yen<00:07:02.230> SS<00:07:02.530> da<00:07:02.770> e<00:07:02.980> th<00:07:03.370> address 00:07:04.230 --> 00:07:04.240 align:start position:0% already associate yen SS da e th address 00:07:04.240 --> 00:07:06.270 align:start position:0% already associate yen SS da e th address but<00:07:04.720> that's<00:07:04.960> not<00:07:05.260> necessarily<00:07:05.620> the<00:07:05.710> case<00:07:05.770> that 00:07:06.270 --> 00:07:06.280 align:start position:0% but that's not necessarily the case that 00:07:06.280 --> 00:07:07.890 align:start position:0% but that's not necessarily the case that like<00:07:06.490> a<00:07:06.520> that's<00:07:07.210> something<00:07:07.570> in<00:07:07.690> like<00:07:07.780> I've 00:07:07.890 --> 00:07:07.900 align:start position:0% like a that's something in like I've 00:07:07.900 --> 00:07:10.350 align:start position:0% like a that's something in like I've also<00:07:08.230> worked<00:07:08.500> with<00:07:08.680> Nick<00:07:09.070> for<00:07:09.670> the<00:07:09.760> last<00:07:09.970> six 00:07:10.350 --> 00:07:10.360 align:start position:0% also worked with Nick for the last six 00:07:10.360 --> 00:07:13.820 align:start position:0% also worked with Nick for the last six months<00:07:10.470> like<00:07:11.470> basically<00:07:12.070> if<00:07:12.310> you<00:07:12.610> own<00:07:12.880> domains 00:07:13.820 --> 00:07:13.830 align:start position:0% months like basically if you own domains 00:07:13.830 --> 00:07:16.200 align:start position:0% months like basically if you own domains like<00:07:14.830> for<00:07:15.010> example<00:07:15.070> I<00:07:15.430> have<00:07:15.580> a<00:07:15.610> motto<00:07:15.790> control 00:07:16.200 --> 00:07:16.210 align:start position:0% like for example I have a motto control 00:07:16.210 --> 00:07:20.880 align:start position:0% like for example I have a motto control XYZ<00:07:16.840> and<00:07:17.110> if<00:07:17.860> you<00:07:18.130> can<00:07:18.700> prove<00:07:19.090> you<00:07:19.360> can<00:07:19.720> you<00:07:20.650> put 00:07:20.880 --> 00:07:20.890 align:start position:0% XYZ and if you can prove you can you put 00:07:20.890 --> 00:07:23.610 align:start position:0% XYZ and if you can prove you can you put a<00:07:20.970> sub-domain<00:07:21.970> record<00:07:22.480> like<00:07:22.630> underscore 00:07:23.610 --> 00:07:23.620 align:start position:0% a sub-domain record like underscore 00:07:23.620 --> 00:07:29.760 align:start position:0% a sub-domain record like underscore UNESCO<00:07:24.310> my<00:07:24.790> token<00:07:25.180> dot<00:07:26.010> X<00:07:27.010> Y<00:07:27.310> Z<00:07:27.640> and<00:07:27.990> DNS<00:07:28.990> you 00:07:29.760 --> 00:07:29.770 align:start position:0% UNESCO my token dot X Y Z and DNS you 00:07:29.770 --> 00:07:31.800 align:start position:0% UNESCO my token dot X Y Z and DNS you can<00:07:29.950> put<00:07:30.160> not<00:07:30.400> just<00:07:30.610> IP<00:07:31.000> but<00:07:31.240> you<00:07:31.330> can<00:07:31.480> put<00:07:31.630> text 00:07:31.800 --> 00:07:31.810 align:start position:0% can put not just IP but you can put text 00:07:31.810 --> 00:07:33.840 align:start position:0% can put not just IP but you can put text record<00:07:32.200> so<00:07:32.590> if<00:07:32.650> you<00:07:32.770> put<00:07:32.980> the<00:07:33.040> same<00:07:33.340> address 00:07:33.840 --> 00:07:33.850 align:start position:0% record so if you put the same address 00:07:33.850 --> 00:07:36.360 align:start position:0% record so if you put the same address and<00:07:34.120> there's<00:07:34.720> ways<00:07:35.050> to<00:07:35.260> kind<00:07:35.380> of<00:07:35.500> prove<00:07:35.830> that 00:07:36.360 --> 00:07:36.370 align:start position:0% and there's ways to kind of prove that 00:07:36.370 --> 00:07:38.970 align:start position:0% and there's ways to kind of prove that that's<00:07:37.270> correct<00:07:37.510> like<00:07:38.050> anyone<00:07:38.410> can<00:07:38.530> do<00:07:38.710> it<00:07:38.890> and 00:07:38.970 --> 00:07:38.980 align:start position:0% that's correct like anyone can do it and 00:07:38.980 --> 00:07:42.330 align:start position:0% that's correct like anyone can do it and by<00:07:39.520> doing<00:07:39.730> that<00:07:39.850> you<00:07:40.600> can<00:07:40.630> say<00:07:41.080> send<00:07:41.770> east<00:07:42.070> team 00:07:42.330 --> 00:07:42.340 align:start position:0% by doing that you can say send east team 00:07:42.340 --> 00:07:45.870 align:start position:0% by doing that you can say send east team at<00:07:42.520> Oakland<00:07:42.850> XYZ<00:07:43.980> common<00:07:44.980> mistake<00:07:45.400> I<00:07:45.610> had<00:07:45.850> a 00:07:45.870 --> 00:07:45.880 align:start position:0% at Oakland XYZ common mistake I had a 00:07:45.880 --> 00:07:50.010 align:start position:0% at Oakland XYZ common mistake I had a for<00:07:46.060> last<00:07:46.300> couple<00:07:47.080> week<00:07:47.290> is<00:07:47.560> that<00:07:47.770> like<00:07:49.020> people 00:07:50.010 --> 00:07:50.020 align:start position:0% for last couple week is that like people 00:07:50.020 --> 00:07:52.650 align:start position:0% for last couple week is that like people ask<00:07:50.380> question<00:07:50.830> like<00:07:51.040> something<00:07:51.460> like<00:07:51.610> also<00:07:52.450> if 00:07:52.650 --> 00:07:52.660 align:start position:0% ask question like something like also if 00:07:52.660 --> 00:07:58.770 align:start position:0% ask question like something like also if I<00:07:52.840> have<00:07:53.050> my<00:07:53.680> token<00:07:54.510> though<00:07:55.510> X<00:07:55.750> Y<00:07:56.100> Z<00:07:57.100> so<00:07:57.730> and<00:07:58.030> then 00:07:58.770 --> 00:07:58.780 align:start position:0% I have my token though X Y Z so and then 00:07:58.780 --> 00:08:01.470 align:start position:0% I have my token though X Y Z so and then my<00:07:58.930> talking<00:07:59.350> dog<00:07:59.380> come<00:08:00.160> who<00:08:00.820> owns<00:08:01.060> matter 00:08:01.470 --> 00:08:01.480 align:start position:0% my talking dog come who owns matter 00:08:01.480 --> 00:08:04.800 align:start position:0% my talking dog come who owns matter kundo<00:08:01.990> is<00:08:02.280> but<00:08:03.280> that's<00:08:03.430> completely<00:08:04.360> Arab<00:08:04.630> and 00:08:04.800 --> 00:08:04.810 align:start position:0% kundo is but that's completely Arab and 00:08:04.810 --> 00:08:08.460 align:start position:0% kundo is but that's completely Arab and so<00:08:05.140> that<00:08:05.290> is<00:08:06.540> domain<00:08:07.540> acquisition<00:08:08.290> mechanism 00:08:08.460 --> 00:08:08.470 align:start position:0% so that is domain acquisition mechanism 00:08:08.470 --> 00:08:11.550 align:start position:0% so that is domain acquisition mechanism and<00:08:09.150> this<00:08:10.150> DNS<00:08:10.630> creative<00:08:11.140> stuff<00:08:11.350> is 00:08:11.550 --> 00:08:11.560 align:start position:0% and this DNS creative stuff is 00:08:11.560 --> 00:08:13.410 align:start position:0% and this DNS creative stuff is completely<00:08:11.800> different<00:08:12.430> ones<00:08:12.610> so<00:08:12.760> they<00:08:12.970> they 00:08:13.410 --> 00:08:13.420 align:start position:0% completely different ones so they they 00:08:13.420 --> 00:08:16.020 align:start position:0% completely different ones so they they have<00:08:13.630> different<00:08:14.230> ownership<00:08:14.610> is<00:08:15.610> that<00:08:15.790> part 00:08:16.020 --> 00:08:16.030 align:start position:0% have different ownership is that part 00:08:16.030 --> 00:08:18.690 align:start position:0% have different ownership is that part clear<00:08:16.210> I<00:08:16.570> guess<00:08:17.550> okay 00:08:18.690 --> 00:08:18.700 align:start position:0% clear I guess okay 00:08:18.700 --> 00:08:21.990 align:start position:0% clear I guess okay and<00:08:19.390> yeah<00:08:19.840> so<00:08:20.080> once<00:08:20.620> so<00:08:21.010> this<00:08:21.160> is<00:08:21.280> example<00:08:21.610> how 00:08:21.990 --> 00:08:22.000 align:start position:0% and yeah so once so this is example how 00:08:22.000 --> 00:08:23.910 align:start position:0% and yeah so once so this is example how you<00:08:22.030> add<00:08:22.360> in<00:08:22.510> the<00:08:22.630> text<00:08:22.960> then<00:08:23.440> once<00:08:23.650> you<00:08:23.770> have 00:08:23.910 --> 00:08:23.920 align:start position:0% you add in the text then once you have 00:08:23.920 --> 00:08:26.160 align:start position:0% you add in the text then once you have the<00:08:24.040> text<00:08:24.340> so<00:08:24.520> currently<00:08:24.910> again<00:08:25.600> this<00:08:25.840> is 00:08:26.160 --> 00:08:26.170 align:start position:0% the text so currently again this is 00:08:26.170 --> 00:08:28.230 align:start position:0% the text so currently again this is temporary<00:08:26.910> pad 00:08:28.230 --> 00:08:28.240 align:start position:0% temporary pad 00:08:28.240 --> 00:08:30.600 align:start position:0% temporary pad eventually<00:08:29.020> it's<00:08:29.320> going<00:08:29.470> to<00:08:29.560> be<00:08:29.740> in<00:08:30.010> a<00:08:30.250> NS 00:08:30.600 --> 00:08:30.610 align:start position:0% eventually it's going to be in a NS 00:08:30.610 --> 00:08:33.060 align:start position:0% eventually it's going to be in a NS manager<00:08:31.060> but<00:08:31.210> for<00:08:31.390> the<00:08:31.510> time<00:08:31.750> being<00:08:32.010> there's<00:08:33.010> a 00:08:33.060 --> 00:08:33.070 align:start position:0% manager but for the time being there's a 00:08:33.070 --> 00:08:35.670 align:start position:0% manager but for the time being there's a two<00:08:33.280> way<00:08:33.490> harder<00:08:34.150> way<00:08:34.180> in<00:08:34.540> the<00:08:34.660> easier<00:08:34.990> way<00:08:35.200> the 00:08:35.670 --> 00:08:35.680 align:start position:0% two way harder way in the easier way the 00:08:35.680 --> 00:08:37.680 align:start position:0% two way harder way in the easier way the harder<00:08:36.010> ways<00:08:36.220> you<00:08:36.820> I<00:08:36.849> know 00:08:37.680 --> 00:08:37.690 align:start position:0% harder ways you I know 00:08:37.690 --> 00:08:40.140 align:start position:0% harder ways you I know assuming<00:08:38.349> you<00:08:38.530> have<00:08:38.680> a<00:08:38.710> skill<00:08:39.550> to<00:08:39.700> manage<00:08:39.880> your 00:08:40.140 --> 00:08:40.150 align:start position:0% assuming you have a skill to manage your 00:08:40.150 --> 00:08:43.589 align:start position:0% assuming you have a skill to manage your DNS<00:08:40.660> record<00:08:41.169> you<00:08:41.590> go<00:08:41.740> to<00:08:41.800> like<00:08:42.190> in<00:08:42.340> a<00:08:42.599> google 00:08:43.589 --> 00:08:43.599 align:start position:0% DNS record you go to like in a google 00:08:43.599 --> 00:08:46.890 align:start position:0% DNS record you go to like in a google cloud<00:08:44.380> dns<00:08:44.980> manager<00:08:45.730> or<00:08:46.090> something<00:08:46.270> and<00:08:46.630> you 00:08:46.890 --> 00:08:46.900 align:start position:0% cloud dns manager or something and you 00:08:46.900 --> 00:08:51.750 align:start position:0% cloud dns manager or something and you basically<00:08:47.290> add<00:08:47.590> your<00:08:47.860> own<00:08:49.410> that<00:08:50.410> record<00:08:51.370> into 00:08:51.750 --> 00:08:51.760 align:start position:0% basically add your own that record into 00:08:51.760 --> 00:08:53.850 align:start position:0% basically add your own that record into the<00:08:51.790> DNS<00:08:52.150> record<00:08:52.570> and<00:08:52.750> once<00:08:52.990> you<00:08:53.140> come<00:08:53.290> to 00:08:53.850 --> 00:08:53.860 align:start position:0% the DNS record and once you come to 00:08:53.860 --> 00:08:58.140 align:start position:0% the DNS record and once you come to the<00:08:54.130> NS<00:08:54.370> a<00:08:54.580> key<00:08:54.640> and<00:08:54.940> installed<00:08:55.470> domains<00:08:57.150> we'll 00:08:58.140 --> 00:08:58.150 align:start position:0% the NS a key and installed domains we'll 00:08:58.150 --> 00:09:00.600 align:start position:0% the NS a key and installed domains we'll do<00:08:58.330> a<00:08:58.360> couple<00:08:58.560> there's<00:08:59.560> a<00:08:59.620> wizard<00:08:59.860> to<00:09:00.400> go 00:09:00.600 --> 00:09:00.610 align:start position:0% do a couple there's a wizard to go 00:09:00.610 --> 00:09:02.370 align:start position:0% do a couple there's a wizard to go through<00:09:00.790> whether<00:09:01.000> you<00:09:01.480> have<00:09:01.690> done<00:09:01.870> any<00:09:02.080> sell 00:09:02.370 --> 00:09:02.380 align:start position:0% through whether you have done any sell 00:09:02.380 --> 00:09:04.350 align:start position:0% through whether you have done any sell upon<00:09:03.040> by<00:09:03.310> yourself<00:09:03.730> because<00:09:03.940> these<00:09:04.180> are 00:09:04.350 --> 00:09:04.360 align:start position:0% upon by yourself because these are 00:09:04.360 --> 00:09:06.030 align:start position:0% upon by yourself because these are things<00:09:04.600> we<00:09:04.810> can't<00:09:05.020> automate<00:09:05.350> ourselves<00:09:05.860> and 00:09:06.030 --> 00:09:06.040 align:start position:0% things we can't automate ourselves and 00:09:06.040 --> 00:09:08.490 align:start position:0% things we can't automate ourselves and then<00:09:06.700> like<00:09:06.940> it<00:09:07.090> once<00:09:07.270> it's<00:09:07.450> done<00:09:07.750> there's<00:09:08.350> a 00:09:08.490 --> 00:09:08.500 align:start position:0% then like it once it's done there's a 00:09:08.500 --> 00:09:11.130 align:start position:0% then like it once it's done there's a button<00:09:09.220> to<00:09:09.490> say<00:09:09.700> submit<00:09:10.180> the<00:09:10.300> proof<00:09:10.540> which 00:09:11.130 --> 00:09:11.140 align:start position:0% button to say submit the proof which 00:09:11.140 --> 00:09:14.220 align:start position:0% button to say submit the proof which everybody<00:09:12.130> anyone<00:09:12.820> can<00:09:13.030> press<00:09:13.330> and<00:09:13.630> once<00:09:14.050> it's 00:09:14.220 --> 00:09:14.230 align:start position:0% everybody anyone can press and once it's 00:09:14.230 --> 00:09:16.140 align:start position:0% everybody anyone can press and once it's pressed<00:09:14.440> it<00:09:14.740> looking<00:09:15.130> up<00:09:15.160> the<00:09:15.370> DNS<00:09:15.760> record 00:09:16.140 --> 00:09:16.150 align:start position:0% pressed it looking up the DNS record 00:09:16.150 --> 00:09:19.550 align:start position:0% pressed it looking up the DNS record chain<00:09:17.050> relationship<00:09:17.980> construct<00:09:18.670> a<00:09:18.760> proof<00:09:19.030> and 00:09:19.550 --> 00:09:19.560 align:start position:0% chain relationship construct a proof and 00:09:19.560 --> 00:09:23.070 align:start position:0% chain relationship construct a proof and put<00:09:20.560> the<00:09:20.650> hash<00:09:21.040> of<00:09:21.280> the<00:09:21.430> proof<00:09:21.730> to<00:09:22.390> something 00:09:23.070 --> 00:09:23.080 align:start position:0% put the hash of the proof to something 00:09:23.080 --> 00:09:25.680 align:start position:0% put the hash of the proof to something called<00:09:23.230> DNS<00:09:23.530> SEC<00:09:23.770> Oracle<00:09:24.340> the<00:09:24.520> insect<00:09:25.060> or<00:09:25.360> call 00:09:25.680 --> 00:09:25.690 align:start position:0% called DNS SEC Oracle the insect or call 00:09:25.690 --> 00:09:28.470 align:start position:0% called DNS SEC Oracle the insect or call verify<00:09:26.140> that<00:09:26.320> that's<00:09:26.710> like<00:09:26.860> not<00:09:27.670> tampered<00:09:28.240> and 00:09:28.470 --> 00:09:28.480 align:start position:0% verify that that's like not tampered and 00:09:28.480 --> 00:09:31.140 align:start position:0% verify that that's like not tampered and if<00:09:28.630> it's<00:09:28.840> correct<00:09:29.080> one<00:09:29.400> there's<00:09:30.400> a<00:09:30.490> registrar 00:09:31.140 --> 00:09:31.150 align:start position:0% if it's correct one there's a registrar 00:09:31.150 --> 00:09:36.240 align:start position:0% if it's correct one there's a registrar which<00:09:31.930> register<00:09:32.680> the<00:09:33.400> same<00:09:34.180> address<00:09:34.630> as<00:09:34.840> a<00:09:35.290> DNS 00:09:36.240 --> 00:09:36.250 align:start position:0% which register the same address as a DNS 00:09:36.250 --> 00:09:43.770 align:start position:0% which register the same address as a DNS domain<00:09:36.550> order<00:09:37.390> and<00:09:39.030> yep<00:09:41.040> if<00:09:42.120> that's<00:09:43.120> a<00:09:43.210> bit<00:09:43.360> too 00:09:43.770 --> 00:09:43.780 align:start position:0% domain order and yep if that's a bit too 00:09:43.780 --> 00:09:46.620 align:start position:0% domain order and yep if that's a bit too much<00:09:44.020> data<00:09:45.120> another<00:09:46.120> solution 00:09:46.620 --> 00:09:46.630 align:start position:0% much data another solution 00:09:46.630 --> 00:09:48.990 align:start position:0% much data another solution something<00:09:47.110> like<00:09:47.290> ez<00:09:47.560> DNS<00:09:48.160> they<00:09:48.640> should<00:09:48.880> be 00:09:48.990 --> 00:09:49.000 align:start position:0% something like ez DNS they should be 00:09:49.000 --> 00:09:51.150 align:start position:0% something like ez DNS they should be able<00:09:49.180> to<00:09:49.420> automate<00:09:49.870> you<00:09:50.500> know<00:09:50.620> the<00:09:50.770> second 00:09:51.150 --> 00:09:51.160 align:start position:0% able to automate you know the second 00:09:51.160 --> 00:09:55.830 align:start position:0% able to automate you know the second bits<00:09:51.930> from<00:09:52.930> their<00:09:53.370> website<00:09:54.370> so<00:09:54.820> that<00:09:54.850> you<00:09:55.570> that 00:09:55.830 --> 00:09:55.840 align:start position:0% bits from their website so that you that 00:09:55.840 --> 00:09:57.770 align:start position:0% bits from their website so that you that that's<00:09:56.170> something<00:09:56.440> you<00:09:56.680> went<00:09:56.860> through<00:09:57.040> right 00:09:57.770 --> 00:09:57.780 align:start position:0% that's something you went through right 00:09:57.780 --> 00:10:00.540 align:start position:0% that's something you went through right easy<00:09:58.780> DNS<00:09:59.200> makes<00:09:59.650> it<00:09:59.830> very<00:10:00.040> simple<00:10:00.340> to 00:10:00.540 --> 00:10:00.550 align:start position:0% easy DNS makes it very simple to 00:10:00.550 --> 00:10:04.560 align:start position:0% easy DNS makes it very simple to register<00:10:01.330> at<00:10:01.690> XYZ<00:10:02.260> domain<00:10:02.620> and<00:10:03.210> they<00:10:04.210> have<00:10:04.450> an 00:10:04.560 --> 00:10:04.570 align:start position:0% register at XYZ domain and they have an 00:10:04.570 --> 00:10:06.420 align:start position:0% register at XYZ domain and they have an interface<00:10:04.840> in<00:10:05.230> which<00:10:05.410> you<00:10:05.590> simply<00:10:05.860> put<00:10:06.220> an 00:10:06.420 --> 00:10:06.430 align:start position:0% interface in which you simply put an 00:10:06.430 --> 00:10:09.240 align:start position:0% interface in which you simply put an address<00:10:06.880> and<00:10:07.090> you<00:10:07.570> decide<00:10:07.990> in<00:10:08.350> which<00:10:08.650> network 00:10:09.240 --> 00:10:09.250 align:start position:0% address and you decide in which network 00:10:09.250 --> 00:10:12.960 align:start position:0% address and you decide in which network robson<00:10:09.910> or<00:10:10.090> maynot<00:10:10.510> you<00:10:10.750> want<00:10:10.990> to<00:10:11.640> claim<00:10:12.640> this 00:10:12.960 --> 00:10:12.970 align:start position:0% robson or maynot you want to claim this 00:10:12.970 --> 00:10:15.630 align:start position:0% robson or maynot you want to claim this domain<00:10:13.450> and<00:10:13.780> they<00:10:14.590> do<00:10:14.650> all<00:10:15.010> the<00:10:15.190> process<00:10:15.520> for 00:10:15.630 --> 00:10:15.640 align:start position:0% domain and they do all the process for 00:10:15.640 --> 00:10:17.220 align:start position:0% domain and they do all the process for you<00:10:15.760> it<00:10:15.910> takes<00:10:16.090> some<00:10:16.300> time<00:10:16.540> but<00:10:16.900> at<00:10:17.050> the<00:10:17.080> end 00:10:17.220 --> 00:10:17.230 align:start position:0% you it takes some time but at the end 00:10:17.230 --> 00:10:19.920 align:start position:0% you it takes some time but at the end you<00:10:17.740> have<00:10:17.980> your<00:10:18.010> own<00:10:18.460> domain<00:10:18.790> claimed<00:10:19.390> on<00:10:19.600> ENS 00:10:19.920 --> 00:10:19.930 align:start position:0% you have your own domain claimed on ENS 00:10:19.930 --> 00:10:22.920 align:start position:0% you have your own domain claimed on ENS the<00:10:20.560> resolver<00:10:21.040> is<00:10:21.160> set<00:10:21.430> and<00:10:21.700> even<00:10:22.420> the<00:10:22.570> address 00:10:22.920 --> 00:10:22.930 align:start position:0% the resolver is set and even the address 00:10:22.930 --> 00:10:31.500 align:start position:0% the resolver is set and even the address is<00:10:23.110> pointed<00:10:23.530> to<00:10:25.020> with<00:10:26.490> automatically<00:10:30.510> yeah 00:10:31.500 --> 00:10:31.510 align:start position:0% is pointed to with automatically yeah 00:10:31.510 --> 00:10:34.020 align:start position:0% is pointed to with automatically yeah this<00:10:31.660> is<00:10:31.840> in<00:10:32.290> the<00:10:32.500> manager<00:10:32.920> after<00:10:33.460> that<00:10:33.820> you 00:10:34.020 --> 00:10:34.030 align:start position:0% this is in the manager after that you 00:10:34.030 --> 00:10:36.690 align:start position:0% this is in the manager after that you have<00:10:34.240> bought<00:10:34.450> the<00:10:34.570> domain<00:10:34.720> you<00:10:35.200> see<00:10:35.700> domain 00:10:36.690 --> 00:10:36.700 align:start position:0% have bought the domain you see domain 00:10:36.700 --> 00:10:39.930 align:start position:0% have bought the domain you see domain DNS<00:10:37.180> names<00:10:37.720> for<00:10:38.020> example<00:10:38.050> dot<00:10:38.590> XYZ<00:10:39.130> who<00:10:39.730> the 00:10:39.930 --> 00:10:39.940 align:start position:0% DNS names for example dot XYZ who the 00:10:39.940 --> 00:10:42.090 align:start position:0% DNS names for example dot XYZ who the owner<00:10:40.120> is<00:10:40.240> and<00:10:40.420> the<00:10:41.200> resolver<00:10:41.650> and<00:10:41.920> the 00:10:42.090 --> 00:10:42.100 align:start position:0% owner is and the resolver and the 00:10:42.100 --> 00:10:44.040 align:start position:0% owner is and the resolver and the address<00:10:42.430> that<00:10:42.640> points<00:10:43.360> it<00:10:43.480> to<00:10:43.600> in<00:10:43.750> this<00:10:43.870> case 00:10:44.040 --> 00:10:44.050 align:start position:0% address that points it to in this case 00:10:44.050 --> 00:10:46.170 align:start position:0% address that points it to in this case is<00:10:44.230> the<00:10:44.380> same<00:10:44.590> address<00:10:44.860> and<00:10:45.190> they<00:10:45.730> do<00:10:45.790> this 00:10:46.170 --> 00:10:46.180 align:start position:0% is the same address and they do this 00:10:46.180 --> 00:10:51.480 align:start position:0% is the same address and they do this automatically<00:10:46.870> for<00:10:47.290> you<00:10:49.380> so<00:10:50.380> so<00:10:51.220> far<00:10:51.430> I 00:10:51.480 --> 00:10:51.490 align:start position:0% automatically for you so so far I 00:10:51.490 --> 00:10:54.420 align:start position:0% automatically for you so so far I explained<00:10:52.020> the<00:10:53.020> things<00:10:53.260> you<00:10:53.800> didn't<00:10:54.100> be<00:10:54.190> doing 00:10:54.420 --> 00:10:54.430 align:start position:0% explained the things you didn't be doing 00:10:54.430 --> 00:10:56.460 align:start position:0% explained the things you didn't be doing today<00:10:54.610> because<00:10:55.120> it<00:10:55.210> takes<00:10:55.390> too<00:10:55.540> long<00:10:55.570> but 00:10:56.460 --> 00:10:56.470 align:start position:0% today because it takes too long but 00:10:56.470 --> 00:10:58.920 align:start position:0% today because it takes too long but there<00:10:57.040> are<00:10:57.220> going<00:10:57.490> to<00:10:57.670> talk<00:10:57.850> about<00:10:58.120> some<00:10:58.780> other 00:10:58.920 --> 00:10:58.930 align:start position:0% there are going to talk about some other 00:10:58.930 --> 00:11:01.770 align:start position:0% there are going to talk about some other way<00:10:59.200> you<00:10:59.260> could<00:10:59.590> do<00:10:59.800> right<00:11:00.310> now<00:11:00.640> as<00:11:01.240> long<00:11:01.510> as<00:11:01.570> if 00:11:01.770 --> 00:11:01.780 align:start position:0% way you could do right now as long as if 00:11:01.780 --> 00:11:03.720 align:start position:0% way you could do right now as long as if you<00:11:02.230> have<00:11:02.380> a<00:11:02.410> Wi-Fi<00:11:02.770> connection<00:11:03.340> and<00:11:03.490> if<00:11:03.640> you 00:11:03.720 --> 00:11:03.730 align:start position:0% you have a Wi-Fi connection and if you 00:11:03.730 --> 00:11:06.300 align:start position:0% you have a Wi-Fi connection and if you have<00:11:03.940> a<00:11:03.970> mobile<00:11:04.210> well<00:11:04.870> meta<00:11:05.500> mask<00:11:05.800> or<00:11:06.040> mobile 00:11:06.300 --> 00:11:06.310 align:start position:0% have a mobile well meta mask or mobile 00:11:06.310 --> 00:11:07.230 align:start position:0% have a mobile well meta mask or mobile wallet<00:11:06.640> or 00:11:07.230 --> 00:11:07.240 align:start position:0% wallet or 00:11:07.240 --> 00:11:10.730 align:start position:0% wallet or and<00:11:07.329> you<00:11:07.899> have<00:11:08.079> a<00:11:08.110> nice<00:11:08.439> okay<00:11:09.339> and<00:11:09.730> the<00:11:10.119> one 00:11:10.730 --> 00:11:10.740 align:start position:0% and you have a nice okay and the one 00:11:10.740 --> 00:11:12.059 align:start position:0% and you have a nice okay and the one doesn't 00:11:12.059 --> 00:11:12.069 align:start position:0% doesn't 00:11:12.069 --> 00:11:14.160 align:start position:0% doesn't there's<00:11:12.850> actually<00:11:13.209> quite<00:11:13.240> a<00:11:13.569> lot<00:11:13.660> of<00:11:13.809> weight 00:11:14.160 --> 00:11:14.170 align:start position:0% there's actually quite a lot of weight 00:11:14.170 --> 00:11:19.199 align:start position:0% there's actually quite a lot of weight but<00:11:14.850> who<00:11:15.850> today<00:11:16.509> we're<00:11:16.689> gonna<00:11:16.809> talk<00:11:17.110> about<00:11:18.209> our 00:11:19.199 --> 00:11:19.209 align:start position:0% but who today we're gonna talk about our 00:11:19.209 --> 00:11:24.150 align:start position:0% but who today we're gonna talk about our own<00:11:20.009> now<00:11:21.009> Dorian's<00:11:21.639> domains<00:11:22.089> and<00:11:22.589> get<00:11:23.589> coin<00:11:23.829> is 00:11:24.150 --> 00:11:24.160 align:start position:0% own now Dorian's domains and get coin is 00:11:24.160 --> 00:11:26.369 align:start position:0% own now Dorian's domains and get coin is kind<00:11:24.699> of<00:11:24.790> sad<00:11:25.029> party<00:11:25.360> integration<00:11:25.929> and<00:11:26.110> their 00:11:26.369 --> 00:11:26.379 align:start position:0% kind of sad party integration and their 00:11:26.379 --> 00:11:29.100 align:start position:0% kind of sad party integration and their status<00:11:26.800> I<00:11:27.179> forgot<00:11:28.179> to<00:11:28.300> take<00:11:28.449> out<00:11:28.600> the<00:11:28.749> bracket 00:11:29.100 --> 00:11:29.110 align:start position:0% status I forgot to take out the bracket 00:11:29.110 --> 00:11:30.989 align:start position:0% status I forgot to take out the bracket but<00:11:29.259> like<00:11:29.379> that's<00:11:30.129> another<00:11:30.369> sub<00:11:30.699> party 00:11:30.989 --> 00:11:30.999 align:start position:0% but like that's another sub party 00:11:30.999 --> 00:11:35.069 align:start position:0% but like that's another sub party integration<00:11:31.509> for<00:11:31.779> the<00:11:31.809> mobile<00:11:32.170> solution<00:11:34.079> and 00:11:35.069 --> 00:11:35.079 align:start position:0% integration for the mobile solution and 00:11:35.079 --> 00:11:39.269 align:start position:0% integration for the mobile solution and so<00:11:35.559> this<00:11:35.829> is<00:11:36.149> now<00:11:37.149> a<00:11:37.179> NS<00:11:37.629> domains<00:11:37.990> which<00:11:38.529> again 00:11:39.269 --> 00:11:39.279 align:start position:0% so this is now a NS domains which again 00:11:39.279 --> 00:11:41.819 align:start position:0% so this is now a NS domains which again we<00:11:39.490> are<00:11:39.639> going<00:11:39.850> to<00:11:39.970> incorporate<00:11:40.749> into<00:11:41.139> the<00:11:41.439> ENS 00:11:41.819 --> 00:11:41.829 align:start position:0% we are going to incorporate into the ENS 00:11:41.829 --> 00:11:45.689 align:start position:0% we are going to incorporate into the ENS manager<00:11:42.480> but<00:11:43.480> from<00:11:44.379> here<00:11:44.589> what<00:11:45.069> you<00:11:45.100> can<00:11:45.369> do<00:11:45.579> is 00:11:45.689 --> 00:11:45.699 align:start position:0% manager but from here what you can do is 00:11:45.699 --> 00:11:48.629 align:start position:0% manager but from here what you can do is like<00:11:45.850> a<00:11:45.879> basically<00:11:46.420> if<00:11:47.110> you<00:11:47.319> type<00:11:47.860> your<00:11:48.100> my 00:11:48.629 --> 00:11:48.639 align:start position:0% like a basically if you type your my 00:11:48.639 --> 00:11:52.650 align:start position:0% like a basically if you type your my fancy<00:11:49.119> name<00:11:49.360> it's<00:11:50.879> this<00:11:51.879> is<00:11:52.119> the<00:11:52.269> list<00:11:52.480> of 00:11:52.650 --> 00:11:52.660 align:start position:0% fancy name it's this is the list of 00:11:52.660 --> 00:11:56.609 align:start position:0% fancy name it's this is the list of domain<00:11:53.249> is<00:11:54.249> which<00:11:54.850> allows<00:11:55.509> you<00:11:55.809> to<00:11:55.869> get<00:11:56.290> there 00:11:56.609 --> 00:11:56.619 align:start position:0% domain is which allows you to get there 00:11:56.619 --> 00:11:59.460 align:start position:0% domain is which allows you to get there sub<00:11:56.860> domain<00:11:57.220> as<00:11:57.629> so<00:11:58.629> like<00:11:58.749> in<00:11:58.899> this<00:11:59.019> case<00:11:59.230> my 00:11:59.460 --> 00:11:59.470 align:start position:0% sub domain as so like in this case my 00:11:59.470 --> 00:12:03.840 align:start position:0% sub domain as so like in this case my fancy<00:11:59.920> name<00:12:00.480> Leroy<00:12:01.480> doe<00:12:01.749> is<00:12:01.990> and<00:12:02.379> this<00:12:03.069> top<00:12:03.670> and 00:12:03.840 --> 00:12:03.850 align:start position:0% fancy name Leroy doe is and this top and 00:12:03.850 --> 00:12:06.989 align:start position:0% fancy name Leroy doe is and this top and this<00:12:04.119> is<00:12:04.300> me<00:12:04.600> though<00:12:04.929> is<00:12:05.139> there<00:12:05.769> for<00:12:06.040> them<00:12:06.220> they 00:12:06.989 --> 00:12:06.999 align:start position:0% this is me though is there for them they 00:12:06.999 --> 00:12:09.600 align:start position:0% this is me though is there for them they give<00:12:07.240> you<00:12:07.389> you<00:12:07.720> for<00:12:07.990> free<00:12:08.279> but<00:12:09.279> like<00:12:09.429> you<00:12:09.550> still 00:12:09.600 --> 00:12:09.610 align:start position:0% give you you for free but like you still 00:12:09.610 --> 00:12:11.160 align:start position:0% give you you for free but like you still have<00:12:09.759> to<00:12:09.939> pay<00:12:10.059> for<00:12:10.209> the<00:12:10.300> gas<00:12:10.449> so<00:12:10.809> like<00:12:10.929> if<00:12:11.079> you 00:12:11.160 --> 00:12:11.170 align:start position:0% have to pay for the gas so like if you 00:12:11.170 --> 00:12:13.049 align:start position:0% have to pay for the gas so like if you want<00:12:11.379> to<00:12:11.439> go<00:12:11.559> for<00:12:11.709> the<00:12:11.769> cheaper<00:12:12.129> one<00:12:12.309> this 00:12:13.049 --> 00:12:13.059 align:start position:0% want to go for the cheaper one this 00:12:13.059 --> 00:12:16.439 align:start position:0% want to go for the cheaper one this could<00:12:13.360> be<00:12:13.509> the<00:12:13.720> way<00:12:13.929> and<00:12:14.230> then<00:12:14.949> I<00:12:15.329> think<00:12:16.329> there 00:12:16.439 --> 00:12:16.449 align:start position:0% could be the way and then I think there 00:12:16.449 --> 00:12:17.970 align:start position:0% could be the way and then I think there are<00:12:16.509> certain<00:12:16.809> domain<00:12:17.199> name<00:12:17.379> I<00:12:17.529> shouldn't<00:12:17.860> be 00:12:17.970 --> 00:12:17.980 align:start position:0% are certain domain name I shouldn't be 00:12:17.980 --> 00:12:20.299 align:start position:0% are certain domain name I shouldn't be pronouncing<00:12:18.639> that's<00:12:18.970> okay<00:12:19.749> that's<00:12:19.899> okay 00:12:20.299 --> 00:12:20.309 align:start position:0% pronouncing that's okay that's okay 00:12:20.309 --> 00:12:23.609 align:start position:0% pronouncing that's okay that's okay okay<00:12:21.309> so<00:12:21.519> like<00:12:21.670> it<00:12:21.759> once<00:12:21.939> some<00:12:22.240> give<00:12:22.569> me<00:12:22.720> stuff 00:12:23.609 --> 00:12:23.619 align:start position:0% okay so like it once some give me stuff 00:12:23.619 --> 00:12:26.489 align:start position:0% okay so like it once some give me stuff so<00:12:24.189> some<00:12:24.369> people<00:12:24.519> actually<00:12:24.790> trying<00:12:25.179> to<00:12:25.499> charge 00:12:26.489 --> 00:12:26.499 align:start position:0% so some people actually trying to charge 00:12:26.499 --> 00:12:31.319 align:start position:0% so some people actually trying to charge so<00:12:26.949> the<00:12:27.579> give<00:12:28.089> me<00:12:28.240> is<00:12:28.420> actually<00:12:28.779> charges<00:12:30.329> 0.005 00:12:31.319 --> 00:12:31.329 align:start position:0% so the give me is actually charges 0.005 00:12:31.329 --> 00:12:35.309 align:start position:0% so the give me is actually charges 0.005 vs<00:12:31.629> that<00:12:32.019> calm<00:12:32.230> stuff<00:12:32.549> next<00:12:33.839> next<00:12:34.839> is<00:12:34.990> like<00:12:35.290> a 00:12:35.309 --> 00:12:35.319 align:start position:0% vs that calm stuff next next is like a 00:12:35.319 --> 00:12:37.679 align:start position:0% vs that calm stuff next next is like a so<00:12:35.619> you<00:12:36.309> guys<00:12:36.519> mentioned<00:12:37.059> I<00:12:37.149> get<00:12:37.299> pretty<00:12:37.569> much 00:12:37.679 --> 00:12:37.689 align:start position:0% so you guys mentioned I get pretty much 00:12:37.689 --> 00:12:40.769 align:start position:0% so you guys mentioned I get pretty much everybody<00:12:38.110> has<00:12:38.230> a<00:12:38.290> geek<00:12:38.499> coin<00:12:39.269> sorry<00:12:40.360> github 00:12:40.769 --> 00:12:40.779 align:start position:0% everybody has a geek coin sorry github 00:12:40.779 --> 00:12:44.249 align:start position:0% everybody has a geek coin sorry github and<00:12:41.610> who<00:12:42.610> do<00:12:43.089> you<00:12:43.149> not<00:12:43.360> know<00:12:43.569> geek<00:12:43.869> point 00:12:44.249 --> 00:12:44.259 align:start position:0% and who do you not know geek point 00:12:44.259 --> 00:12:51.150 align:start position:0% and who do you not know geek point oh<00:12:46.019> great<00:12:47.160> one<00:12:48.160> person<00:12:48.519> so<00:12:49.449> two<00:12:49.959> people<00:12:50.259> okay 00:12:51.150 --> 00:12:51.160 align:start position:0% oh great one person so two people okay 00:12:51.160 --> 00:12:56.129 align:start position:0% oh great one person so two people okay a<00:12:51.399> three<00:12:51.899> you<00:12:52.899> know<00:12:53.079> Billy<00:12:53.369> okay<00:12:54.399> and<00:12:55.389> so<00:12:55.689> coin 00:12:56.129 --> 00:12:56.139 align:start position:0% a three you know Billy okay and so coin 00:12:56.139 --> 00:12:59.249 align:start position:0% a three you know Billy okay and so coin is<00:12:56.439> a<00:12:56.470> bounty<00:12:57.069> system<00:12:57.279> tied<00:12:58.240> into<00:12:58.509> the<00:12:58.779> key<00:12:59.019> hub 00:12:59.249 --> 00:12:59.259 align:start position:0% is a bounty system tied into the key hub 00:12:59.259 --> 00:13:02.340 align:start position:0% is a bounty system tied into the key hub that<00:12:59.470> if<00:12:59.679> they<00:12:59.949> have<00:13:00.790> issues<00:13:00.939> and<00:13:01.720> if<00:13:01.869> you<00:13:01.990> want 00:13:02.340 --> 00:13:02.350 align:start position:0% that if they have issues and if you want 00:13:02.350 --> 00:13:04.079 align:start position:0% that if they have issues and if you want someone<00:13:02.559> to<00:13:02.709> work<00:13:02.980> on<00:13:03.189> there<00:13:03.369> you<00:13:03.639> can<00:13:03.790> put<00:13:03.999> the 00:13:04.079 --> 00:13:04.089 align:start position:0% someone to work on there you can put the 00:13:04.089 --> 00:13:06.150 align:start position:0% someone to work on there you can put the bounty<00:13:04.480> on<00:13:04.509> it<00:13:04.749> and<00:13:04.899> once<00:13:05.619> you<00:13:05.829> solve<00:13:06.009> the 00:13:06.150 --> 00:13:06.160 align:start position:0% bounty on it and once you solve the 00:13:06.160 --> 00:13:10.970 align:start position:0% bounty on it and once you solve the problem<00:13:07.439> you<00:13:08.439> get<00:13:08.679> worried<00:13:09.279> about<00:13:09.309> the 00:13:10.970 --> 00:13:10.980 align:start position:0% problem you get worried about the 00:13:10.980 --> 00:13:13.199 align:start position:0% problem you get worried about the bounties<00:13:11.980> sometimes<00:13:12.369> like<00:13:12.549> east<00:13:12.819> sometimes 00:13:13.199 --> 00:13:13.209 align:start position:0% bounties sometimes like east sometimes 00:13:13.209 --> 00:13:16.590 align:start position:0% bounties sometimes like east sometimes like<00:13:13.420> die<00:13:14.410> and<00:13:14.709> the<00:13:15.339> one<00:13:15.759> thing<00:13:15.999> they<00:13:16.209> released 00:13:16.590 --> 00:13:16.600 align:start position:0% like die and the one thing they released 00:13:16.600 --> 00:13:19.739 align:start position:0% like die and the one thing they released I<00:13:17.139> think<00:13:17.759> several<00:13:18.759> months<00:13:19.029> ago<00:13:19.209> I<00:13:19.329> think<00:13:19.419> is 00:13:19.739 --> 00:13:19.749 align:start position:0% I think several months ago I think is 00:13:19.749 --> 00:13:20.940 align:start position:0% I think several months ago I think is that<00:13:20.470> it 00:13:20.940 --> 00:13:20.950 align:start position:0% that it 00:13:20.950 --> 00:13:25.380 align:start position:0% that it creation<00:13:21.310> with<00:13:21.550> ENS<00:13:23.250> basically<00:13:24.250> I<00:13:24.580> think<00:13:25.210> the 00:13:25.380 --> 00:13:25.390 align:start position:0% creation with ENS basically I think the 00:13:25.390 --> 00:13:27.720 align:start position:0% creation with ENS basically I think the assignee<00:13:25.750> is<00:13:26.140> tied<00:13:26.470> in<00:13:26.620> with<00:13:26.740> the<00:13:26.890> github<00:13:27.130> so 00:13:27.720 --> 00:13:27.730 align:start position:0% assignee is tied in with the github so 00:13:27.730 --> 00:13:30.060 align:start position:0% assignee is tied in with the github so like<00:13:27.880> you<00:13:28.030> you<00:13:28.570> would<00:13:28.900> have<00:13:29.170> the<00:13:29.320> same<00:13:29.350> login 00:13:30.060 --> 00:13:30.070 align:start position:0% like you you would have the same login 00:13:30.070 --> 00:13:34.650 align:start position:0% like you you would have the same login as<00:13:30.600> your<00:13:31.600> github<00:13:32.020> address<00:13:33.010> account<00:13:33.970> so<00:13:34.210> in<00:13:34.510> my 00:13:34.650 --> 00:13:34.660 align:start position:0% as your github address account so in my 00:13:34.660 --> 00:13:36.810 align:start position:0% as your github address account so in my case<00:13:34.720> Mikoto<00:13:35.410> is<00:13:35.530> my<00:13:35.770> github<00:13:36.010> account<00:13:36.190> so<00:13:36.790> you 00:13:36.810 --> 00:13:36.820 align:start position:0% case Mikoto is my github account so you 00:13:36.820 --> 00:13:39.000 align:start position:0% case Mikoto is my github account so you would<00:13:37.000> have<00:13:37.240> like<00:13:37.450> Mikoto<00:13:37.990> and<00:13:38.470> what<00:13:38.770> they<00:13:38.950> do 00:13:39.000 --> 00:13:39.010 align:start position:0% would have like Mikoto and what they do 00:13:39.010 --> 00:13:41.810 align:start position:0% would have like Mikoto and what they do is<00:13:39.340> like<00:13:39.370> if<00:13:39.910> you<00:13:40.120> do<00:13:40.660> the<00:13:40.780> single<00:13:41.080> sign-on 00:13:41.810 --> 00:13:41.820 align:start position:0% is like if you do the single sign-on 00:13:41.820 --> 00:13:46.590 align:start position:0% is like if you do the single sign-on bhaiyyaji<00:13:42.820> hub<00:13:43.090> and<00:13:43.270> they<00:13:43.930> give<00:13:44.230> you<00:13:45.600> Mikoto 00:13:46.590 --> 00:13:46.600 align:start position:0% bhaiyyaji hub and they give you Mikoto 00:13:46.600 --> 00:13:50.070 align:start position:0% bhaiyyaji hub and they give you Mikoto geek<00:13:47.320> coined<00:13:47.680> or<00:13:47.920> ease<00:13:48.220> and<00:13:48.550> I<00:13:49.180> think<00:13:49.570> in<00:13:49.780> their 00:13:50.070 --> 00:13:50.080 align:start position:0% geek coined or ease and I think in their 00:13:50.080 --> 00:13:55.130 align:start position:0% geek coined or ease and I think in their case<00:13:50.110> they<00:13:50.650> may<00:13:50.860> pay<00:13:51.130> for<00:13:51.400> the<00:13:51.520> gas<00:13:52.950> yeah<00:13:53.950> so 00:13:55.130 --> 00:13:55.140 align:start position:0% case they may pay for the gas yeah so 00:13:55.140 --> 00:13:58.740 align:start position:0% case they may pay for the gas yeah so you<00:13:56.140> could<00:13:56.410> get<00:13:57.100> away<00:13:57.250> getting<00:13:58.120> the<00:13:58.330> DNS<00:13:58.720> name 00:13:58.740 --> 00:13:58.750 align:start position:0% you could get away getting the DNS name 00:13:58.750 --> 00:14:02.010 align:start position:0% you could get away getting the DNS name even<00:13:59.470> if<00:13:59.560> you<00:13:59.740> have<00:13:59.890> no<00:14:00.190> gas<00:14:00.460> give<00:14:01.090> a<00:14:01.180> try 00:14:02.010 --> 00:14:02.020 align:start position:0% even if you have no gas give a try 00:14:02.020 --> 00:14:03.690 align:start position:0% even if you have no gas give a try but<00:14:02.740> you<00:14:02.800> can't<00:14:03.010> do<00:14:03.100> all<00:14:03.220> the<00:14:03.340> exercise 00:14:03.690 --> 00:14:03.700 align:start position:0% but you can't do all the exercise 00:14:03.700 --> 00:14:05.520 align:start position:0% but you can't do all the exercise afterward<00:14:04.180> because<00:14:04.510> that<00:14:04.930> requires<00:14:05.080> a<00:14:05.320> gas 00:14:05.520 --> 00:14:05.530 align:start position:0% afterward because that requires a gas 00:14:05.530 --> 00:14:09.930 align:start position:0% afterward because that requires a gas right<00:14:06.060> next<00:14:07.710> yeah<00:14:08.710> this<00:14:09.490> is<00:14:09.610> a<00:14:09.670> couple 00:14:09.930 --> 00:14:09.940 align:start position:0% right next yeah this is a couple 00:14:09.940 --> 00:14:14.520 align:start position:0% right next yeah this is a couple screenshot<00:14:10.420> and<00:14:11.820> yeah<00:14:12.820> so<00:14:13.570> he<00:14:13.870> is<00:14:14.170> proud<00:14:14.470> of 00:14:14.520 --> 00:14:14.530 align:start position:0% screenshot and yeah so he is proud of 00:14:14.530 --> 00:14:20.010 align:start position:0% screenshot and yeah so he is proud of the<00:14:17.100> yeah<00:14:18.100> so<00:14:18.550> this<00:14:18.970> is<00:14:19.030> also<00:14:19.330> to<00:14:19.480> suggest<00:14:19.870> that 00:14:20.010 --> 00:14:20.020 align:start position:0% the yeah so this is also to suggest that 00:14:20.020 --> 00:14:22.380 align:start position:0% the yeah so this is also to suggest that if<00:14:20.200> you<00:14:20.320> have<00:14:20.350> dubs<00:14:20.680> you<00:14:21.010> can<00:14:21.250> give<00:14:21.520> subdomains 00:14:22.380 --> 00:14:22.390 align:start position:0% if you have dubs you can give subdomains 00:14:22.390 --> 00:14:25.470 align:start position:0% if you have dubs you can give subdomains of<00:14:23.080> your<00:14:23.320> dab<00:14:23.560> to<00:14:23.590> your<00:14:24.010> users<00:14:24.490> there's<00:14:25.240> the 00:14:25.470 --> 00:14:25.480 align:start position:0% of your dab to your users there's the 00:14:25.480 --> 00:14:30.840 align:start position:0% of your dab to your users there's the ENS<00:14:26.640> hands<00:14:27.640> on<00:14:27.820> for<00:14:28.180> dabs<00:14:28.420> on<00:14:29.340> the<00:14:30.340> workshop 00:14:30.840 --> 00:14:30.850 align:start position:0% ENS hands on for dabs on the workshop 00:14:30.850 --> 00:14:33.420 align:start position:0% ENS hands on for dabs on the workshop for<00:14:31.270> that<00:14:31.840> developers<00:14:32.440> that<00:14:32.710> will<00:14:33.040> teach<00:14:33.280> you 00:14:33.420 --> 00:14:33.430 align:start position:0% for that developers that will teach you 00:14:33.430 --> 00:14:36.570 align:start position:0% for that developers that will teach you how<00:14:33.580> to<00:14:33.610> do<00:14:34.410> how<00:14:35.410> many<00:14:35.590> of<00:14:35.710> you<00:14:35.830> are<00:14:35.980> interested 00:14:36.570 --> 00:14:36.580 align:start position:0% how to do how many of you are interested 00:14:36.580 --> 00:14:38.700 align:start position:0% how to do how many of you are interested including<00:14:37.210> this<00:14:37.360> kind<00:14:37.600> of<00:14:37.690> process<00:14:38.020> into<00:14:38.530> you 00:14:38.700 --> 00:14:38.710 align:start position:0% including this kind of process into you 00:14:38.710 --> 00:14:42.210 align:start position:0% including this kind of process into you adapt<00:14:39.720> okay<00:14:40.720> so<00:14:41.140> you<00:14:41.200> guys<00:14:41.560> kind<00:14:41.770> of<00:14:41.890> came<00:14:42.070> to 00:14:42.210 --> 00:14:42.220 align:start position:0% adapt okay so you guys kind of came to 00:14:42.220 --> 00:14:46.290 align:start position:0% adapt okay so you guys kind of came to the<00:14:42.340> wrong<00:14:44.280> like<00:14:45.280> there's<00:14:45.520> another<00:14:45.790> sense<00:14:46.060> but 00:14:46.290 --> 00:14:46.300 align:start position:0% the wrong like there's another sense but 00:14:46.300 --> 00:14:47.490 align:start position:0% the wrong like there's another sense but like<00:14:46.450> it's<00:14:46.600> good<00:14:46.810> that<00:14:46.960> you<00:14:47.200> said<00:14:47.230> the 00:14:47.490 --> 00:14:47.500 align:start position:0% like it's good that you said the 00:14:47.500 --> 00:14:50.790 align:start position:0% like it's good that you said the foundation<00:14:48.070> now<00:14:48.250> yeah<00:14:49.030> levered<00:14:49.450> up<00:14:49.570> then<00:14:50.380> you 00:14:50.790 --> 00:14:50.800 align:start position:0% foundation now yeah levered up then you 00:14:50.800 --> 00:14:52.110 align:start position:0% foundation now yeah levered up then you go<00:14:50.920> to<00:14:50.980> the<00:14:51.190> next<00:14:51.430> session<00:14:51.580> we<00:14:51.820> see<00:14:51.970> on<00:14:52.090> a 00:14:52.110 --> 00:14:52.120 align:start position:0% go to the next session we see on a 00:14:52.120 --> 00:14:58.830 align:start position:0% go to the next session we see on a Thursday<00:14:53.280> yeah<00:14:54.310> and<00:14:54.960> that<00:14:55.960> time<00:14:56.200> me<00:14:56.860> and<00:14:57.840> Jeff 00:14:58.830 --> 00:14:58.840 align:start position:0% Thursday yeah and that time me and Jeff 00:14:58.840 --> 00:15:02.210 align:start position:0% Thursday yeah and that time me and Jeff la<00:14:59.080> will<00:14:59.500> be<00:14:59.680> presenting<00:15:00.460> how<00:15:00.580> to<00:15:00.640> do<00:15:00.910> that<00:15:01.120> and 00:15:02.210 --> 00:15:02.220 align:start position:0% la will be presenting how to do that and 00:15:02.220 --> 00:15:06.930 align:start position:0% la will be presenting how to do that and sorry<00:15:04.470> Thursday<00:15:05.470> at<00:15:05.620> 10<00:15:05.860> a.m.<00:15:06.010> and<00:15:06.460> it's 00:15:06.930 --> 00:15:06.940 align:start position:0% sorry Thursday at 10 a.m. and it's 00:15:06.940 --> 00:15:11.040 align:start position:0% sorry Thursday at 10 a.m. and it's called<00:15:07.180> ENS<00:15:08.790> hands<00:15:09.790> on<00:15:09.910> integration<00:15:10.480> workshop 00:15:11.040 --> 00:15:11.050 align:start position:0% called ENS hands on integration workshop 00:15:11.050 --> 00:15:16.590 align:start position:0% called ENS hands on integration workshop for<00:15:11.260> developers<00:15:14.700> okay<00:15:15.700> so<00:15:15.760> yeah<00:15:16.120> the<00:15:16.330> salt 00:15:16.590 --> 00:15:16.600 align:start position:0% for developers okay so yeah the salt 00:15:16.600 --> 00:15:20.310 align:start position:0% for developers okay so yeah the salt case<00:15:16.870> status<00:15:17.170> is<00:15:17.740> I<00:15:18.520> just<00:15:18.850> yeah<00:15:19.330> so<00:15:19.570> they<00:15:19.780> did 00:15:20.310 --> 00:15:20.320 align:start position:0% case status is I just yeah so they did 00:15:20.320 --> 00:15:22.950 align:start position:0% case status is I just yeah so they did integrate<00:15:21.280> a<00:15:21.310> very<00:15:21.640> new<00:15:22.000> like<00:15:22.210> last<00:15:22.480> week<00:15:22.780> or 00:15:22.950 --> 00:15:22.960 align:start position:0% integrate a very new like last week or 00:15:22.960 --> 00:15:24.840 align:start position:0% integrate a very new like last week or something<00:15:23.320> like<00:15:23.470> so<00:15:24.040> that<00:15:24.190> if<00:15:24.340> you<00:15:24.490> create<00:15:24.820> a 00:15:24.840 --> 00:15:24.850 align:start position:0% something like so that if you create a 00:15:24.850 --> 00:15:28.440 align:start position:0% something like so that if you create a account<00:15:26.100> there's<00:15:27.100> a<00:15:27.190> section<00:15:27.550> called<00:15:27.610> ENS 00:15:28.440 --> 00:15:28.450 align:start position:0% account there's a section called ENS 00:15:28.450 --> 00:15:32.460 align:start position:0% account there's a section called ENS name<00:15:28.690> so<00:15:29.110> if<00:15:29.290> you<00:15:29.500> press<00:15:29.860> that<00:15:30.300> he<00:15:31.300> asked<00:15:32.140> you 00:15:32.460 --> 00:15:32.470 align:start position:0% name so if you press that he asked you 00:15:32.470 --> 00:15:34.380 align:start position:0% name so if you press that he asked you whether<00:15:33.430> which<00:15:33.760> like 00:15:34.380 --> 00:15:34.390 align:start position:0% whether which like 00:15:34.390 --> 00:15:36.480 align:start position:0% whether which like so<00:15:34.600> they<00:15:34.750> have<00:15:34.930> a<00:15:34.959> state<00:15:35.290> of<00:15:35.500> us<00:15:35.769> I<00:15:36.070> think 00:15:36.480 --> 00:15:36.490 align:start position:0% so they have a state of us I think 00:15:36.490 --> 00:15:39.120 align:start position:0% so they have a state of us I think status<00:15:37.300> was<00:15:37.630> too<00:15:37.930> short<00:15:38.260> or<00:15:38.470> it's<00:15:38.890> got 00:15:39.120 --> 00:15:39.130 align:start position:0% status was too short or it's got 00:15:39.130 --> 00:15:41.610 align:start position:0% status was too short or it's got squatted<00:15:39.670> I<00:15:40.060> don't<00:15:40.570> know<00:15:40.750> but<00:15:41.019> the<00:15:41.260> state<00:15:41.470> of 00:15:41.610 --> 00:15:41.620 align:start position:0% squatted I don't know but the state of 00:15:41.620 --> 00:15:44.880 align:start position:0% squatted I don't know but the state of us<00:15:41.769> sounds<00:15:42.190> good<00:15:42.399> to<00:15:42.550> eat<00:15:43.540> so<00:15:44.050> like<00:15:44.230> you<00:15:44.500> can 00:15:44.880 --> 00:15:44.890 align:start position:0% us sounds good to eat so like you can 00:15:44.890 --> 00:15:46.680 align:start position:0% us sounds good to eat so like you can basically<00:15:45.100> start<00:15:45.310> whether<00:15:46.089> that<00:15:46.300> name<00:15:46.510> is<00:15:46.660> a 00:15:46.680 --> 00:15:46.690 align:start position:0% basically start whether that name is a 00:15:46.690 --> 00:15:51.600 align:start position:0% basically start whether that name is a variable<00:15:47.230> and<00:15:47.440> if<00:15:47.890> it's<00:15:48.040> good<00:15:49.380> yeah<00:15:50.380> you<00:15:50.610> he 00:15:51.600 --> 00:15:51.610 align:start position:0% variable and if it's good yeah you he 00:15:51.610 --> 00:15:54.150 align:start position:0% variable and if it's good yeah you he asked<00:15:51.790> you<00:15:52.180> to<00:15:52.240> get<00:15:52.930> to<00:15:53.079> the<00:15:53.200> profile<00:15:53.620> then<00:15:54.010> if 00:15:54.150 --> 00:15:54.160 align:start position:0% asked you to get to the profile then if 00:15:54.160 --> 00:15:57.060 align:start position:0% asked you to get to the profile then if you<00:15:54.279> press<00:15:54.640> and<00:15:55.060> of<00:15:56.019> sorry<00:15:56.350> yeah<00:15:56.620> then<00:15:56.829> it 00:15:57.060 --> 00:15:57.070 align:start position:0% you press and of sorry yeah then it 00:15:57.070 --> 00:16:02.130 align:start position:0% you press and of sorry yeah then it takes<00:15:57.519> you<00:15:57.959> to<00:15:58.959> create<00:15:59.350> I<00:16:00.040> think<00:16:00.850> if<00:16:01.209> I<00:16:01.480> we<00:16:01.839> as 00:16:02.130 --> 00:16:02.140 align:start position:0% takes you to create I think if I we as 00:16:02.140 --> 00:16:06.690 align:start position:0% takes you to create I think if I we as long<00:16:02.380> as<00:16:02.560> I<00:16:02.680> remember<00:16:03.630> you<00:16:04.829> you<00:16:05.829> have<00:16:06.070> to<00:16:06.310> stake 00:16:06.690 --> 00:16:06.700 align:start position:0% long as I remember you you have to stake 00:16:06.700 --> 00:16:11.100 align:start position:0% long as I remember you you have to stake 10<00:16:07.390> s<00:16:07.570> and<00:16:07.870> T<00:16:09.390> for<00:16:10.390> one<00:16:10.600> year 00:16:11.100 --> 00:16:11.110 align:start position:0% 10 s and T for one year 00:16:11.110 --> 00:16:28.290 align:start position:0% 10 s and T for one year yeah<00:16:12.029> yeah<00:16:13.410> sorry<00:16:15.120> yeah<00:16:16.120> two<00:16:16.300> E's<00:16:27.060> yeah<00:16:28.060> so 00:16:28.290 --> 00:16:28.300 align:start position:0% yeah yeah sorry yeah two E's yeah so 00:16:28.300 --> 00:16:32.759 align:start position:0% yeah yeah sorry yeah two E's yeah so like<00:16:28.480> if<00:16:28.779> you<00:16:29.250> does<00:16:30.250> anyone<00:16:30.550> have<00:16:30.730> a<00:16:30.760> city<00:16:31.740> okay 00:16:32.759 --> 00:16:32.769 align:start position:0% like if you does anyone have a city okay 00:16:32.769 --> 00:16:37.949 align:start position:0% like if you does anyone have a city okay o<00:16:35.399> SN<00:16:36.399> T<00:16:36.610> for<00:16:36.760> everybody<00:16:37.120> is<00:16:37.600> that<00:16:37.720> what<00:16:37.870> you're 00:16:37.949 --> 00:16:37.959 align:start position:0% o SN T for everybody is that what you're 00:16:37.959 --> 00:16:43.410 align:start position:0% o SN T for everybody is that what you're saying<00:16:38.200> okay<00:16:39.449> yeah<00:16:41.699> yeah<00:16:42.699> so<00:16:43.000> but<00:16:43.240> I<00:16:43.269> don't 00:16:43.410 --> 00:16:43.420 align:start position:0% saying okay yeah yeah so but I don't 00:16:43.420 --> 00:16:45.150 align:start position:0% saying okay yeah yeah so but I don't know<00:16:43.600> how<00:16:43.720> to<00:16:43.779> sit<00:16:44.290> through<00:16:44.500> that<00:16:44.560> dress<00:16:44.949> but 00:16:45.150 --> 00:16:45.160 align:start position:0% know how to sit through that dress but 00:16:45.160 --> 00:16:47.639 align:start position:0% know how to sit through that dress but like<00:16:45.310> during<00:16:45.579> the<00:16:45.610> so<00:16:46.149> after<00:16:46.990> I<00:16:47.019> go<00:16:47.199> explain 00:16:47.639 --> 00:16:47.649 align:start position:0% like during the so after I go explain 00:16:47.649 --> 00:16:50.100 align:start position:0% like during the so after I go explain all<00:16:47.829> these<00:16:47.980> obvious<00:16:48.760> I<00:16:48.970> will<00:16:49.209> stop<00:16:49.810> for<00:16:50.019> like 00:16:50.100 --> 00:16:50.110 align:start position:0% all these obvious I will stop for like 00:16:50.110 --> 00:16:53.370 align:start position:0% all these obvious I will stop for like 5-10<00:16:50.320> minutes<00:16:50.920> to<00:16:51.300> do<00:16:52.300> so<00:16:52.930> that<00:16:53.050> everybody 00:16:53.370 --> 00:16:53.380 align:start position:0% 5-10 minutes to do so that everybody 00:16:53.380 --> 00:16:56.850 align:start position:0% 5-10 minutes to do so that everybody have<00:16:53.740> that<00:16:53.769> ENS<00:16:54.630> address<00:16:55.630> stage<00:16:55.990> if<00:16:56.230> you<00:16:56.290> want 00:16:56.850 --> 00:16:56.860 align:start position:0% have that ENS address stage if you want 00:16:56.860 --> 00:16:59.220 align:start position:0% have that ENS address stage if you want to<00:16:57.100> if<00:16:57.880> you<00:16:58.029> have<00:16:58.060> nothing<00:16:58.420> and<00:16:58.690> if<00:16:58.870> you<00:16:58.899> want 00:16:59.220 --> 00:16:59.230 align:start position:0% to if you have nothing and if you want 00:16:59.230 --> 00:17:01.410 align:start position:0% to if you have nothing and if you want to<00:16:59.320> download<00:16:59.620> a<00:16:59.860> status<00:17:00.550> now<00:17:00.730> now<00:17:01.000> is<00:17:01.149> the<00:17:01.240> time 00:17:01.410 --> 00:17:01.420 align:start position:0% to download a status now now is the time 00:17:01.420 --> 00:17:04.530 align:start position:0% to download a status now now is the time to<00:17:01.600> go<00:17:01.720> to<00:17:02.100> the<00:17:03.100> Google<00:17:03.670> Play<00:17:04.000> or<00:17:04.209> somewhere 00:17:04.530 --> 00:17:04.540 align:start position:0% to go to the Google Play or somewhere 00:17:04.540 --> 00:17:06.659 align:start position:0% to go to the Google Play or somewhere and<00:17:04.780> they<00:17:04.900> start<00:17:05.140> downloading<00:17:05.589> but<00:17:06.160> yeah<00:17:06.400> so 00:17:06.659 --> 00:17:06.669 align:start position:0% and they start downloading but yeah so 00:17:06.669 --> 00:17:10.799 align:start position:0% and they start downloading but yeah so if<00:17:07.089> you're<00:17:07.270> gonna<00:17:07.360> go<00:17:07.540> for<00:17:07.720> this<00:17:07.900> mobile<00:17:09.780> yeah 00:17:10.799 --> 00:17:10.809 align:start position:0% if you're gonna go for this mobile yeah 00:17:10.809 --> 00:17:22.699 align:start position:0% if you're gonna go for this mobile yeah route<00:17:11.350> there's<00:17:12.339> a<00:17:12.429> sin<00:17:12.730> T<00:17:12.910> for<00:17:13.510> you<00:17:13.660> okay<00:17:17.640> okay 00:17:22.699 --> 00:17:22.709 align:start position:0% 00:17:22.709 --> 00:17:27.179 align:start position:0% yeah<00:17:23.709> so<00:17:24.189> there's<00:17:24.399> a<00:17:24.520> yeah<00:17:24.899> support<00:17:25.959> SNT<00:17:26.799> I'm 00:17:27.179 --> 00:17:27.189 align:start position:0% yeah so there's a yeah support SNT I'm 00:17:27.189 --> 00:17:34.110 align:start position:0% yeah so there's a yeah support SNT I'm sorry<00:17:27.429> stitches<00:17:29.429> okay<00:17:30.429> so<00:17:30.899> yeah<00:17:31.899> so<00:17:32.110> once<00:17:33.120> you 00:17:34.110 --> 00:17:34.120 align:start position:0% sorry stitches okay so yeah so once you 00:17:34.120 --> 00:17:36.090 align:start position:0% sorry stitches okay so yeah so once you went<00:17:34.330> through<00:17:34.510> you<00:17:35.080> want<00:17:35.200> to<00:17:35.350> make<00:17:35.679> sure<00:17:35.710> that 00:17:36.090 --> 00:17:36.100 align:start position:0% went through you want to make sure that 00:17:36.100 --> 00:17:37.919 align:start position:0% went through you want to make sure that you<00:17:36.220> actually<00:17:36.549> got<00:17:36.730> it<00:17:36.760> right<00:17:37.090> so<00:17:37.120> wait<00:17:37.539> else 00:17:37.919 --> 00:17:37.929 align:start position:0% you actually got it right so wait else 00:17:37.929 --> 00:17:41.639 align:start position:0% you actually got it right so wait else can<00:17:38.289> you<00:17:38.409> see<00:17:38.620> is<00:17:38.830> fast<00:17:39.700> place<00:17:40.260> easier<00:17:41.260> one<00:17:41.470> is 00:17:41.639 --> 00:17:41.649 align:start position:0% can you see is fast place easier one is 00:17:41.649 --> 00:17:45.240 align:start position:0% can you see is fast place easier one is a<00:17:41.679> easy<00:17:42.070> scan<00:17:42.399> so<00:17:43.000> users<00:17:43.299> can<00:17:43.390> usually<00:17:44.250> how 00:17:45.240 --> 00:17:45.250 align:start position:0% a easy scan so users can usually how 00:17:45.250 --> 00:17:48.480 align:start position:0% a easy scan so users can usually how many<00:17:45.669> who<00:17:46.450> hasn't<00:17:46.870> accessed<00:17:47.649> either<00:17:48.159> scan 00:17:48.480 --> 00:17:48.490 align:start position:0% many who hasn't accessed either scan 00:17:48.490 --> 00:17:52.500 align:start position:0% many who hasn't accessed either scan before<00:17:49.799> two<00:17:50.799> people<00:17:51.250> three<00:17:51.610> people<00:17:51.700> okay<00:17:52.299> so 00:17:52.500 --> 00:17:52.510 align:start position:0% before two people three people okay so 00:17:52.510 --> 00:17:55.200 align:start position:0% before two people three people okay so you<00:17:52.720> scan<00:17:53.169> is<00:17:53.409> a<00:17:53.470> place<00:17:53.890> where<00:17:54.159> it<00:17:54.700> has<00:17:54.880> all<00:17:55.029> the 00:17:55.200 --> 00:17:55.210 align:start position:0% you scan is a place where it has all the 00:17:55.210 --> 00:17:57.060 align:start position:0% you scan is a place where it has all the information<00:17:55.570> about<00:17:55.870> like<00:17:56.230> you<00:17:56.350> know<00:17:56.380> poaching 00:17:57.060 --> 00:17:57.070 align:start position:0% information about like you know poaching 00:17:57.070 --> 00:17:58.409 align:start position:0% information about like you know poaching activities<00:17:57.549> where<00:17:57.820> you<00:17:57.850> can<00:17:58.059> find<00:17:58.299> a 00:17:58.409 --> 00:17:58.419 align:start position:0% activities where you can find a 00:17:58.419 --> 00:18:01.039 align:start position:0% activities where you can find a transaction<00:17:58.779> who<00:17:59.200> sent<00:17:59.409> to<00:17:59.500> you<00:17:59.710> and<00:17:59.970> usually 00:18:01.039 --> 00:18:01.049 align:start position:0% transaction who sent to you and usually 00:18:01.049 --> 00:18:04.200 align:start position:0% transaction who sent to you and usually probably<00:18:02.049> copy<00:18:02.559> and<00:18:02.740> paste<00:18:02.919> same<00:18:03.610> address<00:18:04.000> but 00:18:04.200 --> 00:18:04.210 align:start position:0% probably copy and paste same address but 00:18:04.210 --> 00:18:06.720 align:start position:0% probably copy and paste same address but now<00:18:04.539> you<00:18:05.020> can<00:18:05.260> search<00:18:05.950> with<00:18:06.220> this<00:18:06.399> so<00:18:06.549> if<00:18:06.610> you 00:18:06.720 --> 00:18:06.730 align:start position:0% now you can search with this so if you 00:18:06.730 --> 00:18:10.769 align:start position:0% now you can search with this so if you put<00:18:06.909> my<00:18:07.029> token<00:18:07.299> dog<00:18:07.419> is<00:18:07.710> and<00:18:08.710> it<00:18:09.669> goes<00:18:09.760> to<00:18:10.210> if 00:18:10.769 --> 00:18:10.779 align:start position:0% put my token dog is and it goes to if 00:18:10.779 --> 00:18:15.419 align:start position:0% put my token dog is and it goes to if you<00:18:10.899> look<00:18:11.140> at<00:18:11.230> the<00:18:11.289> URL<00:18:13.080> point<00:18:14.169> yeah<00:18:14.770> it's<00:18:15.100> now 00:18:15.419 --> 00:18:15.429 align:start position:0% you look at the URL point yeah it's now 00:18:15.429 --> 00:18:18.360 align:start position:0% you look at the URL point yeah it's now doing<00:18:15.970> yes<00:18:16.210> look<00:18:16.480> up<00:18:16.690> came<00:18:17.559> a<00:18:17.770> token<00:18:18.070> dog<00:18:18.190> is 00:18:18.360 --> 00:18:18.370 align:start position:0% doing yes look up came a token dog is 00:18:18.370 --> 00:18:22.740 align:start position:0% doing yes look up came a token dog is and<00:18:18.669> next<00:18:19.770> sorry<00:18:20.770> go<00:18:20.980> like<00:18:21.669> yeah<00:18:22.120> and<00:18:22.419> this<00:18:22.570> one 00:18:22.740 --> 00:18:22.750 align:start position:0% and next sorry go like yeah and this one 00:18:22.750 --> 00:18:25.049 align:start position:0% and next sorry go like yeah and this one says<00:18:22.899> a<00:18:22.960> unit<00:18:23.289> name<00:18:23.470> address<00:18:23.710> for<00:18:24.429> this<00:18:24.520> one<00:18:24.820> is 00:18:25.049 --> 00:18:25.059 align:start position:0% says a unit name address for this one is 00:18:25.059 --> 00:18:27.630 align:start position:0% says a unit name address for this one is under<00:18:26.020> this<00:18:26.380> one<00:18:26.590> so<00:18:26.770> that<00:18:26.919> you<00:18:27.070> can<00:18:27.250> see<00:18:27.429> that 00:18:27.630 --> 00:18:27.640 align:start position:0% under this one so that you can see that 00:18:27.640 --> 00:18:30.769 align:start position:0% under this one so that you can see that information<00:18:27.970> who<00:18:28.570> on<00:18:28.750> the<00:18:29.100> next<00:18:30.100> piece<00:18:30.279> and 00:18:30.769 --> 00:18:30.779 align:start position:0% information who on the next piece and 00:18:30.779 --> 00:18:34.139 align:start position:0% information who on the next piece and this<00:18:31.779> is<00:18:32.049> in<00:18:32.380> the<00:18:32.529> case<00:18:32.770> of<00:18:33.070> meta<00:18:33.309> mask<00:18:33.610> instead 00:18:34.139 --> 00:18:34.149 align:start position:0% this is in the case of meta mask instead 00:18:34.149 --> 00:18:36.330 align:start position:0% this is in the case of meta mask instead of<00:18:34.390> again<00:18:35.020> copy<00:18:35.260> and<00:18:35.440> paste<00:18:35.620> the<00:18:35.740> same<00:18:35.890> address 00:18:36.330 --> 00:18:36.340 align:start position:0% of again copy and paste the same address 00:18:36.340 --> 00:18:38.880 align:start position:0% of again copy and paste the same address you<00:18:36.850> can<00:18:37.029> look<00:18:37.210> up<00:18:37.450> my<00:18:37.659> token<00:18:38.020> here<00:18:38.590> and<00:18:38.770> they 00:18:38.880 --> 00:18:38.890 align:start position:0% you can look up my token here and they 00:18:38.890 --> 00:18:41.940 align:start position:0% you can look up my token here and they basically<00:18:40.080> replaced<00:18:41.080> with<00:18:41.260> a<00:18:41.380> serum<00:18:41.649> address 00:18:41.940 --> 00:18:41.950 align:start position:0% basically replaced with a serum address 00:18:41.950 --> 00:18:45.090 align:start position:0% basically replaced with a serum address this<00:18:42.820> is<00:18:42.940> one<00:18:43.120> of<00:18:43.149> the<00:18:43.360> very<00:18:43.779> first<00:18:44.100> basic 00:18:45.090 --> 00:18:45.100 align:start position:0% this is one of the very first basic 00:18:45.100 --> 00:18:48.840 align:start position:0% this is one of the very first basic users<00:18:45.700> to<00:18:46.450> give<00:18:46.659> convenience<00:18:47.289> to<00:18:47.500> send<00:18:47.950> to<00:18:48.820> a 00:18:48.840 --> 00:18:48.850 align:start position:0% users to give convenience to send to a 00:18:48.850 --> 00:18:51.570 align:start position:0% users to give convenience to send to a name<00:18:49.149> instead<00:18:49.480> of<00:18:49.600> an<00:18:49.720> address<00:18:50.049> and<00:18:50.580> some 00:18:51.570 --> 00:18:51.580 align:start position:0% name instead of an address and some 00:18:51.580 --> 00:18:54.930 align:start position:0% name instead of an address and some wallets<00:18:52.409> already<00:18:53.409> resolved<00:18:54.039> transform<00:18:54.549> then 00:18:54.930 --> 00:18:54.940 align:start position:0% wallets already resolved transform then 00:18:54.940 --> 00:18:58.320 align:start position:0% wallets already resolved transform then the<00:18:55.360> name<00:18:56.289> into<00:18:56.710> the<00:18:57.309> hash<00:18:57.640> of<00:18:57.909> the<00:18:58.059> address 00:18:58.320 --> 00:18:58.330 align:start position:0% the name into the hash of the address 00:18:58.330 --> 00:19:03.389 align:start position:0% the name into the hash of the address that<00:18:58.539> it<00:18:58.659> points<00:18:59.140> to<00:19:00.960> and<00:19:02.070> yeah<00:19:03.070> same<00:19:03.370> thing 00:19:03.389 --> 00:19:03.399 align:start position:0% that it points to and yeah same thing 00:19:03.399 --> 00:19:09.470 align:start position:0% that it points to and yeah same thing for<00:19:03.789> my<00:19:04.210> crypto<00:19:07.020> okay<00:19:08.020> next 00:19:09.470 --> 00:19:09.480 align:start position:0% for my crypto okay next 00:19:09.480 --> 00:19:14.600 align:start position:0% for my crypto okay next yes<00:19:10.480> so<00:19:10.899> you<00:19:12.390> have<00:19:13.390> no<00:19:13.630> clue<00:19:13.870> how<00:19:14.020> to<00:19:14.080> get 00:19:14.600 --> 00:19:14.610 align:start position:0% yes so you have no clue how to get 00:19:14.610 --> 00:19:19.039 align:start position:0% yes so you have no clue how to get subdomain<00:19:16.200> raise<00:19:17.200> your<00:19:17.320> hand<00:19:17.529> who<00:19:18.490> doesn't 00:19:19.039 --> 00:19:19.049 align:start position:0% subdomain raise your hand who doesn't 00:19:19.049 --> 00:19:22.110 align:start position:0% subdomain raise your hand who doesn't know<00:19:20.049> how<00:19:20.230> to<00:19:20.260> get<00:19:20.500> a<00:19:20.529> subdomain<00:19:20.830> okay<00:19:21.490> so<00:19:21.909> for 00:19:22.110 --> 00:19:22.120 align:start position:0% know how to get a subdomain okay so for 00:19:22.120 --> 00:19:24.720 align:start position:0% know how to get a subdomain okay so for these<00:19:22.299> people<00:19:22.720> all<00:19:23.559> the<00:19:23.950> people<00:19:23.980> around<00:19:24.460> you 00:19:24.720 --> 00:19:24.730 align:start position:0% these people all the people around you 00:19:24.730 --> 00:19:27.830 align:start position:0% these people all the people around you knows<00:19:25.000> how<00:19:25.029> to<00:19:25.270> get<00:19:25.480> it<00:19:25.659> so<00:19:25.990> they<00:19:26.200> can<00:19:26.380> help<00:19:26.529> you 00:19:27.830 --> 00:19:27.840 align:start position:0% knows how to get it so they can help you 00:19:27.840 --> 00:19:30.690 align:start position:0% knows how to get it so they can help you so<00:19:28.840> shall<00:19:29.350> we<00:19:29.409> just<00:19:29.440> spend<00:19:29.889> five<00:19:29.950> ten<00:19:30.340> minutes 00:19:30.690 --> 00:19:30.700 align:start position:0% so shall we just spend five ten minutes 00:19:30.700 --> 00:19:33.520 align:start position:0% so shall we just spend five ten minutes good<00:19:31.480> okay 00:19:33.520 --> 00:19:33.530 align:start position:0% good okay 00:19:33.530 --> 00:19:37.000 align:start position:0% good okay do<00:19:33.890> it<00:19:34.010> so<00:19:34.640> the<00:19:35.330> three<00:19:35.810> to<00:19:36.110> remind<00:19:36.440> people<00:19:36.590> the 00:19:37.000 --> 00:19:37.010 align:start position:0% do it so the three to remind people the 00:19:37.010 --> 00:19:39.460 align:start position:0% do it so the three to remind people the three<00:19:37.340> or<00:19:37.910> the<00:19:38.150> two<00:19:38.330> versions<00:19:38.870> that<00:19:39.140> you<00:19:39.200> can 00:19:39.460 --> 00:19:39.470 align:start position:0% three or the two versions that you can 00:19:39.470 --> 00:19:41.410 align:start position:0% three or the two versions that you can try<00:19:39.710> now<00:19:39.950> three<00:19:40.220> versions<00:19:40.430> that<00:19:40.640> you<00:19:40.700> can<00:19:40.790> try 00:19:41.410 --> 00:19:41.420 align:start position:0% try now three versions that you can try 00:19:41.420 --> 00:19:42.400 align:start position:0% try now three versions that you can try now<00:19:41.600> to<00:19:41.660> get<00:19:41.870> a<00:19:41.900> sub-domain 00:19:42.400 --> 00:19:42.410 align:start position:0% now to get a sub-domain 00:19:42.410 --> 00:19:45.220 align:start position:0% now to get a sub-domain is<00:19:42.590> either<00:19:43.280> with<00:19:43.610> status<00:19:44.120> you<00:19:44.630> go<00:19:44.810> down<00:19:45.020> and 00:19:45.220 --> 00:19:45.230 align:start position:0% is either with status you go down and 00:19:45.230 --> 00:19:48.880 align:start position:0% is either with status you go down and download<00:19:45.590> status<00:19:45.860> or<00:19:46.480> with<00:19:47.480> get<00:19:47.990> coin<00:19:48.230> if<00:19:48.530> you 00:19:48.880 --> 00:19:48.890 align:start position:0% download status or with get coin if you 00:19:48.890 --> 00:19:50.470 align:start position:0% download status or with get coin if you have<00:19:49.130> a<00:19:49.160> github<00:19:49.550> account<00:19:49.970> and<00:19:50.060> you<00:19:50.180> want<00:19:50.330> to 00:19:50.470 --> 00:19:50.480 align:start position:0% have a github account and you want to 00:19:50.480 --> 00:19:52.690 align:start position:0% have a github account and you want to get<00:19:50.720> your<00:19:50.900> subdomain<00:19:51.230> with<00:19:51.500> git<00:19:51.710> coin<00:19:51.920> or<00:19:52.220> you 00:19:52.690 --> 00:19:52.700 align:start position:0% get your subdomain with git coin or you 00:19:52.700 --> 00:19:56.080 align:start position:0% get your subdomain with git coin or you can<00:19:52.880> go<00:19:53.030> on<00:19:53.240> now<00:19:53.450> dot<00:19:54.050> e<00:19:54.230> NS<00:19:54.700> domains<00:19:55.700> and<00:19:56.030> you 00:19:56.080 --> 00:19:56.090 align:start position:0% can go on now dot e NS domains and you 00:19:56.090 --> 00:19:58.840 align:start position:0% can go on now dot e NS domains and you look<00:19:57.050> for<00:19:57.290> for<00:19:57.650> a<00:19:57.710> domain<00:19:57.950> there<00:19:58.190> if<00:19:58.460> you<00:19:58.670> have 00:19:58.840 --> 00:19:58.850 align:start position:0% look for for a domain there if you have 00:19:58.850 --> 00:20:03.880 align:start position:0% look for for a domain there if you have meta<00:19:59.720> mask<00:19:59.960> or<00:20:00.140> a<00:20:00.200> wallet<00:20:00.440> that<00:20:00.950> has<00:20:02.710> that<00:20:03.710> has 00:20:03.880 --> 00:20:03.890 align:start position:0% meta mask or a wallet that has that has 00:20:03.890 --> 00:20:07.570 align:start position:0% meta mask or a wallet that has that has ether<00:20:04.600> so<00:20:05.600> we<00:20:05.840> doing<00:20:05.990> it<00:20:06.260> everybody<00:20:06.770> has<00:20:07.130> a 00:20:07.570 --> 00:20:07.580 align:start position:0% ether so we doing it everybody has a 00:20:07.580 --> 00:20:23.310 align:start position:0% ether so we doing it everybody has a domain<00:20:08.180> already<00:20:18.640> question-there<00:20:19.640> just<00:20:20.390> go 00:20:23.310 --> 00:20:23.320 align:start position:0% 00:20:23.320 --> 00:20:33.740 align:start position:0% okay<00:20:24.320> yeah<00:20:24.530> a<00:20:24.740> question<00:20:25.070> there<00:20:25.460> yes 00:20:33.740 --> 00:20:33.750 align:start position:0% 00:20:33.750 --> 00:20:40.320 align:start position:0% sorry-sorry<00:20:34.750> speak<00:20:35.410> i<00:20:35.590> speak<00:20:35.620> up<00:20:39.000> 12<00:20:40.000> days<00:20:40.150> ago 00:20:40.320 --> 00:20:40.330 align:start position:0% sorry-sorry speak i speak up 12 days ago 00:20:40.330 --> 00:20:42.840 align:start position:0% sorry-sorry speak i speak up 12 days ago if<00:20:41.080> i<00:20:41.200> didn't<00:20:41.440> registered<00:20:41.920> you<00:20:42.460> know<00:20:42.580> or<00:20:42.820> i 00:20:42.840 --> 00:20:42.850 align:start position:0% if i didn't registered you know or i 00:20:42.850 --> 00:20:48.440 align:start position:0% if i didn't registered you know or i didn't<00:20:43.240> claim<00:20:43.660> it<00:20:44.130> is<00:20:45.130> it's<00:20:45.370> gone 00:20:48.440 --> 00:20:48.450 align:start position:0% 00:20:48.450 --> 00:20:52.200 align:start position:0% you<00:20:49.450> got<00:20:49.960> a<00:20:50.260> domain<00:20:50.560> but<00:20:51.490> you<00:20:51.610> didn't<00:20:51.910> register 00:20:52.200 --> 00:20:52.210 align:start position:0% you got a domain but you didn't register 00:20:52.210 --> 00:20:54.150 align:start position:0% you got a domain but you didn't register it<00:20:52.660> you<00:20:52.690> didn't<00:20:53.080> claim<00:20:53.320> it<00:20:53.380> so<00:20:53.710> yeah<00:20:53.860> there's<00:20:54.070> a 00:20:54.150 --> 00:20:54.160 align:start position:0% it you didn't claim it so yeah there's a 00:20:54.160 --> 00:20:55.770 align:start position:0% it you didn't claim it so yeah there's a lot<00:20:54.310> of<00:20:54.490> you<00:20:54.760> probably<00:20:55.180> didn't<00:20:55.450> get<00:20:55.570> you 00:20:55.770 --> 00:20:55.780 align:start position:0% lot of you probably didn't get you 00:20:55.780 --> 00:20:58.200 align:start position:0% lot of you probably didn't get you probably<00:20:56.050> won't<00:20:56.170> want<00:20:56.380> it<00:20:56.610> did<00:20:57.610> you<00:20:57.790> reveal 00:20:58.200 --> 00:20:58.210 align:start position:0% probably won't want it did you reveal 00:20:58.210 --> 00:21:02.910 align:start position:0% probably won't want it did you reveal your<00:20:58.480> bid<00:21:00.480> okay<00:21:01.480> if<00:21:01.780> you<00:21:01.990> bid<00:21:02.320> but<00:21:02.530> you<00:21:02.620> didn't 00:21:02.910 --> 00:21:02.920 align:start position:0% your bid okay if you bid but you didn't 00:21:02.920 --> 00:21:05.100 align:start position:0% your bid okay if you bid but you didn't reveal<00:21:03.160> then<00:21:04.030> you've<00:21:04.270> lost<00:21:04.600> your<00:21:04.810> bid<00:21:04.960> I'm 00:21:05.100 --> 00:21:05.110 align:start position:0% reveal then you've lost your bid I'm 00:21:05.110 --> 00:21:08.190 align:start position:0% reveal then you've lost your bid I'm afraid<00:21:05.410> if<00:21:05.620> the<00:21:06.120> if<00:21:07.120> you<00:21:07.390> revealed<00:21:07.750> but<00:21:08.080> you 00:21:08.190 --> 00:21:08.200 align:start position:0% afraid if the if you revealed but you 00:21:08.200 --> 00:21:10.020 align:start position:0% afraid if the if you revealed but you haven't<00:21:08.380> finalized<00:21:08.980> the<00:21:09.190> option<00:21:09.520> then<00:21:09.820> that's 00:21:10.020 --> 00:21:10.030 align:start position:0% haven't finalized the option then that's 00:21:10.030 --> 00:21:11.460 align:start position:0% haven't finalized the option then that's fine<00:21:10.270> you<00:21:10.510> can<00:21:10.540> wait<00:21:10.780> as<00:21:10.930> long<00:21:10.960> as<00:21:11.110> you<00:21:11.230> want 00:21:11.460 --> 00:21:11.470 align:start position:0% fine you can wait as long as you want 00:21:11.470 --> 00:21:13.440 align:start position:0% fine you can wait as long as you want and<00:21:11.680> you'll<00:21:12.160> still<00:21:12.340> have<00:21:12.550> it<00:21:12.670> so<00:21:12.850> the<00:21:13.240> thing<00:21:13.420> to 00:21:13.440 --> 00:21:13.450 align:start position:0% and you'll still have it so the thing to 00:21:13.450 --> 00:21:14.820 align:start position:0% and you'll still have it so the thing to do<00:21:13.630> would<00:21:13.750> be<00:21:13.810> to<00:21:13.900> check<00:21:14.170> the<00:21:14.290> name<00:21:14.410> and<00:21:14.590> ethos 00:21:14.820 --> 00:21:14.830 align:start position:0% do would be to check the name and ethos 00:21:14.830 --> 00:21:16.380 align:start position:0% do would be to check the name and ethos can<00:21:14.890> see<00:21:15.340> what<00:21:15.490> it<00:21:15.610> says<00:21:15.790> about<00:21:15.820> the<00:21:16.210> name 00:21:16.380 --> 00:21:16.390 align:start position:0% can see what it says about the name 00:21:16.390 --> 00:21:18.120 align:start position:0% can see what it says about the name whether<00:21:16.690> there<00:21:16.930> was<00:21:16.990> a<00:21:17.050> reveal<00:21:17.380> and<00:21:17.980> then 00:21:18.120 --> 00:21:18.130 align:start position:0% whether there was a reveal and then 00:21:18.130 --> 00:21:30.350 align:start position:0% whether there was a reveal and then you'll<00:21:18.280> know<00:21:18.430> what<00:21:18.460> state<00:21:18.880> you're<00:21:19.030> in<00:21:24.270> okay 00:21:30.350 --> 00:21:30.360 align:start position:0% 00:21:30.360 --> 00:21:32.460 align:start position:0% it's<00:21:31.360> confusing<00:21:31.810> for<00:21:32.170> people 00:21:32.460 --> 00:21:32.470 align:start position:0% it's confusing for people 00:21:32.470 --> 00:21:38.570 align:start position:0% it's confusing for people any<00:21:32.800> other<00:21:33.040> questions<00:21:35.370> anybody 00:21:38.570 --> 00:21:38.580 align:start position:0% 00:21:38.580 --> 00:21:40.530 align:start position:0% troubleshooting<00:21:39.580> yeah<00:21:39.790> yeah<00:21:40.000> sure<00:21:40.210> we<00:21:40.450> are 00:21:40.530 --> 00:21:40.540 align:start position:0% troubleshooting yeah yeah sure we are 00:21:40.540 --> 00:21:42.930 align:start position:0% troubleshooting yeah yeah sure we are here<00:21:40.780> for<00:21:40.930> helping<00:21:41.380> you<00:21:41.500> and<00:21:41.860> that<00:21:42.010> by<00:21:42.580> the<00:21:42.640> way 00:21:42.930 --> 00:21:42.940 align:start position:0% here for helping you and that by the way 00:21:42.940 --> 00:21:44.910 align:start position:0% here for helping you and that by the way yeah<00:21:43.090> help<00:21:43.840> it<00:21:43.990> and<00:21:44.110> there<00:21:44.320> by<00:21:44.470> the<00:21:44.530> way<00:21:44.680> who 00:21:44.910 --> 00:21:44.920 align:start position:0% yeah help it and there by the way who 00:21:44.920 --> 00:21:48.780 align:start position:0% yeah help it and there by the way who already<00:21:45.280> have<00:21:45.610> ENS<00:21:46.620> names<00:21:47.620> and<00:21:48.340> I<00:21:48.430> can<00:21:48.670> give 00:21:48.780 --> 00:21:48.790 align:start position:0% already have ENS names and I can give 00:21:48.790 --> 00:21:51.390 align:start position:0% already have ENS names and I can give you<00:21:48.820> the<00:21:49.260> sticker<00:21:50.260> and<00:21:50.440> then<00:21:50.770> you<00:21:50.830> can<00:21:51.010> write 00:21:51.390 --> 00:21:51.400 align:start position:0% you the sticker and then you can write 00:21:51.400 --> 00:21:57.000 align:start position:0% you the sticker and then you can write down<00:21:51.460> names<00:21:51.880> and<00:21:53.430> yes<00:21:55.170> where<00:21:56.170> do<00:21:56.320> we<00:21:56.440> start 00:21:57.000 --> 00:21:57.010 align:start position:0% down names and yes where do we start 00:21:57.010 --> 00:21:59.130 align:start position:0% down names and yes where do we start a<00:21:57.040> common<00:21:57.580> question<00:21:57.700> either<00:21:58.480> one<00:21:58.870> of<00:21:58.900> these 00:21:59.130 --> 00:21:59.140 align:start position:0% a common question either one of these 00:21:59.140 --> 00:22:07.110 align:start position:0% a common question either one of these three<00:21:59.500> things<00:22:04.410> there<00:22:05.410> is<00:22:05.560> a<00:22:05.850> probably<00:22:06.850> get 00:22:07.110 --> 00:22:07.120 align:start position:0% three things there is a probably get 00:22:07.120 --> 00:22:09.840 align:start position:0% three things there is a probably get coin<00:22:07.360> dot<00:22:07.660> cos<00:22:07.930> slash<00:22:08.410> ENS<00:22:09.070> try<00:22:09.460> that<00:22:09.700> one 00:22:09.840 --> 00:22:09.850 align:start position:0% coin dot cos slash ENS try that one 00:22:09.850 --> 00:22:14.670 align:start position:0% coin dot cos slash ENS try that one there<00:22:10.360> should<00:22:10.570> be<00:22:11.730> you<00:22:12.730> have<00:22:12.910> a<00:22:12.960> yes<00:22:13.960> okay<00:22:14.620> so 00:22:14.670 --> 00:22:14.680 align:start position:0% there should be you have a yes okay so 00:22:14.680 --> 00:22:19.620 align:start position:0% there should be you have a yes okay so it's<00:22:14.950> get<00:22:15.280> coin<00:22:15.640> dot<00:22:16.030> coal<00:22:16.480> slash<00:22:17.350> ENS<00:22:18.270> we<00:22:19.270> can 00:22:19.620 --> 00:22:19.630 align:start position:0% it's get coin dot coal slash ENS we can 00:22:19.630 --> 00:22:22.440 align:start position:0% it's get coin dot coal slash ENS we can probably<00:22:19.990> put<00:22:20.260> that<00:22:20.290> up<00:22:20.650> there<00:22:20.950> a<00:22:21.670> particular 00:22:22.440 --> 00:22:22.450 align:start position:0% probably put that up there a particular 00:22:22.450 --> 00:22:24.870 align:start position:0% probably put that up there a particular how-to<00:22:23.020> for<00:22:23.830> following<00:22:24.370> the<00:22:24.490> meta<00:22:24.670> mask 00:22:24.870 --> 00:22:24.880 align:start position:0% how-to for following the meta mask 00:22:24.880 --> 00:22:27.960 align:start position:0% how-to for following the meta mask instructions<00:22:25.600> to<00:22:25.900> register<00:22:26.380> the<00:22:26.560> domain<00:22:27.370> we 00:22:27.960 --> 00:22:27.970 align:start position:0% instructions to register the domain we 00:22:27.970 --> 00:22:29.910 align:start position:0% instructions to register the domain we are<00:22:28.000> currently<00:22:28.690> on<00:22:29.050> the<00:22:29.110> process<00:22:29.740> of 00:22:29.910 --> 00:22:29.920 align:start position:0% are currently on the process of 00:22:29.920 --> 00:22:34.130 align:start position:0% are currently on the process of redesigning<00:22:30.490> the<00:22:31.300> whole<00:22:32.460> manager<00:22:33.460> and 00:22:34.130 --> 00:22:34.140 align:start position:0% redesigning the whole manager and 00:22:34.140 --> 00:22:36.960 align:start position:0% redesigning the whole manager and hopefully<00:22:35.140> you<00:22:35.560> don't<00:22:35.830> need<00:22:36.190> instructions 00:22:36.960 --> 00:22:36.970 align:start position:0% hopefully you don't need instructions 00:22:36.970 --> 00:22:41.280 align:start position:0% hopefully you don't need instructions which<00:22:37.210> is<00:22:37.360> good<00:22:37.660> design<00:22:37.900> and<00:22:38.640> but<00:22:39.640> the<00:22:40.290> final 00:22:41.280 --> 00:22:41.290 align:start position:0% which is good design and but the final 00:22:41.290 --> 00:22:43.370 align:start position:0% which is good design and but the final manager<00:22:41.710> is<00:22:41.860> not<00:22:42.040> out 00:22:43.370 --> 00:22:43.380 align:start position:0% manager is not out 00:22:43.380 --> 00:22:47.180 align:start position:0% manager is not out we<00:22:44.010> are<00:22:44.190> releasing<00:22:44.970> in<00:22:45.450> little<00:22:45.810> bits<00:22:46.080> bits<00:22:46.470> so 00:22:47.180 --> 00:22:47.190 align:start position:0% we are releasing in little bits bits so 00:22:47.190 --> 00:22:49.550 align:start position:0% we are releasing in little bits bits so if<00:22:47.340> I<00:22:47.490> if<00:22:47.850> I<00:22:48.000> want<00:22:48.180> to<00:22:48.270> eat<00:22:48.420> a<00:22:48.600> da<00:22:48.810> teef<00:22:49.080> domain 00:22:49.550 --> 00:22:49.560 align:start position:0% if I if I want to eat a da teef domain 00:22:49.560 --> 00:22:51.380 align:start position:0% if I if I want to eat a da teef domain tonight<00:22:49.770> I<00:22:49.950> can't<00:22:50.310> get<00:22:50.490> it<00:22:50.610> until<00:22:50.670> the<00:22:51.030> yeah 00:22:51.380 --> 00:22:51.390 align:start position:0% tonight I can't get it until the yeah 00:22:51.390 --> 00:22:55.130 align:start position:0% tonight I can't get it until the yeah you<00:22:51.450> you<00:22:52.140> can<00:22:52.440> go<00:22:52.920> tonight<00:22:53.280> to<00:22:54.090> get<00:22:54.360> a<00:22:54.390> Dottie's 00:22:55.130 --> 00:22:55.140 align:start position:0% you you can go tonight to get a Dottie's 00:22:55.140 --> 00:22:58.490 align:start position:0% you you can go tonight to get a Dottie's domain<00:22:55.530> the<00:22:56.220> suggested<00:22:57.020> versions<00:22:58.020> right<00:22:58.320> now 00:22:58.490 --> 00:22:58.500 align:start position:0% domain the suggested versions right now 00:22:58.500 --> 00:23:00.890 align:start position:0% domain the suggested versions right now are<00:22:58.860> either<00:22:59.280> through<00:22:59.610> my<00:22:59.880> ether<00:23:00.240> wallet<00:23:00.690> it 00:23:00.890 --> 00:23:00.900 align:start position:0% are either through my ether wallet it 00:23:00.900 --> 00:23:04.580 align:start position:0% are either through my ether wallet it has<00:23:01.140> a<00:23:01.580> process<00:23:02.580> that<00:23:02.820> works<00:23:03.060> my<00:23:03.750> crypto<00:23:04.230> had 00:23:04.580 --> 00:23:04.590 align:start position:0% has a process that works my crypto had 00:23:04.590 --> 00:23:08.510 align:start position:0% has a process that works my crypto had it<00:23:04.800> too<00:23:05.040> it's<00:23:05.430> very<00:23:05.760> similar<00:23:06.060> or<00:23:06.810> on<00:23:07.590> mobile 00:23:08.510 --> 00:23:08.520 align:start position:0% it too it's very similar or on mobile 00:23:08.520 --> 00:23:11.110 align:start position:0% it too it's very similar or on mobile I<00:23:08.550> am<00:23:08.790> token<00:23:09.300> is<00:23:09.540> a<00:23:09.600> good<00:23:10.260> process<00:23:10.800> as<00:23:10.920> well 00:23:11.110 --> 00:23:11.120 align:start position:0% I am token is a good process as well 00:23:11.120 --> 00:23:14.960 align:start position:0% I am token is a good process as well there<00:23:12.120> are<00:23:12.330> also<00:23:12.630> other<00:23:13.190> services<00:23:14.190> who<00:23:14.550> help 00:23:14.960 --> 00:23:14.970 align:start position:0% there are also other services who help 00:23:14.970 --> 00:23:18.710 align:start position:0% there are also other services who help you<00:23:15.450> or<00:23:15.720> help<00:23:15.960> users<00:23:16.400> by<00:23:17.400> a<00:23:17.430> subdomain<00:23:18.090> they 00:23:18.710 --> 00:23:18.720 align:start position:0% you or help users by a subdomain they 00:23:18.720 --> 00:23:20.870 align:start position:0% you or help users by a subdomain they are<00:23:18.930> a<00:23:18.960> centralized<00:23:19.740> solution<00:23:20.280> so<00:23:20.610> that<00:23:20.760> you 00:23:20.870 --> 00:23:20.880 align:start position:0% are a centralized solution so that you 00:23:20.880 --> 00:23:23.990 align:start position:0% are a centralized solution so that you simple<00:23:21.270> put<00:23:22.260> and<00:23:22.560> pay<00:23:23.280> with<00:23:23.430> a<00:23:23.490> credit<00:23:23.670> card 00:23:23.990 --> 00:23:24.000 align:start position:0% simple put and pay with a credit card 00:23:24.000 --> 00:23:27.230 align:start position:0% simple put and pay with a credit card and<00:23:24.240> they<00:23:24.510> take<00:23:24.870> care<00:23:25.110> of<00:23:25.170> everything<00:23:25.940> if<00:23:26.940> you 00:23:27.230 --> 00:23:27.240 align:start position:0% and they take care of everything if you 00:23:27.240 --> 00:23:31.750 align:start position:0% and they take care of everything if you want<00:23:27.270> that's<00:23:27.900> ENS<00:23:28.740> listing<00:23:30.260> comm<00:23:31.260> I<00:23:31.440> think 00:23:31.750 --> 00:23:31.760 align:start position:0% want that's ENS listing comm I think 00:23:31.760 --> 00:23:36.620 align:start position:0% want that's ENS listing comm I think Mikoto<00:23:32.760> you<00:23:32.910> want<00:23:33.090> them<00:23:35.420> they<00:23:36.420> have<00:23:36.600> a 00:23:36.620 --> 00:23:36.630 align:start position:0% Mikoto you want them they have a 00:23:36.630 --> 00:23:39.310 align:start position:0% Mikoto you want them they have a question<00:23:36.990> there<00:23:37.140> no<00:23:38.070> okay 00:23:39.310 --> 00:23:39.320 align:start position:0% question there no okay 00:23:39.320 --> 00:23:47.180 align:start position:0% question there no okay any<00:23:40.320> other<00:23:40.530> people<00:23:40.770> here<00:23:40.980> yes<00:23:43.280> yes<00:23:46.190> to 00:23:47.180 --> 00:23:47.190 align:start position:0% any other people here yes yes to 00:23:47.190 --> 00:23:47.830 align:start position:0% any other people here yes yes to continue 00:23:47.830 --> 00:23:47.840 align:start position:0% continue 00:23:47.840 --> 00:23:54.250 align:start position:0% continue do<00:23:48.840> you<00:23:48.960> have<00:23:49.140> a<00:23:49.190> network<00:23:50.190> connection<00:23:52.880> ok 00:23:54.250 --> 00:23:54.260 align:start position:0% do you have a network connection ok 00:23:54.260 --> 00:23:56.480 align:start position:0% do you have a network connection ok please<00:23:55.260> connect<00:23:55.680> to<00:23:55.830> the<00:23:55.980> theorem<00:23:56.340> to 00:23:56.480 --> 00:23:56.490 align:start position:0% please connect to the theorem to 00:23:56.490 --> 00:23:58.550 align:start position:0% please connect to the theorem to continue<00:23:57.000> but<00:23:57.180> this<00:23:57.390> is<00:23:57.540> on<00:23:57.720> a<00:23:57.750> website<00:23:58.170> or<00:23:58.500> is 00:23:58.550 --> 00:23:58.560 align:start position:0% continue but this is on a website or is 00:23:58.560 --> 00:24:01.400 align:start position:0% continue but this is on a website or is this<00:23:58.740> status<00:23:59.280> app<00:23:59.550> they<00:24:00.510> state<00:24:00.720> it<00:24:00.870> up<00:24:00.990> any 00:24:01.400 --> 00:24:01.410 align:start position:0% this status app they state it up any 00:24:01.410 --> 00:24:07.040 align:start position:0% this status app they state it up any guys<00:24:01.710> from<00:24:01.980> status<00:24:02.430> here<00:24:03.920> the<00:24:04.920> can<00:24:05.100> you<00:24:06.050> help 00:24:07.040 --> 00:24:07.050 align:start position:0% guys from status here the can you help 00:24:07.050 --> 00:24:09.320 align:start position:0% guys from status here the can you help him<00:24:07.140> on<00:24:07.380> board<00:24:07.680> G<00:24:07.920> on<00:24:08.130> board<00:24:08.460> them<00:24:08.640> go<00:24:09.090> down 00:24:09.320 --> 00:24:09.330 align:start position:0% him on board G on board them go down 00:24:09.330 --> 00:24:11.240 align:start position:0% him on board G on board them go down there<00:24:09.630> there's<00:24:09.840> a<00:24:09.900> status<00:24:10.230> group<00:24:10.650> people 00:24:11.240 --> 00:24:11.250 align:start position:0% there there's a status group people 00:24:11.250 --> 00:24:15.620 align:start position:0% there there's a status group people trying<00:24:11.970> to<00:24:12.180> on<00:24:12.390> board<00:24:12.570> on<00:24:12.780> status<00:24:14.540> there's<00:24:15.540> a 00:24:15.620 --> 00:24:15.630 align:start position:0% trying to on board on status there's a 00:24:15.630 --> 00:24:21.770 align:start position:0% trying to on board on status there's a group<00:24:16.620> of<00:24:17.150> status<00:24:18.150> people<00:24:18.720> down<00:24:18.900> there<00:24:20.780> any 00:24:21.770 --> 00:24:21.780 align:start position:0% group of status people down there any 00:24:21.780 --> 00:24:26.510 align:start position:0% group of status people down there any other<00:24:21.990> questions<00:24:22.640> doubts<00:24:23.780> yes<00:24:24.830> sir<00:24:25.860> let<00:24:26.460> me 00:24:26.510 --> 00:24:26.520 align:start position:0% other questions doubts yes sir let me 00:24:26.520 --> 00:24:34.880 align:start position:0% other questions doubts yes sir let me come<00:24:26.670> over<00:24:26.700> here 00:24:34.880 --> 00:24:34.890 align:start position:0% 00:24:34.890 --> 00:24:39.920 align:start position:0% on<00:24:35.640> madam<00:24:36.060> asked<00:24:37.160> okay<00:24:38.160> how<00:24:38.730> did<00:24:39.570> you<00:24:39.660> get<00:24:39.810> to 00:24:39.920 --> 00:24:39.930 align:start position:0% on madam asked okay how did you get to 00:24:39.930 --> 00:25:08.680 align:start position:0% on madam asked okay how did you get to that<00:24:40.080> point<00:24:43.850> was<00:24:44.850> erased<00:24:45.180> by<00:24:45.330> previous<00:25:06.410> status 00:25:08.680 --> 00:25:08.690 align:start position:0% that point was erased by previous status 00:25:08.690 --> 00:25:16.910 align:start position:0% that point was erased by previous status so<00:25:09.690> if<00:25:10.380> you<00:25:10.820> makoto<00:25:11.820> makoto<00:25:15.500> if<00:25:16.500> you<00:25:16.710> don't 00:25:16.910 --> 00:25:16.920 align:start position:0% so if you makoto makoto if you don't 00:25:16.920 --> 00:25:19.280 align:start position:0% so if you makoto makoto if you don't have<00:25:17.130> either<00:25:17.430> on<00:25:17.880> your<00:25:18.090> meta<00:25:18.480> mask<00:25:18.720> or<00:25:19.020> on<00:25:19.140> your 00:25:19.280 --> 00:25:19.290 align:start position:0% have either on your meta mask or on your 00:25:19.290 --> 00:25:22.040 align:start position:0% have either on your meta mask or on your wallet<00:25:19.680> whatever<00:25:19.890> please<00:25:20.760> either<00:25:21.120> go<00:25:21.510> on<00:25:21.780> get 00:25:22.040 --> 00:25:22.050 align:start position:0% wallet whatever please either go on get 00:25:22.050 --> 00:25:27.640 align:start position:0% wallet whatever please either go on get coin<00:25:22.380> dot<00:25:22.740> call<00:25:23.070> slash<00:25:23.760> e<00:25:24.030> NS<00:25:24.420> or<00:25:24.980> on<00:25:26.330> status 00:25:27.640 --> 00:25:27.650 align:start position:0% coin dot call slash e NS or on status 00:25:27.650 --> 00:25:30.440 align:start position:0% coin dot call slash e NS or on status the<00:25:28.650> the<00:25:28.980> app<00:25:29.100> and<00:25:29.400> the<00:25:29.820> group<00:25:30.000> down<00:25:30.210> there 00:25:30.440 --> 00:25:30.450 align:start position:0% the the app and the group down there 00:25:30.450 --> 00:25:32.660 align:start position:0% the the app and the group down there will<00:25:30.660> help<00:25:30.870> you<00:25:31.020> either<00:25:31.980> give<00:25:32.400> you<00:25:32.520> the 00:25:32.660 --> 00:25:32.670 align:start position:0% will help you either give you the 00:25:32.670 --> 00:25:36.440 align:start position:0% will help you either give you the tennyson<00:25:33.420> tees<00:25:33.630> that<00:25:33.660> they<00:25:34.110> ask<00:25:34.440> for<00:25:35.450> for 00:25:36.440 --> 00:25:36.450 align:start position:0% tennyson tees that they ask for for 00:25:36.450 --> 00:25:38.000 align:start position:0% tennyson tees that they ask for for registration<00:25:36.900> they<00:25:37.380> are<00:25:37.440> giving<00:25:37.740> it<00:25:37.800> for<00:25:37.980> free 00:25:38.000 --> 00:25:38.010 align:start position:0% registration they are giving it for free 00:25:38.010 --> 00:25:40.970 align:start position:0% registration they are giving it for free and<00:25:38.400> also<00:25:38.700> get<00:25:39.210> coin<00:25:39.480> today<00:25:39.900> is<00:25:40.170> giving<00:25:40.650> it<00:25:40.770> for 00:25:40.970 --> 00:25:40.980 align:start position:0% and also get coin today is giving it for 00:25:40.980 --> 00:25:43.610 align:start position:0% and also get coin today is giving it for free<00:25:41.010> okay<00:25:41.910> they<00:25:42.420> are<00:25:42.600> paying<00:25:42.930> all<00:25:43.260> your<00:25:43.410> gas 00:25:43.610 --> 00:25:43.620 align:start position:0% free okay they are paying all your gas 00:25:43.620 --> 00:25:46.190 align:start position:0% free okay they are paying all your gas so<00:25:44.280> that<00:25:44.430> you<00:25:44.550> get<00:25:44.760> a<00:25:44.820> sub-domain<00:25:45.210> your<00:25:45.900> user 00:25:46.190 --> 00:25:46.200 align:start position:0% so that you get a sub-domain your user 00:25:46.200 --> 00:25:48.650 align:start position:0% so that you get a sub-domain your user gets<00:25:46.620> a<00:25:46.710> sub-domain<00:25:47.040> you're<00:25:47.520> on<00:25:47.820> boarded<00:25:48.480> onto 00:25:48.650 --> 00:25:48.660 align:start position:0% gets a sub-domain you're on boarded onto 00:25:48.660 --> 00:25:53.360 align:start position:0% gets a sub-domain you're on boarded onto their<00:25:49.470> platform<00:25:51.560> but<00:25:52.560> you're<00:25:52.740> paying<00:25:52.950> the<00:25:53.190> gas 00:25:53.360 --> 00:25:53.370 align:start position:0% their platform but you're paying the gas 00:25:53.370 --> 00:25:58.910 align:start position:0% their platform but you're paying the gas with<00:25:53.730> the<00:25:53.850> S&T<00:25:56.150> okay<00:25:57.150> just<00:25:58.050> the<00:25:58.170> essenti<00:25:58.590> okay 00:25:58.910 --> 00:25:58.920 align:start position:0% with the S&T okay just the essenti okay 00:25:58.920 --> 00:26:02.750 align:start position:0% with the S&T okay just the essenti okay so<00:25:58.980> that's<00:25:59.340> one<00:26:00.060> step<00:26:00.630> as<00:26:00.990> you<00:26:01.470> see<00:26:02.130> there<00:26:02.640> are 00:26:02.750 --> 00:26:02.760 align:start position:0% so that's one step as you see there are 00:26:02.760 --> 00:26:06.980 align:start position:0% so that's one step as you see there are different<00:26:03.330> ways<00:26:03.630> of<00:26:03.930> doing<00:26:03.990> it<00:26:05.240> some<00:26:06.240> apps<00:26:06.570> or 00:26:06.980 --> 00:26:06.990 align:start position:0% different ways of doing it some apps or 00:26:06.990 --> 00:26:09.080 align:start position:0% different ways of doing it some apps or if<00:26:07.230> you<00:26:07.380> use<00:26:07.590> the<00:26:07.830> universal<00:26:08.400> logins<00:26:08.730> or<00:26:08.970> the 00:26:09.080 --> 00:26:09.090 align:start position:0% if you use the universal logins or the 00:26:09.090 --> 00:26:11.180 align:start position:0% if you use the universal logins or the metal<00:26:09.270> transactions<00:26:10.020> there<00:26:10.710> is<00:26:10.830> going<00:26:11.010> to<00:26:11.100> be 00:26:11.180 --> 00:26:11.190 align:start position:0% metal transactions there is going to be 00:26:11.190 --> 00:26:14.990 align:start position:0% metal transactions there is going to be patterns<00:26:11.910> where<00:26:12.240> as<00:26:12.680> companies<00:26:13.680> pay<00:26:14.070> for<00:26:14.640> the 00:26:14.990 --> 00:26:15.000 align:start position:0% patterns where as companies pay for the 00:26:15.000 --> 00:26:17.000 align:start position:0% patterns where as companies pay for the gas<00:26:15.150> and<00:26:15.210> for<00:26:15.720> everything<00:26:16.140> to<00:26:16.350> simplify<00:26:16.590> there 00:26:17.000 --> 00:26:17.010 align:start position:0% gas and for everything to simplify there 00:26:17.010 --> 00:26:19.820 align:start position:0% gas and for everything to simplify there is<00:26:17.100> another<00:26:17.640> wallet<00:26:18.030> that<00:26:18.120> you<00:26:18.180> can<00:26:18.510> try<00:26:18.840> is<00:26:19.200> a 00:26:19.820 --> 00:26:19.830 align:start position:0% is another wallet that you can try is a 00:26:19.830 --> 00:26:25.790 align:start position:0% is another wallet that you can try is a jean<00:26:20.700> dot<00:26:21.540> m<00:26:21.870> okay<00:26:22.860> argent<00:26:23.850> if<00:26:24.150> you<00:26:24.630> go<00:26:24.900> on<00:26:25.290> the 00:26:25.790 --> 00:26:25.800 align:start position:0% jean dot m okay argent if you go on the 00:26:25.800 --> 00:26:28.640 align:start position:0% jean dot m okay argent if you go on the on<00:26:26.250> the<00:26:26.880> i've<00:26:27.600> tried<00:26:27.870> it<00:26:28.020> this<00:26:28.140> morning<00:26:28.320> it 00:26:28.640 --> 00:26:28.650 align:start position:0% on the i've tried it this morning it 00:26:28.650 --> 00:26:31.400 align:start position:0% on the i've tried it this morning it worked<00:26:28.890> very<00:26:28.980> well<00:26:29.220> so<00:26:29.970> right<00:26:30.480> now<00:26:30.720> the<00:26:30.780> you 00:26:31.400 --> 00:26:31.410 align:start position:0% worked very well so right now the you 00:26:31.410 --> 00:26:34.640 align:start position:0% worked very well so right now the you can<00:26:31.680> reserve<00:26:32.520> your<00:26:32.990> subdomain<00:26:33.990> on<00:26:34.410> this 00:26:34.640 --> 00:26:34.650 align:start position:0% can reserve your subdomain on this 00:26:34.650 --> 00:26:36.920 align:start position:0% can reserve your subdomain on this wallet<00:26:35.040> that<00:26:35.550> doesn't<00:26:36.180> ask<00:26:36.330> you<00:26:36.420> for<00:26:36.570> any<00:26:36.690> gas 00:26:36.920 --> 00:26:36.930 align:start position:0% wallet that doesn't ask you for any gas 00:26:36.930 --> 00:26:44.960 align:start position:0% wallet that doesn't ask you for any gas or<00:26:37.140> anything<00:26:38.120> yeah 00:26:44.960 --> 00:26:44.970 align:start position:0% 00:26:44.970 --> 00:26:47.610 align:start position:0% okay<00:26:45.970> that's<00:26:46.299> a<00:26:46.420> question<00:26:46.570> for<00:26:46.750> Nick<00:26:47.080> how<00:26:47.380> are 00:26:47.610 --> 00:26:47.620 align:start position:0% okay that's a question for Nick how are 00:26:47.620 --> 00:26:50.669 align:start position:0% okay that's a question for Nick how are we<00:26:47.770> going<00:26:48.070> to<00:26:48.220> set<00:26:48.490> up<00:26:48.640> the<00:26:48.820> price<00:26:49.150> for<00:26:49.510> the<00:26:49.690> for 00:26:50.669 --> 00:26:50.679 align:start position:0% we going to set up the price for the for 00:26:50.679 --> 00:26:55.080 align:start position:0% we going to set up the price for the for the<00:26:50.860> new<00:26:51.460> domains<00:26:52.140> so<00:26:53.140> our<00:26:53.290> goal<00:26:53.530> is<00:26:53.740> to<00:26:53.940> see<00:26:54.940> it 00:26:55.080 --> 00:26:55.090 align:start position:0% the new domains so our goal is to see it 00:26:55.090 --> 00:26:57.210 align:start position:0% the new domains so our goal is to see it as<00:26:55.210> a<00:26:55.240> price<00:26:55.510> that<00:26:55.540> makes<00:26:56.220> broad-based 00:26:57.210 --> 00:26:57.220 align:start position:0% as a price that makes broad-based 00:26:57.220 --> 00:26:59.490 align:start position:0% as a price that makes broad-based spanning<00:26:57.880> and<00:26:58.120> and<00:26:58.450> so<00:26:58.600> forth<00:26:58.870> ineffective 00:26:59.490 --> 00:26:59.500 align:start position:0% spanning and and so forth ineffective 00:26:59.500 --> 00:27:01.650 align:start position:0% spanning and and so forth ineffective but<00:26:59.770> still<00:27:00.040> makes<00:27:00.250> it<00:27:00.429> cheap<00:27:00.640> and<00:27:00.790> we<00:27:01.390> think 00:27:01.650 --> 00:27:01.660 align:start position:0% but still makes it cheap and we think 00:27:01.660 --> 00:27:03.060 align:start position:0% but still makes it cheap and we think that<00:27:01.780> a<00:27:01.809> reasonable<00:27:02.320> level<00:27:02.440> for<00:27:02.710> that<00:27:02.740> is 00:27:03.060 --> 00:27:03.070 align:start position:0% that a reasonable level for that is 00:27:03.070 --> 00:27:05.160 align:start position:0% that a reasonable level for that is similar<00:27:03.520> to<00:27:03.610> existing<00:27:03.820> DNS<00:27:04.299> domain<00:27:04.450> so<00:27:04.960> ten 00:27:05.160 --> 00:27:05.170 align:start position:0% similar to existing DNS domain so ten 00:27:05.170 --> 00:27:07.590 align:start position:0% similar to existing DNS domain so ten dollars<00:27:05.470> a<00:27:05.559> year<00:27:05.970> and<00:27:06.970> that's<00:27:07.120> the<00:27:07.299> sort<00:27:07.540> of 00:27:07.590 --> 00:27:07.600 align:start position:0% dollars a year and that's the sort of 00:27:07.600 --> 00:27:12.720 align:start position:0% dollars a year and that's the sort of target<00:27:07.929> price<00:27:08.200> we're<00:27:08.410> aiming<00:27:08.530> for<00:27:11.730> the 00:27:12.720 --> 00:27:12.730 align:start position:0% target price we're aiming for the 00:27:12.730 --> 00:27:22.490 align:start position:0% target price we're aiming for the questions<00:27:13.059> yes<00:27:20.100> the<00:27:21.100> presentation<00:27:21.790> that 00:27:22.490 --> 00:27:22.500 align:start position:0% questions yes the presentation that 00:27:22.500 --> 00:27:25.710 align:start position:0% questions yes the presentation that longer<00:27:23.500> names<00:27:23.770> will<00:27:24.070> be<00:27:24.280> owned<00:27:25.059> by<00:27:25.120> instantly 00:27:25.710 --> 00:27:25.720 align:start position:0% longer names will be owned by instantly 00:27:25.720 --> 00:27:27.960 align:start position:0% longer names will be owned by instantly what<00:27:26.440> will<00:27:26.650> be<00:27:26.799> the<00:27:26.950> auction<00:27:27.220> process<00:27:27.460> for<00:27:27.940> a 00:27:27.960 --> 00:27:27.970 align:start position:0% what will be the auction process for a 00:27:27.970 --> 00:27:29.610 align:start position:0% what will be the auction process for a smaller<00:27:28.360> name<00:27:28.600> if<00:27:28.690> I<00:27:28.780> want<00:27:28.990> a<00:27:29.140> five<00:27:29.410> letter 00:27:29.610 --> 00:27:29.620 align:start position:0% smaller name if I want a five letter 00:27:29.620 --> 00:27:31.620 align:start position:0% smaller name if I want a five letter name<00:27:30.070> in<00:27:30.250> May<00:27:30.429> what<00:27:31.179> do<00:27:31.330> I<00:27:31.419> do 00:27:31.620 --> 00:27:31.630 align:start position:0% name in May what do I do 00:27:31.630 --> 00:27:35.520 align:start position:0% name in May what do I do so<00:27:32.400> before<00:27:33.400> May<00:27:33.610> will<00:27:33.880> have<00:27:34.030> a<00:27:34.059> one-off<00:27:34.530> option 00:27:35.520 --> 00:27:35.530 align:start position:0% so before May will have a one-off option 00:27:35.530 --> 00:27:38.039 align:start position:0% so before May will have a one-off option for<00:27:35.799> shorter<00:27:36.100> names<00:27:36.340> and<00:27:37.299> it<00:27:37.419> will<00:27:37.540> be<00:27:37.630> similar 00:27:38.039 --> 00:27:38.049 align:start position:0% for shorter names and it will be similar 00:27:38.049 --> 00:27:39.630 align:start position:0% for shorter names and it will be similar to<00:27:38.110> the<00:27:38.230> existing<00:27:38.590> process<00:27:39.040> with<00:27:39.220> a<00:27:39.250> bid<00:27:39.460> in<00:27:39.580> a 00:27:39.630 --> 00:27:39.640 align:start position:0% to the existing process with a bid in a 00:27:39.640 --> 00:27:41.880 align:start position:0% to the existing process with a bid in a reveal<00:27:39.910> but<00:27:40.510> it<00:27:40.630> will<00:27:40.750> be<00:27:40.870> over<00:27:41.169> a<00:27:41.200> much<00:27:41.620> longer 00:27:41.880 --> 00:27:41.890 align:start position:0% reveal but it will be over a much longer 00:27:41.890 --> 00:27:43.890 align:start position:0% reveal but it will be over a much longer period<00:27:42.070> so<00:27:42.549> you'll<00:27:42.700> have<00:27:42.790> a<00:27:42.850> perhaps<00:27:43.540> a<00:27:43.660> full 00:27:43.890 --> 00:27:43.900 align:start position:0% period so you'll have a perhaps a full 00:27:43.900 --> 00:27:46.560 align:start position:0% period so you'll have a perhaps a full month<00:27:44.140> to<00:27:44.260> do<00:27:44.559> the<00:27:44.590> bid<00:27:44.860> and<00:27:45.040> reveal<00:27:45.309> and<00:27:46.240> after 00:27:46.560 --> 00:27:46.570 align:start position:0% month to do the bid and reveal and after 00:27:46.570 --> 00:27:48.630 align:start position:0% month to do the bid and reveal and after that<00:27:46.690> went<00:27:46.960> off<00:27:47.110> then<00:27:47.710> everything<00:27:48.220> moves<00:27:48.429> to 00:27:48.630 --> 00:27:48.640 align:start position:0% that went off then everything moves to 00:27:48.640 --> 00:27:51.450 align:start position:0% that went off then everything moves to the<00:27:48.870> rent<00:27:49.870> based<00:27:50.049> registrar<00:27:50.799> and<00:27:50.950> any 00:27:51.450 --> 00:27:51.460 align:start position:0% the rent based registrar and any 00:27:51.460 --> 00:27:53.070 align:start position:0% the rent based registrar and any unregistered<00:27:52.150> name<00:27:52.360> shorter<00:27:52.750> than<00:27:52.870> six 00:27:53.070 --> 00:27:53.080 align:start position:0% unregistered name shorter than six 00:27:53.080 --> 00:27:55.140 align:start position:0% unregistered name shorter than six characters<00:27:53.470> or<00:27:53.590> longer<00:27:54.010> you<00:27:54.790> can<00:27:54.940> buy 00:27:55.140 --> 00:27:55.150 align:start position:0% characters or longer you can buy 00:27:55.150 --> 00:27:58.950 align:start position:0% characters or longer you can buy instantly<00:27:55.809> just<00:27:56.110> using<00:27:56.380> that<00:27:57.419> yes<00:27:58.419> even<00:27:58.630> short 00:27:58.950 --> 00:27:58.960 align:start position:0% instantly just using that yes even short 00:27:58.960 --> 00:27:59.880 align:start position:0% instantly just using that yes even short ones<00:27:59.110> as<00:27:59.260> long<00:27:59.320> as<00:27:59.500> they're<00:27:59.620> not<00:27:59.650> already 00:27:59.880 --> 00:27:59.890 align:start position:0% ones as long as they're not already 00:27:59.890 --> 00:28:04.820 align:start position:0% ones as long as they're not already owned<00:28:00.220> of<00:28:00.429> course 00:28:04.820 --> 00:28:04.830 align:start position:0% 00:28:04.830 --> 00:28:09.060 align:start position:0% we<00:28:05.830> know<00:28:05.980> why<00:28:06.160> when<00:28:07.030> when<00:28:07.930> when<00:28:08.620> we<00:28:08.770> first 00:28:09.060 --> 00:28:09.070 align:start position:0% we know why when when when we first 00:28:09.070 --> 00:28:11.010 align:start position:0% we know why when when when we first launched<00:28:09.580> the<00:28:09.820> Registrar<00:28:10.420> has<00:28:10.450> always<00:28:10.660> been<00:28:10.960> a 00:28:11.010 --> 00:28:11.020 align:start position:0% launched the Registrar has always been a 00:28:11.020 --> 00:28:12.930 align:start position:0% launched the Registrar has always been a limitation<00:28:11.620> of<00:28:11.710> no<00:28:11.920> more<00:28:12.130> than<00:28:12.340> no<00:28:12.640> fewer<00:28:12.880> than 00:28:12.930 --> 00:28:12.940 align:start position:0% limitation of no more than no fewer than 00:28:12.940 --> 00:28:15.480 align:start position:0% limitation of no more than no fewer than seven<00:28:13.330> characters<00:28:13.870> the<00:28:14.860> the<00:28:15.070> goal<00:28:15.220> was<00:28:15.460> just 00:28:15.480 --> 00:28:15.490 align:start position:0% seven characters the the goal was just 00:28:15.490 --> 00:28:17.940 align:start position:0% seven characters the the goal was just to<00:28:15.820> give<00:28:16.060> us<00:28:16.210> time<00:28:16.510> to<00:28:16.590> grow<00:28:17.590> in<00:28:17.770> popularity 00:28:17.940 --> 00:28:17.950 align:start position:0% to give us time to grow in popularity 00:28:17.950 --> 00:28:21.210 align:start position:0% to give us time to grow in popularity and<00:28:18.490> awareness<00:28:18.880> before<00:28:19.440> people<00:28:20.440> just<00:28:20.650> you 00:28:21.210 --> 00:28:21.220 align:start position:0% and awareness before people just you 00:28:21.220 --> 00:28:23.040 align:start position:0% and awareness before people just you know<00:28:21.310> swept<00:28:21.610> up<00:28:21.790> and<00:28:21.940> she<00:28:22.150> squatted<00:28:22.510> all<00:28:22.900> those 00:28:23.040 --> 00:28:23.050 align:start position:0% know swept up and she squatted all those 00:28:23.050 --> 00:28:27.450 align:start position:0% know swept up and she squatted all those short<00:28:23.320> names<00:28:25.470> so<00:28:26.470> we<00:28:26.500> do<00:28:26.710> have<00:28:26.860> one<00:28:27.100> other<00:28:27.250> way 00:28:27.450 --> 00:28:27.460 align:start position:0% short names so we do have one other way 00:28:27.460 --> 00:28:30.900 align:start position:0% short names so we do have one other way to<00:28:27.490> get<00:28:27.880> an<00:28:28.390> e<00:28:28.600> NS<00:28:28.840> domain<00:28:29.200> today<00:28:29.590> although<00:28:30.460> if 00:28:30.900 --> 00:28:30.910 align:start position:0% to get an e NS domain today although if 00:28:30.910 --> 00:28:33.090 align:start position:0% to get an e NS domain today although if you<00:28:31.030> do<00:28:31.150> so<00:28:31.330> it<00:28:31.450> may<00:28:31.600> take<00:28:31.680> it'll<00:28:32.680> be<00:28:32.800> a<00:28:32.830> couple 00:28:33.090 --> 00:28:33.100 align:start position:0% you do so it may take it'll be a couple 00:28:33.100 --> 00:28:34.790 align:start position:0% you do so it may take it'll be a couple of<00:28:33.160> days<00:28:33.310> before<00:28:33.490> you<00:28:33.730> can<00:28:33.850> use<00:28:34.030> it<00:28:34.150> at<00:28:34.240> least 00:28:34.790 --> 00:28:34.800 align:start position:0% of days before you can use it at least 00:28:34.800 --> 00:28:37.530 align:start position:0% of days before you can use it at least mu<00:28:35.800> makes<00:28:36.010> the<00:28:36.400> people<00:28:36.610> behind<00:28:36.940> lux<00:28:37.240> have 00:28:37.530 --> 00:28:37.540 align:start position:0% mu makes the people behind lux have 00:28:37.540 --> 00:28:39.420 align:start position:0% mu makes the people behind lux have offered<00:28:37.930> up<00:28:38.050> five<00:28:38.380> hundred<00:28:38.560> free<00:28:39.010> deluxe 00:28:39.420 --> 00:28:39.430 align:start position:0% offered up five hundred free deluxe 00:28:39.430 --> 00:28:42.060 align:start position:0% offered up five hundred free deluxe domains<00:28:39.790> to<00:28:40.780> the<00:28:40.900> first<00:28:41.050> 500<00:28:41.590> people<00:28:41.620> to<00:28:41.950> email 00:28:42.060 --> 00:28:42.070 align:start position:0% domains to the first 500 people to email 00:28:42.070 --> 00:28:44.400 align:start position:0% domains to the first 500 people to email them<00:28:42.400> at<00:28:42.940> address<00:28:43.240> with<00:28:43.480> the<00:28:43.570> subject<00:28:43.960> Devcon 00:28:44.400 --> 00:28:44.410 align:start position:0% them at address with the subject Devcon 00:28:44.410 --> 00:28:46.460 align:start position:0% them at address with the subject Devcon and<00:28:44.620> the<00:28:45.100> name<00:28:45.250> that<00:28:45.400> you'd<00:28:45.520> like<00:28:45.640> to<00:28:45.820> register 00:28:46.460 --> 00:28:46.470 align:start position:0% and the name that you'd like to register 00:28:46.470 --> 00:28:48.930 align:start position:0% and the name that you'd like to register once<00:28:47.470> this<00:28:47.680> is<00:28:47.830> launched<00:28:48.190> on<00:28:48.280> November<00:28:48.700> 5th 00:28:48.930 --> 00:28:48.940 align:start position:0% once this is launched on November 5th 00:28:48.940 --> 00:28:50.700 align:start position:0% once this is launched on November 5th that<00:28:49.120> will<00:28:49.270> be<00:28:49.390> fully<00:28:49.600> E&S<00:28:50.110> integrations 00:28:50.700 --> 00:28:50.710 align:start position:0% that will be fully E&S integrations 00:28:50.710 --> 00:28:52.680 align:start position:0% that will be fully E&S integrations you'll<00:28:50.950> be<00:28:51.040> able<00:28:51.130> to<00:28:51.250> just<00:28:51.430> type<00:28:51.640> in<00:28:51.850> your<00:28:52.060> in<00:28:52.570> T 00:28:52.680 --> 00:28:52.690 align:start position:0% you'll be able to just type in your in T 00:28:52.690 --> 00:28:55.110 align:start position:0% you'll be able to just type in your in T or<00:28:52.840> e<00:28:52.870> a<00:28:53.530> theory<00:28:53.920> madri's<00:28:54.250> in<00:28:54.490> the<00:28:54.670> registrar 00:28:55.110 --> 00:28:55.120 align:start position:0% or e a theory madri's in the registrar 00:28:55.120 --> 00:28:58.410 align:start position:0% or e a theory madri's in the registrar field<00:28:55.390> and<00:28:55.690> it<00:28:56.260> will<00:28:56.440> instantly<00:28:57.340> associate<00:28:58.330> it 00:28:58.410 --> 00:28:58.420 align:start position:0% field and it will instantly associate it 00:28:58.420 --> 00:29:00.480 align:start position:0% field and it will instantly associate it with<00:28:58.450> your<00:28:58.630> address<00:28:58.930> so<00:28:59.890> I<00:28:59.920> still<00:29:00.340> suggest 00:29:00.480 --> 00:29:00.490 align:start position:0% with your address so I still suggest 00:29:00.490 --> 00:29:04.860 align:start position:0% with your address so I still suggest using<00:29:00.970> status<00:29:01.780> or<00:29:02.370> get<00:29:03.370> coin<00:29:03.670> or<00:29:03.970> eNOS<00:29:04.840> now 00:29:04.860 --> 00:29:04.870 align:start position:0% using status or get coin or eNOS now 00:29:04.870 --> 00:29:06.990 align:start position:0% using status or get coin or eNOS now today<00:29:05.380> but<00:29:05.680> if<00:29:06.100> you<00:29:06.250> want<00:29:06.430> a<00:29:06.460> permanent<00:29:06.640> one 00:29:06.990 --> 00:29:07.000 align:start position:0% today but if you want a permanent one 00:29:07.000 --> 00:29:12.900 align:start position:0% today but if you want a permanent one then<00:29:07.270> there's<00:29:07.630> your<00:29:07.780> option<00:29:10.860> so<00:29:11.860> now<00:29:12.580> it's 00:29:12.900 --> 00:29:12.910 align:start position:0% then there's your option so now it's 00:29:12.910 --> 00:29:16.350 align:start position:0% then there's your option so now it's only<00:29:13.230> next<00:29:14.230> ten<00:29:14.650> minutes<00:29:14.830> left<00:29:15.250> so<00:29:15.550> we'll<00:29:15.940> just 00:29:16.350 --> 00:29:16.360 align:start position:0% only next ten minutes left so we'll just 00:29:16.360 --> 00:29:20.420 align:start position:0% only next ten minutes left so we'll just go<00:29:16.570> through<00:29:16.600> I<00:29:17.110> assume<00:29:17.980> you<00:29:18.250> already<00:29:18.340> got<00:29:18.700> the 00:29:20.420 --> 00:29:20.430 align:start position:0% go through I assume you already got the 00:29:20.430 --> 00:29:21.740 align:start position:0% go through I assume you already got the [Music] 00:29:21.740 --> 00:29:21.750 align:start position:0% [Music] 00:29:21.750 --> 00:29:25.710 align:start position:0% [Music] domain<00:29:22.750> so<00:29:23.020> how<00:29:23.140> many<00:29:23.200> people<00:29:23.410> got<00:29:24.720> domain 00:29:25.710 --> 00:29:25.720 align:start position:0% domain so how many people got domain 00:29:25.720 --> 00:29:31.850 align:start position:0% domain so how many people got domain today<00:29:26.640> one<00:29:27.640> two<00:29:27.940> three<00:29:28.570> four<00:29:29.340> five<00:29:30.340> people 00:29:31.850 --> 00:29:31.860 align:start position:0% today one two three four five people 00:29:31.860 --> 00:29:35.490 align:start position:0% today one two three four five people congratulations<00:29:32.950> so<00:29:33.460> now<00:29:34.300> whether<00:29:35.080> you<00:29:35.290> have 00:29:35.490 --> 00:29:35.500 align:start position:0% congratulations so now whether you have 00:29:35.500 --> 00:29:38.640 align:start position:0% congratulations so now whether you have it<00:29:35.650> or<00:29:35.800> not<00:29:35.860> we'll<00:29:36.700> quickly<00:29:37.270> go<00:29:37.480> through<00:29:38.110> how 00:29:38.640 --> 00:29:38.650 align:start position:0% it or not we'll quickly go through how 00:29:38.650 --> 00:29:42.780 align:start position:0% it or not we'll quickly go through how you<00:29:38.710> use<00:29:39.370> a<00:29:39.750> new<00:29:40.750> manager<00:29:41.320> to<00:29:41.590> manage<00:29:41.950> a<00:29:42.370> couple 00:29:42.780 --> 00:29:42.790 align:start position:0% you use a new manager to manage a couple 00:29:42.790 --> 00:29:48.930 align:start position:0% you use a new manager to manage a couple of<00:29:42.850> things<00:29:43.560> you<00:29:44.560> need<00:29:44.680> to<00:29:44.740> manage<00:29:47.520> okay<00:29:48.550> I<00:29:48.670> was 00:29:48.930 --> 00:29:48.940 align:start position:0% of things you need to manage okay I was 00:29:48.940 --> 00:29:52.380 align:start position:0% of things you need to manage okay I was Belgian<00:29:49.570> was<00:29:49.690> going<00:29:49.870> to<00:29:49.990> go<00:29:50.260> 3-bike<00:29:50.560> yes<00:29:51.390> yeah 00:29:52.380 --> 00:29:52.390 align:start position:0% Belgian was going to go 3-bike yes yeah 00:29:52.390 --> 00:29:56.340 align:start position:0% Belgian was going to go 3-bike yes yeah yeah<00:29:52.510> we<00:29:52.660> can<00:29:53.230> go<00:29:53.380> we<00:29:53.740> show<00:29:53.950> that<00:29:54.190> also<00:29:55.350> there's 00:29:56.340 --> 00:29:56.350 align:start position:0% yeah we can go we show that also there's 00:29:56.350 --> 00:29:58.320 align:start position:0% yeah we can go we show that also there's someone<00:29:56.680> who<00:29:56.920> managed<00:29:57.400> to<00:29:57.520> get<00:29:57.790> the<00:29:57.970> good<00:29:58.150> coin 00:29:58.320 --> 00:29:58.330 align:start position:0% someone who managed to get the good coin 00:29:58.330 --> 00:30:01.380 align:start position:0% someone who managed to get the good coin domain<00:29:58.990> and<00:29:59.230> was<00:29:59.380> wondering<00:30:00.010> how<00:30:00.490> do<00:30:00.550> you<00:30:00.970> then 00:30:01.380 --> 00:30:01.390 align:start position:0% domain and was wondering how do you then 00:30:01.390 --> 00:30:03.450 align:start position:0% domain and was wondering how do you then what<00:30:01.780> do<00:30:01.870> you<00:30:01.960> do<00:30:02.140> with<00:30:02.350> that<00:30:02.410> domain<00:30:03.130> right 00:30:03.450 --> 00:30:03.460 align:start position:0% what do you do with that domain right 00:30:03.460 --> 00:30:06.120 align:start position:0% what do you do with that domain right now<00:30:03.670> you<00:30:04.180> can<00:30:04.390> first<00:30:04.780> see<00:30:05.140> it<00:30:05.290> and<00:30:05.590> verify<00:30:05.800> it 00:30:06.120 --> 00:30:06.130 align:start position:0% now you can first see it and verify it 00:30:06.130 --> 00:30:09.960 align:start position:0% now you can first see it and verify it in<00:30:06.700> either<00:30:06.910> scan<00:30:07.090> in<00:30:07.420> our<00:30:07.570> manager<00:30:08.020> and<00:30:08.970> you 00:30:09.960 --> 00:30:09.970 align:start position:0% in either scan in our manager and you 00:30:09.970 --> 00:30:12.120 align:start position:0% in either scan in our manager and you can<00:30:10.210> send<00:30:10.750> to<00:30:10.990> it<00:30:11.140> or<00:30:11.380> you<00:30:11.470> can<00:30:11.650> give<00:30:11.830> it<00:30:11.950> out<00:30:12.100> to 00:30:12.120 --> 00:30:12.130 align:start position:0% can send to it or you can give it out to 00:30:12.130 --> 00:30:13.460 align:start position:0% can send to it or you can give it out to send 00:30:13.460 --> 00:30:13.470 align:start position:0% send 00:30:13.470 --> 00:30:17.240 align:start position:0% send pay<00:30:13.950> outs<00:30:14.130> or<00:30:14.520> whatever<00:30:14.880> etc<00:30:15.660> so<00:30:16.110> right<00:30:17.070> now 00:30:17.240 --> 00:30:17.250 align:start position:0% pay outs or whatever etc so right now 00:30:17.250 --> 00:30:19.790 align:start position:0% pay outs or whatever etc so right now what<00:30:18.000> you<00:30:18.120> can<00:30:18.360> do<00:30:18.540> with<00:30:18.750> a<00:30:18.780> manager<00:30:19.290> you<00:30:19.530> can 00:30:19.790 --> 00:30:19.800 align:start position:0% what you can do with a manager you can 00:30:19.800 --> 00:30:23.900 align:start position:0% what you can do with a manager you can search<00:30:20.400> for<00:30:20.430> names<00:30:21.060> okay<00:30:21.900> and<00:30:22.200> subdomains<00:30:22.910> you 00:30:23.900 --> 00:30:23.910 align:start position:0% search for names okay and subdomains you 00:30:23.910 --> 00:30:27.620 align:start position:0% search for names okay and subdomains you can<00:30:24.200> display<00:30:25.200> all<00:30:25.230> the<00:30:25.470> data<00:30:25.680> about<00:30:26.610> or<00:30:27.300> most 00:30:27.620 --> 00:30:27.630 align:start position:0% can display all the data about or most 00:30:27.630 --> 00:30:29.570 align:start position:0% can display all the data about or most of<00:30:27.780> the<00:30:27.870> data<00:30:28.080> about<00:30:28.440> the<00:30:28.650> domain<00:30:28.980> who<00:30:29.340> the 00:30:29.570 --> 00:30:29.580 align:start position:0% of the data about the domain who the 00:30:29.580 --> 00:30:32.870 align:start position:0% of the data about the domain who the owner<00:30:29.790> is<00:30:29.970> what<00:30:30.720> a<00:30:30.750> resolver<00:30:31.350> is<00:30:31.730> what<00:30:32.730> the 00:30:32.870 --> 00:30:32.880 align:start position:0% owner is what a resolver is what the 00:30:32.880 --> 00:30:36.800 align:start position:0% owner is what a resolver is what the address<00:30:33.030> it's<00:30:33.780> pointing<00:30:34.410> to<00:30:34.590> and<00:30:35.540> there<00:30:36.540> was<00:30:36.780> a 00:30:36.800 --> 00:30:36.810 align:start position:0% address it's pointing to and there was a 00:30:36.810 --> 00:30:39.200 align:start position:0% address it's pointing to and there was a question<00:30:36.990> about<00:30:37.230> what<00:30:38.010> is<00:30:38.160> a<00:30:38.190> resolver<00:30:38.670> do<00:30:39.120> you 00:30:39.200 --> 00:30:39.210 align:start position:0% question about what is a resolver do you 00:30:39.210 --> 00:30:41.180 align:start position:0% question about what is a resolver do you understand<00:30:39.720> does<00:30:40.320> everybody<00:30:40.740> understand 00:30:41.180 --> 00:30:41.190 align:start position:0% understand does everybody understand 00:30:41.190 --> 00:30:43.250 align:start position:0% understand does everybody understand what<00:30:41.340> a<00:30:41.370> resolver<00:30:41.880> is<00:30:42.030> or<00:30:42.630> who<00:30:42.990> doesn't 00:30:43.250 --> 00:30:43.260 align:start position:0% what a resolver is or who doesn't 00:30:43.260 --> 00:30:46.460 align:start position:0% what a resolver is or who doesn't understand<00:30:43.800> what<00:30:43.980> a<00:30:44.010> resolver<00:30:44.520> is<00:30:45.410> okay<00:30:46.410> so 00:30:46.460 --> 00:30:46.470 align:start position:0% understand what a resolver is okay so 00:30:46.470 --> 00:30:50.870 align:start position:0% understand what a resolver is okay so this<00:30:47.130> is<00:30:47.370> an<00:30:47.850> important<00:30:48.390> piece<00:30:48.980> ENS<00:30:49.980> has<00:30:50.280> three 00:30:50.870 --> 00:30:50.880 align:start position:0% this is an important piece ENS has three 00:30:50.880 --> 00:30:53.390 align:start position:0% this is an important piece ENS has three parts<00:30:51.270> one<00:30:51.690> is<00:30:51.750> the<00:30:51.990> registry<00:30:52.680> like<00:30:53.220> the 00:30:53.390 --> 00:30:53.400 align:start position:0% parts one is the registry like the 00:30:53.400 --> 00:30:56.300 align:start position:0% parts one is the registry like the database<00:30:54.090> where<00:30:54.450> we<00:30:54.570> have<00:30:54.780> names<00:30:55.260> points<00:30:56.130> to 00:30:56.300 --> 00:30:56.310 align:start position:0% database where we have names points to 00:30:56.310 --> 00:30:58.250 align:start position:0% database where we have names points to this<00:30:56.640> other<00:30:56.850> thing<00:30:56.940> which<00:30:57.270> is<00:30:57.390> a<00:30:57.420> resolver<00:30:57.840> a 00:30:58.250 --> 00:30:58.260 align:start position:0% this other thing which is a resolver a 00:30:58.260 --> 00:31:01.190 align:start position:0% this other thing which is a resolver a resolver<00:30:59.010> is<00:30:59.190> another<00:30:59.490> smart<00:31:00.270> contract<00:31:00.720> that 00:31:01.190 --> 00:31:01.200 align:start position:0% resolver is another smart contract that 00:31:01.200 --> 00:31:03.980 align:start position:0% resolver is another smart contract that has<00:31:01.950> the<00:31:02.280> list<00:31:02.520> of<00:31:02.640> things<00:31:02.850> to<00:31:03.120> which<00:31:03.780> it 00:31:03.980 --> 00:31:03.990 align:start position:0% has the list of things to which it 00:31:03.990 --> 00:31:07.130 align:start position:0% has the list of things to which it points<00:31:04.530> to<00:31:04.830> okay<00:31:05.370> so<00:31:05.430> this<00:31:05.700> name<00:31:06.000> points<00:31:06.900> to 00:31:07.130 --> 00:31:07.140 align:start position:0% points to okay so this name points to 00:31:07.140 --> 00:31:10.550 align:start position:0% points to okay so this name points to this<00:31:07.410> address<00:31:08.370> this<00:31:08.970> wallet<00:31:09.450> this<00:31:09.900> contract 00:31:10.550 --> 00:31:10.560 align:start position:0% this address this wallet this contract 00:31:10.560 --> 00:31:13.720 align:start position:0% this address this wallet this contract and<00:31:10.770> another<00:31:11.550> use<00:31:11.880> cases<00:31:12.390> you<00:31:12.660> can<00:31:12.870> store<00:31:13.230> and 00:31:13.720 --> 00:31:13.730 align:start position:0% and another use cases you can store and 00:31:13.730 --> 00:31:17.270 align:start position:0% and another use cases you can store and an<00:31:14.730> IP<00:31:14.970> FS<00:31:15.360> hash<00:31:15.630> you<00:31:15.840> can<00:31:16.050> point<00:31:16.380> to<00:31:16.590> an<00:31:16.800> IP<00:31:16.950> FS 00:31:17.270 --> 00:31:17.280 align:start position:0% an IP FS hash you can point to an IP FS 00:31:17.280 --> 00:31:20.690 align:start position:0% an IP FS hash you can point to an IP FS hash<00:31:17.490> so<00:31:17.790> in<00:31:18.420> a<00:31:18.780> future<00:31:19.560> day<00:31:20.220> hopefully 00:31:20.690 --> 00:31:20.700 align:start position:0% hash so in a future day hopefully 00:31:20.700 --> 00:31:23.750 align:start position:0% hash so in a future day hopefully browser<00:31:21.210> or<00:31:21.570> madam<00:31:21.900> ask<00:31:22.050> can<00:31:22.590> resolve<00:31:23.490> or 00:31:23.750 --> 00:31:23.760 align:start position:0% browser or madam ask can resolve or 00:31:23.760 --> 00:31:28.430 align:start position:0% browser or madam ask can resolve or translate<00:31:25.070> like<00:31:26.070> my<00:31:26.820> name<00:31:27.210> dot<00:31:27.690> eath<00:31:28.050> or 00:31:28.430 --> 00:31:28.440 align:start position:0% translate like my name dot eath or 00:31:28.440 --> 00:31:31.250 align:start position:0% translate like my name dot eath or whatever<00:31:28.800> into<00:31:29.580> a<00:31:29.610> website<00:31:30.270> that<00:31:30.660> is<00:31:30.840> stored 00:31:31.250 --> 00:31:31.260 align:start position:0% whatever into a website that is stored 00:31:31.260 --> 00:31:35.180 align:start position:0% whatever into a website that is stored on<00:31:31.560> ipfs<00:31:32.340> so<00:31:32.580> decentralized<00:31:33.330> and<00:31:33.660> this<00:31:34.650> piece 00:31:35.180 --> 00:31:35.190 align:start position:0% on ipfs so decentralized and this piece 00:31:35.190 --> 00:31:37.280 align:start position:0% on ipfs so decentralized and this piece is<00:31:35.220> done<00:31:35.670> by<00:31:35.880> the<00:31:35.940> resolver<00:31:36.660> is<00:31:36.840> the 00:31:37.280 --> 00:31:37.290 align:start position:0% is done by the resolver is the 00:31:37.290 --> 00:31:39.410 align:start position:0% is done by the resolver is the translator<00:31:37.950> you<00:31:38.340> can<00:31:38.550> help<00:31:38.880> yourself<00:31:39.030> to 00:31:39.410 --> 00:31:39.420 align:start position:0% translator you can help yourself to 00:31:39.420 --> 00:31:41.540 align:start position:0% translator you can help yourself to understand<00:31:39.810> alike<00:31:40.020> that<00:31:40.170> you<00:31:40.830> can<00:31:41.070> in<00:31:41.370> the 00:31:41.540 --> 00:31:41.550 align:start position:0% understand alike that you can in the 00:31:41.550 --> 00:31:44.090 align:start position:0% understand alike that you can in the manager<00:31:41.940> lists<00:31:42.300> subdomains<00:31:42.930> that<00:31:43.530> you<00:31:43.770> own 00:31:44.090 --> 00:31:44.100 align:start position:0% manager lists subdomains that you own 00:31:44.100 --> 00:31:47.660 align:start position:0% manager lists subdomains that you own and<00:31:44.990> you<00:31:45.990> can<00:31:46.020> manage<00:31:46.470> your<00:31:46.650> own<00:31:46.950> domain<00:31:47.340> like 00:31:47.660 --> 00:31:47.670 align:start position:0% and you can manage your own domain like 00:31:47.670 --> 00:31:51.350 align:start position:0% and you can manage your own domain like transfer<00:31:48.210> it<00:31:48.330> to<00:31:48.360> somebody<00:31:48.690> else<00:31:49.220> added<00:31:50.360> etc 00:31:51.350 --> 00:31:51.360 align:start position:0% transfer it to somebody else added etc 00:31:51.360 --> 00:31:55.070 align:start position:0% transfer it to somebody else added etc etc<00:31:51.420> and<00:31:52.490> this<00:31:53.490> is<00:31:53.670> the<00:31:53.850> current<00:31:54.720> manager 00:31:55.070 --> 00:31:55.080 align:start position:0% etc and this is the current manager 00:31:55.080 --> 00:31:57.500 align:start position:0% etc and this is the current manager better<00:31:55.860> as<00:31:56.220> you<00:31:56.370> can<00:31:56.580> see<00:31:56.790> there<00:31:57.030> is<00:31:57.150> not 00:31:57.500 --> 00:31:57.510 align:start position:0% better as you can see there is not 00:31:57.510 --> 00:32:00.500 align:start position:0% better as you can see there is not finished<00:31:57.840> you<00:31:58.680> have<00:31:58.980> a<00:31:59.220> universal<00:31:59.580> search<00:32:00.180> and 00:32:00.500 --> 00:32:00.510 align:start position:0% finished you have a universal search and 00:32:00.510 --> 00:32:02.900 align:start position:0% finished you have a universal search and here<00:32:00.990> you<00:32:01.110> can<00:32:01.260> search<00:32:01.500> either<00:32:01.980> for<00:32:02.460> the<00:32:02.670> name 00:32:02.900 --> 00:32:02.910 align:start position:0% here you can search either for the name 00:32:02.910 --> 00:32:05.030 align:start position:0% here you can search either for the name and<00:32:03.600> in<00:32:03.870> the<00:32:03.990> future<00:32:04.320> you<00:32:04.440> can<00:32:04.590> also<00:32:04.740> search 00:32:05.030 --> 00:32:05.040 align:start position:0% and in the future you can also search 00:32:05.040 --> 00:32:07.070 align:start position:0% and in the future you can also search for<00:32:05.070> the<00:32:05.670> address<00:32:06.180> so<00:32:06.300> if<00:32:06.420> you<00:32:06.540> know<00:32:06.810> your 00:32:07.070 --> 00:32:07.080 align:start position:0% for the address so if you know your 00:32:07.080 --> 00:32:08.630 align:start position:0% for the address so if you know your address<00:32:07.230> and<00:32:07.560> you<00:32:07.620> want<00:32:07.770> to<00:32:07.830> see<00:32:08.040> the<00:32:08.220> domains 00:32:08.630 --> 00:32:08.640 align:start position:0% address and you want to see the domains 00:32:08.640 --> 00:32:11.510 align:start position:0% address and you want to see the domains you<00:32:09.270> will<00:32:09.450> put<00:32:09.690> just<00:32:09.810> put<00:32:10.050> there<00:32:10.350> the<00:32:10.680> address 00:32:11.510 --> 00:32:11.520 align:start position:0% you will put just put there the address 00:32:11.520 --> 00:32:14.030 align:start position:0% you will put just put there the address and<00:32:11.730> it<00:32:11.970> will<00:32:12.270> do<00:32:12.570> the<00:32:12.600> reverse<00:32:13.200> resolving 00:32:14.030 --> 00:32:14.040 align:start position:0% and it will do the reverse resolving 00:32:14.040 --> 00:32:17.720 align:start position:0% and it will do the reverse resolving okay<00:32:14.670> resolution<00:32:15.660> and<00:32:15.950> the<00:32:16.950> manager<00:32:17.340> looks 00:32:17.720 --> 00:32:17.730 align:start position:0% okay resolution and the manager looks 00:32:17.730 --> 00:32:20.480 align:start position:0% okay resolution and the manager looks very<00:32:18.060> simple<00:32:18.390> at<00:32:18.990> the<00:32:19.080> beginning<00:32:19.530> so<00:32:19.980> you<00:32:20.040> have 00:32:20.480 --> 00:32:20.490 align:start position:0% very simple at the beginning so you have 00:32:20.490 --> 00:32:24.050 align:start position:0% very simple at the beginning so you have your<00:32:21.090> name<00:32:21.330> for<00:32:21.690> example<00:32:21.780> and<00:32:22.580> it<00:32:23.580> tells<00:32:23.850> you 00:32:24.050 --> 00:32:24.060 align:start position:0% your name for example and it tells you 00:32:24.060 --> 00:32:25.870 align:start position:0% your name for example and it tells you the<00:32:24.120> owner<00:32:24.600> the<00:32:25.050> address<00:32:25.410> that 00:32:25.870 --> 00:32:25.880 align:start position:0% the owner the address that 00:32:25.880 --> 00:32:29.590 align:start position:0% the owner the address that owns<00:32:26.090> this<00:32:26.630> domain<00:32:27.020> until<00:32:28.010> what<00:32:28.340> date<00:32:28.730> or<00:32:29.059> the 00:32:29.590 --> 00:32:29.600 align:start position:0% owns this domain until what date or the 00:32:29.600 --> 00:32:31.870 align:start position:0% owns this domain until what date or the opposite<00:32:30.020> this<00:32:30.169> is<00:32:30.350> the<00:32:30.530> day<00:32:31.100> in<00:32:31.460> which<00:32:31.490> it<00:32:31.789> was 00:32:31.870 --> 00:32:31.880 align:start position:0% opposite this is the day in which it was 00:32:31.880 --> 00:32:34.930 align:start position:0% opposite this is the day in which it was registered<00:32:32.630> the<00:32:33.140> resolver<00:32:33.740> this<00:32:34.250> others<00:32:34.610> mark 00:32:34.930 --> 00:32:34.940 align:start position:0% registered the resolver this others mark 00:32:34.940 --> 00:32:37.360 align:start position:0% registered the resolver this others mark contract<00:32:35.360> that<00:32:35.419> contains<00:32:36.110> what<00:32:36.740> we<00:32:36.860> call<00:32:37.100> the 00:32:37.360 --> 00:32:37.370 align:start position:0% contract that contains what we call the 00:32:37.370 --> 00:32:39.970 align:start position:0% contract that contains what we call the pointers<00:32:37.970> okay<00:32:38.690> like<00:32:38.870> you<00:32:38.990> call<00:32:39.350> them<00:32:39.530> here<00:32:39.770> in 00:32:39.970 --> 00:32:39.980 align:start position:0% pointers okay like you call them here in 00:32:39.980 --> 00:32:42.460 align:start position:0% pointers okay like you call them here in DNS<00:32:40.640> context<00:32:41.299> you<00:32:41.450> call<00:32:41.660> these<00:32:41.870> records<00:32:42.320> you 00:32:42.460 --> 00:32:42.470 align:start position:0% DNS context you call these records you 00:32:42.470 --> 00:32:45.220 align:start position:0% DNS context you call these records you know<00:32:42.620> like<00:32:42.799> the<00:32:42.950> MX<00:32:43.309> record<00:32:43.760> the<00:32:44.000> a<00:32:44.030> record<00:32:44.630> etc 00:32:45.220 --> 00:32:45.230 align:start position:0% know like the MX record the a record etc 00:32:45.230 --> 00:32:47.380 align:start position:0% know like the MX record the a record etc will<00:32:45.380> you<00:32:45.470> point<00:32:45.710> to<00:32:45.830> a<00:32:46.130> hosting<00:32:46.850> service<00:32:46.880> etc 00:32:47.380 --> 00:32:47.390 align:start position:0% will you point to a hosting service etc 00:32:47.390 --> 00:32:51.360 align:start position:0% will you point to a hosting service etc in<00:32:48.140> DNS<00:32:48.559> you<00:32:49.039> have<00:32:49.250> a<00:32:49.280> pointer<00:32:49.789> so<00:32:50.030> this<00:32:50.720> name 00:32:51.360 --> 00:32:51.370 align:start position:0% in DNS you have a pointer so this name 00:32:51.370 --> 00:32:54.549 align:start position:0% in DNS you have a pointer so this name points<00:32:52.370> to<00:32:52.610> this<00:32:52.940> address<00:32:53.299> if<00:32:53.870> I<00:32:54.080> put<00:32:54.320> in 00:32:54.549 --> 00:32:54.559 align:start position:0% points to this address if I put in 00:32:54.559 --> 00:32:56.890 align:start position:0% points to this address if I put in fireflies<00:32:55.070> or<00:32:55.100> teeth<00:32:55.460> in<00:32:55.640> meta<00:32:55.850> mask<00:32:56.120> it<00:32:56.450> will 00:32:56.890 --> 00:32:56.900 align:start position:0% fireflies or teeth in meta mask it will 00:32:56.900 --> 00:33:00.460 align:start position:0% fireflies or teeth in meta mask it will resolve<00:32:57.559> it<00:32:57.890> will<00:32:58.100> translate<00:32:58.909> into<00:32:59.299> this<00:32:59.659> okay 00:33:00.460 --> 00:33:00.470 align:start position:0% resolve it will translate into this okay 00:33:00.470 --> 00:33:03.610 align:start position:0% resolve it will translate into this okay and<00:33:00.669> next<00:33:01.669> please<00:33:01.940> thank<00:33:02.299> you<00:33:02.419> and<00:33:02.600> you<00:33:03.409> can 00:33:03.610 --> 00:33:03.620 align:start position:0% and next please thank you and you can 00:33:03.620 --> 00:33:05.560 align:start position:0% and next please thank you and you can see<00:33:03.890> if<00:33:04.130> you<00:33:04.309> switch<00:33:04.610> the<00:33:04.880> button<00:33:05.419> on 00:33:05.560 --> 00:33:05.570 align:start position:0% see if you switch the button on 00:33:05.570 --> 00:33:07.720 align:start position:0% see if you switch the button on subdomains<00:33:05.960> you<00:33:06.620> can<00:33:06.830> see<00:33:07.039> the<00:33:07.220> list<00:33:07.520> of 00:33:07.720 --> 00:33:07.730 align:start position:0% subdomains you can see the list of 00:33:07.730 --> 00:33:11.560 align:start position:0% subdomains you can see the list of subdomains<00:33:08.210> this<00:33:09.169> domain<00:33:10.039> has<00:33:10.549> okay<00:33:11.150> so 00:33:11.560 --> 00:33:11.570 align:start position:0% subdomains this domain has okay so 00:33:11.570 --> 00:33:14.470 align:start position:0% subdomains this domain has okay so Firefly<00:33:12.140> teeth<00:33:12.590> has<00:33:12.890> created<00:33:13.460> these<00:33:13.669> and<00:33:13.970> many 00:33:14.470 --> 00:33:14.480 align:start position:0% Firefly teeth has created these and many 00:33:14.480 --> 00:33:17.470 align:start position:0% Firefly teeth has created these and many more<00:33:14.830> subdomains<00:33:15.830> some<00:33:16.730> of<00:33:16.850> these<00:33:17.000> subdomains 00:33:17.470 --> 00:33:17.480 align:start position:0% more subdomains some of these subdomains 00:33:17.480 --> 00:33:21.669 align:start position:0% more subdomains some of these subdomains will<00:33:18.470> not<00:33:18.890> appear<00:33:19.880> might<00:33:20.480> not<00:33:20.929> appear<00:33:21.470> when 00:33:21.669 --> 00:33:21.679 align:start position:0% will not appear might not appear when 00:33:21.679 --> 00:33:24.990 align:start position:0% will not appear might not appear when you<00:33:21.799> search<00:33:22.159> for<00:33:22.190> them<00:33:22.610> because<00:33:23.330> they<00:33:24.289> are 00:33:24.990 --> 00:33:25.000 align:start position:0% you search for them because they are 00:33:25.000 --> 00:33:30.730 align:start position:0% you search for them because they are complicated<00:33:26.559> names<00:33:27.559> that<00:33:28.280> our<00:33:28.900> system<00:33:29.900> cannot 00:33:30.730 --> 00:33:30.740 align:start position:0% complicated names that our system cannot 00:33:30.740 --> 00:33:33.730 align:start position:0% complicated names that our system cannot find<00:33:31.309> or<00:33:31.520> translate<00:33:32.120> for<00:33:32.419> you<00:33:32.600> so<00:33:33.080> you<00:33:33.140> need<00:33:33.500> to 00:33:33.730 --> 00:33:33.740 align:start position:0% find or translate for you so you need to 00:33:33.740 --> 00:33:35.980 align:start position:0% find or translate for you so you need to input<00:33:34.039> it<00:33:34.429> or<00:33:34.610> search<00:33:34.940> it<00:33:35.150> by<00:33:35.179> hand<00:33:35.570> in<00:33:35.809> which 00:33:35.980 --> 00:33:35.990 align:start position:0% input it or search it by hand in which 00:33:35.990 --> 00:33:39.220 align:start position:0% input it or search it by hand in which case<00:33:36.380> we<00:33:36.740> will<00:33:37.039> be<00:33:37.309> able<00:33:37.429> to<00:33:37.820> list<00:33:38.600> it<00:33:38.809> for<00:33:38.840> you 00:33:39.220 --> 00:33:39.230 align:start position:0% case we will be able to list it for you 00:33:39.230 --> 00:33:41.529 align:start position:0% case we will be able to list it for you there's<00:33:39.830> a<00:33:39.919> longer<00:33:40.130> explanation<00:33:40.429> of<00:33:40.909> why<00:33:41.059> why 00:33:41.529 --> 00:33:41.539 align:start position:0% there's a longer explanation of why why 00:33:41.539 --> 00:33:43.720 align:start position:0% there's a longer explanation of why why that<00:33:41.570> is<00:33:41.900> but<00:33:42.080> I<00:33:42.440> can<00:33:43.039> explain<00:33:43.280> it<00:33:43.429> later<00:33:43.520> if 00:33:43.720 --> 00:33:43.730 align:start position:0% that is but I can explain it later if 00:33:43.730 --> 00:33:47.740 align:start position:0% that is but I can explain it later if you<00:33:43.760> want<00:33:43.820> and<00:33:44.179> please<00:33:45.080> go<00:33:45.500> next<00:33:46.130> one<00:33:46.280> and<00:33:46.820> this 00:33:47.740 --> 00:33:47.750 align:start position:0% you want and please go next one and this 00:33:47.750 --> 00:33:54.880 align:start position:0% you want and please go next one and this one<00:33:47.929> you<00:33:47.990> want<00:33:48.169> to<00:33:48.230> say<00:33:48.350> something<00:33:53.679> so<00:33:54.679> very 00:33:54.880 --> 00:33:54.890 align:start position:0% one you want to say something so very 00:33:54.890 --> 00:33:57.549 align:start position:0% one you want to say something so very quickly<00:33:55.250> the<00:33:55.940> important<00:33:56.390> steps<00:33:56.659> you<00:33:56.960> need<00:33:57.409> to 00:33:57.549 --> 00:33:57.559 align:start position:0% quickly the important steps you need to 00:33:57.559 --> 00:34:00.370 align:start position:0% quickly the important steps you need to set<00:33:58.130> when<00:33:58.970> you<00:33:59.059> go<00:33:59.240> back<00:33:59.450> to<00:33:59.630> details<00:34:00.169> you<00:34:00.350> have 00:34:00.370 --> 00:34:00.380 align:start position:0% set when you go back to details you have 00:34:00.380 --> 00:34:02.289 align:start position:0% set when you go back to details you have the<00:34:00.530> same<00:34:00.890> thing<00:34:01.130> you<00:34:01.370> have<00:34:01.400> the<00:34:01.580> resolver<00:34:02.090> and 00:34:02.289 --> 00:34:02.299 align:start position:0% the same thing you have the resolver and 00:34:02.299 --> 00:34:04.120 align:start position:0% the same thing you have the resolver and the<00:34:02.419> address<00:34:02.720> and<00:34:02.900> these<00:34:03.049> are<00:34:03.230> the<00:34:03.380> two<00:34:03.559> things 00:34:04.120 --> 00:34:04.130 align:start position:0% the address and these are the two things 00:34:04.130 --> 00:34:06.250 align:start position:0% the address and these are the two things that<00:34:04.250> after<00:34:04.730> you<00:34:04.909> have<00:34:04.940> a<00:34:05.120> domain<00:34:05.419> you<00:34:05.900> need<00:34:06.080> to 00:34:06.250 --> 00:34:06.260 align:start position:0% that after you have a domain you need to 00:34:06.260 --> 00:34:08.649 align:start position:0% that after you have a domain you need to set<00:34:06.679> okay<00:34:07.280> get<00:34:07.490> coin<00:34:07.760> does<00:34:08.030> this<00:34:08.240> for<00:34:08.480> you 00:34:08.649 --> 00:34:08.659 align:start position:0% set okay get coin does this for you 00:34:08.659 --> 00:34:11.619 align:start position:0% set okay get coin does this for you status<00:34:09.379> does<00:34:09.590> this<00:34:09.770> for<00:34:10.070> you<00:34:10.220> and<00:34:10.429> so<00:34:10.940> try<00:34:11.570> the 00:34:11.619 --> 00:34:11.629 align:start position:0% status does this for you and so try the 00:34:11.629 --> 00:34:12.250 align:start position:0% status does this for you and so try the next<00:34:11.960> one 00:34:12.250 --> 00:34:12.260 align:start position:0% next one 00:34:12.260 --> 00:34:15.220 align:start position:0% next one you<00:34:12.649> I<00:34:12.679> probably<00:34:13.280> click<00:34:13.550> on<00:34:13.790> the<00:34:14.090> tiny<00:34:14.690> button 00:34:15.220 --> 00:34:15.230 align:start position:0% you I probably click on the tiny button 00:34:15.230 --> 00:34:16.359 align:start position:0% you I probably click on the tiny button next<00:34:15.919> please 00:34:16.359 --> 00:34:16.369 align:start position:0% next please 00:34:16.369 --> 00:34:19.419 align:start position:0% next please yes<00:34:17.359> I<00:34:17.570> click<00:34:18.080> on<00:34:18.260> the<00:34:18.409> edit<00:34:18.770> an<00:34:18.950> a<00:34:19.100> for<00:34:19.340> example 00:34:19.419 --> 00:34:19.429 align:start position:0% yes I click on the edit an a for example 00:34:19.429 --> 00:34:22.359 align:start position:0% yes I click on the edit an a for example can<00:34:19.940> point<00:34:20.389> it<00:34:20.659> to<00:34:20.810> a<00:34:20.840> different<00:34:21.139> address<00:34:21.590> so<00:34:22.340> I 00:34:22.359 --> 00:34:22.369 align:start position:0% can point it to a different address so I 00:34:22.369 --> 00:34:24.580 align:start position:0% can point it to a different address so I now<00:34:22.790> have<00:34:22.820> my<00:34:23.240> token<00:34:23.570> Doty's<00:34:23.840> I<00:34:24.020> can<00:34:24.230> point<00:34:24.440> it 00:34:24.580 --> 00:34:24.590 align:start position:0% now have my token Doty's I can point it 00:34:24.590 --> 00:34:28.090 align:start position:0% now have my token Doty's I can point it to<00:34:24.710> a<00:34:24.740> different<00:34:25.070> address<00:34:25.520> instead<00:34:26.450> of<00:34:27.100> of 00:34:28.090 --> 00:34:28.100 align:start position:0% to a different address instead of of 00:34:28.100 --> 00:34:30.099 align:start position:0% to a different address instead of of this<00:34:28.310> one<00:34:28.550> so<00:34:28.730> my<00:34:29.119> name<00:34:29.359> stays<00:34:29.720> the<00:34:29.899> same<00:34:29.929> I 00:34:30.099 --> 00:34:30.109 align:start position:0% this one so my name stays the same I 00:34:30.109 --> 00:34:32.560 align:start position:0% this one so my name stays the same I still<00:34:30.710> give<00:34:30.859> this<00:34:31.070> out<00:34:31.280> but<00:34:31.850> I<00:34:31.879> pointed<00:34:32.419> to 00:34:32.560 --> 00:34:32.570 align:start position:0% still give this out but I pointed to 00:34:32.570 --> 00:34:35.260 align:start position:0% still give this out but I pointed to whichever<00:34:32.929> thing<00:34:33.889> I<00:34:34.070> want<00:34:34.280> address<00:34:34.790> or<00:34:34.909> wallet 00:34:35.260 --> 00:34:35.270 align:start position:0% whichever thing I want address or wallet 00:34:35.270 --> 00:34:38.109 align:start position:0% whichever thing I want address or wallet next<00:34:35.600> one<00:34:35.720> please<00:34:35.810> I<00:34:36.139> can<00:34:36.830> this<00:34:37.700> is<00:34:37.909> how<00:34:38.060> you 00:34:38.109 --> 00:34:38.119 align:start position:0% next one please I can this is how you 00:34:38.119 --> 00:34:39.159 align:start position:0% next one please I can this is how you send<00:34:38.419> the<00:34:38.540> transaction 00:34:39.159 --> 00:34:39.169 align:start position:0% send the transaction 00:34:39.169 --> 00:34:41.319 align:start position:0% send the transaction with<00:34:39.470> madam<00:34:39.799> asked<00:34:39.950> if<00:34:40.309> when<00:34:40.790> you<00:34:40.909> confirm 00:34:41.319 --> 00:34:41.329 align:start position:0% with madam asked if when you confirm 00:34:41.329 --> 00:34:47.020 align:start position:0% with madam asked if when you confirm thank<00:34:41.690> you<00:34:42.079> next<00:34:43.040> one<00:34:43.569> you<00:34:44.569> can<00:34:45.139> this<00:34:45.770> is<00:34:46.030> you 00:34:47.020 --> 00:34:47.030 align:start position:0% thank you next one you can this is you 00:34:47.030 --> 00:34:49.539 align:start position:0% thank you next one you can this is you add<00:34:47.210> a<00:34:47.419> sub-domain<00:34:47.960> okay<00:34:48.770> this<00:34:49.010> is<00:34:49.129> a<00:34:49.159> way<00:34:49.490> to 00:34:49.539 --> 00:34:49.549 align:start position:0% add a sub-domain okay this is a way to 00:34:49.549 --> 00:34:51.549 align:start position:0% add a sub-domain okay this is a way to for<00:34:49.970> you<00:34:50.089> to<00:34:50.240> sub<00:34:50.480> to<00:34:50.839> other<00:34:50.960> subdomain<00:34:51.290> you 00:34:51.549 --> 00:34:51.559 align:start position:0% for you to sub to other subdomain you 00:34:51.559 --> 00:34:54.339 align:start position:0% for you to sub to other subdomain you pick<00:34:51.710> a<00:34:51.740> name<00:34:51.980> next<00:34:52.369> one<00:34:52.549> thank<00:34:52.849> you<00:34:52.970> and<00:34:53.839> you 00:34:54.339 --> 00:34:54.349 align:start position:0% pick a name next one thank you and you 00:34:54.349 --> 00:34:56.710 align:start position:0% pick a name next one thank you and you execute<00:34:54.919> the<00:34:55.040> transaction<00:34:55.250> and<00:34:55.879> when<00:34:56.540> it's 00:34:56.710 --> 00:34:56.720 align:start position:0% execute the transaction and when it's 00:34:56.720 --> 00:35:00.609 align:start position:0% execute the transaction and when it's executed<00:34:57.139> thank<00:34:57.770> you<00:34:57.950> next<00:34:58.549> one<00:34:58.760> you<00:34:59.450> see<00:34:59.839> the 00:35:00.609 --> 00:35:00.619 align:start position:0% executed thank you next one you see the 00:35:00.619 --> 00:35:03.670 align:start position:0% executed thank you next one you see the sub<00:35:01.309> domain<00:35:01.640> okay<00:35:02.030> it<00:35:02.510> goes<00:35:03.109> back<00:35:03.349> to<00:35:03.530> the 00:35:03.670 --> 00:35:03.680 align:start position:0% sub domain okay it goes back to the 00:35:03.680 --> 00:35:05.829 align:start position:0% sub domain okay it goes back to the details<00:35:04.069> of<00:35:04.339> this<00:35:04.579> sub<00:35:04.849> domain<00:35:05.180> each<00:35:05.420> of<00:35:05.690> these 00:35:05.829 --> 00:35:05.839 align:start position:0% details of this sub domain each of these 00:35:05.839 --> 00:35:08.710 align:start position:0% details of this sub domain each of these are<00:35:06.109> called<00:35:06.410> nodes<00:35:06.859> or<00:35:07.160> is<00:35:07.520> a<00:35:07.609> domain<00:35:08.089> okay 00:35:08.710 --> 00:35:08.720 align:start position:0% are called nodes or is a domain okay 00:35:08.720 --> 00:35:11.470 align:start position:0% are called nodes or is a domain okay and<00:35:08.809> you<00:35:09.290> can<00:35:09.470> set<00:35:09.710> their<00:35:09.980> resolver<00:35:10.670> so<00:35:10.910> this 00:35:11.470 --> 00:35:11.480 align:start position:0% and you can set their resolver so this 00:35:11.480 --> 00:35:13.120 align:start position:0% and you can set their resolver so this other's<00:35:11.869> smart<00:35:12.230> contract<00:35:12.650> that<00:35:12.770> helps 00:35:13.120 --> 00:35:13.130 align:start position:0% other's smart contract that helps 00:35:13.130 --> 00:35:15.730 align:start position:0% other's smart contract that helps translate<00:35:13.819> and<00:35:14.299> you<00:35:14.390> if<00:35:15.049> you're<00:35:15.200> developers 00:35:15.730 --> 00:35:15.740 align:start position:0% translate and you if you're developers 00:35:15.740 --> 00:35:19.000 align:start position:0% translate and you if you're developers you<00:35:15.890> can<00:35:15.920> develop<00:35:16.690> custom<00:35:17.690> resolvers<00:35:18.500> you 00:35:19.000 --> 00:35:19.010 align:start position:0% you can develop custom resolvers you 00:35:19.010 --> 00:35:21.400 align:start position:0% you can develop custom resolvers you will<00:35:19.220> learn<00:35:19.460> a<00:35:19.849> bit<00:35:20.240> of<00:35:20.270> this<00:35:20.569> probably<00:35:20.960> in<00:35:21.200> the 00:35:21.400 --> 00:35:21.410 align:start position:0% will learn a bit of this probably in the 00:35:21.410 --> 00:35:25.500 align:start position:0% will learn a bit of this probably in the in<00:35:22.400> the<00:35:22.839> hands<00:35:23.839> on<00:35:23.990> integration<00:35:24.380> workshop<00:35:24.890> but 00:35:25.500 --> 00:35:25.510 align:start position:0% in the hands on integration workshop but 00:35:25.510 --> 00:35:28.270 align:start position:0% in the hands on integration workshop but everybody<00:35:26.510> can<00:35:26.720> use<00:35:26.930> the<00:35:27.140> default<00:35:27.650> public 00:35:28.270 --> 00:35:28.280 align:start position:0% everybody can use the default public 00:35:28.280 --> 00:35:31.569 align:start position:0% everybody can use the default public resolver<00:35:28.910> which<00:35:29.150> simply<00:35:30.109> gives<00:35:30.380> you<00:35:30.470> a<00:35:30.770> set<00:35:31.339> of 00:35:31.569 --> 00:35:31.579 align:start position:0% resolver which simply gives you a set of 00:35:31.579 --> 00:35:34.180 align:start position:0% resolver which simply gives you a set of pre<00:35:32.270> translatable<00:35:33.020> pointers<00:35:33.740> if<00:35:33.920> you<00:35:34.010> want 00:35:34.180 --> 00:35:34.190 align:start position:0% pre translatable pointers if you want 00:35:34.190 --> 00:35:37.059 align:start position:0% pre translatable pointers if you want you<00:35:34.400> can<00:35:34.579> point<00:35:35.150> it<00:35:35.359> to<00:35:35.420> an<00:35:35.630> address<00:35:35.780> or<00:35:36.230> which 00:35:37.059 --> 00:35:37.069 align:start position:0% you can point it to an address or which 00:35:37.069 --> 00:35:39.760 align:start position:0% you can point it to an address or which is<00:35:37.099> a<00:35:37.250> wallet<00:35:37.640> or<00:35:37.790> a<00:35:37.960> contract<00:35:38.960> you<00:35:39.109> can<00:35:39.319> point 00:35:39.760 --> 00:35:39.770 align:start position:0% is a wallet or a contract you can point 00:35:39.770 --> 00:35:42.309 align:start position:0% is a wallet or a contract you can point it<00:35:39.920> to<00:35:39.980> an<00:35:40.160> IP<00:35:40.339> FS<00:35:40.640> hash<00:35:40.880> you<00:35:41.420> can<00:35:41.599> have<00:35:41.750> a<00:35:41.780> text 00:35:42.309 --> 00:35:42.319 align:start position:0% it to an IP FS hash you can have a text 00:35:42.319 --> 00:35:45.670 align:start position:0% it to an IP FS hash you can have a text file<00:35:42.559> a<00:35:43.190> text<00:35:43.700> field<00:35:43.880> and<00:35:44.380> another<00:35:45.380> things 00:35:45.670 --> 00:35:45.680 align:start position:0% file a text field and another things 00:35:45.680 --> 00:35:48.809 align:start position:0% file a text field and another things please<00:35:46.099> next<00:35:46.430> one<00:35:46.640> you<00:35:47.510> send<00:35:47.720> a<00:35:47.780> transaction 00:35:48.809 --> 00:35:48.819 align:start position:0% please next one you send a transaction 00:35:48.819 --> 00:35:53.620 align:start position:0% please next one you send a transaction save<00:35:49.819> again<00:35:50.299> next<00:35:51.170> and<00:35:52.000> finally<00:35:53.000> the<00:35:53.119> resolver 00:35:53.620 --> 00:35:53.630 align:start position:0% save again next and finally the resolver 00:35:53.630 --> 00:35:55.690 align:start position:0% save again next and finally the resolver has<00:35:53.839> been<00:35:54.049> set<00:35:54.290> you<00:35:54.619> need<00:35:54.829> to<00:35:54.980> point<00:35:55.280> it<00:35:55.549> to 00:35:55.690 --> 00:35:55.700 align:start position:0% has been set you need to point it to 00:35:55.700 --> 00:35:57.880 align:start position:0% has been set you need to point it to someone<00:35:56.210> to<00:35:56.569> something<00:35:56.839> otherwise<00:35:57.349> it's<00:35:57.589> not 00:35:57.880 --> 00:35:57.890 align:start position:0% someone to something otherwise it's not 00:35:57.890 --> 00:35:58.930 align:start position:0% someone to something otherwise it's not usable<00:35:58.369> yet 00:35:58.930 --> 00:35:58.940 align:start position:0% usable yet 00:35:58.940 --> 00:36:00.910 align:start position:0% usable yet so<00:35:59.270> this<00:35:59.480> resolver<00:35:59.990> can<00:36:00.260> point<00:36:00.500> it<00:36:00.650> to<00:36:00.710> an 00:36:00.910 --> 00:36:00.920 align:start position:0% so this resolver can point it to an 00:36:00.920 --> 00:36:03.400 align:start position:0% so this resolver can point it to an address<00:36:01.069> and<00:36:01.490> and<00:36:01.819> content<00:36:02.510> is<00:36:02.690> the<00:36:02.839> IP<00:36:03.049> FS 00:36:03.400 --> 00:36:03.410 align:start position:0% address and and content is the IP FS 00:36:03.410 --> 00:36:06.430 align:start position:0% address and and content is the IP FS hash<00:36:03.740> okay<00:36:04.220> you<00:36:04.790> can<00:36:05.000> point<00:36:05.329> it<00:36:05.510> to<00:36:05.569> an<00:36:05.990> IP<00:36:06.170> FS 00:36:06.430 --> 00:36:06.440 align:start position:0% hash okay you can point it to an IP FS 00:36:06.440 --> 00:36:09.760 align:start position:0% hash okay you can point it to an IP FS or<00:36:06.589> swarm<00:36:07.160> hash<00:36:07.430> as<00:36:07.700> well<00:36:07.849> right<00:36:08.119> and<00:36:08.589> in<00:36:09.589> this 00:36:09.760 --> 00:36:09.770 align:start position:0% or swarm hash as well right and in this 00:36:09.770 --> 00:36:11.829 align:start position:0% or swarm hash as well right and in this case<00:36:09.980> we<00:36:10.099> point<00:36:10.339> it<00:36:10.400> to<00:36:10.520> an<00:36:10.609> address<00:36:10.760> go<00:36:11.210> next 00:36:11.829 --> 00:36:11.839 align:start position:0% case we point it to an address go next 00:36:11.839 --> 00:36:15.819 align:start position:0% case we point it to an address go next one<00:36:13.660> we're<00:36:14.660> sending<00:36:14.900> a<00:36:15.079> transaction<00:36:15.530> empty 00:36:15.819 --> 00:36:15.829 align:start position:0% one we're sending a transaction empty 00:36:15.829 --> 00:36:19.480 align:start position:0% one we're sending a transaction empty but<00:36:16.010> go<00:36:16.250> ahead<00:36:16.369> and<00:36:17.589> that's<00:36:18.589> it<00:36:18.740> so<00:36:19.040> this<00:36:19.309> is 00:36:19.480 --> 00:36:19.490 align:start position:0% but go ahead and that's it so this is 00:36:19.490 --> 00:36:22.089 align:start position:0% but go ahead and that's it so this is the<00:36:19.700> basic<00:36:20.299> things<00:36:20.839> that<00:36:21.109> you<00:36:21.230> have<00:36:21.650> to<00:36:21.920> do 00:36:22.089 --> 00:36:22.099 align:start position:0% the basic things that you have to do 00:36:22.099 --> 00:36:24.579 align:start position:0% the basic things that you have to do with<00:36:22.400> the<00:36:22.520> I&S<00:36:23.150> you<00:36:23.630> get<00:36:23.869> a<00:36:23.900> name<00:36:24.170> or<00:36:24.470> a 00:36:24.579 --> 00:36:24.589 align:start position:0% with the I&S you get a name or a 00:36:24.589 --> 00:36:28.599 align:start position:0% with the I&S you get a name or a subdomain<00:36:25.400> you<00:36:26.299> set<00:36:26.630> the<00:36:26.930> resolver<00:36:27.609> inside 00:36:28.599 --> 00:36:28.609 align:start position:0% subdomain you set the resolver inside 00:36:28.609 --> 00:36:30.549 align:start position:0% subdomain you set the resolver inside when<00:36:28.910> the<00:36:29.089> resolver<00:36:29.569> is<00:36:29.690> set<00:36:29.900> you<00:36:30.140> set<00:36:30.380> the 00:36:30.549 --> 00:36:30.559 align:start position:0% when the resolver is set you set the 00:36:30.559 --> 00:36:33.190 align:start position:0% when the resolver is set you set the pointer<00:36:31.190> or<00:36:31.400> record<00:36:32.270> if<00:36:32.480> it's<00:36:32.630> easier<00:36:32.960> for<00:36:32.990> you 00:36:33.190 --> 00:36:33.200 align:start position:0% pointer or record if it's easier for you 00:36:33.200 --> 00:36:35.289 align:start position:0% pointer or record if it's easier for you to<00:36:33.230> understand<00:36:33.619> with<00:36:33.829> DNS<00:36:34.160> language<00:36:34.670> that 00:36:35.289 --> 00:36:35.299 align:start position:0% to understand with DNS language that 00:36:35.299 --> 00:36:37.390 align:start position:0% to understand with DNS language that points<00:36:35.930> to<00:36:36.109> a<00:36:36.349> wallet<00:36:36.770> for<00:36:36.920> example<00:36:37.250> these 00:36:37.390 --> 00:36:37.400 align:start position:0% points to a wallet for example these 00:36:37.400 --> 00:36:41.410 align:start position:0% points to a wallet for example these three<00:36:37.700> steps<00:36:37.970> after<00:36:38.960> you<00:36:39.500> own<00:36:39.770> a<00:36:39.829> domain<00:36:40.420> okay 00:36:41.410 --> 00:36:41.420 align:start position:0% three steps after you own a domain okay 00:36:41.420 --> 00:36:44.380 align:start position:0% three steps after you own a domain okay and<00:36:42.309> while<00:36:43.309> we<00:36:43.460> talked<00:36:43.700> about<00:36:43.849> this<00:36:44.180> already 00:36:44.380 --> 00:36:44.390 align:start position:0% and while we talked about this already 00:36:44.390 --> 00:36:50.770 align:start position:0% and while we talked about this already but<00:36:44.990> any<00:36:45.200> questions<00:36:45.859> in<00:36:46.040> the<00:36:46.069> meantime 00:36:50.770 --> 00:36:50.780 align:start position:0% 00:36:50.780 --> 00:36:57.170 align:start position:0% lux<00:36:51.780> like<00:36:52.200> luxury<00:36:53.270> luxury<00:36:54.349> yes<00:36:56.000> let<00:36:57.000> you 00:36:57.170 --> 00:36:57.180 align:start position:0% lux like luxury luxury yes let you 00:36:57.180 --> 00:37:18.800 align:start position:0% lux like luxury luxury yes let you exchange<00:36:57.540> easy<00:37:16.040> the<00:37:17.040> lux<00:37:17.520> is<00:37:17.760> repurposed<00:37:18.540> let 00:37:18.800 --> 00:37:18.810 align:start position:0% exchange easy the lux is repurposed let 00:37:18.810 --> 00:37:20.750 align:start position:0% exchange easy the lux is repurposed let you<00:37:18.930> exchange<00:37:19.140> easily<00:37:19.619> and<00:37:19.800> the<00:37:20.310> objective 00:37:20.750 --> 00:37:20.760 align:start position:0% you exchange easily and the objective 00:37:20.760 --> 00:37:23.000 align:start position:0% you exchange easily and the objective for<00:37:20.910> us<00:37:20.940> is<00:37:21.270> to<00:37:21.390> bring<00:37:21.599> that<00:37:21.840> standard<00:37:22.650> DNS 00:37:23.000 --> 00:37:23.010 align:start position:0% for us is to bring that standard DNS 00:37:23.010 --> 00:37:25.370 align:start position:0% for us is to bring that standard DNS naming<00:37:23.730> convention<00:37:24.570> into<00:37:25.080> the<00:37:25.170> blockchain 00:37:25.370 --> 00:37:25.380 align:start position:0% naming convention into the blockchain 00:37:25.380 --> 00:37:27.980 align:start position:0% naming convention into the blockchain community<00:37:26.040> so<00:37:26.460> we've<00:37:26.609> worked<00:37:26.790> with<00:37:27.000> Nick<00:37:27.270> to 00:37:27.980 --> 00:37:27.990 align:start position:0% community so we've worked with Nick to 00:37:27.990 --> 00:37:29.870 align:start position:0% community so we've worked with Nick to integrate<00:37:28.500> this<00:37:28.650> and<00:37:28.980> so<00:37:29.190> our<00:37:29.340> registrar's 00:37:29.870 --> 00:37:29.880 align:start position:0% integrate this and so our registrar's 00:37:29.880 --> 00:37:32.150 align:start position:0% integrate this and so our registrar's you<00:37:30.000> can<00:37:30.090> actually<00:37:30.180> just<00:37:30.420> paste<00:37:31.260> the<00:37:31.859> wallet 00:37:32.150 --> 00:37:32.160 align:start position:0% you can actually just paste the wallet 00:37:32.160 --> 00:37:33.890 align:start position:0% you can actually just paste the wallet address<00:37:32.490> in<00:37:32.670> with<00:37:33.090> your<00:37:33.270> domain<00:37:33.540> name<00:37:33.720> and 00:37:33.890 --> 00:37:33.900 align:start position:0% address in with your domain name and 00:37:33.900 --> 00:37:35.270 align:start position:0% address in with your domain name and it'll<00:37:34.260> actually<00:37:34.349> propagate<00:37:34.770> on<00:37:35.099> to<00:37:35.190> the 00:37:35.270 --> 00:37:35.280 align:start position:0% it'll actually propagate on to the 00:37:35.280 --> 00:37:37.910 align:start position:0% it'll actually propagate on to the blockchain<00:37:35.490> and<00:37:35.849> work<00:37:36.359> anywhere<00:37:36.750> that<00:37:36.990> ENS 00:37:37.910 --> 00:37:37.920 align:start position:0% blockchain and work anywhere that ENS 00:37:37.920 --> 00:37:41.720 align:start position:0% blockchain and work anywhere that ENS works<00:37:38.190> today<00:37:38.990> and<00:37:39.990> so<00:37:40.770> I'll<00:37:41.099> just<00:37:41.160> remind<00:37:41.580> you 00:37:41.720 --> 00:37:41.730 align:start position:0% works today and so I'll just remind you 00:37:41.730 --> 00:37:43.730 align:start position:0% works today and so I'll just remind you guys<00:37:41.790> the<00:37:42.090> first<00:37:42.300> 500<00:37:42.810> people<00:37:42.840> that<00:37:43.590> email 00:37:43.730 --> 00:37:43.740 align:start position:0% guys the first 500 people that email 00:37:43.740 --> 00:37:47.930 align:start position:0% guys the first 500 people that email marketing<00:37:44.369> at<00:37:44.690> MMX<00:37:45.690> Co<00:37:46.200> will<00:37:46.800> get<00:37:46.980> a<00:37:47.010> free<00:37:47.369> dot 00:37:47.930 --> 00:37:47.940 align:start position:0% marketing at MMX Co will get a free dot 00:37:47.940 --> 00:37:51.380 align:start position:0% marketing at MMX Co will get a free dot lux<00:37:48.210> domain<00:37:48.780> name<00:37:48.960> yay<00:37:49.970> thank<00:37:50.970> you 00:37:51.380 --> 00:37:51.390 align:start position:0% lux domain name yay thank you 00:37:51.390 --> 00:37:56.060 align:start position:0% lux domain name yay thank you any<00:37:51.990> other<00:37:52.260> questions<00:37:52.770> and<00:37:53.930> this<00:37:54.930> this<00:37:55.440> gives 00:37:56.060 --> 00:37:56.070 align:start position:0% any other questions and this this gives 00:37:56.070 --> 00:37:58.250 align:start position:0% any other questions and this this gives us<00:37:56.369> way<00:37:56.670> to<00:37:56.900> reminding<00:37:57.900> you<00:37:58.020> that 00:37:58.250 --> 00:37:58.260 align:start position:0% us way to reminding you that 00:37:58.260 --> 00:38:01.339 align:start position:0% us way to reminding you that Dottie's<00:37:59.099> is<00:37:59.369> the<00:37:59.520> current<00:37:59.970> namespace<00:38:00.599> but 00:38:01.339 --> 00:38:01.349 align:start position:0% Dottie's is the current namespace but 00:38:01.349 --> 00:38:03.920 align:start position:0% Dottie's is the current namespace but already<00:38:01.859> you<00:38:02.040> can<00:38:02.280> buy<00:38:02.849> the<00:38:02.910> blocks<00:38:03.390> and<00:38:03.630> that 00:38:03.920 --> 00:38:03.930 align:start position:0% already you can buy the blocks and that 00:38:03.930 --> 00:38:06.950 align:start position:0% already you can buy the blocks and that XYZ<00:38:04.320> domain<00:38:04.950> and<00:38:05.190> in<00:38:05.880> the<00:38:06.180> future<00:38:06.630> hopefully 00:38:06.950 --> 00:38:06.960 align:start position:0% XYZ domain and in the future hopefully 00:38:06.960 --> 00:38:10.160 align:start position:0% XYZ domain and in the future hopefully the<00:38:07.560> whole<00:38:07.849> community<00:38:08.849> and<00:38:08.970> all<00:38:09.270> the<00:38:09.300> TL<00:38:09.930> DS 00:38:10.160 --> 00:38:10.170 align:start position:0% the whole community and all the TL DS 00:38:10.170 --> 00:38:12.109 align:start position:0% the whole community and all the TL DS will<00:38:10.470> be<00:38:10.619> integrated<00:38:11.250> into<00:38:11.369> the<00:38:11.609> system<00:38:12.000> and 00:38:12.109 --> 00:38:12.119 align:start position:0% will be integrated into the system and 00:38:12.119 --> 00:38:14.720 align:start position:0% will be integrated into the system and so<00:38:12.300> if<00:38:12.450> you<00:38:12.599> own<00:38:12.780> a.com<00:38:13.200> domain<00:38:13.440> you<00:38:14.190> can<00:38:14.430> have 00:38:14.720 --> 00:38:14.730 align:start position:0% so if you own a.com domain you can have 00:38:14.730 --> 00:38:18.800 align:start position:0% so if you own a.com domain you can have the<00:38:14.910> same<00:38:15.349> subdomain<00:38:16.349> in<00:38:16.650> system<00:38:17.660> for<00:38:18.660> that 00:38:18.800 --> 00:38:18.810 align:start position:0% the same subdomain in system for that 00:38:18.810 --> 00:38:21.650 align:start position:0% the same subdomain in system for that domain<00:38:18.990> and<00:38:19.980> and<00:38:20.310> also<00:38:20.490> the<00:38:20.609> main<00:38:20.940> domain<00:38:21.300> can 00:38:21.650 --> 00:38:21.660 align:start position:0% domain and and also the main domain can 00:38:21.660 --> 00:38:24.500 align:start position:0% domain and and also the main domain can point<00:38:21.900> to<00:38:22.140> whatever<00:38:22.440> decentralized<00:38:23.510> address 00:38:24.500 --> 00:38:24.510 align:start position:0% point to whatever decentralized address 00:38:24.510 --> 00:38:27.530 align:start position:0% point to whatever decentralized address or<00:38:24.720> IP<00:38:24.780> FS<00:38:25.380> ash<00:38:25.589> that<00:38:26.130> you<00:38:26.220> want<00:38:26.430> will<00:38:26.970> want<00:38:27.270> in 00:38:27.530 --> 00:38:27.540 align:start position:0% or IP FS ash that you want will want in 00:38:27.540 --> 00:38:32.210 align:start position:0% or IP FS ash that you want will want in the<00:38:27.660> future<00:38:27.980> questions<00:38:30.320> who<00:38:31.320> managed<00:38:31.800> to<00:38:32.010> get 00:38:32.210 --> 00:38:32.220 align:start position:0% the future questions who managed to get 00:38:32.220 --> 00:38:35.960 align:start position:0% the future questions who managed to get a<00:38:32.280> subdomain<00:38:32.700> here<00:38:33.619> one<00:38:34.619> two<00:38:34.800> three<00:38:35.160> four<00:38:35.580> five 00:38:35.960 --> 00:38:35.970 align:start position:0% a subdomain here one two three four five 00:38:35.970 --> 00:38:39.980 align:start position:0% a subdomain here one two three four five six<00:38:36.359> seven<00:38:36.890> eight<00:38:37.890> nine<00:38:38.510> yeah<00:38:39.510> come<00:38:39.660> on<00:38:39.720> ten 00:38:39.980 --> 00:38:39.990 align:start position:0% six seven eight nine yeah come on ten 00:38:39.990 --> 00:38:49.910 align:start position:0% six seven eight nine yeah come on ten one<00:38:40.530> more<00:38:40.710> give<00:38:41.099> me<00:38:41.190> ten<00:38:45.440> okay<00:38:46.440> good<00:38:48.740> can<00:38:49.740> we 00:38:49.910 --> 00:38:49.920 align:start position:0% one more give me ten okay good can we 00:38:49.920 --> 00:38:52.220 align:start position:0% one more give me ten okay good can we make<00:38:50.099> a<00:38:50.130> sub<00:38:50.460> domain<00:38:50.609> of<00:38:50.910> a<00:38:50.970> subdomain<00:38:51.330> yes<00:38:51.930> ad 00:38:52.220 --> 00:38:52.230 align:start position:0% make a sub domain of a subdomain yes ad 00:38:52.230 --> 00:38:54.530 align:start position:0% make a sub domain of a subdomain yes ad infinitum<00:38:52.500> you<00:38:53.130> can<00:38:53.280> make<00:38:53.430> sub<00:38:53.700> of<00:38:53.910> sub<00:38:54.150> of<00:38:54.300> sub 00:38:54.530 --> 00:38:54.540 align:start position:0% infinitum you can make sub of sub of sub 00:38:54.540 --> 00:38:58.010 align:start position:0% infinitum you can make sub of sub of sub of<00:38:54.720> subs<00:38:55.640> you<00:38:56.640> can<00:38:56.910> imagine<00:38:57.420> your<00:38:57.630> own<00:38:57.750> things 00:38:58.010 --> 00:38:58.020 align:start position:0% of subs you can imagine your own things 00:38:58.020 --> 00:39:00.290 align:start position:0% of subs you can imagine your own things the<00:38:58.440> only<00:38:58.530> thing<00:38:58.800> is<00:38:58.920> that<00:38:59.130> for<00:38:59.369> each<00:38:59.580> node<00:39:00.030> or 00:39:00.290 --> 00:39:00.300 align:start position:0% the only thing is that for each node or 00:39:00.300 --> 00:39:02.260 align:start position:0% the only thing is that for each node or each<00:39:00.420> subdomain<00:39:00.930> you<00:39:01.290> need<00:39:01.440> to<00:39:01.560> set 00:39:02.260 --> 00:39:02.270 align:start position:0% each subdomain you need to set 00:39:02.270 --> 00:39:04.780 align:start position:0% each subdomain you need to set and<00:39:02.870> maybe<00:39:03.080> set<00:39:03.410> a<00:39:03.590> pointer<00:39:04.220> so<00:39:04.250> it's<00:39:04.580> two 00:39:04.780 --> 00:39:04.790 align:start position:0% and maybe set a pointer so it's two 00:39:04.790 --> 00:39:07.330 align:start position:0% and maybe set a pointer so it's two transactions<00:39:05.450> for<00:39:05.630> that<00:39:05.810> unless<00:39:06.800> you<00:39:07.010> create 00:39:07.330 --> 00:39:07.340 align:start position:0% transactions for that unless you create 00:39:07.340 --> 00:39:10.210 align:start position:0% transactions for that unless you create a<00:39:07.370> custom<00:39:08.140> resolver<00:39:09.140> that<00:39:09.410> maybe<00:39:09.830> does 00:39:10.210 --> 00:39:10.220 align:start position:0% a custom resolver that maybe does 00:39:10.220 --> 00:39:12.310 align:start position:0% a custom resolver that maybe does everything<00:39:10.610> for<00:39:10.850> you<00:39:10.970> already<00:39:11.540> I<00:39:11.840> don't<00:39:12.140> know 00:39:12.310 --> 00:39:12.320 align:start position:0% everything for you already I don't know 00:39:12.320 --> 00:39:20.890 align:start position:0% everything for you already I don't know yeah<00:39:17.020> very<00:39:18.020> good<00:39:18.110> one 00:39:20.890 --> 00:39:20.900 align:start position:0% 00:39:20.900 --> 00:39:23.920 align:start position:0% afterward<00:39:21.740> of<00:39:22.100> the<00:39:22.370> domain<00:39:22.730> what<00:39:23.450> will<00:39:23.630> happen 00:39:23.920 --> 00:39:23.930 align:start position:0% afterward of the domain what will happen 00:39:23.930 --> 00:39:26.380 align:start position:0% afterward of the domain what will happen to<00:39:24.080> the<00:39:24.200> sub<00:39:24.380> domain<00:39:24.710> very<00:39:25.460> good<00:39:25.700> question<00:39:26.150> so 00:39:26.380 --> 00:39:26.390 align:start position:0% to the sub domain very good question so 00:39:26.390 --> 00:39:29.950 align:start position:0% to the sub domain very good question so there<00:39:27.140> are<00:39:27.290> what<00:39:27.830> happens<00:39:28.340> to<00:39:29.000> the<00:39:29.510> subdomains 00:39:29.950 --> 00:39:29.960 align:start position:0% there are what happens to the subdomains 00:39:29.960 --> 00:39:32.140 align:start position:0% there are what happens to the subdomains and<00:39:30.560> the<00:39:31.100> owner<00:39:31.310> of<00:39:31.460> the<00:39:31.670> subdomain 00:39:32.140 --> 00:39:32.150 align:start position:0% and the owner of the subdomain 00:39:32.150 --> 00:39:35.230 align:start position:0% and the owner of the subdomain if<00:39:32.390> you<00:39:32.510> transfer<00:39:33.170> the<00:39:33.830> main<00:39:34.550> domain<00:39:35.000> the 00:39:35.230 --> 00:39:35.240 align:start position:0% if you transfer the main domain the 00:39:35.240 --> 00:39:40.180 align:start position:0% if you transfer the main domain the parent<00:39:35.690> domain<00:39:36.170> so<00:39:36.830> you<00:39:37.790> still<00:39:38.600> own<00:39:39.470> your 00:39:40.180 --> 00:39:40.190 align:start position:0% parent domain so you still own your 00:39:40.190 --> 00:39:42.610 align:start position:0% parent domain so you still own your still<00:39:40.550> appear<00:39:41.180> as<00:39:41.360> the<00:39:41.570> owner<00:39:41.780> of<00:39:42.140> the 00:39:42.610 --> 00:39:42.620 align:start position:0% still appear as the owner of the 00:39:42.620 --> 00:39:45.910 align:start position:0% still appear as the owner of the subdomain<00:39:43.040> but<00:39:44.030> the<00:39:44.630> owner<00:39:44.870> of<00:39:45.230> the<00:39:45.410> parent 00:39:45.910 --> 00:39:45.920 align:start position:0% subdomain but the owner of the parent 00:39:45.920 --> 00:39:49.660 align:start position:0% subdomain but the owner of the parent has<00:39:46.280> the<00:39:47.030> power<00:39:47.390> to<00:39:47.900> take<00:39:48.890> it<00:39:49.040> away<00:39:49.130> from<00:39:49.310> you 00:39:49.660 --> 00:39:49.670 align:start position:0% has the power to take it away from you 00:39:49.670 --> 00:39:52.900 align:start position:0% has the power to take it away from you to<00:39:50.270> change<00:39:50.300> the<00:39:50.780> owner<00:39:50.990> unless<00:39:51.800> there<00:39:52.760> is<00:39:52.790> a 00:39:52.900 --> 00:39:52.910 align:start position:0% to change the owner unless there is a 00:39:52.910 --> 00:40:02.680 align:start position:0% to change the owner unless there is a special<00:39:54.070> registrar<00:39:55.210> right<00:39:59.680> so<00:40:01.150> as<00:40:02.150> Beltran 00:40:02.680 --> 00:40:02.690 align:start position:0% special registrar right so as Beltran 00:40:02.690 --> 00:40:04.390 align:start position:0% special registrar right so as Beltran sees<00:40:02.930> the<00:40:03.140> owner<00:40:03.290> of<00:40:03.470> a<00:40:03.530> domain<00:40:03.800> can<00:40:04.100> always 00:40:04.390 --> 00:40:04.400 align:start position:0% sees the owner of a domain can always 00:40:04.400 --> 00:40:06.430 align:start position:0% sees the owner of a domain can always change<00:40:04.820> the<00:40:05.180> ownership<00:40:05.450> of<00:40:05.750> any<00:40:06.200> of<00:40:06.320> the 00:40:06.430 --> 00:40:06.440 align:start position:0% change the ownership of any of the 00:40:06.440 --> 00:40:09.310 align:start position:0% change the ownership of any of the subdomains<00:40:07.180> so<00:40:08.180> you<00:40:08.570> should<00:40:08.750> really<00:40:08.900> only 00:40:09.310 --> 00:40:09.320 align:start position:0% subdomains so you should really only 00:40:09.320 --> 00:40:11.080 align:start position:0% subdomains so you should really only register<00:40:09.830> a<00:40:09.860> subdomain<00:40:10.220> of<00:40:10.370> a<00:40:10.520> domain<00:40:10.760> if<00:40:10.970> you 00:40:11.080 --> 00:40:11.090 align:start position:0% register a subdomain of a domain if you 00:40:11.090 --> 00:40:13.750 align:start position:0% register a subdomain of a domain if you trust<00:40:11.450> run<00:40:12.140> running<00:40:12.710> it<00:40:12.830> and<00:40:13.040> one<00:40:13.580> way<00:40:13.700> to 00:40:13.750 --> 00:40:13.760 align:start position:0% trust run running it and one way to 00:40:13.760 --> 00:40:15.610 align:start position:0% trust run running it and one way to trust<00:40:14.090> the<00:40:14.270> one<00:40:14.390> running<00:40:14.570> it<00:40:14.810> is<00:40:15.170> that<00:40:15.410> the<00:40:15.470> one 00:40:15.610 --> 00:40:15.620 align:start position:0% trust the one running it is that the one 00:40:15.620 --> 00:40:17.740 align:start position:0% trust the one running it is that the one running<00:40:15.890> it<00:40:15.980> is<00:40:16.100> actually<00:40:16.460> a<00:40:16.490> contract<00:40:17.000> so<00:40:17.690> you 00:40:17.740 --> 00:40:17.750 align:start position:0% running it is actually a contract so you 00:40:17.750 --> 00:40:19.330 align:start position:0% running it is actually a contract so you can<00:40:18.140> have<00:40:18.230> domains<00:40:18.590> that<00:40:18.800> are<00:40:18.920> owned<00:40:19.100> by 00:40:19.330 --> 00:40:19.340 align:start position:0% can have domains that are owned by 00:40:19.340 --> 00:40:20.950 align:start position:0% can have domains that are owned by contracts<00:40:19.940> and<00:40:20.120> they<00:40:20.210> can<00:40:20.390> enforce<00:40:20.720> rules 00:40:20.950 --> 00:40:20.960 align:start position:0% contracts and they can enforce rules 00:40:20.960 --> 00:40:22.660 align:start position:0% contracts and they can enforce rules about<00:40:21.380> how<00:40:21.620> two<00:40:21.680> main<00:40:21.920> subdomains<00:40:22.370> are 00:40:22.660 --> 00:40:22.670 align:start position:0% about how two main subdomains are 00:40:22.670 --> 00:40:24.370 align:start position:0% about how two main subdomains are creators<00:40:23.000> and<00:40:23.300> redistributions<00:40:23.960> and<00:40:24.110> so<00:40:24.230> on 00:40:24.370 --> 00:40:24.380 align:start position:0% creators and redistributions and so on 00:40:24.380 --> 00:40:26.740 align:start position:0% creators and redistributions and so on and<00:40:24.590> that's<00:40:25.100> basically<00:40:25.610> what<00:40:25.940> now<00:40:26.240> that<00:40:26.270> any 00:40:26.740 --> 00:40:26.750 align:start position:0% and that's basically what now that any 00:40:26.750 --> 00:40:28.300 align:start position:0% and that's basically what now that any stock<00:40:26.960> domains<00:40:27.230> is<00:40:27.410> doing<00:40:27.650> its<00:40:27.770> what<00:40:27.950> get<00:40:28.100> coin 00:40:28.300 --> 00:40:28.310 align:start position:0% stock domains is doing its what get coin 00:40:28.310 --> 00:40:30.430 align:start position:0% stock domains is doing its what get coin are<00:40:28.460> doing<00:40:28.700> if<00:40:29.510> you<00:40:29.690> look<00:40:29.870> at<00:40:29.990> the<00:40:30.080> source<00:40:30.290> of 00:40:30.430 --> 00:40:30.440 align:start position:0% are doing if you look at the source of 00:40:30.440 --> 00:40:32.170 align:start position:0% are doing if you look at the source of that<00:40:30.620> you<00:40:30.800> can<00:40:30.950> see<00:40:31.220> that<00:40:31.460> they<00:40:31.610> have<00:40:32.030> no 00:40:32.170 --> 00:40:32.180 align:start position:0% that you can see that they have no 00:40:32.180 --> 00:40:33.670 align:start position:0% that you can see that they have no mechanism<00:40:32.690> to<00:40:32.720> take<00:40:32.960> your<00:40:33.140> name<00:40:33.290> off<00:40:33.320> you 00:40:33.670 --> 00:40:33.680 align:start position:0% mechanism to take your name off you 00:40:33.680 --> 00:40:38.470 align:start position:0% mechanism to take your name off you basically<00:40:35.950> so<00:40:36.950> it's<00:40:37.130> trustless<00:40:37.910> and<00:40:38.240> they 00:40:38.470 --> 00:40:38.480 align:start position:0% basically so it's trustless and they 00:40:38.480 --> 00:40:46.800 align:start position:0% basically so it's trustless and they will<00:40:38.750> not<00:40:39.080> be<00:40:39.320> able<00:40:39.410> so<00:40:39.710> you<00:40:39.800> need<00:40:40.130> to<00:40:40.250> trust<00:40:40.610> or 00:40:46.800 --> 00:40:46.810 align:start position:0% 00:40:46.810 --> 00:40:50.590 align:start position:0% so<00:40:48.100> for<00:40:49.100> the<00:40:49.130> transition<00:40:49.910> to<00:40:50.090> the<00:40:50.240> new 00:40:50.590 --> 00:40:50.600 align:start position:0% so for the transition to the new 00:40:50.600 --> 00:40:53.680 align:start position:0% so for the transition to the new registrar<00:40:51.170> then<00:40:51.770> in<00:40:52.610> a<00:40:52.820> year<00:40:52.850> a<00:40:53.210> year<00:40:53.450> after 00:40:53.680 --> 00:40:53.690 align:start position:0% registrar then in a year a year after 00:40:53.690 --> 00:40:55.060 align:start position:0% registrar then in a year a year after the<00:40:53.750> transition<00:40:54.200> that<00:40:54.290> domain<00:40:54.650> will<00:40:54.830> go<00:40:54.980> away 00:40:55.060 --> 00:40:55.070 align:start position:0% the transition that domain will go away 00:40:55.070 --> 00:40:56.740 align:start position:0% the transition that domain will go away and<00:40:55.340> anyone<00:40:55.550> can<00:40:55.730> grab<00:40:55.940> it<00:40:55.970> and<00:40:56.300> that's<00:40:56.510> why 00:40:56.740 --> 00:40:56.750 align:start position:0% and anyone can grab it and that's why 00:40:56.750 --> 00:41:00.010 align:start position:0% and anyone can grab it and that's why we're<00:40:57.140> making<00:40:57.880> it<00:40:58.880> a<00:40:58.970> you<00:40:59.180> know<00:40:59.300> an<00:40:59.570> extended 00:41:00.010 --> 00:41:00.020 align:start position:0% we're making it a you know an extended 00:41:00.020 --> 00:41:02.110 align:start position:0% we're making it a you know an extended period<00:41:00.200> and<00:41:00.620> and<00:41:01.010> making<00:41:01.220> people<00:41:01.700> very<00:41:01.730> aware 00:41:02.110 --> 00:41:02.120 align:start position:0% period and and making people very aware 00:41:02.120 --> 00:41:04.390 align:start position:0% period and and making people very aware of<00:41:02.180> this<00:41:02.420> however<00:41:03.260> once<00:41:03.710> we've<00:41:03.950> moved<00:41:04.130> to<00:41:04.310> the 00:41:04.390 --> 00:41:04.400 align:start position:0% of this however once we've moved to the 00:41:04.400 --> 00:41:07.540 align:start position:0% of this however once we've moved to the permanent<00:41:04.610> registrar<00:41:05.210> the<00:41:06.140> goal<00:41:06.320> is<00:41:06.530> that<00:41:06.830> to 00:41:07.540 --> 00:41:07.550 align:start position:0% permanent registrar the goal is that to 00:41:07.550 --> 00:41:09.310 align:start position:0% permanent registrar the goal is that to prevent<00:41:07.910> this<00:41:08.060> sort<00:41:08.270> of<00:41:08.420> tragedy<00:41:09.170> of<00:41:09.260> the 00:41:09.310 --> 00:41:09.320 align:start position:0% prevent this sort of tragedy of the 00:41:09.320 --> 00:41:11.470 align:start position:0% prevent this sort of tragedy of the commoners<00:41:09.650> issue<00:41:09.830> anyone<00:41:10.460> can<00:41:10.760> read<00:41:10.940> it<00:41:11.150> can 00:41:11.470 --> 00:41:11.480 align:start position:0% commoners issue anyone can read it can 00:41:11.480 --> 00:41:13.270 align:start position:0% commoners issue anyone can read it can extend<00:41:11.810> the<00:41:11.960> registration<00:41:12.590> on<00:41:12.710> a<00:41:12.740> domain<00:41:13.070> even 00:41:13.270 --> 00:41:13.280 align:start position:0% extend the registration on a domain even 00:41:13.280 --> 00:41:15.789 align:start position:0% extend the registration on a domain even if<00:41:13.460> it<00:41:13.550> doesn't<00:41:13.790> belong<00:41:13.970> to<00:41:14.030> you 00:41:15.789 --> 00:41:15.799 align:start position:0% if it doesn't belong to you 00:41:15.799 --> 00:41:18.229 align:start position:0% if it doesn't belong to you so<00:41:16.799> time<00:41:17.279> is<00:41:17.489> up 00:41:18.229 --> 00:41:18.239 align:start position:0% so time is up 00:41:18.239 --> 00:41:22.849 align:start position:0% so time is up final<00:41:18.930> question<00:41:19.579> No<00:41:20.660> okay<00:41:21.660> so<00:41:21.719> this<00:41:22.499> is<00:41:22.650> it 00:41:22.849 --> 00:41:22.859 align:start position:0% final question No okay so this is it 00:41:22.859 --> 00:41:25.400 align:start position:0% final question No okay so this is it thank<00:41:23.400> you<00:41:23.430> very<00:41:23.489> much<00:41:23.729> for<00:41:23.880> coming<00:41:24.269> and<00:41:24.420> yeah 00:41:25.400 --> 00:41:25.410 align:start position:0% thank you very much for coming and yeah 00:41:25.410 --> 00:41:28.009 align:start position:0% thank you very much for coming and yeah great<00:41:26.309> so<00:41:26.430> now<00:41:26.579> it's<00:41:26.759> your<00:41:26.999> time<00:41:27.180> to<00:41:27.420> put<00:41:27.869> on 00:41:28.009 --> 00:41:28.019 align:start position:0% great so now it's your time to put on 00:41:28.019 --> 00:41:30.259 align:start position:0% great so now it's your time to put on the<00:41:28.049> sticker<00:41:28.589> and<00:41:28.619> they're<00:41:28.920> like<00:41:29.039> chill<00:41:29.339> ENS 00:41:30.259 --> 00:41:30.269 align:start position:0% the sticker and they're like chill ENS 00:41:30.269 --> 00:41:31.069 align:start position:0% the sticker and they're like chill ENS like<00:41:30.569> crazy 00:41:31.069 --> 00:41:31.079 align:start position:0% like crazy 00:41:31.079 --> 00:41:36.739 align:start position:0% like crazy yes<00:41:34.489> what<00:41:35.489> are<00:41:35.519> the<00:41:35.670> requirements<00:41:36.269> for<00:41:36.539> the 00:41:36.739 --> 00:41:36.749 align:start position:0% yes what are the requirements for the 00:41:36.749 --> 00:41:39.709 align:start position:0% yes what are the requirements for the workshop<00:41:37.489> for<00:41:38.489> the<00:41:38.700> hands<00:41:39.029> on<00:41:39.269> integration 00:41:39.709 --> 00:41:39.719 align:start position:0% workshop for the hands on integration 00:41:39.719 --> 00:41:44.420 align:start position:0% workshop for the hands on integration workshop<00:41:41.509> daddy<00:41:42.509> Papa<00:41:43.160> that<00:41:44.160> you're<00:41:44.400> a 00:41:44.420 --> 00:41:44.430 align:start position:0% workshop daddy Papa that you're a 00:41:44.430 --> 00:41:51.279 align:start position:0% workshop daddy Papa that you're a developer<00:41:45.019> that's<00:41:46.019> it<00:41:46.229> that's<00:41:46.650> it<00:41:49.400> thank<00:41:50.400> you 00:41:51.279 --> 00:41:51.289 align:start position:0% developer that's it that's it thank you 00:41:51.289 --> 00:41:53.509 align:start position:0% developer that's it that's it thank you okay<00:41:52.289> thank<00:41:52.319> you<00:41:52.529> guys<00:41:52.619> thank<00:41:53.099> you<00:41:53.130> for<00:41:53.190> coming 00:41:53.509 --> 00:41:53.519 align:start position:0% okay thank you guys thank you for coming 00:41:53.519 --> 00:42:03.059 align:start position:0% okay thank you guys thank you for coming thank<00:41:53.670> you<00:41:53.849> very<00:41:53.999> much 00:42:03.059 --> 00:42:03.069 align:start position:0% 00:42:03.069 --> 00:42:05.130 align:start position:0% you