Your Ethereum wallet is about to change forever
And you won't need a new wallet address
If you’ve used Ethereum, you have an EOA, an externally owned account. It’s the address MetaMask gave you. It’s controlled by a single private key, secured by a seed phrase.
This account model has been unchanged since Ethereum launched. And it’s about to be replaced. Not by asking you to migrate to something new, but by upgrading what your existing address can do.
EIP-8141 introduces frame transactions. It’s the most significant change to how Ethereum transactions work since EIP-1559. And unlike most protocol upgrades, this one is going to be visible in how you actually use your wallet.
What's wrong with your wallet today
Your EOA does exactly one thing: it holds a private key and signs transactions. The entire security model of your onchain life (your ETH, your tokens, your NFTs, your DeFi positions) comes down to that single key.
And it’s completely static.
No spending limit that caps how much can leave your wallet per day
Require a second device to approve transfers above a certain amount
No recovery
You can’t use your phone’s fingerprint sensor or Face ID to sign transactions
Need gas to send transactions.
Every other system you use (your bank, your email, your phone) has layers of security. Your Ethereum wallet has one layer: the key.
Smart accounts tried to solve this
The industry recognized this years ago. The answer was account abstraction, which replaces your EOA with a smart contract that can define its own rules.
ERC-4337 made this possible. Smart contract wallets can do everything your EOA can’t: custom signing methods, recovery, spending limits, gas sponsorship. Products like Safe, Coinbase Smart Wallet, and others are built on this.
But here’s what they don’t tell you: using a smart account today requires an entire parallel infrastructure running behind the scenes.
Your transaction goes through bundlers, an EntryPoint contract, and paymasters before it reaches the chain.
The biggest issue is that mainstream wallets never adopted smart accounts as first-class citizens, so most users still use EOAs.
What Frame Transactions Actually Do
EIP-8141 throws out the middleware introduce by smart accounts and builds the functionality directly into Ethereum.
A frame transaction is a new transaction type that contains a list of frames, steps that execute in sequence. Each frame has a role:
VERIFY checks who you are. It verifies your signature and decides whether the transaction is allowed to proceed. In my opinion, this is the most powerful part of frame transactions - you can use any signature scheme to sign transactions (e.g. Passkeys, post-quantum, etc.)
SENDER executes what you actually wanted to do. Swap tokens, send ETH, interact with a protocol.
DEFAULT handles housekeeping like deploying contracts or cleanup logic.
You can chain these together. One transaction that verifies your identity, checks a spending policy, and executes three operations atomically. All processed natively by Ethereum.
What This Looks Like in Practice
Same Wallet Address. Different Infrastructure.
EIP-8141 does not require you to create a new wallet address. It does not require you to deploy a smart contract. Your existing EOA, the address you’ve been using for years, works natively with frame transactions.
The protocol defines default code, built-in behavior for addresses that have no smart contract deployed. When your EOA receives a VERIFY frame, the default code automatically:
Verifies your ECDSA signature (the same signing method you’ve always used), or
Verifies a P256 signature (the standard used by passkeys, Touch ID, Face ID, YubiKeys)
Your EOA can natively use a passkey to sign transactions. No smart contract deployment. No migration. No new address. The protocol handles it.
This means your MetaMask address can:
Sign with a passkey stored on your phone or laptop
Batch multiple operations into one atomic transaction
Have gas paid by someone else
You keep your address. You keep your history. You keep your token approvals. You gain programmability.
This took many years in the making
Ethereum has been trying to solve the wallet problem for years. EIP-3074, EIP-7702 added code delegation for EOAs. ERC-4337 built an entire account abstraction system outside the protocol. Each was a step in the right direction, each with trade-offs.
EIP-8141 is the convergence. It takes the lessons from all of these and builds them into the transaction format itself:
From ERC-4337: programmable validation, gas sponsorship, custom signature schemes
From EIP-7702: EOA compatibility, no forced migration
From EIP-3074: the idea that authorization should be a protocol primitive
New: frame-based execution, atomic batching, pre-execution introspection
What This Means for You
If you hold crypto in an EOA today, frame transactions mean:
Your wallet gets smarter without you doing anything. Once the upgrade goes live, your address supports passkeys, batching, and gas sponsorship natively.
You can add security rules without migrating. Deploy a policy contract, fund it, configure your rules. Your address stays the same.
Gas fees can be sponsored by dApps, protocols, or services can sponsor your gas through a VERIFY frame. No special wallet required.
Beyond one key: where Functor keystore layer comes in
Frame transactions fix validation. Your EOA can use passkeys, enforce policies, batch operations. But here’s what they don’t fix: your EOA still has one signing key.
The default code verifies that key, and it works the same on every chain. No fragmentation problem. But you’re still one key away from losing everything. And if you want multiple keys with different permissions, a backup key, or a way to rotate credentials without moving assets, you need somewhere to store and manage those keys.
That’s the keystore layer. It’s a registry on Ethereum L1 that stores your public keys. Passkeys, hardware wallet keys, backup keys, session keys. It answers one question: can this key sign for this user?
This is what Vitalik described as asset-signer separation. Your tokens and positions move across chains constantly. Your identity stays in one place. The keystore is that one place.
How frame transactions talk to the keystore
Before frame transactions, the keystore worked through ERC-4337 and ERC-7579. A validator module would read your keys from the keystore when processing a UserOperation. Your key sat in the registry, but reaching it meant going through bundlers, the EntryPoint, and validator modules.
With frame transactions, the VERIFY frame reads the keystore and verifies your signature directly. No bundler, no EntryPoint, no validator module in between.
The keystore itself doesn’t change. Same registry, same key data, same operations. What disappears is the infrastructure that used to sit between the keystore and the user.
Same wallet address, new functionality
With frame transactions and Functor Keystore, any wallet can have a new set of capabilities:
Agent wallets
You want an AI agent to manage DeFi positions without your wallet key.
Register a session key in the keystore. Temporary, scoped, with an expiry. Functor policy engine recognizes the key type and applies tight constraints. The agent operates in a sandbox.
Passkey, post-quantum signature scheme
Register a passkey in the keystore or a post-quantum signature. The VERIFY frame reads the key, verifies the signature against the appropriate scheme, and approves the transaction.
Native account recovery
Your phone is lost. The passkey in its secure enclave is gone.
Without a keystore, you lost access to your wallet.
With the keystore: use your second key to continue signing transactions with the same wallet.
Programmable wallets:
You can configure and setup different kind of permission to each of your signers:
Phone passkey for daily use, up to 1 ETH per day, allowlisted contracts only
Hardware wallet for larger amounts, up to 50 ETH per day, any contract
Session key for a DeFi bot, 0.1 ETH max per transaction, 24-hour expiry, restricted to Aave and Uniswap
Institutional signers
Three authorized signers for a company treasury: CFO, CTO, ops lead. All keys in the keystore. Policy: transactions over $100k require two signatures, only approved counterparties.
Ethereum is upgrading how wallets work at the protocol level. Frame transactions give every wallet programmable validation. The keystore enables programmability, accessibility and portability to wallet signers . For years, this industry has talked about fixing UX and security without having the right infrastructure to do it. That infrastructure is finally here. We're excited to be building part of it.