ENS names vs Ethereum addresses
An ENS name is a human-readable name with records that applications can resolve. The name itself is not a 20-byte Ethereum address, and records can change.
Worked example
| Input | Type | Needed check |
|---|---|---|
| name.eth | Illustrative ENS placeholder | Resolve in a trusted application |
| 0x + 40 hex | Address representation | Network and recipient confirmation |
| Displayed reverse name | Name associated with an address | Forward resolution and context |
Resolve before relying on a name
ENS can store records for different address types. The receiving application must support the relevant record and network context. Check the resolved full address and intended recipient before using it; a familiar name is not evidence that every asset can be received.
Names can move or change
Ownership and resolver records are separate from an immutable address string. An address saved after resolving a name is a snapshot, while the name may resolve differently later. Look-alike characters and copied display names deserve the same care as look-alike addresses.
Common pitfalls
- name.eth is an illustrative placeholder here, not a verified recipient.
- A reverse name shown by an explorer is not a project endorsement.
Related references
Primary sources
Examples explain identifiers. They are not investment recommendations.