This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | |||
|
dido:public:ra:xapend:xapend.b_stds:defact:ethereum:eip:erc_0181 [2021/08/06 17:35] murphy |
dido:public:ra:xapend:xapend.b_stds:defact:ethereum:eip:erc_0181 [2021/08/09 15:01] (current) murphy |
||
|---|---|---|---|
| Line 21: | Line 21: | ||
| : //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.// | ://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.// | + | ://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.// | ://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.// | ||