-
Notifications
You must be signed in to change notification settings - Fork 150
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
Add support for EIP-3651: Warm COINBASE #3805
Comments
Main implementation will be in the hyperledger Besu repository - https://github.com/hyperledger/besu It should be a one or two line fix. More time will be spent configuring it for the appropriate fork. Impact to hedera-services code should be fairly transparent. Expected impact on services code is (a) a library upgrade and (b) a line or two to configure some options. Given the slippery nature of when Ethereum forms actually activate we may want to activate it via a dynamic property, however we will want to test it in integration and perf prior to shipping. We don't want to ship it into hedera's testnet prior to it activating in an Ethereum Mainnet test network, as EIPs have changed as soon as a week before such testnets. |
Team to verify inclusion |
hyperledger/besu#4620 addressed this issue in the Besu repository. |
Problem
Our current EVM model does not utilize the upcoming Shanghai details of EIP-3651: Warm COINBASE
Solution
Add support for EIP-3651: Warm COINBASE
Alternatives
No response
The text was updated successfully, but these errors were encountered: