User Tools

Site Tools


Sidebar

Welcome to DIDO WIKI

dido:public:ra:xapend:xapend.b_stds:defact:ethereum:eip:erc_0181

EIP 181: ENS support for reverse resolution of Ethereum addresses

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.
Table 1: Data sheet for ENS support for reverse resolution of Ethereum addresses
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

Abstract

This EIP specifies a TLD, registrar, and resolver interface for reverse resolution of Ethereum addresses using ENS. This permits associating a human-readable name with any Ethereum 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 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 claim a name as authoritative for that address.
dido/public/ra/xapend/xapend.b_stds/defact/ethereum/eip/erc_0181.txt · Last modified: 2021/08/09 15:01 by murphy
Translations of this page: