You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 27, 2023. It is now read-only.
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.
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.)
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.)
The text was updated successfully, but these errors were encountered: