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 199 #1177

Closed
timbeiko opened this issue Oct 10, 2024 · 12 comments
Closed

Execution Layer Meeting 199 #1177

timbeiko opened this issue Oct 10, 2024 · 12 comments

Comments

@ryanberckmans
Copy link

@ryanberckmans I've added your topic to the agenda at the end, given it's very open-ended, somewhat more of a CL topic (although it has EL implications) and that we may tangentially get to a similar discussion when covering EIP-7783. Are there specific questions you'd like to bring up on the call? If so, we can try and prioritize them.

Thanks, TIm.

My specific questions would be

  • Given the emerging importance of validator bandwidth requirements in driving real-world disaster contingency planning for the validator set, how does the core dev community feel in general about the existing scope and rigor of the bandwidth research? Are we doing a great job here? If not, how can we close that gap?
  • It occurs to me that bandwidth research may have at least two different areas: research into the internal bandwidth dynamics of the protocol and client implementations, and research into the external bandwidth supply available across the world, including rural vs urban availability, growth/expansion expectations, and 1st world vs 3rd world. imo research into both these areas seems important.
  • I also asked some tactical questions here.

@ralexstokes
Copy link
Member

There was strong support from ACDC attendees on 17 October to move ahead with EIP-7742 as we are likely to make some blob count change in Pectra.

I'd request we move EIP-7742 from CFI to SFI :)

@fjl
Copy link

fjl commented Oct 22, 2024

I would like to discuss a small change to EIP-7685:

The idea is to remove empty requests data from the requests_hash commitment, which would give us a stable empty requests_hash value that isn't tied to a particular fork.

@Giulio2002
Copy link

I would like to give an update on 7783. and also with some discussions with others team: ethereum/EIPs#8974 are the guidelines for it

@frangio
Copy link

frangio commented Oct 22, 2024

I would like to discuss a change to EIP-7702:

@timbeiko
Copy link
Collaborator Author

Thanks all, I've added your topics to the agenda!

@benaadams
Copy link

I would like to give an update on 7783. and also with some discussions with others team: ethereum/EIPs#8974 are the guidelines for it

eip-7790 specifically https://eips.ethereum.org/EIPS/eip-7790

@fjl
Copy link

fjl commented Oct 24, 2024

If there is time left after Pectra discussions, I would like to bring up this issue related to revert data in eth_call and related RPC methods: ethereum/execution-apis#600

@timbeiko
Copy link
Collaborator Author

Thanks for the clarification, @benaadams! Added your final item @fjl 😄

@g11tech
Copy link

g11tech commented Oct 24, 2024

would like to bring to notice this required change to handle EIP-7742 blob base fee calc modifications

@timbeiko
Copy link
Collaborator Author

Closed in favor of #1190

@akashkshirsagar31
Copy link

Aleneth added a commit to Aleneth/pm that referenced this issue Nov 3, 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

9 participants