Ethereum advances scaling with EIP-8141, a new transaction type that splits one tx into up to 64 frames

Ethereum is getting a new transaction primitive that could reshape how wallets, dApps, and smart contracts interact with the network. EIP-8141 introduces what’s called a “Frame Transaction,” a single transaction that can be broken into up to 64 programmable sub-units called frames, each capable of performing distinct operations within one atomic execution.

The proposal, co-authored by Vitalik Buterin and several core contributors, was first put forward on January 29, 2026. It has since been moved to “Scheduled” status for inclusion in the 2027 Hegotá hard fork.

What frame transactions actually do

The new transaction type, designated 0x06, lets each frame operate in one of three modes. DEFAULT handles standard transaction deployment. VERIFY runs read-only validation, useful for checking conditions without changing state. SENDER executes in the context of the transaction’s sender, enabling patterns that previously required deploying dedicated smart contract wallets.

Each frame carries an intrinsic cost of 12,000 gas plus 475 gas per frame. For context, a basic Ethereum transfer today costs 21,000 gas, so the overhead per frame is relatively modest considering the functionality it unlocks.

The proposal also introduces several new opcodes. The APPROVE opcode (0xaa) handles authorization logic, while a suite of TXPARAM, FRAME, and SIG opcodes give developers granular control over how frames reference each other, pass parameters, and verify signatures.

Why this matters: native account abstraction without the workarounds

The ecosystem has been building toward account abstraction through proposals like ERC-4337, which created an “alternative mempool” for account-abstracted transactions without changing the protocol itself. EIP-7702 took a different approach, allowing EOAs to temporarily delegate to smart contract code. ERC-4337 adds infrastructure complexity with bundlers and paymasters. EIP-7702 requires persistent delegation setups.

EIP-8141 takes a third path by baking these capabilities directly into the transaction format. A single frame transaction can include a verification step, an approval, and an execution, all without requiring the user to deploy a smart contract wallet or rely on third-party bundler infrastructure.

The proposal explicitly complements rather than replaces EIP-7702 and ERC-4337. Developers who’ve already built on those standards won’t need to rip anything out.

Gas sponsorship and atomic batching

With frame transactions, a third party can cover gas costs within the same transaction structure. A dApp could onboard new users who hold zero ETH by sponsoring their first interactions, all without external relayer networks or off-chain signature schemes.

Atomic batching allows bundling approve-and-swap into a single atomic operation: either everything executes or nothing does, eliminating the current risk where a successful approval and a failed swap leaves a contract authorized to spend tokens.

ERC-20 fee payment is another notable inclusion. Users could pay transaction fees in stablecoins or other tokens rather than ETH, with a frame handling the conversion or payment logic inline.

Users can also create temporary, purpose-specific accounts for individual transactions without deploying persistent smart accounts or setting up delegation.

Post-quantum implications and long-term positioning

Frame transactions create a natural structure for introducing post-quantum signature schemes. Because each frame can carry its own signature verification logic, the network could support quantum-resistant algorithms alongside existing ECDSA signatures without requiring a hard switch.

Disclosure: This article was edited by Editorial Team. For more information on how we create and review content, see our Editorial Policy.