Skip to main content

Intent-Based Wallets: The Endgame of Account Abstraction

· 12 min read
Dora Noda
Dora Noda
Software Engineer

For fifteen years, using crypto has meant one deeply strange ritual: opening a wallet, scrutinizing a hex-encoded transaction, manually funding an account with the right gas token, and signing with a key you are personally responsible for never losing. By 2026, that ritual is on the way out — and the wallets leading the charge are not asking users to sign transactions at all. They are asking users what outcome they want.

That shift, from transaction-based wallets to intent-based wallets, is the long-promised endgame of account abstraction. It is being assembled right now out of three apparently unrelated pieces: ERC-4337 smart accounts, EIP-7702 EOA programmability, and a $10B+ wallet-as-a-service market in which Coinbase, Privy (now part of Stripe), Dynamic (acquired by Fireblocks), Safe, and Biconomy are racing to build the default consumer surface for Web3. Put them together and you get a wallet that finally behaves like Apple Pay: you express a desire, someone else figures out the plumbing, and the blockchain disappears.

The Final Form: Users Specify Outcomes, Not Transactions​

The mental model for a 2020-era crypto wallet was a transaction factory. You selected a chain, chose a gas token, set slippage, reviewed calldata, and signed. Every UX paper cut — wrong network, insufficient ETH for gas, a signature for an approval plus a second signature for the swap — came from the fact that the user was the one operating the low-level machine.

Intent-based architectures invert that model. As Anoma's research on intent-centric topologies frames it, an intent is a partial state change expressing a preference, signed by the user, that a solver network competes to fulfill. CoW Protocol has run this playbook for years as a batch-auction DEX where users sign "sell X for at least Y" and solvers do the routing. Flashbots' SUAVE takes the same idea down into block building. Cross-chain intent protocols are actively replacing bridges, turning "bridge from Arbitrum to Base" into "have these tokens on Base in under a minute."

The critical point for wallets is this: once an account is programmable enough to accept conditional, multi-step instructions and hand them off to a solver, the UI no longer has to look like Etherscan. It can look like a chat box, a Shopify checkout, or a one-tap "Buy PENGU" button inside a consumer app. The wallet becomes the place where intents get authenticated; something else does the executing.

ERC-4337 Built the Execution Pipes​

The first enabling piece is ERC-4337, which went live on Ethereum mainnet on March 1, 2023, and quietly became the execution substrate for most of today's smart wallets. Instead of sending a transaction from an externally owned account, a user signs a UserOperation — a richer object that specifies validation rules, an optional paymaster, and the calls to execute. Bundlers package these into real transactions and send them to a canonical EntryPoint contract. Alchemy's overview of account abstraction walks through this pipeline in detail.

Three capabilities fall out of this design, and together they make intent-based UX actually shippable:

  • Gas abstraction via paymasters. A paymaster contract can agree to pay gas on the user's behalf, sponsored by the application or swapped from any ERC-20 the user holds. The experience is a user with zero ETH transacting immediately after account creation — the pattern that Nadcab's 2026 gas abstraction guide projects will become an invisible default by 2027.
  • Session keys. Rather than reauthorizing every action, a user can grant a scoped, time-limited key — "this dApp may spend up to 100 USDC on trades on Base for the next hour." This is the primitive that makes on-chain games, AI agents, and high-frequency DeFi usable without a signature popup every 30 seconds.
  • Modular validation. Because validation is expressed in contract code, not hard-coded by the protocol, wallets can swap in passkeys, multisig logic, social recovery, or fraud checks without changing the underlying account.

ERC-4337 by itself, however, had a structural problem: smart accounts are separate contracts from the ordinary EOAs most users already had. Migrating 200M+ existing addresses into brand-new accounts was never going to happen cleanly. That is the gap EIP-7702 closed.

EIP-7702 Upgraded Everyone's Wallet Overnight​

Ethereum's Pectra upgrade launched on May 7, 2025, and introduced EIP-7702 — a deceptively simple change that lets an ordinary EOA temporarily delegate its code to a smart contract. The private key still controls the account, but while the delegation is active, the EOA behaves like a smart wallet: it can batch calls, use paymasters, whitelist session keys, and plug into ERC-4337 infrastructure. Turnkey's deep dive on the 4337-to-7702 journey captures the key insight: the two standards are complementary, not competing.

The effect on adoption is dramatic. MetaMask, Ledger, Ambire, and Trust Wallet have shipped EIP-7702 support, and Ledger has rolled it out across Flex, Stax, Nano Gen5, Nano X, and Nano S Plus hardware. BuildBear's ERC-4337 vs EIP-7702 comparison notes that most major wallet providers are expected to follow through 2025 and into 2026, which is exactly what the on-chain data is now showing.

In practical terms, 7702 means users do not have to know they are getting a smart wallet. Their existing address keeps working; it just starts doing more. That is the quiet precondition for a mass-market intent-based UX: you cannot ask hundreds of millions of users to migrate, so you upgrade the account they already have.

The $10B+ Wallet-as-a-Service Battle​

If ERC-4337 and EIP-7702 are the protocol layer, the battle for the product layer is being fought in wallet-as-a-service. This is where consumer-grade onboarding, passkeys, embedded UIs, and intent routing get packaged into an SDK that any app can drop in.

The leaders each come from a different angle:

  • Coinbase Smart Wallet is the reference consumer implementation. Coinbase's announcement and Base's rollout plan describe a wallet with passkey-based authentication, gasless transactions by default, and cross-chain deployment — 8 networks at launch and the same contract address across 248 chains via the Safe Singleton Factory. It is effectively trying to become the "Sign in with Apple" of Web3.
  • Privy, acquired by Stripe in June 2025, is now fused with Bridge to unify crypto and fiat payments, pushing embedded wallets deep into mainstream fintech flows. Openfort's Privy alternatives guide tracks how this acquisition reshaped the consumer-crypto landscape.
  • Dynamic, acquired by Fireblocks, is focusing on developer experience and multi-chain adapters, positioning embedded wallets as an enterprise building block.
  • Safe and Biconomy are competing on the modular-account side, particularly around ERC-7579 — a minimal standard for modular smart accounts co-developed by Rhinestone, Biconomy, ZeroDev, and OKX that lets validators, executors, hooks, and fallback handlers plug into any compliant account.
  • Aggregators such as WAGMI, Web3Modal, RainbowKit, and Reown have already integrated smart wallets at the connector layer, meaning most new dApps are intent-capable by default.

The strategic prize is the identity and intent layer for Web3. Whoever owns the wallet owns the funnel for every transaction, payment, and agent action a user initiates. Openfort's top 10 embedded wallets report and the wave of Stripe/Fireblocks M&A make it clear that incumbents now treat this as strategically important — and finite.

The Four Primitives That Make the Intent Wallet Real​

Strip away the marketing and there are four concrete primitives behind "wallets that hide the blockchain."

  1. Native passkeys (EIP-7212). A precompile for secp256r1 signature verification lets wallets authenticate with the same WebAuthn passkeys iPhones, Android devices, and YubiKeys already use. That removes seed phrases as the default recovery model and replaces them with device-secure, phishing-resistant credentials users already trust.
  2. Session keys (commonly structured as ERC-7579 validator modules). Scoped, revocable permissions underwrite one-tap gameplay, recurring payments, and agent autonomy without turning the signature popup into spam.
  3. Gas abstraction (ERC-4337 paymasters). Apps sponsor gas, users pay fees in the stablecoin they already hold, and "I need to buy ETH first" stops being a gating step.
  4. Batched execution (ERC-7821). A single user action can contain an approve + swap + bridge + stake sequence that either all happens or none of it does, eliminating the half-completed multi-step disasters that define crypto UX today.

Combine these four with a solver network and you have the ingredients for an actual intent-based wallet: the user says "swap $500 of USDC for ETH on whatever chain is cheapest," and the wallet handles bridging, gas, approval, and execution under one authorization.

Why This Is Also a Security Story​

Intent architectures are not just a UX upgrade. They are also a security pattern, which matters more than usual given the $25M Resolv hack reporting from March 2026 that put intent-layer safety on investors' radar.

Two shifts stand out. First, because intents are expressive declarations of desired end states, wallets and solvers can simulate and reason about them before execution — rejecting anything whose outcome would violate a policy, rather than relying on users to spot malicious calldata. Second, smart accounts let wallets layer defense-in-depth: spending limits, address allow-lists, transfer delays on large outflows, and automatic pauses on anomalous activity can all be modules on the account itself, not optional settings buried in a UI.

The flip side is new risk surface. Solver networks can collude, paymasters can front-run, and a mis-scoped session key can drain an account silently. Intent wallets do not eliminate risk; they move it from "did the user read the calldata?" to "did the wallet's modules and solvers behave correctly?" That is a far better question to be auditing in 2026.

What Builders Should Watch in the Next 12 Months​

Three inflection points are worth tracking:

  • EIP-7702 saturation. As more wallets turn on delegation and more dApps start assuming smart-wallet capabilities, the design space for EOA-only UX collapses. Apps that still require users to manually fund gas, approve separately, and sign bridges will feel obsolete.
  • ERC-7579 module ecosystems. Expect a real marketplace of audited validators, session-key modules, recovery policies, and compliance hooks that wallets can compose the way mobile apps compose SDKs. Thirdweb, OpenZeppelin, and Rhinestone are already building toward this.
  • Intent settlement standards. Cross-chain intents are the next battleground, and whoever standardizes settlement (ERC-7683 and its successors) will influence how liquidity and MEV get captured across L2s.

The underlying infrastructure — low-latency RPCs, bundlers, paymasters, indexers — has to keep pace. Every intent that a wallet accepts becomes several chain operations behind the scenes, which means the providers that serve these wallets see traffic scale non-linearly with user counts.

BlockEden.xyz operates high-availability RPC and indexing infrastructure across Ethereum, Base, Arbitrum, Sui, Aptos, and other networks that intent-based wallets settle on. If you are building a smart-wallet SDK, paymaster, solver, or embedded-wallet experience, explore our API marketplace to run on infrastructure designed for the multi-chain, intent-driven future.

Sources​

Share on Twitter