==== EIP 181: ENS support for reverse resolution of Ethereum addresses ==== [[dido:public:ra:xapend:xapend.b_stds:defact:ethereum:eip| Return to Ethereum ERCs ]] : **Note**: The following is an excerpt from the official Ethereum site. It is provided here as a convenience and is not authoritative. Refer to the original document as the authoritative reference. | Title | ENS support for reverse resolution of Ethereum addresses | | Author | Nick Johnson | | Status | Final | | Created | 2016-12-01 | | Description | [[http://eips.ethereum.org/EIPS/eip-181]] | | Specification | [[http://eips.ethereum.org/EIPS/eip-181#Specification]] | | Category | ERC |
Data sheet for ENS support for reverse resolution of Ethereum addresses
=== Abstract === : //This EIP specifies a TLD, registrar, and resolver [[dido:public:ra:xapend:xapend.a_glossary:i:interface|interface]] for reverse resolution of Ethereum addresses using ENS. This permits associating a human-readable name with any Ethereum [[dido:public:ra:xapend:xapend.a_glossary:b:blockchain|blockchain]] address. Resolvers can be certain that the reverse record was published by the owner of the Ethereum address in question.// === Motivation === : //While name services are mostly used for forward resolution - going from human-readable identifiers to machine-readable ones - there are many use-cases in which reverse resolution is useful as well:// ://1. Applications that allow users to monitor accounts benefit from showing the name of an account instead of its address, even if it was originally added by address.// ://2. Attaching [[dido:public:ra:xapend:xapend.a_glossary:m:metadata|metadata]] such as descriptive information to an address allows retrieving this information regardless of how the address was originally discovered.// ://3. Anyone can configure a name to resolve to an address, regardless of ownership of that address. Reverse records allow the owner of an address to [[dido:public:ra:xapend:xapend.a_glossary:c:claim|claim]] a name as authoritative for that address.//