Agenda
- client progress updates
- presentation and discussion of new or updates to AA proposals
Meeting Time: Tuesday, September 01, 2026 at 14:00 UTC (60 minutes)
1 Like
Meeting Summary:
The meeting focused on updates and discussions around the development and specification of Frame Transactions and Native Account Abstraction (AA) for Ethereum, particularly in the context of the upcoming Hegatop fork. lightclient and other client teams provided updates on the stability of the spec and readiness for a DevNet, with most clients close to being ready. Daniil from Nethermind shared updates on spec changes and ongoing research into the max verified gas limit, noting that the current 100K limit may be too low for privacy protocols. Chris presented ideas for unifying the authority models of EIP-8130 and EIP-8141, suggesting a more contract-based approach and exploring the possibility of removing the signature list from the transaction envelope. The group also discussed the potential for increasing the max verified gas limit to better support privacy use cases. The conversation ended with plans to continue discussions asynchronously and to aim for a DevNet launch in the near future.
Click to expand detailed summary
The meeting began with informal conversation before transitioning to the Frames/NativeAA Breakout call agenda. Marc provided context about previous discussions regarding EIPs 8130 and 8141, noting that both camps were working towards either a single transaction type pattern or multiple transaction types that could coexist. He mentioned that EIP 8141 was recently SFI’d to signal native account abstraction as an absolute priority for the Hegatop Fork, and the team established a weekly meeting cadence that would later transition to bi-weekly. The meeting was about to begin formal discussions on spec updates and client team updates when the transcript ended.
The team discussed freezing the specification for DevNet 0, with Guru confirming the specs appear stable and lightclient agreeing to proceed with launching DevNet 0 within a week. Most client teams including Geth and EtherX confirmed readiness for the timeline, while Basu indicated they were not ready yet. The conversation ended with plans to follow up with additional client teams asynchronously and for Daniil from Nethermind to discuss their PRs.
Daniil reported updates on subtitling changes to the spec, including consolidating Frame family opcodes and modes into a shared list to improve cross-client testing speed. He also mentioned running Frozen DevNet fixtures and adding tests for gas accounting bugs. Daniil highlighted the need to increase the max verified gas limit due to current privacy pool withdrawals requiring more gas than the existing 100K limit. Marc offered support with PR reviews, specifically for specs from Agenda, while lightclient suggested treating recent roots changes as out-of-protocol rules similar to expiry frames to avoid protocol envelope modifications.
The team discussed moving recent routes from the transaction object to a frame to the recent Roots contract, with Toni confirming this approach would be acceptable as long as the route remains statically available to prevent reorg issues. soispoke raised concerns about the potential high gas costs if multiple privacy dApps update routes simultaneously, noting that 16 routes could cost around 40,000 gas. The group agreed that while the frame solution might cost more in the first frame, they could potentially exempt recent route tasks from the mempool gas limit if it becomes problematic, and confirmed that the EIP approach still makes sense as long as it’s clearly defined as a rule for the public transaction pool rather than a protocol change.
Iván provided updates on the development progress, noting that they are currently passing all Hive tests and working on writing more execution spec tests. He announced three testnets: a permissioned frames transactions testnet for clients to join permissionlessly, a closed Hegota devnet with additional EIP implementations, and a public Frame Transactions testnet. The team plans to maintain these testnets until an official EthPandaOps devnet is launched.
Chris presented ideas for unifying different authority models (8130 and 8141) into a single transaction type framework, focusing on making the verification process contract-based and extensible. The discussion explored potential changes to transaction frames, including the use of selectors, precompiles, and signature handling methods. Key questions were raised about removing the signature list and replacing it with a frame mode signature, as well as concerns about increasing the 100K transaction size limit for privacy protocols. The team agreed to continue these discussions in the 8141 channel on R&D Discord, with plans to experiment with higher transaction limits once dev nodes are running.
Next Steps:
- lightclient: Coordinate with the DevOps team to schedule DevNet Zero for Frames next week.
- All client teams: Review Daniil’s PRs in the specs repository.
- soispoke: Double-check and follow up offline on the gas cost implications of moving recent roots out of the transaction envelope.
- All participants: Consider and discuss offline the proposal to move the signature list into a frame mode signature.
- All participants: Think about and discuss the ideas Chris presented regarding a generalized transaction type and precompiles.
- Mo: Share notes and potentially form a working group to discuss increasing the max verified gas limit for privacy protocols.
- Daniil’s team: Continue benchmarks to identify a safe limit for max verified gas.
Recording Access:
- Join Recording Session
- Download Transcript (Passcode:
6%N?2cpJ) - Download Chat (Passcode:
6%N?2cpJ) - Download Audio (Passcode:
6%N?2cpJ)
YouTube recording available: https://youtu.be/2-10Mh1ODQM
Post-call note: ethereum/execution-specs#3443 merged today. It fixes an EIP-8141 gas-accounting boundary around storage refunds: payer/receipt gas remains post-refund, while block execution gas remains pre-refund, with the calldata floor applied independently to both paths.
Since the call covered the DevNet 0 spec freeze and ongoing gas-accounting test work, flagging it here so the merged behavior is visible during that pass:
https://github.com/ethereum/execution-specs/pull/3443
If this leaves a fixture or boundary case that should be pinned before DevNet 0, I can take that on.