Coinbase launches a wallet built around passkeys

Coinbase introduced a wallet that starts with a passkey

Coinbase launched its smart wallet on 5 June 2024 with passkey onboarding, avoiding an initial extension installation or recovery-phrase setup. A passkey can be unlocked through a fingerprint or supported security key. Eight networks were covered. Users could fund actions from wallet or Coinbase balances. Developers could optionally sponsor network charges through a paymaster, a service that pays transaction-processing costs. The announcement did not make every action free, and existing-wallet migration remained forthcoming.

Easier sign-in still needs a recovery plan

Coinbase's recovery guide distinguishes cloud-synchronized passkeys from credentials tied to an individual device. It describes an optional recovery phrase that must be generated while the original passkey remains available. That phrase creates an additional onchain signer: an authorization method recorded in the wallet's smart contract.

The guide says this recovery method can be used to establish a new passkey. Creating or changing signers requires a network fee on each chain in use. Coinbase says it cannot access the recovery phrase and warns that sharing it gives someone else control. These are current recovery details checked in September 2026, added to explain a launch whose most visible promise was simpler onboarding.

A familiar gesture can authorize a different kind of account

A fingerprint prompt can make a wallet feel like another familiar app. The important question is what that gesture authorizes. Signing into an ordinary website and authorizing movement from a wallet can look similar on a phone, even though the consequences are different. A clearer interface helps a person recognize whether they are opening an account view, granting a permission or approving a transaction.

This distinction matters particularly for a first-time user. Removing an installation step can make a first purchase easier, but it does not tell the user whether a request is sensible. The useful improvement is fewer mechanical obstacles between an informed decision and its execution. It should not be interpreted as evidence that every request presented through that convenient path is trustworthy.

A hypothetical lost-phone scenario

Imagine a user named Maya creates a wallet on a phone and later replaces that phone. In the first version of the example, she knows which account synchronizes her passkey and confirms that she can access that account on the replacement device. Her task is to restore her usual access method. The wallet's asset balance does not need to be treated as though it lived physically inside the discarded phone.

In a second version, Maya's credential was tied to the old device. Before losing it, she prepared a separate recovery route and kept its secret safely. The relevant question becomes whether that route can authorize a replacement credential. This is a different workflow from asking a customer-support agent to disclose an old password.

In a third version, no working credential and no prepared recovery route remain. The attractive simplicity of the original sign-up screen does not supply the missing authorization. This example deliberately avoids claiming that one recovery procedure works for every wallet. Its purpose is to show why the access method should be understood while it still works, rather than first investigated after a device disappears.

A hypothetical sponsored purchase

Suppose a small digital item costs $8 and the network charge for the transaction would be $0.20. If a participating application sponsors that charge, the buyer's immediate cost in this invented example is $8 instead of $8.20. The application has absorbed a cost; the network has not become costless.

Now assume the same buyer returns later and the application no longer sponsors the charge. A clear confirmation should make the new total visible before approval. It would be misleading to judge that later quote solely by the word “gasless” in a historical launch headline. The point of the example is to separate the item's price from the party paying to process the transaction.

The June release brought a more familiar entry point to self-custody. Its lasting significance lies in that simpler first interaction, accompanied by a need for equally understandable permissions, funding and recovery. Those details determine whether easier onboarding continues to feel manageable after the first successful transaction.