Documentation Index
Fetch the complete documentation index at: https://voltaire.tevm.sh/llms.txt
Use this file to discover all available pages before exploring further.
Skill — Copyable reference implementation. Use as-is or customize. See Skills Philosophy.
ENS Resolution
Resolve Ethereum Name Service (ENS) names to addresses and retrieve ENS records using Voltaire primitives and Contract modules.Overview
ENS resolution requires two components:- Ens module - Name validation, normalization, and namehash computation
- Contract module - Interacting with ENS registry and resolver contracts
Contract Addresses (Mainnet)
| Contract | Address |
|---|---|
| ENS Registry | 0x00000000000C2E074eC69A0dFb2997BA6C7d2e1e |
| Public Resolver | 0x231b0Ee14048e9dCcD1d247744d114a4EB5E8E63 |
| Reverse Registrar | 0xa58E81fe9b61B5c3fE2AFD33CF304c454AbFc7Cb |
Resolving ENS Name to Address
Reverse Resolution (Address to ENS)
Reverse resolution looks up the primary ENS name for an address.Getting ENS Records
ENS supports various text records like avatar, email, URL, and custom records.Common Text Record Keys
| Key | Description |
|---|---|
avatar | NFT or URL for profile image |
url | Website URL |
description | Profile description |
email | Email address |
com.twitter | Twitter/X handle |
com.github | GitHub username |
com.discord | Discord username |
notice | Legal notice |
ENS Name Validation
Validate ENS names before resolution to prevent homograph attacks.Computing Namehash
The namehash is a recursive hash used to identify ENS names on-chain.Full Resolution Helper
A complete helper function combining all functionality:L2 ENS Resolution
For L2 networks, use the same contract addresses but connect to an L1 provider for resolution, or use CCIP-read compatible resolvers.See Also
- Ens Primitives - Name normalization and validation
- Contract - Contract interaction module
- ENS Documentation - Official ENS docs
- ENSIP-15 - Normalization standard

