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.
Testing on ropsten right now for reverse records and the setName is using an old public resolver. Seems like it would make sense to make this dynamic to get the address of 'resolver.eth' so as the public resolver gets upgraded, this contract will also use the updated resolver.
The text was updated successfully, but these errors were encountered:
jefflau
changed the title
Dynamic resolver
Dynamic resolver for reverse registrar
Nov 6, 2018
Does it matter that it uses a different resolver? The idea of setName is to provide a quick and easy option for just setting the name; it doesn't require broader support than that.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
ens/contracts/ReverseRegistrar.sol
Line 23 in 9f0dc10
Testing on ropsten right now for reverse records and the setName is using an old public resolver. Seems like it would make sense to make this dynamic to get the address of 'resolver.eth' so as the public resolver gets upgraded, this contract will also use the updated resolver.
The text was updated successfully, but these errors were encountered: