Skip to content
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

Closed
CarlBeek opened this issue Feb 14, 2024 · 5 comments
Closed

RollCall #4 #960

CarlBeek opened this issue Feb 14, 2024 · 5 comments

Comments

@CarlBeek
Copy link

CarlBeek commented Feb 14, 2024

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

Agenda

Further discussion

Feel free to add comments to this issue with further items of discussion

@GregTheGreek
Copy link

is there a calendar invite that gets circulated?

@ralexstokes
Copy link
Member

ralexstokes commented Mar 8, 2024

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.

  • General interface: will this EIP support your L2? In particular, looking at zk-rollups and any reliance on BLS12-381 they may have (note: there's interest to extend to a fuller set of operations in Gt and expose the pairing result).
  • Point decompression precompile: the EIP currently lacks support for point decompression but it will be cheaper for rollups to leverage compressed points, expand with decompression routines and then use these as inputs to the existing precompile set. I'd like to hear what rollup teams think about this and its relative importance to include in this EIP (I could see a future EIP w/ just this set of precompiles...)

@CarlBeek
Copy link
Author

is there a calendar invite that gets circulated?

@GregTheGreek it's on the "Ethereum Protocol Calls" calendar if that helps

@protolambda
Copy link

@CarlBeek

Wed Mar 13, 2024, 15:00-16:30 UTC

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

@CarlBeek
Copy link
Author

@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.

@CarlBeek CarlBeek mentioned this issue Apr 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants