note: call moving to bi-weekly cadence
Meeting Time: Tuesday, September 22, 2026 at 14:00 UTC (60 minutes)
This meeting was Frame Transaction Breakout number five on September 22, 2026, focused on updates and discussions around the Frame transaction specification and DevNet implementation. The team reviewed 13 open PRs against 8141, with Daniil indicating that none were urgent and could wait for the Frames DevNet Zero launch. Yvonne from Etherex reported that their Frames testnet had been live for fourteen days with three client implementations validating the network, including Etherex, Geth, and Nethermind, with nearly 400 frame transactions sent from about 21 distinct senders. Justin from the Besu team inquired about criteria for joining the testnet without breaking it, and Daniil confirmed that only the latest version of EELS tests was required along with contact information from Yvonne. Anders presented on unified max fee for frame transactions, proposing to replace separate max fees per resource with a single fungible max fee across resources to address base fee variations and improve user experience. The discussion covered potential impacts on mempool filtering and EVM gas accounting designs, with several implementation approaches under consideration including byte limits for state and different gas accounting models. Mislav from ETH Labs presented on a compatibility effort between 8130 and Frames, outlining plans for a fully audited, formally verified smart contract standard that would support features like EIP 7906, smart batching, and cross-chain transactions to make Frame transactions more accessible to wallet developers and app developers.
Marc opened the Frame Transaction Breakout meeting and reviewed the agenda, which included DevNet updates, client updates, and community feedback on proposals. He noted that there were no significant spec changes and highlighted 13 open PRs against EIP 8141, with most being secondary concerns to getting the DevNet Zero up and running. Marc invited Daniel and others to share if any PRs should be prioritized differently.
The team discussed the status of the Frames testnet, which has been live for fourteen days with three client implementations validating the network. Marc noted that almost 400 frame transactions were sent from about 21 distinct senders, and there are ongoing initiatives to improve tooling. The group also touched on a PR related to execution-apis, with a suggestion to create a simulateV2 that adds frame modes and multidim gas info instead of using the frame tx RLP approach.
Justin from the Besu team discussed criteria for joining testnets without breaking functionality, specifically asking about requirements for EELS, hive tests, and kurtosis configs. Daniil confirmed that only the latest version of EELS tests is required for Devnet participation and suggested contacting Yvonne for required information. Marc mentioned that FramesDevNet0 is ready to launch once team members return from being out of office, with several clients including EtherX prepared to participate. The conversation ended with plans for Anders to present about unified max fee.
Anders presented proposals for frame transactions and multidimensional fee markets, discussing three main ideas: using byte limits instead of gas limits, implementing a unified max fee, and redesigning EVM gas accounting. The team discussed potential benefits and concerns, including the impact on legacy transactions and gas estimation tools. They agreed to continue the detailed discussion on the Ethereum Magicians forum before moving forward with implementation decisions.
Mislav presented ETHLabs’ efforts to build an 8130 implementation on top of Frames, along with additional standards and developer tooling. The initiative aims to create a fully audited, formally verified smart contract that wallet and fintech developers can integrate, supporting standards like EIP 7906 and 7715. The team discussed the importance of clear signing, smart batching, and cross-chain transactions, with plans to gather feedback from 8130 authors and the broader community. Daniil raised a question about potentially increasing the max verified gas limit for DevNet from 100K to 500K, which the group agreed to discuss further asynchronously.
1Ur6?hGf)1Ur6?hGf)1Ur6?hGf)YouTube recording available: https://youtu.be/Uhrx_xh_Hhg