Native AA Debate, DES Explores Parallel zkEVM Execution, Affine Metering Targets Higher Throughput, Etherspot Powers Telegram Crypto UX

#web3 #blockchain #ethereum

Welcome to our weekly digest, where we unpack the latest in account and chain abstraction, and the broader infrastructure shaping Ethereum.

This week: Ethereum’s native account abstraction effort shifts into a structured multi-proposal phase, new research explores parallel zkEVM execution and higher throughput models, and Etherspot brings seamless gasless UX to Telegram-native crypto applications.

Native Account Abstraction Debate Moves Into a Dedicated Breakout Process
Delegated Execution Sharding Explores a Hyper-Parallel zkEVM Path
Etherspot Powers Blockgram’s Gasless, Keyless Crypto Experience on Telegram
Research Post Proposes Affine Metering for Higher Ethereum Throughput

Please fasten your belts!

Native Account Abstraction Debate Moves Into a Dedicated Breakout Process

Ethereum contributors held the first dedicated Native Account Abstraction breakout on April 22, shifting the discussion from headliner selection to a broader comparison of competing proposals and implementation paths. The session followed the decision not to make EIP-8141: Frame Transactions a Hegotá headliner, while still keeping account abstraction as an active priority for future fork work. The agenda explicitly covered proposal updates, adoption strategy, mempool design, statelessness and VOPS implications, privacy, and post-quantum security.

The discussion showed clear differences in priorities across stakeholders. Wallet developers focused on practical deployment concerns such as efficiency and hardware wallet support, while other participants emphasized post-quantum readiness and reducing centralization around transaction flow. The breakout also reviewed newer proposals alongside Frame Transactions, including EIP-8202: Schemed Transaction, EIP-8223: Contract Payer Transaction, and EIP-8224: Counterfactual Transaction, indicating that Ethereum’s native AA debate is no longer centered on a single design.

Frame Transactions remained the most detailed proposal in the room, but the summary makes clear that several major issues are still open. The next work items include aligning with Base, Arbitrum, and OP on performance and cost concerns, defining canonical verifiers, resolving the ERC-20 sponsorship model, and addressing statelessness compatibility questions. In parallel, the authors of EIP-7906 were tasked with building a proof of concept to show how transaction assertions could work both independently and alongside Frame Transactions.

The key takeaway is that Ethereum’s account abstraction effort is now moving through a more structured research and coordination phase rather than a single winner-takes-all proposal process. That likely makes near-term progress slower, but it also broadens the path for combining multiple ideas into a native AA design that can satisfy wallets, L2s, privacy use cases, and post-quantum migration requirements.

Delegated Execution Sharding Explores a Hyper-Parallel zkEVM Path

Ethereum Research contributor Conall O’Reilly proposed Delegated Execution Sharding (DES) as a theoretical execution-layer design that could push Ethereum toward much higher scalability by combining parallel transaction execution with recursive zk-proof aggregation. The post frames DES as an extension of ideas already being explored around Lean, post-quantum priorities, and recursive proof systems, arguing that the same logic used to parallelize validator-signature proving on the consensus side could eventually be adapted for execution as well.

The core idea is to split a block’s transactions into separate “execution columns” made up of transactions whose state effects do not collide. Those columns could then be executed in parallel by different committees, with each committee producing zk-proofs for its assigned work. A block proposer would then aggregate those proofs into a higher-level proof covering the full block. In that model, execution would no longer be bottlenecked by a single machine needing to run the entire state transition directly in real time.

The post positions this as a way to move beyond today’s scaling limit, where decentralization still depends on any ordinary node being able to re-execute the full chain. DES instead assumes untrusted parallel execution across many nodes, with validity preserved through succinct proofs rather than direct recomputation. The proposal also suggests that future gas pricing could reflect how parallelizable a transaction is, making access to heavily contested state more expensive and encouraging designs that reduce shared-state contention.

Etherspot Powers Blockgram’s Gasless, Keyless Crypto Experience on Telegram

Blockgram has partnered with Etherspot to integrate Account Abstraction into its Telegram-native crypto platform, aiming to remove much of the friction that still makes Web3 difficult for mainstream users. According to the announcement, the integration brings gasless transactions, smart accounts, and transaction batching directly into a chat-based experience on Telegram.

The setup is designed to simplify three major pain points in crypto onboarding. First, users no longer need to manage seed phrases or private keys in the traditional way, as Blockgram uses smart contract accounts through Etherspot’s Modular SDK. Second, users can pay gas fees in any ERC-20 token through Etherspot’s Arka Paymaster, removing the need to hold ETH just to get started. Third, Etherspot’s Skandha ERC-4337 Bundler enables multi-step actions to be bundled into a single on-chain transaction, reducing approval friction.

Blockgram describes the result as a “gasless, seedless execution terminal” built inside Telegram. The case study positions this as a way to make crypto interactions feel closer to Web2 messaging flows, while still preserving decentralization and self-custody. For users, the stated benefits include one-click approvals, simpler onboarding, and a chat-native way to send, receive, and manage crypto.

More broadly, the integration highlights how Account Abstraction infrastructure is being applied to consumer-facing products beyond standard wallets and DeFi interfaces. In this case, Etherspot’s stack is the core layer that allows Blockgram to hide blockchain complexity behind a familiar messaging experience, turning Telegram into a more usable crypto interface for a wider audience.

Research Post Proposes Affine Metering for Higher Ethereum Throughput

Anders Elowsson argues that Ethereum could materially improve execution-layer throughput by combining a variable PTC deadline, a single unified calldata price, and what he calls affine metering. The proposal is designed around ePBS timing constraints: as calldata usage rises, the PTC deadline shifts later, and as calldata usage falls, the unused propagation window is converted into extra execution time. In this model, calldata and execution are no longer treated as loosely connected resources. Instead, they share a direct linear tradeoff inside the slot.

The post’s core claim is that this design could let Ethereum use a much larger share of each slot for execution, roughly doubling throughput and the gas limit under the illustrated assumptions. The argument depends on replacing EIP-7976’s split calldata pricing model with a single calldata price, so that calldata is charged in proportion to the propagation burden it creates. That makes the timing model cleaner and avoids the limited scaling gains that come from letting transactions buy some calldata too cheaply.

A major criticism of EIP-7976 in the post is that its large price differential creates room for gameability. Transactions heavy in execution could effectively “auction off” their cheaper calldata allowance, while the network still has to deal with the real byte footprint. Under affine metering, every calldata byte is priced consistently, which removes that distortion and simplifies gas accounting.

The post also argues that this framework remains compatible with a future multidimensional fee market such as EIP-7999. In that version, calldata could still be treated as its own resource, while the variable PTC deadline would continue to track raw byte consumption or an equivalent constant-multiple unit.

Start exploring Account Abstraction with Etherspot!