EIP-137

EIP-137
Title	EIP-137
Othernames	Ethereum Name Service (ENS) Namehashing Proposal
Status	Final
Author	Nick Johnson
Type	Standards Track
Category	Interface
Created	2016
Updated	2017

EIP-137

EIP-137 is a standards-track Ethereum proposal that specifies a namehash algorithm and registry interface for hierarchical name resolution, forming a cornerstone of the Ethereum namespace and the Ethereum Name Service ecosystem. The proposal defines canonical hashing, ownership semantics, and public resolver interactions to enable human-readable identifiers to map to Ethereum addresses and other resources. It influenced integrations across wallets, explorers, and infrastructure providers within the broader Web3 and DeFi landscapes.

Background

EIP-137 emerged amid early efforts to make Ethereum addresses more usable for applications such as MetaMask, MyEtherWallet, and blockchain explorers like Etherscan. The proposal intersects with prior naming systems such as the Domain Name System and projects like Namecoin while drawing attention from major projects including Consensys, Parity Technologies, Infura, and Gnosis Safe. Key contributors and reviewers included engineers affiliated with PegaSys, Truffle Suite, MakerDAO, and academic groups from MIT and UC Berkeley that studied human factors in decentralized identifiers. Discussions took place across public venues such as the Ethereum Magicians forum, the Ethereum Foundation repositories, and community calls attended by figures from Chainlink, 0x Project, and Uniswap.

Specification

The specification defines a deterministic namehash function that converts hierarchical labels into fixed-length hashes compatible with Keccak-256 and the Ethereum Virtual Machine. It prescribes registry methods for creating top-level owner entries, assigning subnode ownership, and setting resolver contracts, aligning with interfaces used by projects such as ENS Labs and implementations by OpenZeppelin. The EIP details events and function signatures that integrate with tooling including Web3.js, ethers.js, Geth, and Parity. It references cryptographic primitives popularized by SHA-3 contests and standardization efforts within organizations like the IETF and NIST, and it codifies behavior relevant to wallets such as Ledger and Trezor.

Address Abbreviations and ENS Integration

EIP-137 enables mappings from human-readable names to resources such as Ethereum addresses, content hashes used by IPFS, metadata referenced by Swarm, and application-specific keys used by Metamask and WalletConnect. The proposal's resolver patterns allow integration with directory services used by Unstoppable Domains, Handshake, and legacy DNS providers like Cloudflare and Amazon Route 53 via bridges implemented by teams at Protocol Labs and Fleek. Integration work was carried out by contributors from Status, Augur, Aragon, and Gnosis to support name-based interactions in DAOs, prediction markets, and multisig workflows. The specification's compatibility with ENS registries made it a default for mapping aliases used in Compound Finance, Aave, and MakerDAO front-ends.

Security Considerations

Security analysis of the specification considers ownership transfers, subdomain delegation, and resolver trust models, with risk assessments presented by auditors at firms such as Trail of Bits, OpenZeppelin Audits, and Consensys Diligence. Threat models reference attack vectors observed in incidents involving Mt. Gox, The DAO, and Parity Multisig to stress-test governance and recovery mechanisms. The EIP warns about phishing risks exploited across platforms like Etherscan, MyEtherWallet, and MetaMask and recommends integration patterns that projects such as Ledger and Trezor can adopt to mitigate private-key exposure. Best practices influenced by standards bodies including ISO and audits by CertiK were adopted by deployments used by Compound Labs and Balancer Labs.

Implementation and Adoption

Multiple implementations of the registry and resolver interfaces were developed by teams at ENS Labs, Consensys, Truffle Suite, OpenZeppelin, and community contributors from repositories hosted under the Ethereum Foundation organization. Major infrastructure providers including Infura, Alchemy, and Cloudflare added support for ENS name resolution APIs, while wallets such as MetaMask, Trust Wallet, and Argent integrated lookups to resolve human-friendly names. Decentralized applications in the DeFi sector—such as Uniswap, SushiSwap, Compound Finance, and Aave—adopted ENS name resolution to present readable counterparty identifiers. Academic courses at MIT, UC Berkeley, and Stanford used the specification in curricula covering decentralized systems, and standards discussions continued in forums like Ethereum Magicians and conferences including Devcon and ETHGlobal.

Compatibility and Alternatives

EIP-137 coexists with alternative naming and identifier schemes including Namecoin, Handshake, Unstoppable Domains, and decentralized identifier efforts promoted by the W3C's DID working group. Implementers evaluate trade-offs with DNS-based mappings enabled by DNSSEC and gateway strategies employed by Cloudflare and Amazon Route 53, as well as compatibility layers used by ENS Labs to interoperate with IPFS and Swarm. Competing approaches for human-readable identifiers appear in projects like Keybase, DIDComm, and Solid Project, while blockchain platforms such as Tezos, Polkadot, Solana, and NEAR Protocol have developed their own naming conventions and registries.

Category:Ethereum Improvement Proposals