-
Notifications
You must be signed in to change notification settings - Fork 325
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
Proposal to Include EIP-4396 in the Shanghai Hard Fork #406
Comments
We agreed on ACD126 to not include this in The Merge, but consider it for Shanghai. @adietrichs are you OK if I just change the name of the issue to reference Shanghai instead, so we keep it open, along with the history here? |
@timbeiko did it for you 🙂 |
@adietrichs note that on #616 we agreed to use Ethereum Magicians to discuss potential Shanghai EIPs async over the next few weeks. See here for more info. |
We finalized the scope for Shanghai on ACD151, and discussions about Cancun inclusion should be moved to https://ethereum-magicians.org/t/cancun-eip-consideration/12060 |
I just now opened the PR to create what will presumably become EIP-4396.
The EIP proposes accounting for time between blocks in the base fee calculation to target a stable throughput by time, instead of by block. It appears to be desirable to have something like this in place already for the merge, to avoid (or at least greatly reduce) throughput degradation due to missed slots, or even due to potential consensus issues.
To maximize the chance of this EIP being included in the merge fork, the adjustments are kept to a minimum, with more involved changes discussed in the rationale section.
The text was updated successfully, but these errors were encountered: