If you already own an ENS name on Ethereum mainnet, something like yourname.eth, you might wonder whether that name works on Base, or whether you need a separate yourname.base.eth Basename. The short answer is that both can exist at once and they solve a similar problem in different ways. This guide walks through what each one actually is, how they are managed, and where people tend to get confused.
For the basics of what a Basename is and what it costs to register one, see our guide to what a Basename is.
Two separate naming systems
An ENS name ending in plain .eth, such as yourname.eth, is registered and managed through the ENS App on Ethereum mainnet. It is the original, chain agnostic naming system for crypto addresses, and it has been around since 2017.
A Basename, ending in .base.eth, is a name issued by Base itself. According to ENS's own support documentation, a .base.eth name is not managed inside the ENS App the way a plain .eth name is. It is registered and managed through Base's own interface at base.org, even though it uses the same underlying ENS naming standard. Owning a Basename does not reserve the matching plain .eth name for you, and owning the plain .eth name does not automatically give you the matching Basename either. They are tracked as separate registrations, even when the text before .eth is identical.
Your existing .eth name can already point to a Base address
Here is the part that surprises a lot of people: you do not need a Basename just to receive funds on Base under a readable name. ENS names support records for multiple chains, called coin types, and Ethereum mainnet is only one of them. A plain .eth name can hold a separate address record specifically for Base, set through the ENS App, so that an app aware of multichain ENS records resolves your name to the correct Base address rather than assuming it is the same as your mainnet address.
In practice this means someone with yourname.eth can add a Base specific address under that same name, without ever touching base.org or paying for a separate Basename. Whether that works in a given app depends on whether the app looks up the Base specific record, so support varies.
How resolving a Basename from mainnet actually works
Basenames live on Base, not on Ethereum mainnet, which raises a reasonable question: how does a mainnet wallet or app look one up at all? The mechanism is called CCIP Read, defined in a standard known as ENSIP 10. When a mainnet client tries to resolve a .base.eth name, instead of finding an onchain record directly, it receives a structured response telling it to fetch the data from another source, in this case Base, and verify it. Base's resolution infrastructure is built around this same lookup path, so a .base.eth name resolves consistently whether the request originates from Base itself or from an app on another network that understands CCIP Read.
The practical takeaway is that a Basename is not invisible outside of Base, but support for it depends on an app implementing this lookup correctly. An app that has not built that support will simply fail to resolve the name and fall back to showing nothing, not send funds to the wrong place, since a failed resolution does not produce an address.
A newer idea: naming the chain explicitly
Because more and more networks now have their own names built on the ENS standard, the ENS team has also been working on a way to say, in the name itself, which chain you mean. The proposed format looks like yourname.eth@base, where the part after the @ sign states the chain explicitly rather than leaving it to the app to guess or default to mainnet. This is still an evolving proposal, and broader rollout and support across wallets was not settled at the time of writing, so treat it as a direction the ecosystem is heading in rather than something you can rely on everywhere today.
Which one should you actually use
For most people the answer is simple: you probably do not need both.
- If you already own a plain
.ethname and mainly want a readable address for Base, add a Base specific address record to that existing name through the ENS App rather than buying a second name. - If you do not have an ENS name at all and only care about Base, registering a Basename directly through Base is the more direct path, and it keeps you inside Base's own ecosystem of apps that are built to recognize it first.
- If you are active across many chains and want one identity to carry everywhere, a plain
.ethname with multiple coin type records set is the more flexible long term choice, since it is not tied to a single network the way a Basename is.
The safety point that matters more than the naming details
Whichever system you use, the same caution applies that we cover in our guide to a Basename's honest cautions: a readable name is a convenience, not a security feature. Scammers can register a name that looks almost identical to one you trust, whether that is a lookalike .eth name or a lookalike .base.eth name, so a readable name reduces typos but does not replace checking that you have the right name in the first place. Your funds always live at the underlying address, never at the name, and losing a name through non renewal does not put funds already at that address at risk.
The short version
A plain .eth name is registered on Ethereum mainnet through the ENS App and can hold a Base specific address record alongside its mainnet one. A Basename is issued separately through Base and resolves back to mainnet apps through a lookup mechanism called CCIP Read. You can hold both under the same text if you want, but most people only need one, and which one depends on whether Base is the only network you care about or just one of several.
Sources: ENS support on managing a .base.eth name, ENS case study on Base, ENS on.eth announcement on chain specific names.