Skip to main content
LearnGlossaryCoinbase Smart Wallet
GLOSSARY

What is Coinbase Smart Wallet.

DEFINITION

Coinbase Smart Wallet is a self-custodial smart-contract wallet built by Coinbase and deployed first-class on Base. It replaces the seed-phrase model with WebAuthn passkeys, supports gasless transactions through paymasters, and exposes account-level primitives (session keys, spending limits, multi-sig logic) as part of the wallet contract. The user signs in with a passkey; everything else flows through the smart contract.

WHY IT MATTERS

The first wallet a non-crypto user can actually use.

Wallet UX is the chokepoint for consumer adoption of every on-chain payment story, agent payments included. Seed phrases, gas tokens, and chain-switching are all unforgivable for ordinary users. Smart Wallet removes all three: passkey auth feels like Touch ID, gas is sponsored, the chain is Base by default. The same wallet that a developer would use directly is now usable by a user who has never heard the word 'blockchain'.

For agent payments specifically, the account-abstraction features matter just as much as the UX. Session keys let an agent operate within a scoped envelope without holding the user's full keys. Spending limits cap exposure at the wallet level. Recovery via passkeys means the user can lose a device without losing the wallet. These are the primitives that a consumer-grade agent product needs, and they exist at the wallet layer rather than having to be reinvented at the application layer.

HOW IT WORKS

Passkey at the front, smart contract at the back.

  1. Passkey enrollment. The first time the user clicks 'Sign in', their device prompts to create a passkey. The passkey lives in the device's secure enclave; the corresponding public key is what the wallet contract will recognize.
  2. Smart-contract provisioning. On first use, the wallet contract is deployed (or lazily deployed at first transaction) on Base. The contract is bound to the user's passkey public key, plus any recovery key the user has added.
  3. Transactions. When the user signs a transaction, the passkey signs a UserOperation that gets sent to a bundler. The wallet contract verifies the signature and executes the action. A paymaster covers the gas.
  4. Account-level features. Spending limits, session keys, and multi-sig logic are configurable on the contract. The user (or app) adds a session key for a particular dapp with a particular spending cap; the contract enforces that cap.
  5. Recovery and rotation. Devices come and go - the user can add new passkeys from new devices, remove old ones, and (optionally) configure social or email-based recovery. The wallet survives device loss because the recovery path is at the contract level.

None of these are visible to the user during normal operation. They just sign in, transact, and lose a device without panic. The complexity that used to live on the user has moved into the contract and the supporting infrastructure.

EXAMPLES

Three usage patterns in production.

EXAMPLE 1

Passkey sign-up in 15 seconds

A user clicks 'Sign in with Coinbase Smart Wallet' on an app. The device's passkey prompt asks for biometric confirmation. No seed phrase, no email, no app install. The wallet is provisioned as a smart contract on Base on first transaction. The user is paying within seconds without ever learning what a private key is.

EXAMPLE 2

Gasless USDC payments out of the box

A user with $20 of USDC in their Smart Wallet pays an MCP server $0.05. They do not hold any ETH for gas. The wallet's paymaster (typically Coinbase, sometimes the dapp itself) covers the gas in ETH and either eats the cost or deducts a small USDC equivalent. The user only sees the $0.05 charge and the call result.

EXAMPLE 3

An agent-with-passkey delegation pattern

A consumer-facing agent product (an AI shopping assistant) uses Coinbase Smart Wallet as its identity primitive. Each user has their own Smart Wallet. The agent is granted scoped permission to spend up to a daily limit from the user's wallet via a session key. The user retains custody; the agent operates within an explicit envelope. This is the most common consumer agent shape in 2026.

FAQ

Three common questions.

Is Coinbase Smart Wallet custodial?

No. It is a self-custodial smart-contract wallet. The keys are passkey-derived and held on the user's device(s) - Coinbase does not hold them and cannot recover or sign transactions on the user's behalf. This is the important difference from a Coinbase exchange account, which is custodial. The Smart Wallet brand is consistent (same Coinbase), but the trust model is different: with Smart Wallet, only the user can move funds; Coinbase only operates the supporting infrastructure (relayers, paymasters, indexers).

What is the practical difference between a Smart Wallet and a traditional EOA wallet like MetaMask?

Three big ones. First, account abstraction: the Smart Wallet is itself a smart contract, so it can express arbitrary policies (spending limits, session keys, multi-sig logic) at the wallet level. A traditional externally-owned account cannot. Second, passkey auth: Smart Wallet uses WebAuthn passkeys instead of seed phrases, so the recovery story is the user's device biometrics, not a 12-word backup. Third, gas sponsorship: Smart Wallets natively support paymasters, so users do not need to hold the chain's native token to transact. For consumer and agent UX, all three of these matter.

Why does Coinbase Smart Wallet show up in agent-payment discussions?

Because the wallet is well-positioned as an identity primitive for consumer-facing agents. Two properties matter. One, the passkey UX means a non-crypto user can have a real on-chain wallet without learning anything new - that is the only viable consumer onboarding shape. Two, session keys + spending limits let a consumer give an agent scoped permission to spend without giving it custody. So Coinbase Smart Wallet is often the user's wallet and the spend-policy primitive in the same object, with the agent delegated against it.
Last reviewed: 2026-05-15. Published under CC BY 4.0.

Wallet-grade agent payments.

Passkey UX for the user, session-key controls for the agent. Free to start.