ENS Renamed Two Contracts and Left One Hanging. Here Is What That Actually Means.

The ENS contract naming season started in May 2026 with a simple idea: make the code readable. By August, ETHRegistrarController had become NameRegistrar. ENSRegistry had become ENSRegistryImpl. Two out of three targets hit. The third — ReverseRegistrar — is still stuck, and the accountability summary published August 18 tells a story more interesting than the names themselves.

I read the summary twice. Once for the labels. Once for what the labels hide.

Key Metrics at a Glance

What Actually Happened

In May 2026, ENS governance launched a contract naming season. The goal was to replace opaque, historically accurate names with labels that describe what the contract actually does. The targets were:

• ETHRegistrarController → NameRegistrar
• ENSRegistry → ENSRegistryImpl
• ReverseRegistrar → ???

The first two succeeded. Governance passed the necessary proposals. Developers deployed the new implementations. Users calling the contracts now see names that tell them what they are looking at instead of what committee named them five years ago.

The ReverseRegistrar did not make it. The accountability summary, published on the ENS governance forum, is candid about why. The contract sits behind a proxy that cannot be safely upgraded without a technical workaround that has not been resolved. The risk is not theoretical. A failed proxy upgrade can brick a contract. In ENS's case, that would mean users could not register or update reverse records — the .eth addresses that map Ethereum addresses to human-readable names.

The Competitive Landscape

The table is not about vanity. Contract names are the first line of documentation. A developer auditing a protocol starts with the names. If the names lie — or if they describe a reality that no longer exists — the audit starts on false premises.

ENS improved its documentation by renaming two contracts. The fact that one remains unresolved is not a failure of intent. It is a failure of execution, and the public acknowledgment of that failure is what separates accountable governance from marketing.

Why the ReverseRegistrar Matters More Than It Sounds

The ReverseRegistrar is the contract that lets an Ethereum address claim a reverse record. When you see vitalik.eth resolving to an address, that is the forward lookup. When you see an address resolving back to vitalik.eth, that is the reverse lookup, and it happens through the ReverseRegistrar.

If the ReverseRegistrar proxy upgrade fails, the damage is not just cosmetic. Applications that rely on reverse resolution — wallet interfaces, block explorers, identity verification tools — lose a critical mapping. Users who have configured reverse records could find those records frozen or inaccessible.

The ENS team knows this. That is why they stopped. The accountability summary makes clear that the risk was identified, assessed, and deemed unacceptable without additional safeguards. That is the correct decision. It is also a decision that should have been anticipated before the naming season was announced.

The Accountability Layer

Here is the question the summary does not answer directly: why was the ReverseRegistrar's proxy architecture not audited for upgrade safety before May 2026?

A contract naming season sounds like a documentation project. It is actually an upgrade project. Every renamed contract requires a new implementation deployed and a proxy pointed at it. If the proxy architecture was not designed with renaming in mind, the naming season was always going to hit a wall.

The summary calls it a "technical hurdle." The contract is owned by a multisig that cannot execute the upgrade without a workaround. The workaround exists in theory but has not been executed in practice. The ENS team is waiting for additional review before proceeding.

That caution is commendable. The lack of upfront architecture review is not.

Governance Lessons

The ENS contract naming season teaches three lessons that apply beyond ENS:

1. Documentation changes are deployment changes. Renaming a contract requires the same rigor as changing its logic. Governance proposals should treat them as upgrades, not housekeeping.

2. Proxy architecture must be designed for evolution. If a contract is meant to be upgraded, the upgrade path should be tested before the contract is deployed. Waiting until a naming season to discover the path is blocked is expensive in time and credibility.

3. Accountability summaries are a governance tool. Publishing a candid summary of what worked and what did not — with technical explanations — builds trust faster than silence. Other DAOs should adopt the practice.

Strategic Implications and Future Outlook

The ReverseRegistrar will eventually be renamed. The question is when and how. The ENS team has committed to resolving the proxy upgrade blocker, but no timeline is provided. That is a governance gap. A public commitment with a target date would demonstrate that the naming season is a priority, not an afterthought.

For developers building on ENS, the lesson is simpler: verify the contract names you are calling. The old names still exist in deployed bytecode, in tutorials, in Stack Overflow answers. A renamed contract is only renamed if the caller knows the new name.

TL;DR

• What: ENS renamed two of three targeted contracts (ETHRegistrarController → NameRegistrar, ENSRegistry → ENSRegistryImpl) during its 2026 naming season
• Why: To improve code readability and developer experience
• Impact: The ReverseRegistrar remains unrenamed due to a proxy upgrade safety risk that was discovered mid-season
• Watch: Whether ENS resolves the ReverseRegistrar proxy blocker with a public timeline; whether other DAOs adopt post-mortem accountability summaries

Sources

• ENS Governance Forum — Contract Naming Season Accountability Summary
• ENS DAO Governance Forum — Ecosystem Discussion

Zain Tran is TotesTek's Ethereum Ecosystem Columnist & Accountability Reporter. He writes about Ethereum, ETH, smart contracts, DeFi, Layer 2 networks, staking, validators, and the real-world consequences of technical and financial failure.