You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a call to discuss a frameworks to help aid with coordination between the various EVM-like L2s. The idea is to establish optional norms and standards for L2s to be able to extend the EVM and related tooling while limiting conflicts with the L1 EVM and preventing a proliferation of mutually incompatible standards among the L2s.
Zoom link shared on RIP coordination in the RollCall channel in the EthR&D Discord which is bridged to the RollCall telegram channel shortly before the call.
Would love to discuss scheduling a break-out session to present and discuss with client teams the proposed L2 Transaction Fee API spec. Had been in principle agreed upon during RollCall #4. Just following up here
There are a couple open questions, most importantly how do we want to handle type 3 and type 4 zkevms (and other rollups that are not 100% bytecode compatible).
Imo even an aligning on existing deployment factories that are used on evm bytecode compatible rollups would already provide a huge benefit.
This is a call to discuss a frameworks to help aid with coordination between the various EVM-like L2s. The idea is to establish optional norms and standards for L2s to be able to extend the EVM and related tooling while limiting conflicts with the L1 EVM and preventing a proliferation of mutually incompatible standards among the L2s.
Meeting Info
RIP coordination
in the RollCall channel in the EthR&D Discord which is bridged to the RollCall telegram channel shortly before the call.Agenda
Further discussion
Feel free to add comments to this issue with further items of discussion
The text was updated successfully, but these errors were encountered: