How .base.eth Names Work: A Comprehensive Guide

This article explores ".base.eth" names, powered by the Ethereum Name Service (ENS) protocol, which enable users to register human-readable blockchain identifiers (e.g., name.base.eth). We’ll break down their functionality, compare them with .eth names, and address decentralization, ownership, and security concerns.

Table of Contents

• What Are .base.eth Names?

• How .base.eth Names Work

  • How .eth Names Work
  • Resolution of .base.eth Names
  • ENSIP-10: Wildcard Resolution
  • EIP-3668: Offchain Resolvers
  • Structure on Base
  • Architecture Summary

• Potential Risks

  • Ownership of base.eth
  • Offchain Gateway Control
  • Mitigations
• How Do .base.eth Names Differ from .eth Names?
• Similar Cases: Uniswap’s uni.eth Names
• Are .base.eth Names Beneficial for the Ecosystem?
• Summary
• FAQs

What Are .base.eth Names?

".base.eth" names serve as human-readable blockchain addresses (e.g., jesse.base.eth), simplifying transactions by replacing complex wallet addresses. They were launched via a Dutch auction to prevent bots from squatting high-value names.

👉 Learn more about blockchain naming systems

How .base.eth Names Work

How .eth Names Work

• ENS Registry: Stores ownership (owner), resolution (resolver), and TTL data for each .eth name (e.g., ens.eth).
• Resolver: Holds records like wallet addresses or content hashes.
• Ownership: Owners can transfer names or create subdomains (e.g., nick.ens.eth).

Resolution of .base.eth Names

Unlike .eth names, .base.eth names don’t exist in the ENS Registry. Instead:

1. Queries check Ethereum for name.base.eth → Not found → Query base.eth’s resolver.
2. The resolver directs to an off-chain URL (via EIP-3668), which fetches data from Base’s L2 registry.

ENSIP-10: Wildcard Resolution

Allows subname resolution via parent domains (e.g., jesse.base.eth is resolved through base.eth’s records).

EIP-3668: Offchain Resolvers

Enables resolvers to pull data from external URLs, reducing on-chain storage needs.

Structure on Base

• Names are recorded in Base’s registry (L2) with resolvers storing address/content data.
• Ethereum’s off-chain gateway fetches this data via Base’s backend.

Architecture Summary

1. Users register name.base.eth on Base’s registry.
2. Resolvers set records (e.g., wallet addresses).
3. Clients query Ethereum → Redirect to Base’s off-chain gateway → Fetch L2 resolver data.

Potential Risks

Ownership of base.eth

• Controlled by a 3/11 Gnosis Safe multisig. If compromised, attackers could hijack resolutions.
• Existing .base.eth subnames on Ethereum bypass Base’s resolution.

Offchain Gateway Control

• The gateway URL can be altered to point to a malicious database.
• Risks include censorship, downtime, or fraudulent resolutions.

Mitigations

No foolproof solutions exist. Users must trust Base’s security measures.

How Do .base.eth Names Differ from .eth Names?

| Feature | .eth Names | .base.eth Names |
|------------------|----------------------------|----------------------------|
| Ownership | Immutable (via EthRegistrar)| Controlled by Base team |
| Resolution | Fully on-chain | Hybrid (Ethereum + Base L2)|
| Decentralization | High | Moderate (gateway reliance)|

Similar Cases: Uniswap’s uni.eth Names

Uniswap’s uni.eth names are free but stored off-chain, relying on a centralized gateway (Uniswap’s URL).

Are .base.eth Names Beneficial for the Ecosystem?

Pros:

• Improved UX for onboarding.
• Lower fees via L2 resolution.

Cons:

• Reduced decentralization.
• Trust dependency on Base’s governance.

👉 Explore Ethereum Name Service alternatives

Summary

• Ownership: Users own .base.eth names on Base’s L2.
• Control: Base team manages resolution via Ethereum’s gateway.
• Trust: Security depends on Base’s multisig and infrastructure.

FAQs

1. Can someone steal my .base.eth name?

No, but resolution can be hijacked if the gateway is compromised.

2. Why use .base.eth over .eth?

Lower gas fees and simpler UX, but with trade-offs in decentralization.

3. How does Base ensure gateway reliability?

Through audits and multisig controls, though risks remain.

4. Are .base.eth names stored on Ethereum?

No, they reside on Base’s L2, with Ethereum handling resolution queries.

5. Can I transfer my .base.eth name?

Yes, within Base’s registry, but resolution depends on Base’s gateway.

This guide provides a neutral analysis of .base.eth names, balancing their innovations with inherent risks. For further reading, refer to ENS documentation.