-
Notifications
You must be signed in to change notification settings - Fork 327
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 #4 #960
Comments
is there a calendar invite that gets circulated? |
I'd like to bring up EIP-2537 in the context of L2s to see if there is any relevant feedback or input they'd like to provide as we get this EIP ready for the Pectra fork.
|
@GregTheGreek it's on the "Ethereum Protocol Calls" calendar if that helps |
Is this time correct? The protocol-calls calendar has it scheduled for 14:00 UTC it seems like. DST scheduling issue? Also, 13:55 UTC is the L1 Dencun upgrade. Will the call be right after, or an hour after? I imagine many folks will be busy with the response to the L1 change, especially L2 teams in rollcall. https://blog.ethereum.org/2024/02/27/dencun-mainnet-announcement |
@protolambda the timing of the call was correct as per this issue, I just forgot to ping the protocol calendar people. That said, I'm canceling tomorrow's call as several teams have reached out saying they'd prefer to focus on shipping their own blob-forks tomorrow. |
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
Wed Mar 13Wed Apr 10, 2024, 14:00-15:30 UTCRIP 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: