Closed makoto closed 9 months ago
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.
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
Going to close this as I added the contract into evmgateway
at https://github.com/ensdomains/evmgateway/pull/23/files
A minimum registrar that allows the contract to approve user to update subnames.