Skip to content
This repository has been archived by the owner on Sep 27, 2023. It is now read-only.

migration of reverse resolver records #352

Open
saurik opened this issue Apr 17, 2020 · 0 comments
Open

migration of reverse resolver records #352

saurik opened this issue Apr 17, 2020 · 0 comments

Comments

@saurik
Copy link

saurik commented Apr 17, 2020

Hello! I have a existing contract (0x267bb56749249cf7c9425e9ac6bf2d31cdc2e661) that was previously set up for ENS reverse resolution, by having it call .claim() on what is now the "old" reverse registrar (0x9062C0A6Dbd6108336BcBe4593a3D1cE05512069) in its constructor.

Now, when I go to https://app.ens.domains/name/267bb56749249cf7c9425e9ac6bf2d31cdc2e661.addr.reverse it tells me that this name needs to be migrated, but that "only the parent of this name (addr.reverse) can do this". (As far as I can tell, all of my top-level forward records were migrated by ENS.)

Is reverse resolution just not really supported across this migration? Did I do something wrong when I created this contract, and if so how should I do things differently for future contracts? (I am about to burn all of my contracts I set up with ENS anyway, so it isn't a big deal to fix stuff.)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant