Support ENS names instead of fixed addresses

Would ENS resolution be in the scope of what this metadata repository intends to support?

For example, the Wyvern Protocol is self-upgrading and may change contracts later, so it would be convenient to register the smart contract under an ENS name instead of a fixed address. Other projects with proxy contracts or upgrade mechanisms may share this preference.

The issue names no files, tests, or entry points. First clarify whether this metadata repository should support ENS resolution for upgradeable contracts and how that fits its fixed-address mapping; done would be an agreed scope and implementation approach.

Written by the indexing model from the issue text.