Time-Aware Base Fee Calculation #4396
Conversation
|
EIP file name must be eip-###.md |
Co-authored-by: Sam Wilson <57262657+SamWilsn@users.noreply.github.com> Co-authored-by: lightclient <14004106+lightclient@users.noreply.github.com>
Head branch was pushed to by a user without write access
Head branch was pushed to by a user without write access
Head branch was pushed to by a user without write access
Head branch was pushed to by a user without write access
|
@alita-moore So close. This time it failed on the first one instead of the 4th. 😖 Merging manually since it has been discovered that I'm using the broken bot to censor people and I have to make a show of being benevolent. |
|
Oh I see this is an edge case @MicahZoltu. Shall I treat this the same as eip-1? Also typical dictators 😆 |
|
@alita-moore Why is this an edge case? What happened that caused this to not merge? |
Ah looks like I got my mentions mixed up. I was thinking about the bot not parsing eip-###.md In this case it's most likely because of the fact non-eip are not supported (this touched assets folder). Do you recommend I prioritize this above all else? |
|
Ah, I thought you already added support for |
* create EIP from template * rename EIP and fill header * add skeleton content * update specification * fixed incorrect link * updated specification to allign with EIP-1559 * added throughput graphs * add graph files * fill abstract and update motivation * fill security considerations * fill rationale * Apply suggestions from code review Co-authored-by: Sam Wilson <57262657+SamWilsn@users.noreply.github.com> Co-authored-by: lightclient <14004106+lightclient@users.noreply.github.com> * rename files using EIP number * add eth-magicians link * update header description * Update EIPS/eip-4396.md Co-authored-by: Sam Wilson <57262657+SamWilsn@users.noreply.github.com> Co-authored-by: lightclient <14004106+lightclient@users.noreply.github.com>
This EIP proposes accounting for time between blocks in the base fee calculation to target a stable throughput by time, instead of by block. Aiming to minimize changes to the calculation, it only introduces a variable block gas target proportional to the block time. The EIP can, in principle, be applied to either a Proof-of-Work or a Proof-of-Stake chain, however the security implications for the Proof-of-Work case remain unexplored.