.text(namehash(name), 'avatar')
on it to retrieve the avatar URI for the name.addr
method on the resolver, or an empty string returned by the resolver identically, as a failure to find a valid avatar URI.<address>.addr.reverse
, where <address>
is the lowercase hex-encoded Ethereum address, without leading '0x'. Then, the client calls .text(namehash('<address>.addr.reverse'), 'avatar')
to retrieve the avatar URI for the address.text
causes a revert or returns an empty string, the client MUST call .name(namehash('<address>.addr.reverse'))
. If this method returns a valid ENS name, the client MUST:addr
on the resolver, checking it matches the original Ethereum address.image/jpeg
, image/png
, and image/svg+xml
. Clients MAY support additional image types.https
ipfs
data
avatar
field URI.https
and ipfs
URIs for resolving the metadata URI and the avatar image, and MAY support additional schemes. Clients MAY implement ifps
scheme support by rewriting the URI to an HTTPS URL referencing an IPFS gateway as described above.addr
function on the same resolver and for the same name to retrieve the Ethereum address to which the name resolves. Otherwise, if the avatar URI was retrieved via reverse resolution (starting from an Ethereum address), use that address.https
URIs for a service that provides NFT avatar image resolution support.