Upsert resolvers on setting, which ensures that any resolver actively used in the ENS ecosystem has an entry in the index. At that upsert location, we can also query supports interfaces and add those. This lets us always accelerate extended and bridged queries.
We can then remove the manual configuration of bridge resolvers and inject it into the index once again, which is convenient.
This needs to take into account underlying resolvers, and then it should recursively create resolver contract entries for each of the underlying resolvers.
then we can support underlying {} and so on
Upsert resolvers on setting, which ensures that any resolver actively used in the ENS ecosystem has an entry in the index. At that upsert location, we can also query supports interfaces and add those. This lets us always accelerate extended and bridged queries.
We can then remove the manual configuration of bridge resolvers and inject it into the index once again, which is convenient.
This needs to take into account underlying resolvers, and then it should recursively create resolver contract entries for each of the underlying resolvers.
then we can support
underlying {}and so on