-
Notifications
You must be signed in to change notification settings - Fork 339
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RollCall #6 #1071
Comments
Would love to discuss ethereum/RIPs#26 if possible! |
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 |
I would love to discuss if it makes sense to standardize some of the pre-installed deployment factories. Here is the draft PR for this: ethereum/RIPs#30 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. |
Summary and recording from today's call: Summary: https://notes.ethereum.org/@CarlBeek/RollCall-6-Summary |
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: