contenthash
field for ENS resolvers, allowing for a better defined system of mapping names to network and content addresses. Additionally the content
and multihash
fields are deprecated.contenthash
field allows for easy specification of network and content addresses in ENS.contenthash
is introduced, which permits a wide range of protocols to be supported by ENS names. Resolvers supporting this field MUST return true
when the supportsInterface
function is called with argument 0xbc1c58d1
.content
and multihash
are deprecated.contenthash
MUST be represented as a machine-readable multicodec. The format is specified as follows:contenthash
, applications MUST use the protocol code to determine what type of address is encoded, and resolve the address appropriately for that protocol, if supported.content
field, a grace period MUST be implemented offering those name holders time to update their names. If a resolver does not support the multihash
interface, it MUST be checked whether they support the content
interface. If they do, the value of that field SHOULD be treated in a context dependent fashion and resolved. This condition MUST be enforced until at least March 31st, 2019.contenthash
, a new resolver has been developed and can be found here, you can also find this smart contract deployed on:contenthash
: