Delegatable resolver registrar

[makoto]

A minimum registrar that allows the contract to approve user to update subnames.

[jefflau]

Just had a thought as well. If this is being deployed per user, it could also just be the same contract as the DelegatableResolver. Then you wouldn't have to approve the registrar on the resolver and save a transaction and UX.

[Arachnid]

Is this intended to be used in prod, or just as an example registrar?

[makoto]

Is this intended to be used in prod, or just as an example registrar? more as an example. I initially just had it as a gist, but had problem compiling via remix, hence decided to put into our contract. I don't mind taking this out completely from ens-contracts repo and put that in evmgateway repo instead

[Arachnid]

I don't think this does what you want. It won't prevent duplicate subdomains, because it only prevents the same person being issued the same name twice. I think instead you need to keep a mapping of issued names, or modify the DelegatableResolver to keep track of issued names.

[makoto]

That's my intention. I only added it to avoiding existing operator to waste the gas. Not sure restricting multiple subname operators at registrar level makes sense because the owner of the resolver contract can always approve multiple operators. If we want to change the delegatable resolver to only have single owner per subname, I think I need to add registrar feature directly in the resolver as @jefflau initially suggested.

[makoto]

Going to close this as I added the contract into evmgateway at https://github.com/ensdomains/evmgateway/pull/23/files