Account abstraction is a wildly diverse domain with many opinions forged over nearly a decade of research and development. We have honed in on the most capable and pure form and we have synthesized it into the frame transaction. In the desire for the perfect abstraction lies the root of contention. Several competing ideas have spawned to achieve similar goals. We will share a few thoughts for each. Alternatives to Frames EIP-8130: Account Abstraction by Account Configuration This is the "everything but the kitchen sink" proposal. It is comprehensive and well-thought-out. A few differences that are worth highlighting: All configs and nonces are stored in system contracts. This allows validation of transactions with a subset of the state, but it deviates from traditional account management where the smart account uses its own storage. The standard lays out accepted verifiers and some room for customization, however verifiers have no access to chain state beyond current nonce. This precludes trustless withdrawals from privacy protocols, among other use cases.
3/11/2026Glamsterdam brings significant scaling to the chain that will continue to be realized months after the fork. Hegotá is a good opportunity to return to the topic of hardness after several forks focusing on throughput. Geth Headliner Pick EIP-8141: Frame transaction We believe EIP-8141 is the right choice for EL headliner. It is the ideal companion to FOCIL as it allows smart accounts to also benefit from the improved inclusion guarantees. While the EIP is new, it only brings minor changes to work pioneered by ERC-4337 over the last several years. It gives a definitive answer to how Ethereum's execution layer will migrate to post-quantum cryptographic schemes. Because the migration will take time, it's important to begin early. It also supports other core tenets like privacy and trustlessness. A common issue with privacy protocols today is that they require an EOA with funds to withdraw, which present a chicken-and-egg problem. Frame transactions allow the withdrawal to happen first, then gas payment is approved later. For trustlessness, we can begin to remove the paymaster intermediaries and rely on our public txpool for robust and decentralized transaction relaying.
2/26/2026Add frame abstraction for transaction validation, execution, and gas payment
1/29/2026As of today, all Ethereum execution clients support history pruning for pre-merge data. For mainnet, this means 300-500 GB less disk space required to operate a node. Learn more about what this means and how to take advantage the new functionality: <insert link> If you're a full node operator or a validator, this change will not affect you beyond the space savings as history is not needed to validate the head of the chain. Archive node users and application developers who need the history to generate their custom indexes will need to begin migrating to external history providers as the history will become less available over the p2p with time. A list of providers can be found here: https://eth-clients.github.io/history-endpoints/ This is the first step towards full, rolling history expiry as defined in EIP-4444. Please see the EIP to learn more about the motivation for history expiry and the longer term plan history expiry: https://eips.ethereum.org/EIPS/eip-4444
7/7/2025