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

Execution Layer Meeting 178 #931

Closed
timbeiko opened this issue Dec 21, 2023 · 6 comments
Closed

Execution Layer Meeting 178 #931

timbeiko opened this issue Dec 21, 2023 · 6 comments

Comments

@timbeiko
Copy link
Collaborator

timbeiko commented Dec 21, 2023

Meeting Info

Agenda

@CarlBeek
Copy link

CarlBeek commented Jan 3, 2024

Please can we add EIP-7587 to the agenda. It reserves the 0x100 to 0x1ff address range for RIP precompiles as we discussed on ACDE-177: #921.

@lightclient
Copy link
Member

@CarlBeek yes. I don't have permissions to update Tim's post, but will make a local note of it.

@tkstanczak
Copy link

tkstanczak commented Jan 4, 2024

Suggesting 7553 for discussion:
ethereum/EIPs@127988e?short_path=41459de#diff-41459deea2791d37cd24d9139a73beacd8e7bad2aaaa194db237754a0b8951d6

ethereum/EIPs#7949

@poojaranjan
Copy link
Contributor

poojaranjan commented Jan 4, 2024

Can we briefly discuss the RIP process and process documentation if time permits? I have some questions and would appreciate pointers to move forward with, if possible:

  • Should the Rollup proposal be added as "Standard Track - Core" or should there be a new category "Standard Track - RIP" for these proposals?

  • If/when that RIP will be considered to be deployed on the Ethereum mainnet, will it follow any different process than other EIPs considered for an upgrade? (Considering the proposal is already in "Final" status and may not accept any specs change even if suggested during testing with other EIPs.)

  • Should we move the file for EIP-7212 out of EIPs GitHub Repo as it is now being pursued as a Rollup proposal instead of an "Ethereum mainnet" proposal?

If we choose, "Standard Track - Core" for RIP proposals, we must consider updating EIP-1 according to which

Standard Track - Core are improvements requiring a consensus fork as well as changes that are not necessarily consensus critical but may be relevant to “core dev” discussions.

I'd appreciate the client devs' and EIP/RIP Editors' responses. Thanks!

@non-fungible-nelson
Copy link

I would like to discuss the Besu Mainnet halting event on January 6th. I would also like to discuss the Reddit AMA with misrepresented performance numbers, impacting the perception of minority clients.

@timbeiko
Copy link
Collaborator Author

@non-fungible-nelson I just opened #939 for this week's call. Will add this to the agenda!

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

7 participants
@tkstanczak @timbeiko @CarlBeek @lightclient @poojaranjan @non-fungible-nelson and others