--- tags: Forschungsingenieurtagung --- ![](https://notes.ethereum.org/_uploads/Sk7IjHZxeg.png) # Ethereum Forschungsingenieurtagung The Ethereum Foundation is organizing an L1 research and engineering workshop in Berlin at [web3.hub](https://www.w3hub.berlin/) on June 9-13, 2025. Expect a mix between past [interop events](https://blog.ethereum.org/2024/05/22/nyota-interop-recap) and [R&D workshops](https://github.com/ethereum/pm/tree/master/Breakout-Room-Meetings/DevconSEA/R%26D-workshop)! [toc] # Workshop Structure & Goals ## Implementation Tracks Two parallel client engineering tracks will run for the entire week: **Fusaka Interop** & **Performance Engineering**, with the following goals: 1. Run an all-client [Fusaka devnet](https://notes.ethereum.org/@ethpandaops/fusaka-devnet-1) that steadily handles 12 blobs per block being submitted with the same architecture as mainnet (external builders, realistic L2 transaction payloads, etc.). * Stretch Goal: Run a PeerDAS devnet with 24, 36 & 48 blobs per block being submitted without crashing. 1. [Run all clients in high gas settings](https://notes.ethereum.org/@ethpandaops/berlinterop-perf) to benchmark their opcode/precompile performance, get state growth benchmarks and analyze CL security implications. :::warning The tooling you'll need to participate in implementation tracks is linked [**here**](https://notes.ethereum.org/@ethpandaops/interop-tools) :panda_face: ::: ## R&D Breakouts In addition to the implementation tracks above, breakout sessions focused on Ethereum's **scalability** and **resilience** are scheduled throughout the week. These aim to align researchers, client implementers, and other stakeholders around the most impactful R&D areas to double down on short-term. As a general goal, **R&D Breakouts should define a prototyping plan**, with clear assignment of engineers & researchers post-interop. A stretch goal for the week is to get working prototypes (vibe coded OK!) and demo them on Friday! ## Pre-Event Goals To make the most of our time together, please come prepared. Before the event, teams should: * Implement and join `fusaka-devnet-0` (full spec TBC) * The week will be much more productive if we are debugging cross-client issues than if teams are individually working on their implementations. * [EL teams] Join [PerfNet](https://teragas.wtf/), be ready to fix bugs! * See the `#gas-limit-testing` channel * Assign specific individuals to get up to speed on the breakouts relevant to their team. * Each session will have pre-reads. Realistically, not everyone can get up to speed on everything, so please allocate bandiwdth across your team attendees. ## Event Non-Goals Covering all of this in 5 days is ambitious. To focus our efforts, it's also worth stating a few **non-goals**: * Engineering prototyping and/or devnets beyond what is required for the implementation tracks above * Comprehensively exploring all possible L1 R&D topics * Finalizing the scope for Glamsterdam # Agenda The event will run from Monday to Friday. Mornings will generally be dedicated to **Fusaka Interop** & **Performance Engineering** while afternoons will cover broader **R&D Breakouts**. On Wednesday and Thursday, external ZK and L2 teams will join for thematic breakouts throughout the day. [This preliminary agenda](https://docs.google.com/spreadsheets/d/1UqtuuBrClZCW-HD0Rd_5JUFjI8OhLXfWNtO8Wyu19YI/edit?usp=sharing) lists the most notable breakouts for each day, as well as links to relevant pre-reads when appropriate.