Ethereum is turning into a labyrinth of unnecessary complexity with EOF - Let's reconsider EOF

[chfast]

@Arvolear

Because this upgrade is so complex and consists of numerous new opcodes, it must be coordinated with the L2 teams.

• For opstack , it is not as simple as “merging upstream changes”.
• For ZK rollups, constraints generation spec, tracers, zkECs, etc, need to be updated.
  • For example, Linea still doesn’t support a simple push0 opcode.
  • zkstack has its own Solidity compiler that will need to be updated as well.

I really want to believe that L2s would wish to implement EOF, but given their reluctance to ship much smaller changes, I have doubts about that.

These are general criticisms of the rollup centric roadmap, not EOF in particular. If EOF were not proposed these would still be problems, in the same way they are stated.

Note that one engineer from Optimism said that if EOF ships on mainnet it will appear on the op-stack. This is because of OP’s architecture that relies on lightly modified L1 clients, they will get the bulk of the work for free. The parts of the EVM that EOF would modify are fairly separated from the pieces that are changed to accomodate the other parts of the OP stack such as the sequencer.