Back to Home

globalregistrar

Registry
0x2272d8d4dec7...decc6918f1a9
FrontierContract #130Source VerifiedEdit this contract
Deployed August 10, 2015 (10 years ago)Block 63,331

A second deployment of the Ethereum GlobalRegistrar — the early name registry that predated ENS — made on August 10, 2015.

Frontier EraVerified Source

Historical Significance

The GlobalRegistrar is a direct precursor to the Ethereum Name Service (ENS). Before ENS, these early registrars were the only mechanism for on-chain name resolution on Ethereum. They established the conceptual foundation — names mapped to addresses, with ownership and renewal mechanisms — that ENS later formalized. The TODO comments in the source code document how unfinished the infrastructure was in Ethereum's first weeks.

Context

Ethereum launched without a built-in name resolution system. Within the first two weeks, multiple developers deployed name registry contracts following patterns described in the official Ethereum documentation. These early registrars were functional but lacked auction mechanisms, dispute resolution, and the standardized resolver architecture that ENS introduced in 2017. ENS became the dominant naming system for Ethereum and displaced all early ad-hoc registrars.

Key Facts
Deployment Block
63,331
Deployment Date
Aug 10, 2015, 10:31 AM
Code Size
2.8 KB
Gas at Deploy
779,965
Transactions by Year
20154
2022303

Description

This contract is a deployment of the GlobalRegistrar, an early Ethereum name registry system that allowed users to claim human-readable names and associate them with Ethereum addresses. It was deployed at block 63,331 on August 10, 2015 by address 0xdd38c62d238be6bb72162afec32ddccedd3a0a51.

The GlobalRegistrar implements three interfaces: NameRegister (basic name-to-address resolution), Registrar (with owner, address, subRegistrar, and content fields per name), and GlobalRegistrar (the full implementation). Names are reserved via the reserve(bytes32 _name) function on a first-come, first-served basis — the contract explicitly notes a TODO for a proper bidding mechanism.

The source code contains several unfinished TODO comments, including a planned auction for short names (12 characters or fewer) and a hall-of-fame in the constructor. This reflects the iterative, draft nature of early Ethereum infrastructure development.

The Linagee Name Registrar at 0x5564886ca2c518d1964e5fcea4f423b41db9f561 (deployed August 8, 2015) is an earlier deployment of equivalent functionality. Both contracts represent the proto-ENS era of Ethereum naming — before the Ethereum Name Service launched in May 2017.

Source Verified

Etherscan verified
Heuristic Analysis

The following characteristics were detected through bytecode analysis and may not be accurate.

Detected Type: Registry

Bytecode Overview

Opcodes2,894
Unique Opcodes147
Jump Instructions72
Storage Operations62

External Links