Please set resolver.eth on ropsten to new resolver

[makoto]

I think it's still pointing to the old one as specifying the default resolver gives warning that i have to update resolver.

[makoto]

You can point to 0xde469c7106a9FBC3fb98912bB00be983a89bDDca which is deployed by someone outside of ENS team.

[makoto]

Shall we rather ditch the idea of resolving via ENS name and take from the resolver address of the parent domain or shall we add into interfaceImplementer ?

https://gitter.im/ethereum/go-ethereum/name-registry?at=5cc8d9603b6cb0686a7fdaac

[mcdee]

What should be official way of obtaining the public resolver for eth? We seem to have two different methods at current:

• obtain the address of resolver.eth
• obtain the resolver of eth

Given that resolver.eth would need to continue to be renewed over time to retain the functionality I'd prefer the second option, but don't much mind either way.

(And just as a point of order: the current resolver for eth on ropsten is pointing to an instance of OwnedResolver so it doesn't suit for a public resolver. Any chance of fixing that, assuming that this is the way that is chosen to go to provide the address of the public resolver?)

[Arachnid]

Checking the resolver of .eth is definitely not a solution. It would require us to use the public resolver for that, requires us to migrate records every time there's an update, and is .eth specific.

For now, looking up resolver.eth is the official discovery mechanism, though using interface discovery on the parent name seems worth exploring.

[lyricalpolymath]

just checked and the manager on ropsten still faces this issue ensdomains/ens-app#211 because resolver.eth is not set on ropsten to
0xde469c7106a9FBC3fb98912bB00be983a89bDDca

0xde469...DDca is the new resolver, that we used for verifying ipfs contenthash
https://manager.ens.domains/name/ipfs.devtest.eth