Base App is Coinbase Wallet again. Name the job.

On September 10, 2026, Coinbase renamed Base App back to Coinbase Wallet, about 14 months after it retired that name. It's the clearest naming lesson crypto has had this year, and the lesson is simple: name the product after the job users hire it for, not the infrastructure you'd like them to care about.

I've named, renamed and un-named enough products across crypto, iGaming and fintech to see this one coming. The rename didn't fail because "Base" is a bad word. It failed because a name is a promise about what the product does, and "Base" made the wrong promise.

A product name is a claim about what the product does

When Coinbase turned Coinbase Wallet into Base App in July 2025, CoinDesk described it as an all-in-one app: trading, USDC payments, a social feed built on Farcaster, messaging on XMTP, content creation and mini apps. Coinbase told CoinDesk that "Base is evolving to be more than a chain."

That line gives the whole plan away. The company wanted the network's name to carry a consumer product, and the product to lift the network in return. It's a tempting move for any founder who owns both a protocol and an app. You get one brand, one story and one set of marketing dollars.

But users don't buy stories. They open an app to do something. "Wallet" tells you what the thing does in one word. "Base" tells you who built the plumbing.

"Base" meant two things, and users picked the wrong one

Here's the part every Web3 founder should read twice. According to CoinCodex, the confusion was structural: Base was both Coinbase's Ethereum layer-2 network and the name of the wallet, so people couldn't tell if the app only worked with the Base chain. CoinCodex reports that the rename was prompted by an X user asking whether Base App supports blockchains beyond Base.

It always did. The Block lists 11 networks the wallet now supports, including Bitcoin, Solana, Ethereum and BNB Chain. The product was multichain, and the name said the opposite.

This is the most common naming mistake I see in Web3 product design: a team names the user-facing thing after the layer they're proudest of. Users read the name literally, and a literal reading of "Base App" is "the app for Base." No onboarding screen will talk someone out of what the icon on their home screen already told them.

The name was tied to a strategy, and the strategy moved

The social bet didn't land. In March 2026, on David Senra's podcast, Brian Armstrong said of the social features, as The Block reported: "We tried it as an experiment. It didn't quite work." The Block also notes that the Farcaster-powered feed had already been removed by February 2026.

So by spring, the app was a self-custodial trading product still wearing a name picked for a social super-app. When Coinbase switched back, Ryan Kass, who heads Coinbase Wallet product, told The Block that the old name "better captures the product's role as Coinbase's self-custodial front door to the 'everything exchange.'"

Read that as a naming rule, not a PR line. A name has to survive the next pivot. "Wallet" survives almost any pivot a wallet can make: social, trading, payments, perps. "Base App" was fastened to one strategy and one chain, so it was always going to break when either changed.

Rename when the job changes, not when the roadmap does

Renames are expensive in ways that don't show up on the invoice. Brand design is the cheap part. The expensive part is everything downstream: app store listings, SEO equity, support docs, partner integrations, and the trust you spent years building with people who hold real money in your product.

Before I sign off on a rename for a crypto or fintech client, I ask four questions:

• Has the user's job changed, or only our strategy deck? If people still open the app to hold and move assets, it's still a wallet.
• Does the new name read literally the way we want? Say it to someone outside the company and ask what the product does. Don't explain it first.
• Does it collide with anything we already own? A network, a token or a sister product with the same word will split attention and confuse search.
• Will it survive our next pivot? If the answer depends on one feature working out, it won't.

Base App fails three of the four. That's why a strong brand and design system should start with naming architecture before anyone draws a logo: which names describe infrastructure, which describe products, and which should never appear on a home screen.

Protocol names and product names do different jobs

My working rule, from building branded products for money-adjacent audiences: protocol names can be abstract, but product names can't.

A chain, a token or an SDK can get away with a word that means nothing yet. Developers will learn it. A consumer app that holds someone's savings gets one glance to explain itself. Coinbase can afford to make this mistake in public and pay for the reversal. A seed-stage team that renames its wallet after its own L2 is spending trust it doesn't have yet, and that's the kind of call I'd rather catch while working as a founder-side partner than fix after launch.

Coinbase didn't need a new name. It needed the old one, and it took 14 months to find that out.

Sources

1. CoinDesk – Coinbase Wallet Becomes 'Base App' in Major Rebrand (July 2025)
2. The Block – Coinbase CEO Brian Armstrong says Base App's SocialFi features 'didn't quite work' (March 2026)
3. The Block – Coinbase rebrands Base App back to Coinbase Wallet after just over a year as social experiment falls short (September 2026)
4. CoinCodex – Coinbase Renames Base App Back to Coinbase Wallet Amid Confusion Over Supported Chains (September 2026)