globalregistrar

The GlobalRegistrar contract (deployed at block 110,226 on August 19, 2015) served as Ethereum's first persistent, on-chain name resolution system. It implemented a hierarchical naming architecture through which any account could reserve a human-readable name and associate it with an address, a sub-registrar, or arbitrary content hash. Names were first-come, first-served: once a bytes32 identifier was claimed, only the owner could transfer or disown it. The contract was compiled with Solidity v0.1.1—one of the earliest released compiler versions—and authored in the style of the canonical dapp-bin examples maintained by the Ethereum Foundation.

This deployment (sometimes called version 9, or "v9") is notable for being the instance that was eventually hardcoded into the go-ethereum (Geth) client as the official registrar address. Prior to this, users had to manually load the registrar address each session; after the hardcoding, eth.namereg pointed directly to this contract by default, making it the de-facto human-name layer for the Frontier network.

The contract sits within a lineage of 19 nearly-identical deployments of the same source code—ranging from the very first deployment by Linagee (v0, block 51,807) through several intermediate versions—as the Ethereum community converged on a single authoritative instance. Each earlier iteration was rendered obsolete once the community adopted v9. The source code itself left room for a planned but never-implemented auction mechanism for short names, visible in the inline TODO comments, a window into the rapid, iterative development culture of the early Ethereum ecosystem.

Historically, the GlobalRegistrar represents the first attempt at a decentralized naming service on Ethereum, pre-dating the Ethereum Name Service (ENS) by roughly two years. Where ENS later introduced a fully decentralised auction and resolver architecture, the GlobalRegistrar operated on simple first-come-first-served reservation and manual address association.