Frame Transaction Breakout #4, Sep 8, 2026

Protocol Calls & happenings
1

Agenda

Meeting Time: Tuesday, September 08, 2026 at 14:00 UTC (60 minutes)

GitHub Issue

2

Meeting Summary:

The meeting focused on the readiness and launch planning for DevNet Zero, particularly for Frames, with updates from various client teams and discussions on proposed changes. Matt confirmed no new spec changes were needed for DevNet Zero, while Guru reported a version 0.3.0 release for Frames that exercises deep EVM code paths and is ready for assessment. Multiple client teams, including Etherex, Nethermind, and others, confirmed readiness to launch on DevNet Zero, pending coordination with PandOps for network facilitation. The group discussed Rahul’s proposal for implementing transaction features, including expiry validation, through a new approach using the transaction payload rather than special frames, though concerns were raised about the added complexity and state dependencies. Daniil presented two PRs: an ERC proposal for standardizing key lifecycle management across EIP-8141 and EIP-8130, and a suggestion to redefine the maxverifygas constant as a mempool floor rather than a strict limit. The conversation ended with Alex seeking feedback on EIP-7906 for transaction assertions and Tamaya flagging a new proposal called “Matcha” to allow multiple Frame transactions per sender.

Click to expand detailed summary

The meeting began with technical issues regarding host labels and login status, which were quickly resolved. Marc announced they would start the formal meeting in two minutes and shared the agenda link in chat. The main agenda item focused on the goal of launching DevNet Zero Frames this week, with Matt and Guru scheduled to provide updates on specification changes and test releases respectively.

Matt reported no spec changes in the last week and mentioned that DevNet Zero is frozen except for clarifications. Guru announced the release of version 0.3.0 for Frames, which updates the ELS implementation and exercises deeper EVM code paths, making it ready for DevNet Zero assessment. The team discussed the need to identify who from PandOps would facilitate DevNet, but Barnabas was confirmed to be on vacation. The meeting focused on Frames DevNet Zero readiness and potential launch timing for this week.

The team discussed the readiness of various clients for the upcoming DevNet launch, with EtherX, Nethermind, and Iván’s implementation all reporting they are ready to proceed. Iván proposed a test for fork transition coverage and mentioned that Nethermind has successfully joined as a validator on the public testnet. The team agreed to coordinate with DevOps/PandaOps to move forward with the DevNet launch, and the conversation ended with plans to discuss FrameXFury and Nethermind PRs in the remaining agenda items.

Raxhvl presented a proposal to implement transaction expiry as a feature in Frame Transactions, suggesting moving it from a special frame to the transaction payload. The proposal includes a new feature system using key-value pairs that would allow optional transaction qualities. Lightclient and Toni raised concerns about adding state dependency and complexity, questioning whether this functionality could be implemented outside the protocol. The discussion concluded with agreement to continue the conversation in the Frame Transactions ETH discussion session.

Daniil presented two ERC proposals related to native account abstraction. The first proposal addressed defining a common key lifecycle for EIPs 8141 and 8130, introducing a tree structure with authority IDs and predicates, and proposing two tiers for storing key fingerprints on-chain. The second proposal suggested changing the definition of maxverifygas from a strict limit to a mempool floor, allowing different nodes to handle heavier transactions if capable. Marc encouraged feedback on both proposals, and Iván provided information about joining the Frames DevNet testnet for those interested in testing their clients.

Alex proposed EIP-7906 to extend Frame Transactions with post-transaction frames and opcodes for state diffs, which received feedback to focus on data and event shape. Toni recommended including transaction assertions in Hegarta without commingling it with BAL data. Soispoke flagged a new post about allowing multiple Frame transactions per sender to address privacy app needs and mempool policy limitations. The team was reminded about the upcoming ACDE meeting on Thursday to discuss client team preferences for Agota non-headliner EIPs, with a decision on Frames as a headliner expected during that meeting.

Next Steps:

  • Guru: Post the link to the Frames 0.3.0 test release in the chat.
  • Iván: Check the feedback from Guru on the proposed test for fork transition coverage for the XP verifier install after the call.
  • Iván: Send deposit tokens to Matt (lightclient) if he wants to spin up validators on the public testnet, via Telegram or Discord.
  • raxhvl: Comment on the Frame Transaction ETH Magicians session for further discussion on the proposed transaction features.
  • Daniil: Direct feedback and questions about the ERC proposal to the Ethereum Magicians topic and the PR.
  • Justin (Besu): Reach out to Iván for details on joining the Etherex testnet, via the provided link or Discord/Telegram.
  • Alex: Talk to Toni after the call about the exact shape of the data for EIP7906 (transaction assertions).
  • Client teams: Submit preferences for Agota non-headliner EIPs to Nixo and Ansgar at least 24 hours in advance of Thursday’s ACDE meeting.

Recording Access:

3

YouTube recording available: https://youtu.be/qlWcrvOHvtY