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

devnet-5 readiness #2942

Open
9 of 10 tasks
tersec opened this issue Dec 16, 2024 · 2 comments
Open
9 of 10 tasks

devnet-5 readiness #2942

tersec opened this issue Dec 16, 2024 · 2 comments
Labels

Comments

@jangko jangko added the EL label Dec 18, 2024
@jangko
Copy link
Contributor

jangko commented Dec 20, 2024

The idea behind Update EIP-7702: Update chainid to uint256 is this
https://ethereum-magicians.org/t/eip-7702-set-eoa-account-code/19923/326?u=matt.

This have greater implication to our codebase, because we still use 64 bit ChainId and NetworkId.

Of course we can limit the changes to AuthorizationList only, but when they start to test it against network chainid using value greater than 64 bit, that can be problematic.

@tersec
Copy link
Contributor Author

tersec commented Dec 20, 2024

The idea behind Update EIP-7702: Update chainid to uint256 is this https://ethereum-magicians.org/t/eip-7702-set-eoa-account-code/19923/326?u=matt.

This have greater implication to our codebase, because we still use 64 bit ChainId and NetworkId.

Of course we can limit the changes to AuthorizationList only, but when they start to test it against network chainid using value greater than 64 bit, that can be problematic.

Ok, it can be split out from this and prioritized to after this happens, and hopefully devnet-5 won't have a chain ID which triggers this, in which case it won't matter yet, or for the other supported networks (mainnet, Holesky, or Sepolia).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants