# L2 Interop Working Group - Call #11 **July 9, 2025** - [Recording](https://youtu.be/pYec41Im3FE) - [Calendar invite for future calls](https://docs.google.com/forms/d/e/1FAIpQLSfMFEJmyVgjLuiipgxprEkiQXwwK3F_PfGbWvU8ZmV6e_ka0A/viewform) ### [Agenda](https://github.com/ethereum/pm/issues/1608) 1. Wallet Privacy + Interop 2. Native interop upgradeability [Ian Norden, Polymer] 3. Based rollup interop [mteam, Spire] ## Call Notes *condensed notes below – watch the recording (above) for full discussion* --- ## AI summary ### 1. Privacy & Experimental Wallet Updates - EF/Wonderland/Ambire working on experimental wallet fork of Ambire to accelerate privacy work - Key features: - Private sends and receives without revealing sender/receiver - SDK development to enable integration by major wallets - Focus on standardizing address derivation and secret communication - Documentation available at: [https://defi-wonderland.notion.site/Overview-Deterministic-Secret-Generation-from-a-Signature-2269a4c092c780d7b171eed265fd8fca](https://defi-wonderland.notion.site/Overview-Deterministic-Secret-Generation-from-a-Signature-2269a4c092c780d7b171eed265fd8fca) - Status Wallet update: - Implementing gasless private transfers with ZKP spam prevention - Collaborating with Railgun and Linea ### 2. Native Interop Between Rollups (Polymer Labs) - Core concept: Native interop verified by L1 state transition function - Current challenges: - Rollups settle differently on L1 in heterogeneous formats - Need for upgradability in verifier contracts - Difficulty maintaining parity as system evolves - Proposed solutions: - Standardize settlement (within clusters) - Push upgradability to L1 with shared registry contract - Absorb all settled outputs into rollup sequencer state transition - Team has implemented version of registry contract - Integration potential with ongoing L1 chain config work (ERC-7785) ### 3. Based Rollups & Interop (Spire Presentation) - Defined interop as user ability to move assets between apps - Base rollups offer: - Composability zones for synchronous operations - Reduced friction for developers - Backwards compatibility with existing protocols - Challenges: - Slow development of dependencies and precompiles - L1 block building pipeline limitations - Complex cost and fee structures - Future outlook: - Base rollups as one option among many for interop - Potential for isolated experiments, especially L3s on L2s - Integration with larger interop infrastructure (chain abstraction, intents)![](https://notes.ethereum.org/_uploads/SyjR-A2rgx.png) ![](https://notes.ethereum.org/_uploads/rJlxMAnSxg.png)