My vote is against including EOF in Fusaka. As we’re building a zkEVM tech stack for Ethereum, we will always maintain compatibility with the L1, and will be directly impacted by this decision. The L1 roadmap is our roadmap. In my experience, committing a high-cost feature to delivery with unconvincing value never leads to a good outcome. I haven’t seen (yet) sufficient user research data on how this will help Ethereum, Linea, ENS Namechain, Status Network, and the other Ethereum L2 rollups I’m talking to reach their business objectives, eg increase quality demand for blockspace. I’d like to see Fusaka scope kept to solve the most painful and pressing problems for Ethereum’s users (eg increasing blobs) that we have >70% confidence in, and continue to do product discovery on solutions like EOF. If it truly solves a painful problem, the solution/feature always finds a way of making it back into the roadmap, with a sense of inevitability. We’re not there yet imo. @TimBeiko @adietrichs @tkstanczak