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

EIP-7002: Implement Validator Exit Contract system call #6918

Closed
lucassaldanha opened this issue Apr 9, 2024 · 0 comments · Fixed by #7263
Closed

EIP-7002: Implement Validator Exit Contract system call #6918

lucassaldanha opened this issue Apr 9, 2024 · 0 comments · Fixed by #7263
Labels
enhancement New feature or request Prague

Comments

@lucassaldanha
Copy link
Member

Our experimental implementation of EIP-7002 is doing some contract storage manipulation to execute the same logic as the system call implemented in the contract.

However, contract storage manipulation is not the best way of implementing this. The smart contract has all the logic to handle the system call. All we need to do is implement the mechanism to perform "send a tx" from the system account. I believe we do not have this logic in Besu at the moment, the closest thing I can think of is how we use a fake transaction in the TransactionSimulator, but we would need a way of ensuring that changes in contract storage are persisted.

System call specification: https://eips.ethereum.org/EIPS/eip-7002#system-call

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request Prague
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants