dido:public:ra:xapend:xapend.b_stds:defact:ethereum:eip:erc_0181
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
dido:public:ra:xapend:xapend.b_stds:defact:ethereum:eip:erc_0181 [2020/05/07 18:56] nick ↷ Page moved from dido:public:xapend.stds:defact:ethereum:eip:erc_0181 to dido:public:ra:xapend.stds:defact:ethereum:eip:erc_0181 |
dido:public:ra:xapend:xapend.b_stds:defact:ethereum:eip:erc_0181 [2021/08/09 15:01] (current) murphy |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ======== EIP 181: ENS support for reverse resolution of Ethereum addresses ========= | + | ==== EIP 181: ENS support for reverse resolution of Ethereum addresses ==== |
| - | [[dido:public:xapend.stds:defact:ethereum| Return to Ethereum ERCs ]] | + | [[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 connivence and is not authoritative. Refer to the original document as the authoritative reference. | + | : **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> | <table> | ||
| Line 15: | Line 15: | ||
| </table> | </table> | ||
| - | ====== Abstract ====== | + | === 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.// | + | : //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 ====== | + | === 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:// | : //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.// | |
| - | - //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.// |
| - | - //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 [[dido:public:ra:xapend:xapend.a_glossary:c:claim|claim]] a name as authoritative for that address.// |
| - | - //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.1588892173.txt.gz · Last modified: 2020/05/07 18:56 by nick
