# L2 Interop Working Group - Call #3 **Feb 13, 2025** - [Recording](https://www.youtube.com/watch?v=rcj1neTKQOY) - [Calendar invite for future calls](https://docs.google.com/forms/d/e/1FAIpQLSfMFEJmyVgjLuiipgxprEkiQXwwK3F_PfGbWvU8ZmV6e_ka0A/viewform) ### [Agenda](https://github.com/ethereum/pm/issues/1279) 1. Updates from the message passing working group 1. L2-interop repo: walkthrough of the new github repo 1. Accelerating "intents everywhere" [presentations] - Josh (EF) - Nam (Hyperlane) - Spencer (Arbitrum) - Hart (Across) - T1 (Can) ## Call Notes *condensed notes below – recommend watching the recording (above) for full discussion* **TL;DR:** - Interop is iterative (lots of stuff already shipping) - 1st step: find most effective path to getting seamless cross-chain sends into the hands of all users. - Intents-based solutions are a great way to solve that 1st step. Lots of progress there. But, we need a shared framework to move faster and ensure ethereum-wide compatibility. - Intents are not a silver bullet & other flavors of interop will be a part of the endgame UX. - Soon will share more details on the "open intents framework" underway (plays nice with existing intents solutions, 7683, etc). Many teams are kindly supporting this initiative including Hyperlane, Across, Arbitrum, Optimism, Polymer, EF, Polygon, ZKsync, Linea, OpenZeppelin and more (DM me if you have questions / would like to support!) - Continued solid progress also on a shared standard for message passing. Thanks to Espresso, OpenZeppelin, Axelar, Base, Uniswap, OP, and all the other teams active on that front. - Reminder: we have a repo now! Go to github.com/ethereum/L2-interop. Issues/PRs welcome. Thanks to Wonderland team for pushing this. - Watch the recording for more, and for awesome presentations from Hyperlane, Across, Arbitrum, and t1. --- #### FULL NOTES COMING SHORTLY 🙏 #### AI Summary for now below (likely contains inaccuracies)... --- ### Message Passing Working Group Update - Proposed two parallel workstreams: - Development of new dev API - Integration with existing protocols (e.g., 0x, Hyperlane) - Timeline for dev API development: - Identify core contributors for regular meetings - Revisit and document goals/properties in GitHub - Set deadline for interface finalization - Establish commitments from major projects for adoption ### Open Intents Framework - Framework components: - a standard to describe intents (7683) - mutliple reference solver implementations - multiple settlement systems - Supporters include: - Optimism (Mark from OP expressed support) - Arbitrum (announced Universal Intent Engine) - Hyperlane - Across - Polygon - Linea - ZKsync - OpenZeppelin - Framework designed to: - Be neutral and open source - Support EIP-7683 compatibility - Enable multiple settlement systems - Facilitate broad ecosystem adoption ### Live Demonstrations - Arbitrum (Spencer) - Universal Intents Engine - Support for Open Intents Framework - Hyperlane (Nam) - Open Intents Framework - Across Protocol (presented by Hart): - Demonstrated EIP-7683 in production on Base to Arbitrum - Completed $10 USDC transfer in ~1 second - First few hours of Unichain launch showed: - 3-second median fill times - 4-second P90 fill time - 8 unique solvers participating - t1 (presented by Can): - Introduced TEE-enabled rollup with real-time proofs - Demonstrated potential for faster solver payments: - Average transaction: $2,200 every 16 seconds - Potential solver capital requirement reduction ### Next Steps and Collaboration - Created new L2 Interop repo hosted in Ethereum org - Teams encouraged to: - Submit PRs for improvements - Use issue templates for new tasks - Participate in documentation - Polymer team shared document for aligning on framework goals - Discussion to continue async in the Intents working group