Welcome to our weekly digest, where we unpack the latest in account and chain abstraction and the broader infrastructure shaping Ethereum.
This week: Ethereum core devs move EIP-8141 Frame Transactions toward inclusion in Hegotá as the L1 and L2 native AA camps converge; Pedro Gomes proposes splitting native account abstraction into three composable EIPs; Glamsterdam’s gas repricing exposes compatibility risks for some existing contracts and AA infrastructure; and a proposal to give ecrecover a post-quantum upgrade path.
- EIP-8141 Advances Toward Hegotá Inclusion
- A Composable Take on Native Account Abstraction
- Glamsterdam Gas Changes Put AA Infrastructure to the Test
- A Post-Quantum Upgrade Path for ecrecover
Please fasten your belts!
EIP-8141 Advances Toward Hegotá Inclusion
On All Core Developers Execution Сall #244, EIP-8141 Frame Transactions, the native account abstraction proposal, gained enough backing to move toward Scheduled for Inclusion (SFI) in Hegotá. Ethrex, Geth, Nethermind, and Besu all signaled support, a clear shift from a few weeks ago when native AA was only a candidate.
One important point: contributors clarified that this is consensus toward inclusion rather than a formally ratified decision, which still has to be recorded on a later call. Even so, the direction is now clear.
The bigger story is that the two approaches are starting to converge. EIP-8141, currently being considered for Ethereum L1, and EIP-8130, championed by Base and supported by parts of the L2 ecosystem, are being reconciled to avoid splitting Ethereum into two account models. A shared transaction type is the preferred outcome, with account interoperability, meaning the same account and address working across L1 and L2, as the fallback. Vitalik framed the two as points in one design space rather than competitors.
The call covered plenty beyond AA. Glamsterdam is entering adversarial testing on a large devnet with millions of validators and deliberate attack scenarios, ahead of proposed Glamsterdam activations on Sepolia on September 28 and Hoodi on October 26, with mainnet tentatively targeted for early December.
Developers also made history expiry a readiness requirement for Glamsterdam and kept narrowing Hegotá’s scope, with execution-client preferences due September 9 and FOCIL still the consensus-layer headliner. For a fork this large, the theme was managing risk and coordination as much as shipping features.
A Composable Take on Native Account Abstraction
WalletConnect’s Pedro Gomes published a proposal to break native account abstraction into three composable pieces rather than one large standard. The goal is to separate an account’s authority model from how transactions are actually carried, so chains can adopt the parts they want at their own pace.
The first piece, EIP-8398, defines a portable account keystore. It standardizes actors, authenticators, and account configuration so an account’s identity and permissions can move across chains independently of any single transaction format.
The second, EIP-8399, adds a basic native AA transaction type. It introduces a new transaction format with built-in batching, fee sponsorship, and keyed sequential nonces, using the keystore from the first EIP as its authority model.
The third, EIP-8400, layers on optional advanced controls like spending policies, account locking, and nonce-free transactions, all within the same transaction envelope. Base’s EIP-8130 stays unchanged, so this reads as an effort to modularize native AA and bridge the competing designs rather than replace them.
Glamsterdam Gas Changes Put AA Infrastructure to the Test
A closer look at Glamsterdam’s gas repricing shows a trade-off that matters for builders. Two proposals, EIP-8037 and EIP-8038, raise the cost of creating and touching state to support roughly three times more throughput, but they also change assumptions some deployed contracts were built on.
The new state charges are steep. Creating a new account would jump from 25,000 to about 183,600 gas, and a new storage slot from 20,000 to nearly 98,000, because these operations expand the state that every node has to store.
Researchers replayed about 930 million historical transactions against the new schedule. Most failures were fixable simply by allowing a higher gas limit, but a smaller group, roughly 2.7 million transaction replays under EIP-8037 and around 3 million under EIP-8038, remained in the potentially broken category.
The account abstraction angle is front and center. The outreach report flags the ERC-4337 EntryPoint and smart account stacks like Alchemy, ZeroDev, alongside protocols such as Across, CoW, and 0x, and warns that immutable contracts may need a new implementation and user migration rather than a simple config change.
The saving grace is timing. The proposals are still under review with a testing window open, so wallets, bundlers, indexers, and gas estimators can update before mainnet, and everyday users should be unaffected if that infrastructure keeps up.
A Post-Quantum Upgrade Path for ecrecover
Circle’s Mira Belenkiy floated a proposal to give ecrecover, the workhorse signature-checking function in countless Ethereum contracts, a post-quantum upgrade path. Rather than disabling it, the idea is to let ecrecover read post-quantum signatures carried in EIP-8141 frame transactions, triggered by a sentinel value in the usual signature fields.
The appeal is backward compatibility. A huge number of immutable, already-deployed contracts verify signatures through ecrecover, so a graceful path lets them keep working in a quantum world without redeployment, though the proposal explicitly does not try to fix EOA accounts themselves.
The thread also prompted some thoughtful pushback. One reviewer warned that adding a post-quantum path without retiring the old key is a downgrade risk, since an attacker who cracks the classical key could still spend through the unchanged path, so accounts also need a fail-closed cutoff. Another argued a clean new opcode would be better than overloading ecrecover.
The proposal is still early and remains under debate, with an EF researcher noting a preference for a deprecation path through EIP-8151. The discussion is a useful window into a quiet but important question: how Ethereum protects the enormous base of ecrecover-based code as post-quantum cryptography arrives, with Frame Transactions again at the center.
Start exploring Account Abstraction with Etherspot!
- Learn more about account abstraction here.
- Head to our docs and read all about Etherspot Modular SDK.
- Skandha — developer-friendly Typescript ERC4337 Bundler.
- Arka — an open-source Paymaster Service for gasless & sponsored transactions.
- Explore our TransactionKit, a React library for fast & simple Web3 development.
- Follow us on X (Twitter) and join our Discord.
❓Is your dApp ready for Account Abstraction? Check it out here: https://eip1271.io/
Follow us
Etherspot Website | X | Discord | Telegram | Github | Developer Portal
Top comments (0)