Hey everyone! We are having our 3rd annual ENS Workshop later this year and would love for you to attend. It'll be on October 7th (day before Devcon) in Osaka near the Devcon conference site. We'll be discussing the current state and future of ENS. You have to submit an application to attend by the end of the month.
check buttonwhich in turn doesn't mention exactly what the value it got from the TXT record, thus you can end up a lambo which I'm currently stuck in which either the value your system has is cached (which sucks since I have a long TTL) or the value I have is wrong (which doesn't seem to be the case).
@Iamchauncey_lee_twitter controller has a power to set resolver, address, etc. registrant has a power to set the controller.
Thank you for detailed explaination. I find I can still set address for an ens after I transfered the registrant to another address, so I transfered both registant and controler to the new owner.
Your name was rejected because the name you claimed has a commonly understood meaning in the Ethereum or wider Internet community
It sounds like that was supposed to be read more like:
Your name was rejected because:
- it has a commonly understood meaning in the Ethereum/wider Internet community
@Laramie43ip you should be able to just copy the keystores over; as long as you retain the directory structure they should work.
Migrating multiple domains you can either write individual commands, e.g.
ethereal ens migrate --passphrase=secret --domain=mydomain1.eth ethereal ens migrate --passphrase=secret --domain=mydomain2.eth ...
or you can supply multiple domains on the single command, e.g.:
ethereal ens migrate --passphrase=secret --domains='mydomain1.eth&&mydomain2.eth'
There isn't a lot of difference between them, so whichever you prefer