Founders & Origins4 min readEthereum Name Service (ENS)

ENS: From a Name to a Payment Address

ENS began allocating .eth names in 2017 with a five-day auction. Its journey to renewable registration reveals three different jobs: assigning a name, controlling its records and finding the address behind it.

ENS: From a Name to a Payment Address

3-Minute Fast Briefing

  • The ParadoxThe initial .eth registrar launched on May 4, 2017, with sealed bids and a separate reveal period.
  • The Turning PointThe permanent registrar launched in May 2019 with registration and renewal; “permanent” did not mean a name could never expire.
  • The LegacyA name’s owner and its payment destination are different records. Resolution turns the readable name into the address a wallet can use.

Chronological Timeline

May 4, 2017The initial registrar launches

Names of at least seven characters become available under an auction system.

May 4, 2019The permanent registrar launches

A registration-and-renewal system replaces the temporary registrar, with a migration path for existing holders.

Five Days for a Shorter Address

In May 2017, getting an Ethereum name could mean waiting through five days of an auction. The initial Ethereum Name Service registrar, deployed on May 4, accepted sealed bids for 72 hours, then allowed 48 hours for bidders to reveal them. The winner still had to finalize the result. A service meant to make cryptocurrency easier to use began with a surprisingly demanding introduction.[1]

The designers had a reason to move cautiously. Useful names could be acquired simply to hold for resale. The initial system allowed names of at least seven characters, released availability gradually and used a second-price auction. It was explicitly temporary: the specification left room to learn from the experiment. These were rules for distributing scarce names, before a wallet ever tried to send money to one.[1]

The Nameplate and the Destination

ENS separated that allocation problem from the lookup itself. A registrar set the rules for obtaining a name. The registry recorded who controlled it and which resolver to ask. The resolver supplied information such as an Ethereum address. The division mattered: the address that controlled the name was not automatically the address that should receive a payment.[2][7]

Think of a nameplate and a forwarding address as a metaphor. Keeping the same nameplate does not require keeping the same destination. In the original ENS design, a wallet first found the resolver through the registry, then asked that resolver for the address. The familiar-looking name was an entry point into maintained records, not a replacement for the account to which the transaction would actually be sent.[2]

A Permanent Registrar, a Renewable Name

The next milestone came on May 4, 2019. ENS’s mainnet release introduced the permanent registrar. Its release-era documentation separated the base contract handling ownership from controllers handling registration and renewal. Existing holders could migrate during a one-year transition and recover their old deposits. The name could move into a new registration system without asking everyone to start the naming experiment again.[3][4]

“Permanent” described the registrar, not unlimited possession of every name. Users paid to register for a duration and could extend that period by renewing. The new flow also retained a hidden first step: commit a hash, wait, then reveal the registration request. This time the purpose was to prevent an observer from seeing a desired name in a pending transaction and racing to register it first. It was not another five-day bidding contest.[4][5]

An Easier Label Still Needs Care

The redesign put the ongoing work in clearer places. Registration acquired the name, renewal maintained its term, and the lookup records determined where it led. In the 2019 contracts, even someone other than the owner could pay for a renewal. Paying to extend a name and having authority to change it were deliberately different powers.[4]

The same care appears when going in the other direction. ENS documentation says an application displaying an address’s preferred name should resolve that name back to an address and check that they match. A readable label alone is not enough. ENS made a long address easier to share, but the useful achievement lies in the round trip: a person recognizes a name, software follows its records, and the destination still has to be the intended one.[6]

Connected Lore & Universe

Connected Stories in this Universe

Explore the chain reaction of historical breakthroughs, blunders, and legends.

Sources & References

  1. [1]Source 1: ENSIP-2: Initial Hash RegistrarENSAccessed 2026-09-17
  2. [2]Source 2: ENSIP-1: ENSENSAccessed 2026-09-17
  3. [3]Source 3: May 4 2019 launch on mainnetENS / GitHubAccessed 2026-09-17
  4. [4]Source 4: Eth Registrar — mainnet release READMEENS / GitHubAccessed 2026-09-17
  5. [5]Source 5: ETH RegistrarENSAccessed 2026-09-17
  6. [6]Source 6: ResolutionENSAccessed 2026-09-17
  7. [7]Source 7: The RegistryENSAccessed 2026-09-17
← Back to all storiesExplore all coins →