Base Names

Basenames are human-readable ENS names issued for the Base ecosystem, such as alice.base.eth. They can make a wallet address easier to recognize and use in supported apps. A Basename is not a separate “.base” top-level domain: it is a project-issued subname under base.eth, with registration and profile management handled through Base’s own service.

Key Facts

• Product name: Basenames, sometimes informally called Base names.
• Format: a name such as alice.base.eth, not alice.base.
• Relationship to ENS: Basenames are project-issued ENS subnames. Base manages their registration and records through its own interface; they are not registered or renewed in the ENS app like a name someone owns directly under .eth.
• Network: the name is designed for identity and address resolution in Base’s ecosystem. A Basename becoming a primary name on Base does not automatically make it a primary name on every network.
• Older BNS: Base’s launch announcement says an earlier independent Base Name Service began winding down as Basenames launched, so “BNS” and “Basenames” should not be treated as interchangeable products.

How Basenames Work

ENS organizes names hierarchically. A project that controls a parent name can issue subnames beneath it and set the rules for registration, renewal, and editable records. Base uses the parent base.eth to issue names ending in .base.eth. ENS documentation explains that these project subnames are real ENS names, while the project—not ENS Support—runs the registration system and handles most management requests.

The Base interface lets users claim or manage their Basename and related profile information. Name records can connect a readable name with a wallet address or profile data where an application supports those records. Some resolution flows use ENS standards to retrieve records stored beyond Ethereum Mainnet; the underlying network and resolver behavior can matter to an app integrating the name.

Basenames Compared With .eth Names

A person who owns a second-level ENS name such as alice.eth manages it through the ENS system and can create subnames beneath it. A Basename such as alice.base.eth is issued under Base’s project-controlled parent. ENS Support says registration, renewal, and record edits for a project subname happen through that project’s site. It also says a Basename is set as the holder’s primary name on Base when registered, while making it the primary name on Ethereum is a separate action.

This means Basenames and personally registered .eth names can serve related but different roles. One does not automatically replace the other. App support, name records, fees, renewal rules, and the networks on which a name appears depend on the project’s current implementation and the app performing resolution.

Limits and Safety

A readable name reduces the chance of mistyping a long address, but users should still verify the resolved address before sending funds. A name can resolve differently across apps if records or resolver support differ. Project-issued names also depend on the parent project’s registration and management rules, so check the current terms, price, renewal requirements, and support channel before registering.

“Onchain identity” does not prove that a profile or its claims are accurate. Do not rely on a name alone to authenticate a person, and do not assume a Basename grants control of a social account, website, or content. The Base blog has also said that the earlier independent Base Name Service (BNS) would wind down as Basenames launched; users should check which service issued any older BNS name and what migration or discount rules still apply.

Related Terms

• Ethereum Name Service (ENS)
• Base Network
• On-Chain Identity

See Also

• Are Layer 2 Networks Actually Decentralized?
• Why Calling It a ‘Wallet’ May Have Been Crypto’s Biggest Mistake
• How Crypto Invented Its Own Language
• Swap crypto with ChangeNOW

Sources

• Base: Build Your Onchain Identity with Basenames — Introduces Basenames, describes their ENS basis, and explains the transition from the earlier independent Base Name Service.
• ENS Support: What Are Project Subnames? — Current guidance on project-issued names such as name.base.eth, where they are managed, and how Base primary names work.
• ENS Docs: Offchain / L2 Resolvers — Explains how ENS resolution can retrieve name records stored on a Layer 2 such as Base.

Social Media Sentiment

A small r/BASE discussion in September 2024 asked whether someone who already owned an ENS .eth name had a reason to get a “.base” name too. The question reflects uncertainty about how Base names relate to ENS; the actual Basename format is .base.eth, and its project-issued registration and Base-specific primary-name behavior differ from a directly owned .eth name. This one short thread is historical and is not a measure of current user opinion.

Reddit discussion: “Base Name Service vs Ethereum Name Service”

Last updated: 2026-10